Ally lets you do OKRs your way. You can configure your own OKR rules by defining your OKR structure. Here's how you have to import your OKR template if you've chosen the 'Objectives are always aspirational, key results are always measurable' option in the OKR Model Configuration section in your Admin dashboard.
The OKR Import template for this configuration has a total of 16 columns which will be used to input the OKR details into Ally. Below are the columns to be filled and the expected data:
1. Row ID: Row number for each OKR, which will be used as a reference for parent ID.
2. Title: The title of your objective, key result or project.
3. Parent: The Row ID of the parent objective to be mentioned in this column. If multiple alignment is enabled for your organization, any key result that has multiple parents will have two row IDs, separated by a new line, such as below. If the OKR does not have a parent, leave this column blank.
4. Entity: The entity for the OKR needs to be mentioned here – whether it is an organization, team or individual level OKR/project.
For organization level, the name of the organization needs to be entered.
For team level, the name of the team/sub-team needs to be entered.
For an individual level OKR, enter ‘Individual’ as the entity name.
If there are multiple teams/sub-teams responsible, they can be entered separated by a new line.
5. Owner Email: The email address of the OKR owner. If multiple owners are enabled for your organization, any OKR that has multiple owners will have two email addresses, separated by a new line, such as below. Please note that the user must exist in your organization’s Ally instance.
6. Time Period: The time period for which the OKR has been defined. Please note that this field is case sensitive and needs to be present in your organization’s Ally instance.
7. Start Date: The date on which the objective, key result or project is expected to begin. Please note that the expected date format for this field is mm-dd-yyyy.
8. End Date: The date on which the objective, key result or project is expected to end. Please note that the expected date format for this field is mm-dd-yyyy.
9. Metric Name: This is a mandatory field for key results in this configuration. Will be ignored for objectives and projects.
10. Metric Type: The metric type can be either ‘Numeric’ or ‘%’ – based on the type of your metric and how it’s being tracked. This is a mandatory field if ‘Metric Name’ is mentioned.
11. Metric Start: The metric start value goes here. This is a mandatory field if ‘Metric Name’ is mentioned.
12. Metric End: The metric end value goes here. This is a mandatory field if ‘Metric Name’ is mentioned.
13. Tags: If your OKR has any tags associated with it, please mention them here, separated by a new line.
14. OKR Description: The OKR description and any other necessary details go here.
15. Delegate: If the OKR needs to be delegated to another user, the email can be entered here. Read more about delegating your objectives here.
16. Weights: If the OKR has a customizable weight assigned to it, the valid options are – 0x , 0.25x , 0.5x , 1x , 2x , 4x.
17. Objective Type: Mention the OKR type here, enter ‘Objective’ for objectives; ‘Key Result’ for key results(OKRs with metrics); ‘Project’ for projects. The default type here will be ‘Objective’.
18. Goal Type: The goal type will always be ‘Aspirational’ for the objectives and ‘Committed’ for the key results.
You can also bulk import your users and teams, take a look here on how to fill the template.
Reach out to our Support team at [email protected] for the import template or to share the completed template for import.