The Structural Diagnostic

A 2-Week Embedded Assessment for Founder-Led Teams

Let’s talk about why you are overwhelmed

You're not overwhelmed because you're bad at your business.

You're overwhelmed because your business has quietly outgrown the way it operates, and nobody has stopped to look at the structure underneath.

That distinction matters. Because the first kind of problem responds to effort. The second one doesn't.

Before we go further:
what this is actually costing you

Most founders treat organisational chaos as a discomfort problem. Something to manage, push through, fix eventually when there's more bandwidth. The mental and physical toll is real — but it's not the whole picture.

Structural dysfunction has a price tag. Here's what it typically looks like at your stage.

⏰Your time, every day, on decisions that shouldn't reach your desk.

Let’s do some simple math:

  • You spend approximately 2-3 hours daily resolving questions, unblocking decisions, and managing escalations that your team should handle independently

  • Your time is valued conservatively at €150/hour

2.5 (average) hours x 20 work days x €150 = €7500

That’s how much of your own capacity that is consumed by structural ambiguity — not the work itself, but the absence of clear structure around the work.

This does not even take into consideration the toll managing chaos has on your own emotional happiness.

Every month you don't fix it, you spend it again.

👔The senior hire made to solve a structural problem.

The most common response to organisational chaos at your stage is to hire someone “senior enough” to "figure it out." A Head of Operations, a VP of Delivery, a COO.

The hire costs €80,000–120,000 in salary plus €15,000–25,000 in recruitment fees. And then they walk into the same structural ambiguity your team is already navigating (undefined decision rights, unclear ownership, knowledge scattered across tools nobody maintains).

These people usually respond in 2 predictable ways:

  1. They default to you the same way everyone else does, and your problem is unresolved, but your payroll ballooned.

  2. They make a genuine effort to put structure in place, until they hit a wall, and that wall is you 😅.

    Every meaningful structural change eventually requires the founder to change something too. Nobody scoped that at hire. So the changes stop at the edge of the hire's authority, 12 months pass, and everyone is frustrated but nobody can say exactly why. The hire leaves. The structure stays broken.

In fact, the more talented and senior the hire, the more likely scenario 2 happens.

Cost of a failed senior hire, conservatively: €150,000–200,000 and 12 months of your attention.

🫂The people who leave because the ambiguity becomes unsustainable.

Good people tolerate chaos when they believe in the mission and trust the leadership. But there's a limit.

When roles are unclear, when progression is undefined, when they're compensating daily for structural gaps that nobody seems to be addressing, the ones with options leave.

Replacing a mid-level hire costs roughly 50–75% of their annual salary in recruitment, onboarding, and the productivity gap during ramp-up.

Two departures in a year: €50,000–100,000, before counting the institutional knowledge that walked out with them.

(Those without options? Quiet quitting.)

———

None of these numbers are invented. They're derived from what structural dysfunction at your stage predictably produces.

The chaos you're living in right now is not just exhausting, it has a monthly invoice attached to it.

The question is whether you're going to keep paying it.

You've already tried the obvious things

You added meetings. Standups, check-ins, alignment sessions. The miscommunication continued, just with a fuller calendar.

You did the offsite. Two days, good energy, real conversations. Things felt different for about three weeks.

You introduced tools. ClickUp, Notion, Slack — sometimes all three. The chaos just moved into them.

You rolled out performance reviews. Suddenly everyone had goals. But people only half-heartedly commit to them because there are too many things outside of their control.

