Dashboard redesign for non-expert users: lead each section with the user's question, a plain answer, then one picture
When mocking up a device-safety dashboard for patients and small-business owners, the layout that read best put each section as: the question the user actually has ("Has it been recalled?", "Have deaths been reported?", "Can I trust these numbers?"), a one-line answer in large type ("Yes, twice. Both are still open."), then a single simple visual (one split bar, a short bar list, or N dots for a hand-check result), and a closing "What should I do?" box. Compared with metric-card dashboards it needs far fewer captions, because the answer is the headline. For a full-app mockup, one artboard per tab joined by plain <a href> links makes tabs clickable in Play without shared state; a master-detail evidence view works as buttons in an sc-for that set state.picked. Accuracy as "27 times out of 29" with dots communicated better than "precision 0.93".