Why Standards Break Down as Architecture Firms Grow

If you're a firm owner or principal, you might still remember when the firm was small and a few people did everything. Heck, you might have worn all the hats of sales, project management, client management, production (drafting, rendering), etc.

As the firm grew, you had a small team who was very efficient. They knew what you knew because you taught them. They produced, and over time your handholding goes down to practically zero. They're efficient. The team is cranking out quality set after set and the client is satisfied.

You get new clients while the existing client keeps giving you more work. The success then causes your firm to grow and you hire more staff and promote more people. Now instead of a 5-10 person firm, you now have a much larger production staff. You no longer do the work but instead focus more on management only to find that managing so many production staff is much harder than when there were fewer of them.

You also soon discover that your firm, while making more top line revenue, the profit percentages are decreasing as a result of the chaos created from growth. Below are some of the issues contributing to the decline in profit margin:

Production Pressure Slowly Erodes Standards

Most firms do create internal standards:

• BIM guides

• drawing standards

• production manuals

• employee handbooks

But under real project pressure, these standards do not get referenced because of a combination of the following:

• The team does not know where to find them

• Even if they do find them, it takes too long to answer the question they have

• Many times, the information is outdated and no longer reliable

The team member then just reverts to the fastest method:

• asking a neighbor

• asking Google

Over time the consistency of the standard erodes into tribal knowledge. While this gets people to talk to one another, it can also cause people to adopt bad habits, convey wrong information, etc. When all this information lives in a person's head, their departure (for any reason) becomes more painful and training for new replacements takes longer and has more knowledge/skill gaps.

Documentation Is Not a System

Many firms attempt to fix this problem by writing more documentation.

• Standards manuals get more detailed

• More people are assigned to write manuals

• Checklists are created

But documentation alone does not change behavior. Documentation relies on people remembering to follow it, looking for it, reading through it, and finding the right answers. During active projects, this does not happen because the system does not synergize with behavior.

This is why many firms repeatedly experience:

• late redline cycles

• coordination revisions

• recurring project delivery issues

The problem is not lack of documentation. The problem is the documentation retrieval method. It's OUTSIDE of the workflow and finding information becomes a roadblock.

When Effort Tries to Compensate

When operational friction increases, firms rarely redesign systems. Instead they just increase effort because the pressure felt from a project deadline is like a black hole. Working on anything else feels like wasting time.

So, principals review more drawings. Project managers absorb more coordination issues. Teams work longer hours. This additional labor hides operational failure, while reducing project profits.

Architecture firms are in the business of selling time, which means inefficiencies can be absorbed through additional effort for long periods without noticeable consequences until you see the numbers. Each project phase is in the red but the PMs will say "well make it back in the next phase" but that never happens.

Over time, the PMs get stretched thin, the team feels like they're working in a sweat shop, and things become a downward spiral, including the profits. This kind of culture will lead to production quality degradation, morale degradation, loss of talent, and ultimately loss of business. I've seen and been through a few of these situations and it's never good. It makes you not want to climb out of bed.

However, there is a better way.

What Healthy Operational Standards Actually Look Like

Strong documentation alone doesn't solve the problem. You need to have strong and updated documentation along with an easy retrieval method. This is where AI comes in.

AI competes directly with the two earlier methods:

• Asking someone next to you

• Asking Google

Asking AI is not faster than asking someone next to you or maybe google but it's more reliable because it pulls the answer right from the source, your strong documentation. The coworker's memory might be vague and google gives you generic responses.

This solves the problem of information retrieval but we also have the problem of project pressure on memory. We all know a typical project has hundreds of things that need to be done, which equals hundreds of things to remember. We won't be able to remember all of these things so it would be best to bake in items within the workflow.

For example: If a production member is looking to create an SD presentation slide deck, it would be helpful to them to have guiding notes in an InDesign layer they can turn on/off so it wouldn't print when issuing something for the client but will help the deck meet firm standards.

These should not be in the written standards as then it creates two places one must update.

Here are some more examples:

• predictable milestone reviews baked into the project schedule template

• links to firm training video on the Floor Plan for Design Options

• team member responsibility matrix in project deliverable checklist

These structures shape behavior automatically. Teams do not need to remember them. They simply operate within them. Operational clarity improves project flow, reduces rework, and increases leadership capacity.

The Real Shift: Designing the Firm Itself

Architecture firms carefully design buildings. But many firms themselves evolve without intentional organizational design.

Over time this produces:

• principal dependency

• inconsistent delivery systems

• hidden operational friction

Sustainable firms eventually recognize that the organization itself must be designed.

So they focus on the following:

• Decision structures.

• Delivery standards.

• Knowledge systems.

These elements form the operational architecture of the firm.

When they are intentionally designed, firms become:

• operationally clearer

• financially healthier

• less dependent on heroic effort.

Architecture Firms Need Firm Architecture Too

Architecture firms rarely fail because of design ability. They struggle because the systems that produce architecture were never intentionally designed. In the early days, effort and talent are enough to carry the firm. But as the firm grows, complexity grows with it.

More projects. More people. More coordination. More decisions.

Without operational structure, the firm slowly begins to rely on effort instead of systems. And effort does not scale. Firms that recognize this eventually make an important shift. They stop trying to work harder inside the same structure. Instead, they start designing the organization itself.

When firms begin to experience declining margins despite increasing revenue, the cause is rarely design talent or effort.
It is almost always the operational system that delivers the work.

Diagnosing those systems is the purpose of the ReFirm Operational Evaluation.
Because great buildings are not the only things that require architecture. Great firms do too.