Key takeaway
Order the first screen around the signed-in person: records they must handle, exceptions that need their judgment, and items they handed off that are still waiting. Each item should open a record. Company charts can wait; an empty queue should say there is nothing to do.

Consider a hypothetical case. A salesperson opens the admin home and sees this month's order total, a conversion rate, and a category pie. The numbers are all there. They still post in the team chat: which customers should I call first today? The workbench did not answer. It reported on the company. It did not arrange this person's work.
The first screen should be ordered around the person who just signed in. Give priority to three kinds of items only: records they must handle, exceptions that are stuck and need their judgment, and items they already handed off that nobody has accepted yet. Each block should open a specific record. Company-wide totals can stay, but not in front of those three, and not on the screen of someone who cannot act on them.
A queue, an exception list, and a waiting list answer different questions
A queue holds records where the rule is already clear, finishing the record moves the work forward, and the owner is the current user. For a salesperson that might be inquiries whose next-contact time has arrived. For a warehouse lead it might be orders that are cleared to ship and have a complete address. Sort by urgency, not by a single created-at order for every role.
An exception is a record the process cannot finish without a decision. A missing address, a payment that does not match the order, a failed import row. A red count that says "12 exceptions" tells people something is wrong and still does not tell them which record to open.
A waiting list holds items the current user started that the other side has not accepted or confirmed. These are easy to file under "done by me" and then lose. The sender assumes the work is in someone else's hands. The workbench should keep showing that nobody has explicitly taken it. How acceptance is defined is a separate state-design problem. This screen only has to keep the entry visible.
All three pass one test: selecting an item opens a record someone can act on. A module that fails that test does not belong on the first screen.
The role chooses the first screen; permission chooses what can be opened
Sales, warehouse, and finance can share one set of orders and still need different mornings. Sales looks for people to contact, the warehouse looks for shipments that can leave, finance looks for payments waiting for review. One operating overview forces each of them to hunt for an entry.
That is not the same decision as a permission matrix. Permission answers whether this person may open a class of records. The workbench answers which of the records they may open should appear first. Access to every order is not a reason to spread every order across the first screen.
You also do not need a separate system per role. One body of data and different default views is enough. Let people collapse secondary modules. Do not let them collapse "assigned to me." That block is why the screen exists.
A module tradeoff table
Use this table to decide what reaches the first screen. Write the empty state before anyone argues about charts. A blank panel looks like a page that failed to load.
Module | Question it answers | Put it first | Keep it off the first screen | What to say when empty |
|---|---|---|---|---|
Assigned to me | Which records are mine right now | Roles that process records daily | People who only read reports | Nothing is waiting for you |
Blocked exceptions | Which records need my decision | People who clear blockers | Every warning pushed to every person | No exceptions need you |
Started by me, still waiting | Has anyone taken what I handed off | People who often submit or hand off | Roles that almost never initiate | Nothing is waiting on someone else |
Due today | Which records pass a time limit today | Work that has real deadlines | Reference data with no due date | Nothing is due today |
Recently opened | Where did I stop | As a secondary entry | As a substitute for the queue | The module can hide itself |
Summary numbers | What is the scale or mix lately | People who prioritize from numbers, and only if the number opens its rows | Everyone's first screen, or any number whose definition is still unsettled | State the scope; do not treat zero as a verdict on the business |
Quick create | How to start a record | Roles that create often, beside the queue | Filling the first screen | Not applicable |
Notice or policy | Is there a change I must know today | A short, dated notice | A permanent company introduction | Hide the module when there is no notice |
Ask one question: after seeing this module, can the person do something immediately? If not, move it down or leave it out.
A hypothetical example: three first screens, one company
- Sales: follow-up and confirmation
- Warehouse: dispatch and exceptions
- Finance: review and discrepancies
- A shared set of business records
This is a hypothetical case, not a real company's system. A small equipment trader keeps orders, shipments, and payments in one admin.
The salesperson sees:
- Follow-ups due, sorted by next-contact time, overdue items first.
- Proposals they submitted that are still waiting on the customer or a manager.
- A way to create an inquiry.
This month's sales total is not the first block. If it appears, put it in a side column and name the basis, for example order date, excluding cancelled orders. The number should open those orders. An uncheckable total does not help.
The warehouse lead sees a different cut:
- Ready to ship: the business state allows shipping and the address is complete.
- Shipping exceptions: missing address or insufficient stock, for them to resolve or send back.
- Shipments that must leave today.
No sales total. That number does not tell them which order to pick first.
Finance sees:
- Payment requests waiting for review.
- Records where the amount received does not match the order.
- Requests returned to someone else that have not been submitted again. Finance can see the work is no longer theirs without treating it as finished.
The three screens read the same records through different slices. Build views, not three backends.
Four designs that look finished and go unused
One first screen for the whole company. People search through someone else's indicators for their own work, then go back to a spreadsheet or a chat.
A red number that does not open a filtered list. The page says "12 exceptions" and lands on every order. The exception module should carry its filter with it.
Notifications used as a workbench. Dismissing a message means someone saw it. A workbench is the list of unfinished records, and an item leaves only when the record is handled. Whether a message should be sent at all is a separate rule. More notice boards will not fix it.
An empty panel with no sentence. People cannot tell "nothing to do" from "the list is broken." When there are no records, say so.
A checklist for the business owner and the builder
Fill this in per role. The request stops being "build us a dashboard."
[Workbench module checklist]
1. Who uses it
- Daily roles:
- The first job each role opens the system to finish:
2. First-screen modules
- Which records are in "assigned to me," and which field sorts them:
- Which exception types exist, and which filter each one opens:
- Whether "started by me, still waiting" is needed, and how waiting is defined:
- Which modules are explicitly off this role's first screen:
3. After the click
- Does each block open a record rather than another chart:
- When the record is done, does it leave the queue:
4. Empty state and access
- Sentence shown when there is no data:
- If the person cannot see those records, is the module hidden, or visible but empty of rows:
- May the person collapse modules, and which block may not be collapsed:
5. Numbers
- If a summary number is shown, who confirms its definition:
- Can the number open the rows that make it up:Bring the completed list with the current spreadsheets and role names. If the work today is scattered across sheets, business system development is about organizing forms, records, and tasks, and the system preparation guide is a way to gather the sheets and the jobs people actually do.
A lead that nobody follows up is a different problem. How a sales follow-up workflow is put together covers time limits and reminders. How a weekly report is assembled covers who a summary is for. Neither replaces the module choices on this page.