The Raise-Your-Hand Rule: The Cultural Installation Protocol the Big Four Cannot Sell
HOT Readiness Index for this protocol: 9.7/10. The Raise-Your-Hand Rule is a 90-day revenue accountability installation protocol that embeds real-time commercial challenge authority into every employee in the operating model. Deployed correctly, the protocol produces a measurable cultural shift from Month 1 exposure (47 typical challenges surfacing non-commercial work) through Month 2 learning (teams self-editing upstream) to Month 3 default (commercial thinking becomes the assumed operating frame). Documented first-month value recovery exceeded $100,000 at the Scales division engagement.
Execution Protocol: Fast-Facts
- The Rule: “How does this contribute to our revenue goals?” Any employee can challenge any task with this exact question. If the answer isn’t clear, work stops until the connection is established or the task is eliminated.
- Month 1 — Exposure: 47 hands raised at Scales division. 31 projects killed outright. 10 redesigned with new scope. 6 kept after clarification. Value recovered: $100,000+ in direct project cost in month one.
- Month 2 — Learning: 23 hands raised. Teams begin self-editing before filing. Revenue ROI becomes standard in project pitches. Filter moves upstream from challenge-after-initiation to clarification-before-initiation.
- Month 3 — Default: 8 hands raised. Revenue connection is now assumed. Non-commercial work is no longer being initiated. The 8 remaining challenges are edge cases, not waste indicators.
- Installation cost: Near-zero financial cost. Political cost requires explicit senior leadership commitment to protect employees exercising the Rule.
- Maintenance requirement: Quarterly reinforcement from senior leadership. Regression from Month 3 default to Month 1 baseline occurs in 6 weeks if reinforcement is removed.
- Baseline non-commercial work rate in typical engineering organizations: 30-40% of engineering capacity.
The Anti-Consulting Critique
The Big Four will never install the Raise-Your-Hand Rule inside a client organization, and the structural incompatibility is categorically the cleanest in this library. The Rule is designed to empower the lowest-level employees in the organization to publicly challenge the commercial justification of any active project. A significant percentage of those active projects will be Big Four consulting engagements — strategic studies, operational assessments, transformation initiatives, change management workstreams — which the firm itself scoped, sold, and is currently billing against. The first employee who asks “How does this engagement contribute to our revenue goals?” and receives an unclear answer triggers the same stop-work consequence that applies to internal projects. The firm cannot recommend a governance mechanism that will systematically challenge its own deliverables.
The second structural problem is the methodology itself. Big Four governance assessments are built on top-down frameworks: RACI matrices, decision rights architectures, governance council designs, steering committee charters. All of these mechanisms consolidate decision authority upward into structures the firm can study, recommend modifications to, and bill for implementing. The Raise-Your-Hand Rule rejects this entire architecture. It pushes decision authority downward to every individual employee. It requires no matrix, no council, no charter — just a single sentence protected by senior leadership commitment. A firm whose practice revenue depends on selling top-down governance frameworks cannot credibly recommend a bottom-up challenge mechanism that makes those frameworks redundant.
The third structural problem is the political architecture. The Rule works because senior leadership explicitly protects employees who exercise it, including when the challenged project is owned by another senior leader. This requires the sponsoring executive to commit, in advance, to defending a challenge against their peers’ work product — which is a political act that most consulting engagements are designed to avoid at all cost. Big Four engagements rely on alignment workshops, stakeholder interviews, and consensus-building to ensure no senior stakeholder feels targeted. The Raise-Your-Hand Rule does the opposite. It accepts that senior stakeholders will have their projects challenged, killed, and redesigned in the process — and treats that outcome as the point, not the side effect. No consulting engagement that depends on sustained senior-leadership comfort can sell a protocol whose entire mechanism is designed to make senior leaders uncomfortable.
The Blitz: Tactical Execution Protocol
The Blitz is the 90-day cultural installation of the Raise-Your-Hand Rule, executed in three sequential monthly phases. Deployed correctly, the installation produces four artifacts: a documented list of non-commercial work surfaced and killed in Month 1, a self-editing behavior pattern observable in Month 2 project submissions, a baseline cultural default established in Month 3, and a quarterly reinforcement protocol assigned to senior leadership for ongoing maintenance.
The installation protocol rejects the three standard governance interventions used in Big Four engagements. Steering committee formation is replaced by individual employee challenge authority. RACI matrix redesign is replaced by a single-sentence governance protocol. Top-down communication cascades are replaced by a direct announcement from the highest-level sponsor, delivered simultaneously to the full organization, with explicit protection language included in the announcement itself.
The installation’s critical success factor is the protection clause. Without explicit senior leadership protection for challengers, the Rule collapses in Week 2 because the first employee to exercise it faces political retaliation and everyone else learns to stay silent. The protection clause is not optional. It is the entire reason the Rule works. Senior leadership must commit publicly, visibly, and in writing to defending challengers — and must follow through in at least the first three high-profile challenge cases, including cases that target other senior leaders’ projects. The first three cases are the proof point. After that, the Rule runs itself.
How to Weaponize This Framework
Step 1 — Secure senior leadership protection before announcement. Before announcing the Rule, confirm that the highest-level sponsor will publicly defend challengers against political retaliation, including challenges that target other senior leaders’ pet projects. Get the commitment in writing. If the commitment is soft — “we’ll see how it plays out” or “depends on the specific case” — the Rule will fail. Do not announce. Return to the protection conversation until the commitment is firm, or shelve the protocol entirely. A soft-protection installation is worse than no installation, because it teaches the organization that commercial challenges are dangerous.
Step 2 — Announce the Rule with the exact sentence and explicit protection language. The announcement contains three elements: the Rule itself (“How does this contribute to our revenue goals?”), the consequence (work stops until the connection is established or the task is eliminated), and the protection (no employee will face political consequence for exercising the Rule, regardless of who owns the challenged work). Deliver the announcement from the highest-level sponsor, simultaneously to the full organization. Do not phase the rollout. Do not pilot it in one division. Universal simultaneous announcement is the mechanism that establishes the Rule as an organization-wide protocol rather than a localized experiment.
Step 3 — Track the hands-raised count monthly and reinforce quarterly. Month 1 should produce 40-60 challenges in a typical mid-sized engineering organization. If the count is under 10, the Rule is not being exercised — usually because the protection clause is perceived as soft. If the count exceeds 100, the organization had significantly more non-commercial work than average and the cleanup phase will extend into Month 4 or Month 5. Month 2 should show a roughly 50 percent decline in hands raised as the filter moves upstream. Month 3 should show single-digit challenges representing