Scoping Red Flags
Use this table to identify whether an opportunity is blocked now or simply not yet ready.
| Signal | What It Means | Hard Stop or Timing Issue | Recommended Response |
|---|---|---|---|
| No identifiable pain ("just exploring") | No urgency and no measurable business case yet | Timing issue | Shift to discovery education; agree measurable pain baseline before scoping |
| IT team actively blocks all new vendor evaluations | Access path to pilot is closed regardless of value | Hard stop (unless sponsor intervenes) | Escalate for executive alignment; pause scoping until policy path exists |
| Budget cycle is 12+ months out | Funding window does not support near-term pilot | Timing issue | Park in nurture plan with re-entry date and stakeholder check-ins |
| Primary format is handwritten/fax with no digitization plan | Document quality may prevent viable extraction outcomes | Hard stop for current scope | Recommend prerequisite digitization workflow before pilot |
| No executive awareness of initiative | No sponsorship for cross-functional execution | Timing issue leaning hard stop | Identify sponsor candidate and secure sponsor briefing before workshop |
| Previous vendor failure created trust deficit | Higher scrutiny and objection risk | Timing issue | Use small proof points, transparent risk plan, and reference outcomes |
| Regulatory audit just passed and urgency dropped for 12 months | Priority likely displaced by other initiatives | Timing issue | Keep light-touch engagement; schedule revisit tied to next control cycle |
Usage Guidance
- Capture red flags explicitly in scoping report risk section.
- Do not hide or soften blockers.
- Convert each red flag into an owner-backed mitigation or a clear defer decision.