Executive Coach Insights on Building Psychological Safety in London Teams
Psychological safety sounds soft until a project stalls, a key engineer walks, or a regulator’s question exposes a blind spot that the team noticed but kept quiet. In my coaching sessions across London, from Shoreditch fintechs to Canary Wharf banks, the pattern repeats: when people trust they can speak candidly without penalty, decision quality rises, errors surface earlier, and teams move faster with fewer surprises. When that trust erodes, leaders spend their time firefighting. This piece distills what I teach as an Executive Coach and Leadership Coach to London leaders who need results under pressure. No slogans, just practical methods that hold up when deadlines are tight, cultures are mixed, and the hybrid calendar is a puzzle of trains, Teams calls, and school runs. What psychological safety really means Psychological safety is not niceness, consensus, or permission to do weak work. It is a shared belief that someone can take an interpersonal risk, like admitting a mistake or pushing back on a director’s plan, and not be punished for it. The “not punished” part is the hinge. People still face standards and consequences for performance, but they do not face embarrassment, exclusion, or subtle retaliation for speaking up. It looks different in different settings. A London product squad with three time zones may define risk as asking a naïve question on a public Slack thread. A boutique PE firm in Mayfair may define risk as challenging a senior partner’s assumptions in front of the investment committee. The behaviors that foster safety will differ by context, but the foundation remains the same: curiosity, candor, and accountability live together. Why London context matters Psychological Executive Coaching safety is not built in a vacuum. London teams juggle cultural diversity, hierarchy cues, and history. You can have five English speakers in a room and still have mismatches in tone, directness, and power distance because one person grew up in Warsaw, another in Lagos, and a third in Leeds. Add in class markers many pretend do not exist, like accent and school, and you get invisible lines that affect who speaks and who self-edits. Hybrid schedules complicate things. A lot of trust is formed in passing, on a wet Tuesday after a client lunch when you walk back across London Bridge and decide to share a concern. Remote-first setups limit those micro-moments. London’s commute amplifies the challenge. People who live an hour out of the city on a packed train are pragmatic about which days they come in. If your team only experiences one another through one-hour calls, you must engineer trust more deliberately. Regulation and reputation also weigh on leaders here. Financial services and health tech face heavy oversight. Fear of saying the wrong thing to the wrong stakeholder makes some managers clamp down on debate. Ironically, those environments benefit the most from psychological safety because silent teams miss risks that later get very public. The cost of getting it wrong I have seen teams in London carry a 10 to 25 percent productivity drag because work cycles include rework someone spotted but did not raise. Voluntary attrition moves in the same band: when teams feel unsafe, high performers Leadership Coach London who have options take them. Vendors and contractors, an essential part of the London ecosystem, either withhold concerns or price the risk. Clients notice. Auditors notice. Recruiting gets harder because your reputation follows you on WhatsApp groups and in private DMs. Fixing a low-safety culture typically takes measurable effort for 3 to 6 months before you see steady results. Leaders who expect immediate improvement often abandon the plan in week four. The teams that stick with it save cost later because they institutionalize habits that catch issues early. I am a Business Coach by background, and I approach this as operational risk management with human tools. What it looks like when it works You hear fewer prefaced apologies and more specific observations: “I think the pilot criteria miss edge cases in small retailers.” People ask for help earlier, and the help arrives without side comments. Meetings start with context, not theatre. Leaders summarise what they heard and what they decided, with an audit trail others can see. Slack threads have more questions than sarcasm. In numbers, the teams I have coached that invested in this work typically show one or more of the following within a quarter: Fewer last-minute escalations, often down by 20 to 40 percent. A measurable increase in peer-to-peer code or proposal reviews, which correlates with lower defect rates. Shorter cycle time, not dramatic at first, but a steady 5 to 10 percent decline across sprints. These figures are directional and based on client reporting, but they hold across sectors when leadership behaviour changes and processes reinforce it. Behaviours that break safety, often unintentionally Not all harm is loud. The fastest way to kill psychological safety is with micro-signals that say, “your input carries risk.” Examples from my London coaching notes: A senior partner invites feedback then responds first with a counterargument. Others learn that speaking up triggers debate they are not paid to win. A manager praises only “polished” updates. Ambiguous data disappears from weekly check-ins, and surprises grow. Jokes about accents or regional stereotypes slide by unchallenged. People clock who is “in” and who is not. Decisions change after the meeting, with no visible rationale. Team members learn that speaking in the room does not actually matter. None of these require malice. All of them are fixable with structure and habit. The leader’s role: modelling at the moment of risk A single scripted ritual will not fix culture. Repeated moments, handled consistently, will. I coach executives to look for three recurring moments where their behaviour either builds or erodes psychological safety. First, the moment someone brings unwelcome news. Your face, your first sentence, and your follow-up question set the norm. The most effective leaders I coach practice a neutral opening line they can deliver even when irritated: “Thanks for surfacing this early. Walk me through what you know and what you need.” It sounds simple. Under pressure, it is a discipline. Second, the moment of dissent. When someone disagrees with your plan, the reflex is to defend it. Instead, restate their point accurately, ask two clarifying questions, and only then respond. This is not performance. It is a reliable way to ensure the team sees disagreement as a contribution, not a threat. Third, the moment after a mistake. Blame hunts for a target. Leaders who pause and run a small, structured review of what happened, what signals we missed, and what we are changing, reduce repeat errors and stigma. They also retain the people who learn fast. A short meeting design that helps candour Here is a compact format London teams have used to shift dynamics within weeks. Use it for project reviews, not every meeting. Keep it under an hour. Start with a one-sentence purpose and the decision you hope to reach. Share a two-minute “facts only” update from the owner. Do a round where each attendee states one risk or open question, no cross talk. Ask the most junior or least tenured person to speak first in the open discussion. Close with decisions, owners, and the timestamped reason, captured in writing. Teams like this because it keeps theatrics low and fairness high. The inversion, asking the least powerful to start, does two things. It prevents early anchoring from senior voices, and it signals that rank does not trump insight. It also works well on calls where cameras are off and power dynamics become even stronger. The checklist I give first-line managers Managers in London often have high spans of control, ten to twelve direct reports, with hybrid calendars and limited time for training. You do not need a sweeping program to begin. Start with a daily repeatable set of behaviours that compound. Ask one good question per meeting that invites challenge, such as, “What are we not seeing because we are too close to this?” Acknowledge uncertainty in your own updates once a week, in front of the team. Praise a specific learning behaviour, not just outcomes. For example, “Thanks for running a small test and bringing the negative result quickly.” Write and share decisions with rationale in a place others can find. Close 1:1s by asking, “What felt awkward or risky this week?” then sit with the silence for ten seconds. These seem small. They pull on the right levers: permission to challenge, visible modelling of not-knowing, recognition for smart risk, traceable decisions, and safe space for the awkward truth. Edge cases: high-stakes environments and fast-growth teams Some roles in London, like trading, incident response, or surgical teams, operate with low error tolerance. Leaders sometimes ask if psychological safety applies there. It does, but the cadence differs. You build safety before and after the moment of action, not during it. In the moment, roles and commands need to be crisp. Before, you run pre-mortems and scenario drills that invite the most junior person to name failure modes. After, you run blameless but rigorous debriefs. Fast-growth startups face a different edge case. Speed masks safety gaps because results still arrive. By the time they feel the gap, it is harder to correct because habits have set. I often encourage founders to designate a rotating “red team” voice in sprint reviews, with explicit permission and a timebox to challenge the plan. It keeps debates healthy without bogging the team down. Bronwyn Leigh Crawford Leadership Training and Coaching 43 Upper Park Rd Camberley Surrey GU15 2EG United Kingdom Phone: +44 7503 082377 How to measure it without a four-month survey You can over-instrument culture. Start small, track what matters, and triangulate. Pulse questions in your weekly check-in, two items only: “I felt safe to speak my mind this week” and “I received usable feedback.” Use a 1 to 5 scale and watch trends, not single points. Track surfacing time for risks. If issues appear closer to deadlines, safety is narrowing. Look at who speaks in meetings. Rotate who opens, and note whether names at the edge of the org chart contribute more after you change the format. Correlate safety pulse trends with defect rates or cycle times. You should see modest but steady improvements as safety improves. None of these require extra software. A spreadsheet works. The point is to give your team proof that the work is real and that you will act on what you learn. A note on language, accent, and exclusion London’s diversity is the city’s strength. It can also become the quiet reason someone self-censors. If you are a senior leader who went to a well-known school, you may not notice how quickly a new hire with a different background adjusts their tone in your presence. Correcting this does not ask you to perform false modesty. It asks you to remove unnecessary friction. Small practices help. Slow your speech slightly. Avoid idioms that do not translate. If you reference British TV or cricket, pause and offer a sentence of context. When someone says, “Sorry, could you repeat that,” treat it as a sign of engagement, not a lack of preparation. When a joke targets background, accent, or religion, do not let it slide. You do not need to make a speech. “Let’s keep it on work,” said promptly, resets the line. Contractors, vendors, and the extended team Many London teams are blended. Psychological safety cannot stop at the payroll boundary if you expect real accountability. Invite key vendor leads to the pre-mortem. Share decision logs with them. When a contractor raises a risk, treat it as a contribution to the project, not a sales ploy. If you punish or ignore it, word will travel across the supplier market, and the next vendor will be more careful with you than with your competitor. That costs you money. The role of training, and its limits Good Leadership Training can accelerate the shift, especially when it focuses on practice rather than slides. I run sessions where executives role-play hot moments, get real-time feedback, and then set micro-commitments for the week. Training helps, but it does not replace repetition in the field. You will need line managers to adopt two or three behaviours and repeat Business Executive Coaching them dozens of times before teams trust the change. If you hire an Executive Coach or a Leadership Coach, be clear about outcomes and cadence. Do not outsource culture. A coach can observe your meetings, give you private feedback, and hold you to your commitments. The change still shows up in your voice, in the room, when a director challenges you and everyone waits to see how you respond. Correcting misuse: safety is not a shield against standards Sometimes people weaponise psychological safety to avoid accountability. I have heard, “I do not feel safe with how direct this feedback is,” used to derail clear performance conversations. This is where leaders must hold the line. Safety means you will be treated fairly and respectfully while the work is judged against explicit standards. It does not mean the work is beyond critique. To keep this clean, separate person from process. Anchor feedback in observable behaviour and impact, not identity or intention. Use examples: “In last Friday’s client call, you committed to a timeline without checking engineering capacity. That put us at risk with the regulator. Next time, pause and confirm. If the client insists, escalate in the moment.” When you speak this way, people feel respected, and you protect performance. Scripts that help under pressure Preparation beats improvisation when meetings heat up. Here are phrases leaders I coach keep handy, especially in cross-cultural groups. When someone offers a weak objection: “Say more. What did you notice that triggered that concern?” When a junior person hesitates: “I am interested in your take before we move on.” When you made a call that missed: “My decision last week created extra work. I am correcting that, and here is what I learned.” When the room gets defensive: “Let’s separate intent from impact. What happened, and what do we change?” When a decision must be final: “We are deciding now. The call is X, for reasons A and B. If new data appears, we will revisit Thursday.” The point is not to sound scripted. The point is to remove panic and model how to hold tension with composure. A few London case notes A fintech in Old Street had a pattern of last-minute design changes that blew up sprints. Product felt steamrolled by sales commitments, sales felt judged, engineering felt stuck in whiplash. We ran four weeks of structured reviews with the meeting format above, added a visible decision log in Confluence, and gave sales two courtesy vetoes per quarter with a written rationale. Within two months, cycle time shortened by 8 percent and Friday panic messages dropped sharply. Psychological safety rose because decisions felt traceable, not arbitrary. A global asset manager in Canary Wharf struggled with analysts from non-UK backgrounds speaking up in committee. We adjusted the agenda so the two most junior analysts opened risk discussion with five minutes each. Senior partners held questions until both finished. The content quality improved, but the real change came in reputation. Within a quarter, recruiting diversity rose, tracked by offer accept rates from candidates who had previously declined. The firm did not soften standards. It opened the floor. A hospital technology provider, split across London and Bangalore, had long email chains where engineers hinted at problems but did not state them. We banned sarcasm in written updates and introduced a simple red-amber-green format with a weekly 20-minute “red room” where only red items were discussed, no blame allowed. The first month was awkward. In month two, someone flagged a data mapping issue that would have delayed a pilot by three weeks. They caught it with six days to spare. Building the habit loop Habits stick when they are small, obvious, and rewarding. Psychological safety emerges when leaders attach visible reward to candour and inquiry. That reward can be as simple as public praise for an early flag, or as structural as counting “issues raised before sprint planning” as a positive KPI on performance reviews. The key is consistency. If someone gets burned once for speaking up, your next five positive cues will barely move them. I often ask leaders to keep a weekly micro-journal. Ten lines, no flourish. Note where you encouraged candour, where you missed it, and what you will try next week. Over twelve weeks, patterns emerge. Perhaps you suppress debate near month-end because numbers are due. Or you cut off questions when a board member is visiting. Awareness gives you the chance to plan rather than react. Pairing candour with clarity Candour without direction becomes noise. Safety should sit next to strategy. If your team knows where you are going, what constraints are non-negotiable, and which trade-offs you prefer, their input becomes sharper. London teams spend a lot of time aligning with external forces, from regulators to clients. Translate those external demands into team-level constraints and choice points. People can handle tough news if they understand the playing field. I advise executives to write a one-page “operating spec” and share it quarterly. Include three items: the north star for the next quarter, the constraints you cannot change, and the places you want extra scrutiny. Invite the team to annotate it with questions. This simple document becomes a reference, and it channels candour into the areas you most need it. The 90-day arc I recommend Although I avoid rigid templates, a rough sequence helps busy leaders organise their effort. Weeks 1 to 2: Baseline with a short pulse, observe three recurring meetings, and gather a few candid comments in 1:1s. Share why you’re focusing on psychological safety, using concrete language about decisions and risks. Weeks 3 to 6: Introduce the meeting format for one or two critical forums. Start the manager checklist. Begin keeping a decision log. Run one pre-mortem on a high-visibility project. Measure speaking time and participation, at least informally. Weeks 7 to 10: Expand practices to adjacent teams. Invite a vendor lead into a pre-mortem. Run a short retro on the safety work itself: what feels better, what still feels risky. Adjust based on feedback. Keep publishing weekly decisions with rationale. Weeks 11 to 12: Review metrics. Share wins and misses. Identify two practices to standardise and one to drop. Celebrate specific behaviours you want repeated, naming people and moments. This arc is not magic. It is consistent with how habits form and with the operating tempo of London firms. When to bring in external help You can make solid progress alone. Bring in a coach when stakes are high and speed matters, or when you cannot see your own patterns. An Executive Coach with real board and line experience can shadow your meetings, surface blind spots, and provide steady accountability that your peers, who are fighting their own fires, cannot. When you commission Leadership Training, insist on practice, feedback, and follow-up, not lectures. Pair training with measures, and involve the people who quietly shape culture: PAs, project managers, and senior ICs who run the rituals. Final thoughts from the field Psychological safety is not a corporate mood. It is an operational advantage that compounds. In London, with its blend of intensity, diversity, and formality, you need to earn it through repeated, observable behaviour. The tools are simple. The work is not. Leaders who practice under pressure, write decisions down, and reward early warnings build teams that speak the truth faster and ship better work. That is the point. It is also what your clients, your regulators, and your future hires will quietly expect. If you lead a team here and want a place to start tomorrow, pick one meeting, run the five-step format, and close by naming one person who made the work safer by saying something hard. Then do it again next week. The rhythm builds the culture. The culture handles the pressure.