top of page
PRESWERX logo

The Architecture Firm That Has No Plan Past This Year

Writer: Joshua Harden
Joshua Harden
Sep 5
3 min read

Ask a principal at a mid-size architecture firm what their five-year plan looks like, and the answer is often a list of projects currently in the pipeline. That is a snapshot of current workload, not a strategic plan, and the difference matters more than it seems. A firm can have a full pipeline and no strategy at all, coasting on relationships built by one or two rainmakers while nobody maps out what happens when a market shifts, a partner retires, or a repeat client stops building. Strategic planning for architects means deciding, on purpose, what kind of firm this will be in five years, rather than discovering it by default.

Confusing a Pipeline with a Plan

A healthy backlog feels like proof that the firm is doing something right, and it often is, for now. But backlog describes what has already been won, not what the firm is positioned to win next. A plan asks harder questions: which building types will still be in demand in five years, which clients are worth deepening relationships with versus chasing one-off work, and which markets the firm has quietly been avoiding out of habit rather than strategy. Without those questions on the table, a full pipeline today says nothing about the pipeline three years out.

The Principal Transition Nobody Schedules

Many firms are still led by the founder or the generation that built the reputation the firm runs on, and the transition to the next generation of leadership gets treated as a someday problem. Someday arrives faster than expected, often through a health event or a retirement announced with six months' notice, and clients notice when the handoff feels improvised. A real strategic plan puts succession on the calendar years in advance: who is being groomed for client relationships, who is learning to run project pursuits, and what the ownership structure looks like when the transition actually happens.

Service Lines and Project Types Are Not the Same Thing

Firms often describe themselves by what they've built rather than what they're capable of and want to build more of. A firm known for K-12 schools might have staff quietly capable of higher-education work, or interior renovation expertise nobody has marketed. Strategic planning forces a firm to separate its history from its intentions, and to decide which service lines get investment, staffing, and business development attention going forward, rather than letting the next project define the next five years by accident.

Culture Doesn't Scale Itself

A firm growing from twenty people to sixty faces a different problem than getting more work: keeping the culture that made clients want to hire the firm in the first place. Design review habits, mentorship structures, and decision-making norms that work informally at twenty people usually break at sixty without someone designing the replacement on purpose. Firms that treat this as a strategic question rather than only a staffing question tend to grow without the quality erosion that shows up in client complaints two or three years after a growth spurt.

Building a Plan You Will Actually Use

The plans that get followed tend to be short, specific, and revisited on a fixed schedule, quarterly at minimum, rather than a fifty-page document written once and filed away. A useful plan names three or four priorities for the year, assigns an owner to each, and sets a date to check progress against them. It also survives contact with a bad year: when a major client leaves or a project falls through, the plan should absorb the shock without requiring a total rewrite, because the underlying direction was set independent of any one project.

The Bottom Line

A firm can run entirely on the next project and still fail as a business, because a pipeline reacts to whatever comes in the door while a strategy decides what the firm is trying to become. Architecture firms that build a real planning habit, distinct from the project schedule, end up making deliberate choices instead of inheriting them from whichever client called last.

bottom of page