October 27, 2026 · layne

12 team norms examples grouped by communication, meetings, decisions, and accountability.

Team Norms: What They Are, With 12 Examples for Small Teams

Team norms are the agreements a team makes about how people work together, communicate, make decisions, and handle problems. They establish expectations so employees aren’t left guessing about what’s acceptable, who’s responsible, or what happens when something goes wrong. For a growing small business, effective team norms reduce unnecessary confusion, improve accountability, and help people work together without needing the owner to settle every disagreement or answer every question.

And if you’re thinking, “Isn’t that just common sense?”

It should be. But common sense has an unfortunate habit of meaning something different to everyone.

What are Team Norms?

Team norms are the shared expectations and behaviors that shape how people work together. They exist whether you’ve written them down or not. They’re the everyday behaviors like communication, meetings, decision-making, accountability, and how people handle conflict.

The challenge is making sure everyone understand and agrees on what those expectations should be.

When your business has eight employees, you probably don’t need to explain much of this. Everyone knows how you like things done. They know which questions deserve a call versus a text, which decisions they can make themselves, and how to handle a customer who’s unhappy.

A lot of that knowledge comes from working directly with you.

Now imagine that same business with 30 employees. Some of those people have never worked directly with you. Others have picked up habits from managers who interpreted your expectations differently. The original eight employees all think their way is the right way because, for years, it was.

Suddenly, you have three different versions of how your business operates, and none of them are necessarily wrong.

This is one reason why company culture breaks as your business grows. What use to happen naturally now requires some intention.

Team norms make the unwritten expectations visible. They give people something to work from rather than forcing everyone to figure out the rules through trial, error, and the occasional uncomfortable conversation.

Team Norms vs. Working Agreements vs. Company Values

These terms get used interchangeably, but they’re not quite the same thing.

Type What It Means Example
Company Values What the organization believes is important. We value accountability.
Team Norms The expectations and behaviors that shape how people actually work together, whether written or unwritten. People are expected to flag problems before they escalate.
Working Agreements The explicit commitments a team makes about how it will work together. We notify the team as soon as a deadline is at risk.

Every team has norms, whether they realize it or not. Working agreements give people the opportunity to examine those norms, decide which ones are worth keeping, and make the expectations visible to everyone.

Think of company values as the foundation. They describe what your business stands for, but they don’t necessarily explain what someone should do at 2:30 on a Tuesday when a problem comes up.

Working agreements go a little further by spelling out how a particular group will operate. Your leadership team, field crews, and accounting department may share the same basic norms while having different working agreements.

None of these need to become elaborate documents. In fact, the more complicated you make them, the less likely anyone is to remember them.

12 Team Norms Examples for Small Business Teams

Before you copy these into a document and announce them at your next staff meeting, there’s something worth mentioning.

The best team norms aren’t necessarily the ones that sound the best. They’re the ones your team is willing to practice.

Below are 12 examples organized into four areas where small businesses frequently experience communication breakdowns, confusion, and unnecessary friction.

1. We respond to direct messages within one business day.

Not every email or message deserves an immediate response, but people should know when to expect one. Establishing a reasonable timeframe keeps work moving without making everyone feel obligated to monitor their inbox constantly.

2. We use a phone call for urgent issues, not a text.

If something needs immediate attention, the other person needs to know that. An urgent message sitting unread for two hours doesn’t help anyone, especially when a customer, a crew, or an active project is waiting for an answer.

Of course, what qualifies as urgent should be agreed upon, too.

3. We say “I don’t know” instead of guessing.

There’s nothing wrong with not knowing something. There is a problem with pretending you do, especially when someone else is making a business decision based on your answer.

Create the expectation that asking questions and finding accurate information are more valuable than appearing to have every answer.

4. We don’t hold meetings without an agenda or a clear purpose.

If nobody knows why they’re attending, there’s a good chance they shouldn’t be. A meeting should have a reason to exist, an expected outcome, and the people necessary to accomplish it.

And before you ask, “weekly check-in” isn’t necessarily a purpose.

5. We document decisions and share them within one hour of the meeting.

A discussion isn’t the same thing as a decision. When a meeting ends, people should know what was decided, who’s responsible, and when the work needs to happen.

