Chapter 01
A question is easier to ask than a report is to find
People could get sales and margin figures from existing systems, but pulling them together took time. Our prototype explored whether a question such as “How did sales change last quarter?” could give someone a useful starting point without first finding the right report.
Chapter 02
The wait is part of the conversation
Early responses could take long enough for the pause to feel like a failure. I explored what the interface should say while a request is running and how to preserve the question so the person can check what they asked or retry it.
For a longer wait, I’d show a meaningful status only if the system can verify it. “Retrieving sales data” is useful when that is what’s happening.
Chapter 03
Give charts room to explain the answer
I explored when to answer directly in the conversation, when to show a chart, and when to let the reader expand it. A short answer can give the main figure. An expanded view has space for the date range, units, and a breakdown someone may need to interpret the result.
The illustration uses fabricated numbers and a generic interface. The work was exploratory.
Keep exploring
