Overview
In our world, the OKR component is as important as a button, a text field, or a dropdown. They're used everyone across the platform – the only problem? There wasn't an OKR component. Various designs + dev implementations were starting to feel disconnected and reveal the true cost of ad-hoc development.
We buckled down and designed a fresh, responsive, accessible, & intuitive component we can plug into any page.
What does an OKR component really need?
Our goal was to make sure a user could answer all these questions instantly or easily when they looked at the component:
What is my overall progress against my OKR?
Can I update it on the spot?
What are my dependencies, and how does this OKR align to others?
What's the urgency here? How much time do I have left?
