A back-office menu had 40+ items. Here's how to cut it to 7.
A step-by-step method for turning a sprawling, feature-by-feature sidebar into a handful of task-based workspaces with a contextual panel, worked through on a fictional clinic back-office.
On this page · 9 sections
Back-office sidebars rarely get designed. They get accumulated: every new module adds an entry, and nobody removes the old ones. After a couple of years the menu has forty-plus items, three levels of nesting, and a wall of badges that nobody reads.
This tutorial is a method for fixing that. By the end you can take any sprawling sidebar and reduce it to about seven workspaces, each with a short contextual panel. It takes a spreadsheet, a short list of roles, and about thirty minutes.
The example is Clinic OS, a fictional clinic back-office. It's a composite built from patterns I've seen across projects, not a real client or a real product, and every number in it is invented.
Step 1: Inventory every item
Before you design anything, list what exists. Export the whole menu into a flat table, including nested items and the settings pages nobody visits. For each row, write down:
- 01the item's name
- 02its badge, if it has one
- 03the one role that uses it most
Do this in a spreadsheet, not in a design tool. You want something you can sort and filter, because Step 3 depends on it.
Expect the exercise to be a little uncomfortable. Seeing every item on one screen is usually the moment a team agrees the menu has a problem.
Step 2: List the roles and their jobs
Write down three to five roles that use the app, and for each one the five to eight things they do on a typical day. Write them as verbs: check in a patient, not Patients. Reorder a drug, not Stock.
For Clinic OS that gives you front desk, nurse, pharmacist, finance and admin. A front desk person checks patients in, sends reminders and answers messages. A nurse reviews lab results and issues prescriptions.
The verbs matter. A noun names where data lives. A verb names what someone is trying to get done, and that is what navigation should answer.
Step 3: Map items to tasks
Add a column to your inventory: which daily task does this item serve? Then sort.
Three groups appear almost immediately:
- 01items that map cleanly to one task
- 02items that serve several roles
- 03items that serve no daily task at all
The last group is your setup and admin candidates: templates, rotas, integrations, things configured once and then forgotten. They don't belong in the first level of anyone's navigation.
Step 4: Cluster tasks into workspaces
Now group the tasks, not the items, by one question: what am I doing right now?
Resist grouping by the data an item touches. Appointments and Patients both touch patient records, but they belong to different jobs, so they shouldn't automatically share a home.
Aim for five to eight groups and name them in the words your users already use. Clinic OS lands on seven:
- 01Front Desk
- 02Care
- 03Pharmacy
- 04Billing
- 05Inventory
- 06Messaging
- 07Admin
If you end up with fifteen groups, you've grouped by feature again. Merge until each one answers a distinct "what am I doing?"
Step 5: Settle the items that fit two places
Some items will belong in two workspaces. Prescriptions, for example, is used by nurses in Care and by pharmacists in Pharmacy.
Pick one rule and apply it every time: an item's home is the workspace where most people use it, and every other workspace gets a link, not a copy. For Prescriptions that means Care owns it, and Pharmacy links to it.
A link is not free. It's one more thing to keep in sync, and users will occasionally look in the wrong place first. That cost is real, and it is still smaller than the cost of two copies drifting apart.
Step 6: Design the shell
The shell has two parts. At the top, a grid of the workspaces, which answers "what am I doing?" Underneath it, a contextual panel that shows only the items of the selected workspace, which answers "what can I do here?"
Keep each panel to roughly five to nine items, grouped under small headings. If a panel runs past that, one of your workspaces is probably two workspaces.
Take Messaging as an example. Before, its items were scattered across three unrelated top-level sections. After, they sit together.
Step 7: Redesign the badges
Badges are where good navigation goes to die. If everything carries a count, nothing stands out, and people learn to ignore all of them.
Use one rule: only badge what needs action, and show the count on the workspace, not on every item. A count that never goes down is noise. Remove it.
In the Clinic OS example, only two workspaces carry a badge at any moment. Those are the two where somebody is actually waiting.
Step 8: Test it before you ship it
You don't need a research project. Pick five tasks from Step 2, hand them to a colleague who didn't design the menu, and time how long each takes to find, first in the old menu and then in the new one.
Then watch for the costs you accepted:
- 01things that are now one click deeper
- 02existing users who have to relearn where things live
- 03items in the wrong workspace, which usually show up as someone hesitating between two tiles
Fix the placement, not the labels. Hesitation between two tiles almost always means the item is in the wrong place.
Recap
The whole method fits on one line: list every item, work out who uses what, think in verbs, group by what someone is doing, then build a grid and a contextual panel.
Here is the template to start from. Paste it into a spreadsheet and fill in your own menu:
1Item,Owner role,Daily task (verb),Workspace,Badge2Appointments,Front desk,Check in a patient,Front Desk,243Prescriptions,Nurse,Issue a prescription,Care,4Claims,Finance,Submit a claim,Billing,10Then count your own sidebar and run Step 1. Most teams find out in the first ten minutes how many of their items nobody uses every day.