--- title: "Build the Ship You Want to Sail On: Culture and Giving Back" author: "Harry" published: 2026-10-31T04:50:51.238Z updated: 2026-10-31T05:08:38.186Z category: "Career & Teams" tags: [] canonical: "https://fxblog.dev/posts/how-to-build-a-good-team-culture" --- # Build the Ship You Want to Sail On: Culture and Giving Back ## Key takeaways - Culture is what a team repeats every week, not the values written on a slide. - Recognition works when it is specific, timely and in the form the person prefers. - Teams where people feel safe to speak up do better work; a lead builds that safety by how they react to bad news. - Mentoring gives advice; sponsorship puts someone's name forward for real opportunities. Leads should do both. - Giving back beyond your team, through a talk, a doc or a mentee, turns what you learned into the next person's head start. > **TL;DR** If your team's good habits live only in you, the team works only while you're in the room. How to build a good team culture: pick a few habits and repeat them every week. Thank people specifically, answer bad news calmly so it keeps arriving early, put people forward for real opportunities, and hand on what you learned beyond your own team. > > **Do this:** This Friday, thank one person specifically, in the way they prefer to be recognised. Part 4, **Manage the Team: Goals, Trust and Delivery**, ended with a good quarter and a question Pip couldn't shake: what is she building beyond the work, and what would still be there if she moved on tomorrow? She asks Kit over Friday lunch. Kit, unusually, puts his chopsticks down. **Dev Voyage: Uncharted Waters, in five parts:** 1. **From Best Engineer to First-Time Lead** 2. **Hire and Grow Your Crew** 3. **One-to-Ones That Matter, and Handling Conflict** 4. **Manage the Team: Goals, Trust and Delivery** 5. **Build the Ship You Want to Sail On: Culture and Giving Back** (you are here) ## Culture is what you repeat > **Note** > > **Kit:** We tell each other when something's broken. Fast. We thank people by name. And nobody eats alone on Fridays. > **Pip:** Those are habits. > **Kit:** What's the difference? Not much. Culture is what happens every week when someone ships, breaks something, or arrives on day one. Every moment that mattered on Pip's voyage was a habit someone kept: - Kit agreeing her 30-60-90 plan in week one, then checking it every two weeks. - Pip thanking Brock in the channel for a one-line answer. - Kit saying "thanks for shouting fast" the Friday she broke checkout. - Brock adding **praise:** to his reviews after the clash with Quill. ## The second after bad news When Google studied its teams in Project Aristotle, psychological safety mattered most of the five factors it found. Amy Edmondson defines it as a shared belief that the team is safe for interpersonal risk taking. re:Work puts it in a teammate's words: "If I make a mistake on our team, it is not held against me." A lead builds it mostly in the second after someone brings bad news. ![When someone brings bad news: a calm thanks teaches the team to report early; blame teaches them to hide it, and the next problem arrives later and bigger](https://fxblog.dev/media/01a1904b-bd88-7716-a987-d2545caf7230/1600) _The second after bad news_ | When someone says... | Builds safety | Destroys it | | ----------------------------- | ---------------------------------------------- | ------------------------ | | "I broke the build." | "Thanks for saying it fast. What do you need?" | "Again?" | | "I don't understand this." | "Good question. Who else might not?" | "It's in the docs." | | "I think your plan is wrong." | "Tell me why." | A cooler tone for a week | > **Tip** > > Once a month, tell the crew about a mistake you made and what you changed. When the lead goes first, everyone else finds it easier. ## Mentor, then sponsor "Great job, team" is gone by lunch. "Quill, the zero-price test caught a bug that would have refunded every free order" is remembered. Pip had asked each person in their first one-to-one how they like to be recognised, as Lara Hogan suggests. Brock: in writing, never in a meeting. Quill: in standup. Lara Hogan also separates two roles leads blur: - A mentor gives advice. - A sponsor spends their own standing to put someone forward, naming them in rooms they aren't in. Pip had mentored Quill for months. This quarter, when the Admiral asked who could present the discount service to the client, she sponsored him: "Quill built it. He should present it." He did, nervously, and well. ## The map changes hands Pip gave a talk at a local meetup on the question that gets answered in one line, and turned her 30-60-90 template and interview scorecard into a handbook page for the next lead. At the end of the year, on deck at sunset, Kit held out a rolled-up chart. > **Note** > > **Kit:** The map. It's yours now. > **Pip:** Where are you going? > **Kit:** The whole fleet! You run the Red Fox. Then Quill, at her elbow: "The new deckhand starts Monday." "Get the 90-day plan," said Pip. "And biscuits." ## Try it Every Friday, fifteen minutes: 1. Thank one person specifically, in the way they prefer. 2. Name one person for an opportunity they weren't in the room for. 3. Answer one newcomer's question in public, so it stays answered. 4. Once a month, say one of your own mistakes out loud. On Monday a nervous young crab arrived with a laptop still installing updates and 200 unread messages. Quill met him at the gangway and handed him a one-page plan. If you're at the start of your own voyage, it begins with **Your First 90 Days: How to Join a Crew Without Sinking**, in Dev Voyage: Calm Sea. ## Read this with your AI ```text Read the post "Build the Ship You Want to Sail On: Culture and Giving Back". 1. I'll list what my team does every week. Tell me which habits build safety and which erode it. 2. Rewrite these three thank-you messages so each is specific: [paste] 3. Suggest one person I could sponsor this month, and the opportunity, given: [team and context] ``` > **Success** > > You know how a culture is built from repeated habits, how to make bad news safe, and how to give back beyond your team. The voyage is complete; the next one is yours to lead. ## FAQ ### How can a team lead improve team culture? Pick a few habits and repeat them every week: thank people specifically, react calmly to bad news, run a blameless review after mistakes, and give newcomers a plan and a buddy. Culture changes through what you do repeatedly, not what you announce. ### What is the difference between a mentor and a sponsor? A mentor gives advice and shares experience. A sponsor uses their own influence to put someone forward: recommending them for a project, a talk or a promotion when they are not in the room.