Post Project Assessment Framework
Turn every completed project into a blueprint for a stronger next iteration.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 99%
The Post Project Assessment Framework is a four-question review conducted after a launch, promotion, offer, or new initiative. It begins with an honest 1-to-10 outcome score, creating a shared judgment of overall performance. The reviewer then isolates the wins worth preserving, identifies lessons that should become specific changes, and examines the weight—tasks, constraints, or habits that slowed progress and should be removed. Together, these answers distinguish what to repeat, improve, and stop. The resulting record becomes a practical blueprint for the next iteration rather than a retrospective that is forgotten. Repeating the assessment across similar projects helps a business raise quality, perceived value, conversion, and operational efficiency over time.
Origin
Jasmine Star described the framework while publicly debriefing the first six-month cohort of her mastermind on The Jasmine Star Show.
Core principles
- 01Evaluate outcomes honestly before planning the next iteration.
- 02Preserve the specific elements that produced strong results.
- 03Convert shortcomings into concrete changes rather than vague regret.
- 04Remove unnecessary work that slows execution or adds little value.
- 05Repeated assessment should increase value and performance over time.
How to run it
- 1
Assess the outcome
Give the completed project an honest score from 1 to 10. Treat 10 as something you would repeat exactly and 1 as something you would not do again.
Pro tip Record the score before discussing individual successes or failures so those details do not distort your initial judgment.
Watch out Do not inflate the score to protect feelings or justify the effort already invested.
- 2
Assess the wins
Write down what worked well and what should remain in the next iteration. Use the strongest elements as a quality benchmark for the rest of the project.
Pro tip Describe each win specifically enough that another person could reproduce it.
Watch out Do not rely on memory or settle for a vague statement that something simply worked.
- 3
Assess the lessons
Identify what should change and which promising elements need major adjustments. Convert each lesson into an amendment or experiment for the next iteration.
Pro tip Pair every lesson with a concrete change, owner, or test.
Watch out Avoid framing lessons as regret without deciding what will be done differently.
- 4
Assess the weight
Find what slowed the project down, held it back, or no longer served the desired outcome. Decide what to eliminate, simplify, or stop carrying forward.
Pro tip Look for unnecessary approvals, deliverables, meetings, and responsibilities as well as obvious failures.
Watch out Do not preserve low-value work merely because it has become familiar.
In the wild
After the first cohort, Jasmine scored the experience and reviewed its wins, lessons, and weight. She chose to preserve strong participant curation, pattern recognition, and responsiveness to feedback. She also identified changes: explain the mastermind model repeatedly, reinforce how members should use the group, and create more unstructured conversation time at live events.
→ The review produced specific design changes for the second cohort, including recurring expectation-setting and longer events with informal discussion periods.
Common mistakes
Stopping at a vague lesson
Saying that something could have been better does not determine the next action. Translate the observation into a specific change for the next iteration.
Forgetting to document wins
Teams often focus only on problems and lose the practices that created success. Record repeatable wins and use them as the standard for other parts of the project.
Keeping unnecessary weight
Improvement is not only about adding tactics. Failing to remove low-value work can leave the next iteration slower and more complicated.
Is it for you?
Best for
Business owners and teams who regularly repeat launches, promotions, events, or other comparable projects.
Not ideal for
It is less useful when a project has no meaningful outcome data or will never be repeated in any comparable form.
From the transcript
“Now this is a framework that I call is the Post Project Assessment Framework.”
“It's four questions that are going to empower me to get better with every iteration and I want you to do the same.”
“And then lastly, we want to assess the weight. So what slowed us down? What held us back? What are things that we should actually…”
From the episode
Candid Reflections of My First Mastermind (What Worked and What Didn’t)