nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Goals section UX

Cyril Secourgeon

We would like to use the Goals section for outcomes, and by that I mean our OKRs. The problem is that the navigation is very basic: simple tree view. Lots of levels, because we’re using one level for company objective, the next one for company KR, then the product department objective related to that company KR, then the related KR, etc. It’s easy to get lost. Also, it means that we can’t really manage product department objectives that cover several company objectives.
Views more visual like we can find in Miro or others specialised OKR tools would be much better.

Comments

Rachel Lin

Hey Cyril, thanks for sharing! Can you show us an example and why you'd find that visual tree chart easier to navigate than a list view? Does it require additional searching / filtering capabilities to be useful?

Cyril Secourgeon

Hey Rachel,

Lots of great inspiration here

I've added below a screenshot that I particularly like from this page. It gives us that overview that the tree view can't provide. As a leader, it's great to skim through and get an overall idea of all the OKRs.

I think it's good to keep in mind that OKRs can either CASCADE (which is currently covered in Atlas tree view) but best practice is to ALIGN them. ie. it's not a 1:1 link, sometimes an L2 OKR can cover multiple L1 OKR.

I'm not sure at this stage if it requires additional searching / filtering features. I feel that what you've already done in Goals is more than enough for an mvp.