Form Follows
Function and Faith

The moment we reclaimed clarity in that conference room shifted more than our roadmap. It forced a different posture altogether. You can only pull that many sticky notes off a wall when you’ve already counted the cost of what you’re protecting. Purpose had set a boundary that day, and once we crossed it, the entire decision landscape changed. Options that looked viable an hour earlier no longer fit. Ideas that once felt exciting suddenly felt distracting.

You’ve likely felt that shift yourself—the way clarity sharpens your instincts and strips away the noise. It’s the same energy you feel on a trail when the weather turns and you move from exploring to navigating. The terrain doesn’t change, but your relationship to it does. What matters becomes obvious. What doesn’t falls away.

That’s the moment when purpose stops being inspirational language and starts behaving like a force multiplier. It takes the sprawling set of things you could do and narrows it to the few things you must do. It cuts, trims, and simplifies until only the necessary remains. And once you’ve experienced that kind of focus, you start to see purpose for what it is: not an aspiration, but a constraint—one sturdy enough to bear weight.

That’s where the next idea begins.

Purpose as a Design Constraint

That conference room moment taught me something I’d understood in theory but had never felt in my gut: purpose isn’t decoration. It’s not the polished language you put on a landing page or the framed statement in a hallway. Purpose is a design constraint—one of the strongest constraints you can commit to, because it governs everything downstream.

When Louis Sullivan wrote that form follows function, he wasn’t arguing about the look of a building. He was naming a moral obligation. He believed that every structure carries a truth claim. A building should look like what it does. A tool should feel like what it’s for. When form drifts from function, you’re not just making a design mistake—you’re distorting intent. You’re obscuring what’s real.

But Sullivan’s clarity collapses the moment you lose track of function. That’s where most teams stumble. You watch people equate function with the backlog. You watch capability masquerade as purpose. You watch product teams justify building something simply because they can. And in that drift, purpose becomes optional instead of foundational.

Purpose cuts through that noise by asking the most direct question available to you: Why does this exist?

Not “What does it do?”

Not “What else could it do?”

But “Why does it deserve to exist at all?”

That question is clarifying because it’s ruthless. It doesn’t care about the ingenuity of your architecture or the elegance of your UX flow. It doesn’t care about the argument you crafted for leadership. It only cares about the difference between the world as it is and the world as it should be. It asks whether your work closes that gap in any meaningful way.

Once you can answer that question with conviction, the shape of your decisions changes. Choices stop feeling like a maze of equally valid options. They start sorting themselves into two categories: aligned or distracting. The work doesn’t get easier, but the path gets narrower. You stop debating whether you could do something and start evaluating whether you must.

This is what Viktor Frankl was getting at when he wrote that those who have a why can bear almost any how. Purpose doesn’t reduce effort, but it anchors effort. It gives fatigue a direction. It gives trade-offs meaning. You can stretch farther when you know the tension is attached to something that matters.

But you pay for that clarity with refusal.

When we cut 70% of that roadmap, we weren’t just choosing simplicity. We were rejecting revenue opportunities, shelving ideas that had strong advocates, and walking away from features that checked every competitive-analysis box. We were disappointing partners and peers who had already imagined what those features would unlock. We were saying no to smart, logical, well-reasoned requests because they weren’t aligned with the reason we existed.

Refusal is part of the work. Purpose narrows your field of play. It reduces surface area. It forces depth over breadth and consistency over convenience. You grow in one direction by pruning everything else. And yes, you feel that cost. You feel it in customer calls, in roadmap negotiations, in internal debates where someone says, “But this could be huge for us.”

Yet the cost of drifting is higher.

When purpose erodes, the system bloats. You collect features that don’t fit. You produce a product that’s technically impressive and strategically incoherent. You build a team that stays busy without moving in the same direction. You watch morale sag because the work feels disconnected from any meaningful arc.

Purpose is the load-bearing structure of a system. You don’t always notice it when it’s present, but you always feel the collapse when it’s gone. It’s the constraint that keeps everything aligned, honest, and true to what you set out to build in the first place.

If you want form to follow function, you have to know the function. And if you want the function to matter, you have to anchor it in purpose.

Sullivan’s Moral Architecture

Louis Sullivan wasn’t just critiquing architectural trends when he wrote that “form ever follows function.” He was taking aim at a deeper issue: the temptation to use design as a disguise instead of a declaration. His frustration wasn’t merely with excessive ornament. It was with the impulse to wrap a structure in borrowed symbolism rather than letting its purpose speak for itself.

In the late 19th century, that impulse was everywhere. Banks tried to signal stability by copying Greek temples. Corporate buildings hid behind Gothic arches meant to evoke heritage and credibility they hadn’t earned. Architects layered on decorative façades to make new structures appear older, wiser or more impressive than they truly were. The message underneath was simple: the honest building wasn’t enough.

Sullivan rejected that idea. He argued that a structure should reveal what it is and what it exists to do. A tall office building should embrace its height. A storefront should reflect the rhythms of commerce. A building deserved the dignity of its own purpose. Mimicry wasn’t elegance. It was insecurity.

His stance was moral as much as aesthetic. For Sullivan, integrity in design meant refusing to dress something up to appear more than it was. Form should emerge organically from function, not from fashion or tradition. The external shape should tell the truth about the internal reality. Anything else blurred the line between signaling and deception.

