Program Strategy Office
Portfolio governance and initiative management
- 1.
The portfolio constraint is now explicit: architecture, data, integration, Java capacity, and leadership signoff bandwidth are limiting progress more than initiative effort.
- 2.
Lending remains the forcing function. KPMG closes on Thursday, June 26, and Monday's LoanStart 1.5 / 2.0 architecture discussion will either sharpen the post-KPMG decision path or distract from it.
- 3.
OAO and RTI both got more live this week. Bottle Rocket's June 22-23 discovery workshop plus Monday's Enlight standups mean retail work is moving, but still without enough enterprise guardrails on sequencing and ownership.
- 4.
Orion is still the portfolio hinge and still lacks clear cross-program stewardship. That remains the cleanest PSO-level governance gap.
- 5.
PSO should leave with named owners, dates, and deferrals. Another status pass will not reduce portfolio risk.
- ›Orion still has the broadest blast radius in the portfolio. PSO should treat architecture and product stewardship here as an immediate governance decision, not a background staffing issue.
- ›The portfolio is still routing too many hard choices through executive escalation and PMO choreography instead of through durable capability ownership.
- ›Lending still needs a bounded decision path after KPMG, not open-ended vendor debate and not a drift back to LoanStart as the practical default.
- ›OAO is getting momentum through discovery, but momentum without a recommendation date and decision standard will create more noise than progress.
- ›Monday's stack makes the sequencing problem visible in one place:
- ›`Updated Ryan and Justin Weekly Meeting`
- ›`LoanStart 1.5 and 2.0 - Technology Architecture and Lending Roadmap Discussion (June 22nd)`
- ›`Enlight/ Accnt Maintenance Future Planning Stand Up`
- ›`Enlight Standup PI 10`
- ›`Bottle Rocket Discovery Work Shop` on June 22-23
- ›Those are not separate work threads. They all compete for the same enterprise attention, architecture judgment, and delivery capacity.
- ›August R2 must be governed as one enterprise release calendar across LTI, RTI, and SLWE. Otherwise PSO will approve local progress that the enterprise cannot absorb cleanly.
- ›Orion continues to sit underneath LTI, RTI, SLWE, and OAO. Until ownership is named, dependency resolution will stay slower than the portfolio needs.
- ›Tadd's lane is a portfolio constraint, not just a technology function. Architecture and technical prioritization are now scarce enterprise services.
- ›Albert's lane is also a portfolio constraint. Data analytics and governance are directly connected to Orion, SLWE, retail ownership flows, and broader customer/party strategy.
- ›Monica's older deposit-enablement signal still matters: authority has to match responsibility or middle-layer ownership becomes symbolic.
- ›Daniel Parsons and PSO should operate as the portfolio decision log, not the portfolio note-taker. The meeting needs decisions on sequencing, ownership, and deferral.
- ›Hillary Stephens remains thinly evidenced in the local week-of source set. That is not a criticism of Hillary. It is a signal that coordination work is happening with weak artifact visibility.
- ›Confirm the lending decision sequence now:
- ›what exactly KPMG is delivering on June 26
- ›who reviews it immediately
- ›what date the platform / workflow direction is expected
- ›Name an interim owner for Orion architecture and product stewardship if permanent roles are still unresolved.
- ›Set R2 guardrails now across LTI, RTI, and SLWE, including what will be explicitly deferred if shared capacity tightens.
- ›Require each major initiative to identify the post-go-live capability owner, decision rights, and adoption metric before more scope gets protected.
- 1.Name interim cross-program ownership for Orion architecture and product stewardship.
- 2.Lock the post-KPMG lending decision path with owners and dates.
- 3.Set enterprise priority order for shared architecture, data, integration, and Java capacity through the August release window.
- 4.Require explicit deferral candidates for any R2 scope that depends on unresolved leadership, architecture, or signoff bandwidth.
- ›KPMG closes Thursday, June 26. If the deliverable is incomplete or the review path is vague, lending will lose decision momentum fast.
- ›LoanStart 1.5 / 2.0 could become either a useful interim clarifier or a way to postpone the real lending architecture choice.
- ›Bottle Rocket discovery may accelerate OAO expectations before PSO has settled ownership and decision cadence.
- ›RTI / Enlight continues to consume meaningful retail and technical bandwidth without a fresh breakthrough signal.
- ›The Orion ownership gap remains the portfolio's highest-leverage unresolved governance issue.
- ›Sparse source risk remains real: no fresh structured weekly team-note files were recovered for Tadd, Monica, Albert, Daniel, or Hillary in this review window.
- 1.Justin: force the room to decide who makes enterprise tradeoffs when shared capacity collides.
- 2.Daniel Parsons / PSO: run the meeting as a decision forum with named owners, dates, and deferrals captured live.
- 3.Tadd Tobkin and Albert Estrada: bring a concrete view of architecture and data bottlenecks by initiative, plus an interim Orion stewardship proposal.
- 4.Initiative owners: return with post-go-live capability ownership and adoption metrics, not just milestone status.
- 5.Portfolio team: produce one August readiness view across LTI, RTI, and SLWE with critical path, signoff dates, and explicit deferral options.