A decade spent where strategy meets the org chart — and bends.
The framework comes from the field, not the faculty lounge.
The framework comes from the field, not the faculty lounge.
The author of Organizational Refraction has spent more than a decade working at the intersection of technology strategy and organizational execution — the exact seam where bold decisions meet the structure that's supposed to carry them out. Most recently, as a fractional CTO to mid-to-large enterprises, they were brought in precisely when leadership teams couldn't tell whether their problem was the strategy, the people, or something structural they couldn't name.
That vantage point — inside the org, accountable for outcomes, but able to see the whole transmission path — is where organizational refraction was first observed and then named. The book is the structured account of a pattern seen too many times to be coincidence: well-formed intent arriving somewhere it was never aimed, bent by the medium it traveled through.
The thinking, in public, before the book.
Since early 2026, the author has published five case analyses developing the organizational-refraction model in the open — each diagnosing a real strategy-to-execution breakdown and showing where the intent bent. Together they form the evidentiary spine the book builds on.
- January 2026 "Strategy-to-Execution Continuum in Software Development"
- February 2026 "Two teams, two ways of expressing intent, one deadline"
- February 2026 "The outsourcing decision that looked different to everyone"
- March 2026 "One strategy, multiple realities"
- April 2026 "Invite an engineer to your strategy meeting"
Where the model was tested.
The refraction framework has been pressure-tested against real organizations, including documented analyses of:
KPN
A cautionary analysis of how an outsourcing decision hollowed out strategic capability: refraction left uncorrected until the organization could no longer translate its own intent.
DBS Bank
A correction-by-design analysis of the "two-in-a-box" leadership pairing: equal-stratum leaders carrying different domain stacks, deliberately structured to keep intent intact across the gap.
AWS
A mechanism case: how one individual's domain knowledge-parity corrected a chained-transcoding loss that would otherwise have dropped a deal-breaking sustainability requirement.
[Peer endorser quote to be sourced — target: a recognized operator or strategy authority who can speak to the author's credibility. Do not publish placeholder live.]— [Name, Title, Company / Institution]
Bring the diagnostic to your leadership team.
The author works with executive teams and boards on locating and correcting refraction in their own organizations — through keynotes, leadership workshops, and board sessions.
Pre-order Organizational Refraction
(Pre-order links coming — COO to provide final URLs)
Or join the launch list and start with the free Refraction Self-Assessment.