Tines Academy › Lesson
Choose how to show each answer
Brief Tines 3B on the whole dashboard, then arrange the headline number, charts, and response list so the team can find what they need.
Objective: Choose a suitable way to display each answer and arrange the dashboard around what its audience needs to know first.
Describe the whole dashboard, then build one stage
A brief describes the whole dashboard you want to build. Maya’s will answer her team’s three questions, let them filter the results, refresh every weekday morning, and restrict access to the support team. The prompt in this lesson gives Tines 3B that full picture, then asks it to build just the next stage.
You’ve already loaded and prepared the data. In this lesson, you’ll arrange the dashboard’s main number, called the headline number, alongside charts and a response list so the team can find what they need. Filters and scheduled updates come later.
Building in stages gives you less to check before moving on. As you get more comfortable describing and testing dashboards, you can ask for more in a single prompt.
Match each answer to how you’d show it
Lay it out for the person reading it
Tines 3B may already have arranged much of the page. Keep what works, but check that the layout reflects what Maya’s team needs to see first.
Put the answer people need most at the top, followed by the detail that helps them understand it. Maya’s dashboard starts with the headline number and weekly trend. Below those, the product area bars show where negative feedback is concentrated, and the table lists responses to follow up on.
Give each section a title that says what it shows and which period it covers. The bars count negative ratings by product area. The follow-up table shows negative ratings from the last seven days, newest first. With real data, ticket links let the team follow up in the source system; with test data, they open the fictional response instead.
Show the counts behind percentages so people can judge whether a change involves a handful of responses or many more. Use labels as well as color, so the page is readable even when someone can’t distinguish the colors.
Build the layout
Open your existing workflow. Choose the tab that matches your setup, then send the prompt in workflow chat.
The dashboard helps our support team leads decide what needs attention each Monday and follow up on negative feedback during the week. Later, we’ll add filters and weekday updates. Keep the existing space-access restrictions. The dashboard should display information without changing tickets or contacting customers.
For now, arrange the prepared data in this order:
1. A headline number showing last full week’s percentage of negative ratings, compared with the week before.
2. A line chart of the weekly percentage over the last 12 full weeks.
3. Bars showing negative rating counts by product area over those same weeks, ordered from most to fewest.
4. A table of negative ratings from the last seven days, newest first, with a link to each ticket.
Title each section with what it shows and the period it covers. Show the counts behind each percentage and on each bar. Use labels as well as color. Keep the data-quality summary compact and visually secondary, directly beneath the weekly chart within the same section. Keep the preparation rules and saved data unchanged. Don't add filters or scheduled updates yet. Keep the workflow as a draft and summarize what changed, including how the headline comparison is calculated.
The dashboard helps our support team leads decide what needs attention each Monday and follow up on negative feedback during the week. Later, we’ll add filters and weekday updates. Keep the existing space-access restrictions. The dashboard should display information without changing tickets or contacting customers. Keep the "Test data" label visible.
For now, arrange the prepared data in this order:
1. A headline number showing last full week’s percentage of negative ratings, compared with the week before.
2. A line chart of the weekly percentage over the last 12 full weeks.
3. Bars showing negative rating counts by product area over those same weeks, ordered from most to fewest.
4. A table of negative ratings from the last seven days, newest first, showing each fictional ticket ID. Let people open the full test response, including its comment. Don’t invent ticket links.
Title each section with what it shows and the period it covers. Show the counts behind each percentage and on each bar. Use labels as well as color. Keep the data-quality summary compact and visually secondary, directly beneath the weekly chart within the same section. Keep the preparation rules and saved data unchanged. Don't add filters or scheduled updates yet. Keep the workflow as a draft and summarize what changed, including how the headline comparison is calculated.
Check the layout
Read the build summary in workflow chat. Look for what changed and how the headline number compares the two weeks.
Check the order and labels
Open the page in Browser.
The sections should appear in this order:
Headline number
Weekly line chart
Product area bars
Recent negative responses
Each title should explain what the section shows and which dates it covers. The data-quality summary should sit beneath the weekly chart without drawing attention away from it.
Check the headline number
The headline number should show the last full week’s negative-rating percentage and compare it with the week before.
Compare both percentages with the weekly chart. Can you tell whether negative ratings increased or decreased?
Check the product area bars
The bars should cover the same 12 full weeks as the line chart, ordered from most negative ratings to fewest.
Each bar should show its count. You shouldn’t need color alone to understand the chart.
Open a response
The table should show negative ratings from the last seven days, newest first. This period can include the current week, unlike the weekly chart.
With a connector, open one ticket link and find the matching survey response.
Without a connector, open one test response. Compare its fictional ticket ID, rating, and comment with the saved original.
If something doesn’t match
Tell Tines 3B what you expected and what you saw. Ask for a focused fix, then repeat the affected check.
Ask it to record unfinished checks in Readme.
Point at what you want to change
If you spot a title or column you’d like to change, you can point to it rather than describe where it is.
In Browser, select Inspect, then select the part of the page you want to change.
In workflow chat, describe the change. For example: “Shorten this title, but keep the date range.”
Select Inspect again to turn it off.
Check the result in Browser. The wording should change without losing the date range or changing the numbers.
If the layout already works, keep it as it is.
What to do if something still feels fuzzy
You described the full dashboard to Tines 3B and arranged the headline number, charts, and response list around Maya’s team’s questions. You also added titles that explain what each section shows and which period it covers. Next, you’ll add filters so the team can explore the results in more detail.
Build it safely: You checked the layout, date ranges, and a ticket link or test response in Browser before moving on to filters.