​
Status Framework by Card Type

Each card type in the system uses a specific set of statuses to indicate its current state in the workflow. These built-in statuses provide enhanced functionality and visual cues that improve team collaboration and communication efficiency.

​
KPI Statuses

You can set upper and lower thresholds for your KPIs to define acceptable performance ranges. This helps in identifying when a KPI is performing well or when it requires attention. For example, if you wanted to be alerted when something like “conversion rate” dips below a given percentage, you could set a lower threshold for that KPI.
StageCommitmentDescription
In BoundsWithin acceptable parametersThe KPI measurement is currently within the defined threshold range, indicating healthy performance.
Out of BoundsOutside acceptable parametersThe KPI measurement has crossed a defined threshold boundary, requiring attention and potential intervention.

​
Outcome Statuses

Outcome Status
 Outcomes support the following statuses to communicate commitment and risk:
StageCommitmentDescription
UncommittedNo official commitmentThe outcome has been identified but not yet formally committed to by the team or organization.
At RiskCommitted but endangeredProgress toward the outcome is threatened by obstacles, delays, or resource constraints.
ProgressingCommitted with active workWork toward achieving the outcome is underway with noticeable progress, but not yet complete.
On TrackCommitted and proceeding wellThe outcome is being pursued according to plan, with expected progress and no significant obstacles.

​
Opportunity Statuses

Opportunity Status
 Once opportunities have been prioritized, use statuses to communicate when and if the team will address them. Opportunities support the following status:
StageCommitmentDescription
IdentifiedNo/Unknown commitmentAware that the Opportunity exists but have made no commitment to solving it. This is how all Opportunities start.
Not nowNo commitmentRecognized as an opportunity but deliberately chosen not to address it at this time, possibly due to resource constraints or competing priorities.
LaterCommitted (Moderate Confidence)Committed (for now) to solving the Opportunity. Confidence is relatively high that it’s an opportunity worth addressing, but this is subject to change.
NextCommittedCommitted and will begin work soon to start addressing the opportunity. It may be the case that the opportunity is currently being researched or solutions being identified.
NowCommittedCommitted and work is actively underway to address it. It’s best if there is an identified solution associated with an opportunity in Now - if not, solutioning should be underway.

​
Solution Statuses

Solution Status
 Once solutions have been ideated, use statuses to communicate when and if the team will implment them. Solutions support the following status:
StageCommitmentDescription
IdeaNo/Unknown commitmentInitial concept for addressing an Opportunity. No commitment to implementation has been made.
Not nowNo commitmentSolution evaluated but intentionally deprioritized due to resource constraints, technical limitations, or strategic considerations.
LaterCommitted (Moderate Confidence)Planned for a future timeframe beyond the current planning horizon. Recognized as valuable but with lower immediate priority than Now/Next items.
NextCommittedSolution approved with implementation details being finalized. Awaiting resource allocation or developer availability.
NowCommittedSolution actively under development. Implementation work is in progress.
Note: Using “Later” for Solutions is generally discouraged. The “Later” status is more appropriate for Opportunities (problems) where you’ve committed to solving them but haven’t yet fully defined the problem space or solution approach.

​
Experiment Statuses

Experiment Status
 Once solution assumptions have been identified, use experiment (assumption test) statuses to communicate how tests are progressing. Experiments support the following statuses:
StageCommitmentDescription
DevelopingIn preparationExperiment design is being created or refined before execution. Methods and metrics are being established.
PendingReady for executionExperiment is fully designed and waiting to be run. All prerequisites are in place.
RunningIn progressExperiment is currently active and collecting data. Results are not yet available.
FailedCompleted (invalidated)Experiment has concluded and results indicate the assumption was incorrect or not supported by evidence.
PassedCompleted (validated)Experiment has concluded and results support the original assumption, providing validation.

​
Now / Next / Later Syncing

The roadmap view automatically syncs decisions made in the tree to prioritize opportunities and solutions. View the Roadmap Documentation to learn more about how statuses keep the roadmap in sync with the tree.