---
title: "Backoffice UX Case Study | Parmis Meshgi"
description: "A Backoffice Menu Management UX and product design case study by senior product designer Parmis Meshgi."
canonical_url: "https://meshgi.com/backoffice/"
html_url: "https://meshgi.com/backoffice/"
author: "Parmis Meshgi"
location: "Toronto, Canada"
language: "en-CA"
last_updated: "2026-09-29"
---

> A Backoffice Menu Management UX and product design case study by senior product designer Parmis Meshgi.

Canonical page: [https://meshgi.com/backoffice/](https://meshgi.com/backoffice/)

[← All work](https://meshgi.com/product-design/)

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 ↓](https://meshgi.com/backoffice/#value)

![Menu Management grid with sample records and selection controls](https://meshgi.com/assets/menu-grid.png)

My role Lead product designer

Workshops, interaction rules, responsive guidance, and handoff

Product Backoffice

Restaurant administration and menu configuration

Period 2025 to 2026

Work with design, product, engineering, and quality assurance

Status Partial 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.

Problem

### Every record has connections.

Items, categories, prices, choices, stores, and service channels affect each other.

Risk

### Small inconsistencies spread.

Mixed row behavior and repeated controls slow work and increase editing mistakes.

Direction

### 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.

01

### Separate 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.

02

### Give 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.

03

### Define 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.

04

### Use 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.

05

### Sequence 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.

Product proof

## The grid makes scanning, selection, and connected data visible.

![Menu Management grid with sample names, prices, tags, and selection states](https://meshgi.com/assets/menu-grid.png)

Record library

Selection, tags, prices, and related data stay visible in one scanning view.

Result

## A shared foundation reached delivery in stages.

Delivered

### Navigation and configuration

Navigation, category, and linked-option work reached delivery in stages.

Expanded

### Combo Sets

Combo Sets gained a list, detail view, permissions, and multi-store actions.

Measure next

### Administration signals

Future measures include bulk completion, navigation errors, and time to find an item.

[Work index See all product design work →](https://meshgi.com/product-design/)

[Next work project POS →](https://meshgi.com/pos/)