The Raise-Your-Hand Rule: The Three-Month Cultural Installation That Killed Non-Commercial Work in an Engineering Division
The Stagnation Slaughter Score for this framework: 9.7/10. Most organizations I have worked with have an engineering function that spends 30-40 percent of its time on work that does not clearly connect to revenue. The work is technically interesting. The work passes every internal review. The work is often genuinely impressive from an engineering craft standpoint. The work also generates nothing. The Raise-Your-Hand Rule is the mechanism I built to strip that work out of the operating model in ninety days — not through top-down edict, but by empowering every engineer in the building to challenge it in real time, publicly, without political cost.
The Blitz You Will Never Authorize Through Normal Governance
The Scales division case that produced this framework is one I return to often because the findings were so much larger than I expected them to be. I walked in assuming engineering discipline had eroded at the margins — a few stray projects, some legacy initiatives that had outlived their justification, maybe $50,000 or $100,000 of annual waste hiding in the corners of the operating budget. What the first month of the Raise-Your-Hand Rule surfaced was forty-seven active projects that could not be connected to revenue in any defensible way. Thirty-one of them were killed outright. Ten were redesigned. Six were kept after clarification that mostly revealed the project had a real commercial purpose that had just never been articulated. The net recovery in Month One alone exceeded $100,000 in direct project cost, not counting the downstream opportunity cost of the engineering hours those projects had been consuming.
That is what the infographic above captures. Month One is exposure — the Rule is announced, employees exercise it immediately, and the organization discovers how much non-commercial work had been running under the radar. Month Two is learning — teams start self-editing before submitting work, because they know the question is coming and they would rather answer it internally than have a peer ask it publicly. Month Three is cultural default — commercial thinking becomes the operating assumption, and the eight hands raised in that month are edge cases rather than indicators of waste. Ninety days, three stages, one question. That is the entire intervention.
Why I Built This Framework
I built the Raise-Your-Hand Rule because the traditional mechanism for enforcing commercial accountability on engineering teams is budget review, and budget review fails. Budget review happens annually, on a calendar cadence, mediated by layers of management, dominated by political considerations, and entirely disconnected from the actual moment of project initiation. By the time a non-commercial project reaches budget review, it has already been resourced for a year, has built political constituencies defending it, and has accumulated sunk-cost arguments that make cancellation difficult. The review rarely kills anything. It just ratifies what was already happening.
The Rule bypasses this entire apparatus. It happens in real time. It happens at the moment of initiation or reassignment. It is exercised by the person being asked to do the work, not by a reviewer three levels above them. And it is structured as a simple question — “How does this contribute to our revenue goals?” — that cannot be refused without surfacing exactly the kind of work that should not be happening in the first place. A project lead who cannot answer the question has just publicly documented that the project should not exist. A project lead who can answer the question has just publicly documented the commercial case and made the project defensible. Either outcome is better than the status quo, which was that nobody was asking.
The Rule also works because it inverts accountability. Traditional engineering governance assumes the engineer is the requester and management is the approver. The Rule makes the engineer the auditor and management the respondent. That inversion matters. Engineers in most organizations have accurate intuitions about which projects lack commercial justification — they see it every day. What they lack is a sanctioned mechanism to surface those intuitions without political cost. The Rule is the sanction. Once installed, it runs itself.
The Blitz: How I Actually Roll Out the Raise-Your-Hand Rule in Ninety Days
The Blitz is the three-month cultural installation protocol that takes the Rule from announcement to default operating behavior. Here is what I actually do, and what the infographic above reconstructs from the Scales division rollout:
Week 1 — I announce the Rule with explicit protection. The announcement is simple: “Any employee can challenge any task by asking — How does this contribute to our revenue goals? If the answer is not clear, work stops until the connection is established or the task is eliminated.” The critical second half of the announcement is the protection: no employee will face political consequences for asking the question, even if the question targets a project owned by a senior leader. Without that protection, the Rule dies in Week 2 because the first person to exercise it gets punished and everyone else learns to stay silent. The protection is non-negotiable. It is the reason the Rule works.
Month One — I expect forty to fifty hands raised. The number seems high until you realize how much non-commercial work has been running unchallenged. In the Scales division, forty-seven hands raised in the first month. Thirty-one of the challenged projects were killed outright — they had no defensible commercial case. Ten were redesigned with new scope that could be connected to revenue. Six were kept after clarification that revealed a legitimate commercial purpose. The $100,000+ in Month One recovery is the floor, not the ceiling — the downstream opportunity cost of freed engineering hours compounds for the remainder of the fiscal year.
Month Two — I watch the filter move upstream. Teams start self-editing. Before submitting a new project request, the team lead asks the revenue question internally. If the answer is unclear, the project gets reworked before it is filed. Hands raised drops from forty-seven to roughly twenty-three — not because the Rule is losing force, but because less bad work is being initiated. This is the inflection point where the cultural shift begins. The question has moved from being asked after the fact to being asked before the fact. The work that survives Month Two is work that started with a commercial case attached.
Month Three — I watch commercial thinking become default. Hands raised drops to roughly eight. The eight are typically edge cases — ambiguous projects where reasonable people disagree about the commercial connection, or specialized initiatives where the revenue path is longer than one fiscal year and requires explicit articulation. These are not indicators of waste. They are indicators that the organization is now handling the hard cases with the same rigor it used to handle only the obvious ones. By the end of Month Three, commercial thinking has become the assumed operating frame. Engineers initiate projects with revenue ROI already in the pitch. Managers ask the question preemptively. The Rule stops being an intervention and starts being the culture.
The Deep Framework: Why Ninety Days Is the Critical Window
The infographic above plots the rollout across a single axis: time required for the Rule to shift from intervention to default. Month One is exposure — the Rule is new, behavior has not yet adapted, and the latent non-commercial work in the organization is surfaced all at once. Month Two is learning — teams adapt their initiation process to anticipate the Rule, and the filter moves upstream from the point of challenge to the point of proposal. Month Three is default — the commercial question is baked into how work gets started, and the Rule operates in the background rather than as an active intervention.
If the ninety-day window is interrupted — by a reorganization, by a leadership change, by an extended period where senior leaders stop reinforcing the protection — the Rule regresses. Regression is fast. I have seen organizations go from Month Three default behavior back to Month One baseline in six weeks if the reinforcement infrastructure is removed. The Rule is cheap to install and expensive to sustain if sustainment is ignored. Quarterly reinforcement from senior leadership is not optional. It is the maintenance cost.
The Sacred Terms inside this framework are non-negotiable. The question is the exact sentence — “How does this contribute to our revenue goals?” — not a paraphrase, not a softer variant. The specific wording matters because it is designed to produce a specific answer structure that cannot be dodged with vague commitments. The protection is the explicit guarantee that no employee will face political consequence for exercising the Rule. The stop is the operational consequence of an unclear answer — work stops, not slows, until the connection is established or the task is eliminated. Mislabel any of these and the Rule degrades into a soft-governance suggestion that changes nothing.
The Uncomfortable Truth
Every organization I have worked with has an engineering function doing 30-40 percent non-commercial work. The engineers know which projects are not defensible. They have known for years. What they have been missing is a sanctioned mechanism to surface those intuitions without political cost. The Rule is the sanction. Once installed with protection, it runs itself — and it reveals a volume of waste the organization did not realize it was carrying.
The forty-seven hands raised in Month One of the Scales division rollout were not a sign of a broken engineering culture. They were a sign of a normal engineering culture. Every organization I have ever worked with has some version of that number hiding in its operating model, waiting for someone to ask the question. The only variable is whether leadership has the courage to install the Rule, protect the people who exercise it, and let the consequences surface publicly in front of the stakeholders whose projects get killed. That is a political decision, not an operational one. Most organizations never make it, which is why most organizations keep running 30-40 percent non-commercial work year after year.
About the Author
Todd Hagopian is the founder of Stagnation Assassins and the creator of the HOT System (Hypomanic Operational Turnaround), a proprietary methodology built from five major turnarounds across Berkshire Hathaway, Illinois Tool Works, and Whirlpool Corporation. He is the author of The Unfair Advantage (winner of the Firebird, Literary Titan Silver, and NYC Big Book Distinguished Favorite awards) and Stagnation Assassin: The Anti-Consultant Manifesto (Koehler Books, July 2026). His frameworks — the 80/20 Matrix, the Karelin Method, the 3-A Method, the 3-S Method, and the Orthodoxy-Smashing Framework — have generated an estimated $3 billion in measurable shareholder value across Fortune 500, Fortune 1000, and small business transformations. He writes at toddhagopian.com and can be reached through the Stagnation Assassin Circle.
Join the Community
The Raise-Your-Hand Rule is one component inside the broader Revenue Responsibility Engineering framework and the HOT System arsenal. If you want direct access to the full corporate implementation guide, the video course (retail $5,000), monthly office hours with me, and a private community of transformation leaders pressure-testing these frameworks in real engagements — join the Stagnation Assassin Circle. Membership is free for readers. The war on stagnation needs more soldiers. Claim your seat here.