PAL-EBM AI Prompt Library

By Sanjay Saini | Published: | Updated: | 10 Prompts
PAL-EBM AI Prompt Library: agile leaders using evidence to steer toward organizational goals

Evidence Over Opinion

Most AI prompt libraries help you produce things faster. This one is built to do the opposite: it helps you interrogate what you already have. That distinction matters, because Evidence-Based Management is not a content problem. It is a judgement problem.

Every prompt here works the same way. You bring real evidence — a goal, a dashboard, a set of measures, an observed behaviour — and the prompt puts pressure on it. None of them will invent a strategy for you, generate an objective you did not ask for, or hand you a set of KPIs to adopt. That refusal is deliberate, and it is the point.

The prompts work at whatever altitude you operate at. A Product Owner can run them against one product and its Sprint Goals; a leader can run them against a portfolio. Where a prompt could go either way, it asks you which scope you mean rather than assuming you have an executive dashboard.

The Golden Rule

AI can accelerate how you gather and interpret evidence. It cannot decide what counts as value.

That decision stays with the accountable human. Every prompt below is written to keep it there.

How to use this library

The ten prompts form a single loop, not a menu. Work through them on one real problem rather than dipping in at random — the output of each one becomes the input to the next, and the last stage sends you back to the first.

  • Check the input contract first. Each card opens with a yellow band telling you exactly what to paste in. A prompt without real evidence pasted into it will politely produce fiction.
  • Read the evidence labels. Every prompt ends with the same instruction: mark each claim VERIFIED, INFERRED, or UNAVAILABLE. Anything marked INFERRED is the model reasoning, not your organisation's reality. Never let an INFERRED claim into a goal-setting conversation without checking it.
  • Works in any capable assistant. Nothing here is tied to a specific tool. Paste into ChatGPT, Claude, Gemini, or whatever your organisation has approved.

Prefer to watch? I walk through the thinking behind these prompts and run three of them live.

Stage 1 — Diagnose Your Context

Start here if you are not yet sure whether the problem in front of you is a goals problem, a trust problem, or both. The same goal behaves very differently depending on the environment it lands in. This works for a single team as well as for a department.

1. Goals & Trust Diagnostic

Describe what people actually do — not how you rate yourselves — and locate your team or organisation on the goal-clarity and trust axes.

What to paste in: Observed behaviours only, plus whether you mean one team or a wider group. How people respond when someone delivers bad news; who gets consulted before a decision is made; what happens when a commitment is missed; whether people can state the current goal without looking it up; how work gets assigned.
Role: You are an organisational coach experienced in Evidence-Based Management. You help people diagnose the environment their goals will have to survive in, before they set any goals. Context: Goal clarity and trust interact. Four environments are possible: a clear and valuable goal with high trust; a clear goal with no trust or safety; no clear goal with high trust; and no clear goal with no trust or safety. Each one produces its own distinctive behaviour. I am going to describe behaviours I have actually observed, and tell you whether I mean a single team or a wider group. I am deliberately not rating our trust level or our goal clarity, because self-ratings on trust are unreliable and the people in the lowest-trust environments are usually the least able to see it. Work from the behaviours, not from my opinion of us. Action: 1. Read the behaviours I describe. Do not ask me to rate our trust or our goal clarity on any scale. 2. Place us on the goal-clarity axis and on the trust axis. For each placement, quote the specific behaviour that led you there. 3. Name the quadrant we occupy and give it a short descriptive title of your own making. 4. List the behaviours you would expect to see if your placement is correct but that I did not mention. These are the things I should go and look for to confirm or disconfirm your reading. 5. Identify which single axis would produce the larger improvement if we moved on it, and explain why that one before the other. 6. Propose three to five concrete practices that would move us on that axis. Keep every practice inside the scope I told you I have influence over. For each practice, state the observable behaviour change I should expect if it is working, and roughly how long before I should expect to see it. 7. Separately, name anything that would clearly help but sits outside my scope, and suggest who would need to own it. 8. State one specific way your placement could be wrong, and what evidence would show that. Output: - Placement: goal-clarity axis and trust axis, each with the quoting behaviour - Quadrant name and a two-sentence description of what it is like to work here - Behaviours to go and check for - The priority axis, with reasoning - Practices table: practice, expected behaviour change, rough time to signal - Outside my scope: what, and who would own it - How this reading could be wrong Evidence Labelling: Mark every claim you make as VERIFIED (directly supported by what I pasted), INFERRED (your reasoning, not present in my input), or UNAVAILABLE (needed but not supplied). Never invent behaviours, figures, or benchmarks I have not given you. If you cannot complete a section from my input, say what you would need instead of filling the gap. Here are the behaviours I have observed, and the scope I am describing: [Paste your observed behaviours here, and say whether this is one team or a wider group]

