What’s the best way to establish healthy team norms early in a project?

That’s a great question, and one that sits right at the intersection between structure and culture.

In predictive environments, I’ve found that healthy team norms start even before kickoff, with the Team Charter or Appointment Term (often part of the project initiation phase).

It’s not just a formality: it defines who is accountable for what, but also how the team commits to behave, clarifying roles, decision rights, escalation paths, and collaboration rules.

When this document is co-created (not imposed), it becomes the foundation of trust and accountability.

In agile environments, the same intent is achieved through Working Agreements or Team Norms built during the first Sprint Planning or Team Canvas sessions.

The difference is rhythm: instead of a static document, norms evolve through retrospectives, living agreements that adapt as the team learns.

In both cases, the key is balance:

• Predictive → structure first, culture second.
• Agile → culture first, structure second.

But ultimately, both must coexist, because accountability without trust becomes control, and trust without accountability becomes chaos.

I start establishing team norms from day one through co-creation rather than top-down rules. I facilitate a short session where everyone defines what respect, accountability, and communication mean for our team.

Once we agree, we document it and revisit it every few weeks during retros, not to police behavior, but to keep alignment alive. When people help shape the norms, they’re far more likely to uphold them.