You’ve probably felt this: Opening a Revit file from five years ago is more work than starting fresh. A problem you solved on Project A gets rediscovered on Project B. Your firm’s knowledge exists only in people’s heads—not in reusable systems.
That’s not laziness. That’s architecture.
Anthropic has a concept called compounding engineering: Normal engineering makes future work harder (technical debt). Compounding engineering makes future work easier.
The difference isn’t effort—it’s whether you extract and codify what you learn.
When Anthropic ships a feature, they don’t just close the ticket. They ask: What pattern can we extract that makes the next feature easier? Every solved problem becomes infrastructure for future problems.
Construction does the opposite. Matt Goldsberry at HDR: “No firm has all project data in a single data lake. Each new project starts from the same baseline rather than building on past work.”
Your firm completes 50 projects. Those 50 projects should make project 51 dramatically easier. Instead, it’s almost as hard as project 1.
Here’s what flips the switch: Shift from project-based delivery to capability-based delivery.
After you solve a problem, extract the generalisable solution. When your team figures out a healthcare patient room layout, don’t just archive the model—codify it as a reusable template. When you crack a facade coordination strategy, extract it as a plugin that future projects can use.
Make “contribution to firm knowledge base” part of performance reviews. Currently, only project delivery is rewarded, so knowledge extraction never happens.
The compounding effect: Each project adds capability, not just complexity. Five years in, your firm has 50 solved problems accessible instantly. Project 51 becomes genuinely easier because you’re not rediscovering solutions—you’re leveraging them.