Evaluate an idea and give a go/no-go recommendation
Workflow: Evaluation
1. Describe the task
Evaluating an idea against strategy and existing opportunities takes time few reviewers have for every submission, and a decision made on gut feel is hard to defend later.
Hand the first pass to Prism. Point it at the idea, or name it in the prompt, and it checks the idea against your Master Context and the opportunity elements already in your workspace, then returns a go or no-go recommendation with reasoning and next steps attached.
With the idea open on screen:
Example prompt:
Evaluate this idea against our master context and the relevant opportunity elements in our workspace. Provide a go/no-go recommendation with an assessment that is factual and constructive.
2. Give context
Required inputs
- An existing idea element, either open on screen when you prompt, so Prism's context awareness identifies it, or named explicitly if it isn't.
- Relevant opportunity elements already created in the workspace, not just described in your Master Context as prose. With six matching opportunity elements in place, Prism cross-referenced them by name and returned a confident recommendation. Against a workspace with no matching Opportunities, the same idea returned a more conditional, more cautious verdict.
- A Master Context set for the workspace, naming your strategic pillars.
3. What ITONICS AI creates
Example output:
Idea: "Our branches operate as pickup points for rival delivery platforms" Cross-referenced against six existing opportunity elements in the workspace, including "Branch Network as Third-Party Logistics Hub" and "MVNO Expansion via EPG Connect."
Recommendation: GO, phased execution.
Strengths: The financial logic holds up, a €40K retrofit per branch with a 14-month payback, phased rather than committed in full. It uses real estate and staff already in place, with no new headcount required at scale. A 2,000-branch footprint is a network advantage no pure-play courier can easily replicate.
Risks: Hosting rival platforms risks looking like the group is subsidizing its own competition, and needs clear internal positioning before launch. Managing multiple platforms adds integration costs that could compress the payback timeline. A single retrofit-cost assumption also ignores the real gap between high-traffic and low-traffic branches.
Recommended next step: pilot 50 to 100 branches across 2 to 3 high-traffic urban markets before committing to a full rollout.
Follow-up prompts:
Example prompt:
Which of the six opportunity elements weighed most heavily on this recommendation?
Example prompt:
Stress-test the payback assumption at a 24-month scenario instead of 14.
Example prompt:
Save this recommendation into the idea's rich text field.
More AI use cases
The modular platform for R&D, strategy & innovation teams
Data
Prototype
Decision