Surface latent scope risks the surface mapping missed
Reviews the intake picture for signals that could compromise delivery or client outcomes — data quality issues, political landmines, unrealistic expectations, or downstream scope expansion — and surfaces them as named risks.
In / outIntake data and client context → named risk register for this engagement (risk, signal, potential impact, recommended mitigation)
You might say…
“We're two weeks in and it turns out the client's data hasn't been cleaned since 2022 — something we would have caught in intake if we'd known what to look for.”
What it does
Single-judgement skill that audits the fit verdict for what the straight mapping under-weights: requirements the client appears to meet but probably doesn't, exclusions that look distant but a detail in the intake quietly trips, and dependencies the method assumes are present. Names the few items most likely to become out-of-scope surprises mid-delivery so they can be raised in clarification rather than discovered later. Used when the situation is unfamiliar or the clean-fit verdict feels too comfortable for the complexity described.
Trigger: Use alongside the fit check to catch risks that don't show up in the formal criteria but could derail delivery if left unnamed.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation