RELATED IDEAS
Improve support for OKRs
There are options for tracking OKRs in Aha! however each has limitations.
For example, currently, a goal can have a success metric -- which is similar to a key result. However each goal can only have a single success metric. OKRs in organizations often have multiple success metrics (key results) for each objective.
For example:
Objective: Create an Awesome Customer Experience
Key Results:
Improve Net Promoter Score from X to Y.
Increase Repurchase Rate from X to Y.
Maintain Customer Acquisition cost under Y.
One option for improving support for OKRs would be to allow multiple success metrics per goal.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +5
Agree. Our organization uses quarterly OKRs and this enhancement would be extremely beneficial. We would love key results to be a nested record within goals, similar to the relationship between features and requirements. We'd like to assign them unique timeframes or dates, be able to see progress on each individual ones, and allow the teams to tie work (specifically features) to specific key results across workspaces (not just within the workspace or branch the KR lives in).
We consider some of the suggestions here but there are big drawbacks. For example, going the custom field route and creating 4 key results fields - one for each quarter, creates a lot of overhead and loses a lot the automation Aha offers around related records, progress calculations, and reporting hierarchies.
Replacing one of the native objects with key results or getting creative with the hierarchy is not an option for us as we have a need for the rest of the objects, plus the Aha rich knowledge base and support article will substantially diminish.
To make this work in my organisation, we have had to be creative with the hierachy and terminology. At the workspace level we have named goals as Key results and at the line level we have names goals outcomes. This means that you can have multiple key results all laddering up to a single outcome, and the key results can contain a basic information about your target, baseline and current.
Another suggestion I would offer -- we were instructed by someone at Aha to add a Custom Table for Key Results and have them live on the Goal (we use Objective) object. The downside for us is that there's this pesky Success Metric field that we can't hide and is required...so now we must just tell folks to enter "N/A" for that field. Could it be removed?
Agree - my organization is really focused on OKR's and the initiative approach is not suitable for us.
Agree - our organization is really focused on OKRs and are looking at software to help track and manage. Integration in Aha would really help.
yes, multiple success criteria is a simple fix. But what make OKR important is the way one tracks outcome vs output. The outdated practice of following the release, projects etc are only 2ndary to the overview of our outcome achievement. We need to have a first rated definition and tracking of OKRs on backbone of outputs i.e. releases/projects/epics.
It would be so great, if we track OKRs by simply extending a goal to have multiple success metrics.