The Habits That High-Performing Teams Never Post About (But You’ll Recognize Immediately)

I wanted to share something with you today.

Let’s start here.

Marcus — let’s call him Marcus :) — had been a manager for eleven days when he called his first all-hands.

He’d prepared. Color-coded slides. A “vision statement” he’d rewritten four times. He even showed up early to test the projector, which — and I respect this — was the most useful thing he did all week.

The meeting lasted ninety minutes. At the end, someone asked “so what are we actually doing differently starting Monday?” and Marcus said “great question” and then answered a completely different question.

Nothing changed. The meeting had a follow-up meeting. That meeting had a recap email. The email had action items nobody owned.

Photo by Cherrydeck on Unsplash

Three months later, Marcus was the most exhausted person in a company.

I don’t tell you this to make fun of Marcus. I tell you this because Marcus is every team that has confused talking about work with doing work. I’ve met multiple Marcuses across my career. You probably know a Marcus. You might be a Marcus. Most companies are running on full Marcus energy right now and calling it culture.

But here’s what’s wild — and why you should send this to whoever runs your Monday standups — the teams that actually move fast aren’t doing anything exotic. They’re not using some framework you’ve never heard of. They’ve just quietly built a set of habits that most teams never bother to name, let alone practice.

I’m going to name them for you.

1. They stopped using meetings to share information. Like, completely.

Think about the last status meeting you sat in. Not led — sat in. You already knew most of what was being said, or most of it didn’t even matter to you at that point. You were waiting for the one update that mattered. It came at minute forty-three. You could have read it in eight seconds.

Elite teams figured out that information sharing and problem solving are two completely different activities, and mixing them in the same room is the reason your Thursdays feel like a punishment.

Status goes async. Three bullets in a shared channel. What shipped, what’s next, what’s stuck. Done. And even better: make progress transparent and visible to everyone who needs it, when they need it — not just when a manager decides to ask.

I consider transparency the actual unlock here. Anyone — not only managers — should be able to know where Karol from Marketing is at with the thing she needed to finish before you could move forward on yours. That visibility removes the need for the check-in meeting entirely.

The real meeting — the actual meeting — is reserved for the problem nobody can solve alone. That’s when you need each other. Not to read a PowerPoint at each other. To fight and solve something together.

A 2022 MIT Sloan Management Review study tracked 76 companies across 50+ countries after they introduced meeting-free days. When companies cut meetings by the equivalent of two days a week, productivity jumped 71%. Not improved. Not inched forward. Jumped.

Your move this week: Cancel one recurring status meeting. Replace it with a pinned channel where everyone posts three bullets every Monday morning or ensure you have a place where progress is visible to all. See if anyone notices anything missing — other than the hour they just got back.

2. They fight about the work before it exists, not after it ships.

There’s a specific kind of team silence that should terrify you. It’s the silence in planning meetings when someone proposes something and everyone nods. No questions. No pushback. Just nodding.

That silence isn’t agreement. It’s deferred disagreement. And it will collect interest.

Six weeks later, when the thing is half-built and clearly wrong, suddenly everyone has opinions. Suddenly someone remembered they had concerns. Suddenly there’s a retrospective where the people who put in the most effort feel frustrated and burned out, wondering why no one said anything earlier.

High-performing teams have made it socially normal — expected, even — to challenge something while it’s still just an idea. The rule is simple: say it now, while we can still change it, or hold it forever. Not because they’re harsh. Because they respect each other’s time too much to waste it building the wrong thing politely.

One practical tool that changes this overnight is running proposals through a structured template before the meeting — whether live or async. The goal is to make sure the right questions get asked before anyone commits to anything.

Here’s the template I use and recommend with every client:

Proposal Review Template

• I.C.E Proposal Discussion: Discuss things like impact, confidence, and effort
• OFQ Proposal Discussion: Discuss the Objective, explore how people feel about the proposal and ask powerful questions to uncover potential opportunities
• Wish, Wonder and Need: Discuss with the team what the wish for, what they wonder (risks, ideas..) and what they actually need.
• Generic Stakeholder Discussion
• NHF Discussion: Discuss Non-negotiables, hopes and fears.

You can learn more about these methods at Nova.

The person proposing fills this out beforehand.

Everyone else reads it before the meeting.

The meeting itself becomes a real conversation, not a reveal.

Pro tip: Run these async first. When people aren’t put on the spot in a live meeting, they have time to actually think — and you’ll get more honest feedback, more creative concerns, and less reflexive nodding.

3. They write the meeting before they have the meeting.