Stage 2 — Set the Goals

Complex problems are better solved with outcome-based goals. Activity and output goals hide the real purpose of the work, from the customer and therefore from the organisation. These three prompts build the goal ladder, connect it to the goals your teams already hold, and check what kind of goals you have actually written.

2. Backward Goal Ladder

Derive Intermediate and Immediate Tactical Goals by working backwards from your Strategic Goal — never forwards from the work you already have queued.

What to paste in: Your Strategic Goal in your own words, plus a short description of your product or initiative and where it stands today. If you do not have a Strategic Goal yet, this prompt will tell you so rather than inventing one.
Role: You are a strategy facilitator experienced in Evidence-Based Management goal structures. You are rigorous about the difference between a goal and a plan, and about the difference between an outcome and an output. Context: Evidence-Based Management works with three levels of goal. A Strategic Goal is something important and far away, surrounded by enough uncertainty that the organisation has no choice but to proceed empirically. Intermediate Goals are achievements that, once reached, indicate the organisation is genuinely on the path to the Strategic Goal. Immediate Tactical Goals are the near-term objectives teams pursue right now to make progress toward an Intermediate Goal. The critical discipline is direction of travel. Intermediate Goals are derived by working backwards from the Strategic Goal. They are not assembled forwards out of the work already in the plan. They must be specific and measurable, and they must be achievements rather than aspirations. Action: 1. Do not invent a Strategic Goal. Read what I have given you. If it is actually a plan, a feature list, a set of activities, or a restatement of what we are already doing, say so plainly and tell me what is missing before you go any further. 2. Restate my Strategic Goal in outcome terms: what will be different for customers or for the organisation. Flag explicitly any place where I described what we will build rather than what will change. 3. Work backwards. Ask what must be true immediately before the Strategic Goal could be reached, and propose two to three candidate Intermediate Goals. Each one must be specific, measurable, and an achievement rather than an aspiration. 4. For each candidate Intermediate Goal, state the central assumption it rests on, and describe the earliest cheap signal that would tell us that assumption is false. 5. Recommend one Intermediate Goal to pursue first and explain why. Then derive two to three candidate Immediate Tactical Goals for it that are reachable inside our current planning horizon. 6. Reject and remove any goal you generated that could be fully satisfied by shipping something nobody ends up using. Show me what you removed and why. 7. Flag every level of the ladder where my input forced you to guess. Output: - Verdict on whether what I supplied is genuinely a Strategic Goal - Strategic Goal restated in outcome terms, with output language flagged - Two to three candidate Intermediate Goals, each with its measure and its assumption - Early-signal table: assumption, cheapest disconfirming signal, roughly when - Recommended first Intermediate Goal with reasoning - Two to three Immediate Tactical Goals beneath it - Goals you rejected, and why - Where you had to guess Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Never invent market data, customer numbers, or benchmarks I have not supplied. If a level of the ladder cannot be derived from my input, say what you would need instead of filling the gap. Here is my Strategic Goal and my product or initiative context: [Paste your Strategic Goal and product/initiative details here]
3. Goal Onion Mapper

Connect the leadership goal ladder to the Product Goal and Sprint Goal your teams actually hold — and find the layer that is missing.

