Interface design

A dashboard earns its space when someone can tell what happened and what needs their attention at a glance. I use that same test for forms, landing pages, and the rest of an interface.

Design around decisions

I sketch the most important path first, then use typography and spacing to show what comes next. I check where a long label wraps, what a list shows when it is empty, and how a dense screen reads on a phone. Those details become part of the component design before implementation.

Put the first decision in the right place

Someone opening a monitoring dashboard may have a specific question in mind. Is the service healthy enough to leave alone, or does it need attention now? Someone comparing development services has a different task. They need to recognise their problem, understand which service covers it, and decide whether to ask for help. The two screens can share a visual identity while giving very different information the most space.

I start by writing down the question a screen needs to answer. Then I arrange its content in the order someone can use it. A status belongs near the system it describes. An explanation can sit beside a difficult choice. A secondary action can wait until the visitor has enough context to decide whether it is relevant.

Give comparable things a common shape

A list becomes easier to scan when each item tells its story in a consistent order. On a project index, that might mean a title, a short description of the work, and one link to the detail. On a dashboard, it may mean a metric, its unit, the time period, and a supporting trend. I pay attention to alignment because it lets the eye move between equivalent pieces of information without hunting.

Consistency also makes exceptions more visible. If one project is awaiting a decision, a short status beside its name can be enough. Adding a bright badge to every row would give routine items the same emphasis. I choose colour, weight, and spacing according to the decision the reader needs to make.

Write the labels while designing the flow

A button labelled “Continue” makes sense when the next step is clearly visible. At the end of a form, someone may need a more precise description. Opening a message in WhatsApp and submitting an enquiry directly to a server are different actions. The wording should tell the visitor which one they are about to take.

I review labels in context, including what appears after a choice. If the interface asks for a phone number, the country selector, example format, and validation message should agree. If an option is optional, people should be able to tell before they spend time looking for the information. These are design decisions even when the visible change amounts to a few words.

Design the narrow version with real priorities

A desktop screen can show a summary and supporting detail side by side. On a phone, their order becomes a decision. A service page might put the description and next action first, followed by related reading. A monitoring tool might lead with the health signal and move its history underneath. Shrinking every element would preserve the arrangement while making the task harder.

I check the space around a control as well as its visible shape. A compact menu can still give each destination a comfortable tap area. Long labels need room to wrap. A popup needs a way to reach every action when the screen is short or the text is enlarged. An interface earns its polish in these ordinary conditions.

Show the states between the polished screens

A design showing a full list and a completed form leaves several moments undecided. What appears before the list arrives? What does someone see on the first day, before they have any records? If a search finds nothing, can they revise the query without losing it? I include those states when they affect the main task.

Error messages deserve the same attention. “Something went wrong” may be all the system knows, but often it can be more specific. A field with too few digits can identify the issue beside the input. A connection problem can leave the person’s work in place and offer another attempt. The design should reflect what the underlying system is able to promise.

For a design handoff, I make the relationships between states explicit. Take a project filter with an “All projects” option. Choosing a category changes the list, but it should also leave a visible indication of the current choice. If that category has no results, the screen needs a way back to the full list. A design that shows these three moments together gives the developer enough information to implement the interaction and gives a reviewer a short, meaningful test to perform. It also lets us discuss the wording before the design depends on a particular length of text.

Where the same decision appears elsewhere, I reuse the label. Visitors should be able to recognise a familiar action the second time they encounter it.

Review decisions with the people who know the work

A useful review follows one task from beginning to end. I might ask you to find a service on a phone, choose between two options, or explain what a dashboard number means. Where you look first and which words make you pause tell us more than a general preference for one colour over another.

Bring the content your customers already see, the questions they ask, and any screens your team relies on. A rough sketch with a realistic example can be more revealing than a polished mockup filled with sample text. From there we can agree on a set of screens and component states that a frontend developer can build and that you can recognise as your product.

Essential storage is always on. It remembers your choices and supports basic site features.