Jeff Bezos banned PowerPoint at Amazon. Before you assume this is another Silicon Valley quirk, stay with me. His replacement was a six-page written memo. Every meeting starts with twenty minutes of silence while everyone reads it. No presenting. No slides. Just reading.

The logic is uncomfortable and correct: if you can’t write clearly about something, you don’t actually understand it yet. Bullets let you hide. Full sentences don’t.

You don’t need to go full Amazon on this. But try writing one page — just one — explaining what you want to decide and why, before your next big meeting. If it’s hard to write, that’s the point. You just found the confusion before you walked six people into a room for an hour to find it together.

And if you can do this consistently, make it a non-negotiable norm: every meeting invitation includes an objective written like this —

“The objective of this meeting is [specific goal], so by the end of the session we will have [concrete outcome].”

“Align the team” is not a meeting objective. “Decide which of these two [ approach 1 ] and [approach 2] approaches we’re taking for the Q3 launch, so that design can start Monday” is a meeting objective.

Also include who’s invited and what you’re expecting from each person. Is this a presentation where they should listen? A collaborative working session where they should come with ideas? Knowing this in advance changes how people show up — and whether they show up prepared.

Your move this week: Before your next meeting, write the objective as a single sentence using the format above. Send it with the invite. Watch the quality of the conversation change.

4. They built a culture where the newest person can stop everything.

At Toyota factories, there’s a cord running along the entire assembly line. Any worker — day one, first week, doesn’t matter — can pull it and stop the whole production line the moment they see something wrong.

This sounds like a productivity nightmare.

It’s the opposite.

Toyota’s own data shows that catching a defect at its source costs approximately $1 to fix — let it reach final assembly and that same defect costs $100 or more. The cord isn’t an interruption. It’s the cheapest insurance policy in manufacturing history.

Here’s where it gets more interesting: American car companies copied the idea. They installed the cords. Workers never pulled them. They were afraid. The tool was there. The culture and habits wasn’t.

That’s the real lesson. You can implement every process in this article, but if the person closest to the problem doesn’t feel safe raising it, nothing works. Elite teams make speaking up the obvious move — not the brave one.

How to build this in your team starting this week: Create a standing “flag it” channel or section in your weekly update where anyone can surface a concern, a risk, or a “something feels off” — with zero obligation to also bring the solution. Leaders respond within 24 hours, publicly, with either “we’re on it” or “here’s why we’re not changing course.” Do this consistently for four weeks and watch what happens to the quality of information you actually receive.

At my team we have a space inside Nova called: The Decision Log. All team members must keep the decision logged updated indicating blockers, decisions, wins, etc.

5. They ask “who” before they figure out the “how.”

Most teams hit a wall and immediately try to solve their way through it — collectively, in a room, over sixty minutes, with no one who actually owns the outcome.

The better question is always: who is the right person for this?

And this isn’t something you leave to the team to volunteer for. Leaving ownership to whoever raises their hand first is how you end up with the wrong person carrying the wrong thing, quietly struggling, while the right person is fully available and completely unaware they were needed.

A leader’s job at this stage is to know their people well enough to assign with intention — matching not just skills, but roles, workload, growth plans, and conversations you’ve already had with them. The leader who doesn’t know who should own what shouldn’t be scheduling an execution meeting yet. They should be doing that homework first.

The practical filter: Before any execution conversation, a leader should be able to map the key deliverables, decisions, and non-negotiables to specific names — not task lists. If you can’t do that mapping before the meeting, you’re not ready for the meeting.

6. They run the pre-mortem nobody taught you about.

This one is short, counterintuitive, and one of the highest-return habits on this list.

Cognitive psychologist Gary Klein developed it in 2007 and published it in the Harvard Business Review. Nobel laureate Daniel Kahneman called it his favorite tool for making better decisions. And almost nobody in day-to-day team management uses it.

It’s called the pre-mortem, and it works like this: before you launch anything significant — a campaign, a product, a hire, a restructure — you gather the team and tell them to imagine it’s one year from now, and the project has completely failed. Not underperformed. Failed. Then you give everyone two minutes to write down, individually and silently, every reason they think that happened.

Research from 1989 showed that this method of mentally transporting yourself to a future failure increases the ability to accurately forecast risks by 30%.

Why does it work? Because asking “what could go wrong?” in a planning meeting puts people in an optimistic, collaborative mode — nobody wants to be the one who kills the energy. But asking “it already went wrong, why?” gives people psychological permission to be honest. The failure is hypothetical. The concerns are real.

I’ve run this with client teams and the number of legitimate risks that surface in twenty minutes — risks everyone knew but nobody had said aloud — is consistently surprising.

