Loading
Loading
Case study · Studio study
The internal tool the company already runs on — made explicit.
Studio study with a working title. Not a named-client claim.
Overview
Millwright is an internal operations console: the jobs, records, and approvals that currently live in sheets and inboxes. We treat internal tools with the same seriousness as customer products because they are the company.
The challenge
Internal tools get no design, no authz, and a deploy story of 'ask Dave'. They also accumulate the real business rules. The work is to make those rules visible, permissioned, and recoverable.
Objectives
SSO and role-aware navigation
Every mutation auditable
Jobs you can retry
A UI a new operator can learn in a week
Strategy
Start with the spreadsheet columns that are actually the schema. Build the smallest console that deletes three manual processes. Add an assistant only for search and draft — not for approvals.
Discovery
Shadowing revealed five 'final' versions of the same tracker. We picked one ontology and migrated with a diff the operators could see.
UX
List → record → action. Bulk actions with a preview. Saved views per role. No marketing language in the empty states.
Design
Utilitarian, not ugly. A system of tables, filters, and a maroon attention column. Keyboard shortcuts documented in the product.
Engineering
A boring CRUD core with a job runner. Deploy on a private network or SSO-gated URL. Backups tested. Feature flags for dangerous actions.
Architecture
SSO
The only door.
Technology
Frontend
Backend
AI
Infra
Implementation
Result
Sheet count
Reduced (placeholder)
Audit
On writes
Retry
Jobs
Replace with measured results after a client engagement.
Voice
“Replace with an ops director: the tool matches the Tuesday, not the all-hands slide.”
Start
Tell us what you are trying to ship. We will come back with questions, a shape, and whether we are the right studio for it.