The Engagement

A structured assessment that tells you exactly where the system is breaking down — and what to fix first.

The Problem I Solve

Something feels broken — but you can't tell whether it's the strategy, the structure, the process, or the people. You're making changes that don't stick, debating root cause without getting anywhere, and watching the same friction surface in new clothes every quarter.

What I Do

I run a structured diagnostic across your Vision, Alignment, Organizational Clarity, and Operational Infrastructure to identify exactly where the disconnects are — and recommend the highest-leverage interventions, ranked by impact and effort.

What You Walk Away With

A clear picture of what's actually broken, prioritized by impact — and a roadmap your team can act on.

How You'll Feel

The shift — during, and after.

After we start

Seen.

Someone outside the noise is taking the system seriously — not just chasing the loudest complaint.

After I leave

Clear-eyed.

You know what's actually broken, why, and what to fix first. The fog lifted.

How It Unfolds

An outside read on how your system actually runs.

Every diagnostic is shaped to your context — which parts of the Stack to focus on, who to interview, how deep to go — so the timing and emphasis shift accordingly. What follows is what a typical Systems Diagnostic looks like, roughly 3–6 weeks, not a fixed plan you'd be locked into.

Week 1

Scope + stakeholder map.

Calibrate which parts of the Stack to interrogate first based on your hypothesis of what's wrong — and map who needs to be interviewed (leadership, mid-level managers, sometimes ICs) to triangulate the answer.
Weeks 1–2

Listen to leaders.

1:1 conversations (30–60 minutes each) with leadership team members to surface how each person experiences the system — what's working, what's not, where they think the breakdowns are — and where they disagree with each other.
Weeks 2–4

Observe the system in motion.

Shadow existing operating moments (standups, planning meetings, decision moments) and review the artifacts that hold the system together — org chart, OKRs, dashboards, role descriptions, meeting cadences, decision frameworks. Looking for gaps, contradictions, and orphaned ownership.
Weeks 3–5

Synthesize against the Stack.

Map findings to the four layers of the Viewpoint Stack: where each layer is strong, where it's load-bearing for something it can't support, and where the cracks are. Separates symptoms from root causes.
Weeks 5–6

Readout + prioritized roadmap.

A working session with your leadership team to walk through the findings — plus a written roadmap of interventions ranked by impact and effort, with my recommendation on what to tackle first and what to leave alone.

Is This a Fit?

This works best for leaders who suspect something is wrong — and want a clearer picture before they commit to a fix.

Works the same whether the scope is the whole company or a single function — Product, Operations, Customer Success, PMO, Revenue Ops — that needs its own clear-eyed read.

Best fit for you if…

You're scaling and something stopped working — but it's not obvious what
You've made changes (reorgs, new processes, new tools) that didn't produce the change you expected
Your leadership team is debating root cause and getting nowhere
You're considering a major investment (hiring, restructuring, system replacement) and want a clearer picture before committing
You want an outside view from someone who isn't trying to sell you a particular solution

Probably not for you if…

You already know what's broken and are ready to fix it — you might need The Build instead
You're heading into strategic planning and need shared direction — The Strategic Reset is the better starting point
You want validation of an existing plan rather than a genuine outside read
You're not prepared to act on what the diagnostic surfaces — this isn't a desk drawer document

Common Questions

What leaders usually want to know before they sign on.

What's the deliverable?

A diagnostic readout session with your leadership team (typically 60–90 minutes) plus a written roadmap document. The roadmap covers what I observed, how it maps to the Viewpoint Stack, the prioritized list of interventions, and a clear recommendation on sequencing.

How disruptive is this to my team?

Light. The bulk of the work is 1:1 conversations (30–60 minutes each), some shadow time in your existing meetings (no extra meetings created), and document review I do on my own time. Most leaders describe it as "didn't really notice it was happening."

Will this turn into a Build engagement?

Sometimes. The diagnostic is designed to stand alone — the roadmap is yours to execute however you want. If the roadmap surfaces work I'm well-suited to lead, we can scope The Build separately. But there's no obligation, and I'd rather be honest about whether someone else is a better fit than push for the next engagement.

What if the issue isn't what I thought it was?

That's actually the most common outcome. Most diagnostics surface a different root cause than the leader expected coming in — which is exactly why an outside read is useful. You'll end the engagement with a sharper diagnosis than the one you walked in with.

Do you talk to people outside the leadership team?

When useful, yes. I'll often interview a small sample of mid-level managers or individual contributors to triangulate what leadership tells me — but only with your buy-in and with clear framing of what's being asked and why. Confidentiality is the default; nothing is reported back attributable unless you and I agree it should be.

The Systems Diagnostic