Chapter Three

Form Follows
Function and Faith

Purpose & Conviction:
Function becomes meaningful when guided by belief.

Meaning as a Design Constraint

17–25 minutes

You reach a point in any meaningful endeavor where purpose stops being an inspiring idea and starts becoming an operational boundary. Earlier in the chapter, purpose acted like a pruning tool—removing what didn’t belong, narrowing options, and exposing what mattered. But once you’ve trimmed the excess, you face a different kind of pressure. Not the pressure to expand, but the pressure to stay true.

That’s where meaning steps in. Purpose defines why something exists. Meaning defines what it demands of you. You can articulate a purpose once, but meaning shows up every day in the decisions you make, the requests you decline, and the opportunities you leave on the table.

Teams often think conviction shows up in the bold moments—the big strategic pivots, the daring bets, the public declarations. But you discover what you actually believe in the quieter moments, when no one is watching, when a decision feels small enough that bending the rule seems harmless. Those little decisions reveal whether your purpose is a statement or a standard.

And this is where design shifts from intention to discipline. Purpose doesn’t just guide what you build. It guides what you refuse to build. It shapes the edges of your identity. It protects the integrity of the thing you’re trying to make.

That’s the threshold you step into now—the space where meaning becomes an active constraint. Not a philosophical one, but a practical one. A constraint that forces you to decide what you will not do because doing it would pull you away from what you’re for.

Which leads to the first practice that gives meaning its shape: learning to refuse with conviction.

The Practice of Refusal

The hardest part of designing with purpose rarely shows up in the headline decisions. It shows up in the tiny ones—the ones that arrive quietly, look reasonable, and carry just enough logic to slip past your defenses if you’re not paying attention.

It’s the feature request that technically makes sense but subtly drifts you off mission. It’s the partnership that promises new revenue but asks you to soften the very thing that made you distinct. It’s the phrasing that sounds polished yet blurs what you actually do. These aren’t dramatic betrayals. They’re small, polite departures from purpose.

And those small departures accumulate. Each one feels justifiable. Each one feels temporary. But each one nudges you a little further from what you’re for. Over time, the distance adds up.

Alasdair MacIntyre captures this with unsettling clarity: we become what we practice. Every decision is a rehearsal for the next. Every yes reinforces a direction. Every no reinforces a boundary. Identity isn’t declared. It’s formed by repetition.

If you practice alignment, you become coherent. If you practice compromise, you become fragmented. Purpose doesn’t erode in a single moment. It erodes through a sequence of unexamined concessions.

Pressure to compromise is guaranteed. The real question is whether you’ve built a way to test the pressure. You need a practice that helps you examine the cost before you pay it.

The one I’ve relied on is disarmingly simple: Does this serve the why?

Not “Could this eventually serve the why?” Not “Is there a scenario where this might serve the why?” But “Does this, right now, directly serve the why?” That question cuts through rationalizations because it forces you to evaluate the present, not the fantasy.

If the answer is yes, you keep exploring. If the answer is no, you stop. The discipline is in stopping.

It never feels easy. Saying no often feels like loss. It feels like turning down opportunity. It feels like you’re closing a door that others would gratefully walk through. It feels narrow when everyone else seems to be expanding.

But refusal isn’t narrowness. Refusal is clarity.

When you refuse what doesn’t fit, you create room for what does. You create room for depth instead of scatter, excellence instead of adequacy, intention instead of busyness. You begin to build something that feels shaped rather than swollen.

John O’Donohue wrote that beauty is the illumination of your soul. He wasn’t talking about cosmetics. He was naming integrity—the moment form, function and purpose align. Beauty emerges when nothing is pretending to be something else.

And people can feel that integrity before they can explain it. They sense coherence. They sense when something has been shaped with care and conviction. They lean in because it feels trustworthy.

They can feel the opposite too. They notice when features are bolted on. They notice when language inflates to mask confusion. They notice when purpose gets buried under ornament or ambition. Even if they can’t articulate it, something feels off.

We’re wired to detect patterns. We can feel incoherence long before we can name it.

The Courage to Be Narrow

There’s a particular kind of courage required to design with purpose: the courage to be narrow.

We live in a culture that rewards doing more. More features, more audiences, more use cases. The assumption is that scale comes from expansion, that credibility grows with scope, and that success means widening your reach until you cover as much ground as possible.

But you’ve seen where that path leads. Breadth often undermines depth. When you try to serve everyone, you struggle to serve anyone well. The signal blurs. The focus scatters. The integrity of the work starts to bend under the weight of accommodating everything and protecting nothing.

Purpose demands a different posture. It asks you to draw boundaries and hold them. It forces you to declare who you’re for and who you’re not for, what you will do and what you will refuse to do, even when that refusal looks like you’re leaving opportunity on the table.

