ExecutiveWeekly

Executive Team

Weekly leadership sync — Greg, Tim, and extended team

Prep sessions

Bottom Line Up Front

1.
Force a decision path on lending this week. The right move is not to pick a final platform in the room, but to lock the decision basis, owners, and date that platform direction lands after KPMG closes on June 26.
2.
Name the portfolio constraint plainly: data, architecture, integration, and leadership signoff capacity are now the limiting factors, not initiative effort.
3.
Treat Monday's stack as proof of where attention is going: LoanStart 1.5 / 2.0 architecture discussion, Ryan weekly, Enlight standups, and a two-day Bottle Rocket discovery workshop all point back to the same enterprise problem of sequencing shared capacity.
4.
Keep August R2 framed as a governance gate, not a delivery milestone. If LTI, SLWE, RTI, and OAO all press into August without harder tradeoffs, the bank will create motion without clarity.
5.
Use Greg and Tim for the decisions only they can make: enterprise tradeoffs, interim ownership, and the level of short-term inefficiency the bank will accept to build durable capability.

Talking Points

Transformation Portfolio

›Lending remains the center of gravity. The bank still has the same underlying problem: cycle time, re-key friction, low frontline fit in nCino, and too much dependency on LoanStart for small-business volume.
›This week's new signal is not a solved answer; it is a tighter forcing function:
›KPMG discovery closes June 26.
›Monday now includes a dedicated LoanStart 1.5 / 2.0 architecture and roadmap discussion.
›Monday also includes Ryan's weekly touchpoint, which creates a natural lane to align banker-experience priorities before platform recommendation work hardens.
›OAO is active enough to stay executive-relevant. Bottle Rocket has a two-day discovery workshop on June 22-23, so OAO is still in live definition, not background maintenance.
›RTI / Enlight remains active but constrained by shared capacity. Monday includes both future-planning and PI 10 standups, which reinforces that account maintenance and near-term retail scope are still moving, but the evidence does not show an executive-level breakthrough yet.
›SLWE remains an August pressure contributor. The strongest current signal is still the R2 gate itself: Ted Lane's scope, Salesforce architecture questions, and signoff bandwidth matter more than another status tour.
›Orion remains the hinge. The cross-program dependency has not been matched by clear architecture and product stewardship. That is still the cleanest portfolio-level risk to surface.

Decisions Needed This Week

›Confirm what the lending decision actually is:
›platform choice
›workflow / architecture pattern
›or both on sequenced dates
›Set the post-KPMG decision path now:
›KPMG close on June 26
›executive review immediately after
›platform direction by mid-July if August scope is expected to mean anything
›Name interim ownership for Orion architecture / product stewardship if permanent roles are still unresolved.
›Decide how much August R2 scope the bank is actually willing to defend across LTI, RTI, SLWE, and OAO versus what gets explicitly deferred.

Key Risks & Watchlist

›Decision-latency risk: KPMG can deliver and the bank can still drift if no executive checkpoint is named.
›Shared-capacity congestion: architecture, data, integration, Java, and leadership signoff are still acting like enterprise bottlenecks.
›False-convergence risk: the room could talk as if LoanStart, Newgen, OpenText, nCino minimization, and OAO are separate issues when they are really one sequencing and operating-model problem.
›Orion ownership gap: still the portfolio's highest-leverage governance hole.
›Sparse agenda risk: because no explicit exec-team meeting invite was visible for June 22-24, this packet is strongest on decision pressure and portfolio implications, weaker on a confirmed formal agenda.

Relationship Lens

›Greg: keep the conversation at enterprise altitude. Frame this as confidence, stewardship, and what will actually let the bank serve customers faster without adding hidden drag.
›Tim: make the execution tradeoffs explicit. Who owns the bottlenecks, what gets sequenced, and what is deferred.
›Political read: do not let the conversation collapse into vendor preference. Keep pulling it back to decision rights, architecture pattern, and operating capability.

Key Decisions

1.Confirm the exact lending decision sequence and the date the executive team expects a recommendation after KPMG closes on June 26.
2.Name an interim owner for Orion architecture and product stewardship.
3.Set explicit August R2 guardrails across LTI, RTI, SLWE, and OAO.
4.Decide what short-term inefficiency the bank will tolerate in order to build durable internal capability instead of buying speed that creates future rigidity.

Watch Items

›LoanStart 1.5 / 2.0 discussion on Monday could become either a useful architecture clarifier or a distraction from the bigger lending decision.
›Bottle Rocket discovery momentum may accelerate OAO expectations before enterprise capacity and decision rights are settled.
›RTI / Enlight continues to consume retail and technical bandwidth even without a fresh executive escalation signal.
›Any slippage or incompleteness in the June 26 KPMG output materially weakens the LTI decision path.

Next Actions

1.Justin should lead with enterprise constraints and decision cadence, not initiative mechanics.
2.Ask Greg and Tim to leave with named owners and dates, not just directional agreement.
3.Pull the Monday LoanStart and Bottle Rocket discussions back into one portfolio-sequencing conversation.
4.Schedule the post-KPMG executive review now if it is not already on calendar.