Architects. Be Yoda.

Wisdom required. Bathrobe optional.
Why architects should be the guide, not the hero.

In Star Wars, Luke Skywalker is the hero. He is inexperienced, impulsive and, at the beginning of the story, a whiny little punk. He finds himself alone, in over his head, and in need of help.

Yoda, by contrast, is small, understated and dressed for comfort. She brings experience, perspective and strategy. Hollywood in the seventies was not especially brave with casting, but the point stands.

Luke is the hero.
Yoda is the guide.

That distinction matters.

In Building a StoryBrand, Donald Miller argues that businesses clarify their message and grow when they stop casting themselves as the hero and instead position the customer as the hero of the story, with the organisation acting as the guide who helps solve their problem.

Drawing on classic storytelling structure, Miller reframes the roles. The client is the hero, facing a problem that stands in their way. That problem is the villain. The organisation plays a different role. It is the guide, the experienced professional who understands the stakes and structures the path forward.

It is a simple idea, and a powerful one. It reshapes how authority is established, how value is understood and how the client relationship is framed.

In architecture we often position ourselves as Luke. Not because we are all whiny punks, but because we have been trained to tell our story that way.

We are the hero of our professional journey. We worked hard for registration. We navigate complexity. We absorb risk. That narrative matters, and we have earned it.

A project is not our autobiography.

On a project, the client is living their story. Their capital is on the line. Their reputation is attached to the outcome. Their problem is the thing that matters most.

When we lead with our philosophy, our constraints or the challenges of practice, we unintentionally centre ourselves. When we position ourselves as the hero rather than the guide, the project may still succeed, but leadership becomes harder to read. We make our effort visible, but our leadership less so.

Clients are right to focus on their own problem. They are trying to make a site viable, unlock funding, manage political pressure, protect long term value, or avoid a costly mistake. Every decision sits inside that pressure.

The shift is not about shrinking ourselves. It is about changing roles.

In our career and in building our practice we can absolutely be the hero. On a project, however, the client must hold that position. Our role is to guide.

My first reaction to this idea was concern for design rigour. If the architect is not the hero, does ambition disappear? No, it doesnt.

Acting as the guide does not weaken design ambition. It supports it. When clients trust the framework around a project, they are far more willing to back strong ideas.

Guidance means structuring decisions, making consequences visible and setting the path rather than reacting to it.

When architects occupy that role clearly, the entire dynamic shifts. The client feels steadied. The process feels deliberate. Design ambition becomes easier to support because it sits within a framework the client trusts.

Guide the project properly, and you stop looking like overhead and start looking like leverage.

Yoda was never the one fighting the battle. She ensured the hero won it.

“Do or do not. There is no try.”