6 Yellow Flags on Team Culture (And How to Fix Them)
6 Yellow Flags on Team Culture ⚠️
Background
First of all, these aren't red flags. They won't tank your team overnight. But left unchecked, they quietly erode trust, slow you down, and make the team feel less like a team. Here are six yellow flags I've seen — and what to do about them.
1. Decisions Made in Desk Huddles
Quick hallway or desk conversations are great for brainstorming, but when they turn into decision-making moments, people not present feel excluded.
If a huddle leads to a decision, write it down — post a summary on the team channel with the rationale. Decisions that affect others should be visible to others.
2. Over-Tagging Managers and TLs on Slack
Not every message needs a manager's or TL's explicit attention. When we tag them on routine updates, two things happen:
Over-tagging:
- It creates noise for them.
- It signals to the rest of the team that their attention doesn't matter as much.
Default to posting in the channel without tags. Trust that team members read their channels. Reserve direct tags for genuinely urgent or blocking items.
3. Long Sync Meetings That Should Be Async
If a meeting drifts into a 5+ minute deep-dive on a single topic that only involves a subset of attendees, that discussion belongs on Slack or a focused follow-up.
Respect everyone's time in syncs — keep them crisp, use them for alignment and decisions, and move detailed discussions async.
A good rule of thumb: if only 2 people are talking for more than 5 minutes, take it offline.
4. Not Showing Up for Each Other
When a teammate is presenting — whether it's a design review, a demo, or a tech talk — low attendance sends a demoralizing message.
Show up. Even if the topic isn't directly in your area, your presence signals support and builds a culture where people feel safe sharing their work. It also exposes you to parts of the system you don't work on daily.
5. Letting Go of Code Attachment
With tools like Claude, writing code has become faster and cheaper than ever. Code is a commodity; design and judgment are not.
Be open to review feedback that challenges your approach at a fundamental level — even if it means scrapping a PR and starting over. A rewrite informed by good feedback is progress, not waste.
Defend your ideas in design discussions, not in PR comments after the code is written.
6. Silence During Active Incidents
When something breaks or an incident is in progress, post it on the team channel immediately — even if you're actively working on it. Silence during incidents breeds confusion and duplicate investigations.
A short message like "Investigating elevated lag on X — will update in 30 min" goes a long way. It keeps the team informed and opens the door for others to help.
None of these are fireable offenses. They're habits — and habits can change. The best teams aren't the ones that never have yellow flags. They're the ones that notice them early and talk about them openly.
#blog
Comments
Post a Comment