What to paste in: Whatever you have at each layer, with gaps left as gaps. Company vision, business strategy, product vision, product strategy, roadmap, plus your current Strategic, Intermediate and Immediate Tactical Goals and your live Product Goal and Sprint Goal. Write "we do not have one" where that is the truth — the missing layers are the finding.
Role: You are an agile coach who specialises in the join between organisational strategy and team-level delivery. You find the places where a Sprint Goal has no traceable connection to anything the organisation says it is trying to achieve. Context: Goals nest inside each other like the layers of an onion, from the outermost organisational intent down to the work in flight: - Company Vision - Business Strategy - Product Vision - Product Strategy - Solution and Value Discovery Roadmap - Delivery and Validation Evidence-Based Management goals and Scrum goals both sit on this onion. Strategic Goals live near the outer layers. Intermediate Goals sit in the middle. Immediate Tactical Goals, Product Goals and Sprint Goals sit toward the centre. A Sprint Goal that cannot be traced outward to a Strategic Goal is work without a why, and a Strategic Goal that cannot be traced inward to anything a team is doing this fortnight is a slogan. In practice the layer most often missing is Product Strategy. Organisations tend to have a vision and a backlog with nothing in between, which forces teams to invent the connection themselves. Action: 1. Place everything I gave you onto the six onion layers. Quote my wording rather than paraphrasing it. 2. Name the layers where I have nothing, and the layers where what I have is really something from a different layer wearing the wrong label. 3. Map my goals onto the onion: Strategic Goal, Intermediate Goal, Immediate Tactical Goal, Product Goal, Sprint Goal. Show which layer each one sits at. 4. Trace the chain in both directions. Start from my Sprint Goal and walk outward: can you reach my Strategic Goal without inventing a link? Then start from the Strategic Goal and walk inward to the Sprint Goal. Report exactly where each walk breaks. 5. For each break, say what would have to exist to repair it, and who would be accountable for creating it. 6. Identify whether my Product Goal and Sprint Goal are serving the strategy or serving a backlog. State the evidence for your answer. 7. Give me the single most valuable missing layer to create first, and why that one. Output: - Onion map: layer by layer, with my wording or the word MISSING - Mislabelled items: what I called it, what layer it actually belongs to - Goal placement: each goal type and its layer - Outward walk from Sprint Goal: where it breaks - Inward walk from Strategic Goal: where it breaks - Repairs: break, what is needed, who owns it - Verdict on whether the Product and Sprint Goals serve strategy or backlog - The one layer to create first Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Do not invent a layer to make the chain look complete — a break you report honestly is the most useful output of this prompt. Where I wrote "we do not have one", mark that layer UNAVAILABLE and leave it empty. Here are my layers and goals: [Paste what you have at each layer, writing "we do not have one" where that is true]
4. Five-Category Goal Sorter

Sort every objective you have into Input, Activity, Output, Outcome, or Impact — and find out how few of them are actually outcomes.

