Insights

Practical insights on delivery, transformation and measurement

The Nexdil Insight Series: short, practical episodes on PMO, AI and project management, written by practitioners.

Nexdil Insight Series

Practical insights in three series

Short, practical episodes on PMO, AI and project management. Each one is also available as a LinkedIn carousel.

PMO Insight Series

Governance, steering and PMO setup: how organisations turn strategy into delivery.

Episode 1

Is your steering committee actually steering?

Five warning signs that your committee receives updates instead of making decisions, and how to fix it.

Read episode
Episode 2

Setting up a PMO? Five mistakes in the first 90 days

What new PMOs get wrong early, and what to do instead.

Read episode
Episode 3

Five signs your organisation needs a PMO

A 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 episode
AI Insight Series

AI in project delivery: finding the right use cases, governing AI projects and leading teams that use AI.

Episode 1

Problems, not tools: finding your first AI use case

Five steps for project and PMO teams to pick an AI use case that is worth doing and safe to try.

Read episode
PM Insight Series

Project practice and certification: reporting, risk, and preparing for PMI exams.

Episode 1

Is your project a watermelon?

Green on the outside, red on the inside: five warning signs every sponsor should spot.

Read episode
Episode 2

Is your risk register a filing cabinet?

Full of risks, empty of action: five warning signs and how to fix them.

Read episode
Episode 3

Status reports executives actually read

Senior 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 episode
Episode 4

PMP eligibility: how to count your project experience

Most 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 episode
Episode 5

Preparing for the PMP? Five study habits and an 8-week plan

How well-prepared candidates study, and a simple plan to follow.

Read episode
PMO Insight Series · Episode 1

Is your steering committee actually steering?

Or just receiving updates? 5 warning signs, and how to fix them.

1. The meeting is a status readout

Updates that could have been an email take up the whole hour.

Sponsor, ask: “What decisions do you need from us today?”

2. Nobody remembers what was decided

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?”

3. The wrong people are in the room

Delegates without authority attend, so decisions are deferred.

Sponsor, ask: “Can everyone here commit their part of the organisation?”

4. The pack arrives on the day

Members read the papers in the meeting instead of before it.

Sponsor, ask: “Can we have the pack two working days before we meet?”

5. Problems never reach the committee

Issues are solved, or buried, below the committee.

Sponsor, ask: “What issue have we not been told about?”

Turn updates into decisions

  • Before: Pack out 2 working days ahead
  • During: Decisions first, updates last
  • After: Decision log shared within 24 hours
  • Put decisions at the top of the agenda, not at the end.
  • Keep a decision and action log with names and dates.
  • Agree escalation thresholds for cost, time and scope.
  • Review membership every quarter. Authority, not seniority.

Download this episode as a carousel (PDF)

Back to the PMO Insight Series

PMO Insight Series · Episode 2

Setting up a PMO? Five mistakes in the first 90 days

5 mistakes to avoid in the first 90 days, and what to do instead.

1. Starting with templates

Forms before purpose make a PMO look like bureaucracy.

Before you start, ask: “What problem will this PMO solve first?”

2. No executive sponsor

Without a senior champion, PMO standards become optional.

Before you start, ask: “Which executive will back the PMO when it is challenged?”

3. Trying to do everything at once

Reporting, training, tools and assurance, all in the first quarter.

Before you start, ask: “Which two services will we deliver well this quarter?”

4. Measuring activity, not value

Counting reports produced instead of decisions improved.

Before you start, ask: “How will leaders know the PMO made a difference?”

5. Buying a tool first

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 90-day start that earns trust

  • Days 1–30: Listen: find the real pain points
  • Days 31–60: Design: agree the mandate and two services
  • Days 61–90: Deliver: show the first quick wins
  • Agree the mandate with your sponsor in writing.
  • Start with one portfolio view and one reporting standard.
  • Show a visible quick win within 90 days.
  • Expand services every quarter as trust grows.

Download this episode as a carousel (PDF)

Back to the PMO Insight Series

PMO Insight Series · Episode 3

Five signs your organisation needs a PMO

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.

1. Nobody can say how many projects are running

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.

2. Every project reports differently

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.

3. Problems surface too late

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.

4. Good people start every project from scratch

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.

5. Benefits are promised but never checked

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.

Where to start

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.

Back to the PMO Insight Series

AI Insight Series · Episode 1

Problems, not tools: finding your first AI use case

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.

1. Start with the work, not the tool

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?”

2. Find where inconsistency costs you

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?”

3. Ask what better information would change

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?”

4. Score pain and readiness

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?”

5. Check the data and the rules

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?”

Where to start: pain × readiness

  • High pain, ready: Start here: quick wins
  • High pain, not ready: Define the process first
  • Low pain: Schedule later
  • Pick one task and one tool for your first pilot.
  • Run it for 4 to 6 weeks with a clear success measure.
  • Keep a person in the loop for decisions and sign-off.
  • Check your AI and data policy before you begin.

Download this episode as a carousel (PDF)

Want help applying this? Our AI project delivery and governance service starts with a short readiness assessment.

