An internal tool can end up being the application someone spends more time in than anything else on their computer.
They might use it to answer the phone, find a customer, organise a visit, check an order or work through a queue of requests. The same screens come around repeatedly, often while another person is waiting for an answer.
That's a good reason to care about how those screens work.
An admin template is a useful starting point. It can give a project a consistent set of components and save time on the ordinary interface work. The decisions about what somebody needs to see and do still belong to us.
Follow a task all the way through
When I look at an internal application, I want to follow a real piece of work across the screens involved.
Take a phone call about an existing appointment. The person answering may need to find the customer, identify the right address, check the appointment, read the latest note and make a change. Looking at each page separately can make the application seem perfectly reasonable while hiding how much navigation that task requires.
I'd want to know which information they keep having to remember, copy or reopen. That can tell us more than asking whether the dashboard looks good.
Sometimes the useful change is quite small: showing the address beside the appointment, keeping a filter when someone returns to a list, or giving a related record a clear link. Those choices can make a workflow easier to follow without adding another feature to the navigation.
Make the important distinctions visible
A status label needs to help someone decide what happens next.
Pending might mean we're waiting for the customer. It might mean a member of staff needs to approve something. It might mean a background job hasn't finished. If the distinction changes what the person should do, the interface needs to explain it somewhere.
I have the same feeling about dates. A table with three unlabelled dates might be compact, but I'd rather know which one means booked, due or last updated. The database column names don't always give us the words that work best on screen.
Colour can help people scan a list. I'd still want the meaning available in text, particularly for information that affects a decision.
Design for an interrupted day
The person using the application may be talking, reading another system, or answering a colleague at the same time.
I want forms to make their current state clear. Has the change saved? Is something still running? If validation fails, can the person see the affected field and keep the information they've already entered?
Keyboard access matters here too. Moving through a familiar form should feel predictable, and opening a dialog shouldn't leave someone searching for where their focus has gone.
For an action that has consequences, I'd use specific wording. A confirmation should identify what will happen to the record, especially when there are several similar records on the screen. The person pressing the button should have enough context to check their choice.
Spend the design effort where the work happens
I can enjoy polishing a dashboard as much as the next developer. I also want to look at the customer search, the edit form and the list that somebody opens dozens of times.
Those are good places to notice awkward spacing, unclear labels and information that appears in the wrong order. They are also places where a consistent component helps: once someone has learned how a picker or menu behaves, the next screen should meet that expectation.
I like internal software that feels considerate. Someone can come back after an interruption, understand where they are, and carry on. That's a design outcome I'd happily spend time on.