Insight / Product design
Published
Digital product design includes everything around the screen
How information, changing states, trust, accessibility and ongoing operations shape a useful digital product.
A polished screen can show what a digital product looks like when everything goes well. People also meet it when they are unsure where to begin, enter the wrong information, lose a connection or return months later. Design has to account for those moments, and for the system that makes the screen useful.
Organise the work before arranging the interface
Information architecture is the set of choices about what belongs together, what each thing is called and where a person can find it. Start by listing the tasks people need to complete and the information each task requires. Then map a path through them using language that makes sense to the people doing the work.
For example, a booking service may have availability, reservations, cancellations and receipts. If staff call a reservation a “session” while customers call it an “appointment”, the product needs a clear shared vocabulary. Navigation and labels should be tested with real tasks: can someone find how to change a time without knowing how the team organised its database?
Draw the states between success and failure
Every meaningful action has states. A form can be untouched, partly complete, saving, saved, rejected or awaiting confirmation. A list can be empty because no records exist, because a filter hides them or because the data did not load. Treating each of these as the same blank screen makes it harder to know what to do next.
Map the important states before building the finished interface. Write the message a person needs at each point, the action available to them and what the system will do with their work. If a payment or booking is submitted twice, is the result clear? If the connection drops after a save request, can the product confirm what happened without asking someone to guess? These details are part of the experience, not technical cleanup.
Make trust visible in ordinary interactions
Trust grows when the product tells the truth about what it knows and does. Show the difference between “saved on this device” and “received by the service” when that difference matters. Explain why sensitive information is requested, who can access it and how someone can correct it. Ask only for data the task requires and make destructive actions understandable before they happen.
A useful interface also works for people who navigate by keyboard, use assistive technology, read at different speeds or need clearer contrast. Accessibility affects the structure and words of the product as much as its colours. Test core tasks with more than one input method and device size while changes are still easy to make.
Design for the people who keep it running
Content needs an owner. Support teams need enough context to resolve problems without seeing information they do not need. Product teams need a way to release changes, detect errors and restore service. A feature that adds a new field may also create work for permissions, data retention, documentation and customer support.
Take a hypothetical community booking tool. Its success is not the attractive calendar alone. It is the ability to keep capacity accurate, tell someone when a place is confirmed, handle a cancelled session and help staff correct a mistake. Those responsibilities should influence the first release, even if some are handled manually at the start.
Our UX and UI guide explains the foundations of interaction design. For the systems and people behind a release, see the parts of an application and our development process.