Every engineering organisation sends signals. Most leaders tune into the loudest ones — the missed deadline, the production outage, the frustrated engineer. But those are symptoms, not causes.
After seven startups and two acquisitions, I’ve learned to listen for four specific signals. They tell you everything you need to know about where an org is healthy and where it’s struggling.
The Four Signals
People — Culture, psychological safety, team dynamics. This is the human system that makes or breaks everything else. I look at Westrum typology, how information flows, whether people can disagree openly. A generative culture accelerates everything; a pathological one poisons even good architecture.
Process — Delivery cadence, planning discipline, feedback loops. How does work flow from idea to customer value? How fast do you learn? I measure cycle time, deployment frequency, and how quickly feedback reaches the people who can act on it.
Architecture — Coupling, deployability, twelve-factor principles. The structural decisions that either enable or constrain everything above. Can you deploy independently? Can you scale what needs scaling? Does your architecture support the org you want to become?
Measure — DORA metrics, developer experience platforms, health scorecards. Without data, transformation is opinion. This is where you prove whether your changes are working. If you’re not measuring, you’re guessing.
Why This Framework?
I started my career measuring concrete. My PhD at Cardiff was heavily experimental — making, moulding, and testing high-strength concrete under pressure. That work taught me something I still carry: you can’t improve what you don’t measure.
The same rigour applies to engineering organisations. Gut feel gets you a target. Data tells you if you’re getting there.
Across seven startups, I’ve seen the same patterns repeat. Dysfunctional teams aren’t usually broken everywhere — they’re broken in one or two dimensions that cascade into everything else. The Four Signals framework helps me find the root cause fast, so I can focus investment on the highest-leverage improvements.
How I Can Help
I work with engineering organisations to diagnose where they are, define where they want to be, and measure the journey between. Whether that’s as a full-time CTO, fractional leader, mentor, or advisor — the approach is the same: rigour over opinion, data over gut feel.
If your engineering org is struggling and you’re not sure why, let’s talk.