You already know how uncomfortable that feels. You risk turning away people who might have paid you. You risk sounding smaller than your ambitions. You risk being misunderstood by those who think value comes from being universal.

Yet choosing to be narrow is the most honest act of service you can offer. When you’re explicit about who you’re for, you create the conditions for real depth. You free yourself to design with precision instead of approximation. You build something that speaks directly to the people you’re committed to serving, not a watered-down version made to offend no one and delight no one.

And the gift extends in both directions. The people you serve get clarity about what they can count on. They see your decisions align with their needs. They recognize the conviction behind your choices. The people you’re not for get clarity too. They can move on without friction, without wrestling your product into a shape it was never meant to take.

This is the alignment Simon Sinek points to: people buy the reason behind what you build, not the catalog of features you bolt onto it. They’re responding to your intention. They’re responding to your willingness to hold a line. They’re trusting that you won’t sacrifice the core purpose in the name of pleasing everyone at once.

But that trust only forms if you’re willing to resist expansion for expansion’s sake. I’ve watched teams lose that resistance. They begin with a sharp purpose, something with edges. Then the pressure arrives: investors pushing for broader markets, sales teams lobbying for new features to close deals, marketing insisting on a wider umbrella.

The drift is rarely dramatic. It’s incremental. A compromise here, a small expansion there. Soon the purpose that once guided every decision becomes soft around the edges. The product that once served someone specific becomes an all-purpose tool for no one in particular. The message that once stood firm becomes a vague, bloated claim that could belong to any competitor.

What’s lost in that drift isn’t only focus. It’s meaning. Because meaning shows up when you commit to serving a specific need without apology. When you refuse to dilute the work just to gather more attention. When you choose depth over reach.

The courage to be narrow is the courage to matter. It’s the willingness to stand somewhere instead of everywhere. It’s the discipline to stay true when the easiest thing in the world is to expand your way into irrelevance.

The Feedback Loop of Alignment

Purpose creates a feedback loop that shapes every choice you make. When you act in alignment with what you stand for, those choices reinforce your identity. They sharpen the edges of who you’re becoming. They signal to your team, your users, and even to yourself: this is what we’re building and this is why it matters. Alignment draws in the people who resonate with that purpose and filters out the ones who don’t.

You feel that reinforcement in the work. Each decision that fits your purpose builds confidence. Each refusal of something misaligned strengthens your ability to recognize the next right move. The momentum becomes self-reinforcing. You start to trust the direction because the decisions keep confirming it.

The inverse happens just as reliably. When you act against your purpose, even in small ways, the friction is immediate. A decision that looks harmless in isolation begins to chip away at your identity. Confusion spreads. Your team hesitates because the signals conflict. Your users notice shifts they can’t articulate but can feel. Misalignment attracts the wrong expectations and the wrong audiences, which multiplies the confusion.

And that drift compounds. One misaligned choice makes the next one easier to rationalize. A small exception becomes precedent. Before long, the product reflects compromises rather than conviction.

This is the dynamic Donella Meadows describes when she writes about leverage points—places in a system where a small adjustment yields outsized impact. Purpose is one of the highest leverage points you have. It’s upstream of architecture, process, features, and culture. It influences what you choose to build, how you prioritize, who you serve, and what you refuse.

When purpose is clear, the entire system stabilizes. Decisions begin to harmonize. Feedback loops reinforce the direction rather than destabilize it. The work feels coherent because it is coherent.

When purpose is vague, the system loses integrity. Decisions contradict each other. Feedback loops tangle. The work feels chaotic because the center is missing.

This is where Nassim Taleb’s framing of antifragility becomes useful. A system becomes stronger under stress only when it has a non-negotiable core. That core isn’t rigidity—it’s conviction. You adapt your tactics, but you don’t trade your reason for existing.

Purpose gives you that anchor. When you’re clear on what you’re for, you can flex in everything else. You can pivot without losing direction. You can respond to feedback without diluting identity. You can manage complexity without becoming reactive.

But without that anchor, stress doesn’t strengthen you. It scatters you. You chase every possible angle. You respond to every complaint. You drift with the loudest voice or the latest trend. The work becomes unmoored, and so do the people doing it.

Systems Thinking and Purpose as Leverage

Donella Meadows pushed us to see systems not as collections of parts but as webs of intent. She argued that if you want to influence a system, you have to find the leverage points—those few places where a small shift creates a disproportionate effect. Her list of twelve leverage points starts with the obvious but weak levers like numbers, buffers and flows. At the top sits the hardest one to touch: the ability to transcend paradigms.

Just beneath that, though, sits something most leaders overlook: the goals of the system. In practice, that’s purpose.

