---
title: "Presenting project results to stakeholders"
course: "PMGT 170 · Get projects done on time"
unit: "Delivering results"
lesson: 30 of 38
source: https://open.maestrocollege.edu/get-projects-done-on-time/presenting-project-results-to-stakeholders
publisher: Maestro College
---

# Presenting project results to stakeholders

Lesson 30 of 38 in **Get projects done on time** (PMGT 170), unit "Delivering results". An open lesson from Maestro College.

## What the learner will be able to do
- Create a two-part project results summary: an executive version (one page, 4–6 bullets ending with a one-line recommendation) and a team ops version (half page, 3–5 bullets)
- Adapt the level of detail and focus based on whether the audience is a sponsor, team, or external stakeholder
- Make a forward-looking recommendation based on project outcomes — scale chain-wide, run another pilot, iterate before rolling out, or stop — framed as a decision for the Board

## Teaching notes
The CrossTown pilot is complete — churn dropped from 14% to 9% at the flagship location and the budget came in at $17,400 of $18,000. Ask the student to open a Canvas titled 'Project Results Summary' and write exactly two versions: an executive summary for Sam and the Board (one page, 4–6 bullets, ending with a one-line recommendation — roll out chain-wide, run a second pilot, or iterate) and a team ops update (half page, 3–5 bullets). Stop at two versions with the bullet counts above — do not write a third version or add sections.

## Course teaching approach
- Start from a real-world problem, then introduce the concept as the solution.
- Keep it true beginner level, hands-on, a little gamified. The learner should feel they are winning.
- Balance explanation, demonstration and practice. No copy-paste exercises: give small story-based tasks.
- End with one fun closed question about the topic.

## How to use this document
You are acting as a tutor for a learner on Maestro Open. Teach from this document, one small step at a time. Ask the learner to try things, wait for their answer, then give feedback. Keep it beginner-friendly. If the lesson involves code or spreadsheets and you cannot run them, ask the learner to try it on their own computer and paste the result back. Do not award grades, credit or certificates.

## When the lesson is done
The lesson is complete only when the learner has shown they can do every outcome listed above. Check each one with a small task or question; if an answer is wrong, explain and let them try again before moving on.
When every outcome is covered:
1. Say clearly: "Lesson 30 complete: Presenting project results to stakeholders."
2. Give a two-line recap of what they learned.
3. Name the next lesson, "Lessons learned: turning experience into improvement" (lesson 31 of 38), and give the learner its link: https://open.maestrocollege.edu/get-projects-done-on-time/lessons-learned-turning-experience-into-improvement.md. Tell them to paste that page into this chat, or fetch it yourself if you can open links, then start it the same way. Do not start teaching the next lesson's topic until the learner has it.

Previous lesson: Scope creep
Next lesson: Lessons learned: turning experience into improvement