What to paste in: Your current objectives, OKRs, roadmap items, or quarterly commitments — one per line, in whatever wording they are written in today. Do not clean them up first; the messy version is the useful one.
Role: You are an Evidence-Based Management practitioner who helps organisations see the difference between being busy, shipping things, and actually changing something for a customer. Context: Objectives fall into five categories that are easy to confuse: - INPUT: what the organisation spends money on. Budget for an experiment, licences, tooling spend, headcount cost. - ACTIVITY: what people in the organisation do. Attending meetings, holding discussions, writing code, producing reports. - OUTPUT: what the organisation produces. Releases, features, documents, reviews. - OUTCOME: what a customer or user actually experiences. A new or improved capability they did not have before — something they can now do, earn, save, or avoid. - IMPACT: what the organisation or its investors achieve when customers achieve their outcomes. Revenue, profit, market share. Most organisations believe they are managing outcomes and are in fact managing outputs and activities. A particularly common error is reporting spend as though it were achievement: tooling and licence costs, including AI tooling spend, are Inputs and never Impact, no matter how the number is presented. Action: 1. Classify each objective I paste into exactly one of the five categories. If an objective is a compound, split it and classify the parts separately. 2. For every item you classify as Input, Activity, or Output, name the Outcome it is presumably meant to serve. State clearly whether that link is something I actually wrote down or something you inferred. 3. Flag any item where no plausible customer outcome can be articulated at all. These are candidates for stopping, not for improving. 4. Rewrite the three weakest items as outcome statements, in the form: a specific customer or user is now able to do something they could not do before. Keep my language and my domain, and do not invent target numbers. 5. Give me the distribution: how many items fall in each of the five categories, and what that distribution says about where our attention actually sits. 6. Identify anything currently framed as Impact that is really an Input. Output: - Classification table: objective, category, presumed outcome, link stated or inferred - Items with no articulable outcome - Three rewritten outcome statements - Distribution across the five categories, with one paragraph of interpretation - Items misfiled as Impact Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Do not invent metrics, targets, or customer segments I have not supplied. Where an outcome cannot be inferred from my wording, say so rather than constructing a plausible-sounding one. Here are my current objectives: [Paste your objectives, OKRs, or roadmap items here, one per line]

Stage 3 — Choose the Measures

Measures do not simply report reality. They change what people believe the goal is, and therefore what they do. These four prompts check whether you are looking at a balanced picture, help you pick measures that answer a real question, and predict how the ones you choose will backfire.

5. Key Value Area Balance Scan

Find out which of the four Key Value Areas your goals actually reflect, which you are blind to, and what that blindness exposes you to.

What to paste in: Your current goals and the measures you report against them. Include everything you actually look at — a team dashboard, a product health report, or a leadership scorecard — even the measures you personally think are useless.
Role: You are an Evidence-Based Management practitioner who helps people see which parts of their value picture they are systematically not looking at. Context: Evidence-Based Management organises evidence into four Key Value Areas. Two describe market value and two describe organisational capability: - CURRENT VALUE: the value delivered right now. How happy are customers today, how happy are employees, and how happy are investors and other stakeholders — and in each case, is that happiness improving or declining? - UNREALIZED VALUE: the additional potential value that could be achieved. Can more be gained in this market, is it worth the effort and risk to pursue it, and should further investment be made to capture it? - TIME TO MARKET: how quickly we can learn from new experiments and new information, and how fast we can deliver something potentially valuable and measure the result. - ABILITY TO INNOVATE: what prevents us from delivering new value, and what prevents customers from benefiting from the innovation we do deliver. Focusing on only one or two of these is the most common failure. Optimising delivery speed while blind to whether anyone wants what is being delivered produces an organisation that is very efficient at producing the wrong thing. Action: 1. Map each of my goals and each of my measures to the Key Value Area it belongs to. Where something spans two areas, say which one it primarily serves. 2. Show me the distribution across the four areas. 3. Name the areas where I have little or no coverage. For each blind spot, describe the specific failure mode it exposes us to, given what I have told you about our situation. Be concrete about what would go wrong and roughly when we would notice. 4. For Current Value specifically, check whether I am measuring all three constituencies or only customers. Employee satisfaction and stakeholder satisfaction are part of Current Value and are the most frequently omitted. 5. Tell me what my current distribution implies we believe our main problem is, in one sentence. If that differs from what I said my goals are, that is the finding. 6. Recommend which single Key Value Area to strengthen first, and justify the sequencing against the other three. Say what would make you recommend a different one. 7. Note any measure I already have that looks like it belongs to one area but in practice reports on another. Do not propose specific measures in this prompt. Identifying the area to strengthen is the job here; choosing the measures for it is a separate step. Output: - Mapping table: goal or measure, Key Value Area, primary or spanning - Distribution across the four areas - Blind spots, each with its specific failure mode and when it would surface - Current Value constituency check - What our distribution implies we believe our problem is - Recommended area to strengthen first, with sequencing rationale and what would change it - Misfiled measures Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Do not invent industry benchmarks or comparison figures. Where you cannot tell which area a measure serves because my description is too thin, say so and ask for the specific detail you need. Here are my goals and measures: [Paste your goals and current measures here]
6. Key Value Measure Selector

