Gallery
Feature Prioritization Toolkit
Share
Explore
Cost of Delay

icon picker
Enter Cost of Delay Data

Answer key questions about your features to surface assumptions and determine their cost of delay and duration.
❕ Among all your features, unit of time should be consistent, so choose either "week" or "month" and stick with that value.
Search
Digital kanban simulation
Stand-up check in
Guide to asyncronous work
Team aligment snapshot
Cultural assessment quiz
Easy team metrics
Project brief
Feature
Digital kanban simulation
What is the idea/problem/opportunity?
What type of benefit does it provide?
Increase revenue
How will it generate this benefit?
Cost of delay
$500
per (unit of time)
Per week
What are any assumptions that need to be tested?
Duration of effort
60 days

About the four types of value:
Increase revenue
This type of revenue is often related to attracting new customers, or more revenue from existing customers through the development of new products, services, or entering new markets.
Protect revenue
This type of value is to lengthen the life-cycle of current revenue streams, and avoiding current revenue streams from falling. Investment here does not generate new revenue, it protects the revenue we already have.
Reduce costs
This type of value looks to reduce any costs we are currently incurring.
Avoid costs
This type of value captures the costs we could incure in the future, and putting measures in place to avoid them. The easiest example of this are features that need to be completed by some date in order to avoid regulatory fines.

"Cost of delay" + "per (unit of time)"
This figure represent how much value is lost per unit of time by not having a feature in the market.
Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.