From HR to architecture.
A short account of how I arrived at organizational architecture — and what it changed.
I started in HR.
Early on, I noticed something. The problems I was asked to solve — engagement, retention, performance, culture — kept returning. Not because the solutions were wrong, but because the problems themselves were not where people thought they were.
They were structural.
An engagement problem that never goes away is usually an operating-model problem. A retention problem that returns every year is usually a job-architecture problem. A performance problem that survives every intervention is usually a decision-rights problem.
The organization was doing what it was designed to do. Unfortunately, it had never been designed — it had simply grown.
That recognition changed the direction of my work.
Today I work at the intersection of organization, workforce, human systems, and transformation. I help leaders see the architecture underneath the symptoms — and then design it deliberately.
I don't manage organizations. I architect them.
Not from beliefs. From causes.