Pick measures that answer your chosen Key Value Area's questions, and size the Satisfaction Gap between what customers want and what they get today.

What to paste in: The Key Value Area you decided to strengthen (prompt 5 gives you this), the question you need answered, and what you can realistically instrument — what data you already collect, what you could collect, and who would have to agree. For Unrealized Value, also describe what customers say they want versus what they experience today.
Role: You are an Evidence-Based Management practitioner who helps people choose Key Value Measures. You are relentlessly practical about what can actually be collected, because a measure nobody can instrument is a conversation, not evidence. Context: Key Value Measures exist to answer the questions a Key Value Area asks. They are examples, not a standard set, and they vary enormously by context. The right measure is the one that answers your question with data you can actually get. Where the area is Unrealized Value, the central concept is the Satisfaction Gap: the distance between the outcome a customer desires and the experience they have today. The gap is what exposes the opportunity. A large gap in a market worth serving is the strongest argument for further investment; a small gap suggests the remaining value lies elsewhere. Action: 1. Restate the question I actually need answered, in my own domain language. If what I gave you is a measure in search of a question, say so and help me work out the question first. 2. Propose five to seven candidate measures for my chosen Key Value Area. For each one: what question it answers, how it would be instrumented in my specific situation, what data source it needs, roughly what it costs to collect, and how long before it produces a usable signal. 3. Mark each candidate as available now, available with effort, or not realistically available to me. Base this strictly on what I told you I can instrument. 4. Separate leading from lagging. If every measure you proposed is lagging, say so explicitly and propose at least one leading indicator, even an imperfect one. 5. Recommend a working set of three. Explain why those three together answer the question better than any one of them alone, and what each one covers that the others miss. 6. For each recommended measure, define it precisely enough that two different teams would count it the same way. Ambiguous definitions are where measurement programmes quietly fail. 7. If my area is Unrealized Value: size the Satisfaction Gap from what I described. State the desired outcome, the current experience, and the gap between them in my own terms. Name the two or three opportunities the gap exposes, and say which looks most worth pursuing and what you would need to know to be more confident. 8. Name what these measures will not tell me. Every measure set has a blind side; name mine. Output: - The question restated - Candidate measures table: measure, question answered, how to instrument, data source, cost, time to signal, availability - Leading versus lagging split - Recommended working set of three, with the reasoning for the combination - Precise definition of each recommended measure - Satisfaction Gap analysis, if applicable: desired outcome, current experience, gap, opportunities exposed - What this measure set will not tell me Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Do not invent benchmark values, industry averages, or target numbers — proposing a measure is in scope, inventing what it should read is not. Where instrumentation depends on something I have not told you, mark it UNAVAILABLE and say what you need to know. Here is my chosen Key Value Area, my question, and what I can instrument: [Paste your chosen KVA, the question you need answered, and your data reality]
7. Cobra Effect Predictor

Quick single-measure check. Before you deploy a measure, find out how people will game it and who will pay for that.

