The right view for the job: which project visualization to use when

Most project management platforms can show the same data a dozen ways. Most teams pick one view, usually whatever the tool opens to, and use it for everything. Then they wonder why the client meeting runs long, the standup turns into a status report, and nobody noticed that the design team was booked at 130 percent.

Every visualization is built to answer one question well. The fastest way to improve how a firm sees its work is to match the view to the question, and the question to the meeting.

The quick reference

Gantt chart

Answers: When will it be done, and what depends on what? A Gantt chart lays work out over time, shows how phases overlap, and makes dependencies and milestones obvious. It is the best view for planning a project and for walking a client through the timeline.

Watch out: Gantt charts go stale fast and say nothing about who is overloaded. Keep them at the level of phases and milestones, not every small task.

Kanban board

Answers: What is moving, and what is stuck? A Kanban board shows each task's status as a card moving across columns. When one column piles up, as review usually does, you have found your bottleneck. It suits creative and production teams, retainers and support work, where work flows continuously.

Watch out: Boards have no sense of time, so pair them with dates. They also need work-in-progress limits; a column with 30 cards is a list, not a flow.

Calendar

Answers: What is happening when? Calendars are for events with fixed dates: deadlines, client reviews, launches, shoots, meetings and time off. Content and campaign teams often live in one.

Watch out: A calendar shows events, not effort. A busy calendar is not a plan, and it will not tell you whether the work behind those dates fits the people available.

Burndown and burnup charts

Answers: Are we on pace to finish within scope and budget? A burndown chart plots the work or budget remaining against an ideal line to zero. A burnup chart plots work completed against total scope, which makes scope creep visible, because you can watch the scope line move.

Use them for fixed-fee projects, sprints and monthly retainer hours. Watch out: they are only as good as your time data. If scope changes often, use a burnup; a burndown quietly hides new work. (More on that in Three keys to avoiding scope creep.)

Workload view

Answers: Who is overbooked, and who has room? A workload view shows each person's booked hours against their capacity, week by week. It is the heart of the weekly resourcing meeting and of good trafficking.

Watch out: It only works if work is scheduled in hours, not just assigned as tasks, and if tentative pipeline work shows up alongside confirmed projects.

Budget vs. actual

Answers: Are we making money on this? A simple comparison of hours or dollars budgeted, spent and remaining, ideally next to percent complete, by project, client or phase. It belongs in every weekly project review and every account review.

Watch out: Spend without progress is meaningless. Fifty percent of budget gone at 50 percent complete is fine. At 30 percent complete, it is a conversation you need to have this week.

List or table

Answers: What exactly needs doing, by whom, by when? Lists are unglamorous and essential. They are the best view for an individual's "my work this week," and for sorting, filtering and updating many tasks at once.

Watch out: A list has no sense of flow or time. Use it for doing the work, not for understanding the project.

Match the view to the meeting

One set of data, many views

The point is not to pick a favorite view. It is to keep one set of live project data and look at it the way each question needs. That is the idea behind Kerdion OPS: prospects, plans, projects, time and profit in one place, shown as a board, a timeline, a calendar, a workload or a budget, depending on who is asking. See Kerdion OPS

Related: Three keys to avoiding scope creep · The six pillars · How we assess