A short update in your team’s shared channel is usually sufficient. You don’t need a five-page meeting summary.

6. We start meetings on time, even when someone is late.

When five people wait ten minutes for a sixth, you’ve taken time away from five people who were prepared.

Occasional emergencies happen. Consistently running late, however, shouldn’t become the team standard.

7. We disagree in the room and commit to the decision afterward.

Healthy disagreement is useful. People should be able to challenge an idea, share concerns, and offer alternatives before a decision is made.

Once the team has agreed on a direction, however, everyone needs to support its execution. Continuing the argument through side conversations and quiet resistance doesn’t improve the decision.

8. We allow the person closest to the work to make decisions within their authority.

Your project manager shouldn’t need the owner’s permission to make every routine project decision. Neither should your customer service manager, operations lead, or department head.

Establish clear limits for decisions involving spending, risk, customer commitments, or changes in scope. Inside those boundaries, let people do the jobs you’ve hired them to do.

9. We speak to the original decision-maker before reversing their decision.

Few things undermine someone’s authority faster than discovering a decision they made has been overturned without a conversation.

Sometimes a decision needs to change. That’s business. But the person responsible deserves an explanation, particularly when they’re the one who has to communicate that change to everyone else.

10. We ask for help when we’ve been stuck for more than one business day.

Struggling silently for three days doesn’t demonstrate independence. It creates delays and often makes the original problem harder to solve.

The time limit can change depending on the work. What’s important is creating an expectation that asking for help is a responsible action, not an admission of failure.

11. We flag missed deadlines before they happen.

Your team shouldn’t have to discover on Friday that something promised for Thursday isn’t finished.

Unexpected problems happen. Early communication gives people the opportunity to adjust resources, reset expectations, or find another solution before the delay creates bigger problems.

12. We give feedback directly to the person involved, not to everyone else.

If someone isn’t meeting expectations, the conversation belongs with that person.

Talking around problems, complaining to coworkers, or waiting for the owner to intervene only creates more frustration. Direct, respectful feedback should be a normal part of working together, not something reserved for annual performance reviews.

What Your Team’s Behavior May Actually Be Telling You

Here’s where I think a lot of business owners get frustrated: You have employees who are capable, experienced, and generally good at their jobs. Yet you’re still dealing with missed communications, repeated disagreements, decisions that somehow end up back on your desk, and managers who don’t seem to be operating on the same page.

It’s tempting to conclude that people aren’t taking enough ownership.

Sometimes that’s true. But sometimes the expectations were never made clear in the first place.

Consider a commercial construction company where the estimator, project manager, and operations manager each have a different understanding of when a change order needs approval.

The estimator believes it’s the project manager’s responsibility. The project manager thinks operations should review anything that affects the schedule. Operations assumes the owner wants to approve anything that changes the project’s financial exposure.

All three people may be trying to protect the business.

Meanwhile, the change order sits unresolved, the customer is waiting, and the owner is frustrated that nobody can make a decision.

You could tell everyone to communicate better. You could hire another manager. You could even implement new project management software. But if nobody agrees on who has the authority to make the decision, what exactly have you solved?

A team norm can establish the expected behavior, such as escalating decisions that exceed agreed limits. But the business also needs to define those limits.

Norms help people work within a clear structure. They cannot replace a structure that doesn’t exist.

The 4 Things to Look at Before Setting Team Norms

If you’re experiencing recurring team problems, resist the temptation to immediately write a long list of rules. Instead, take a closer look at what’s actually happening.

1. Where do people keep asking the same questions?

Pay attention to the questions that repeatedly make their way to you or your managers.

Are employees asking how to handle situations they’ve encountered before? Are people seeking approval because they genuinely need it, or because they’re afraid of making the wrong call?

Repeated questions may indicate missing instructions, unclear decision authority, or conflicting expectations.

Start by identifying the questions you should no longer need to answer.

2. Where do handoffs regularly fall apart?

Look at what happens when work moves between departments or individuals.

Sales hands something to operations. Estimating hands a project to the field. A completed job moves to accounting for billing. A service technician identifies additional work that requires customer approval.

Where does information get lost? Where do people make assumptions about what someone else is responsible for?