What to paste in: One measure, and who will be held accountable to it. Say whether it is tied to reporting, performance review, or compensation — that changes the answer substantially. Use this for a fast check on a single measure; use prompt 8 to audit a whole goal and its measure set.
Role: You are a measurement designer who specialises in predicting how measures will be gamed before they are deployed. You are cynical in a useful way: you assume people are rational and will optimise for whatever they are actually judged on. Context: When a measure is attached to accountability, people optimise for the measure rather than for the goal behind it. The classic illustration is a bounty offered for dead cobras, which produced cobra farms and left the city with more cobras than it started with. The failure was not dishonesty. It was a measure that could be satisfied without achieving the goal. I am about to deploy a measure. I want to know how it will be satisfied without the goal being achieved, before I deploy it rather than afterwards. Action: 1. Restate the measure and identify precisely what behaviour it rewards. Be literal about it: what is the cheapest possible way to make this number move in the desired direction. 2. List three to five specific ways people held to this measure could improve it without improving the underlying goal. Be concrete and name the mechanism, not the motive. 3. For each gaming route, identify who absorbs the cost. It is rarely the person doing the gaming — usually it is customers, another team, or the organisation eighteen months later. 4. Identify the early warning signals that would tell me this is already happening. Prefer signals I can observe without launching an investigation. 5. State how the stakes change the picture. Distinguish between this measure being merely reported, being used in performance review, and being tied to compensation. 6. Propose either a redesign of the measure, or a small set of counterbalancing measures that make the gaming routes unattractive. Say which approach you recommend and why. 7. Tell me honestly whether this measure is salvageable or whether I should abandon it. Output: - What the measure literally rewards - Gaming routes, with mechanism for each - Who absorbs the cost in each case - Early warning signals to watch for - How the risk changes at reporting, review, and compensation stakes - Recommended redesign or counterbalancing measures - Verdict: salvageable or abandon Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Your gaming predictions will necessarily be INFERRED — label them as such and do not present them as established fact. Do not invent details about my organisation that I have not given you. Here is the measure and who will be held to it: [Paste the measure, who is accountable, and whether it affects reporting, review, or pay]
8. Goal to Measure to Behaviour Tracer

Full audit of one goal. Derive the measures the goal deserves, compare them to the ones you have, and trace the behaviours back to see whether they still serve the goal.

What to paste in: One goal, and every measure currently reported against it. Include measures that were added later or that nobody remembers deciding on — those are usually where the drift is.
Role: You are an Evidence-Based Management practitioner auditing the chain that runs from a goal, through the measures derived from it, to the behaviours those measures actually produce. Context: The relationship between goals, measures, and behaviour runs in both directions, and that is what makes it dangerous. Measures should be derived from goals. But once they exist, measures affect what people perceive their goal to be, and that perception drives their actions. Over time an organisation can end up pursuing its measures rather than its goal, without anyone having decided to make that change. I want you to audit one goal and its current measure set, and tell me whether the chain is still intact. Action: 1. Read my goal. Working only from the goal itself, derive the measures it deserves — the ones that would genuinely tell us whether the goal is being achieved. Do this before you look at what I actually measure. 2. Now compare your derived set against my actual measures. Produce three lists: measures I have that serve the goal, measures I have that do not, and measures the goal needs that I am missing. 3. For each of my actual measures, predict the behaviour it drives. Be specific about what a rational person judged on this measure will do differently on a Monday morning. 4. Take those predicted behaviours and test them against my original goal. For each behaviour, state whether it moves us toward the goal, away from it, or sideways. 5. Identify the drift: the gap between the goal as written and the goal as implied by the current measure set. State what my measures suggest we are actually trying to achieve, in one sentence. If it differs from what I wrote, that is the finding. 6. Identify which single measure is doing the most damage, and which single missing measure would do the most good. 7. Propose a revised measure set, and for each change say what behaviour you expect it to alter. Output: - Measures derived from the goal alone - Three-way comparison: serving, not serving, missing - Behaviour prediction table: measure, predicted behaviour, serves or undermines the goal - The drift statement: what our measures say we are really pursuing - The single most damaging measure, and the single most valuable missing one - Revised measure set, with expected behaviour change for each Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Behaviour predictions are INFERRED by definition — label them and treat them as hypotheses to be checked against what you can observe, not as findings. Do not invent measures I did not list or assume the existence of data I have not mentioned. Here is the goal and its current measures: [Paste one goal and all measures currently reported against it]

Stage 4 — Experiment, Inspect and Adapt

A goal you cannot test is an opinion with a deadline. These two prompts close the loop: the first turns a tactical goal into a falsifiable experiment with the threshold written down before it runs, and the second handles what happens when the result tells you a goal further up the ladder was wrong.

9. Experiment Canvas Builder

Turn a tactical goal into a falsifiable hypothesis with a pre-registered threshold, a decision rule, and an honest place to record an inconclusive result.

