What the Didn't Happen Award Is and Why It Exists
The Didn't Happen Award is a tongue-in-cheek recognition given for a planned initiative, project, idea, or milestone that was proposed but never executed, launched, or realized. Unlike traditional awards that celebrate outcomes, this award highlights situations where effort was anticipated, resources were allocated, or plans were formalized, yet the intended result did not occur. Organizations may use it internally to acknowledge complex planning that did not translate into execution, or externally to communicate transparently about projects that were paused, canceled, or never started. It can serve as a diagnostic tool, signaling gaps in feasibility assessment, resourcing, or stakeholder alignment.
Within a mature framework, the award is rarely intended to mock; instead, it can foster candid conversations about risk, assumptions, and learning. Typically nominated by peers, managers, or cross-functional partners, candidates are evaluated on clarity of proposal, documentation quality, and lessons extracted. This structured approach turns apparent failure to act into a shared reference for future prioritization, budgeting, and decision governance.
Purpose and Intended Outcomes
Clarifying Why Plans Do Not Advance
Organizations introduce a Didn't Happen Award to surface reasons why promising ideas remain unrealized. By formally naming these outcomes, teams can distinguish between strategic pauses and outright abandonment. The award prompts documentation of constraints such as regulatory barriers, technical debt, market readiness, or budget restrictions. When handled with psychological safety, it reduces stigma around unexecuted plans and encourages candid postmortems that improve future forecasting and scoping.
Encouraging Honest Planning and Forecasting
A secondary goal is to refine how initiatives are proposed and resourced. The existence of the award nudges teams to be more rigorous in defining milestones, success metrics, and exit criteria before execution. Leadership gains visibility into the gap between intended roadmaps and delivered results, supporting better capacity planning and prioritization. Over time, this can reduce optimism bias in pipeline management and strengthen governance practices.
Eligibility and Nomination Process
Criteria for Consideration
Nominations generally target initiatives that reached a defined stage of planning or approval but did not move beyond a gate. Common criteria include documented business cases, stakeholder sign-off, allocated budget or person-hours, and a clear timeline that was not met. The award usually excludes ideas that remained at the conceptual stage without formal commitment. Governance committees may define thresholds such as minimum budget size or cross-team involvement to prevent trivial nominations.
How Nominations Are Evaluated
A standing panel, often comprising product, finance, and operations representatives, reviews nominations against predefined rubrics. Reviews consider the quality of planning, accuracy of assumptions, transparency in communications, and the depth of lessons documented. Nominees may be asked to present a brief summary outlining what was intended, where the plan stalled, and how the organization benefited from the learning. Final selections aim to highlight systemic patterns rather than individual blame.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Eligibility Threshold | Documented proposal with stakeholder sign-off and allocated resources | Internal policy or charter |
| Evaluation Body | Cross-functional governance committee | Program management office |
| Frequency | Annual or biannual cycle | Internal cadence documentation |
| Recognition Format | Certificate, internal mention, or symbolic prize | Communications guidelines |
| Data Sources | Project repositories, roadmap archives, PMO records | Enterprise PMIS |
Key Components of a Formal Program
Governance and Ownership
A dedicated sponsor or committee oversees policy, criteria, and ceremonies around the award. This body defines nomination windows, eligibility rules, and review timelines. They also ensure alignment with broader risk and compliance frameworks, so recognition does not conflict with accountability expectations. Clear ownership reduces ambiguity about who can nominate, who judges, and how decisions are communicated enterprise-wide.
Documentation and Evidence
Nominations typically require artifacts such as project charters, roadmaps, meeting notes, and status reports. These materials help the review panel reconstruct the decision journey and verify that the initiative reached a meaningful stage. Structured documentation also provides a baseline for extracting lessons and feeding them into planning templates, checklists, and stage-gate criteria.
Ceremony and Internal Communication
Organizations may host a lighthearted ceremony where recipients are presented with a symbolic item, such as a certificate or a small prop, often accompanied by a concise narrative of what was planned and why it did not proceed. Communications emphasize learning and psychological safety, highlighting how acknowledging non-achievements can strengthen future planning. The event can be integrated into all-hands meetings, town halls, or internal newsletters to normalize transparency.
Common Misconceptions and Risks
Myths Versus Realities
- The award is a penalty: In practice, it is designed to reward candid reflection and institutional learning rather than to assign blame.
- Only failed projects qualify: The award can recognize well-planned initiatives that were paused strategically due to changed priorities or new information.
- It discourages ambition: On the contrary, it encourages more rigorous scoping and clearer hypothesis setting, which can increase successful execution over time.
Potential Risks if Poorly Managed
If perceived as shaming or politicized, the award can erode trust and lead to superficial planning to avoid nomination. To mitigate this, governance should emphasize anonymity in aggregate findings, protect psychological safety, and focus on systemic improvements rather than individual fault. Clear criteria, transparent processes, and consistent application help sustain the award’s positive intent.
How to Implement or Evaluate an Existing Program
Steps to Establish a Didn't Happen Award
Start by defining the objective, scope, and eligibility thresholds with leadership and key stakeholders. Draft a simple policy outlining nomination windows, review panels, documentation requirements, and recognition formats. Pilot the program with one team or portfolio, gather feedback, refine criteria, and then expand organization-wide. Establish regular cadence for review and communication to keep the award visible and constructive.
Assessing an Existing Initiative
If your organization already has a version of this award, evaluate clarity of criteria, consistency in application, and perceived fairness. Survey participants on psychological safety and usefulness of lessons learned. Examine whether nominated initiatives reveal recurring bottlenecks, such as underinvestment in discovery or weak prioritization governance. Use findings to update processes, tools, and guidance to strengthen long-term impact.
Benefits and Organizational Value
A well-run Didn't Happen Award can improve decision discipline, surface hidden risks early, and encourage more realistic planning. Teams learn to frame hypotheses clearly, define exit conditions, and communicate status transparently. Over time, this can reduce wasteful investment in low-return initiatives and foster a culture where learning from non-action is as valued as execution. When integrated with portfolio management and stage-gate processes, the award becomes a practical mechanism for aligning capacity with strategic priorities.