Building Strong Teams with Coaching Practices

Many managers think coaching is something you do during quarterly reviews, a formal ritual where you deliver feedback, set goals, and hope something sticks. That’s not coaching, that’s performance management.

Real coaching happens in the everyday moments: when someone’s stuck on a decision, when they’ve just failed at something, when they’re about to present to leadership for the first time and you can see the panic in their eyes. Coaching isn’t a process, it’s a muscle you build by actually helping people get unstuck.

Building Early Foundations

What to Prioritise

When you’re building a team from scratch, every hire feels critical. Because it is. You’re not just filling a role; you’re establishing norms that will persist long after you hire person number 20. The question isn’t “can this person do the job?” It’s “will this person make everyone around them better?”

The teams that scale well prioritise learning velocity over current skill level. Not “how good are they now?” but “how quickly do they get better?” Someone who’s at 70% capability but grows 5% every month is a better hire than someone at 90% who plateaus.

Here’s how this shows up in practice: I worked with a startup that hired a junior PM straight out of university. No product experience. The founders debated whether this was reckless, they needed someone who could contribute immediately. They hired her anyway because she asked exceptional questions, synthesised feedback instantly, and demonstrated learning from every conversation.

Twelve months later, she was running the largest product. The “experienced” PM they hired a year before had left after six months because he couldn’t adapt to the organisation (I know, that was me, lol). Experience is great, but learning velocity matters more in early-stage environments.

Quick Wins That Establish Culture

The first few months set the tone for how your team operates. You can’t build comprehensive coaching programmes when you’re five people and fighting for survival. But you can establish simple practices that signal how you’ll work together.

Daily unblocking standups that aren’t status theatre. Not “here’s what I did yesterday”, that’s email. Instead: “here’s where I’m stuck, here’s what I need.” Make it safe to admit you don’t know something. The person who says “I’m confused about our pricing strategy and it’s blocking me from writing this feature spec” is more valuable than the person who pretends everything’s fine while quietly struggling.

I watched a founder establish this norm by being vulnerable first. In the first standup, instead of projecting confidence, he said: “I’m stuck on whether we should focus on feature velocity or stability this quarter, and it’s affecting every planning conversation. I need help thinking through the tradeoffs.”

Everyone else followed his lead. Within a week, the standup became the place where real work happened, decisions got made, blockers got cleared, not the place where people performed busyness.

Explicit decision rights. Who can make what decisions without approval? This sounds like corporate bureaucracy, but the absence of clarity is worse. When nobody knows who decides, either everything gets escalated (slow) or people make conflicting decisions (chaos).

The early-stage version is simple: “You own decisions in your area unless they’re irreversible or expensive. If you’re unsure, bias toward making the decision and telling me afterward rather than asking permission first.”

This does two things: it gives people autonomy (good for learning), and it creates a feedback loop (they make a decision, see the consequence, learn). Coaching happens through iteration, not abstraction.

The Startup Reality

Resource Constraints

You don’t have budget for fancy L&D programmes. You probably don’t even have budget for conference tickets. Coaching in resource-constrained environments means getting creative about learning opportunities.

Use customer conversations as training ground. Every early-stage team does customer development. Turn those conversations into coaching moments. Instead of the PM doing all customer calls solo, bring engineers and designers. Afterward, debrief: What surprised you? What did we miss? How should this change what we build?

This serves double duty: you get better customer insights (multiple perspectives), and your team develops customer empathy directly rather than filtered through the PM’s interpretation.

Speed Versus Quality Tradeoffs

Startups worship speed. “Move fast and break things” and all that. But speed without learning creates chaos. You ship quickly, fail quickly, and don’t extract any insight from the failure because you’re already onto the next thing.

The coaching challenge in fast-moving environments: how do you create space for reflection without killing momentum?

The answer I’ve seen work: retros that are actually retrospective, not performative. Most retros are complaints disguised as process improvement: “Communication could be better.” Great, what does that mean? Nobody knows, so nothing changes.

