↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

How to Create Group Norms That Make Your Team Stronger

The article defines group norms as informal and formal rules that guide how team members interact, shaping predictability, shared expectations, and ultimately team culture. It argues that while every group develops norms, deliberately creating and revisiting them leads to clearer communication, easier conflict resolution, faster onboarding, and healthier work habits. The text then details a practical process: get broad buy-in, reflect on current and past experiences, write specific and measurable norms, secure explicit agreement, gently enforce them, and treat them as living agreements. Examples from companies like Google, Doist, REI, and The Bush School illustrate how intentional norms support engagement, feedback quality, and psychological safety.

Reading notes
#

  • Google discovered that teams across the company operated with very different interaction styles, decision-making approaches, and communication habits.
  • Their research led to the conclusion that effective teams are intentionally built on shared values expressed as group norms.
  • Group norms are described as informal and formal ground rules that direct how people interact, clarify roles, and create predictability.
  • Teams with clear norms benefit from more constructive meetings and communication, using shared rules and language.
  • Shared norms give teammates a common value system so they work together toward goals with aligned expectations.
  • When expectations are explicit, individuals understand what is required and can meet or exceed those expectations.
  • Overlapping understanding of norms makes conflict resolution easier inside the group.
  • Defined norms help new teammates get oriented quickly while supporting a healthy company culture.
  • The article distinguishes values as group beliefs and norms as group behaviors, which together produce group culture.
  • It notes that every team has norms about things like dress and punctuality, but most of these develop without explicit discussion.
  • Unplanned norms in written communication can lead to long email threads, scattered texts, information overload, and lost details as teams grow.
  • A snowball effect can occur when one person’s behavior, such as a boss’s late-night messaging habit, sets de facto rules for the whole group.
  • Research cited shows that handling after-hours work communication can generate anxiety that negatively affects workers and their families.
  • The article says creating norms is easiest when a team is forming, even if this requires an extra meeting up front.
  • It states that codifying or adjusting norms on existing teams is also possible and can simplify onboarding and long-term culture maintenance.
  • Changing norms on teams with communication problems requires examining the issues closely and designing a plan to address them.
  • The first recommended step is to find allies, since a single person cannot control group behavior without broader engagement.
  • Successful norm creation is said to require buy-in from most teammates as well as support from leadership.
  • An example from Doist mentions Andrew in people operations initiating a company-wide engagement survey that leadership supported.
  • After securing support, the next phase is reflection on what currently works and what does not in the team’s collaboration.
  • Team members are encouraged to recall their most positive and most negative teamwork experiences individually.
  • Sharing these highs and lows as a group can reveal shared patterns and collective insights about existing norms.
  • The REI marketing department used Radical Candor training to shift from vague, sugar-coated criticism to clearer, kind feedback.
  • The article suggests that any group can benefit from approaching norm discussions with honesty, kindness, sincerity, and specificity.
  • It warns that vague comments and overly polite tendencies can create miscommunication and later dissatisfaction with the process.
  • Circulating specific prompts before group discussions can help people prepare what they want to contribute and receive from the group.
  • Under “Get specific,” the author cites Maura Thomas’s point that managers’ expectations often differ from what employees think they are.
  • Thomas has observed that when managers do not communicate clear directions, employees tend to fill the gap with assumptions.
  • To avoid this, the article advises being extremely clear and documenting the team’s shared expectations in writing.
  • It recommends straightforward objectives and guidelines that are measurable and achievable as key to effective norms.
  • After sharing individual reflections, the team should understand which current behaviors are helpful and which are problematic.
  • Taking notes on positive and negative norms allows the group to see them side-by-side and choose which to keep or change.
  • The process includes turning those choices into concise, digestible written norms that reinforce desired behaviors and adjust unhealthy ones.
  • A tip is given to limit systematic changes to no more than three new norms at a time, even if many existing norms are kept.
  • The article includes an example of clear documentation of expectations around using Twist as a team communication tool.
  • In the “Agree” step, it emphasizes that norms work best when there is consensus and everyone agrees to follow them.
  • Early agreement on norms is presented as a way to make mutual accountability easier within the team.
  • The Bush School example describes new faculty meeting in a peacemaking circle where each participant proposes norms for the space.
  • In subsequent rounds at The Bush School, participants can ask questions about norms, add new ones, or pass, creating an additive process.
  • That process is said to ensure everyone is heard and to set the tone for the school year.
  • The article suggests posting norms in visible places and referencing them, such as in chat boxes or first slides for virtual meetings.
  • For quarterly review feedback, it advises sending the agreed guidelines along with the agenda to keep them top of mind.
  • Once norms are compiled and accepted, they should be stored where everyone can access them and consulted when necessary.
  • For enforcement, the text notes that rules will inevitably be bent or broken, especially when they are newly formalized.
  • Planning in advance how to respond to violations is presented as a way to ease the transition to written norms.
  • Kathryn Blumsack is quoted saying that ignoring norm violations effectively creates a second set of norms that undermines the original ones.
  • She uses punctuality as an example, arguing that failing to mention lateness signals that being on time is not truly important.
  • The article stresses that all members share responsibility for upholding norms, rather than leaving enforcement solely to leaders.
  • It mentions humor-based peer enforcement like swear jars or colored hankies to flag discussion rule violations as successful in some groups.
  • A Doist example shows teammates reinforcing the norm that no one works during off time by acknowledging that expectation.
  • The “Reevaluate” step describes norms as living agreements that should be revisited and updated as teams evolve.
  • Some groups review norms at each meeting, at project kickoffs, or on a quarterly schedule to gather ongoing feedback.
  • Establishing a regular cadence for revisiting norms is presented as a way to maintain positive momentum.
  • At Doist, the team conducts post-mortems after launches, particularly when problems occurred, to reflect and improve.
  • Combining personal reflection with high standards at Doist leads to norm adjustments and stronger coordination in future work.
  • The article notes that regular post-mortems alongside Radical Candor help teams reassess norms and move toward better communication and workflows.
  • Google’s Project Aristotle investigated norms across many teams and identified safe risk-taking as a core element for well-being and performance.
  • The project concluded that psychological safety, supported by certain key norms, distinguished higher-performing, happier teams.
  • Google promoted specific norms: demonstrating engagement by being present and using active listening.
  • Another recommended norm is showing understanding by recapping discussion points and verbally validating contributions.
  • Teams are encouraged to be inclusive by building rapport, asking for feedback, and expressing gratitude to colleagues.
  • The guidelines also highlight showing confidence and conviction by stating decisions clearly while allowing vulnerability.
  • The article states that creating group norms begins with asking how people want to interact, from overall culture down to meeting etiquette.
  • It suggests that identifying shared values and practical norms often comes from simple questions about what would work for the group.