A strong operating rhythm makes trade-offs visible and keeps banking priorities moving. The goal is consistent decisions that balance Run, Change, and Innovate.
Picture the same bank, the same quarter, twice.
Version one: the quarter opens with twelve clean priorities and good intentions. Week two, a payments incident pulls two squads into triage and nobody records the trade-off, it just happens. Week three, a vendor forces an upgrade nobody asked for, and another project quietly loses steam while the core team chases it. Week four, the monthly check-in is a slide parade. Nobody asks the hard question. The list still says the same twelve priorities it said a month ago, and adoption hasn’t moved. Nothing got decided all quarter. It just eroded.
Version two: same incident, same vendor upgrade, same pressure, but a different result because there’s a rhythm underneath it. Week one, there’s one project list everyone can see, with a business owner, a delivery owner, an adoption target, and a first benefit measure for every item on it. Week two, the payments incident hits, and a thirty-minute weekly risk huddle logs the exception, sets the first fix, and records the short pull of two squads with a return date, and the onboarding owner already knows what will slip and says so out loud. Week three, the vendor upgrade gets scored against the bank’s bright lines, and the CTO says plainly what’s mandatory and what can wait; one item moves down the list to protect Run, and that trade gets written into the list, not settled in a hallway. Week four, the monthly portfolio review is a decision room, not a status meeting: one page per item, and the group makes three calls:
- Continue one initiative with a narrower goal
- Stop a pilot that never showed value
- Rebalance people toward the work that sets up next quarter
Drift had nowhere to live.
That’s the entire difference an operating rhythm makes. Not more effort. Not more meetings even, just a few real forums on a fixed cadence where trade-offs get made out loud instead of by accident.
“Priorities must be set at the top of the house and communicated so everyone marches to the same drumbeat.”
— Angelo Incorvaia, Senior Technology Leader, TD Bank / Citi
The single project list is what makes that possible: short enough to talk through end to end, with names, dates, and outcome targets instead of feature lists, re-ranked quarterly and reviewed monthly by a room that includes the CEO sponsoring what matters, the COO running the flow, the CFO bringing the money story, and the CTO bringing the standards.
The weekly layer is where big failures actually get caught while they’re still small. Ben Gurdus was blunt about why that cadence can’t be optional for the highest-risk rails: “Deposit and payment rails get conservative windows and extra checks. When they fail it is front page risk.” The weekly risk huddle is thirty minutes, cameras on, no slides:
- Top five risks, each with an owner and a next move
- The exception backlog
- Time to recovery from the previous week
The instinct in a calm month is to cancel it. Don’t. Rhythm beats drama precisely because it doesn’t wait for drama to show up.
None of this replaces good engineering discipline underneath it. Daniele Tonella’s frame for the pipelines that carry all of this work is exactly right: velocity comes from guardrails, not heroics. Fixed release cadence, checks that block when quality slips, canary releases to lower blast radius. The rhythm and the pipeline are the same idea at two altitudes: decisions on a schedule, and the plumbing that lets those decisions actually ship.
Operating rhythm isn’t a program, and it isn’t exotic. It’s leadership on a calendar. Keep the appointments. Make the calls out loud. The wheel turns because someone decided, on purpose, which way to push it this week.
— Rick Mavrovich
