Form Follows
Function and Faith

We started at the Canadian border, where the North Fork of the Flathead River cuts a quiet line between Montana and the edge of Glacier country. Morning light settled on the water like a calm invitation, but the stillness didn’t last. South of us, the Nez Perce and Salmon–Challis National Forests were burning. Not one fire. Many. A patchwork of closures, warnings, and shifting conditions that reshaped the Great Western Trail day by day.

The Great Western Trail isn’t a single route—it’s a chain of off‑road tracks, forest roads, and scenic byways that carry you from the Canadian line all the way to Mexico. Its beauty is its sprawl. Its challenge is the same. You move through ecosystems the way you move through seasons, each section asking something different from you. That fall, the mountains asked for patience.

By the second afternoon, the sky had turned the color of a campfire ember. Smoke pooled in the valleys, rolling up the ridgelines in thick waves that bent with the wind. We found ourselves pulling over more than we planned—checking maps, cross‑referencing satellite updates, figuring out which parts of the trail were still safe to cross and which had been swallowed by closures. Routes we’d marked months earlier vanished behind glowing perimeters. Others, farther east or west, suddenly became our only path.

There were moments where we moved quickly—windows cracked, headlights on in the middle of the day—threading through long stretches of haze where the mountains looked like ghosts. And there were moments where we didn’t move at all, waiting in clearings for visibility to return, listening to the low hum of the wind push smoke across the tree line. The goal was still the same: Mexico. But the trail kept reminding us that purpose matters more than speed.

One night, camped just below a ridge that looked out over a valley tinged orange from distant flames, I felt that reminder land. Progress wasn’t measured by miles. It was measured by whether we were still aligned with why we set out in the first place. We weren’t out there to conquer anything. We weren’t chasing an arbitrary timeline. We were learning how to make the next right call with the information we had, even when the landscape refused to cooperate.

Years later, standing in a conference room surrounded by a wall of feature requests, the same instinct surfaced. The details were different, but the dynamic was familiar—too many paths, too little clarity, and a creeping sense that movement had replaced direction. I recognized the feeling from those smoke‑filled valleys: when everything looks possible, it’s dangerously easy to forget what’s essential.

And just like on the trail, the answer wasn’t to push harder. It was to remember why we started.

The Room Where We Said No

The conference room carried the familiar mix of cold coffee, worn carpet, and the faint chemical smell of whiteboard markers. We’d been inside long enough to forget what time it was. The wall behind me had disappeared under a grid of sticky notes—feature requests, each backed by data, each advocated by someone who genuinely believed it would help. Taken together, the roadmap looked less like a plan and more like a signal that we’d let the problem sprawl.

I stood with the marker in my hand, realizing how far we’d drifted from the simplicity that sparked the project. The platform we were building for small nonprofits started as a focused solution: help them track donors without drowning in spreadsheets. Over time, that clarity blurred. Event management joined the list. Email campaigns. Volunteer coordination. Grant tracking. None of it was wrong, but none of it came from purpose. It came from possibility.

We were six months from launch. Every new idea had a champion. Every request had a rationale. And yet, as I scanned that crowded wall, I felt something deeper than scope creep. I felt the weight of forgetting why we started.

Our lead engineer broke the silence first. “We can’t ship all of this in six months. We need to cut two-thirds of this board.” He wasn’t challenging the ambition. He was naming the cost.

The room went still. Everyone understood the truth in his words, but no one wanted to choose which vision to disappoint. Prioritizing by revenue made sense. Surveying beta users made sense. Ranking by engineering effort made sense. But every suggestion kept us anchored to the same assumption: that more features somehow equaled more value.

I set the marker down and asked a different question. “What are we actually for?” It wasn’t a dramatic line. It was a genuine admission that we’d been moving so fast we hadn’t looked up in months.

You could feel the shift. The question pulled us out of tactics and into purpose. Our designer, who had been silent most of the morning, spoke up. She reminded us of the early conversations with small nonprofits who were juggling donor lists across half a dozen spreadsheets. She talked about directors who stayed up late trying to remember who gave last month, who needed a thank-you note, who had drifted away. She reminded us that the whole point was to give them a system that supported relationships instead of burying them in workflows.