Effective retros focus on specific recent decisions and ask: knowing what we know now, would we make the same choice? If not, what would we do differently?

Example: A team ships a feature fast but discovers users are confused by the UI. The performative retro: “We should test with users more.” The effective retro: “We skipped user testing because we thought speed mattered more. The feature sat broken for two weeks while we fixed it. Total time: three weeks. If we’d spent two days on user testing upfront, we’d have shipped in two weeks total. For the next feature, we’ll test critical UI before launch.”

That’s coaching disguised as process. You’re teaching the team to recognise patterns and adjust. Do this consistently and speed becomes sustainable instead of chaotic.

Scaling for Growth

When to Formalise

The danger of early-stage informality is that it doesn’t scale. What works with five people, everyone in one room, osmotic learning, ad-hoc mentoring, breaks at 20 people. You can’t be in every conversation. New hires don’t absorb culture through proximity.

The signal that you need to formalise coaching: new hires take longer to ramp up than your earliest hires did. Not because they’re less capable, because the tribal knowledge that early employees absorbed informally is now locked in people’s heads.

At this inflection point, you need lightweight structure. Not a corporate L&D programme, simple practices that transfer knowledge systematically.

Document decisions, not just outcomes. Early teams do this naturally through Slack conversations and meeting notes. As you grow, those conversations fracture across channels. You need a place where critical decisions are recorded with context: what we decided, why, what alternatives we considered, what we’ll watch to know if we were right.

This serves immediate tactical needs (new hires can see how decisions get made) and long-term strategic needs (in six months when the decision turns out wrong, you remember why it seemed right at the time).

Pair new hires with culture carriers, not just domain experts. The early employees who exemplify how you want the team to operate. Give them explicit mentoring responsibilities. Not “be nice to new people.” Specific: “Spend 30 minutes a day with Alex this month answering questions about how we work.”

The best culture carriers aren’t necessarily the most senior. They’re the people who embody the behaviours you want to scale: the engineer who writes great docs, the designer who brings research into every conversation, the PM who’s brilliant at synthesising feedback.

Team Evolution

Teams that start together often struggle as the company grows because roles that were fluid early on need to become more defined. The PM who used to write code and do customer support now needs to focus on strategy. The engineer who used to participate in product decisions needs to spend more time on infrastructure.

These transitions are painful. People feel like they’re losing scope, losing impact. Coaching through this requires helping people see that depth enables more impact than breadth, but only if they’re working on the right things.

Key Takeaways

Here’s what actually matters:

• Coaching happens in everyday moments, not formal sessions. The best coaching is helping someone get unstuck right now, not delivering feedback in a quarterly review. Build the muscle of asking good questions instead of giving answers.

• Prioritise learning velocity over current capability in early hires. Someone who’s 70% ready but grows quickly beats someone who’s 90% ready but plateaus. Early teams need people who get better, not people who already know everything.

• Make it safe to be stuck by being vulnerable first. If you want people to admit blockers, you need to model it. The leader who says “I don’t know” gives permission for everyone else to be honest about what they’re struggling with.

• Use customer conversations as coaching opportunities. Bring different team members into customer calls. The learning from direct exposure beats filtered insights every time.

• Formalise when new hires ramp slower than early hires did. That’s the signal that informal knowledge transfer isn’t working anymore. You need lightweight structure—documented decisions, explicit mentoring pairs—to scale culture.

Getting Started This Week

Pick one person on your team who’s currently stuck on something. Instead of telling them what to do, ask: “What’s your instinct on this? What would you decide if I wasn’t here?”

Listen to their answer. Chances are it’s 80% of the way to a good decision. Coach the remaining 20%—help them see the blind spots, pressure-test their assumptions—but let them make the call.

Do this once this week. See what happens. That’s coaching.

Have questions or thoughts? Get in touch - I’d love to hear from you!