Short answer: Engineering prioritization should rank every project by the revenue it enables, not by technical interest or who asked loudest. Ask the 10 questions below of each project, starting with "What revenue will this enable, and which customers benefit?" This is revenue responsibility engineering from Todd Hagopian's Stagnation Assassin: projects that cannot answer get killed or redesigned.
Related reading: How NPV Gets Manipulated in Boardrooms
Related reading: Boeing MAX: Stagnation Genome Autopsy
Most engineering teams are run as cost centers, judged on staying within budget and hitting technical milestones. That rewards polish on things customers will not pay for and starves the changes that would open new revenue. It is more work, less profit, delivered by very capable people.
Why Cost-Center Engineering Misfires
Cost-center engineering optimizes for technical excellence and budget compliance, so commercial impact goes unmeasured. Stagnation Assassin contrasts the two models on eight dimensions:
Related reading: The Raise-Your-Hand Rule: 90-Day Reset
- Focus: budget compliance versus revenue generation.
- Metrics: budget variance and cost per unit versus revenue attribution and share gains.
- Resource allocation: fixed annual budgets set by internal politics versus dynamic allocation to commercial opportunity.
- Decision authority: centralized approvals that create queues versus decentralized decisions with commercial accountability.
- Innovation: technology-driven with long cycles versus market-driven with rapid iteration.
- Mindset: risk aversion versus intelligent risk-taking.
- Relationships: separated from Sales and Marketing versus integrated with commercial teams.
- Compensation: technical mastery versus revenue outcomes.
"Engineering becomes a profit center measured by revenue contribution, market impact, and commercial outcomes."
Todd Hagopian, Stagnation Assassin, Chapter 9
The 10 Revenue Questions
- What revenue will this enable? Every project gets a Revenue Impact Statement: revenue enabled, customers who benefit and how commercial success will be measured. No answer, no funding.
- Is it in the top 20 percent of revenue drivers? Rank all projects by revenue potential, fund the few projects that carry most of the total impact, and put the rest on maintenance-only support.
- Will customers pay a premium for it? Look for actual commitment, not interest. No premium, no priority.
- How long until it earns revenue? Favor short time-to-revenue. Break long projects into phases that each earn something.
- Does it reduce churn or raise lifetime value? Keeping customers is often worth more than a new feature.
- Can it be sold separately? A standalone product, add-on service or premium tier may be worth more than bundling.
- How long is the competitive window? In the book's experience, competitors deny, dismiss and then copy, which leaves a window of roughly fourteen to twenty-two months. Prioritize projects where you can be first.
- Does revenue scale faster than cost? Automation and self-service create leverage; people-dependent processes do not.
- Does it multiply revenue elsewhere? Integrations and partner revenue can raise the value of the core product.
- If we killed it tomorrow, who would complain? If the honest answer is "only the engineers working on it," kill it.
The Raise-Your-Hand Rule
Give every employee the right to 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. In the book, the number of raised hands fell sharply over three months as commercial thinking became the default.
Why Revenue Focus and Decision Speed Multiply
Fast decisions without commercial alignment execute the wrong priorities quickly; alignment without speed executes the right ones too late. Stagnation Assassin works the numbers from the Refrigeration transformation:
- Before: eighteen-day decisions, 40 percent commercial alignment, about twenty-four commercially valuable decisions a year.
- 70% Rule only: 1.4-day decisions, still 40 percent aligned.
- Revenue responsibility only: 90 percent aligned, still eighteen-day decisions.
- Both: 1.4-day decisions at 90 percent alignment, about seven hundred commercially valuable decisions a year.
A 12-Week Rollout
- Weeks 1 to 4, visibility: dashboards linking projects to revenue; a Revenue Impact Statement for every project.
- Weeks 5 to 8, accountability: project approval requires revenue projections; engineering presents revenue outcomes in regular commercial reviews.
- Weeks 9 to 12, incentives: revenue metrics in performance reviews and compensation.
- Ongoing, culture: hire and promote engineers who think commercially.
Related reading on Stagnation Assassins: Innovation Pipeline Checklist, Sniper SKU Development and Cross-Functional Team Checklist.
Frequently Asked Questions
What is revenue responsibility engineering?
It is Todd Hagopian's model for running engineering as a profit center: every project states the revenue it enables and the customers it serves, resources move to the biggest commercial opportunities, and engineers are measured on commercial outcomes.
How should engineering projects be prioritized?
By revenue enabled, time to revenue, customer willingness to pay and competitive window. Rank all projects, fund the top drivers fully and put the rest on maintenance support.
What is a Revenue Impact Statement?
A short statement required for every engineering project in Stagnation Assassin: what revenue it will enable, which customers benefit, and how commercial success will be measured. Projects that cannot answer are killed or redesigned.
Sources
- Todd Hagopian, Stagnation Assassin: The Anti-Consultant Manifesto, Chapter 9 (revenue responsibility engineering, eight differences, implementation phases, Raise-Your-Hand Rule, compound velocity effect) and Chapter 8 (competitor response pattern).
- The 10 questions are carried over from the previous version of this article; the unsourced opening anecdote, case figures and thresholds were removed.
Put This to Work With Your Team
Stagnation Assassins exists to turn these frameworks into results inside real organizations. If your leadership team is putting in more work for less profit, pick one of two next steps. Book Todd Hagopian to speak at your leadership offsite or conference, or read the books and run the playbook yourself.

