Across different roles, organizations, and stages of growth, the same patterns kept appearing.
What you’ve seen on this site isn’t based on theory or borrowed frameworks.
It comes from working inside technology organizations over time: watching how decisions move, where they stall, and how leadership interacts with the system around it.
Over more than 35 years, I’ve worked across a range of roles and environments, including:
Different contexts.
Consistent patterns.
Not because people lacked capability, but because ownership, context, or authority were unclear.
Critical work depended on specific people instead of the system supporting it.
Coordination broke down across boundaries even when intent was aligned.
They had been building structurally long before they became visible.
For a long time, I approached these as isolated leadership or execution challenges.
Better communication. Clearer expectations. Stronger leadership behaviors.
Those helped, but they didn’t fully explain what was happening.
The shift came from recognizing that these patterns weren’t isolated.
They were structural.
They emerged from how decisions were made, how authority was distributed, and how coordination actually worked under pressure.
Over time, those repeated patterns became clearer.
Clear enough to describe.
Clear enough to test.
Clear enough to use.
That’s what led to the development of the operating model and the ASCENT framework that now guide this work.
The structure came after the experience - not before it.
Most situations map to dynamics that have been seen before.
Real decisions, real constraints, real organizational context.
Not just individual behavior, but how the organization enables or constrains it.
Because it worked.
Not as a theory, but as a way to make sense of situations that otherwise felt inconsistent or unpredictable.
Once the patterns were visible, decisions became clearer and leadership became more sustainable.
After enough repetition, pattern recognition stops being intuition and becomes a reliable way to see what others miss.
The next step is to look at how these patterns may be showing up in your organization.