Every record has connections.
Items, categories, prices, choices, stores, and service channels affect each other.
Work 03 · Administration
Backoffice
Menu Management
Administrators need clear structure when one menu change can affect many records, stores, and service channels.
Read the case study ↓
My roleLead product designer
Workshops, interaction rules, responsive guidance, and handoff
ProductBackoffice
Restaurant administration and menu configuration
Period2025 to 2026
Work with design, product, engineering, and quality assurance
StatusPartial release
Navigation and configuration work shipped in stages
Project value
Make dense menu work predictable without hiding its connections.
What the design needed to achieve
- ✓
Separate navigation, record scanning, and detailed editing.
- ✓
Give every table row the same selection and navigation behavior.
- ✓
Preserve one source for shared options across connected products.
Small inconsistencies spread.
Mixed row behavior and repeated controls slow work and increase editing mistakes.
Assign each area one job.
The interface separates structure, scanning, preview, and full editing.
Design decisions
Use stable interaction rules across a dense administration product.
01Separate the editing layers
Clear structure
The left tree selects an area, the grid supports scanning, and the right panel previews one record.
Intended impact
People keep their place while moving from overview to detail.
02Give each row one behavior
Predictable navigation
One click selects and previews. The arrow or See Details opens the full page.
Intended impact
Rows stay stable and can still support inline editing.
03Define bulk actions first
Controlled scale
The team prioritized named bulk actions before an unrestricted edit-anything model.
Intended impact
Large changes remain clear, reviewable, and easier to deliver.
04Use one flexible Quick Menu
Cross-channel reuse
The selected direction uses one flexible column, insertion, reorderable tabs, multi-select, and search.
Intended impact
One structure adapts across POS, kiosk, mobile, and future sizes.
05Sequence responsive work
Delivery focus
The team defined Menu Management components before updating the full shared system.
Intended impact
Engineering receives useful guidance without waiting for a complete system rewrite.
A decision after feedback
A row needed one predictable action.
Engineering read an early navigation rule two ways. I compared five interactions and wrote the rule that the team could build.
- 01 · Find the gap
One phrase, two meanings
"Double-click to navigate" could mean a second click on a selected row or a true double-click.
- 02 · Compare
Five interactions
I evaluated five options and compared patterns in four administration products. A second implicit click would conflict with interactive columns and later inline editing.
- 03 · Decide
Separate preview from detail
One click selects and previews. The arrow and See Details open the full page. The team rejected both second-click and double-click navigation.
- 04 · Align
Write the rule for reuse
I recorded the decision for product and front-end work. The same behavior applies across Menu Management tables.
Product proof
The grid makes scanning, selection, and connected data visible.
Selection, tags, prices, and related data stay visible in one scanning view.
Result
A shared foundation reached delivery in stages.
Navigation and configuration
Navigation, category, and linked-option work reached delivery in stages.
Combo Sets
Combo Sets gained a list, detail view, permissions, and multi-store actions.
Administration signals
Future measures include bulk completion, navigation errors, and time to find an item.
Delivery is documented in stages. The portfolio has no verified task-time or error-rate result for this redesign.
Work indexSee all product design work →