The Critical Alignment Model is the backbone of the first 90 days because it prevents the leader from beginning at the easiest and most visible point, which is usually the behaviour of an individual. CAM begins with the purpose or intended outcome, then examines Environment, Structure, Implementation and People, in that order. Environment and Structure tell us what is intended and available. Implementation and People reveal what is actually expressed.

The sequence matters. If the purpose is vague, people can work very hard in different directions and every disagreement will appear personal. If the environment rewards silence, you cannot reasonably blame people for failing to raise risks. If the structure contains contradictory priorities, missing resources or no criteria for success, effort will not reliably produce the desired result. If the implementation does not use the agreed processes, the written system is largely fictional. Only after those conditions have been understood and addressed can we make a fair assessment of a person’s performance.

The first month is much more than listening politely while everybody tells you what they want you to hear. You are building a map of reality. That requires curiosity, questions, observation across different settings, access to the available data and the patience to notice contradictions without rushing to explain them. You are learning how the team thinks, decides, communicates, responds under pressure and understands its purpose.

Begin with the outcome. What is this team here to produce, for whom, and how will anyone know whether it has succeeded? Ask the formal question and then listen for the lived answer. People may repeat a company objective while organising their days around avoiding complaints, pleasing a senior stakeholder or completing activities that are easy to count. Those are not minor discrepancies. They reveal the difference between the written and unwritten ground rules.

Then examine Environment and Structure in detail. What is permitted here? What is rewarded? What gets someone quietly excluded? How safe is it to disagree with a senior person? What happens when a promise cannot be kept? Are team members personally responsible for outcomes or only for completing their portion of a task? Which standards are genuinely uncompromising and which are applied according to mood, hierarchy or convenience?

Look at what is measured and what remains invisible. Find out who measures it, how often, why it matters and what decisions are made from the information. A dashboard that nobody uses is decoration. Data collected without interpretation creates administrative work rather than intelligence. Equally, a team may care deeply about an outcome and have no meaningful way of detecting whether it is improving.

Trace the flow of work. Where does something begin, who receives it next, what has to be true before it can move forward, and where does it repeatedly slow down? What knowledge lives in one person’s head? Where are approvals duplicated? Which bottlenecks are treated as personality defects because nobody has mapped the sequence? Talk with the people closest to the work. They often know exactly where the friction is, even if they have stopped believing anyone wants to hear it.

During this first month, you are assessing all five dimensions of CAM without making premature conclusions about the final one. You will notice people, of course, but keep asking what the environment, structure and implementation are eliciting from them. The questions you are trying to answer include:

By the second month, you should have an emerging account of what is present. Now you begin to question it. This is where observation becomes synthesis. You compare what people say with what the data shows, what the process promises with what actually occurs, and what the organisation values with what leaders reward when the pressure is on.

The central question is: what is the observed reality? Be careful with the word observed. A confident opinion is not an observation. A complaint repeated by several people may be important, but repetition does not automatically make the explanation accurate. If the team says one person is unreliable, trace the dependencies around their work. If everyone believes a meeting is useless, identify its intended purpose, who needs its information and what happens elsewhere when the meeting is cancelled. If a process is described as bureaucratic, examine whether the process is unnecessary or whether people resent the accountability it creates.

Begin a trust analysis. Trust is not created through friendliness or team-building theatre. It is built when people say what they mean, do what they said they would do, admit what they do not know, communicate early when something changes and apply standards consistently. Look for the gap between promise and delivery, between what is said in the room and what is said afterwards, and between the permission to contribute and what happens when somebody offers a difficult truth.

This month is also where you test your own interpretation. Bring your emerging map back to the team. Explain what you think you are seeing and invite correction. Ask what you have missed. Ask whose perspective is absent. Transparency matters because secret diagnosis produces anxiety, while shared inquiry develops people’s capacity to think about the whole system. You are already developing leaders by showing them how to observe without blame and question without turning every conversation into a contest.

Use contrast analysis to locate the differentiators. If this is the outcome we intend and this is the outcome we are producing, what accounts for the gap? Some gaps will sit in Environment: a protective culture, conflicting values or a lack of psychological and intellectual safety. Others will sit in Structure: missing benchmarks, unclear authority, inadequate tools or an incoherent sequence. Some will sit in Implementation: the process exists, but is not trained, followed, measured or improved. Only some gaps will be located primarily in People.

The third month is where you begin making deliberate improvements, establishing useful rhythms and developing the team’s capacity to continue the work without depending on you for every answer. The aim is not to complete leadership in 90 days. It is to leave the first 90 days with an accurate map, trusted working relationships, clear priorities and a way of improving that the team can participate in.

• Use Critical Alignment Model to decide where each intervention belongs.
• Use T.R.U.S.T.M.E. to understand the value systems operating within individuals and the group, particularly when one person experiences another person’s order as restriction, enterprise as selfishness or belonging as conformity.
• Use Core, Improve, Innovate to distinguish what must be protected, what can be made better and what requires genuinely new thinking.
• Use Disruptive Leadership when the status quo no longer serves the greater good and the team needs the courage to look at the white space rather than rearrange the words already on the page.

Improvement should include rhythm without creating bureaucracy for its own sake. Establish meetings that have an intelligible purpose. Create measures that support decisions. Clarify who leads, who contributes, who decides and who needs to be informed. Make commitments visible. Review what was learned, not only what was completed. Notice where the system is improving and where an intervention has produced an unintended consequence.

Most importantly, begin developing future leaders. Do not make yourself the permanent centre of competence. Invite the person with the strongest fit to lead the relevant work. Ask team members to explain the reasoning behind a recommendation, assess consequences, identify the benchmark of excellence and consider what would make the result replicable. Leadership capacity grows when people are trusted with real thinking and real responsibility, then supported to learn from what happens.

Functional flow does not mean vagueness about authority. Someone still owns the decision. The difference is that title does not silence expertise, and collaboration does not become an endless committee. The responsible person listens widely, decides clearly, explains enough of the reasoning for others to understand the direction, and then the team throws its weight behind the decision. If new evidence appears, the decision can be revisited through the same disciplined process. Until then, alignment matters.

Do not make yourself the permanent centre of competence.