This time the quiet in the room felt different. It felt like alignment.

I turned back to the wall and started pulling down sticky notes. Not in frustration, but with clarity. Event management went first. Email campaigns followed. Volunteer scheduling. Grant tracking. Anything that pulled us away from the core function of helping small nonprofits sustain meaningful donor relationships.

When the board cleared, what remained felt unmistakably right: a tool built to remember people, track relationships, surface patterns in giving, and make gratitude timely instead of accidental.

Cutting the roadmap by seventy percent didn’t feel like loss. It felt like purpose reasserting itself. Someone in the room laughed—not out of surprise, but because clarity often brings relief you didn’t realize you needed.

The trade-offs arrived quickly. A potential partner walked away because we wouldn’t build event management. A beta user chose another tool for its broader feature set. Competitors rushed updates while we stayed focused. None of it felt good in the moment, but it all reinforced the same lesson: purpose always carries a cost.

Sticking to that purpose changed the way we made decisions. Every new feature request faced the same test: Does this help small nonprofits remember people? If the answer wasn’t a clear yes, we didn’t build it. The conversation ended before the rabbit holes began.

The product we finally shipped wasn’t the biggest or the most expansive. But it held together. It made sense. And nonprofits didn’t just adopt it—they appreciated it. Because it delivered the one thing they needed most: a clear, dependable way to strengthen relationships in the work that mattered to them.

The room where we said no became the room where the product found its shape.

The Emotional Stakes of Clarity

That moment in the conference room wasn’t just about product strategy. It forced us to confront who we were becoming and whether we still recognized ourselves. You face these moments more often than you expect in product work—the moments where the debate on the surface is about features, and the debate underneath is about identity. Were we still the team that set out to build something helpful for small nonprofits, or had we drifted into building whatever anyone asked for? The walls were covered in ideas that all made sense individually, but together they represented a version of the product none of us had originally set out to build.

When we finally pulled down those sticky notes, the room shifted. It wasn’t discouragement. It was release. You could feel shoulders drop. You could sense the focus returning. Every person in that room knew we’d been carrying an expanding set of obligations that didn’t belong to us, and setting them aside felt like reclaiming our work rather than abandoning it.

One of our engineers—someone who had been grinding through every iteration with us since the beginning—spoke up quietly: “I forgot why I joined this team. Now I remember.” That sentence landed harder than any roadmap review or stakeholder meeting we’d held in months. It reminded all of us that clarity isn’t academic. It has emotional weight. When you rediscover the purpose that brought you together, you reconnect to the reason you said yes in the first place.

Purpose does that. It brings you back to the origin story: the problem that bothered you enough to act, the people you wanted to serve, the moment when you saw a small gap in the world and believed you could add something meaningful. Purpose narrows your attention to what matters. It frees you from pretending you can be all things to all people.

What I didn’t see coming was how the shift affected the people using our product. The first wave of feedback after we shipped the simplified version looked different. Instead of long feature requests, we started getting notes that sounded like relief. People thanked us for resisting the urge to overload the tool. They noticed the restraint. They noticed the focus.

One nonprofit director put it plainly: “Every other tool I’ve tried makes me feel like I’m managing a database. Yours makes me feel like I’m caring for people.” That line stayed with me because it revealed something we hadn’t articulated out loud: when you design from purpose, the experience changes. Function stops being a checklist of features and starts becoming a reflection of what you believe matters.

That’s the shift from form following features to form following function. It’s the difference between accumulation and intention. When you remove what doesn’t serve the core purpose, what remains feels coherent. It feels honest. People sense that even if they never name it. They recognize when a system respects their time. They recognize when a product sees them rather than their data. They recognize when the design grows from conviction instead of competition.

Clarity shows up in how a product works, but it also shows up in how it makes people feel. And when you get that right, the feedback changes from critique to connection.