Work Operations dashboard
Case study
Operations dashboard
An internal dashboard that replaced scattered spreadsheets for a growing operations team — one source of truth for status, handoffs, and ownership.
- Client
- Growing business
- Industry
- Operations
- Timeline
- 6 weeks to v1
- Year
- 2025
- Role
- Build partner — discovery, UX, dashboard, rollout
- Laravel
- Admin UI
- MySQL
- Role-based access
1
Shared ops workspace
4
Role types supported
6 wks
Sheet chaos to live
0
Copy-paste handoffs
Overview
Operations lived across multiple spreadsheets, chats, and inboxes. Status was always somebody’s best guess. GujjuTicks designed and shipped a web dashboard around real daily workflows — with roles, filters, and clear ownership — so the team could stop reconciling sheets.
The challenge
Growth made the spreadsheet model brittle. Updates lagged, handoffs got missed, and nobody trusted a single “current” view of work.
- Status scattered across sheets, email, and chat
- No consistent ownership when items moved between people
- Managers spent hours reconciling conflicting versions
- New hires needed tribal knowledge just to find the truth
Our approach
We mapped the real day-to-day path of work — not the org chart — then built a dashboard that mirrored those statuses, permissions, and filters.
- Shadowed ops routines to capture actual steps and exceptions
- Defined roles and what each role can see or change
- Designed status transitions that match how work already moved
- Shipped in slices so the team could adopt without a big-bang cutover
What we built
A practical ops dashboard the team could run from — not a BI vanity board.
Role-based access
Operators, leads, and admins see the right queues and actions — without exposing everything to everyone.
Status workflows
Clear states and transitions so handoffs are intentional, visible, and auditable.
Filters & search
Find work by owner, status, date, or priority instead of scrolling a giant sheet.
Exports & summaries
Light reporting for weekly reviews — without sending people back to spreadsheets.
Delivery timeline
A clear path from discovery to launch.
-
Week 1
Discover
Map workflows, pain points, and the minimum viable ops model.
-
Week 2
Design
Roles, statuses, key screens, and migration plan from sheets.
-
Weeks 3–5
Build
Dashboard, permissions, filters, and iterative team demos.
-
Week 6
Rollout
Pilot with one squad, train, then expand usage.
The outcome
The team runs day-to-day work from one place. Handoffs are clearer, managers stop reconciling versions, and the product is ready for automation later.
- Single shared source of truth for operational status
- Fewer missed handoffs between people and shifts
- Faster onboarding for new ops team members
- Foundation ready for notifications and automations
“We stopped asking “which sheet is right?” The dashboard became the meeting.”
More work
Replace spreadsheet ops
Need a dashboard your team will actually use every day?