List and board views
Ask a different question of the same working records.
Use lists, boards and filters to organize the overview around the work you need to inspect, without creating a separate copy of every record.
An overview should explain what needs attention.
A long list is not always the best way to discuss progress. The same records may be easier to inspect as a table, a board or a focused filtered view. Tsumira uses views to shape that overview. The underlying work still needs accurate fields and clear ownership; a different layout does not correct the data or settle what completion means.
Choose a view for a specific working question.
A list helps inspect details across records; a board can support a discussion of progress and grouped work. Choose the layout that helps the team answer the next question rather than creating another view simply because it is available. Explain the fields and grouping that readers should use when interpreting the screen.
- Lists and boards over working records
Filter deliberately and notice what is excluded.
Use filters to focus the overview on useful subsets of work. A record absent from a filtered view is not necessarily deleted, completed or inaccessible everywhere. Check the active criteria before drawing conclusions, and keep the broader view available when comparing totals or deciding which work is still outstanding.
- Focused subsets with explicit filter criteria
Keep the data source and user authority intact.
A view is an organized way to inspect records, not a new independent business ledger. Avoid maintaining duplicate fields in separate lists just to create another perspective. The user's permitted access still matters, and a visual grouping does not grant authority to edit all the underlying material. Review data and permissions when testing the setup with real colleagues.
- One maintained record set, multiple useful perspectives
A concrete workflow
Name the question
Decide whether the team needs detail, progress or a focused subset.
Choose layout
Use the supported list or board representation that fits.
Set criteria
Apply the filters needed and explain what they leave out.
Review conclusions
Check the underlying records before using the overview to decide.
An illustrative working example
Illustrative scenario: checking launch readiness
A team uses a board to discuss the launch-material list, then filters the list to inspect unfinished items. A colleague notices that a required record is outside the filter and opens the broader view before saying the launch is ready. The pilot tests whether the view answers the intended question, whether criteria are visible to its users and whether the same records remain understandable when another colleague takes over.
Questions about this topic
Does a view create another copy of the data?
The view organizes the working records. Keep one maintained source where possible instead of copying lists for each perspective.
Why is an item missing from my view?
Check the selected filters and your access before assuming deletion or completion. A narrower view may intentionally omit the record.
Does a board define our process automatically?
No. Agree the meaning of fields, groups and completion with the team. The layout supports that process rather than determining it.
Can a view expand someone's permissions?
Do not treat visual availability as a new access grant. The underlying record authority remains relevant to reading and editing.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Sheets
Application concept: Translate the purpose of a Google Sheet filter into a reviewed List view with explicit inclusion and exclusion rules.
Notion
Application concept: Compare a Notion board's workflow meaning with the supported List board view before adopting its grouping.
Linear
Application concept: Plan a narrow overview of agreed Linear references rather than claiming a replacement for its complete issue workflow.