Rank Value, Readiness, Risk, and Dependencies
Build a transparent ranking model without hiding assumptions, evidence gaps, critical risks, or portfolio dependencies inside one total.
What you will complete
Complete the Prioritization Matrix and Dependency Map with learner-chosen weights, rationales, evidence labels, and critical gates.
Portfolio rule: A weighted total may order discussion. It may not override a failed ownership, evidence, human-control, or safety gate.
Keep dimensions separate
Value describes why the outcome matters. Readiness describes process stability, data, access, rules, owner capacity, and testability. Risk covers customer, employee, privacy, reliability, integration, and adoption consequences. Dependencies show what must happen first. Display each dimension before any weighted total.
Label weights as choices
No supplied source validates universal portfolio weights. The learner may choose weights for its current strategy, document why, and test how the ranking changes under another reasonable weighting. Sample numbers in this course are fictional teaching inputs rather than Flowgrammer recommendations.
Use critical gates
Some conditions should not be averaged away: no accountable owner, no lawful or approved data path, no human decision boundary for consequential cases, no measurable outcome, or a critical unresolved safety issue. A high value score cannot purchase its way through a failed gate.
Worked example: Harbourline Business Services
Fictional teaching example: Harbourline chooses fictional weights of 35 percent value, 30 percent readiness, 20 percent risk fit, and 15 percent dependency fit. Lead qualification ranks highly but cannot proceed until the sales owner approves decision rules. Meeting summaries rank lower in strategic value but can use an existing approved tool. These values and sample scores are learner choices, not benchmarks.
Harbourline is not a Flowgrammer client. Its people, projects, weights, scores, costs, metrics, and outcomes are fictional learner inputs. Replace them with evidence from your organization and retain the evidence source beside each decision.
Workbook exercise
Complete section 3 of the 90-Day AI Automation Portfolio Workbook.
- Define value, readiness, risk, and dependency anchors.
- Choose and justify portfolio weights.
- Label every score as observed evidence, calculation, or assumption.
- Run sensitivity and critical-gate checks before creating the priority order.
Ask the affected owner to challenge one assumption. Record the original entry, revision reason, decision owner, and review date rather than silently replacing the history.
Common failure modes
- Using one opaque priority number.
- Presenting sample weights as universal.
- Awarding readiness points for missing information.
- Letting a high total erase a critical risk.
A portfolio should expose weak evidence and constrained capacity. Repair the responsible layer instead of increasing the score or compressing the schedule.
Capstone connection
Complete the Prioritization Matrix and Dependency Map with learner-chosen weights, rationales, evidence labels, and critical gates. The section must be specific enough for leadership, affected operators, and an implementation reviewer to inspect. It remains planning evidence rather than proof of implementation or outcome.
Check your application
1. What should happen when a project ranks first but has no accountable owner?
2. How should sample weights be described?
3. Why run a sensitivity check?