Eradicating the "Hero" Culture: The Real Work of Crossing the Finish Line
"Boring" is a Strategic Asset
Eradicating the “Hero” Culture: The Real Work of Crossing the Finish Line
We often think of IT heroes as the people who save the day. In reality, a reliance on “heroics” is the clearest sign that your organization is failing to manage toward completion. As part of my ongoing series Why the “Finish Line” Mindset Matters Now More Than Ever, this post explores why we must move from individual heroics to systemic discipline.
In many organizations I’ve joined, the IT function was celebrated for its “fire drills” and “heroic” last-minute saves. This culture normalizes crisis, mistaking the adrenaline of a last-minute save for operational excellence, because it lacks the discipline to succeed without a hero. This is unsustainable, unscalable, and fundamentally incompatible with strategic execution.
To move from reactive firefighting to disciplined, finish-line execution, we must instill rigor across two critical domains: Project Delivery and IT Operations.
Here is a prescriptive leadership playbook for moving from heroics to process:
Domain 1: Instilling Project Delivery Discipline
We must stop relying on individual project managers to “make it happen” and start implementing systemic standards.
Establish Project Standards & Methodology:
How: Implement a standardized Project Management Office (PMO) framework (e.g., PMBOK, Prince2, or a customized Agile hybrid). Every project must follow the same phases: Initiate, Plan, Execute, Monitor, Close.
Why it Ends Heroics: It removes ambiguity about who does what, when, and how. Success is determined by adherence to the process, not individual brilliance.
Leadership Insight: The size of your organization may not warrant or afford a dedicated PMO function in the org chart, but the discipline can still be implemented and a champion named to oversee it.
2. Enforce Rigorous Stage-Gate Governance:
How: Define clear “Go/No-Go” criteria for moving between project phases. A project cannot move from “Plan” to “Execute” without an approved budget, signed-off requirements, and a signed Project Charter. A project cannot move to “Close” without formal UAT acceptance.
Strategic Rationale (and Why it Stops Heroics):
The Signed Project Charter: This foundational “contract” stops “Scope Creep Heroics” before they start. By requiring a signature, you ensure the business has formally committed resources and budget, and that everyone agrees on the high-level scope and objectives before the heavy lifting begins. It prevents the PM from having to make heroic efforts to deliver a project that was never properly defined or authorized.
The Signed Requirements: This signature locks the scope, eliminating “The ‘Nice’ PM Hero.” It prevents PMs from accepting “under the table” requests and forces a formal change control process for any deviation. This creates the transparency and accountability needed to stop scope creep—which is often just a mask for poor discipline—by making every change a visible, business-approved decision.
The Signed UAT (User Acceptance Testing): By requiring a formal signature that the system meets the agreed-upon business requirements, you prevent the business from operating on “almost done” systems. This forces an honest, measurable decision on when the project is truly operational, removing the need for a heroic save at the very end to fix a flawed delivery.
Formalizing the Handover: A project is only complete when it reaches a formalized Operational Acceptance Sign-off. This isn’t a formality; it’s the explicit, documented agreement from the IT Operations and Support teams that they have accepted full responsibility for the system. This sign-off confirms that documentation, monitoring, and support procedures are in place and that the team is trained. Without this gate, we aren’t crossing the finish line; we are just leaving the race early.”
In short: This process ends heroics by proactively removing the conditions (flawed scope, unapproved changes, untested systems) that create crises. It makes “done” a measurable standard at every stage, ensuring the team advances only on solid ground.
Define Meaningful Performance Measures (KPIs):
How: Move beyond just “On Time/On Budget.” Measure Schedule Variance (SV), Cost Variance (CV), and Scope Creep (via change requests).
Why it Ends Heroics: It provides objective data. You cannot “hero” your way out of a bad SV or CV. It brings light in preventing the Hero activities of folding in extra scope under the table because the requestor is “nice”. It forces honest conversations about project health before a crisis erupts.
Domain 2: Maturing IT Operations
We must stop offering vague “support” and start running IT as a professional services organization.
Define and Catalog the Services:
How: Implement an IT Service Management (ITSM) framework (like ITIL). Create a formal IT Service Catalog that lists every service IT provides, who is eligible, and how to request it.
Why it Ends Heroics: It eliminates the “shadow IT” requests and the “can you just do this for me” favors that drive reactive work.
Implement Service Level Agreements (SLAs):
How: For each service in the catalog, define clear, measurable SLAs (e.g., “Priority 1 Incident Resolution: 4 Hours”). Establish common expectations with the business about what “good” looks like.
Why it Ends Heroics: It replaces emotional urgency with objective priority. The team knows exactly what is expected, removing the need for heroic efforts to manage arbitrary deadlines.
The Strategic Outcome: Valuing the “Boring”
When you apply this discipline to both projects and operations, you achieve the ultimate goal: Boringly Predictable Operations.
“Boring” is good. “Boring” means projects land on time because the governance worked. “Boring” means systems stay up because the processes were followed.
As a leader, you must stop rewarding the fire-fighter and start rewarding the fire-marshal.
Don Ross is a seasoned IT executive with a track record of shaping teams into valued business partners and successfully delivering organizations across transformational finish lines. He has led multi-million dollar technology portfolios, navigated complex regulatory environments, and built high-performing teams across North America. He writes The Strategic CIO Perspective to share practical lessons on IT leadership, governance, and execution.