Scaling your Builders Org Architecture
This simple trick will make your friends love you! Not really.
In the Builders Org equation, there exist 3 components. The raw ability to write code, knowing what and what not to build, and the architectural scaffolding that either supports or detracts from that. The How, What, and Where of product engineering.
Of these, architecture is probably the hardest to mature and evolve; and it’s because it’s the component that involves the most intuition and art. You usually don’t find out if you’ve made the correct choices until way after the fact.
For comparison, where you fit in the maturity curve of engineering is probably the easiest. Can your organization write enough code well? You can probably speak to if you are lacking quantity or quality or both, right now.
The product function is a bit harder. It takes longer to figure out if you are working on the wrong thing. Luckily, there are a million articles on product/market fit. To summarize it, if you are selling like hotcakes, you’re probably fine. If you’re not, you’re probably not fine.
Architecture is the most mystical. Does it take a long time to deliver because you’re lacking resources and you need to scale your Eng Org? Is your product failing to deliver value because your Product managers don’t know what they are doing…
