A new team forms — or a new leader inherits an old one — and the instinct is to prove momentum: straight to the task list, the delivery plan, the quick wins. Six months later the symptoms arrive on schedule: duplicated effort, turf friction, decisions relitigated weekly, meetings that are long and somehow still inconclusive. None of it is a mystery. The team went to work before it existed.
What a charter actually settles
A proper start-up conversation — a charter — settles the questions that otherwise get answered by accident, in the wrong order, under pressure. Who are we and what's the situation we're walking into? What are we here to accomplish, stated plainly enough that a stranger could repeat it? What principles govern how we'll operate — the real ground rules, not the poster ones? And what tensions already exist in the room: the histories, the overlapping mandates, the things everyone knows and nobody says. Naming tensions early doesn't inflame them; it drains their power to sabotage the work later, because a named tension can be managed while an unnamed one can only be tripped over.
Structure and task lists come last, not first — they're the output of a charter, not a substitute for one.
Only once identity, intent, principles and tensions are settled does the conversation earn the right to move to structures, plans and who-does-what. Run in that order, the structural decisions take a fraction of the usual time — because the arguments that normally derail them have already been had, once, on purpose.
Set up the frame, then hand over the work
There's a leadership discipline embedded in the sequence. The leader's job is to set up the frame — the intent, the principles, the acknowledged tensions — with the team contributing throughout. But the detailed how — the working structures, the task breakdown, the way the team organises its own delivery — belongs to the team. Leaders who prescribe the how as well as the what get compliance without commitment: plans that nobody argues with and nobody owns. Teams that build their own structures inside a clear frame execute them with conviction, because the plan is theirs.
Start with the history, and re-charter on change
For an inherited or long-standing team, one addition pays for itself: start with a short history walk. Lay out the team's timeline together — the wins above the line, the hard passages below it. Twenty minutes of shared history lowers everyone's attachment to old grievances and old glories alike, and gives the new leader the context no briefing pack contains. And the charter isn't a founding document to laminate: any significant change — new members, new mandate, a merger of two teams — is a signal to re-contract. Most "team dysfunction" in mature teams is just an expired charter that nobody renewed.