Run it in under 30 minutes: State the plan clearly. Tell the group to assume it failed in 12 months. Give two minutes of silent individual writing. Then go around the room and collect every reason without debate. Group the themes. Assign someone to address the top three before kickoff. Done.

7. They fight hard in the room. Then they lock the door on the argument.

This one is less comfortable to talk about but it’s probably the most operationally important habit on this list.

Andy Grove built it at Intel. Bezos made it famous at Amazon. The principle is called “Disagree and Commit” and it works like this: you argue — genuinely. You push your position. You challenge the alternatives. You don’t perform agreement to seem collaborative.

And then, once the decision is made, everyone becomes its most committed advocate. Even the people who voted against it.

No hallway politics. No quiet foot-dragging. No “well, I said from the start that this wouldn’t work” six weeks later.

This single habit eliminates more dysfunction than any org chart redesign I’ve ever seen. Because what usually kills team speed isn’t disagreement — it’s unresolved disagreement that never got a room.

The norm to establish: At the end of every significant decision meeting, before closing, go around and ask each person: “Are you in or do you have a blocker?” If someone has a blocker, it gets aired now. If they say they’re in, that’s a public commitment — and the group holds each other to it.

8. They write down how they work together — and they actually review it.

This is the habit nobody talks about because it sounds almost embarrassingly basic. And yet it’s responsible for more team dysfunction than any of the others on this list when it’s missing.

Most teams assume that everyone on the team has the same defaults. The same understanding of what “urgent” means. The same idea of when it’s appropriate to message someone at 9 PM. The same definition of who makes final calls on what. The same threshold for when something is “done.”

They don’t. They never did. And nobody ever checked.

High-performing teams — particularly the ones operating across time zones, functions, or growth stages — write down a Working Agreement: a short, living document that makes implicit norms explicit. Not a values poster. Not a culture deck. A practical, editable set of agreements about how the team actually operates and that guides them day-to day.

Here’s a story that illustrates why this matters. A startup I worked with had two co-founders who had been friends for years. They launched, hired a team of eight, and within five months were dealing with a level of interpersonal friction that made no sense given how talented the people were. When we sat down to map it, almost every conflict traced back to assumption collisions — the designer thought “feedback” meant “please tear this apart.” The engineer thought it meant “say something nice and flag only the blockers.” The ops lead thought Monday morning messages were fine. The marketer thought they were aggressive. Nobody was wrong. Nobody had ever talked about it.

One Working Agreement session later — two hours, asynchronous, everyone contributing — and half the friction dissolved on its own.

What to include in yours:

• Communication: Which channels for what, and expected response times by type
• Meetings: When we meet, what for, and what requires a meeting vs. a message
• Decisions: Who decides what unilaterally, what requires consultation, what requires consensus
• Feedback: How we give it, when we give it, and what we mean when we ask for it
• Availability: Core hours, boundaries, and how to signal when you need uninterrupted time
• Quality standards: What “done” means, what “good enough” means, and who sets that bar.

This shouldn’t be a document people read during onboarding. This should be part of the day-to-day process and part of what leaders enable and enable.

Tip: Review it quarterly. Add to it when something breaks down. It’s not a contract — it’s a conversation you had once and wrote down, and help you improve the process so nobody has to have it again every six months.

9. They treat failure like a receipt, not a verdict.

The teams that learn the fastest aren’t the ones who fail the least. They’re the ones who extract the most information from every failure and make it impossible for the same mistake to be invisible twice.

Build the habit with one rule: After anything that didn’t go as planned — a launch, a campaign, a client situation — the person closest to it writes a three-paragraph “what happened and what I learned” and shares it with the team before the week is out. Not to confess. Not to be judged. To make sure the team gets the tuition too.

One last thing before you go rebuild your entire team structure.

Three questions.

Be honest!

:)

If you asked your team for raw, unfiltered feedback right now — not in a survey, out loud, in a room — would you get silence or a real conversation? Silence means the cord exists. Nobody’s pulling it.

Look at your last five meetings. At the end of each one: was there a decision, or was there another meeting? That ratio tells you everything.

Last time someone on your team messed something up — what was their first instinct? Hide it, or surface it? That answer is your culture. Not your values document. Not your LinkedIn post. That specific moment.

None of this requires a consultant, or a team offsite where someone walks on hot coals. It requires naming what the best teams already do quietly, and deciding that your team is going to do it out loud.

Start with one habit. If you’re not sure which one, start with the meeting. Cancel the status update. Post three bullets instead.

Everything else follows from there.

…and…If you are looking for a tool to help you with this you can try Nova.