A project can have a complete charter and still have a team that is not ready to work together. When I interviewed Tony Llewellyn, he treated setup as the place where shared vision, accountability, working norms, and leadership capacity become real or remain meeting notes.
The risk appears later under pressure. Missing conversations return as unclear commitments, sponsor confusion, and behavior nobody addressed while it was still easy to shape.
Teams do not become aligned just because the chart exists
Tony Llewellyn described a pattern many teams know well. Shared vision, roles, and accountabilities appear on the plan, but only as items to complete quickly. They get the check mark without getting the process.
His concern was practical. If a project moves forward before those conversations are done properly, the missing work does not disappear. It returns later through misunderstood expectations, weak commitments, sponsor confusion, and behaviors nobody addressed while they were still easy to shape.
That is an uncomfortable point because it means the team is rarely short on documents. It is short on real alignment.
Social intelligence is not extra work
Tony Llewellyn made a strong case that project success depends on three forms of intelligence: technical, commercial, and social. Most teams know how to defend the first two. The third one gets treated like vague soft stuff, even though it shapes how people share information, challenge assumptions, recover from stress, and make decisions together.
His version of governance was useful because it forced that issue into the same conversation as budget and risk. If the team can only advance when technical and commercial conditions are in place, why would it ignore the conditions that determine whether people can actually work through pressure together?
Tony named three prerequisites he wanted in place before a project moved forward: the money has to be right, leadership has to be strong enough to guide the team through ignored but necessary processes, and the sponsor or client has to be competent enough to keep shaping the brief and making decisions.
Those conditions matter because even the best team methods start failing when the commercial model is unstable, the leader treats the process as theater, or the client cannot keep up with the decisions the project requires.
That is a better way to read readiness. It is not only about schedule and scope. It is also about whether the people with authority can keep the work coherent when conditions change.
Rules work better when the team builds them
Tony Llewellyn was especially clear about behavioral norms. Teams are more likely to uphold rules they helped create. They are more likely to quietly subvert rules handed down from above.
Tony said it in five words: “It's all in the setup.”
That distinction matters on fast projects because experienced professionals can move so quickly into familiar roles that they import old habits without noticing. The team can look organized while carrying forward the same meeting behavior, silence, lateness, and low trust that hurt previous work.
Tony connected psychological safety to this same issue. People are more likely to speak honestly when the norms and the leaders make it safe to do that without ridicule or punishment. That does not happen because someone announces a safe space. It happens because the process, the norms, and the leadership behavior all support it.
At the next setup meeting that feels routine, test something more useful than whether the charter exists. Ask whether the team has actually agreed on the decision path, personal accountability, and the rules for raising concerns under pressure. That is the work teams otherwise try to borrow from the future.
Treat setup as a delivery gate. Before the work advances, the people with authority should be able to explain the decision path, the commitments they own, and how the team will raise concerns when pressure rises.
