The S.A.I.D. diagnostic

When a delivery problem keeps coming back in one part of the organisation, the S.A.I.D. diagnostic answers one question: which structural condition is generating it, and what should change first?

S.A.I.D. stands for Structural Analysis and Intervention Direction. It is the method behind the paper, and I run every diagnostic myself.

To feel one of the six conditions before reading about them, play Why Nothing Gets Fixed: about 90 seconds, no signup.

Who it is for

A leader who sponsors one delivery area and has watched the usual fixes come and go: reorganisation, a new framework, training, more people. The area moves for a while, then settles back.

An area means several teams working toward one outcome, under one accountable leadership group. The diagnostic looks at one area at a time, because structure is built, and fails, area by area.

It is not for a single struggling team, a problem with one person, or a market that has moved. If that is your situation, I'll say so in the first conversation.

What it examines

Six structural conditions, each a question about how the work is set up:

• Decision Authority. Is authority held where the relevant information lives?
• Priority Integrity. Do stated priorities hold when pressure rises?
• Outcome Visibility. Can the organisation tell activity from value?
• Constraint Transparency. Do real blockers reach the people who can remove them?
• Behavioural Consistency Under Pressure. Do the operating principles survive when the stakes rise?
• Structural Load. Is the system asked to carry more than it can deliver well?

The same questions go to leadership and to the teams. Where their answers differ, the gap is often the finding.

How it works

Four to six weeks

1. Scoping. We agree the area, the outcome it exists for, who takes part, and the brief they will see before answering.
2. Data collection. People across the area, leaders and team members, answer a structured questionnaire online, in English or Romanian. It takes about 30 minutes. Leaders get paired questions, so their view can be compared with the teams'. There is no cap on the number of respondents.
3. Analysis. The answers are scored condition by condition, checked for consistency, and compared between leadership and teams. I review and validate every result, and test the pattern against what I have observed, before anything is reported.
4. Findings session. I walk the sponsor and the leadership group through what I found and what to do first.

What you receive

• The structural finding: which condition, or combination, is generating the problem.
• The mechanism behind it, and the evidence from the area that shows it.
• The gap between how leadership and teams describe the same system.
• An intervention direction, and the order in which changes should happen.
• A written findings report, and a follow-up conversation two to four weeks after delivery.

What you do not receive

No dashboard, no radar chart, no maturity level, no benchmark against other companies, and no evaluation of individuals. Each condition is described in plain words, from critical to strong, with the evidence behind it, not reduced to a number. Numbers tell you a problem exists. They rarely tell you what to change.

If you run the diagnostic again later, a progress report shows how each condition has moved since the first run.

Investment

EUR 8,000 per area, fixed fee

The fee covers the whole diagnostic, with no limit on how many people take part. Designing the change itself, the Structural Delivery Blueprint, is a separate piece of work, scoped to the area.

Confidentiality

Findings belong to the sponsor and stay confidential. Respondents are not asked for their name, and results are reported for groups, never per person. Where a group is very small, such as a leadership team of one or two, we agree beforehand how its view is presented. How the data is handled is agreed in writing before collection starts.