How do I move a key result to the backlog?
Category: OKRs
Profit.co allows you to move any Key Results (KR) to the backlog.
Why this feature?
- Moving key results to the backlog is a useful practice that allows teams to prioritize work items, avoid scope creep, allocate resources effectively, and adjust to changing priorities.
- This feature helps you to save the key results in the OKR backlog which acts as a repository, and also you can directly move key results from our backlog while creating key results or contemplating for your reference in the future.
Step 1
Navigate to OKRs from the left navigation panel.
Select the key result that you want to move to the KR backlog, and click on the More option of that Key Result.
Then, click on the Move to Backlog option from the dropdown.

A Confirmation tab will appear, click on Yes.

You can also do this by clicking on the Key Result and in the View page of the selected key result, you will find the Move to Backlog option.

Step 2
You will find the backlogged Key Result in the Backlog option.

Note: To reuse the backlogged key result hover over the key results and click on Add as Key Result to reuse the Key Result.

Related Answer Post
To know more about how to create a key result from OKR Backlog, click here.
Related Questions
-
What does Milestone tracked Key Result imply?
Profit.co offers multiple ways to track Key Results, and the Milestone Tracked type is specifically designed for goals ...Read more
-
How do I view user login history in the Cockpit?
Profit.co has introduced three new widgets within the OKR Cockpit to help organizations monitor user login behavior and ...Read more
-
How do I enable and Configure Risks & Issues Management at Key Result Level in Profit.co?
In Profit.co, you can enable Risks & Issues Management at the Key Result level to proactively identify potential ...Read more
-
How to Configure Module Linkage Between BSC and OKR in Profit.co?
Profit.co now lets you control, objective by objective, whether an objective appears only in the OKR module or across ...Read more