If the same handoff creates problems repeatedly, you may need both a clear working agreement and a better-defined process.

3. Which behaviors do your leaders tolerate?

Warning: This one can be uncomfortable.

You can establish the best communication norms in the world, but they won’t mean much if your leadership team consistently ignores them. You included.

If the expectation is to start meetings on time, the owner doesn’t get a permanent exemption. If the norm is to address problems directly, managers shouldn’t be discussing employee performance with everyone except the employee.

People learn what is acceptable by watching what actually happens.

The real rules of your business are the behaviors you allow to continue.

4. Where are employees operating under different assumptions?

Ask several people how your team handles the same situation.

Who approves additional spending? What happens when a customer escalates a complaint? When should a missed deadline be communicated? Who can change a project priority?

If you get five different answers, you have something to work on.

The employees may not be disagreeing about the company’s goals at all. They may simply be following different sets of unwritten rules.

How to Set Team Norms in One 60-Minute Meeting

You don’t need an expensive retreat, a three-day workshop, or a 40-page culture document to establish team norms.

You need the right people in a room and a willingness to have a productive conversation about how they actually work together.

Here’s a simple one-hour exercise.

  1. Identify the Best and Worst Team Experiences

    10 minutes

    Ask everyone to think about the best team they’ve worked on and the worst.

    Have them write down what made each experience good or bad. Focus on behaviors, not personalities.

    What made communication easy? What caused frustration? When did people feel trusted? What made work unnecessarily difficult?

    Give everyone time to write their answers individually before discussing them. This helps prevent the loudest person in the room from setting the direction.

  2. Find the Common Themes

    15 minutes

    Bring the answers together and group similar observations.

    You may notice recurring concerns about slow decisions, unclear deadlines, meeting overload, poor handoffs, or people avoiding difficult conversations.

    Don’t try to solve everything immediately. First, identify the behaviors that are creating the most friction.

  3. Turn Those Themes Into Clear Agreements

    20 minutes

    For each theme, write one sentence beginning with “We.”

    Avoid statements like “We communicate effectively” or “We respect one another.” Those sound nice, but they’re open to interpretation.

    Instead, write something observable:

    “We notify the team as soon as a deadline is at risk.”

    “We make decisions within our assigned authority.”

    “We address concerns directly with the person involved.”

    Someone reading the norm should understand what behavior is expected without needing a lengthy explanation.

  4. Choose Your Top Five to Eight Norms

    10 minutes

    You probably won’t solve every team issue in an hour. That’s fine.

    Have the team vote on the five to eight agreements that would make the biggest difference in how they work together.

    If everything becomes a priority, nobody remembers any of it.

    Assign someone to document the final list and share it with the team.

  5. Schedule a Review

    5 minutes

    Before the meeting ends, put a date on the calendar to revisit the agreements.

    I recommend reviewing them after 30 days to see how they’re working, then quarterly once they’ve become part of the team’s routine.

    Ask what’s working, what’s being ignored, and whether anything needs to change.

    Don’t make these rules permanent simply because someone typed them into a document.

Total Time: 60 Minutes | Outcome: 5–8 Team Norms

What Not to Assume: Another Policy Won’t Fix Everything

Let’s say you set your norms, everyone agrees to them, and for two weeks things improve. Then the same problems come back.

It’s easy to assume the team isn’t committed or that you need stricter accountability.

Maybe. But I’d look a little deeper before deciding that’s the issue.

If your team keeps bringing decisions back to you, a norm that says “We make decisions at the appropriate level” isn’t going to fix unclear authority. Or if deadlines are constantly missed because your employees are overloaded, a requirement to communicate delays earlier will help people anticipate problems. It won’t eliminate the workload. And if managers consistently undermine one another, writing “We support team decisions” won’t resolve competing priorities or conflicting direction from leadership.

This is where some businesses end up creating policy after policy without really improving how they operate.

They keep documenting the behaviors they want without changing the conditions that produce the behaviors they’re getting.

Sometimes the solution really is a clearer expectation or a more direct conversation with an employee. Other times, the problem involves how responsibilities, decisions, information, and resources flow through the business. You have to understand which one you’re dealing with before choosing the fix.

