This site is moving soon to become part of an integrated Appfire documentation and information site for our apps. This site will remain available during the transition to our new and improved site. Once this site is moved over, this banner will be updated with the new site link for easy access.
Take a look here! If you have any questions please email support@appfire.com
Creating OKRs with OKRs for Jira
Remember to hold an OKR planning meeting with all people engaged in working with the OKRs before starting the quarter. It will help you align the goals on all of the levels and make sure you’re all on the same page.
How to create a new OKR?
Click the “New OKR” button.
Define your objective
- Start by choosing the objective’s type - do you set it as a company goal, is it an objective for your team?
Then, define your objective. If you’re looking for some inspiration, take a look at our OKR examples and a guide to writing good OKRs. It may seem easy at first, but how you define your goal will impact the way you work on it later on.
The objective should be an ambitious statement that will inspire people working towards it. Aim for simplicity of language and choose meaningful words only.
Do write objectives like: “Become a European leader of fashion e-commerce”
Don’t write objectives like: “Be better in what we do so that we will become leaders of European online fashion stores this quarter”.
After defining the objective, describe it in a few sentences so that everyone in the company would know what are you doing and why.
Next, choose if that’s a top-level objective or if it contributes to some other objective that’s already been created.
If it does contribute to some other objective, you can also decide to change the weight, and by doing so, decide on its % of contribution towards the parent objective
3. Fill in the details & click “Create”
Add all additional information that would be valuable to you and the others. It will make filtering and daily work on the OKRs easier.
You can choose to copy this data from its parent objective by clicking on the “Set the same as the parent objective” button.
you can set one of the default periods or create your own, start and due date are prefilled based on the period’s dates
select the owner (start typing to search for the user you’re looking for)
you can also add collaborators (people helping the Owner with the OKR), Teams and Labels
4. (optional) Set the restrictions
If you have OKR restrictions feature enabled, you will also see the third section at the end of the form. It allows you to set the restrictions to the OKR right away when it’s being created.
Now, decide what to create next on the Created OKRs screen.
On this view you can see all OKRs you’ve created this session, making it easy to create multiple OKRs in one go. You can create KRs for the objectives you’ve just created, create sub-objectives or create other top-level objectives (they’re top level in this tree but can have any existing objective as a higher-level item).
On the right side, there is an info panel with all information you’ve filled in during the creation process. You cannot edit them here (for now), but by clicking on the link next to the OKR name, a new tab with an OKR page and editable Info section will open. The info on the Created page will be updated right after you make the changes, so you don’t have to close it.
You can also add sub-objectives and key results later, directly from the OKR Overview. Simply hover over a top-level objective and click on the 3-dot menu. “Add sub-objective” and “Add key result” are one of the options avaialble. You can also add new KRs and sub-objectives via Alignment.
Adding a key result
Define your key result & choose its type
There are 2 key result types. The first one is manual, which means that adding both progress updates (changing the current value) and status updates (choosing the current status) is your job. With automatic KRs, you need to connect Jira issues and then we update the progress for you based on their statuses. With every issue moved to Done, your progress increases, with every new issue added, it decreases a bit. The status of auto KRs still needs to be updated manually, as it’s a very subjective matter.
Start value is the value with which you start at the beginning of the period. If you start a new project, it will be most likely a 0. For instance, if you plan to reduce the number of bugs in your system from X to Y, then X will be the start value.
The desired value is the value you plan to achieve in the OKR period. If you have a binary goal (to do sth, to learn sth), then the desired value would be either 1 or 100.
2. Fill in the details & click Create
Add the details that will help you to filter the Overview and work with the OKRs.
Similarly to the objective’s form, you can choose to copy this data from its parent objective
3. (optional) Set the restrictions
If you have OKR restrictions feature enabled, you will also see the third section at the end of the form. It allows you to set the restrictions to the OKR right away when it’s being created.
by clicking on the “Set the same as the parent objective” button.
Created KR will appear under its objective on the Created OKRs page.
If you have any suggestions or feature requests, please contact us via chat or email: support@appfire.com