Name the people and the decisions.
“We want to see everything in one place” is a starting point, not a requirement. Ask what someone needs to know at a particular moment and what they will do with that knowledge.
A team lead checking today’s exceptions may need a different view from a person managing an individual task. Decide which users the first version must serve and what they need to do without switching tools.
Turn one decision into requirements.
Illustrative requirements, not measured client outcomes
Which jobs need attention today?
- User: the person responsible for coordinating work.
- Information: status, due date, owner and blockers.
- Source: the agreed job system, not another editable copy.
- Timing: an update interval chosen for the working day.
- Action: review the job and assign or resolve the next step.
- Access: show only the records that person is allowed to see.
This definition gives a team something to evaluate. It does not assume a chart, real-time updates or a replacement of the existing job system.
Check whether the information is trustworthy.
Identify the source of each field, its owner and how it becomes available. Check missing records, duplicates, inconsistent categories and delayed updates. A polished interface cannot make unreliable data correct.
Agree how freshness is shown and what users see when a source is unavailable. “No jobs” and “we could not load the jobs” are different states. Make that distinction visible rather than quietly showing an empty view.
Where several systems are involved, assess the connections and record ownership before committing to the view.
Define who can see and change what.
Different users may need different records or actions. Scope sign-in, roles and permissions explicitly. A screenshot of a dashboard is not evidence that access controls already exist.
Decide whether the dashboard only reads information or can change it. If it can approve, assign or update records, define the business rules, confirmation and history required for those actions.
Choose a useful first version.
Select a small set of important decisions and a complete workflow. Include the necessary data connections, empty/error states and access boundaries. Leave additional views for later unless they are essential to that first workflow.
Write acceptance criteria that a person can check: the correct records appear, freshness is clear, access is appropriate and the next action works. Test with intended users and realistic, safely handled data.
Explore an interface, then define your system.
Atlas brings tasks, calendars, analytics and team views together as a concept showcase using sample content. It helps you explore an interface, while your organisation’s shared records, connections and permissions still need to be scoped.
SeasonReady demonstrates distinct worker and employer views with an illustrative client and brief. It offers another way to discuss what different people need from a connected app and dashboard.
See how MindLabs approaches custom systems and how discovery and delivery work.