The Brief

Business operations, finally in one place.

Most businesses run on fragmented systems, inventory in one tool, staff in another, payments somewhere else. Nothing talks to each other. Nexus was built to replace that chaos with one unified management system, role-based, clear, and built for real operational speed.

01

Fragmented systems

Daily operations spread across multiple tools that don't communicate with each other.
02

Limited visibility

Staff see too much or too little, this affecting efficiency and accountability by role.
03

Operational overload

Managing inventory, staff, payments, and reports simultaneously slows decision making.

Unify operations

One system for all business functions

Role based clarity

Each user sees exactly what they need

Reduce cognitive load

Less noise, faster decisions, clearer flow

Unify operations

One system for all business functions

Role based clarity

Each user sees exactly what they need

Reduce cognitive load

Less noise, faster decisions, clearer flow

User Testing

Three roles. One system.

Each role has a different level of access and a different set of needs. The design had to serve all three without creating confusion between them.

Admin

Restaurant Owner

Full access across all modules. Manages users, permissions, business settings, and reports.

  • Full system control
  • User management
  • All reports & analytics

Manager

Operations Lead

Oversees daily operations: inventory, staff scheduling, and performance tracking.

  • Inventory management
  • Staff scheduling
  • Performance reports

Staff

Team Member

Task focused view. Sees only what’s relevant to their daily work, no noise, no distraction.

  • Personal task view
  • Shift & schedule
  • Limited reporting

Admin

Restaurant Owner

Full access across all modules. Manages users, permissions, business settings, and reports.

  • Full system control
  • User management
  • All reports & analytics

Manager

Operations Lead

Oversees daily operations: inventory, staff scheduling, and performance tracking.

  • Inventory management
  • Staff scheduling
  • Performance reports

Staff

Team Member

Task focused view. Sees only what’s relevant to their daily work, no noise, no distraction.

  • Personal task view
  • Shift & schedule
  • Limited reporting

Process

To approach the complexity of the system, we followed a structured design process that helped us define roles, workflows, and system logic before moving into visual design.

Key Flow

From login to full control.

The primary system flowת how each role enters, navigates, and operates within Nexus.

01
Login & Access
02
Role Dashboard
03
Core Actions
04
Reports & Data
05
Settings & Control
01

Login & Access

02

Role Dashboard

03

Core Actions

04

Reports & Data

05

Settings & Control

The Solution

One system. Three perspectives.

Nexus was designed around a single principle: every role should feel like the system was built specifically for them.

Admin sees everything. Managers see what drives operations. Staff see only what moves their day forward.

Same system, three completely different experiences, all consistent, all connected.

Logo

Color palette

#E4C065

#305F6E

#543C2F

#A5844D

#FFFFFF

#262626

Typography

Primary: URBANIST

Urbanist font is an excellent choice for our restaurant management system because its round corners perfectly complement the welcoming and friendly spirit of our project.

Decisions that shaped the system.

01

Tablet first

The entire system was designed for tablet use, since staff and managers operate on the floor, not at a desk.
02

First screen = most important action

Every role's home screen shows only what they need to act on immediately.
03

Menu depth by role

The sidebar navigation shrinks or expands based on access level. Admin sees everything, staff sees only what moves their day.

Final Screens

The finished system.

Three roles, one unified interface, built for clarity and speed.

System screens

These screens define the foundation of the system and support daily operations across all roles.

Log in

Users are directed into the system with permissions according to their role

Invoices

Invoices are easy to review, create without disrupting daily workflows

Orders

Orders can be added, reviewed and updated

Suppliers

Organized access to suppliers and related data

Role based screens

The same system adapts to different roles by adjusting access, focus, and available actions.

Manager overview

A high leveloverview of the restaurant’s performance

SALES

Clear visibility into sales data, for manager view only

Inventory

Full control over the products, for manager and kitchen staff’s view and update

Creation form

One unified form used across the system, for manager and kitchen staff’s update

Reflection

What I learned. What I'd do differently.

01

Structure first, design second

On a role based system, early decisions about access and workflows determine everything that follows. Getting that right saved us from rebuilding later.
02

Complexity is not the enemy, confusion is

The challenge wasn't the number of features, it was making sure each role only ever saw exactly what they needed.
03

Consistency at scale

Maintaining a unified product language across three different role interfaces taught me that a strong design system isn't optional, it's the foundation.
04

If I had just more time

I'd run role specific usability tests to validate that each interface truly serves its user, and explore how the system scales as the business grows.
01

Structure first, design second

On a role-based system, early decisions about access and workflows determine everything that follows. Getting that right saved us from rebuilding later.
02

Complexity is not the enemy, confusion is

The challenge wasn't the number of features, it was making sure each role only ever saw exactly what they needed.
03

Consistency at scale

Maintaining a unified product language across three different role interfaces taught me that a strong design system isn't optional, it's the foundation.
04

If I had just more time

I'd run role specific usability tests to validate that each interface truly serves its user, and explore how the system scales as the business grows.