If You Have to Hide Goals, You Have Too Many

When your goals form a tree so deep that you need to hide some of its branches to understand the rest, the view may not be the real problem. On October 19, Mooncamp announced a way to hide in-between goals in its Cascade and Tree layouts. It is a sensible fix for a crowded view. It also raises a more useful question for any team: why is the tree so crowded in the first place?

What Mooncamp changed

Mooncamp's release notes describe a Parent Alignment option that hides goals between the ones you want to see. A matching goal appears beneath its nearest matching ancestor, so a selected set of goals is easier to scan without every intervening level on screen. The change affects the view, not the underlying parent-child relationships. For a large organization navigating a complex strategy map, that can be genuinely useful.

A clearer view is not a simpler strategy

There is a difference between making a large structure easier to browse and deciding whether the structure should be that large. Hiding intermediate goals helps a reader follow selected connections. It does not decide which outcomes matter, remove duplicate objectives, or give a team a clearer priority. The complexity remains; it is simply out of sight for the moment.

Some organizations really do have a wide strategy map: a portfolio spans distinct business units, or a central objective connects work that sits far apart. In those cases, selectively hiding levels can make a real structure easier to navigate. The point is not that every hierarchy should be flat. It is that a navigation feature answers “how do I see this?” not “should this many goals exist?” Treat the two questions separately, or a neater screen can make an overgrown plan feel finished.

Follow the tree back to the team

Imagine a product team opening its quarterly goals. The company objective is several layers above the team's work, and people need a filtered view to trace the connection. The filter may help them find their place. But ask what the extra layers contribute: does each one describe a real outcome or an accountable group, or is it there because another goal needed somewhere to attach?

Remove the layers that do no work

Before adding another view or filter, review the hierarchy itself. A useful alignment tree should explain how work contributes, not require a map legend.

• If two goals describe the same intended outcome, decide which one owns it.
• If no team can explain why a goal is in the chain, question whether it belongs there.
• If a layer only exists to connect two other goals, check whether those goals can be linked more directly.
• If teams cannot say which few outcomes they are prioritizing, cut or combine goals before adding another reporting view.

Make alignment easy to explain

Focused teams do not need every goal to be visible at once. They need a small enough set of meaningful objectives that each team can explain what it owns, how that work contributes, and what it is choosing not to pursue. The links between levels matter when they show a real contribution. When they multiply without clarifying a choice, they turn alignment into maintenance.

The recitation test is practical, not a demand that everyone memorize every company-level objective. Ask a team to name its own outcome, the measure that would show progress, and the reason that outcome matters now. If its members can do that without hunting through a chart, the connection is doing its job. If the explanation takes a tour of several layers, the team may need a clearer choice before it needs a cleaner view.

Choose focus before ergonomics

OKR Studio is built for teams of 5 to 500 people who want to focus on what matters without taking on enterprise complexity. That starts with the quality and number of goals a team commits to, not with making an ever-deeper hierarchy easier to navigate. A feature that hides complexity can be right for a complex organization. For a team setting its goals, the better test is whether the structure helps people make a choice they can explain.

Focus Your Next OKR Cycle

Set clear goals with OKR Studio and keep your team focused on the outcomes that matter.