make this a bar chart, not a pie — they redo it.
What goes on a view
The colleague has a full toolbox to work with:- KPI tiles for the big numbers.
- Charts — area, bar, line, donut.
- Gauges and progress bars for things with a target.
- Tables with sortable columns and per-row buttons.
- Recommendation cards — what to do, plus the reasoning.
- Forms to collect input from teammates.
- Alerts and call-outs for what needs attention now.
Inline or saved
Every view starts inline in a chat. If it’s a one-off summary, leave it there and close the tab. If it’s something you’ll revisit, ask the colleague to save it. Now it lives at its own URL on your views page. Bookmark it. Open it next quarter — the colleague keeps it fresh as new data comes in.Action buttons
Views aren’t read-only. Every component can have buttons that do real work. A row in your sales view has a “Send follow-up” button. Click it. The colleague drafts the email and sends — or, if you’ve set the email tool to Review, shows you the draft first. An alert at the top of a customer health view has an “Open ticket” button. Click it. The colleague creates a Linear ticket with the relevant detail pre-filled. This is what makes views different from a static report. The dashboard is also the control panel.How they refresh
Views are live. As your colleague gathers more data — through a job, a session, or just normal use — the relevant views update. You can also click refresh on any view to pull the latest. And if a view is going stale, ask the colleague:Refresh this view and recompute the numbers from scratch.
Where to next
Examples
Real views teams are running.
Verification loops
Trust the numbers in your dashboards.