Lifehacks for Team Coaches

None of this is new methodology. These are the calls we make in almost every project. See the Team Coach page for the role itself, and use this page as a checklist: jump to the situation you are in, and follow a link when you want the reasoning.

1. Living your role

Two habits that separate knowing the role from living it.

Be clear about your three perspectives. We are open with the team from the start about the three perspectives (trainer, mentor, coach) that we will deliberately switch between as the situation asks. Mentoring and coaching feel natural and need no announcement, but stepping back into the trainer role mid-work can read as inconsistency, so there we flag it: "trainer hat on for ten minutes, then back to you." (Team Coach)

The sprint is one lap, not the race. We keep building the team's own skills even when it slows this iteration down, because phase IV of Business Design is a marathon of several sprints and only a growing team finishes it. Handing over the answer is faster today and more expensive every time after. (Dream Big, Act Small)

2. Stakeholder management and decisions

How we manage sponsors and stakeholders so the team's work survives contact with the organisation.

Small room, real decision. We keep the D-Day audience as small as the organisation allows, because every extra person makes a decision less likely. The call has to fall in the room. A sponsor who takes it away to "align internally" rarely brings it back. (Decide Workshop, Project Sponsor)

No first reactions in a crowd. We pre-frame every manager one-on-one before the Decide Workshop, because a room full of them produces political noise, status fights and groupthink. An objection we hear in a corridor costs nothing — the same one at D-Day costs the team its decision. (Decide Workshop, Sponsor's Sneak Preview)

Clear the critical flanks with the sponsor. We identify the politically critical areas with the sponsor before we start, and agree together on a workable mitigation or workaround as we go. Using existing customer contacts is often one of the first escalations, because the team will be talking to customers within days, but it is rarely the only one. Without that realistic upfront clarification the team could be blocked in constant escalation. (Alignment with Project Sponsor, Kick-off Workshop)

Rough on purpose. We keep early material deliberately unpolished, because a slick interface makes an idea look more thought-through than it is and the sponsor then decides on the polish instead of the insight. An early prototype or visualization is not a beauty contest, it fulfills a sole purpose - enabling a decision. (Demo or Die, Prototyping)

3. Setting up a project

Everything that has to be right before the kick-off — where we have the most leverage and use it the least.

The charter is our contract too. We read the charter as our own contract, not just the team's briefing, because our mandate for everything we do with the team comes from it. Before we say yes, we check four things: is the objective concrete, is it consistent with what the sponsor says out loud, is it clear enough to act on — and do we have the capacity we are about to promise? (Project Charter "Sprint", Project Charter "Exploration")

Clear priority, not wishlist. We agree with the sponsor on a single sprint priority. It can either be business results, capability building, or a stress test of the system, because optimising for all three optimises for none. And we say it plainly: a team that aims to compete in champions league will not build the capability to do so during the game. Neither will a business design team deliver exceptional value when it's not equipped with right capabilities or needs to operate in an environment not fit for the purpose. (Setup, Organisational Context)

Small teams and an outside perspective. We cap the team at five members max and insist on one member decoupled enough to contradict the others. A larger team is already unmanageable and a polite team drifts into groupthink. We screen out anyone too grand for tasks outside their comfort zone. (Project Team, Roles)

4. Working with the team

The situations that eat projects: no time, no courage, no progress, and the things nobody says out loud.

"I'll make it work" is a no. We treat "I'm very busy, but I'll make it work" as a red flag, not a commitment, because good people are always busy. The real question is never capacity, it is priority. We book a one-on-one, open the next two weeks of the calendar together, and take something out. (Kick-off Workshop, Review Workshop)

Exploration as a test of patience. Teams used to fast results can find divergent exploration deeply uncomfortable, so we name the pattern and create awareness for the many micro-convergences along the way: every insight is a small landing that opens the next set of questions. (Discover, Design Workshop)

Name the observation first. We do everything to anticipate and name critical situations or biases before the team walks into them, because afterwards it is only a post-mortem. We continuously build our experience and use the co-coach to reflect about project observations and extend our own library of interferences and interventions.

Reality might kill every good intention. We watch for the gap between designing an experiment and running it. Teams debate hypotheses, experiments and thresholds with ease, then stall at execution because they fear how the people on the other side will react. So we name it early when the team defines the experiments and we stay close during the execution, putting the rollercoaster of emotions into context, that might happen on experiment feedback. (Validate, Validate Workshop)

First hand customer feedback. We prepare our team to sit in front of customers themselves, because that is where uncomfortable answers become undeniable. Hand it to an agency or a synthetic AI panel and you get a clean document nobody defends at D-Day. (Customer & User Interview, Competitive Landscape, AI Tools for Research)

When it stalls, go one-on-one. We work down a ladder when the team stalls: first a one-on-one. What exactly is blocking you? Only then, redistribute inside the team, call for a GTD Workshop to close tasks together in a day, and as a final escalation the sponsor. Jumping straight to the sponsor costs us the team's trust. (Review Workshop, GTD Workshop)

Name the elephant before the jury does. We surface personal and political tension as early as we become aware and not only at the D-Day, because it otherwise appears at the worst possible moment — in front of the jury. An unaddressed conflict doesn't only cost the mood; it costs the credibility of the recommendation the team is about to make. (Review Workshop, Kick-off Workshop)