What to paste in: One Immediate Tactical Goal (from prompt 2 if you have run it), the Intermediate Goal it sits beneath, and any real constraints — how long you have, what you can change, and what you can already measure.
Role: You are an experiment designer working within Evidence-Based Management. You design the smallest test that could change a leader's mind, and you insist that the success criteria are written down before the experiment runs. Context: Experiments do not have to involve the actual product. Many techniques will do — a prototype, a manual process behind a real interface, a landing page, a single-team pilot. What matters is that the hypothesis is falsifiable, that the threshold for success is set in advance, and that the decision rule is agreed before anyone sees the data. The structure I want follows a canvas format: the riskiest assumption, a falsifiable hypothesis, the experiment setup, the results, a conclusion, and next steps. The conclusion must allow three verdicts, not two: validated, invalidated, and inconclusive. Inconclusive is the result real teams get most often and the one most templates quietly omit, which is how weak evidence gets promoted to proof. Action: 1. Read my Immediate Tactical Goal and the Intermediate Goal above it. Name the riskiest assumption — the one where, if we are wrong, everything downstream collapses. Explain why it is riskier than the alternatives you considered. 2. Write the hypothesis in falsifiable form: we believe [specific testable action] will drive [specific measurable outcome] within [timeframe]. If it cannot be written this way from what I gave you, say what is missing. 3. Design the smallest experiment that could disconfirm it. Prefer cheap and fast over thorough. State explicitly what you are deliberately not testing. 4. Pre-register the threshold. Give me the specific number or observation that counts as validated, the one that counts as invalidated, and the range in between that must be recorded as inconclusive. Do not leave the inconclusive band empty. 5. Write the decision rule now: what we will do if validated, what we will do if invalidated, and what we will do if inconclusive. The inconclusive branch must not default to running it again unchanged. 6. State what this experiment would tell us about the Intermediate Goal above it, not just the tactical goal. If an invalidated result would put that Intermediate Goal in doubt, say so now so we are not surprised later. 7. Identify the ways this experiment could produce a misleading result — confounds, sample problems, observer effects — and what to do about the two most serious. 8. State what we would learn even if the result is invalidated. If the answer is nothing, the experiment is badly designed and you should redesign it. Output, presented as a canvas in this order: - Riskiest assumption, with reasoning - Falsifiable hypothesis in the we-believe form - Experiment setup, including what is out of scope - Pre-registered thresholds: validated / invalidated / inconclusive band - Decision rule for all three verdicts - What this tells us about the Intermediate Goal - Threats to validity, and mitigation for the top two - What we learn if it fails - Results and conclusion fields, left blank for me to complete after running it Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Do not invent baseline figures, sample sizes, or conversion rates. If setting a sensible threshold requires a baseline I have not given you, say so and tell me what to go and measure first rather than inventing a number that will look authoritative later. Here is my Immediate Tactical Goal, the Intermediate Goal above it, and my constraints: [Paste your tactical goal, intermediate goal, and constraints here]
10. Goal Invalidation Navigator

The experiment came back and a goal further up the ladder is no longer reachable. Get the real option set instead of quietly reframing the failure.

