Assign Owners and Human Decision Rights
Name sponsors, business owners, system owners, reviewers, builders, and pause authority while preserving consequential human decisions.
What you will complete
Complete the Ownership and Decision-Rights Map for every active initiative and exception path.
Portfolio rule: Every active initiative needs a person accountable for its business outcome and a person accountable for operation after launch.
Separate ownership roles
The executive sponsor supplies authority and resolves portfolio conflicts. The business owner defines the operating outcome and policy. The system owner watches normal operation, failures, access, and maintenance. A builder or vendor delivers scoped work. Reviewers handle named exceptions. One person may fill several roles, but the responsibilities remain distinct.
Write the human boundary
Classify each important step as software completes, software prepares and a person approves, or a person decides. Keep judgment, sensitive exceptions, important relationships, policy changes, and final accountability with named people. Do not create approval queues for low-risk deterministic work without a reason.
Assign decision and pause authority
Record who can approve discovery, design, build, launch, expansion, policy change, pause, rollback, and stop. Define escalation when an owner is unavailable. A vendor cannot quietly become the business policy owner because it configured the system.
Worked example: Harbourline Business Services
Fictional teaching example: Harbourline names its COO as portfolio sponsor. The revenue leader owns lead-qualification policy, a revenue-operations manager owns the system after launch, and sales reviewers accept consequential routing decisions. Finance owns invoice-intake policy. Contract review remains human-led. The chatbot pilot stays paused because nobody owns the customer outcome.
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 4 of the 90-Day AI Automation Portfolio Workbook.
- Assign sponsor, business owner, system owner, builder, reviewer, and affected-user representative.
- Classify critical steps by software and human responsibility.
- Name exception and escalation owners.
- Record authority for policy change, launch, pause, rollback, and stop.
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 a committee as the only owner.
- Making the vendor responsible for business policy.
- Keeping every step in human review.
- Leaving pause authority undefined.
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 Ownership and Decision-Rights Map for every active initiative and exception path. 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. Who owns the definition of a successful business outcome?
2. Which decision normally remains human?
3. Why name pause authority before launch?