Redesign a Slow Proposal Workflow
Generate materially different operating concepts before screening them with constraints and evidence.
20 minutes
Scenario
A consultancy needs ten days to prepare a proposal. Leaders jump to an AI writer, but rework data points to vague scope, repeated standard text, late price checks and unclear approval ranges.
- Your role
- Service designer facilitating a SCAMPER session
- Method
- SCAMPER
Evidence pack
Rework
Sixty-two percent of delayed proposals require scope clarification.
Content
About half the proposal uses approved service modules with small changes.
Pricing
Finance rejects 12% because the approved price range was not checked before drafting.
Approval
Partners review every proposal, including standard work within an approved range.
Confidentiality
Client notes may be processed only in the approved workspace.
Outcome
The customer needs an accurate scope, price and mobilisation plan—not more narrative.
Constraints
- Price commitments require an approved source and authority.
- Client notes stay in the approved workspace.
- Generation and screening must be separate phases.
Case steps
Work through each prompt using the evidence pack. These guided cases support self-directed practice; server-scored attempts are not available yet.
Write one user-outcome challenge and decompose the current workflow into transformable elements.
Generate at least seven ideas using four or more SCAMPER lenses without scoring them.
Combine ideas into three distinct concepts with mechanism and critical assumption.
Screen the concepts and select one bounded evidence test with a stop rule.