■ · People
Team, trust and culture
Culture isn't the values on the wall. It's what people actually do when the owner isn't watching: whether they speak up, admit mistakes, keep promises and hold each other to the standard. That's built, or broken, by the owner every day. The upside: it means you can start shaping it today.
Safe to speak up
Harvard professor Amy Edmondson defined team psychological safety as a shared belief that the team is safe for interpersonal risk taking: asking questions, admitting mistakes, disagreeing. In her study of 51 work teams, psychological safety was linked to the learning behavior that drove team performance.
Google's Project Aristotle, a study of what made its teams effective, reached a similar conclusion. Who was on a team mattered less than how the team worked together, and psychological safety was the most important of the five factors it identified. The others were dependability, structure and clarity, meaning, and impact.
For a small business this matters in a very practical way. If people are afraid to tell the owner bad news, the owner finds out late. That's how small problems become a crisis.
■ How teams break down
Five problems that build on each other
Patrick Lencioni's The Five Dysfunctions of a Team describes problems that stack, each one making the next more likely. In plain terms:
| Problem | What it looks like | What the owner can do |
|---|---|---|
| 1. No trust | People hide mistakes and weaknesses | Admit your own mistakes first, openly |
| 2. Fear of conflict | Polite meetings, real arguments in private | Ask for disagreement. Debate ideas, never people |
| 3. No real commitment | People nod, then don't follow through | End every decision with who does what by when |
| 4. Avoiding accountability | Nobody calls out missed standards | Make standards visible: scorecards, checklists |
| 5. Ignoring results | Personal comfort matters more than team results | Keep the team's results on the table every week |
Care personally, challenge directly
Kim Scott's Radical Candor describes good feedback as two things at once: caring about the person and being willing to tell them the truth. Care without challenge becomes being too nice to help. Challenge without care becomes harshness. Neither builds a strong team. This is the same balance as running a tight ship: firm on the standard, decent to the person.
Values that actually mean something
Most company values are words nobody can argue with, like "integrity" or "excellence." Useful values describe behavior and help make decisions. "We tell clients about mistakes before they find them" is a value you can hire, train and hold people to. Write three to five like that, and use them in hiring and reviews.
How healthy is your team?
Check each one that's true most of the time. Better yet, ask your team to answer too.A team of detectives, not a team of yes men
The goal is a team that will tell you your plan has a hole in it. That only happens if you've rewarded it before.
Clear standards make accountability fair. When the standard is written down, holding someone to it isn't personal.
Invite the team to interrogate Class II and III decisions. They see problems you can't, and they commit to plans they helped test.
Most team problems are conversations nobody had. Clear at Work covers how to have them.
Go deeperCase file, step-by-step how-to, common mistakes and questions to work through
Case file: The team that stopped speaking up
A fictional example
Diane is the nurse manager of a 22-bed hospital unit. Her team is skilled, but she noticed something worrying: in shift huddles, nobody raised problems. Then she learned that a near-miss with a medication had happened the week before, and two nurses had seen the warning signs but didn't say anything.
When she asked one of them privately, the answer was honest: "The last time someone raised a concern in huddle, the charge nurse made them feel stupid. Nobody's going to do that again."
Diane started with herself. In the next huddle, she shared a mistake she'd made early in her career and what she learned from it. She started ending every huddle with the same question: "What's one thing that could go wrong today?" When someone raised a concern, she thanked them by name, even if it turned out to be nothing.
She also talked privately with the charge nurse, not to blame her, but to explain what was happening: "When people get shut down, they stop warning us. I need you to help me make it safe to speak up." She coached her on a simple response to any concern: "Thanks for raising that. Tell me more."
Over the next three months, people raised more concerns in huddles, and more small problems were caught before they became big ones. Diane said, "The team didn't get braver. The room got safer."
How to build a team people speak up in, step by step
- Go first. Admit a mistake or an uncertainty yourself. It shows that it's safe.
- Ask direct questions that invite problems, like "What could go wrong?" and "What am I missing?"
- Thank people for speaking up, every time, especially when the news is bad.
- Respond to concerns with curiosity: "Tell me more," not "That's not a problem."
- Close the loop. Tell people what happened because of what they raised.
- Address put-downs privately and quickly, including from senior people.
- Keep the standards high. Safety to speak up is not the same as low expectations.
"Before we go: what's one thing that could go wrong today, or one thing you're unsure about? There's no wrong answer. If you saw it, I want to hear it."
Common mistakes and how to fix them
| Mistake | Fix |
|---|---|
| Saying "my door is always open" and waiting | Ask directly and often. People rarely walk through an open door alone. |
| Reacting badly to bad news | Thank the messenger first. Solve the problem second. |
| Ignoring a senior person who shuts others down | Coach them privately and quickly. Others are watching. |
| Confusing a safe team with an easy team | Keep high standards and high support together. |
Questions to work through
- When did someone on your team last bring you bad news? How did you react?
- Who on your team rarely speaks in meetings? What might be stopping them?
- What's one mistake you could share to show it's safe to admit them?
- Has anyone been shut down for raising a concern? What did others learn from it?
- How do you close the loop when someone raises an issue?