Purpose carries weight because it’s positioned upstream from structure, incentives and behavior. It shapes what you measure, what you reward, how you organize, what you optimize for, who you bring onto the team and what you choose to build. When you alter purpose, you don’t just tweak the system—you redirect the entire flow of decisions that cascade from it.

This is why drift is costly. When purpose loses definition, downstream questions become impossible to answer cleanly. What should we prioritize? Which metrics matter? What trade-offs are acceptable? Without purpose as the anchor, these decisions turn into internal negotiations instead of straightforward reflections of what you’re trying to achieve.

I watched this unfold inside a company that began with a focused mission: make healthy food affordable for low-income families. That single goal shaped everything. They optimized for accessibility, not margin. They measured success by how many families they served. They hired people drawn to food justice, not just retail experience.

Growth brought pressure. Investors wanted scale, and leadership shifted their language. Conversations that used to center on affordability shifted to market expansion and competitive positioning. The mission statement stayed on the website, but the operative purpose changed. The new north star was growth for its own sake.

The system adapted to that new goal with unnerving speed. Prices rose to improve margins. Marketing targeted wealthier customers. Hiring skewed toward traditional retail talent. Within two years the company had drifted so far that the original team barely recognized it. Revenue climbed, investors smiled and the numbers looked great, but the families they once served couldn’t afford the products anymore.

The founder exited. Early employees followed. The system had evolved into something coherent but misaligned with its original intent.

That’s the kind of leverage purpose holds. When it’s clear and protected, it creates stability. When it drifts, the entire system tilts with it.

Meadows also warned that systems resist changes to their goals. Reinforcing loops defend the status quo. That’s why purpose can’t be shifted through a rephrased mission statement alone. You have to adjust the incentives, metrics and structures that support the old direction.

But when those structural elements move in support of a clarified purpose, the effects multiply. Decisions that once felt complicated fall into place. Priorities sharpen. Teams stop debating what matters and start acting on it. The system aligns around the goal, and everything downstream begins to make sense again.

What Is Your Irreducible Purpose?

I want to ask you a question, and I want you to pause before you answer it. Set aside the deck you’ve presented a hundred times. Set aside the positioning statements you’ve polished. Set aside the features you’ve fought for.

What is the irreducible purpose of what you’re building?

Not the mission statement. Not the value prop. Not the roadmap.

What is the one thing that, if removed, would make the entire effort meaningless to you?

What is the why that gives every how its legitimacy?

Most of us never get this far. We know what we’re building. We can explain how it works. We can describe the personas, the flows, the user journeys. But ask why it needs to exist at all, and the answer often gets blurry. You hear phrases like “market opportunity” or “competitive gap” or “customer demand,” but not the conviction that anchors an identity.

When you operate without that conviction, you drift. You add because you can. You build because the team has capacity. You solve problems that don’t matter. You introduce complexity no one asked for. You start mistaking activity for progress.

But when you know your irreducible purpose, the entire system reorganizes around it. Decisions that felt heavy become straightforward. You start recognizing which options actually move you toward your purpose and which ones only create noise. You sort signal from static.

You know what belongs in the product and what deserves to be cut. You know which opportunities to pursue and which distractions to decline. You know which metrics reveal truth and which ones only inflate your ego. You know what to celebrate because it affirms your purpose, and what to mourn because it betrays it.

You understand what you are for.

And that clarity doesn’t remove the difficulty of the work. It gives the work a direction. You’re no longer wandering through a maze of possible futures. You’re moving with intent toward something that matters enough to constrain you.

Your irreducible purpose is the anchor that keeps your form honest, your function meaningful, and your conviction intact.

The Feature That Failed the Test

Let me tell you about a feature we almost shipped.

It started as a simple request: give nonprofit leaders a single place to understand their outreach. The team mocked up a dashboard that was polished, fast and undeniably impressive. You could scan giving trends, retention patterns and engagement scores in seconds. Predictive analytics sat at the top like a badge of sophistication. It was the kind of feature that wins demos and makes investors lean forward.

But when we set it against our purpose, it collapsed.

We weren’t building a tool for optimizing conversions or squeezing more yield from donor lists. We were building something to help small nonprofits remember people. To help them honor stories, not segments. To narrow the distance between a donor and the impact they cared about.

And this dashboard—beautiful as it was—pulled in the opposite direction. It turned names into metrics. It made relationships feel like abstractions. It nudged users toward managing people instead of caring for them. Every improvement we added only made it more impressive and more misaligned.

That tension forced a hard call. The dashboard wasn’t a bad idea. In another product, with another purpose, it might have been essential. Some beta users asked for it. A prospective investor called it the missing piece. Competitors flaunted their dashboards as proof of maturity.

But none of that changed what the feature did to us. It eroded the thing we were trying to protect. It didn’t serve the why that anchored everything else.

So we cut it.

