When Noise Became Signal
The American River looked wild that summer—sunlight flashing off whitewater, the air thick with the smell of pine and dust, laughter carrying down from upstream. I’d come as a chaperone for a youth group from Southern California. For several days, we camped along the banks, rafting different stretches of the river under the July heat. It was the kind of trip that felt both structured and spontaneous—long days on the water, evenings around campfires, no screens, no schedules beyond what daylight allowed.
On the third afternoon, after a full run through the rapids, we pulled the rafts onto a gravel bar near a bend in the canyon. The group scattered—some skipping rocks, others cooling off in the shallows. I wandered a few yards downstream, drawn by the sound of the current. From the edge of the bank, I could see the river split around a cluster of boulders, colliding and folding back on itself before rejoining in a smooth, deep run. To the eye, it looked like chaos—competing currents, swirling eddies, random bursts of whitewater exploding from nowhere.
Then the light changed.
The sun dipped slightly, softening the glare, and the pattern emerged. What had looked like disorder began to make sense. Each surge followed a traceable path, shaped by the slope of the riverbed and the position of the rocks. The turbulence wasn’t random—it was responsive. Every twist of the current was water adjusting to resistance, seeking the easiest route forward, redistributing its energy when blocked.
The river wasn’t fighting itself. It was learning itself.
I stood there for a long time, listening. The roar of the water no longer sounded like noise. It had rhythm. Flow, impact, correction, renewal. And in that rhythm, I recognized something deeply familiar.
I’d seen this pattern in my work for years—projects that felt chaotic until we stepped back far enough to see the structure underneath. Teams pulling in different directions that, once aligned, revealed a coherence that had been there all along. Confusion that turned out to be adaptation in progress. Systems that weren’t broken, only finding their way toward balance.
The river named what I’d been trying to articulate: order isn’t something we impose; it’s something we uncover. Systems—whether natural or human—generate order constantly, but that order hides inside complexity. You can’t see it if you’re thrashing in the middle of the current. You have to step back far enough to see the flow.
That’s the work of a designer, a leader, a teacher—of anyone who builds or stewards systems. To learn to read the water. To notice where energy gathers and where it dissipates. To understand that turbulence isn’t failure; it’s feedback.
Once you see that, everything changes. The noise starts to make sense. The confusion becomes data. The patterns reveal themselves.
That’s when noise becomes signal.
The Moment of Recognition
Before I learned to see patterns, I spent a lot of energy fighting them.
Early in my career, I worked on a campus portal project that refused to gain traction. We had invested months in rollout plans, training sessions, and brown-bag demos across departments. The design was clean, the functionality solid, and leadership was supportive. But adoption lagged. People would log in once, poke around, and never return. Despite the energy we poured into promotion, the portal remained an unused doorway.
Each week brought new theories about what was wrong. We held working sessions, ran surveys, and gathered feedback from students, staff, and faculty. The suggestions varied wildly. Some wanted more integration with existing tools. Others wanted fewer. Some asked for personalization; others wanted simplicity. The feedback loops were noisy and contradictory. Our instinct was to fix everything at once—to build more features, add dashboards, adjust layouts, run workshops. It felt productive, but it wasn’t progress.
The analytics were equally disorienting. We tracked logins, click paths, time-on-page, and engagement by role. Yet no matter how we sliced the data, the picture stayed the same: users weren’t connecting with the system. The metrics told us what was happening, but not why. We were looking at the surface of the system, not its structure.
I remember the frustration that began to spread through the team. Designers blamed content owners for inconsistency. Developers blamed users for not understanding the tools. Administrators blamed both for failing to communicate the value. Every new meeting felt like a reset—a new attempt to diagnose symptoms without addressing the underlying condition. We were busy, but we weren’t aligned.
The turning point came when I asked a simple question to my student staff: “What would make this portal actually useful for you?” Their answers shifted everything. They didn’t want more announcements or prettier layouts—they wanted tools that made their daily lives easier. That conversation led to an experiment over Christmas break. We built a student dashboard—not because leadership asked for it, but because the students did.
The dashboard wasn’t fancy, but it was real. It displayed their current schedule and showed the next class location and time. It included a live camera feed from the cafeteria so they could see if they had time to grab lunch before class. We added another feed from the campus convenience store, along with their balance on their campus card. It wasn’t a massive redesign—it was a reorientation toward relevance.
When students returned from break and logged in, adoption skyrocketed. Word spread fast. They started using the portal daily—not because they had to, but because it genuinely helped them navigate campus life. That was the breakthrough moment for the entire initiative. We realized adoption wasn’t about awareness or design polish. It was about alignment—providing the right information to the right people at the right time.
From there, the insight cascaded. Staff, faculty, and administrators each needed their own kind of usefulness—different dashboards, data, and pathways. The portal wasn’t one system. It was many systems connected by purpose. Once we recognized that, everything else started to fall into place.
Looking back, I can see the pattern clearly. For months, we treated adoption as a communication problem when it was really a systems problem. The breakthrough wasn’t technical—it was structural. We stopped trying to push people into a generic system and instead designed pathways that reflected their realities. That was the moment I learned that behavior follows structure—and that structure must begin with empathy.
The Cost of Noise
Not long after that earlier project, I found myself in a completely different world—this time working inside a media company that managed a sprawling portfolio of college sports sites. Each site served a passionate fan base, covering dozens of teams across multiple conferences. The scale was exhilarating: millions of unique visitors, massive traffic surges on game days, and a constant stream of stories, stats, and highlight videos.
But with that scale came a familiar challenge. The signals were buried in noise.
We had data pouring in from every direction—page views, ad impressions, social shares, livestream metrics. Every dashboard demanded attention, yet despite all the activity, one number refused to move: retention. Traffic spiked around major games and evaporated almost as quickly. Fans showed up for the score, then disappeared until the next big matchup. We were building features, producing content, and refining layouts, but we weren’t creating sustained engagement.
The turning point came one evening in a dim analytics room surrounded by screens filled with dashboards from across the network. A data analyst—one who had quietly tracked user behavior over several seasons—displayed a single graph that changed everything. It plotted session length over time, segmented by user cohort. At first glance, it looked ordinary. Then she pointed to one line.
Users who engaged with a specific type of content within their first three visits—not the content we had been optimizing for—had retention rates five times higher than everyone else. It wasn’t live scores or stats that brought them back. It was stories —the human side of the game—promoted before kickoff. Those who read pregame stories, tuned in to a livestream, and returned later for highlight videos stayed. Those who didn’t almost never came back.
We had been optimizing the wrong thing. We obsessed over real-time data accuracy, mobile layouts, ad placements, and site performance. All important, but none of it explained why some users stayed and others drifted away. The system had been showing us the signal the entire time—through patterns of behavior repeating week after week, season after season—but we were too busy amplifying our own noise to hear it.
The insight felt almost embarrassingly simple: people weren’t loyal to the platform. They were loyal to the story. Our best users followed a rhythm of engagement—before, during, and after the game. They came for anticipation, connection, and closure. The continuity of story, not just the immediacy of score, sustained their attention.
We’d mistaken the medium for the meaning. We built elegant front ends and sophisticated live feeds, but the structure of our content failed to reflect the natural emotional cycle of fandom. We weren’t designing for the rhythm of human attention; we were designing for the cadence of our CMS.
Once we saw the pattern, our approach changed. We began designing around the fan’s journey instead of the site’s structure. Pregame stories moved front and center 48 hours before kickoff. Livestreams became the anchor during game time. Postgame highlight videos and recaps were published within hours, linked directly to the next matchup. The product team built lightweight automations to surface this cycle across every site, creating a consistent pattern of engagement that mirrored how fans actually experienced sports.
Within two months, repeat visits doubled. Within six, they tripled. Average session time soared, and user churn dropped by half. We hadn’t added new features. We had removed them—simplifying navigation, consolidating modules, and aligning the experience around the one behavior that mattered most: connection through story.
The system hadn’t changed. Our ability to read it had. Noise had blinded us to the feedback loops hiding in plain sight. What felt like chaos—millions of clicks and sessions across hundreds of sites—contained a coherent pattern waiting to be recognized. Once we tuned into it, the work became simpler. Every decision became a question of alignment: does this amplify the story, or distract from it?
That was the real cost of noise. Not confusion, but misdirection. The system was speaking clearly all along. We just weren’t listening.
