The view your boss understands at first glance

Four tiles - table, filter, grouping, timescale - flowing into one saved menu entry: a Microsoft Project view

Meeting room, steering committee. You project the plan, and what appears on the screen is the Gantt chart the way you use it: three hundred rows, bars packed like a barcode, the timescale in days. Four seconds pass and someone asks: “sorry — are we late or not?”.

And you start scrolling.

It’s not the plan’s fault, and it’s not the fault of whoever asked. You are showing a working tool to people who have to make a decision. Those are two different jobs, and in Microsoft Project they are solved with two different views.

The Gantt you use isn’t built for the people who decide

The default Gantt Chart view is built for the person who writes the plan. The table underneath it is called Entry, and the name says it all: Task Name, Duration, Start, Finish, Predecessors, Resource Names. These are the fields you need to enter the data.

A committee doesn’t enter anything. It wants to know three things: where we are, compared with what we promised, and what happens next. None of those three is a column of the Entry table.

There’s a scale problem too. You work in days, because that’s where your problems live. The people listening think in months and quarters: if one month takes up two metres of screen, the project can’t be seen — only guessed at.

A view is four things at once

Here is the point almost everyone misses, and it’s the reason the effort of tidying up the screen gets thrown away every single time.

In Project a view is not “the Gantt”. It is the combination of four elements:

  • the table: which columns you see;
  • the filter: which rows you see;
  • the grouping: how they are ordered and summed;
  • the timescale: how much time fits on the screen.

Whoever prepares the meeting usually changes one or two of them by hand, shows the plan, and when the file is closed everything snaps back. Next week it starts all over again. Saving the combination — not the individual pieces — is the whole trick.

Build it once

Start from the Gantt Chart and change the four elements, in this order.

The rows. A committee doesn’t look at detail tasks. On the View tab, in the Data group, choose Outline → Level 2: the skeleton of the plan remains, and three hundred rows become twenty. If the plan has good milestones, the Milestones filter works even better: you show only the dates somebody promised.

The columns. Don’t modify the Entry table: copy it. On the View tab, Data → Tables → More Tables, select Entry, click Copy, and give the copy a name of your own — “Committee” is fine. Then remove Predecessors and Duration, and add the columns that answer the three questions:

  • % Complete: where we are.
  • Start Variance and Finish Variance: how far we have drifted from the baseline. These are the columns nobody uses and that say everything — they only exist if you have saved a baseline, and if you haven’t, this is the reason to do it today.
  • Remaining Work: how much is genuinely left, which is a different question from how much has been done.

The time. Use the zoom slider at the bottom right and widen until you see months or quarters. The plan must fit on one screen: if you have to scroll to tell the story, you are not telling it.

The save. View → Task Views → Other Views → More Views → New, give it a name — “Committee status” — and tick Show in menu. From that moment it is a menu entry like any other, and next week’s meeting costs you one click.

Carry it into your other projects

A saved view lives in the file where you created it. If you manage several projects, the Organizer copies it wherever you need it: File → Info → Organizer, Views tab, and you move it from the current file to Global.MPT, the template every new project is born from.

One thing to watch: if the view uses your “Committee” table, you must copy that too, from the Tables tab. A view without its table arrives lame — and you find out in the meeting.

What a view does not do

It doesn’t change the plan. It doesn’t recover a day of delay, doesn’t fix a wrong dependency, doesn’t invent a baseline you never saved. All it moves is the boundary between what is shown and what stays out.

And that is exactly why it must be used honestly. A level-2 view hides the detail: if the detail contains a problem, the problem doesn’t disappear — it disappears from the projection. The rule I gave myself is simple: whatever I hide from the meeting must live in a line of commentary, not in silence.

The real gain isn’t cosmetic

Once the view is saved, the way the meeting starts changes. You don’t open the file and hunt around: you open the menu entry, and in three seconds the screen shows the plan in the language of the people listening. The discussion starts from the right question instead of “sorry, can you show me just the phases?”.

It’s half an hour of work, once. Then it follows you into every project that comes after.


ProjectEdgeTools builds small tools that fix real Microsoft Project headaches — from cleaning sensitive data out of your plans to getting them into Power BI in one click. Have a look at the suite.

#MicrosoftProject #ProjectManagement #PMO #Reporting #Views

This article is part of the guide The plan that holds: Microsoft Project best practices, symptom by symptom, nineteen things you can see in a plan and the move that reveals each one in thirty seconds.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top