And the cost was real. We lost a beta user who needed analytics for a board report. We lost an investor who questioned whether we were thinking big enough. We walked away from the comfort of looking like every other CRM in the space.

But the gain was real too. By saying no, we kept our purpose intact. We kept our identity sharp. We created space to build what actually mattered.

You can add features later. You can upgrade, extend or modernize almost anything with enough time. But recovering a compromised identity is something else entirely. Once you dilute your purpose, every future decision becomes harder to untangle.

The features you refuse shape your product as much as the ones you release.

Sometimes they shape it more.

Where Could Less Align Form with Function?

I want you to step back from what you’re building and ask a different kind of question. Not the familiar ones about roadmaps, competitive gaps or feature velocity. A sharper question. A braver question.

Not “What could we add?” but “What could we remove?”

Not “What are we missing?” but “What doesn’t belong?”

Not “How can we do more?” but “How can we do less, better?”

Most teams never ask these questions because they feel counterintuitive. Growth looks like addition. Progress looks like expansion. Success looks like breadth. You’re rewarded for showing momentum, for pointing to what you shipped, for proving you can keep pace with everyone else.

But addition without intention erodes clarity. You’ve seen it in products that started simple and slowly bloated. You’ve seen it in teams that once moved with purpose and now struggle under the weight of too many priorities. You’ve seen it in your own work when something you built with conviction became crowded with reasonable but unnecessary extras.

The uncomfortable truth is that most of us are building too much. We add because the cost of saying no feels higher than the cost of saying yes. We take on features that don’t serve purpose because we’re afraid someone will think we’re falling behind. We conflate capability with value and abundance with meaning.

But value doesn’t flow from abundance. Value flows from coherence.

Coherence is what you feel when you encounter something designed so intentionally that it seems inevitable. There’s a confidence to it. A sense that every element earns its place. Nothing distracts. Nothing apologizes. Nothing performs a role it shouldn’t.

Coherence emerges when you align form with function. And function, if you’re honest with yourself, emerges from purpose.

This is the heart of Sullivan’s argument. Form follows function. Not form follows features. Not form follows whatever the market expects this quarter. Not form follows what makes the demo impressive for five minutes.

Form follows function. And function follows purpose.

When you accept that cascade, you give yourself permission to remove everything that interrupts it. You give yourself permission to design with conviction instead of anxiety. You give yourself permission to pursue clarity without apology.

So ask yourself this:

Where could less align form with function in your work?

What feature could you cut to reveal the product’s true center of gravity? What language could you simplify to strengthen the promise you’re making? What process could you streamline to reduce friction and help the system breathe again?

Where are you holding onto ornament—visual, technical or strategic—because it makes you feel safe, not because it serves the purpose?

And here’s the question beneath all the others: What would your work look like if everything unnecessary disappeared? What would remain that tells the truth about what it’s for?

Beauty as Integrity

John O’Donohue wrote that beauty is the illumination of the soul. He wasn’t talking about charm or polish. He was naming a kind of clarity that appears when what’s inside and what’s outside finally match. You feel it when something stops performing and starts being itself.

Most of us inherit a weaker idea of beauty. We think of it as enhancement. As flourish. As something you apply when everything else is done. That version of beauty sits on top of the work. O’Donohue’s version emerges from inside the work. It’s what becomes visible when you remove what doesn’t belong.

You create that kind of beauty through integrity. Not moral perfection, but coherence—every part aligned with purpose, every detail connected to intent. When the form carries the essence honestly, beauty shows up without being asked to.

You’ve probably felt this in products that seem understated at first glance. They’re not loud. They’re not overloaded. They don’t chase feature parity with competitors. Yet something about them feels right. Every element earns its place. Every interaction supports the reason the product exists. Nothing in the experience tries to distract you from what the product is for.

That sense of rightness is beauty functioning as integrity. It’s the calm that appears when there’s no internal contradiction, no mixed motives hiding under the surface. You trust these products because they aren’t trying to do more than they should.

You can apply the same test to your own work. When someone encounters what you build, can they feel the through-line? Can they sense the care behind each choice? Do they notice that nothing exists for ornament alone? People may not articulate it in those terms, but they notice when every part serves the purpose instead of competing with it.

This is what Sullivan was pointing to when he said form follows function. He wasn’t only pushing against decorative excess. He was describing a deeper kind of beauty—the beauty that emerges when a thing is true to its purpose. When the design doesn’t pretend. When the form doesn’t perform. When nothing has been added to impress.

Purpose makes that integrity possible. It becomes the boundary that shapes every decision and keeps every detail aligned. It’s the discipline that turns restraint into clarity and clarity into beauty.

When you build with that kind of alignment, your work carries a quiet confidence. It doesn’t need embellishment. It doesn’t need to prove itself. It simply expresses what it is and why it exists. And that is its beauty.

Scroll to Top