Once you see the principle, you start spotting its violations everywhere—especially in digital products. A platform with menus stacked three layers deep. A dashboard cluttered with widgets that exist only because someone asked for them years ago. A feature list padded to impress investors instead of solving real problems. These choices create the same false impressions that Sullivan pushed against. They add weight without adding meaning.

You know the feeling when you open a product and instantly understand it. No pretense. No ornamental jargon. Just a clear expression of purpose. That clarity doesn’t happen by accident. It’s the result of a team willing to choose restraint over spectacle, alignment over accumulation.

Sullivan didn’t argue for minimalism for its own sake. He argued for honesty. When a system’s form reflects its true function, you experience it as coherent and necessary—as if everything belongs and nothing is wasted.

That’s the heart of his moral architecture: design that tells the truth about what it is. Design that doesn’t pretend. Design that aligns appearance with purpose. When you build from that place, clarity isn’t a byproduct. It’s the point.

The Compass and the Map

I used to assume purpose worked like a map. You’d articulate your why, sketch the destination, and trust that clarity to lay out a predictable route. Once you had the map, you could move with confidence: build this now, add that next, follow the sequence.

But purpose doesn’t behave like a map. It behaves like a compass.

A map prescribes a path. A compass orients you. A map tells you where to place your foot. A compass tells you which way to face.

The distinction matters because the landscape never stays still. Markets shift. User needs evolve. Technology cycles speed up. Competitors adjust their posture. If you’re clinging to a map, every environmental change looks like drift or failure. You’re constantly re‑plotting, constantly validating, constantly wondering whether a detour means you’re off course.

A compass gives you something steadier. The terrain can surprise you, but the direction remains. You adjust your path without losing your orientation. You stay responsive without becoming reactive.

That’s why Sinek’s point about why over what resonates. People aren’t drawn to your feature list. They’re drawn to the direction beneath it. They’re responding to your center of gravity—to the sense that you know where you’re heading even when the road twists.

That clarity only becomes durable when it’s paired with conviction.

Conviction is the willingness to absorb the cost of alignment. You choose the harder no when the easier yes would create drift. You hold the line when compromise would blur the purpose. You accept that being focused can make you misunderstood or underestimated.

Conviction isn’t rigidity. Rigidity anchors you to a plan. Conviction anchors you to a principle. Rigidity rejects feedback. Conviction weighs feedback without losing orientation.

I’ve watched teams with a strong sense of purpose but no conviction. They can articulate their why, but they bend at every point of friction. A few customer requests pull them off center. A shiny opportunity lures them into work they don’t actually believe in. They stay busy, but they lose their shape.

I’ve also seen teams with conviction but a blurry purpose. They execute with intensity, but the direction is arbitrary. They ship quickly, but they’re not shipping what matters. Their alignment is real, but it’s alignment around the wrong thing.

Purpose without conviction is aspiration. Conviction without purpose is momentum without meaning. You need both if you want to stay oriented when the landscape shifts under your feet.

When Purpose Matured the Product

I want to tell you about a product that only found its shape once its purpose grew up.

It started as a note-taking app—one of many in an overcrowded field. In the early days, it chased feature parity like a reflex. Markdown support. Cloud sync. Collaboration. Templates. Integrations. Tags. Search. Import and export workflows. Every release added something because every competitor offered something. The roadmap looked impressive, but the product felt unfocused.

The app worked. It didn’t fail. But it didn’t matter. It was trying to be Evernote and Notion and Roam and Bear at the same time, which meant it blended in instead of standing out.

Then the founder hit a wall—not a business problem, but a purpose problem. Growth was steady. Revenue looked fine. The crisis was internal. He realized he’d built a product driven by comparison, not conviction. He’d shipped features because he wasn’t sure what else to ship.

So he stopped and asked a different set of questions. Why does this product deserve to exist? What need does it serve that nothing else truly serves? What was the original spark that made him open a text editor and start tinkering in the first place?

He remembered that he didn’t start taking notes to be productive. He didn’t take notes to organize a second brain or build a personal knowledge graph. He took notes to think. To wrestle with ideas. To slow down and hear himself. Notes weren’t a database. They were a private workspace for thought.

With that clarity, the app changed. He stripped away most of what he’d added. Templates disappeared. Collaboration vanished. Integrations were cut. What stayed was a blank page, a responsive editor, and a design that removed every bit of friction between a thought forming and a thought captured.

The app became radically simpler. And it paid for that simplicity. Some users left because they wanted productivity workflows. Others left because they wanted to organize everything in one place. Many left because they wanted more options, not fewer.

But a different user emerged. Writers who needed quiet. Researchers who needed to think on paper. People who didn’t want to manage knowledge—they wanted to explore it. For them, the app wasn’t missing features. It was free of them.

Those users didn’t merely stick around. They advocated. They wrote articles. They recorded videos. They treated the app as a thinking partner. A community formed—not because the product had everything, but because it had one thing done well.

The app didn’t scale as fast as it might have if it had stayed broad. But it scaled honestly. It attracted people who shared its purpose. It became a tool with a point of view.

That’s what happens when purpose matures. The product doesn’t balloon; it sharpens. It sheds what isn’t aligned. It finds the people it’s meant for. It becomes coherent.

Form follows function. And when the function clarifies, the form has no choice but to change with it.