About
I Didn’t Start With a Framework
I started by trying to make sense of what I was seeing inside technology organizations.
Over more than 35 years in technology, I’ve worked across engineering, architecture, leadership, and organizational roles.
What I kept encountering were the same patterns: teams working hard but not moving together, decisions slowing down at the wrong moments, and organizations relying on individuals more than the system around them.
This work came from trying to understand why.
What Looked Like Leadership Problems Were Usually System Problems
For a long time, I approached these challenges the same way most people do - through better communication, clearer expectations, stronger leadership behaviors.
Those helped, but they didn’t fully explain what was happening.
The turning point was recognizing that the issues weren’t isolated to individuals.
They were emerging from how the organization itself was structured:
how decisions were made
how authority was distributed
how teams coordinated under pressure
That realization changed how I approached everything.
This Work Is Built From Lived Experience, Not Theory
The patterns behind this work weren’t developed in isolation or borrowed from generic leadership models.
They emerged over time from working inside different technology organizations, in different roles, under different pressures - and seeing the same dynamics repeat.
Eventually, those patterns became structured enough to describe, test, and use consistently.
That structure is what now underpins my work with clients.
WHAT I ACTUALLY DO
Work with technical leaders in real situations
Work with technical leaders in real situations
Work with technical leaders in real situations
Not hypothetical scenarios. Real decisions, real tradeoffs, real constraints.
Help make system behavior visible
Work with technical leaders in real situations
Work with technical leaders in real situations
How decisions move, where things stall, and what the organization is actually optimizing for.
Strengthen leadership within that system
Work with technical leaders in real situations
Strengthen leadership within that system
So decisions, alignment, and execution hold up under pressure.
Why This Work Is Different
I don’t approach this as traditional executive coaching.
I don’t bring a generic leadership model and try to apply it to a technical organization.
And I don’t step in to act as an external decision-maker.
This work sits in a different place.
It combines:
deep technical experience
organizational systems thinking
and a structured approach to leadership development
So that leadership evolves alongside the system it operates within.
Why This Matters to Me
I’ve seen what happens when strong technologists are placed into leadership roles without the system around them evolving at the same pace.
The pressure increases. Expectations expand. And the support structure often lags behind.
I’ve also seen what happens when that gap is addressed clearly.
Decisions improve. Alignment becomes easier. And leadership becomes more sustainable - not just for the individual, but for the organization.
That’s the work.
Background
- 35+ years in technology across engineering, architecture, and leadership
- Experience inside startups, scale-ups, and established organizations
- Focused on technical leadership, organizational systems, and decision-making under complexity
For a deeper look at my experience and perspective:
SELECTED PERSPECTIVES
Jeff creates space for people to discover solutions they didn’t know they had. He has a rare ability to ask the question everyone needed to hear, while making every person feel seen and valued.
- Marissa B.
Jeff listens thoughtfully, synthesizes diverse perspectives, and brings clarity that is both grounding and reassuring. His steady presence cultivates trust and collaboration.
- Krista C.
Jeff blends strategic foresight with genuine care. He knows when to offer guidance and when to step back, creating an environment where people feel supported without being directed.
- Anne S.
If This Perspective Resonates, The Next Step Is Simple
A short conversation is usually enough to determine whether this way of looking at your organization is useful.