Bring a difficult operating question to the room

I examine the funding question that sits between treasury models and relationship knowledge: who can decide to move a material balance, and what might prompt that decision? The session follows a fictional commercial-bank deposit review from account records to connected ownership and withdrawal authority. Participants consider what a relationship manager may know, the assumptions a model may contain and the gaps neither function can close alone. I discuss the economic cost of diversification, including the possibility of losing associated business, and how to make that trade-off visible to directors. The aim is to help an executive team ask better questions about a concentration it already understands imperfectly. I do not offer a formula for an acceptable deposit mix or advice about a particular institution. The discussion is most useful when participants bring a question about governance, evidence or decision ownership rather than confidential customer data. We finish by identifying one assumption that deserves a joint treasury and commercial review before the next planning cycle.

I use a synthetic payment interruption to explore the difference between restoring a system and restoring a bank's ability to make a reliable promise. The audience follows the first hour of the exercise: incomplete information, competing priorities, an uncertain fallback authority and customers needing an answer. I describe how observers can capture decision delays without turning the exercise into a judgement of individual competence. We consider who should participate, which assumptions should remain visible and what evidence is needed before a finding can be closed. The session also examines investment choices after the rehearsal. Some weaknesses require technology expenditure; others require access, staffing or a decision that senior leaders have avoided making. Participants leave with questions they can use when reviewing their own recovery evidence. This is a governance and operating discussion, not a technical recovery design or an assurance that any organisation will perform similarly in an incident. No live systems or customer records are used in the session.

I explore what happens after a bank decides that connected exposure should fall. A portfolio limit can look clear in a board paper while leaving relationship managers uncertain about renewals, customer notices and acceptable exceptions. The session follows a fictional construction-linked portfolio through a sequenced reduction using maturities and selective refinancing. I describe the income forgone, the arguments for a faster exit and the reasons management retained some exposure for longer. We examine how to distinguish a shared repayment dependency from a superficial sector connection, and how to keep exceptions visible in the overall arithmetic. The audience is invited to consider the chief executive's responsibility for implementation, especially when commercial measures still imply growth. I focus on the questions that make a transition credible rather than prescribing credit policy. Participants should avoid discussing identifiable borrowers; the value lies in examining decision processes and evidence standards that can be applied within their own institution's controls and professional advice.

I discuss how unresolved customer work can disappear between departments even when each team reports acceptable performance. The starting point is a service request that has been processed several times but has not produced the outcome the customer needs. We examine completion rules, reopened cases, aged work and the role of personal escalation. I share the reasoning behind a common case register across sixty-two branches and the decision to establish an honest baseline before comparing performance. The session asks participants to trace one customer journey through their own organisation without disclosing personal information. Where does responsibility transfer, what evidence accompanies it and who remains accountable when the next team cannot act? I also discuss the limits of standardisation: local judgement can improve service, while undocumented workarounds can conceal recurring weaknesses. The purpose is to make operating accountability practical. It is not a promise that a particular workflow or software product will produce the same improvement in another bank.