Skip to content

Instantly share code, notes, and snippets.

@alexwitherspoon
Created October 22, 2021 01:58
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save alexwitherspoon/dedf8305b914622b3be53ecae33b6f16 to your computer and use it in GitHub Desktop.
Save alexwitherspoon/dedf8305b914622b3be53ecae33b6f16 to your computer and use it in GitHub Desktop.
## **Brief (tweet-length)**
Summarise the work in a sentence or two. What’s the background and why is this in consideration. Remember, this is a bet — what are we betting on? Is it high-risk high-reward or a sure thing?
## **What’s the problem being solved?**
Is it business (make more money) or user (achieve a goal)? What is wrong with the current state, what problem are people facing? How can we improve this? What is the ideal outcome?
### **Customer feedback?**
Any direct feedback from customers relating to this? Requests from departments or clients etc? Have we tried to solve this problem before? What happened?
## **Success criteria**
### **What’s the hypothesis?**
If we solve this problem, what will happen? Will it lead to greater engagement? Better retention? More revenue? What would success look like?
### **How can we measure success?**
Pick one key metric as a proxy for this outcome, how can we track it and what numbers indicate things have gone well?
### **Pivot/proceed/pull gates**
We don’t want to ship and hope. We don’t want to chase a sunk cost. At what points and what metric measurements should we try something different, keep going or pull the feature entirely?
Will we roll out with a subset of users? At what points do we increase user % in that pool? At what point do we do a full roll-out?
### Who Is Doing What?
- **Responsible**: People or stakeholders who do the work. They must complete the task or objective or make the decision. Several people can be jointly *Responsible*.
- **Accountable**: Person or stakeholder who is the "owner" of the work. He or she must sign off or approve when the task, objective or decision is complete. Success requires that there is only one person *Accountable*, which means that "the buck stops there."
- **Consulted**: People or stakeholders who need to give input before the work can be done and signed-off on. These people are "in the loop" and active participants.
- **Informed**: People or stakeholders who need to be kept "in the picture." They need updates on progress or decisions, but they do not need to be formally consulted, nor do they contribute directly to the task or decision.
## **Impact**
### **Confidence**
Would you bet a significant amount of your own money on the success of this? What can we learn early on to double that bet? Or halve it? Or Reduce it to zero? What % chance of success would you say there is (gut-feel is fine)?
### **Size of impact**
How big would success be for the company? What’s the financial size of the opportunity? What’s the size of the opportunity in user engagement?
### **Why now/cost of delay**
What do we unlock by moving on this now? What would happen if we waited 6 weeks? 3 months? 1 year? What’s the risk if we do nothing?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment