Follow a real example
Trace a delayed or repeated task. Check what the person knew, which priorities competed, what tools were available, and what happened at each handoff.
Our approach
Find what is making the work harder.
A missed deadline can come from competing priorities, unavailable information, a skill gap, or more work than the team can handle. We examine the work before recommending a change.
Core principles 01 02 03 04 05 06
Start with the work people actually do.
Show the limits of the evidence
We explicitly document what supports a finding, what weakens it, what alternatives remain plausible, and how confident we should be.
Define what better would mean
Choose an observable measure, such as work completed by its original promised date. Record what the available information can tell us and what still needs to be collected.
Explain why a change might help
Each recommendation names a change in the work, the reason for testing it, and a measure that would help the team judge its usefulness.
Scope protects quality
We agree on the problem, available records, conversations and deliverables before work begins. Additional observation, data collection or implementation requires a separate scope.
Competence is project-specific
Before accepting work, we check the experience and expertise it requires. Work that needs specialist input must be scoped with that input available.
How findings are challenged
A final report should survive skeptical questions.
We check whether the findings follow from the records, whether another explanation fits, and whether the proposed test could reveal a problem with our recommendation.
Does the evidence support the claim?
Findings must be traceable to evidence. Correlation, stakeholder opinion, and plausible explanations are not quietly upgraded into causal certainty.
What alternatives were considered?
We document alternative explanations and identify what would be needed to distinguish among them when the available evidence is incomplete.
Is the recommendation connected to a metric?
A recommendation is stronger when the expected mechanism and verification measure are explicit. If the proposed change works, we should know what movement to expect.
Did the work drift outside competence or scope?
We do not use a management-consulting engagement as a back door into legal, clinical, safety, cybersecurity, accounting, or other regulated advice.
Each broader-diagnostic finding records:
- The finding itself
- Evidence source
- Coverage
- Corroboration
- Limitations
- Alternative explanations
- Confidence level: high, moderate, or low
- Whether further measurement is needed
Why this matters
Two people may describe the same handoff differently. Records may omit unfinished work. A procedure may differ from what happens on a busy day. Those gaps belong in the findings because they affect which changes are worth testing.
What keeps happening at work?
Describe a recent example, its effect on the team, and what you have already tried. We can discuss whether a review would help.