Back to the AI Insight Series

PM Insight Series · Episode 1

Is your project a watermelon?

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.

1. Green for weeks, then suddenly red

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?”

2. Nobody can say what “green” means

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.”

3. Milestones slip, but the end date doesn't

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?”

4. The risk log hasn't changed in a month

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?”

5. Reports describe activity, not progress

“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?”

The fix: make status honest and useful

  • Green: on plan
  • Amber: at risk; the team can recover it
  • Red: needs a sponsor decision to recover
  • Write down what each colour means and use it on every project.
  • Report against baseline dates, so slippage is visible.
  • Add “decisions needed”: who, what, by when.
  • Reward early amber. Bad news early is good governance.

Download this episode as a carousel (PDF)

Back to the PM Insight Series

PM Insight Series · Episode 2

Is your risk register a filing cabinet?

Full of risks. Empty of action. 5 warning signs, and how to fix them.

1. Risks are really issues

Problems that have already happened are logged as risks.

Project lead, ask: “Which of these has already happened?”

2. Every risk is “medium”

Scores cluster in the middle, so nothing stands out.

Project lead, ask: “Which three risks would we act on this week?”

3. Teams own risks, not people

When “IT” or “Procurement” owns a risk, nobody does.

Project lead, ask: “Who, by name, owns this risk?”

4. No actions, no dates

Risks are described in detail, but no response has a date.

Project lead, ask: “What are we doing about it, and by when?”

5. It only wakes up for audits

The register comes alive before reviews, then goes quiet.

Project lead, ask: “What changed in the register since our last meeting?”

Make every risk actionable

  • Cause: Because of…
  • Risk: there is a risk that…
  • Effect: which would lead to…
  • Write each risk as cause, risk and effect using the pattern above.
  • Give every risk one named owner and a response with a date.
  • Review the top risks at every project meeting.
  • Close it or escalate it. Don’t let risks sit.

Download this episode as a carousel (PDF)

Back to the PM Insight Series

PM Insight Series · Episode 3

Status reports executives actually read

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.

1. Are we on track? (one line)

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.

2. What changed since the last report?

List the milestones completed and any change to scope, cost or the end date. Executives want movement, not a restatement of the plan.

3. What could hurt us?

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.

4. What do you need from me?

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.

A simple test

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.

Back to the PM Insight Series

PM Insight Series · Episode 4

PMP eligibility: how to count your project experience

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.

1. Know which path applies to you

Your educationProject experience neededPlus
High school diploma or secondary school completion60 months leading projects in the last 8 years35 contact hours of training, or an active CAPM
Associate's degree or qualifying technical or vocational credential48 months leading projects in the last 8 years35 contact hours of training, or an active CAPM
Bachelor's degree or higher36 months leading projects in the last 8 years35 contact hours of training, or an active CAPM
Bachelor's or postgraduate degree from a GAC-accredited programme24 months leading projects in the last 8 years35 contact hours of training, or an active CAPM

Always confirm the current requirements in the PMP Certification Handbook on pmi.org before you apply.

2. Count months, not projects

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.

3. Describe what you led, not what the project did

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.

4. Keep evidence ready

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.

Back to the PM Insight Series

PM Insight Series · Episode 5

Preparing for the PMP? Five study habits and an 8-week plan

5 study habits of well-prepared candidates, and a simple 8-week plan.

1. Study from the exam outline

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?”

2. Learn the mindset, not just the terms

Many questions test what a project leader should do next, not definitions.

Ask yourself: “What would a servant leader do first in this situation?”

3. Practise predictive, agile and hybrid

Questions span all three ways of working.

Ask yourself: “Can I explain when each approach fits best?”

4. Practise under exam conditions

Full, timed mock exams build stamina and pacing.

Ask yourself: “Have I completed at least two full timed mocks?”

5. Learn from every wrong answer

The real learning is in why an answer was wrong.

Ask yourself: “Do I keep an error log, and what does it tell me?”

A simple 8-week study plan

  • Weeks 1–5: Learn topic by topic, with quizzes
  • Weeks 6–7: Full mock exams and an error log
  • Week 8: Review weak areas, then rest
  • Check your eligibility before you book anything.
  • Block study time in your calendar, like any meeting.
  • Aim for steady scores of 75%+ on quality mock exams.
  • Book your exam once your mock scores are consistent.

Download this episode as a carousel (PDF)

Back to the PM Insight Series

Coming next

Topics we are writing about

  • How to qualify for the PMP® exam
  • PMP® exam changes and preparation strategy
  • Why project managers need practical delivery skills
  • How to set up a PMO that improves delivery
  • How to turn strategy into execution
  • How to measure transformation benefits
  • Fibre rollout KPIs every ISP should track
  • How to improve fibre contractor performance
  • How to reduce delays in ISP/OSP projects

Get new episodes by email

About one email a month with course dates, PM Series workshops and new Insight Series episodes.

Chat with us

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 WhatsApp

Or call +233 24 262 9852 · info@nexdilglobal.com