Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

Table view is the operational view for larger journeys. Use it when you need to inspect many items at once and work through the map systematically.

​
What table view is best for

Use table view when you need to:
  • Sort by status, owner, priority, impact, or effort
  • Filter down to one type of work
  • Find stale or incomplete items
  • Audit missing properties
  • Clean up larger journeys
  • Review linked tasks and metadata in one pass

​
How to use it well

Start by narrowing the surface.
  1. Filter to the item group or status you care about
  2. Sort by the property that matches the review goal
  3. Look for missing owners, unclear status, or outdated titles
  4. Open rows that need deeper inspection
  5. Update items without losing their connection to the journey

​
Why table view matters

As journeys grow, the problem stops being “we need more context” and becomes “we need to find and maintain the right context quickly.” Table view solves that by making the journey easier to scan and manage in bulk.

​
Best use cases

Table view works especially well for:
  • Pre-planning cleanup
  • Owner audits
  • Priority reviews
  • Status reviews
  • Metric maintenance
  • Linked task follow-up

​
How it complements journey view

Journey view is better for understanding the story. Table view is better for maintaining the quality of the dataset behind that story. Teams usually get the most value when they review in journey view first, then switch to table view to clean up what the discussion exposed.