🔍 FIELD NOTE
Everything on the desk is a memo except the sheet somebody signed.
A charter your team approved for itself binds nobody
I have sat in workshops where a platform team writes its charter, and it’s always interesting. The mission gets argued into shape, scope is settled, roles are named, ways of working are agreed line by line. By the end the document is genuinely better and the team feels genuinely clearer, and everyone in the room is happy to put their name to it. Then it goes up on the intranet, and every name attached to it belongs to someone who was in the room.
The test arrives months later, and it is never a debate about wording. A senior stakeholder walks a demand straight past the charter, work that sits outside the team's scope, or an exception to a standard the team is supposed to hold. The team does what teams do, they open the document and point at the line. And pointing changes nothing, because the person crossing the line never agreed to it. To them the charter is not an agreement being broken. It is a description the team wrote about itself, and descriptions do not outrank a delivery date.
That is the mistake, and I think it is close to universal. We treat a charter as an act of self-definition, when the delivery playbook underneath most ServiceNow programmes treats it as an instrument of consent. There, a charter exists for one reason, to obtain the approval of the stakeholders it touches. A governance team is not established when its members agree to meet, it becomes real when the organisation formally approves it, starting with the appointment of its accountable owner. Even a control board's charter is framed as the tool for winning executive backing early, because that early backing is what gives the process credibility when it has to say no later. In every case the signature is the mechanism. The document is just what the signature is attached to.
A charter is not a description of your team. It is an agreement with everyone who is not in it.
So route yours outward, starting with the people whose behaviour the charter has to change, the leaders whose requests it will one day redirect, the sponsors whose escalations it will slow down, the process owners whose territory it borders. Put the document in front of each of them and ask for explicit agreement, with a name recorded against it. The delivery playbook is uncompromising about exactly this discipline, across ServiceNows standard delivery methodology, every single delivery task carries one accountable name, none carries zero and none carries two. Your charter deserves the same rigour, with every commitment carrying a named owner on your side and a named counter-signature on the other.
Expect the counter-signing to be slower and scratchier than the writing was. That friction is not the process failing, it is the charter doing its work early and cheaply, surfacing the collision in a meeting room months before it would otherwise surface as an escalation.
A self-approved charter is a memo. It becomes a mandate the day someone outside the team signs it.
P.S. Try one measure this week. Name the five people outside your team the charter most needs to bind, then count how many of them have ever read it. That count is the charter's real strength, whatever the document says.