Portfolio evaluation partner
Decide how to compare initiatives using evidence, constraints, and opportunity cost
When leadership must choose which agent initiatives to advance or stop, this area becomes relevant. For the portfolio investment sponsor, the concern is specific: unproven projected benefits crowd out smaller initiatives with better evidence. The operating model design starts from that consequence and follows the relevant evidence through the customer workflow. Portfolio evaluation should preserve uncertainty rather than convert every estimate into a precise score. A recommendation needs to explain which assumptions drive it and which new evidence would change the allocation.
Connect the operating question to inspectable evidence
- Portfolio investment sponsor
- Owns the bounded decision and the consequence of acting.
- Initiative proposals
- Defines the starting context for the proposed work.
- Comparable decision criteria
- Exposes the first material uncertainty to examine.
- Gate recommendation brief
- Carries unresolved conditions into an accountable next action.
Decision at stake
Decide how to compare initiatives using evidence, constraints, and opportunity cost
Make the decision explicit
- Portfolio investment sponsor
- Leadership must choose which agent initiatives to advance or stop.
- Decision
- How to compare initiatives using evidence, constraints, and opportunity cost.
- Comparable decision criteria
- Use initiative proposals to establish the relevant starting condition.
For the portfolio investment sponsor, this becomes relevant when leadership must choose which agent initiatives to advance or stop. The immediate decision is how to compare initiatives using evidence, constraints, and opportunity cost. The scope should be narrow enough that the customer leadership team can identify a meaningful alternative, including continuing the current approach if the available evidence already supports it.
The practical failure to challenge is that unproven projected benefits crowd out smaller initiatives with better evidence. That concern gives the work a concrete direction: establish what the relevant boundary should do, inspect how it behaves or would operate, and identify the owner of any gap. It should not be diluted into a broad transformation exercise before the specific question has been answered.
Coverage
Examine comparable decision criteria alongside dependency concentration
Keep the review distinctions visible
- Comparable decision criteria
- Apply shared criteria while preserving each initiative's evidence quality.
- Dependency concentration
- Show where initiatives depend on the same scarce reviewer or platform.
- Stop and revisit conditions
- Record the evidence that would reopen a hold or stop recommendation.
Comparable decision criteria
For this scope, comparable decision criteria should be examined alongside initiative proposals. Use comparable criteria while keeping evidence strength visible. A forecast and an observed result should not receive the same treatment merely because both can be assigned a number. The portfolio review should explain which assumptions drive the recommendation and which alternatives remain plausible.
Dependency concentration
For this scope, dependency concentration should be examined alongside capability and demand evidence. Map scarce resources and shared dependencies across initiatives. Funding several pilots can create competition for the same technical, data, or review capacity. The proposed assessment should make opportunity cost and concentration visible rather than evaluate every idea as if it had unlimited independent resources.
Stop and revisit conditions
For this scope, stop and revisit conditions should be examined alongside shared resource limits. Record explicit gates and revisit conditions for advance, hold, partner, or stop recommendations. A portfolio item should not remain open indefinitely without a next evidence question. The authorised owner makes the allocation decision, with uncertainty and the rationale preserved for later review.
Prerequisites
Start with initiative proposals
Give each input a specific job
- Initiative proposals
- Defines the operating boundary.
- Capability and demand evidence
- Examine dependency concentration.
- Shared resource limits
- Shows conditions affecting stop and revisit conditions.
- Executive sponsor
- Confirm access and a reviewer who can resolve gaps.
The starting material is initiative proposals, capability and demand evidence, and shared resource limits. Review these together rather than assuming one document tells the whole story. A stated rule may differ from a configured behaviour, and a proposed responsibility may not yet have an available owner. Identify those differences before selecting the detailed work.
Participation should include an executive sponsor, accountable delivery owners, and the people who can accept or implement the resulting decisions. The customer should define which information and environments may be used. Synthetic or sanitised examples can support preparation when they preserve the relevant behaviour; if they omit a material dependency, record the limitation and agree how the missing evidence would be obtained.
How the work proceeds
Make the mandate usable in operating decisions
Follow the evidence through the work
- Comparable decision criteria
Use initiative proposals to define the decision criteria.
- Dependency concentration
Inspect capability and demand evidence and retain observations that challenge the expected result.
- Stop and revisit conditions
Use shared resource limits to identify unresolved conditions and a responsible owner.
- Gate recommendation brief
Link the recommendation to its evidence, remaining limits and next validation condition.
Use scoring only where its meaning is clear. Separate observed evidence from estimates and show sensitivity to assumptions that drive the recommendation. The proposed portfolio review should account for shared scarce resources and the cost of keeping an initiative open, including the attention required to maintain unfinished pilots.
A practical first slice would focus on comparable decision criteria and then follow its consequences into dependency concentration. Keep stop and revisit conditions visible as a separate review question rather than assuming it is satisfied by the first result. The customer leadership team should record observations, competing explanations, and changes to the original assumptions. A second reviewer can challenge whether the evidence supports the recommendation and whether an apparently successful example omitted the condition that matters most.
Indicative artefacts
Use gate recommendation brief to make the next action explicit
Every artefact needs an operating use
Illustrative working format
- Portfolio evaluation rubric
- Boundary — initiative proposals.
- Evidence-based option map
- Findings about dependency concentration.
- Gate recommendation brief
- Action on stop and revisit conditions.
Indicative outputs include portfolio evaluation rubric, evidence-based option map, and gate recommendation brief. Their form should follow the decision and the customer’s existing operating records. The first should establish the assessed boundary and relevant observations; the second should make material gaps or dependencies inspectable; the third should identify the action, owner, and evidence needed to revisit the decision.
Acceptance should be tested through use: can the responsible owner explain what was examined, identify an unresolved issue, and act on the next step without reconstructing the whole engagement? Findings should preserve counterevidence and limits. A polished document is insufficient if it does not help resolve the customer’s specific question.
Illustrative scenario
Remediation or new pilots: explicit portfolio gate
Examine the constructed decision boundary
Illustrative scenario
- Remediation or new pilots
An organisation must allocate funding between an existing agent and new experiments.
- Next-investment evidence
Compare achievable outcomes and constraints for each option.
- Explicit portfolio gate
Recommend the supported next step; the owner records advance, hold, partner or stop.
Consider an illustrative situation in which an organisation must choose between improving one existing agent and funding several new pilots. This is a constructed example, not a client engagement or an observed Softlander outcome.
For improving an existing agent versus starting new pilots, an illustrative comparison would examine the evidence available for each next investment. A modest remediation effort might have a clearer decision path, but that remains a recommendation grounded in the actual constraints. The portfolio owner should record advance, hold, partner, or stop decisions explicitly.
The useful learning would be the difference between the expected behaviour and the behaviour or responsibility actually demonstrated. If the exercise leaves stop and revisit conditions unresolved, that should remain a named next step. A recommendation to narrow the scope, improve a prerequisite, or hold the decision can be appropriate when the example exposes a material dependency.
Scope and authority
A proposed mandate needs confirmed authority and capacity
Keep analytical work separate from decision authority
- Operating mandate and handover design
- Can include portfolio evaluation rubric.
- Executive sponsor
- Customer executives retain investment, release and risk decisions.
- Staffing, price and retained commitments
- Cannot be inferred from evidence-based option map.
These are proposed working arrangements, not claims of current staffing or an active retained relationship. Executives retain investment, release, and risk decisions. Capacity, role authority, conflicts, and commercial terms need explicit agreement before a commitment.
Ways to engage
Related engagement scopes
AI Fractional Agentic AI Office
Create a regular place for agentic AI decisions. Connect initiative priorities, architecture questions, risk ownership and evidence reviews.
AI Fractional Agentic Transformation Office
Coordinate the operating changes behind agent adoption. Align workflow redesign, ownership, dependencies and adoption measures.
AI Harness Engineering Pod
Engineer a bounded AI execution harness with tool adapters, context handling, orchestration, recovery and observable traces.
Continue exploring
Related insights and resources
Engineer the harness, not just the prompt
Define the contracts around an agent's decisions: what state it trusts, which actions can execute, how interrupted work resumes, and what evidence an operator needs to recover safely.
Governing agent decisions
Governance becomes useful when it changes a decision. Connect each agent workflow to an accountable owner, explicit operating conditions, proportionate evidence and a practical route for exceptions and withdrawal.
Do you need an agent centre of excellence?
A centre can concentrate scarce expertise and reusable controls, or become an approval queue detached from real work. Choose the mandate before the structure.