Every design firm has someone who just knows things.
Which tile has never once come back with a problem. Which faucet installs cleanly and which one every contractor complains about. Which vendor ships when they say they will, which one needs chasing at week three, and which one is worth the chasing anyway. What the firm roughly charges for a primary bath before anyone opens a spreadsheet.
None of that came from a book. It was earned across dozens of projects, most of it through something going wrong once. It’s the most valuable thing the firm owns.
And in most firms, it lives in one person’s head.
What that actually costs
The obvious risk is that the person leaves. That’s real, but it’s rare enough that most firms never plan for it, and it isn’t the expensive part.
The expensive part is ordinary. It’s the Tuesday when that person is on a site visit and a junior designer has to make a call without her, so they specify something reasonable instead of the thing that would have been right. It’s the new hire who takes eight months to get good when they could have taken four. It’s the same product researched from scratch for the third time in two years, because the two designers who used it before are on other jobs and nobody remembers what it was called.
None of these show up as a line item. They show up as a firm that feels busier than its revenue suggests it should be, where the founder is a bottleneck on decisions she’d rather not be making, and where growth means the quality gets thinner because it was never written down in the first place.
Firms that scale well aren’t the ones with the most talented individual designers. They’re the ones where what the firm knows is available to everyone in it.
Two different things, often confused
“Capturing firm knowledge” sounds like one project. It’s two, and they need different treatment.
Standards are what should be true on every project you run. Your real terms with each vendor and what their product actually costs you once freight and receiving are counted. The categories you break a project into and the way you name rooms. The budget you’d expect for a kitchen in your market. The phases your projects go through and what genuinely happens in each. This is your firm’s accumulated judgment, and it should be identical on job one and job forty. Set deliberately, updated when it changes, and inherited by every project and every person without anyone having to ask.
The record of a specific job is the opposite. It’s true about exactly one project and it needs to stay true for years. What was designed and which version the client actually approved. What was specified, from whom, at what price, and why that one rather than the alternative. The bids, the plans, the contracts. Nobody needs this until suddenly somebody does, whether that’s a warranty claim, a repeat client, or a renovation of the thing you built in 2023. At that point either it exists or the answer is somebody’s recollection.
Most firms are weak at both, but they’re weak differently. Standards fail by never being written down. Records fail by being written down in eleven places.
What good looks like
One version, obviously marked. More project confusion comes from version ambiguity than from missing files. A folder holding six decks with a naming convention only one person understands is worse than useless, because everyone believes they’re looking at the current one. Old versions should be kept, since you need to know what the client saw in June, but exactly one should be unambiguously current.
Findable by the project, not by the person. If locating a document requires knowing who worked on the job and how they organize their drive, the firm doesn’t have that document. Someone does. Things belong to the project.
Set once, applied everywhere. Anything that’s true across all your work, like vendor pricing, categories, budgets, and processes, should be defined in one place and flow into every project automatically. When it lives in each project separately, it drifts, and after a year of drift nobody can say what the firm’s standard actually is.
Learnable without a tour. The real test: can a competent designer who joined last week open a finished project and understand what happened, what was chosen, and why? If yes, your firm can train people by letting them read. If no, every new hire costs a senior designer a month.
The process is knowledge too
The easiest thing to overlook is the process itself.
Experienced designers carry a project sequence in their heads. What happens in schematic design, what has to be settled before construction admin, which conversation has to happen before which decision, what gets missed when you’re rushing. Junior designers don’t have it, and it’s rarely taught explicitly. They learn it by being corrected, which is a slow and slightly demoralizing way to learn anything.
Writing down how your firm actually runs a project, meaning the phases, the milestones inside each one, the tasks that genuinely happen and the ones that only look important, is some of the highest-return work a firm can do. It turns the founder’s instinct into something the whole team can follow, and it makes every project legible to everyone on it rather than only to the person running it.
It also survives contact with reality better than most firms expect. The objection is always that every project is different. Every project is different, in the last 20%. The first 80% is the same job you’ve done forty times.
Experience only compounds if you keep it
The argument for all of this isn’t tidiness. It’s that experience is the only real asset a design firm has, and it either accumulates or it evaporates.
A firm where captured knowledge improves every year, because year six builds on everything learned in years one through five. A firm where knowledge isn’t captured gets more experienced people, which isn’t the same thing, and which walks out the door with them.
The difference between the two isn’t talent. It’s whether anyone wrote it down. And the firms that do write it down, and then share what works with the rest of us, are the ones quietly raising the standard for everybody.
Four Stripes is built around that distinction. The standards your firm sets once, including vendor pricing, categories, budgets and your project process, carry into every job automatically, while each project keeps its own durable record of what was designed, what was specified, and which version was current. So what your firm learns stays with the firm.
Key takeaways
- Firm knowledge that lives in one person’s head disappears when they’re unavailable, and it never reaches the people who join later
- The expensive cost isn’t someone leaving. It’s the ordinary Tuesday when the person who knows is on a site visit
- Standards and job records are two different problems. Standards fail by never being written down; records fail by being written down in eleven places
- Old versions should be kept, but exactly one should be unambiguously marked current
- Your process is knowledge too, and writing it down is some of the highest-return work a firm can do