Signs Your Team Norms Aren’t Working

The easiest way to evaluate team norms isn’t to look at whether you’ve written them down. It’s to look at what people actually do.

A few warning signs:

  • Nobody can name the norms. They’re on a poster or in an employee handbook, but people don’t use them when making decisions.
  • Leaders are the first to break them. Employees are expected to follow rules that management routinely ignores.
  • You’re having the same argument every month. The team has discussed the issue repeatedly, but nobody has changed how the work gets done.
  • New employees learn the real rules through gossip. The official expectations say one thing, while experienced employees quietly explain how things actually work.
  • Every exception needs the owner. People understand the basic rules but have no authority or guidance when something unexpected happens.

If you’re seeing several of these patterns, revisit the agreements with your team. Find out whether the norms are unclear, unrealistic, inconsistently enforced, or simply disconnected from how the business operates.

And if the problems continue even when people understand and follow the norms, you may be looking at something beyond team behavior.

Frequently Asked Questions

How many team norms should a team have?

Most small teams should start with five to eight team norms. That’s enough to establish meaningful expectations without giving employees another long document to remember. There’s a reason a handful is 5.

The 12 examples above are a starting point, not a requirement to adopt all 12. Choose the agreements that address your team’s biggest recurring frustrations, edit them, or make your own.

Who should set team norms?

Team norms should be created by the people expected to follow them, with the team leader participating in the conversation. When employees help define expectations, they can raise practical concerns that leadership may not see.

The leader still has a responsibility to address unacceptable behavior and ensure the agreements support the business. Collaboration doesn’t mean every expectation is negotiable.

How often should we revisit our team norms?

Review new team norms after the first 30 days, then at least quarterly. You should also revisit them when the team changes significantly, such as adding a new employee, adjusting staff departments, or delivering a new service.

A norm that made perfect sense with six people may need to change when the same group grows to 20.

Should every department have the same team norms?

Departments should share a few basic expectations, but they may need different working agreements for their responsibilities. A field service team and an accounting team can both value prompt communication without using the same response times or escalation methods.

Consistency is helpful when it supports coordination. Forcing everyone into identical rules simply for the sake of uniformity can create unnecessary friction.

What should I do when someone repeatedly ignores a team norm?

Start by addressing the behavior directly and finding out why the agreement isn’t being followed. The person may not understand the expectation, may be working under conflicting instructions, or may simply be choosing not to follow it.

Those situations require different responses. Once expectations and obstacles are clear, continued noncompliance becomes an individual accountability issue that the manager needs to address.

Can team norms work when employees are remote or spread across job sites?

Yes, and clear team norms can be especially helpful when employees don’t work in the same location. Without regular face-to-face interaction, people need consistent expectations about communication, decisions, availability, and how to raise problems.

For businesses with multiple job sites or remote employees, make sure agreements reflect how work actually happens rather than assuming everyone is sitting at a desk checking the same messages.

Why does my team still come to me for every decision?

Your team may understand its responsibilities without knowing how much authority it has to make decisions. Employees often escalate decisions when approval limits are unclear, past decisions have been reversed, or different managers give conflicting direction.

Team norms can establish when decisions should be escalated, but you’ll also need to clarify who owns those decisions and what authority comes with the role. Without that, people may continue bringing questions to you because it’s the safest option.

What to Do Next

You don’t have to change your entire company culture to improve how your team works together. Start with the recurring frustrations your employees already recognize, have an honest conversation about the expectations behind them, and agree on a few behaviors everyone is willing to practice.

Then pay attention to what changes.

If communication improves but decisions still stall, or if accountability becomes clearer but the same operational problems continue… there’s probably more happening beneath the surface.

That’s when it’s worth looking at how your business operates as a whole. The Unrestricted Humans Growth Framework examines the relationships between people, processes, technology, and organizational structure to identify where growth may be creating unnecessary friction.

Because ultimately, you’re not trying to build a company where everyone follows more rules. You’re trying to build one where capable people understand what’s expected, have the authority to do their jobs, and can move the business forward without needing you in every conversation.

Not sure which norms your team is missing? Take the 12-question assessment and see where your team stands.

-L

Leave a Reply

Your email address will not be published. Required fields are marked *