# Innovation mechanism selector · [Bet name] · [Date] **Owner:** [PM] **Decision maker:** [Name] **Answer needed by:** [Date] ## The bet as a question [One question the roadmap can't answer yet. No solution language.] ## Placement (from the innovation portfolio, Chapter 20) - Ambition: Core / Adjacent / Transformational - Horizon: 1 / 2 / 3 - Why: [one or two sentences] ## Blocking uncertainty (pick the main one) - [ ] Feasibility: can it be built? - [ ] Desirability and adoption: will customers use it, and will their security teams approve it? - [ ] Availability: does someone already have it? - [ ] Capability: do we have the skills and people? - [ ] Business model: can we make money from it? ## Candidate mechanisms | Mechanism | Answers the question? | Cost (L/M/H) | Time to answer | Control | Customer impact | Reversible? | |---|---|---|---|---|---|---| | [e.g. hackathon] | | | | | | | | [e.g. venture client pilot] | | | | | | | | [e.g. design partners] | | | | | | | ## Build, partner or buy check 1. Internal resources relevant? [Yes / Partly / No, with evidence] 2. Resource tradable by contract? [Yes / No] 3. Bounded collaboration enough? [Yes / No] 4. Deep integration needed and feasible? [Yes / No] - Model-provider dependency: [none / describe] - Need the team, or only the technology? [team / technology / both] ## Choice **Mechanism:** [name] **Why this one:** [the cheapest mechanism that answers the question in time, and why] **Rejected and why:** [one line each] ## Landing plan - Receiving owner (PM and engineering lead): [names, signed] - Follow-on capacity reserved: [sprint, quarter slot or budget] - Gatekeepers involved from the start: [security, legal, procurement] - Decision date: [date] **Evidence that decides:** [thresholds set now] - Possible outcomes: Absorb / Continue with new question / Hand to another mechanism / Stop