Lesson 26: Release-Quarter Investment Review Template for Expansion Bets

Lesson 25 gave you a quarterly roadmap and risk alignment snapshot.
This lesson turns that snapshot into a funding decision for the next release quarter: which expansion bets get calendar time, which stay parked, and which need mitigation before you spend a sprint on them.

You are not building a venture pitch deck. You are building a small-team investment sheet that respects live-ops reality.

What You Will Build

By the end of this lesson, you will have:

A one-page release-quarter investment review with ranked bets
A risk x capacity scoring grid that prevents silent overload
A confidence evidence column tied to Lessons 21-24 artifacts
A defer / fund / mitigate decision row per bet with owner and re-test date

Step 1 - List candidate expansion bets from the quarterly snapshot

Open your Lesson 25 quarterly snapshot and copy every workstream action that implies new scope in the next release quarter.

Examples of expansion bets:

new platform port or storefront
major content chapter or seasonal mode
net-new monetization experiment
large tooling migration (engine upgrade, backend swap)
marketing spike that requires engineering hooks

Pro tip: If a line item is pure maintenance (crash fix, save patch, policy copy refresh), it belongs in stabilization capacity, not the expansion investment sheet.

Step 2 - Score each bet with a simple impact and risk pair

For each bet, capture:

Player or revenue impact (low / medium / high)
Operational risk (low / medium / high) using reliability, support, and commercial lanes from Lessons 23-24

Create a 3x3 mental filter:

high impact + low risk -> default fund if capacity exists
high impact + high risk -> fund only with mitigation package and named owner
low impact + high risk -> default defer

Common mistake: Treating every high-impact idea as high priority without scoring operational risk. That is how release quarters quietly absorb hidden red work.

Step 3 - Add owner capacity and backup realism

For each bet, add:

primary owner hours per week available next quarter
backup owner and their realistic overlap
known concurrent obligations (support rota, certification window, day-job contract)

If primary and backup cannot cover the bet without crossing 90 percent load on reliability owners, mark the bet capacity blocked even if impact is high.

Step 4 - Attach confidence evidence from prior lessons

Each funded bet should point to at least one artifact:

Lesson 21 control panel lane thresholds for release readiness
Lesson 22 stabilization board exit criteria if the bet touches live code
Lesson 23 metrics review or incident postmortem if the bet responds to a trend
Lesson 24 monthly scorecard lane if the bet assumes commercial stability

If evidence is missing, the bet is speculative until you schedule a cheap discovery slice.

Step 4.5 - Check cross-course compliance dependencies before funding

Some expansion bets look commercially strong but depend on unresolved compliance controls. Add one dependency check column:

compliance dependency (none, legal hold, retention exception, vendor DPA, other)

If a bet depends on unresolved legal-hold or retention workflows, mark decision as mitigate first until the owning track is green. For teams using AI-heavy live-ops data paths, map this to the AI RPG governance sequence in Lesson 36, Lesson 37, and Lesson 49 so temporary exception waivers cannot remain open past one release window without explicit re-approval.

Step 5 - Build the investment review table

Use this schema:

Bet	Impact	Ops risk	Capacity OK	Evidence pointer	Decision	Owner	Re-test date
Example: console port	High	High	No	Needs packaged perf baseline	Mitigate first	Tech lead	+14 days

Decisions use only three verbs:

Fund -> calendar commitment with exit criteria
Defer -> parked with revisit trigger
Mitigate -> pre-work required before funding vote

Mini Exercise

Take one real bet from your roadmap and run it through the full table.
If you cannot fill the evidence pointer cell in two lines, the bet is not ready for funding yet.

Troubleshooting

Table grows past eight rows -> you are planning a portfolio, not a quarter. Cut to the top six bets and move the rest to a parking lot doc.
Every bet scores high risk -> your reliability lane is still yellow. Re-run Lesson 24 rhythm before expansion funding.
Owners disagree on impact -> anchor impact to measurable player outcomes (retention slice, conversion step, crash-free sessions), not opinions.
Bet is high impact but blocked by unresolved legal-hold or DPA lane -> keep decision at mitigate, assign owner deadline, and re-test after the compliance dependency is green.
Bet clears commercial scoring but depends on an active waiver exception -> require waiver-expiry proof and re-approval timestamp before changing decision from mitigate to fund.

FAQ

Is this the same as a roadmap prioritization workshop

No. Workshops generate ideas.
This review commits or refuses calendar time under explicit risk and capacity rules.

How often should we run it

Once per release quarter, after the Lesson 25 snapshot is approved.
Mid-quarter changes should be rare exceptions with a written trigger.

Should marketing-led bets skip engineering scoring

No. Store events, creator programs, and influencer pushes still consume build, support, and analytics attention.
Score them with the same operational risk lens.

Lesson Recap

You now have a release-quarter investment review that:

ranks expansion bets with impact and operational risk
forces capacity honesty across owners and backups
binds funding decisions to evidence from your launch-ops stack
replaces vague roadmap optimism with explicit fund, defer, or mitigate calls

Next Lesson Teaser

You have completed the numbered gap-fill arc through quarterly alignment and release-quarter funding discipline for this course track.
Use the release-quarter operations binder (Lessons 21–26) on the course overview to refresh or export the whole ops stack as one artifact, or cross-link into the AI-assisted RPG prototype course when live dialogue systems share the same launch-ops owners.

Related Learning

Bookmark this template and run it before you lock the next quarter roadmap with publishers, partners, or your own milestone promises.