Skip to content
Design Academy My progress

Stage 3 · Lesson 9 of 10

Structuring complex products

Roles, permissions, objects and workspaces in larger products.

  • Beginner
  • 35 min
  • 3 check questions
  • Exercise: 50 min

By the end of this lesson you can

  • Recognise what makes a product structurally complex.
  • Use object-based thinking to organise complex products.
  • Apply progressive disclosure and roles to keep complexity manageable.

The idea

Some products are complex by nature: project management tools, accounting software, hospital systems. They have many features, many types of user and lots of data. You cannot make them simple, but you can make them clear.

Think in objects

Object-oriented UX starts by identifying the main "things" in a system and how they relate: in a project tool, Projects contain Tasks, Tasks have Comments and an Assignee, People belong to Teams. Structuring navigation and screens around these objects makes the product predictable: every object has a list view, a detail view and consistent actions.

Progressive disclosure

Show what most people need first, and reveal advanced options when asked. Advanced settings, bulk actions and rarely used fields can sit behind an "Advanced" section or a secondary menu.

Roles and permissions

Different users need different things. A manager approves expenses; an employee submits them. Structuring by role (or hiding what a role cannot do) reduces clutter, but be careful: people often share roles or switch between them.

Consistency

In complex products, consistent patterns matter more than anywhere else. If every list sorts, filters and selects in the same way, users only learn it once.

Why it matters in real projects

Complex products are where structure has the most impact. Users spend hours a day in them, so small inefficiencies multiply. Clear objects, consistent patterns and progressive disclosure reduce training costs, errors and support requests, and they make the product easier to extend without becoming a maze.

A realistic example

A property management platform has grown feature by feature. Each team added its own menu items, so there are 23 top-level links. Landlords cannot find tenancy documents.

The designer runs an object mapping workshop: Properties, Units, Tenancies, Tenants, Payments, Maintenance requests and Documents. The new navigation is built around Properties, with everything else reachable from a property's detail page. Documents attach to the object they belong to rather than living in a separate section. Top-level links drop to six, and support tickets about finding documents fall sharply.

Step by step

  1. List the objects

    Identify the main things users work with, using research and the existing product.

  2. Map relationships

    Draw how objects connect: which contain, belong to or reference others.

  3. Define attributes and actions

    List what each object has and what people can do with it.

  4. Design consistent views

    Plan a list and detail pattern that every object uses.

  5. Apply progressive disclosure

    Decide what is essential and what can be revealed later.

  6. Consider roles

    Map which roles need which objects and actions.

Common mistakes

  • Mistake Organising by feature or team.

    Instead Organise around the objects users think about.

  • Mistake Showing every option at once.

    Instead Use progressive disclosure for advanced features.

  • Mistake Inconsistent patterns between sections.

    Instead Use the same list, detail and action patterns everywhere.

Check your understanding

Choose an answer, then check it. There is an explanation either way.

Question 1 of 3What is the first step in object-oriented UX?
Show answer

Identify the main objects users work with. Objects form the backbone of the structure.

Question 2 of 3What does progressive disclosure mean?
Show answer

Showing essential options first and revealing advanced ones when needed. It keeps screens focused without removing power.

Question 3 of 3Why is consistency especially important in complex products?
Show answer

Users learn a pattern once and reuse it everywhere. Consistency reduces learning effort.

Practice exercise

Exercise · about 50 min

Object map

Create an object map for a school's homework app used by teachers, students and parents.

Steps

  1. List at least six objects.
  2. Draw relationships between them.
  3. List attributes and actions for three objects.
  4. Note which roles can see and act on each object.

Deliverable

An object map with roles noted.

Self-assessment

Tick each item when it is true of your exercise. Be honest; this is for you.

4 items

Summary

  • Complex products cannot be simple, but they can be clear.
  • Organise around objects and their relationships.
  • Use progressive disclosure and roles to reduce clutter.
  • Consistent patterns make complexity learnable.

Further reading

Third-party sources, chosen for reliability. They open in a new tab.

Your notes

Marking complete updates your course and roadmap progress.

Back to Information architecture Roadmap

PreviousSearch and filtering patterns Next lessonValidating information architecture