Mission format
Targeted diagnosis
Clarify one precise technical decision from a bounded set of observations.
When this mission makes sense
-
01
Competing interpretations of the same incident or cost
-
02
A team stuck on which workstream to start next
-
03
A tool or metric that does not answer the expected decision
Decisions it must unlock
- What exact decision must be made?
- Which assumptions should be dropped?
- What scope should be observed first?
What is observed
- Decision framing
- Limited, documented observation
- Restitution of possible trade-offs
What is produced
- Framing note
- Assumptions and limits list
- Ranked possible decisions
What we need from you
- Description of the decision to make
- Real calendar constraints
- Access to relevant systems or documents
How it starts
-
1.
Framing conversation
-
2.
Gather inputs and access
-
3.
Targeted observation
-
4.
Written restitution of possible decisions
Who should join
- CTO
- Platform lead
- Relevant product owner
Duration : Short, bounded engagement; exact duration set during framing.
Mode : Remote by default; on-site when constraints require it.
Geographic scope : France · Europe · Middle East · Africa
Explicit limits
- Long-running transformation delivery
- Staffing or body shopping
- Guaranteed operational outcome
What documents the reasoning
- Published review methods
- Public examples of technical reasoning
Related expertise areas
Frame a targeted diagnosis
Describe the decision you need to make. First reading is done by leadership or a responsible expert.