Is your steering committee actually steering?
Five warning signs that your committee receives updates instead of making decisions, and how to fix it.
Read episodeShort, practical episodes on PMO, AI and project management. Each one is also available as a LinkedIn carousel.
Governance, steering and PMO setup: how organisations turn strategy into delivery.
Five warning signs that your committee receives updates instead of making decisions, and how to fix it.
Read episodeWhat new PMOs get wrong early, and what to do instead.
Read episodeA PMO is not overhead when it answers the questions your leaders keep asking. These five signs show when it is time to set one up, or fix the one you have.
Read episodeAI in project delivery: finding the right use cases, governing AI projects and leading teams that use AI.
Five steps for project and PMO teams to pick an AI use case that is worth doing and safe to try.
Read episodeProject practice and certification: reporting, risk, and preparing for PMI exams.
Green on the outside, red on the inside: five warning signs every sponsor should spot.
Read episodeFull of risks, empty of action: five warning signs and how to fix them.
Read episodeSenior leaders give a status report about two minutes. Here is a one-page structure that tells them what they need and what you need from them.
Read episodeMost PMP applications that stall do so on experience, not training hours. Here is how to count your months and describe your projects so PMI can approve them.
Read episodeHow well-prepared candidates study, and a simple plan to follow.
Read episodeOr just receiving updates? 5 warning signs, and how to fix them.
Updates that could have been an email take up the whole hour.
Sponsor, ask: “What decisions do you need from us today?”
There is no record of last month's decisions, or who owns the actions.
Sponsor, ask: “Where is our decision log, and who owns each action?”
Delegates without authority attend, so decisions are deferred.
Sponsor, ask: “Can everyone here commit their part of the organisation?”
Members read the papers in the meeting instead of before it.
Sponsor, ask: “Can we have the pack two working days before we meet?”
Issues are solved, or buried, below the committee.
Sponsor, ask: “What issue have we not been told about?”
5 mistakes to avoid in the first 90 days, and what to do instead.
Forms before purpose make a PMO look like bureaucracy.
Before you start, ask: “What problem will this PMO solve first?”
Without a senior champion, PMO standards become optional.
Before you start, ask: “Which executive will back the PMO when it is challenged?”
Reporting, training, tools and assurance, all in the first quarter.
Before you start, ask: “Which two services will we deliver well this quarter?”
Counting reports produced instead of decisions improved.
Before you start, ask: “How will leaders know the PMO made a difference?”
Software can't fix a process nobody has agreed.
Before you start, ask: “Can we run the process in a spreadsheet before we buy a tool?”
A project management office earns its place when it gives leaders reliable answers and helps projects deliver what they promised. These are the five signs we see most often in organisations that need one.
If it takes days to produce a simple list of active projects, their owners and their status, you have no portfolio view. Decisions about funding and priorities are being made without it.
One team sends a slide deck, another an email, a third nothing at all. Leaders cannot compare projects, so attention goes to whoever reports loudest rather than to where the risk is.
Status stays green until the week before a deadline and then turns red. That usually means there is no shared definition of status and no habit of raising risks early.
Without common templates, a lessons-learned habit and a simple way of working, each project manager reinvents the plan, the risk register and the report.
Business cases describe the benefits, but nobody confirms after go-live whether they arrived. The organisation keeps funding projects without learning which ones paid back.
You do not need a large team. A short diagnostic, a single reporting standard and a monthly portfolio review often fix the first three signs within a quarter. Our PMO advisory starts with exactly that.
Most AI efforts in project teams start with a tool and then look for a use. The better start is a problem you already have. These five steps help a project or PMO team find its first sensible AI use case.
List the tasks your team finds slow, repetitive or error-prone. Ignore the tools for now.
Ask your team: “Which task takes the most time without needing judgement?”
Status reports, minutes and risk logs that change with each author are strong candidates.
Ask your team: “Where does inconsistent work cost us time or credibility?”
AI earns its place when it improves a decision, not when it only produces more output.
Ask your team: “What would we decide differently with better information?”
Rate each task 1 to 5 for pain, and 1 to 5 for how defined and repeatable it is today.
Ask your team: “Is this task done the same way every time?”
Confirm the data is available and allowed to be used, especially personal or client data.
Ask your team: “Are we permitted to put this data into an AI tool?”
Download this episode as a carousel (PDF)
Want help applying this? Our AI project delivery and governance service starts with a short readiness assessment.
Green on the outside, red on the inside. These five warning signs show when a project's status is hiding real problems, and the question a sponsor should ask about each.
Status never passes through amber. Problems were there all along; they just weren't reported.
Sponsor, ask: “What would have to happen for this to turn amber?”
Each project manager uses their own judgement, so the colours can't be compared across projects.
Sponsor, ask: “Show me our written definition of green, amber and red.”
The delay is absorbed on paper. The final date only moves when it can no longer be hidden.
Sponsor, ask: “How far has each milestone moved from the baseline?”
Same risks, same owners, no new actions. A static risk log is a sign nobody is looking.
Sponsor, ask: “Which risk changed this month, and what did we do about it?”
“We held six workshops” is not the same as “we finished two deliverables”.
Sponsor, ask: “What did we finish, compared with what we planned to finish?”
Full of risks. Empty of action. 5 warning signs, and how to fix them.
Problems that have already happened are logged as risks.
Project lead, ask: “Which of these has already happened?”
Scores cluster in the middle, so nothing stands out.
Project lead, ask: “Which three risks would we act on this week?”
When “IT” or “Procurement” owns a risk, nobody does.
Project lead, ask: “Who, by name, owns this risk?”
Risks are described in detail, but no response has a date.
Project lead, ask: “What are we doing about it, and by when?”
The register comes alive before reviews, then goes quiet.
Project lead, ask: “What changed in the register since our last meeting?”
Most status reports are written for the project team and read by executives. That mismatch is why they get skimmed. A report built for a senior reader answers four questions on one page.
Start with an overall status and one sentence explaining it. Agree what each colour means in advance, for example: green means on plan; amber means at risk but the team can recover it; red means the team needs a decision or support to recover.
List the milestones completed and any change to scope, cost or the end date. Executives want movement, not a restatement of the plan.
Show the top three risks or issues only, each with an owner and the action being taken. A long risk list belongs in the register, not the report.
This is the section most reports leave out and the one executives value most. Name the decision, the person who needs to make it and the date it is needed by.
If your sponsor can read the report in two minutes and know whether to act, it works. If not, cut it until they can. We teach this structure in the Nexdil PM Series reporting workshop.
Before you book an exam date, make sure your experience will pass PMI's review. Most delays we see come from how experience is counted and described, not from the training-hours requirement.
| Your education | Project experience needed | Plus |
|---|---|---|
| High school diploma or secondary school completion | 60 months leading projects in the last 8 years | 35 contact hours of training, or an active CAPM |
| Associate's degree or qualifying technical or vocational credential | 48 months leading projects in the last 8 years | 35 contact hours of training, or an active CAPM |
| Bachelor's degree or higher | 36 months leading projects in the last 8 years | 35 contact hours of training, or an active CAPM |
| Bachelor's or postgraduate degree from a GAC-accredited programme | 24 months leading projects in the last 8 years | 35 contact hours of training, or an active CAPM |
Always confirm the current requirements in the PMP Certification Handbook on pmi.org before you apply.
PMI counts calendar months. If you ran two projects at the same time from January to June, that is six months, not twelve. List your projects in date order and mark any overlap before you add up the total.
For each project, write a short summary covering the objective, your role, what you were responsible for and the outcome. Use the language of project leadership: planning the schedule, managing risks, leading the team, reporting to sponsors, closing the work.
PMI selects some applications for audit. Keep your training certificate, your degree or diploma, and the name and contact of a supervisor who can confirm each project before you submit.
Next step: download our free PMP Eligibility Checklist and count your months before you register.
5 study habits of well-prepared candidates, and a simple 8-week plan.
Plan your study around PMI's current Exam Content Outline, not just one textbook.
Ask yourself: “Have I mapped my study plan to the Exam Content Outline?”
Many questions test what a project leader should do next, not definitions.
Ask yourself: “What would a servant leader do first in this situation?”
Questions span all three ways of working.
Ask yourself: “Can I explain when each approach fits best?”
Full, timed mock exams build stamina and pacing.
Ask yourself: “Have I completed at least two full timed mocks?”
The real learning is in why an answer was wrong.
Ask yourself: “Do I keep an error log, and what does it tell me?”
About one email a month with course dates, PM Series workshops and new Insight Series episodes.
Hello! Ask us anything on WhatsApp. Tap a question to start:
When does the next PMP cohort start?I want training for my teamTransformation or PMO supportFibre rollout supportChat on WhatsAppOr call +233 24 262 9852 · info@nexdilglobal.com