Case study 03
Strategic Prioritization & Decision Framework
A structured approach to evaluating and prioritizing product opportunities using quantitative and qualitative analysis, business value, and strategic alignment.
- ScenarioA fictional finance automation team with eight requests and room for two a quarter
- My roleProduct manager and owner of the backlog
- StakeholdersFinance leaders, operations, engineering, internal audit
- OutputScored backlog, decision log, quarterly plan
The problem
Everything is a priority
A finance automation team receives more requests than it can build. Each comes from a leader who is sure theirs is the most important. Without a shared way to compare them, the loudest request wins and the team keeps switching direction.
My goal was not to find a perfect formula. It was to make the trade-offs visible, so leaders could agree on the order and understand why their request was or was not next.
My approach
Score, then challenge the score
- Agree on criteriaImpact on a 1 to 10 scale (hours saved, error risk, users reached) and effort on a 1 to 10 scale (engineering weeks, dependencies).
- Score togetherScored each request with the requester and engineering in one session, so the numbers were shared, not mine.
- Rank by value for effortScore = Impact / Effort gives a first order.
- Check what numbers missStrategy fit, dependencies, compliance deadlines and risk can move an item up or down, with the reason written down.
- Decide and publishShared the order, the reasons and the next review date with everyone who asked.
Sample artifact
The scored backlog
| Request | Impact | Effort | Score | Decision |
|---|---|---|---|---|
| AI invoice matching | 9 | 3 | 3.0 | Priority 1 |
| Reporting automation | 8 | 3 | 2.7 | Priority 2 |
| Data reconciliation | 8 | 4 | 2.0 | Priority 3 |
| User experience improvements | 6 | 4 | 1.5 | Priority 4 |
| Vendor self-service portal | 7 | 5 | 1.4 | Next quarter |
| Executive dashboard redesign | 5 | 4 | 1.3 | Next quarter |
| Multi-currency support | 6 | 6 | 1.0 | Revisit with expansion plans |
| Legacy report migration | 4 | 5 | 0.8 | Not now |
Synthetic scores. Score = Impact / Effort, rounded to one decimal.
Key decisions
Where judgment changed the order
Data reconciliation stays in the top three
It scored below reporting automation, and one leader asked to drop it.
Kept it. AI invoice matching needs clean vendor data, and an upcoming audit depended on it. The dependency made it more valuable than its score.
The executive dashboard waits
A senior leader asked for it first.
Moved it to next quarter, openly. I showed what it would displace. With the trade-off on the table, the leader agreed.
Re-score every quarter
Options: fix the order for the year, or review it.
Chose quarterly reviews. Priorities change; the decision log shows why they changed.
Outcomes
What the framework gives the team
- One order everyone can see, with the reasons behind it.
- Fewer escalations, because requesters know when and why their item will be reviewed.
- A decision log that new team members and auditors can read.
- Focus: engineering works on two items at a time instead of six.
Illustrative example. This work sample uses a fictional scenario and synthetic data. It does not contain confidential or proprietary employer information.