And now, there's AI. If the chaos persists, surely you're just under-leveraging AI? (You're not. But the FOMO is real.)

Here's why none of it held: you were solving a structural problem with non-structural interventions.

Better tools don't fix undefined ownership. More meetings don't fix unclear decision rights. AI doesn't fix confused workflows. It just moves faster through the confusion.

Structural problems require structural diagnosis first. And that's not what any of those interventions produced.

What "structure" actually means — and what it doesn't.

Before going further, a necessary clarification, because "organisational structure" gets misunderstood constantly.

I am:

❌ not talking about your org chart
❌ not auditing your CRM
❌ not evaluating your project management tool
❌ not recommending software
❌ not an AI implementation consultant

Tools are downstream of structure — and adding better tools to a structurally unclear organisation moves the chaos into the new tool faster.

What I'm assessing is the layer underneath. Six specific dimensions that govern how your organisation actually operates:

Who

Decision rights and ownership

  • Who has the authority to move work forward?

  • Who owns outcomes?

  • Is that explicit or just assumed?

Failure here looks like constant escalation, duplicate work, and decision paralysis.

What

Scope and definition of work

  • Is the objective clearly defined?

  • Does your team have a shared understanding of what "done" means?

Failure here looks like endless iteration, deliverables that don't solve the original problem, and teams working on different interpretations of the same brief.

When

Cadence and time structure

  • Are planning horizons clear?

  • Do deadlines reflect real constraints or just optimism?

  • Are priorities stable across cycles?

Failure here looks like constantly shifting priorities, artificial urgency, and missed dependencies nobody saw coming.

Where

Information architecture

  • Where does knowledge live?

  • Can people find it without asking someone?

  • Where do decisions get documented?

Failure here looks like knowledge scattered across multiple places, teams recreating the same information, losing decisions, and running clarification meetings that should be unnecessary.

Why

Strategic context and alignment

Do your teams understand:

  • why their work matters

  • why priorities are set the way they are

  • why trade-offs get made?

Failure here looks like local optimisation, output without impact, and the particular kind of disengagement that comes from doing technically correct work that feels meaningless.

How

Operational interfaces

  • How do teams hand work to each other?

  • How are cross-team dependencies managed?

  • How does conflict get resolved?

Failure here looks like projects stalling between teams, rework from integration failures, and hidden dependencies that surface at the worst possible moment.

These six dimensions exist at two levels in every organisation:

  • the whole-organisation level (how the business operates across functions), and

  • the process level (how specific workflows operate end to end).

The Structural Diagnostic assesses both — starting with the organisational level to identify where failures are most severe, then going deep on the specific processes where those failures are doing the most damage.

Why most diagnostics get this wrong
— and how I work differently

The most common alternative to just pushing through is hiring an executive coach. And coaching has genuine value — for how you think, how you make decisions, how you lead.

But your coach only ever speaks to you. Which means they're working entirely inside your perception of what's happening. And your perception — I say this with respect — is almost always the least reliable source of information about what's actually broken in your organisation. Not because you're not self-aware. But because you cannot see the system you built from inside it. The blind spots are structural, not personal.

And it's not just you. Your senior team will describe the organisation as they experience it from their corner of it. The people doing the daily work will tell you something else entirely. Nobody's lying. Everyone's giving you a partial picture filtered through their own position in the system.

I don't work with anyone's version of events. I go and look at the actual events.

How?

  • I embed. I sit in your meetings, read your Slack threads, open your shared drives, and do actual work alongside your team.

  • I ask for a real task (not a simulation, a real one) because the friction of actually doing the work is data that no conversation can produce.

This is borrowed from Toyota's "Genba" philosophy — the idea that truth lives where the work happens, not in reports about where it happens. Senior Toyota leaders are expected on the factory floor precisely because the floor reveals what dashboards conceal.

Two weeks of embedded observation — without a stake in the politics, without the history, without the habits of someone who's been inside it for years — produces a quality of picture that's genuinely hard to get any other way.

Not because I'm smarter than the people in your organisation. Because I'm looking at it fresh, and I'm looking at all of it at once.

Why most diagnostics get this wrong
— and how I work differently

The most common alternative to just pushing through is hiring an executive coach. And coaching has genuine value — for how you think, how you make decisions, how you lead.

But your coach only ever speaks to you. Which means they're working entirely inside your perception of what's happening. And your perception — I say this with respect — is almost always the least reliable source of information about what's actually broken in your organisation. Not because you're not self-aware. But because you cannot see the system you built from inside it. The blind spots are structural, not personal.

And it's not just you. Your senior team will describe the organisation as they experience it from their corner of it. The people doing the daily work will tell you something else entirely. Nobody's lying. Everyone's giving you a partial picture filtered through their own position in the system.

I don't work with anyone's version of events. I go and look at the actual events.

How?

  • I embed. I sit in your meetings, read your Slack threads, open your shared drives, and do actual work alongside your team.

  • I ask for a real task (not a simulation, a real one) because the friction of actually doing the work is data that no conversation can produce.

This is borrowed from Toyota's "Genba" philosophy — the idea that truth lives where the work happens, not in reports about where it happens. Senior Toyota leaders are expected on the factory floor precisely because the floor reveals what dashboards conceal.

Two weeks of embedded observation — without a stake in the politics, without the history, without the habits of someone who's been inside it for years — produces a quality of picture that's genuinely hard to get any other way.

Not because I'm smarter than the people in your organisation. Because I'm looking at it fresh, and I'm looking at all of it at once.

What I actually do in two weeks

Before we start: the onboarding session

Before the two-week engagement begins, we spend two (max three) hours together. This is a practical briefing for me to get started. I need to understand what the business does and how it delivers, where you feel the most friction right now, who's in the organisation and what they're supposed to be doing, and what a useful task might look like for me to pick up during immersion week.

This session is what makes the two weeks efficient. I show up on day one already oriented, which means I spend the time observing and working rather than catching up.

Week 1: Immersion

I spend the first week developing an accurate picture of how your organisation actually operates.

  • I have individual conversations with 8–12 people across every level of your organisation, not just leadership. I'm specifically looking for the gap between what the top believes is happening and what the people doing the work experience. That gap is almost always where the most important findings live.

  • I do real work alongside your team. I ask for a task — the kind you'd give a new hire or a contractor — and I do it. The friction I encounter in doing it is data no interview can produce.

  • I review your actual artefacts: your folder structures, your project management tools, your meeting notes, your documentation — or the absence of it. I look at how information is structured, how these artefacts are maintained, where the duplicates are, and how easy it is to orientate myself as I seek to complete my given task.

  • I attend 2–3 of your regular meetings as an observer. How decisions are made in rooms is different from how decisions are described afterward.

  • I build a preliminary organisational map: who is in each function, what they formally own, and where the informal reality diverges from the formal structure.

By the end of Week 1, I have a scored assessment of your organisation across all six structural dimensions — WHO, WHAT, WHEN, WHERE, WHY, HOW — and a clear picture of which processes deserve deep attention in Week 2.

Week 2: Diagnosis and Synthesis

The second week goes deep on the processes where the structural failures are most costly, and produces your complete deliverable package.

  • I map out the processes of your 2–3 highest-friction workflows in Miro — end-to-end, built from what I observed rather than what people described. Process mapping zooms in on the WHO, WHAT, WHEN, WHERE, WHY, HOW of workflows and uncover where the bottlenecks are. Mapping often reveals that your team doesn't agree on how the process works, which is itself a significant finding.

  • I synthesise the 6-dimension structural assessment with evidence: a scored evaluation of each dimension with the specific observations that support the score.

  • I produce the Structural Stress Score — where your organisation sits on the five-level scale, based on what I found, not what you reported.

  • I produce the prioritised intervention roadmap: the structural changes that will have the highest impact, sequenced across three time horizons, with explicit reasoning for the sequence.

  • We close with a 90-minute debrief where I walk you through the complete findings, you challenge what I found, and we work through what you do first.

What I actually do in two weeks

Before we start: the onboarding session

Before the two-week engagement begins, we spend two (max three) hours together. This is a practical briefing for me to get started. I need to understand what the business does and how it delivers, where you feel the most friction right now, who's in the organisation and what they're supposed to be doing, and what a useful task might look like for me to pick up during immersion week.

This session is what makes the two weeks efficient. I show up on day one already oriented, which means I spend the time observing and working rather than catching up.

Week 1: Immersion

I spend the first week developing an accurate picture of how your organisation actually operates.

  • I have individual conversations with 8–12 people across every level of your organisation, not just leadership. I'm specifically looking for the gap between what the top believes is happening and what the people doing the work experience. That gap is almost always where the most important findings live.

  • I do real work alongside your team. I ask for a task — the kind you'd give a new hire or a contractor — and I do it. The friction I encounter in doing it is data no interview can produce.

  • I review your actual artefacts: your folder structures, your project management tools, your meeting notes, your documentation — or the absence of it. I look at how information is structured, how these artefacts are maintained, where the duplicates are, and how easy it is to orientate myself as I seek to complete my given task.

  • I attend 2–3 of your regular meetings as an observer. How decisions are made in rooms is different from how decisions are described afterward.

  • I build a preliminary organisational map: who is in each function, what they formally own, and where the informal reality diverges from the formal structure.

By the end of Week 1, I have a scored assessment of your organisation across all six structural dimensions — WHO, WHAT, WHEN, WHERE, WHY, HOW — and a clear picture of which processes deserve deep attention in Week 2.

Week 2: Diagnosis and Synthesis

The second week goes deep on the processes where the structural failures are most costly, and produces your complete deliverable package.

  • I map out the processes of your 2–3 highest-friction workflows in Miro — end-to-end, built from what I observed rather than what people described. Process mapping zooms in on the WHO, WHAT, WHEN, WHERE, WHY, HOW of workflows and uncover where the bottlenecks are. Mapping often reveals that your team doesn't agree on how the process works, which is itself a significant finding.

  • I synthesise the 6-dimension structural assessment with evidence: a scored evaluation of each dimension with the specific observations that support the score.

  • I produce the Structural Stress Score — where your organisation sits on the five-level scale, based on what I found, not what you reported.

  • I produce the prioritised intervention roadmap: the structural changes that will have the highest impact, sequenced across three time horizons, with explicit reasoning for the sequence.

  • We close with a 90-minute debrief where I walk you through the complete findings, you challenge what I found, and we work through what you do first.

The tangible deliverables

Deliverable 1

The 6-Dimension Structural Assessment

A scored evaluation of your organisation across WHO, WHAT, WHEN, WHERE, WHY, and HOW — with the evidence behind each score, not just the rating.

What you do with it: Bring it into a working session with your leadership team. For the first time, you'll have a shared, evidence-based picture of where the structural failures actually are. This is a documented diagnosis you can all look at together. It replaces a conversation you've been having in circles with one that can actually go somewhere.

The 6-Dimension Structural Assessment

A scored evaluation of your organisation across WHO, WHAT, WHEN, WHERE, WHY, and HOW — with the evidence behind each score, not just the rating.

What you do with it: Bring it into a working session with your leadership team. For the first time, you'll have a shared, evidence-based picture of where the structural failures actually are. This is a documented diagnosis you can all look at together. It replaces a conversation you've been having in circles with one that can actually go somewhere.

Deliverable 2

Process Maps of Your 2–3 Highest-Friction Workflows

End-to-end maps of the processes causing the most daily pain — built from direct observation and participation.

They typically look different from what anyone expected, because they show what's actually happening rather than what's supposed to happen.

What you do with them: Use them in the same leadership session. The maps reliably produce a specific reaction: "I didn't know it worked like that." That reaction is the starting point for redesign.

The maps can either be exported as PDFs or built directly in a whiteboarding software of your choice, owned by your team, and become the baseline against which you measure improvement.

Process Maps of Your 2–3 Highest-Friction Workflows

End-to-end maps of the processes causing the most daily pain — built from direct observation and participation.

They typically look different from what anyone expected, because they show what's actually happening rather than what's supposed to happen.

What you do with them: Use them in the same leadership session. The maps reliably produce a specific reaction: "I didn't know it worked like that." That reaction is the starting point for redesign.

The maps can either be exported as PDFs or built directly in a whiteboarding software of your choice, owned by your team, and become the baseline against which you measure improvement.

Deliverable 3

The Structural Stress Score

A precise assessment of where your organisation sits on the five-level scale, with the specific observations that place you there.

What you do with it: Use it to catch yourself before the wrong next move.

Every level on the scale has a predictable misdiagnosis — the plausible-sounding intervention that founders at that level reliably reach for, and that reliably fails to address the structural root cause. If you find yourself thinking 'we need a reorg' or 'we need to tighten execution,' the scale tells you what that impulse usually signals structurally, and what to do instead.

Getting the diagnosis right is worth more than any intervention. The wrong next move at each level doesn't just fail to fix things, it often accelerates the drift to the next level.

The Structural Stress Score

A precise assessment of where your organisation sits on the five-level scale, with the specific observations that place you there.

What you do with it: Use it to catch yourself before the wrong next move.

Every level on the scale has a predictable misdiagnosis — the plausible-sounding intervention that founders at that level reliably reach for, and that reliably fails to address the structural root cause. If you find yourself thinking 'we need a reorg' or 'we need to tighten execution,' the scale tells you what that impulse usually signals structurally, and what to do instead.

Getting the diagnosis right is worth more than any intervention. The wrong next move at each level doesn't just fail to fix things, it often accelerates the drift to the next level.

Deliverable 4

The Prioritised Intervention Roadmap

A sequenced plan of the structural changes that will have the highest impact, organised into three time horizons:

  • 30 days — structural quick wins that don't require significant change management, budget, or external help. These are the interventions that prove to your team that things can actually change.

  • 30–90 days — medium-complexity structural changes that require working sessions, stakeholder alignment, or process redesign.

  • Watch but don't touch yet — dimensions that are amber but will likely improve once the higher-priority items are addressed. Knowing what not to fix yet is as valuable as knowing what to fix first.

The roadmap includes explicit reasoning for the sequence, not just a list of recommendations, but an argument for why this order and not another.

What you do with it: Use it to stop guessing about where to start. Know which changes actually move the needle. Start immediately. Plan accordingly.

The Prioritised Intervention Roadmap

A sequenced plan of the structural changes that will have the highest impact, organised into three time horizons:

  • 30 days — structural quick wins that don't require significant change management, budget, or external help. These are the interventions that prove to your team that things can actually change.

  • 30–90 days — medium-complexity structural changes that require working sessions, stakeholder alignment, or process redesign.

  • Watch but don't touch yet — dimensions that are amber but will likely improve once the higher-priority items are addressed. Knowing what not to fix yet is as valuable as knowing what to fix first.

The roadmap includes explicit reasoning for the sequence, not just a list of recommendations, but an argument for why this order and not another.

What you do with it: Use it to stop guessing about where to start. Know which changes actually move the needle. Start immediately. Plan accordingly.

Deliverable 5

The 90-Minute Debrief

A session where I walk you through all four documents, you challenge my findings, and we work through the sequencing together.

What you do with it: Leave with a clear answer to whatever question brought you here, and confidence that the answer is grounded in facts and observations.

The tangible deliverables

Deliverable 1

The 6-Dimension Structural Assessment

A scored evaluation of your organisation across WHO, WHAT, WHEN, WHERE, WHY, and HOW — with the evidence behind each score, not just the rating.

What you do with it: Bring it into a working session with your leadership team. For the first time, you'll have a shared, evidence-based picture of where the structural failures actually are. This is a documented diagnosis you can all look at together. It replaces a conversation you've been having in circles with one that can actually go somewhere.

Deliverable 2

Process Maps of Your 2–3 Highest-Friction Workflows

End-to-end maps of the processes causing the most daily pain — built from direct observation and participation.

They typically look different from what anyone expected, because they show what's actually happening rather than what's supposed to happen.

What you do with them: Use them in the same leadership session. The maps reliably produce a specific reaction: "I didn't know it worked like that." That reaction is the starting point for redesign.

The maps can either be exported as PDFs or built directly in a whiteboarding software of your choice, owned by your team, and become the baseline against which you measure improvement.

Deliverable 3

The Structural Stress Score

A precise assessment of where your organisation sits on the five-level scale, with the specific observations that place you there.

What you do with it: Use it to catch yourself before the wrong next move.

Every level on the scale has a predictable misdiagnosis — the plausible-sounding intervention that founders at that level reliably reach for, and that reliably fails to address the structural root cause. If you find yourself thinking 'we need a reorg' or 'we need to tighten execution,' the scale tells you what that impulse usually signals structurally, and what to do instead.

Getting the diagnosis right is worth more than any intervention. The wrong next move at each level doesn't just fail to fix things, it often accelerates the drift to the next level.

Deliverable 4

The Prioritised Intervention Roadmap

A sequenced plan of the structural changes that will have the highest impact, organised into three time horizons:

  • 30 days — structural quick wins that don't require significant change management, budget, or external help. These are the interventions that prove to your team that things can actually change.

  • 30–90 days — medium-complexity structural changes that require working sessions, stakeholder alignment, or process redesign.

  • Watch but don't touch yet — dimensions that are amber but will likely improve once the higher-priority items are addressed. Knowing what not to fix yet is as valuable as knowing what to fix first.

The roadmap includes explicit reasoning for the sequence, not just a list of recommendations, but an argument for why this order and not another.

What you do with it: Use it to stop guessing about where to start. Know which changes actually move the needle. Start immediately. Plan accordingly.

Deliverable 5

The 90-Minute Debrief

A session where I walk you through all four documents, you challenge my findings, and we work through the sequencing together.

What you do with it: Leave with a clear answer to whatever question brought you here, and confidence that the answer is grounded in facts and observations.

What this is actually worth

The Structural Diagnostic isn't just four documents (and one meeting).

It's the beginning of a set of transformations that change how you and your team relate to work:

From losing €6,000–9,000/month to a bottleneck that has your name on it

to a team that moves work forward without you.

From burning €150,000–200,000 on a senior hire who doesn't solve the problem

to knowing exactly what needs to exist before the next hire makes sense.

From losing good people (and €50,000–100,000 with each one) because the ambiguity became unsustainable

to an organisation people stay and grow in.

From months spent fixing symptoms

to knowing exactly what's broken and what to fix first.

From a vague sense that something is wrong and no language for it

to a diagnosis you can act on and explain to your team.

The diagnostic that produces all of this is €4,500.

I'm taking 5 clients at this rate. After that, this engagement moves to €6,500.

What this is actually worth

The Structural Diagnostic isn't just four documents (and one meeting).

It's the beginning of a set of transformations that change how you and your team relate to work:

From losing €6,000–9,000/month to a bottleneck that has your name on it

to a team that moves work forward without you.

From burning €150,000–200,000 on a senior hire who doesn't solve the problem

to knowing exactly what needs to exist before the next hire makes sense.

From losing good people (and €50,000–100,000 with each one) because the ambiguity became unsustainable

to an organisation people stay and grow in.

From months spent fixing symptoms

to knowing exactly what's broken and what to fix first.

From a vague sense that something is wrong and no language for it

to a diagnosis you can act on and explain to your team.

The diagnostic that produces all of this is €4,500.

I'm taking 5 clients at this rate. After that, this engagement moves to €6,500.

✅This is for you if:

  • You're leading a team of 10–50 people

  • You're generating €1.5M–€10M in revenue

  • You've tried the people fix and the tools fix and neither held

  • Your best people are working harder than the results justify

  • You're willing to give me genuine access — to your team, your tools, your actual work

  • You're ready to act on what I find, even if it's not what you expected

🚫This is not for you if:

  • The dysfunction is coming from above your level of authority — a parent company, a board, or an investor relationship that's structurally broken. I can diagnose what's happening, but I can't fix what you don't control.

  • You want validation more than accuracy

  • You're looking for a tool audit, an AI readiness assessment, or a CRM evaluation — that's not what this is

  • You're not prepared to act on what I find

✅This is for you if:

  • You're leading a team of 10–50 people

  • You're generating €1.5M–€10M in revenue

  • You've tried the people fix and the tools fix and neither held

  • Your best people are working harder than the results justify

  • You're willing to give me genuine access — to your team, your tools, your actual work

  • You're ready to act on what I find, even if it's not what you expected

🚫This is not for you if:

  • The dysfunction is coming from above your level of authority — a parent company, a board, or an investor relationship that's structurally broken. I can diagnose what's happening, but I can't fix what you don't control.

  • You want validation more than accuracy

  • You're looking for a tool audit, an AI readiness assessment, or a CRM evaluation — that's not what this is

  • You're not prepared to act on what I find

What happens next?

If this resonates, here’s how we start:

Option 1 — Email me

  1. Email me hi[at]victoriaenglert.com

  2. Subject line: “The Structural Diagnostic”

  3. In 3-4 sentences, tell me:

    • Your team size

    • The #1 thing that’s making you feel stuck

    • When you’d ideally want to start

I'll come back to you within 48 hours with whether I think I can help and what that would look like.

Option 2 — Book a call

make an appointment directly here. No pitch, no pressure. I'll ask you a few questions about what's going on, tell you honestly whether this is the right fit, and we go from there.

What happens next?

If this resonates, here’s how we start:

Option 1 — Email me

  1. Email me hi[at]victoriaenglert.com

  2. Subject line: “The Structural Diagnostic”

  3. In 3-4 sentences, tell me:

    • Your team size

    • The #1 thing that’s making you feel stuck

    • When you’d ideally want to start

I'll come back to you within 48 hours with whether I think I can help and what that would look like.

Option 2 — Book a call

make an appointment directly here. No pitch, no pressure. I'll ask you a few questions about what's going on, tell you honestly whether this is the right fit, and we go from there.

One last thing

I'm not interested in producing reports that live in Google Drive.

I'm interested in giving you an accurate picture of what's actually broken — specific enough to act on, honest enough to be uncomfortable in places, grounded in what I actually observed rather than what sounded plausible in an interview.

The chaos you're living in has a structure to it. Once you can see that structure, you can change it. That's what this is for.

Curious about my background? Here's how I became obsessed with organizational structure.

Interested to see how I can help your team build adaptive structures that lift you out of chaos?

Book a catch-up call

One last thing

I'm not interested in producing reports that live in Google Drive.

I'm interested in giving you an accurate picture of what's actually broken — specific enough to act on, honest enough to be uncomfortable in places, grounded in what I actually observed rather than what sounded plausible in an interview.

The chaos you're living in has a structure to it. Once you can see that structure, you can change it. That's what this is for.

Curious about my background? Here's how I became obsessed with organizational structure.

Interested to see how I can help your team build adaptive structures that lift you out of chaos?

Book a catch-up call