Awareness: The Performance Gap - Building your PMO in Asana using the principles of PMI’s PMO Practice Guide

Hello everyone!!

Following on the success of my series Deploying Project Management Principles using Asana (I am very grateful :folded_hands: and delighted you are finding those useful), I decided to share with you all how to build your PMO in Asana using the Project Management Office principles from PMI.

My name is Rashad, and I am a PMO certified practitioner. I have built couple of PMOs from the ground up and I have done so using Asana for 12 years. So grab your coffee :hot_beverage: and hopefully(?!) enjoy!

__

You can’t manage what you can’t see.

Earlier this month, World Quality Week - an annual global celebration driven by the Chartered Quality Institute - asked how quality can power performance. It’s the right question. But for most CEOs, the harder one comes next: where does that performance get lost?

Picture a growing business with a clear strategy, an engaged board and a capable leadership team. On paper, everything is in place.

Ask the CEO what’s actually in flight across the business, though, and the answer might take a while. There’s the big transformation programme, of course. Then there’s the system upgrade finance started, the process review someone in sales mentioned, the client onboarding idea from the offsite, and three or four “quick fixes” that have been quick for about a year.

Every status report says green. Right up until one doesn’t.

This is the watermelon effect: green on the outside, red on the inside. It’s one of the most expensive colour schemes in business, and it’s where the performance gap begins.

This post opens a 10-part series on closing that gap, one step at a time (this is step 1 of 10). I’ll be working from the framework I trust most, PMI’s PMO Practice Guide, alongside the Asana features that make it practical.

How the gap forms

Few organisations set out to lose sight of their own work. It happens gradually.

Improvement often has no natural home, unless a business has an Improvement or Operational Excellence team. It usually sits with whoever cares most, a senior operator who already has a full-time job. Requests arrive in corridors, meetings and messages. Each one is reasonable on its own, but nobody holds the whole list.

Without a single view, a few predictable things happen:

  • The same request waits months, depending on who was asked and how busy they were.
  • Work starts without anyone deciding it should. No one stopped it either.
  • Routine commitments slip quietly. It’s not unusual for recurring work such as audits or reviews to run late year after year, simply because nothing makes the delay visible.
  • Leadership meetings become update meetings, spent working out what is happening rather than deciding what should.

Nobody is lazy. There’s simply no system, and without a system even the CEO can’t see the whole picture.

The method: PMI’s Value-Generating PMO Flywheel

In 2025, the Project Management Institute (PMI) published Project Management Offices: A Practice Guide. It reframes the PMO as a value-driven service with customers, not a reporting function that chases people for updates.

At its heart is the Value-Generating PMO Flywheel, a 10-step model that runs from Awareness Building to Value Recognition. Each step feeds the next, and the momentum builds. This series takes one step per post.

Step 1 is Awareness Building. PMI is clear that it isn’t a launch announcement. It means understanding who your customers are, what they’re struggling with, and how you’ll show them the value you bring. The guide describes it as “not a one-time event but a continuous process” (PMI, 2025, p. 146).

In plain terms: before you can fix how work gets delivered, people need to see the work.

The first move: one view of everything in flight

The instinct is often to start with a process, a template or a policy. I believe that the better first move is an inventory.

That means sitting down with each head of function and asking three simple questions:

  1. What are you working on that isn’t business as usual?
  2. Who owns it?
  3. What would you start tomorrow if you had the capacity?

These questions help you identify what is in motion, what is still a wishlist, and who is dependable in the team. It surfaces the wishlist, which is where most of the hidden demand lives.

Then everything goes into one place: a single view that the CEO, the leadership team and the people doing the work can all look at and agree on.

The Asana feature: Portfolios

In Asana, that single view is a Portfolio. A portfolio sits above your projects and shows them side by side, with each one’s owner, status, progress and due date. Portfolios can sit inside other portfolios. A strategy portfolio, for example, might hold a business improvement portfolio, a business development one, and an operations and assurance one. Each can also be linked to the company goal it supports.

Figure 1.0 shows a Portfolio list view, with projects, their status and the portfolio overall health check and its blockers.

Figure 1.0: One view of everything in flight, a couple of layers deep when needed

What makes a portfolio powerful for a CEO isn’t the colours. It’s the conversations it forces:

  • A project with no owner isn’t a project. It’s a wish.
  • A project with no recent status update is telling you something. Asana flags it as “no recent update”, and that flag is often more honest than a green dot.
  • Twenty projects with the same five names against them is a capacity problem waiting to happen. More on that in step 7.

:light_bulb: Start with an inventory, not a perfect structure. Don’t spend weeks designing fields and categories. Get everything in, even the half-formed ideas, and refine later. A rough, complete picture beats a beautiful, partial one. You may decide to capture this inventory in a different format. That is ok, as long as you have the portfolio view in mind, because this will drive your strategy forward. It will help you simplify complexity in the business.

:light_bulb: Make the portfolio leadership’s default view. If the leadership team still asks for updates by email or slides, the portfolio becomes one more thing to maintain. Review it in the regular leadership meeting, and ask owners to update their status before the meeting, not during it.

:light_bulb: Normalise amber and red. The first time someone marks a project “at risk”, thank them publicly. That’s how the watermelon effect ends: by making it safe to tell the truth early.

Three questions for your next leadership meeting, try answering these honestly:

  1. Can you name our top five initiatives and who owns each one?
  2. Do we know which of our people are over capacity today?
  3. When did a status last turn red early enough for us to act?

If any of these made you pause, you’re not alone. That pause is the performance gap.

Coming up next

In step 2, Needs Assessment, we’ll look at how to turn the wishlist into one front door for every request, and how Asana Forms make it possible to assess priority on the day a request arrives, not months later.

I hope you enjoyed your coffee. If your strategy keeps stalling between the boardroom and the work, let’s talk. No pitch, just a conversation.

Rashad


Resources

5 Likes

@Rashad_Issa This is great work! Very clear and easy to follow. Gave me some great ideas of how to work & clear up some of the confusion in our Technical PMO. Thank you thank you!

1 Like

That makes me very happy! Thanks a lot for the feedback

1 Like