Mix frameworks in one tree: EOS Rocks above team OKRs
by Aisha Mahmoud · Carrowin Financial · 8 months ago
Leadership runs EOS. The product and growth teams run OKRs underneath. Today I fake the parent-child link with naming conventions. I want the parent to genuinely be a Rock and the children genuinely Key Results, in the same hierarchy, with traceable work hanging off the bottom. The framework should be a label on a node, not a wall between trees.
Category: Frameworks
3 comments
The framework-as-a-label model is exactly right. We should not have to choose EOS or OKR at the account level, that decision belongs on the node.
Plus one. We run OGSM at the top and SMART goals in ops. Today I fake it with naming conventions and it is fragile.
In progress for Q2. First cut lets a Rock parent OKR children with traceable work underneath. OGSM mixing comes right after.