Feedback Is Infrastructure

Prefer to listen in your podcast app? Apple Podcasts · Spotify

Honolulu, 1938. Beth Slingerland takes over as director of the lower school at Punahou School, one of the best resourced schools in the islands.

Some of her students are clearly bright. Engaged. Capable in every subject that doesn’t involve a page of text. And yet they cannot read.

She doesn’t jump to judgmental conclusions. She looks for what the system is failing to sense.

She starts working with Anna Gillingham and Bessie Stillman, who had spent years building a one-on-one method for teaching dyslexic children to read. Multisensory, slow, exact. See the letter. Say the letter. Trace it. Feel it in the hand and the mouth at once.

It worked. But it only reached one child at a time.

Slingerland thought it could reach a room.

She adapted the method for whole-class instruction, and in 1960, back in Renton, Washington, she taught her first class of teachers how to run it. Not one tutor. A trained cohort, a repeatable format, and a screening tool to catch the pattern early.

She wasn’t just noticing the signal anymore. She was building the pathway that let other teachers notice it too, long after she left the room.

A friend of mine trained at Hamlin Robinson School, the Seattle school built to run the Slingerland Approach. She described it to me: how a student sees a letter, says it, traces it with a big arm movement, feels it in the muscle. Vision, sound, movement, and touch, each carrying a different piece of the same signal.

Watching her demonstrate it brought me straight to operating systems.

Learning isn’t the accumulation of information. Learning is the integration of signals.

That is as true for an organization as it is for a seven-year-old learning to read.

Most organizations already collect enormous amounts of information: complaints, near misses, patient stories, denied claims, employee departures, dashboards, incidents, survey responses, financial results. Collecting isn’t the hard part. Turning what they collect into learning is.

Think about your own body. Pain is not a design flaw. Pain is information. A healthy nervous system doesn’t eliminate painful signals. It carries them, integrates them, and turns them into coordinated action before a small injury becomes a catastrophe.

Organizations feel pain too. A complaint, a near miss, a resignation, a frustrated patient, a difficult employee, a denied claim: these aren’t simply problems to eliminate. They’re nerve endings, places where the organization is sensing reality.

But sensing is only the beginning. A nerve ending that never reaches the brain can’t protect the body. A complaint that never reaches decision-makers can’t improve an organization. Information without integration is just noise.

In midwifery, no single number tells you how labor is going. Not the heart tracing alone. Not the exam alone. You read them together, along with another dozen data points, or you miss what’s actually happening.

The same principle shows up everywhere information has to become a decision. Autonomous vehicles combine cameras, radar, GPS, and lidar before deciding what’s real. The brain constantly integrates vision, hearing, touch, balance, and movement before it concludes, “This is what’s happening.”

No single pathway is enough. A patient complaint is one sensor. A denied claim is another. A near miss, an employee resignation, a difficult meeting, a quarter’s financial performance: each is a sensor too. None tells the whole story. Together they reveal patterns that none could reveal alone.

That doesn’t mean more sensors solve the problem by themselves. A hospital with twenty dashboards and no way to read them together isn’t better sensed than one with two. The rule needs both halves: pathways that let signals in, and infrastructure that brings them together. Sensing without integration is just more noise with better formatting.

This is why meetings matter, not because meetings are about communication, but because they’re sensing events. Every question asked, every hesitation, every disagreement is a chance to detect reality. A meeting that suppresses those signals doesn’t just feel unpleasant. It degrades the organization’s ability to sense.

I’ve heard a lot of chatter lately in founder circles about where feedback should happen: always private to protect dignity, always public to protect shared learning. Perhaps that’s the wrong argument. The better question isn’t where a signal is shared. It’s whether it travels, connects with other signals, and changes a decision.

Culture matters, but maybe culture isn’t primarily a set of beliefs. Maybe it’s the set of predictions people have learned from watching what the infrastructure around them actually does with a signal. When information travels, integrates, and improves decisions, people learn that reality matters. When it disappears into silence, they learn something else.

Leadership, then, isn’t only making decisions. It’s designing systems that sense reality before reality forces the issue.

Beth Slingerland could have spent her career noticing one child at a time. Instead she built a training, a screening tool, a format other teachers could run without her in the room. Almost ninety years later, a school built for exactly that purpose is still training teachers in it, and a friend of mine is still tracing letters into the air with a classroom full of students.

That’s the difference between sensing and infrastructure. Sensing ends when you leave the room. Infrastructure outlives you.

That is the signal.

The Question we posed for readers is:

Where are your organization’s nerve endings, and where do those signals disappear before they become learning?

Seen this pattern where you work? Hit reply and tell me. That's the harvest.

Want a bit more? Listen on Spotify or Apple for One More Signal about this topic.