
Hierarchy view
Monday.com

I based the Hierarchy structure on an extended sub-item mental model, using indentation, spacing, and lightweight rows to make up to six levels of work readable on one “mega board.” This keeps depth visible without overwhelming users, and reduces context switching between separate boards.

The GA redesign of the “Edit hierarchy” modal reduced setup friction with clearer copy and a cleaner UI, making it easier to configure levels correctly on the first try and supporting the feature’s strong retention.
Hierarchy view is a multi-level planning experience I designed at monday dev to answer the top request from CROs and Enterprise customers: “let me see all related work in one place.”
The project spanned an end-to-end process—from in-depth user interviews with a major global enterprise customer to translating complex technical requirements into an interface that lets teams plan, track, and update work across multiple linked boards.
A core focus was reducing context switching and cognitive load. The initial concept evolved into a more familiar, sub-item-like experience that effectively creates a “mega board” – a single place where users can move fluidly from micro-tasks to macro initiatives without jumping between boards.
More about the project can be read from desktop

Hierarchy view
Monday.com

I based the Hierarchy structure on an extended sub-item mental model, using indentation, spacing, and lightweight rows to make up to six levels of work readable on one “mega board.” This keeps depth visible without overwhelming users, and reduces context switching between separate boards.

The GA redesign of the “Edit hierarchy” modal reduced setup friction with clearer copy and a cleaner UI, making it easier to configure levels correctly on the first try and supporting the feature’s strong retention.
Hierarchy view is a multi-level planning experience I designed at monday dev to answer the top request from CROs and Enterprise customers: “let me see all related work in one place.”
The project spanned an end-to-end process—from in-depth user interviews with a major global enterprise customer to translating complex technical requirements into an interface that lets teams plan, track, and update work across multiple linked boards.
A core focus was reducing context switching and cognitive load. The initial concept evolved into a more familiar, sub-item-like experience that effectively creates a “mega board” – a single place where users can move fluidly from micro-tasks to macro initiatives without jumping between boards.
Managers users struggled to manage hierarchical work across multiple boards, which led to:
I designed a unified view that supports up to six levels of hierarchy, allowing users to:
The feature became a “game changer” for Enterprise accounts and a key deal enabler in sales conversations.