When to use each project view: board, list, timeline, grid
Most teams start with a board. Cards move from left to right, work gets done. But as projects grow, a single board can't answer every question. "What's due next week?" "Who's overloaded?" "Where are all the bugs?" Each question needs a different way to look at the same work.
A project view is a configurable way to display your project's issues from a particular angle. Board, list, timeline and grid views all show the same underlying data, organized differently to answer different questions about your work. Choosing the right view means picking the one that matches the question you're asking right now.
TL;DR: Boards handle daily execution by status. Lists help you search and filter fast. Timelines show how work unfolds over weeks. Grids give you two dimensions at once. They all share the same data. Pick the view that answers your current question.
What is a project view in project management?
A project view is a way to visualize the same set of issues from a different angle. Your data stays the same. Change a status on the board and it updates on the timeline. Add a due date in the list and it appears on the timeline.
The four main view types each serve a different purpose:
- Board: columns for status, assignee or label. Best for daily workflow.
- List: searchable, sortable table. Best for finding and filtering.
- Timeline: horizontal calendar with date bars. Best for planning over time.
- Grid: two-dimensional matrix. Best for cross-referencing two fields.
Most teams use more than one view per project. The key is knowing when to reach for each one.
When should you use a board view?
Use a board view when you need to track work through stages. Boards organize issues into columns, usually by status, so you can see what's in progress, what's done and what's next. They're the go-to view for daily execution.
You can also group columns by assignee or label to see work from different angles. Add custom fields to display extra context like priority or effort directly on each card.
Boards work well when:
- Your workflow has clear stages that tasks move through
- You want a visual overview of what's in progress right now
- The team needs to pick up the next available task
- You want to spot bottlenecks (too many cards stuck in one column)
Example: A development team uses a board with columns for Backlog, In Progress, Code Review and Done. During standup, they glance at the board to see what's stuck in Code Review and what's ready to pick up next.
Boards are the most intuitive view type. If you're just getting started with project management tooling, start here.
When should you use a list view?
Use a list view when you need to find, filter or sort issues quickly. Lists show all your issues in a searchable table where you can filter by status, assignee, label or any field. It's the fastest way to locate a specific issue.
Lists work well when:
- You need to search for a specific issue by name or keyword
- You want to see all issues matching a filter (e.g. everything assigned to you that's still open)
- You're doing bulk updates like changing statuses or adding labels
- You want a compact view of many issues without the visual overhead of cards
Example: A project manager needs to find all issues labeled "Design" that are still open. A quick filter on the list view shows exactly those issues, sorted by due date. She updates priorities for the top three in a few clicks.
Lists aren't flashy, but they're the view you'll reach for every time you think "where was that thing?"
When should you use a timeline view?
Use a timeline view when you need to plan work over weeks or months. It displays issues as horizontal bars on a calendar, from start date to due date, so you can see how work is distributed over time and spot scheduling conflicts before they become problems.
You can group the timeline by assignee, status or label, depending on the question you're trying to answer.
Timelines work well when:
- You're planning deliverables across multiple weeks
- You need to spot scheduling conflicts or overlapping deadlines
- You want to check if a team member is overcommitted during a specific period
- Stakeholders ask "when will this be done?" and you need a visual answer
Example: A marketing team is planning a product launch. The timeline shows "Landing page copy" (Mar 3-10), "Design review" (Mar 8-14) and "Developer handoff" (Mar 12-19) all overlap in the second week. That's a risk zone. They move the copy deadline earlier so the design review starts with final copy in hand.
The timeline is your planning view. Use it weekly to check the big picture, then switch to the board for daily work. For a deeper walkthrough, read our guide to planning deliverables with a timeline view.
When should you use a grid view?
Use a grid view when you need to cross-reference two fields at once. A grid places issues in a two-dimensional matrix with one field on columns and another on rows, making patterns like workload imbalances or coverage gaps visible at a glance.
You pick what each axis represents: status, assignee or label.
Grids work well when:
- You want to see team workload by status (who has too much "In Progress"?)
- You're doing release planning with priority on one axis and sprint on the other
- You need to spot gaps, like a priority level with nothing assigned
- You want a quick effort vs. priority matrix to decide what to tackle first
Example: A product team sets up a grid with status as columns and assignee as rows. They immediately see that one developer has 6 items in "In Progress" while another has none. Time to rebalance the workload before the sprint deadline.
Grids pair well with custom fields, which display extra metadata like effort or feature area directly on each card inside the grid cells. Read more about grid setups in our post on managing projects with matrix views and swimlanes.
How to choose the right project view for your workflow
Here's a quick comparison to help you decide:
| Board | List | Timeline | Grid | |
|---|---|---|---|---|
| Best for | Daily execution | Searching and filtering | Planning over time | Cross-referencing two fields |
| Answers | "What's the status?" | "Where is that issue?" | "When is it due?" | "How does X relate to Y?" |
| Organizes by | One field (columns) | Sortable columns | Time (dates) | Two fields (rows x columns) |
| When to use | Every day | When searching for something | Weekly planning sessions | Workload review, sprint planning |
| Needs dates? | No | No | Yes (start + due) | No |
A practical way to decide: ask yourself what question you're trying to answer.
- "What should I work on next?" → Board
- "Where's that issue about the login bug?" → List
- "Are we on track for the March deadline?" → Timeline
- "Is anyone on the team overloaded right now?" → Grid
Most projects benefit from at least two views. A board for daily work plus a timeline or grid for planning is a common setup.
Eigenfocus includes all four view types. Check pricing and get started.
How do project views work together in practice?
Views aren't isolated. They're projections of the same data. Change something in one view and it shows up everywhere. Here's a concrete example of how a team uses all four views during a single week.
Scenario: launching a new feature
The project has these deliverables: API endpoints, Frontend components, Documentation, QA testing and Launch checklist. Three people are working on it: Alex (backend), Sam (frontend) and Jordan (QA/docs).
Monday morning, planning session (Timeline view)
Jordan opens the timeline grouped by assignee. She sees that Alex has "API endpoints" and "Documentation" overlapping in week 2. That doesn't make sense since Alex is backend. She reassigns Documentation to herself and adjusts the dates so QA testing starts after the frontend work wraps up. The timeline now shows a realistic schedule with no overlaps.
During the day (Board view)
Alex opens the board to see his current tasks. Three cards sit in "To Do," one in "In Progress." He drags "Auth endpoint" to "In Progress" and starts working. By end of day, he moves it to "Code Review." Sam sees it there during her evening check and knows she can start integrating tomorrow.
Wednesday standup (Grid view)
The team opens a grid with status as columns and assignee as rows. Sam has 4 items in "To Do" and nothing in "In Progress." She was blocked waiting for the auth endpoint. Now that it's done, she picks up the first frontend card. The grid made the bottleneck obvious in seconds.
Thursday, bug triage (List view)
QA found several issues during testing. Jordan opens the list view, filters by the "Bug" label and sorts by priority. She assigns the critical bugs to Alex and adds due dates. Those dates now appear on the timeline for Monday's planning session.
Every view answered a different question. The data stayed consistent throughout.
You can further customize these views with custom statuses to match your workflow stages, like replacing "In Progress" with "In Review" or "Needs Feedback."
Common questions about project views
What's the difference between a board view and a grid view?
A board view uses one dimension: columns. A grid view uses two: columns and rows. A board might show issues grouped by status. A grid shows issues grouped by status and assignee at the same time, revealing patterns a single-axis board can't show.
Can I use multiple views in the same project?
Yes. You can create as many views as you need per project. Each view can be a different type (board, list, timeline or grid) with its own grouping and filters. Changes in one view are reflected everywhere since all views share the same underlying data.
Do I need to set up all four view types?
No. Start with whatever view matches your main workflow. Most teams begin with a board. Add a timeline when you need to plan over time, or a grid when you need to cross-reference two fields. Each view should solve a specific need, not add complexity for its own sake.
Can I customize what information appears on cards in each view?
Yes. You can add custom fields to your project and control which fields are visible per view. For example, you might show effort estimates on the board but hide them on the timeline where dates matter more.
Do all my issues appear in every view?
Yes. Views are projections of the same data. An issue exists once in your project and shows up in whichever views match its properties. The one exception is the timeline, which only displays issues that have both a start date and a due date.
Pick the right view for your next project
Every project has different questions at different stages. Boards handle the daily "what's next." Lists help you find things fast. Timelines show the plan over weeks. Grids reveal patterns across two dimensions.
Explore how teams use Eigenfocus for project management, software development or as a kanban tool.