01
Roles
Each person sees the work that belongs to them.
BRIEF 03 OF 06 · ROLES, SCREENS, DATA
Web application
A product built around the steps a team already uses, when a template cannot hold them.
THE BRIEF
The real system has become a spreadsheet, and a template keeps dropping the exceptions.
- 01 Roles
- 02 Screens
- 03 Records
THE PIECE
How this brief is actually done
A web application at MitCoral is scoped from the work a team already does. Who touches the record, which step is skipped, and which spreadsheet everyone is afraid to edit. The first screens remove that, and they stop there.
Roles decide what each person can see. The next step is visible on a phone and on a desk. The record lives in one place, with a history, instead of in a file that only one person trusts.
This is not a case study with a logo. If a template can hold the work, MitCoral says so and does not build an application to fill a portfolio.
INSIDE THE PIECE
What it holds
02
Screens
The next step, on a phone and on a desk.
03
Records
One place, with a history, instead of a private file.
THE LIMIT
What this page will not claim
Version one does not rebuild the company, and it does not replace tools that already work.
THE FIRST VERSION
From the first call
Three marks. The page goes into real use before the scope grows.
-
01
Map
Who does the work, and where trust is lost.
-
02
Shape
The smallest set of screens that removes that loss.
-
03
Live
Real use, then the corrections the first weeks show.
THE SERVICES
Which services this brief uses
ON THIS BRIEF
Questions teams ask
When is an application the right piece?
When a page and a form cannot hold the roles or the exceptions. If they can, this brief does not start.
Do you show a named product here?
No. The portfolio shows the shape of the build. It does not borrow a product name.
What is left out of version one?
Everything the brief did not name. Later work waits until the first version is in real use.
The other briefs
Same studio. The piece changes with the work.