This record is designed to help teams document work that was stopped, sunsetted, or did not achieve its intended results. Honest, specific answers are far more useful than polished ones. Please describe events and decisions factually and avoid attributing blame to individuals. There are no right or wrong answers, and the aim is collective learning rather than evaluation.
Project, pilot, or experiment name
Internal reference or tracking ID (if any)
Team, department, or function that led the work
Person completing this form
Other contributors to this post-mortem
How would you classify this effort?
Product, feature, or service that was sunsetted after release
Pilot or trial that did not meet its success criteria
Experiment or test that produced inconclusive or negative results
Internal initiative or process change that was discontinued
Research or discovery effort that was closed before build
Other
Please summarize what was sunsetted and how long it had been live:
Please summarize the pilot scope, participants, and duration:
Please describe the experiment design and what was being tested:
Please describe the initiative and who was affected by stopping it:
Please describe the research questions and why work stopped at this stage:
Please describe the effort in your own words:
Start date
End or wind-down date
Approximate duration in weeks
Original problem statement: what customer, user, or business problem was this work intended to address?
Original goals and intended impact, as understood when the work began
Which goal categories were attached to this effort? (Select all that apply)
Increase revenue or monetization
Reduce cost or improve efficiency
Improve customer or user retention
Improve customer or user satisfaction
Grow acquisition, adoption, or usage
Improve quality, reliability, or performance
Improve employee experience or productivity
Meet a learning or discovery objective
Explore a new market, segment, or technology
Other
Please specify the other goal category:
Were explicit, measurable success criteria defined before work started?
Please list the success criteria and the thresholds that were set:
Why were success criteria not defined, and how did that affect the work?
Was there a written brief, charter, or approved plan for this effort?
Where is that document stored?
How were scope and expectations communicated instead?
How was the decision to stop or sunset the work made?
Planned end date or pre-agreed milestone review
Stage-gate or checkpoint decision
Escalation to a steering group or leadership forum
Team recommendation accepted by a decision maker
Budget or resource withdrawal
Gradual wind-down without a single formal decision
Other
Please describe how the wind-down happened in practice:
Approximate number of people who contributed at any point
Approximate person-weeks of effort invested
Please record the approximate spend by category. The variance column is calculated automatically as actual minus planned.
Budget and Spend Summary
Cost Category | Planned Amount | Actual Amount | Variance (Actual - Planned) | ||
|---|---|---|---|---|---|
A | B | C | D | ||
1 | Internal personnel time | $60,000.00 | $74,500.00 | $14,500.00 | |
2 | External tools or services | $12,000.00 | $9,800.00 | -$2,200.00 | |
3 | Research and participant incentives | $5,000.00 | $6,300.00 | $1,300.00 | |
4 | Marketing or launch spend | $20,000.00 | $0.00 | -$20,000.00 | |
5 | $0.00 | ||||
6 | $0.00 | ||||
7 | $0.00 | ||||
8 | $0.00 | ||||
9 | $0.00 | ||||
10 | $0.00 |
Total estimated cost of the effort (including internal time, if known)
What is the final status of this effort?
Fully sunsetted and removed from service
Paused with intent to revisit later
Paused indefinitely with no current plan to resume
Partially delivered, remaining scope cancelled
Merged into another project or roadmap item
Converted into a smaller ongoing maintenance mode
What conditions would trigger a revisit, and who would decide?
Which project or roadmap item absorbed this work?
What is being maintained, by whom, and at what ongoing cost?
Are there any users, customers, or internal teams still affected by the wind-down?
Who is affected, what support or transition was offered, and what remains outstanding?
Overall, how closely did the final outcome match the original goals?
In one or two sentences, what happened, in plain language?
Most projects and experiments rest on assumptions about users, technology, operations, or the market. This section compares what was assumed with what was observed, so that future teams can tell which beliefs held up and which did not.
Please list the main hypotheses or assumptions the work was built on, and what actually happened for each.
Hypothesis and Outcome Comparison
Hypothesis or Assumption | Assumption Type | Evidence Expected | Actual Result Observed | Deviation (1 = matched, 5 = opposite) | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | Users want a self-serve verification step instead of a manual review | User need | Higher completion rate within 7 days | Completion improved by 3 percentage points, well below the 15 point target | ||
2 | The existing platform can support the new workflow without rework | Technical feasibility | Delivery within the planned sprint capacity | Required an unplanned data-layer change that consumed six additional weeks | ||
3 | Support volume would fall once the flow was simplified | Operational impact | Fewer related support contacts per week | Contact volume stayed flat and shifted to a different topic | ||
4 | ||||||
5 | ||||||
6 | ||||||
7 | ||||||
8 | ||||||
9 | ||||||
10 |
Which sources of evidence were used to judge outcomes? (Select all that apply)
Quantitative product or usage analytics
Financial or commercial data
User or customer interviews
Surveys or questionnaires
Usability or lab testing
Operational or support metrics
Technical benchmarks or load tests
Team observation and anecdote only
External research, benchmarks, or published studies
No systematic evidence was collected
What did the team observe, and how reliable do you consider those observations?
Why was systematic evidence not collected, and what could have been measured at low cost?
Did the work produce statistically or practically meaningful results on any measure?
Which measures moved, by how much, and how confident are you in the result?
What prevented meaningful measurement (for example sample size, duration, instrumentation, or changing conditions)?
Was any hypothesis strongly disproven?
Which hypothesis was disproven, and what evidence disproved it? Why is this finding worth remembering?
Did any unexpected positive result appear, even though the effort overall did not succeed?
Please describe the unexpected positive result and whether it could be pursued elsewhere:
What best explains the gap between expected and actual outcomes?
The underlying user or customer need was smaller or different than assumed
The solution was not a good fit for the problem
The solution was directionally right but under-resourced or too slow
Technical constraints or dependencies blocked delivery quality
External or market conditions changed during the work
Success criteria were unrealistic or poorly chosen
The effort was stopped before it had a fair chance to prove itself
Other
How much more time or support would have been needed, and was that realistic?
Please explain the main reason for the gap:
Please rate how each area performed relative to expectations.
Far below expectations | Below expectations | About as expected | Above expectations | Far above expectations | |
|---|---|---|---|---|---|
User or customer demand for the solution | |||||
Quality of the delivered solution | |||||
Speed of delivery relative to plan | |||||
Accuracy of the original forecasts or estimates | |||||
Quality of the evidence gathered during the work | |||||
Alignment between stakeholders during the work |
How many iterations, versions, or test cycles were completed?
Approximate number of users, customers, or participants reached during the effort
If you could re-run the work with the knowledge you have now, what would the revised hypothesis be?
This section looks for the underlying conditions that shaped the outcome, not just the final trigger. Please consider multiple contributing factors, including process, information, resourcing, and decision-making. Focus on systems and circumstances rather than individual performance.
Which categories of obstacles were encountered? (Select all that apply)
Unclear or shifting goals and scope
Insufficient time or unrealistic schedule
Insufficient staffing or skills
Budget or funding constraints
Technical complexity or integration difficulty
Data quality, availability, or instrumentation gaps
Dependencies on other teams or external parties
Low user or stakeholder engagement
Competing internal priorities
Slow or unclear decision making
Changes in market, customer, or business conditions
Tooling or infrastructure limitations
Communication or handover gaps
Other
Please describe the other obstacle category:
Obstacle Detail and Impact
Obstacle or Blocker | Severity (1 = minor, 5 = critical) | Foreseeable in Advance? | Response or Mitigation Attempted | Response Effectiveness (1 = none, 5 = fully resolved) | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | Required data fields were not captured by the existing platform | Added a temporary manual collection step and raised a platform change request | ||||
2 | Two dependent teams had conflicting delivery windows | Escalated to a joint planning session and re-sequenced the work | ||||
3 | Target user segment proved harder to recruit than expected | Expanded recruitment channels and extended the test window by two weeks | ||||
4 | ||||||
5 | ||||||
6 | ||||||
7 | ||||||
8 | ||||||
9 | ||||||
10 |
What was the single most significant root cause of the outcome?
Problem-solution mismatch
Insufficient evidence before committing resources
Execution or delivery shortfall
Resourcing or prioritization shortfall
External conditions outside the team's control
Goal or success criteria design flaw
Timing, being too early or too late
Other
Please describe the root cause in your own words:
Were there early warning signs that the work was not on track?
What were the warning signs, when did they first appear, and why were they not acted on sooner?
Did the team ever recommend stopping or changing direction earlier than it actually did?
What was recommended, when, and what decision was made in response?
Were factors outside the team's control a major contributor?
Which external factors contributed? (Select all that apply)
Shifts in business strategy or leadership direction
Budget or hiring changes elsewhere in the organization
Vendor, supplier, or partner changes
Customer or market behavior changes
Technology or platform changes outside the team
Regulatory or policy environment changes
Other
Please indicate how much each factor contributed to the outcome.
Not a contributing factor | Minor contribution | Moderate contribution | Major contribution | Decisive contribution | |
|---|---|---|---|---|---|
Clarity of the original problem definition | |||||
Realism of the original plan and estimates | |||||
Adequacy of staffing and skills | |||||
Quality of cross-team collaboration | |||||
Speed and clarity of decision making | |||||
Quality of user research and feedback loops | |||||
Stability of requirements during the work | |||||
Suitability of the chosen technology or approach |
Which decisions, if any, would the team revisit with hindsight? (Select all that apply)
The decision to start the work at all
The chosen solution or approach
The size of the initial scope
The success criteria and metrics selected
The timeline and sequencing of milestones
The people or skills assigned
The decision to continue past an early checkpoint
The decision to stop when we did
None, the decisions were reasonable at the time
What would the team do differently if a similar effort were started tomorrow?
What should future teams explicitly avoid doing?
Is there anything about this outcome that remains unclear or unresolved?
Even when an effort does not reach its goal, it usually produces something of value. Please identify outputs that another team could reuse, and record the practical lessons that should shape future work.
Which types of assets were produced? (Select all that apply)
Source code, scripts, or prototypes
Design files, mockups, or interface patterns
Research findings, interview notes, or reports
Datasets, dashboards, or measurement setups
Process templates, checklists, or playbooks
Training or enablement materials
Vendor evaluations or tool comparisons
Documentation of technical constraints or architecture
Cost, effort, or sizing estimates
None of the above
Was anything else produced that could be useful to others?
Reusable Asset Register
Asset Name | Asset Type | Location or Link | Custodian or Owner | Reuse Potential | Retention Agreed? | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | Verification flow prototype | Prototype | Shared drive/Prototypes/Verification v3 | Design Systems Team | |||
2 | User interview synthesis on trust signals | Research report | Research repository / 2027 / Trust Signals | Research Guild | |||
3 | Instrumentation checklist for onboarding events | Template | Team wiki/Playbooks/Measurement | Data Enablement | |||
4 | |||||||
5 | |||||||
6 | |||||||
7 | |||||||
8 | |||||||
9 | |||||||
10 |
Do any assets carry handling, confidentiality, or usage restrictions?
Please describe the restrictions and who can grant access:
Was any data collected that should be deleted or anonymized after the effort ends?
What data is affected, who is responsible, and by when should it be handled?
Which kinds of insight did this effort generate? (Select all that apply)
Better understanding of a user or customer need
Evidence that a need is smaller than expected
Technical knowledge or constraint discovery
Improved estimation or planning reference points
A validated method or working practice
A method or practice shown not to work here
New internal relationships or collaboration patterns
Insight into our own decision-making habits
None that we can currently articulate
Please list the top three lessons learned from this effort, in order of importance.
What is now known that was not known before this work began?
Which existing practices, standards, or templates should be updated based on these findings?
Please rank these outcomes of the effort from most valuable to least valuable.
Reusable technical or design assets | |
Documented evidence about the problem space | |
Improved estimation and planning references | |
Team skills and experience developed | |
Relationships and cross-team understanding |
Could any part of this work be revived later under different conditions?
What conditions would need to change, and what would a sensible next step look like?
Overall learning value of this effort to the organization
How complete and reusable is the documentation produced?
Learning only helps if it reaches the people who can use it. Please agree who will share what, with whom, through which channels, and by when. Keep the plan realistic and proportionate to the value of the insight.
Primary audience for these findings
Secondary or wider audience, if any
Which sharing channels will be used? (Select all that apply)
Written post-mortem report or summary document
Team or guild presentation session
Recorded walkthrough or briefing video
Internal knowledge base or wiki article
Lessons-learned or retrospective forum
Newsletter, digest, or internal announcement
Workshop or training session
Handover meeting with a specific team
Update to onboarding or reference material
Other
Please specify the other channel:
Dissemination Activities and Ownership
Activity or Deliverable | Owner | Format | Target Audience | Target Completion Date | Scheduled? | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | Publish post-mortem summary in the knowledge base | Jordan Lee | Written article | All product teams | 11/20/2027 | ||
2 | Run a 45-minute lessons-learned session | Priya N. | Live session | Engineering and Design leads | 12/4/2027 | ||
3 | Add findings to the measurement playbook | Data Enablement | Playbook update | Delivery teams | 12/15/2027 | ||
4 | |||||||
5 | |||||||
6 | |||||||
7 | |||||||
8 | |||||||
9 | |||||||
10 |
Will a summary of this post-mortem be published for a broad internal audience?
What level of detail will the published summary contain?
Full detail, including figures and names of teams involved
Key findings and recommendations only
Short headline summary with a link to the full record
Not yet decided
Why will it not be published broadly, and who will still have access?
Will any part of these findings be shared outside the organization?
What will be shared, with whom, and who should review it before release?
How long should the full record be retained for future reference?
Until the end of the current planning cycle
About one year
About two to three years
Long term, as a permanent reference
Not sure, please advise
Who should confirm the retention approach?
Where will the full record and supporting assets be stored?
Document owner or custodian after this form is submitted
Should this record be linked from any planning, risk, or strategy documents?
Which documents should reference it, and who will add the links?
Would the team be willing to answer questions from other teams about these findings?
Who should be contacted, and what is the best way to reach them?
Is there anything that should not be repeated outside this record, and why?
Reviewer or approver of this post-mortem (name and role)
Date of review
I confirm that this record is accurate to the best of my knowledge and is written for learning purposes rather than individual evaluation.
Signature of the person completing this form
Any final comments, acknowledgements, or thanks you would like to record
Analysis for Project Post-Mortem & Lessons Learned Form (Sunsetted Projects, Failed Pilots, Unsuccessful Experiments)
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
This post-mortem form is a well-structured, comprehensive instrument designed to capture organizational learning from sunsetted projects, failed pilots, and unsuccessful experiments. It is organized into five clearly delineated sections that follow a logical narrative arc: understanding what was attempted and why, comparing assumptions against reality, diagnosing root causes, identifying reusable value, and planning knowledge dissemination. The form's design reflects a strong emphasis on psychological safety — the introductory paragraph explicitly encourages honest, blame-free reporting and frames the exercise as collective learning rather than individual evaluation. This tone-setting is a significant strength, as it is likely to improve the candor and completeness of responses. The use of varied input types — including tables with calculated fields, matrix ratings, ranking exercises, conditional follow-ups, and open-ended narratives — creates a rich, multi-dimensional record while keeping each individual question focused and manageable. The form also demonstrates thoughtful attention to practical concerns such as data handling restrictions, retention periods, and storage locations, which are often overlooked in learning-oriented documents.
This section establishes the factual foundation of the record. It captures who did what, when, why, and at what cost — providing the essential context that future readers will need to interpret the lessons that follow.
This field serves as the primary identifier for the record. A clear, recognizable name ensures that the post-mortem can be found, referenced, and linked from other documents. The placeholder example is helpful and encourages respondents to use a descriptive, real-world label rather than an internal code.
This optional field supports cross-referencing with existing project management or tracking systems. Making it optional is appropriate since not all efforts will have an assigned identifier, particularly informal experiments or early-stage research.
Identifying the owning team is operationally important for routing follow-up questions, understanding the organizational context, and connecting the record to broader team-level learning. The placeholder example is clear and encourages a functional label rather than individual names.
This field establishes authorship and a point of contact for clarification. In a learning-oriented document, knowing who wrote the record helps future readers assess the perspective and level of firsthand knowledge behind the narrative.
Recognizing multiple contributors is valuable for collaborative post-mortems and helps ensure that diverse perspectives are acknowledged. This optional field encourages inclusivity without adding friction.
This classification question is one of the form's strongest design choices. By offering six distinct categories — from sunsetted products to closed research efforts — the form accommodates a wide range of project outcomes. The conditional follow-ups are particularly effective: each option triggers a tailored open-ended prompt that elicits the most relevant detail for that type of effort. This reduces cognitive load on the respondent while ensuring that the right information is captured.
These temporal fields establish the timeline of the effort. The end date is marked as mandatory, which is sensible since the entire premise of the form depends on knowing when the work concluded. The duration field allows decimals and is optional, which is appropriate for approximate figures.
This is a foundational question. Without a clear articulation of the original problem, the rest of the analysis loses its reference point. The placeholder example is excellent — it is specific, concrete, and demonstrates the level of detail expected.
Capturing goals as originally understood (rather than as retrospectively reframed) is critical for honest post-mortem analysis. The placeholder example with quantified targets sets a strong expectation for specificity.
This multiple-choice question with ten options provides a useful taxonomy for categorizing the type of impact the work was intended to achieve. The follow-up for the "Other" option ensures that unanticipated categories are captured without constraining the respondent.
This yes/no question with conditional follow-ups is well designed. Whether success criteria were defined or not, the form prompts for relevant detail — either the criteria themselves or the reasons for their absence and the resulting impact. This dual-path approach ensures that the absence of criteria is itself documented as a learning point.
This question captures the level of formalization behind the effort. The conditional follow-ups ask for either the document location or how scope was communicated informally, which is useful for understanding governance practices.
The seven options cover a realistic spectrum of decision-making processes, from planned milestone reviews to gradual wind-downs. The follow-up for the "Other" category is appropriate. This question helps future teams understand what governance mechanisms were in place.
These fields capture the human investment in the effort. The use of approximate figures is appropriate for a retrospective record where exact data may not be readily available.
This table is a particularly well-designed element. The inclusion of a calculated variance column (actual minus planned) provides immediate analytical value without requiring manual computation. The pre-populated rows demonstrate expected categories and encourage respondents to think about different cost types. The currency input type ensures consistent formatting.
This summary field provides a single figure for quick reference and comparison across efforts. It complements the detailed table above.
The six status options are comprehensive and mutually distinct. The conditional follow-ups are well-targeted: paused efforts are asked about revisit triggers, merged efforts are asked about the absorbing project, and maintenance-mode efforts are asked about ongoing costs. This ensures that the disposition of the work is clearly documented.
This question addresses an important operational concern — the downstream impact of stopping work. The follow-up prompts for affected parties, transition support, and outstanding items, which helps ensure that no loose ends are left undocumented.
This 5-point rating provides a quick quantitative summary of outcome alignment. It serves as a useful high-level indicator that can be compared across multiple post-mortems.
This concluding field in Section 1 is excellent for creating an executive summary. By constraining it to one or two sentences and asking for plain language, the form encourages clarity and accessibility for readers who may not have deep context.
This section is the analytical heart of the form. It systematically compares what was assumed with what was observed, creating a structured record of validated and invalidated beliefs.
This open-ended field is the primary narrative vehicle for hypothesis analysis. The placeholder example effectively demonstrates the expected format — paired assumption and observation. This is essential for creating actionable learning records.
This table is one of the form's strongest elements. The five columns — hypothesis, assumption type, expected evidence, actual result, and deviation rating — create a rigorous comparison framework. The deviation rating scale (1 = matched, 5 = opposite) is intuitive and enables quick scanning of where assumptions diverged most from reality. The pre-populated rows demonstrate the expected level of detail.
This multiple-choice question with ten options covers a comprehensive range of evidence types. The follow-ups for anecdotal-only evidence and no systematic evidence are particularly thoughtful — they prompt reflection on what could have been measured at low cost, turning a gap into a learning opportunity.
This question distinguishes between statistical and practical significance, which is a nuanced and useful distinction. The conditional follow-ups capture either the results and confidence levels or the barriers to meaningful measurement.
This question targets one of the most valuable outputs of any experiment — a clearly disproven hypothesis. The follow-up asks not just what was disproven and why, but why the finding is worth remembering, which encourages forward-looking thinking.
Even in unsuccessful efforts, unexpected positives can emerge. This question ensures those are captured and considered for pursuit elsewhere. It reflects a balanced, growth-oriented perspective.
The eight options provide a useful diagnostic taxonomy. The follow-ups for "stopped too early" and "Other" allow for nuanced explanations. This question helps categorize the nature of the shortfall for pattern analysis across multiple post-mortems.
This matrix rating across six sub-questions provides a structured, comparable assessment of performance across key dimensions. The five-point scale from "Far below" to "Far above" expectations is clear and balanced.
These numeric fields capture the scale and iteration count of the effort, providing useful context for interpreting the results.
This forward-looking question is excellent for crystallizing learning into actionable form. It encourages respondents to synthesize their insights into a refined understanding.
This section moves beyond surface-level triggers to explore underlying systemic conditions. The introductory paragraph wisely directs respondents to consider multiple contributing factors and to focus on systems rather than individuals.
The fourteen obstacle categories are comprehensive and cover technical, organizational, resource, and external factors. The follow-up for "Other" ensures completeness. This question provides a quick taxonomy for pattern analysis.
This table is well-designed with five columns covering the obstacle, severity, foreseeability, mitigation attempted, and response effectiveness. The severity and effectiveness rating scales are clear and intuitive. The foreseeability column (yes/no) is particularly valuable for distinguishing between genuinely unforeseeable issues and those that could have been anticipated.
Forcing a single primary root cause is a useful analytical discipline. The eight options cover the most common categories. The follow-up for "Other" allows for nuanced explanations. This question helps identify the dominant factor for high-level pattern recognition.
This question targets one of the most actionable aspects of post-mortem analysis — recognizing and acting on early signals. The follow-up asks what the signs were, when they appeared, and why they were not acted on, which creates a complete narrative of the warning-sign-to-action gap.
This question captures whether the team's own judgment was aligned with the eventual outcome and whether decision-making processes supported timely course correction.
The conditional follow-up with six external factor categories helps distinguish between internal and external causes, which is important for fair and accurate analysis.
This matrix with eight sub-questions and a five-point contribution scale provides a nuanced, multi-factor assessment. It complements the single root-cause question by capturing the full distribution of contributing factors.
This multiple-choice question with nine options (including "None") is well-designed for capturing retrospective reflection on specific decision points. It encourages honest assessment without implying that past decisions were unreasonable.
This is one of the most practically valuable questions in the entire form. It directly translates retrospective analysis into forward-looking guidance. The mandatory status is appropriate given its central role in the learning objective.
This question complements the previous one by capturing negative lessons — what not to do. It is particularly useful for creating concise, memorable guidance.
This closing question acknowledges that not all questions will be answered and provides a space for documenting open issues. This is honest and practical.
This section ensures that the value produced by the effort is not lost, even though the primary goal was not achieved. It is a strong expression of the form's learning-oriented philosophy.
The ten asset categories are comprehensive, covering technical, design, research, process, and documentation outputs. The follow-up for "None of the above" captures any other useful outputs.
This table is well-structured with six columns covering asset name, type, location, custodian, reuse potential (star rating), and retention agreement (checkbox). The inclusion of a custodian field is particularly practical — it ensures that assets have a clear owner. The reuse potential rating helps prioritize which assets are most worth preserving.
This question addresses a practical concern that is often overlooked. The follow-up asks for the nature of restrictions and who can grant access, which supports responsible asset management.
This question reflects good data stewardship practices. The follow-up captures what data is affected, who is responsible, and by when — creating an actionable data handling plan.
The nine insight categories cover a useful range from user understanding to decision-making habits. The "None that we can currently articulate" option is a thoughtful inclusion that acknowledges that insights may not always be immediately clear.
This question is the crystallization point of the entire form. By asking for exactly three lessons in priority order, it forces distillation and prioritization. The placeholder format encourages structured responses.
This question captures the net knowledge gain from the effort, which is the core value proposition of the post-mortem process.
This question connects learning to organizational process improvement, ensuring that insights lead to concrete changes in how work is done.
This ranking exercise with five items forces respondents to evaluate the relative value of different outcomes. It is a useful prioritization tool that complements the open-ended fields.
This question captures the possibility that the work might have future value under different conditions. The follow-up asks for the conditions and next steps, which is practical and forward-looking.
These two rating fields (digit rating and star rating) provide quick quantitative summaries of the effort's learning value and the quality of the documentation produced. They are useful for tracking the effectiveness of the post-mortem process over time.
This section ensures that learning reaches the people who can use it. The introductory paragraph wisely advises that the plan should be realistic and proportionate to the value of the insight.
Identifying the primary audience is essential for tailoring the dissemination approach. The placeholder example is helpful and encourages specificity.
This optional field captures broader dissemination opportunities without adding mandatory burden.
The ten channel options cover a comprehensive range from written reports to workshops and handover meetings. The follow-up for "Other" ensures flexibility.
This table is excellent for creating an actionable dissemination plan. The six columns — activity, owner, format, target audience, target date, and scheduled status — create a complete tracking framework. The checkbox column for scheduling status adds practical accountability.
This question addresses the tension between transparency and sensitivity. The conditional follow-ups capture either the level of detail for published summaries or the reasons for limited distribution — both of which are important for governance.
This question addresses external sharing considerations. The follow-up asks what will be shared, with whom, and who should review it, which supports responsible disclosure practices.
The five retention options cover a realistic range. The follow-up for "Not sure" asks who should confirm the approach, which is a practical way to ensure the question gets resolved.
This field ensures that the record has a known, accessible location. The placeholder example provides a clear directory structure convention.
Assigning a custodian ensures long-term maintainability of the record and provides a point of contact for future inquiries.
This question promotes integration of learning into broader organizational processes. The follow-up asks for specific documents and responsible parties.
This question encourages ongoing knowledge sharing beyond the written record. The follow-up captures contact details and preferred communication channels.
This question provides a space for documenting sensitive information that should remain within the record. It is a thoughtful addition for responsible information management.
These fields capture the review and approval process, adding a layer of accountability and quality assurance to the record.
This checkbox serves as a declaration of accuracy and reinforces the learning-oriented purpose of the record. It is a simple but effective way to formalize the respondent's commitment to honest reporting.
The signature field adds formality and accountability to the record. It complements the confirmation checkbox and the reviewer fields.
This closing field provides space for positive recognition and personal reflections, which reinforces the form's constructive, learning-oriented tone.
While the form is comprehensive and well-designed, a few observations may be worth considering. The form is lengthy — spanning five sections with numerous questions, tables, and conditional follow-ups. For some respondents, particularly those completing the form under time pressure, this length may create completion fatigue. Consider whether a shorter summary version could be offered for less complex efforts, with the full form reserved for larger or more significant projects. Additionally, the form relies heavily on open-ended text fields; while this captures rich narrative detail, it may produce inconsistent levels of detail across respondents. The pre-populated table rows and placeholder examples help mitigate this, but additional guidance on expected response length could further improve consistency. Finally, the form does not currently include any automated scoring or aggregation features; if multiple post-mortems are collected over time, a mechanism for cross-form pattern analysis could significantly amplify the organizational learning value.
Mandatory Question Analysis for Project Post-Mortem & Lessons Learned Form (Sunsetted Projects, Failed Pilots, Unsuccessful Experiments)
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
The following questions are currently set as mandatory in the form. Each is analyzed below with a context-specific explanation of how requiring the field may support data completeness, operational processing, or record-keeping in the context of a post-mortem and lessons-learned exercise.
Question: Project, pilot, or experiment name
Recommendation: Requiring this field ensures that every record has a clear, identifiable label, which is essential for filing, searching, and cross-referencing post-mortem records over time. Without a project name, the record would be difficult to locate or associate with specific efforts. This is a foundational identifier for the form's purpose.
Question: Team, department, or function that led the work
Recommendation: Identifying the owning team supports organizational accountability and helps route follow-up inquiries to the right group. It also enables pattern analysis across teams — for example, identifying whether certain types of challenges recur within specific functions. Requiring this field ensures that every record is properly attributed.
Question: Person completing this form
Recommendation: Requiring this field establishes authorship and provides a point of contact for clarification. In a learning-oriented record, knowing who authored the document helps future readers assess the perspective and firsthand knowledge behind the narrative. It also supports record-keeping by ensuring every submission has a named contributor.
Question: How would you classify this effort?
Recommendation: This classification is central to the form's structure — it determines which conditional follow-up questions are presented and helps categorize the record for future analysis. Requiring this field ensures that every post-mortem is properly typed, which supports consistent data collection and enables meaningful comparisons across different types of efforts.
Question: End or wind-down date
Recommendation: The entire premise of the form depends on documenting efforts that have concluded. Requiring the end date ensures that the record is anchored to a specific point in time, which supports timeline analysis, retention planning, and contextual understanding of when the learning was captured. Whether this date reflects a formal closure or a gradual wind-down may depend on the nature of the effort.
Question: Original problem statement: what customer, user, or business problem was this work intended to address?
Recommendation: Without a clear problem statement, the rest of the analysis lacks its reference point. Requiring this field ensures that every record begins with a shared understanding of what the work was trying to solve, which is essential for evaluating whether the outcomes matched the intent. This is a core element of the form's learning objective.
Question: Original goals and intended impact, as understood when the work began
Recommendation: Capturing goals as originally stated — rather than as retrospectively reframed — is critical for honest outcome assessment. Requiring this field ensures that the comparison between intent and result is grounded in the original expectations, which supports accurate and fair analysis. The necessity of this field is closely tied to the form's purpose of capturing what was learned.
Question: Were explicit, measurable success criteria defined before work started?
Recommendation: Whether success criteria were defined or not is itself a valuable learning data point. Requiring this field ensures that every record documents the level of upfront clarity, which supports analysis of how planning practices correlate with outcomes. The conditional follow-ups capture relevant detail regardless of the answer, making this a high-value mandatory field.
Question: Are there any users, customers, or internal teams still affected by the wind-down?
Recommendation: This question addresses downstream operational impact, which is important for responsible closure practices. Requiring it ensures that no record is filed without considering whether anyone is still affected, which supports transition planning and stakeholder communication. The necessity of this field may vary depending on the scale and nature of the effort, but requiring it as a default prompt ensures the consideration is not overlooked.
Question: Please list the main hypotheses or assumptions the work was built on, and what actually happened for each
Recommendation: This field is the primary vehicle for hypothesis-outcome analysis, which is a core objective of the form. Requiring it ensures that every record includes at least a basic comparison of assumptions versus reality, which is the foundation of organizational learning from unsuccessful efforts. Without this field, the record would lack its most analytically valuable content.
Question: Was any hypothesis strongly disproven?
Recommendation: A clearly disproven hypothesis is one of the most valuable outputs of any experiment or pilot. Requiring this field ensures that every record explicitly addresses whether such a finding exists, which supports the creation of a searchable knowledge base of validated and invalidated beliefs. The conditional follow-up captures the evidence and rationale, making this a high-value mandatory prompt.
Question: What was the single most significant root cause of the outcome?
Recommendation: Identifying the primary root cause is essential for actionable learning. Requiring this field ensures that every record includes a clear diagnostic conclusion, which supports pattern analysis across multiple post-mortems and helps future teams avoid similar pitfalls. The necessity of selecting a single cause may depend on the complexity of the effort, but the form's follow-up for the "Other" option allows for nuanced explanations.
Question: Were there early warning signs that the work was not on track?
Recommendation: Recognizing and acting on early signals is one of the most practically valuable aspects of post-mortem analysis. Requiring this field ensures that every record addresses whether warning signs existed, which supports the development of better monitoring and escalation practices. Whether this question is always applicable may depend on the nature of the effort, but requiring it as a default ensures the consideration is documented.
Question: What would the team do differently if a similar effort were started tomorrow?
Recommendation: This field directly translates retrospective analysis into forward-looking guidance, which is the ultimate purpose of the post-mortem process. Requiring it ensures that every record includes actionable recommendations, which supports the practical application of lessons learned. This is arguably the single most important output of the form.
Question: Do any assets carry handling, confidentiality, or usage restrictions?
Recommendation: Documenting handling restrictions supports responsible asset management and helps prevent inappropriate reuse of sensitive materials. Requiring this field ensures that every record includes a consideration of data handling concerns, which supports good stewardship practices. Whether specific restrictions exist will vary by effort, but the question itself should always be considered.
Question: Please list the top three lessons learned from this effort, in order of importance
Recommendation: This field is the crystallization point of the entire form — it distills the analysis into concise, prioritized takeaways. Requiring it ensures that every record includes at least three actionable lessons, which supports the creation of a practical, searchable knowledge base. The constraint to exactly three items encourages focus and prioritization.
Question: Primary audience for these findings
Recommendation: Identifying the primary audience is essential for tailoring the dissemination approach and ensuring that learning reaches the right people. Requiring this field ensures that every record includes a clear target audience, which supports effective knowledge-sharing planning. Without this field, the dissemination section would lack direction.
Question: Will a summary of this post-mortem be published for a broad internal audience?
Recommendation: This question addresses the transparency and accessibility of the learning record. Requiring it ensures that every record documents a decision about broad publication, which supports governance and consistency in how post-mortem findings are shared. The conditional follow-ups capture either the level of detail or the reasons for limited distribution.
Question: Where will the full record and supporting assets be stored?
Recommendation: Ensuring that the record has a known, accessible location is essential for long-term usability. Requiring this field supports record-keeping by preventing records from being filed without a clear storage location, which could lead to lost or inaccessible learning materials. This is a practical, operational requirement for effective knowledge management.
Question: I confirm that this record is accurate to the best of my knowledge and is written for learning purposes rather than individual evaluation
Recommendation: This confirmation checkbox serves as a declaration of accuracy and reinforces the form's learning-oriented purpose. Requiring it ensures that every submission includes an explicit acknowledgment of the record's intent, which supports a culture of honest, constructive reporting. It also provides a simple form of accountability for the completeness and accuracy of the submission.
The form currently designates approximately 20 questions as mandatory across its five sections. This is a relatively high proportion given the overall length and complexity of the form, but it is broadly consistent with the form's purpose as a structured learning record where completeness is important for the value of the output.
Balancing Data Collection Depth Against Completion Rates: The mandatory fields are distributed across all five sections, which ensures that no section is left entirely blank. However, the total number of required fields — combined with the form's overall length — may create completion fatigue, particularly for respondents documenting smaller or less complex efforts. Consider whether a tiered approach could be implemented: for example, a shorter mandatory core set for simple efforts, with additional fields required only for larger or more significant projects. This would help maintain data quality for important records while reducing friction for simpler ones.
Conditional Logic: The form already makes effective use of conditional follow-ups (options follow-up, yes/no follow-up), which is a strong design choice. Consider whether any currently mandatory fields could benefit from conditional logic — for example, the question about early warning signs might be made optional for efforts that were planned to end at a specific date and did so as expected. This would reduce unnecessary burden while preserving completeness where it matters most.
Best Practices for Mandatory Field Selection and Placement: The mandatory fields in this form are generally well-chosen — they focus on core identification, key analytical conclusions, and essential governance elements (storage location, confirmation). The placement is logical, with mandatory fields appearing at natural decision points within each section. One general observation is that the mandatory fields in Section 3 (Root-Cause Analysis) and Section 4 (Reusable Assets) are particularly important for the form's learning objective, as they ensure that actionable conclusions are captured. Maintaining the mandatory status of these fields is advisable.
Overarching Observations: The distribution of mandatory fields is relatively balanced across sections, with Sections 1 and 5 having the most required fields. This is appropriate given that Section 1 establishes the foundational context and Section 5 handles governance and dissemination. However, the cumulative effect of 20 mandatory fields on a form of this length should be monitored through completion rate data. If drop-off rates are high, consider whether any fields — such as the confirmation checkbox or the early warning signs question — could be made optional while still capturing the essential learning. Regular review of mandatory field necessity, informed by respondent feedback and completion analytics, will help ensure that the form remains both comprehensive and practical.
To configure an element, select it on the form.