Make the dashboard readable. Show what each filter changes.

Start with the intended audience, the decisions they make and the information they can legitimately use. A dashboard may help someone monitor work, investigate a change or reach a detailed record. Its structure should support those tasks without asking the reader to infer every definition. Discovery establishes what each figure represents, where its information comes from and which rules need a product-owner decision.

The design scope can include research, information architecture, wireframes, visual layouts, reusable components and an interactive prototype. Use explicitly illustrative data when real records are unnecessary or unavailable. The owner supplies approved definitions and calculation requirements; designers should not silently create business rules to make a sample chart look convincing.

Evaluate the complete screen at representative sizes with ordinary, empty, waiting and unsuccessful states as appropriate. A filter may intentionally affect the full dashboard or only one part, but its visible scope must match that intention. Handover includes labels, states, data expectations and interactions. Real calculation, connected analytics and access-controlled records need implementation and verification separate from prototype approval.

Imagine a dashboard with a period control, a chart, summary figures and a detailed list. A reviewer chooses a month. The chart changes, but a summary still uses all-time records and the list keeps its earlier selection. The screen may be showing deliberate different views, or it may be inconsistent. This is a hypothetical design exercise using illustrative data, not a Dubai business result or a connected analytics product.

Agree what the period control is intended to affect. If a summary deliberately remains all-time, label that meaning and make the relationship understandable. If the entire dashboard should follow the selection, show the selected period consistently and define the waiting or failed-response state while new results are being obtained. Avoid presenting old figures with a new label.

Walk through the same question before and after the filter changes. Ask the reviewer which period and population each component represents and how the detailed rows relate to a summary. Record unresolved definitions with the owner. The design should communicate the chosen rule; the implementation must provide and test the corresponding calculations and data responses.

Share the current dashboard or proposed task, intended users and definitions the business has already approved. Supply suitable sample records and explain which source owner can clarify the measures. Include cases where a period or population change has a material effect on interpretation. A list of desired charts is helpful when it is accompanied by the decisions those charts should support.

Dubai design reviews are conducted remotely with Asia/Dubai and Asia/Kolkata named in dated invitations. Nominate a product owner to consolidate decisions about definitions and a technical contact for data and implementation constraints.