Engineering

Stop building generic admin panels - design for the real operator.

Why most internal tools fail the people who use them every day, and a checklist for building ones that actually get used.

Every product has a back office: the screens staff use to approve, fix, refund, update and answer questions. These tools often get built last and in a hurry, usually as a generic table of every record with an edit button. Then the team works around them with spreadsheets and sticky notes.

The problem with "show everything"

A generic admin panel answers the question "what data do we have?" The operator is asking something else: "what do I need to deal with right now?" Those are different screens. When the tool can't answer the second question, people export to Excel, and you lose the audit trail, the validation and the speed you built the system for.

Start with a day in their chair

Before designing anything, sit with the people who'll use it for an hour. Watch what they search for, what they copy and paste, and what they keep in a notebook next to the keyboard. That notebook is your requirements document.

A checklist for internal tools that get used

  1. Lead with a work queue. The first screen shows what needs action, oldest or most urgent first, not every record.
  2. Search the way they talk. If staff say "the Smith order from Tuesday", make that searchable.
  3. Put the next action on the record. Approve, refund, resend, escalate. One click, with a confirmation for anything that can't be undone.
  4. Show history inline. Who changed what and when, right on the record, so nobody has to ask.
  5. Design the error states. What happens when a payment fails or a field is missing? Operators spend most of their day on exceptions.
  6. Respect permissions. Not everyone should see or change everything. Make roles part of the design, not an afterthought.
  7. Measure time to resolve. If a task took ten minutes before and four after, the tool is working.

Platforms help, if you configure them properly

Much of our consulting work is on Salesforce, which gives you a strong back office out of the box. The same rules still apply: page layouts, list views and quick actions should be designed around real tasks, not left on their defaults.

If your team has more workarounds than workflows, we can help.

Keep reading

More from TemTed.