Page 167 · Module 07, Operate with Precision · this screen continues that page
All 108 frameworksThe prompt
Copy & paste readyLabelsReplace these
Who should run this prompt
Module role profileWho should audit and improve your operations? Operations problems hide in plain sight — in the handoffs nobody notices, the processes nobody has documented, and the decisions nobody has questioned. The roles on this page bring the discipline of people who have built systems that run without heroics. Use them to find what is broken before it breaks you, and to build what scales before you need it to.
The roles below are who the book suggests running this prompt — this lesson’s prompt doesn’t open with a single swappable role clause, so pick one and adapt the prompt’s own wording yourself.
◆◆◆◆◆ → ◆ seniority, board level down to specialist◈ outside the organisation
How to make any role sharper
- Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
- Add what they care most about: "You care most about [X]" shapes every word of the output.
- Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
Use this when
The problem it solvesYour team has a long list of ideas, experiments, and features. Everyone has an opinion about what to do next. You're choosing based on loudest voice or gut feel and the results are inconsistent.
How the framework works
From the printed pageICE Scoring was popularised by Sean Ellis, the growth hacker who coined the term 'growth hacking.' It scores every idea across three dimensions: Impact (how much will this move the key metric if it works?), Confidence (how sure are we that it will work, based on evidence?), Ease (how quickly and cheaply can we execute it?). Each is scored 1–10. The ICE Score = Impact × Confidence × Ease. The highest-scoring ideas rise to the top. It is deliberately simple - a tool for fast, defensible prioritisation, not academic analysis.
The method, in four moves
Do these in orderScore ideas as a team, not individually averaging scores removes individual bias.
Revisit Confidence scores after each experiment update them with real data.
Use ICE for prioritising experiments and quick decisions use RICE (7.5) for larger product decisions.
Cap your active list at the top 5 ICE scores - focus beats volume every time. A high ICE score is not a mandate it is a starting point. Always ask: 'If this idea scores highest but fails, what do we learn?' Ideas that teach you something even in failure are more valuable than safe wins that teach nothing. Build your experiments to generate insight, not just results. PRO TIP
Where the framework comes from
Sean Ellis — ICE Scoring framework, growth hacking methodology
Pairs well with
As printed with this frameworkModule 07 — Operate with Precision
Build systems that run without you and improve without being told.
12 frameworks, printed on pages 160–183.
When this page changes, your copy of the book does not have to.
The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.
If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.
Copying is free. An account keeps them.
Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.