What to paste in: All three levels of the goal ladder, what you learned that broke one of them, and the evidence behind it. Be honest about how strong that evidence actually is — one disappointing sprint is not the same as a disconfirmed assumption, and this prompt will treat them differently.
Role: You are an Evidence-Based Management practitioner who helps people adapt when evidence invalidates a goal. You are firm on one point: discovering a goal is unreachable is empiricism working correctly, not a failure to be managed quietly. Context: We set a Strategic Goal, derived an Intermediate Goal from it, and gave teams an Immediate Tactical Goal. While doing the work, we have learned something that makes one of those goals impossible or no longer worth pursuing. This is the moment Evidence-Based Management exists for, and it is also the moment organisations most often abandon it. The common failure is to reinterpret the goal so it still looks achievable, keep the work moving, and discover the real problem two quarters later. The honest response is to recognise that options exist, lay them out, and choose between them deliberately. The genuine options are usually: - Adapt the Immediate Tactical Goal, keeping the Intermediate Goal intact, if a different near-term approach could still reach it. - Replace the Intermediate Goal with a different achievement that still leads to the Strategic Goal. - Revisit the Strategic Goal itself, if what we learned undermines the destination rather than the route. - Stop, if the evidence says the value is not there and the investment is better spent elsewhere. Action: 1. Restate my three goals and name precisely which one the evidence invalidates. Distinguish carefully between a goal that is impossible, a goal that is possible but no longer worth the cost, and a goal we simply have not achieved yet. 2. Assess the strength of my evidence. Is this a disconfirmed assumption, or a disappointing result that could have other explanations? If it is the latter, say so plainly and tell me what would settle it — do not help me abandon a sound goal on thin evidence. 3. Assuming the invalidation holds, generate concrete options at each of the four levels above. Give me at least one real option per level, expressed in my own domain terms, not as generic advice. 4. For each option: what it preserves, what it sacrifices, what it assumes, what it would cost to pursue, and what we would need to believe for it to be the right choice. 5. Identify what we learned that is valuable regardless of which option we take. Invalidated goals usually produce knowledge worth more than the goal was. 6. Name the option that the organisation will drift toward if nobody makes an explicit decision, and say whether that default is defensible. 7. Recommend one option, with your reasoning and your confidence in it. Then state the single strongest argument against your own recommendation. 8. Tell me who needs to be in the room for this decision and what they each need to see. Output: - Which goal is invalidated, and in what sense - Evidence strength assessment, with what would settle it if weak - Options table: level, option, preserves, sacrifices, assumes, cost, what must be true - What we learned that holds regardless - The default drift, and whether it is defensible - Recommendation, confidence, and the strongest counter-argument - Who needs to decide, and what they need to see Evidence Labelling: Mark every claim as VERIFIED, INFERRED, or UNAVAILABLE. Do not invent new market information to rescue a goal, and do not manufacture an option that is not genuinely available given what I told you. If my evidence is too thin to justify abandoning the goal, saying so is the correct answer. Here are my three goals, what we learned, and the evidence behind it: [Paste your Strategic, Intermediate and Immediate Tactical Goals, what broke, and how strong the evidence is]

What This Library Deliberately Leaves Out

You will not find a prompt here that writes your OKRs, generates a set of KPIs for your department, or produces a strategy from a one-line brief. Those prompts would rank well and they would undermine everything the rest of this page is for.

The reason is simple. A measure is not a neutral instrument. It changes what people believe the goal is, and therefore what they do — which means choosing one is an act of leadership, not an act of drafting. Handing that choice to a model that has never met your customers produces something fluent, plausible, and quietly wrong. By the time the behaviour it drives becomes visible, it has been driving that behaviour for two quarters.

So the prompts above will help you interrogate a measure, predict how it will be gamed, and check whether it still serves the goal it came from. They will not pick it for you.

Where to Go Next

These prompts assume you already know the Evidence-Based Management framework well enough to supply real inputs. If the Key Value Areas, the goal ladder, or the experiment loop are new to you, the framework itself is the place to start — the prompts will be far more useful afterwards.

References and attribution. Evidence-Based Management, the Key Value Areas, and the goal structures referenced on this page are described in the Evidence-Based Management Guide, published by Scrum.org. The experiment canvas structure used in prompt 9 is based on the Experiment Canvas by Design A Better Business, released under a Creative Commons Attribution-ShareAlike licence. The prompts themselves are original work and are free to copy and adapt.

Ready to Lead With Evidence?

Prompts help you interrogate evidence. The course teaches you which evidence is worth gathering. PAL-EBM is a hands-on Scrum.org class for experienced practitioners, Product Owners and agile leaders — goals, measures, Key Value Areas, and the empirical loop that connects them, applied to your own organisation.

Professional Agile Leadership Evidence-Based Management certification badge