It is the third week of the role. You have read the strategic plan, attended the leadership team meetings, sat in on two all-hands calls, and had a one-on-one with every direct report your predecessor left behind. The org chart makes sense. The OKRs are visible in the tracker. And you have a quiet, persistent feeling that something significant is not adding up, and that you cannot point to it in anything you have been handed. That feeling is not imposter syndrome. It is pattern recognition. The plan describes one organization. The meetings you have sat in describe a different one. The gap between those two things is your first real job.
The first 90 days as a Chief of Staff are when the alignment picture is most murky and most consequential. Murky because you do not yet know which signals to trust. Consequential because the read you build in this window shapes every intervention you make for the next year. Most CoS frameworks treat this period as a listening phase, and they are right, but they stop short of the harder question: you are not just listening for information. You are trying to understand whether the people responsible for executing the strategy actually understand it and believe in it. Those are different questions from "what is going on around here."
Days 1-30: Map What Is Real, Not What Is Documented
The MIT Sloan Management Review found that only 28% of leaders responsible for executing strategy can name three of their organization's strategic priorities. That finding describes your leadership team right now, before you have done anything about it. Not because the people around you are disengaged or careless. Because the gap between what gets documented in a strategic plan and what actually lives in people's heads is enormous, and nobody has been measuring it.
Your first 30 days are not a listening tour. They are a mapping exercise. And the map you are building has three specific layers.
The first layer is decision authority. Who actually drives decisions in this organization, as opposed to who is listed as the decision-maker on the RACI? In almost every organization, these are different people. The formal chart says one thing. The meetings tell you another. Watch for who speaks last in a disagreement. Watch for whose silence causes a conversation to stall. Those are the people whose alignment actually matters.
The second layer is resource allocation versus stated priority. The Economist Intelligence Unit (2013) found that 85% of senior executives said poor strategy execution was responsible for their organization's most significant failure. The mechanism behind that failure is almost always the same: stated priorities and actual resource allocation do not match. Someone says the Q3 initiative is the priority. The three people with the most capacity to move it are spending 60% of their time on something else. That gap is measurable in the first 30 days if you are looking for it.
The third layer is who goes quiet, and this one takes longer to see clearly than the first two, because silence requires context before it means anything. Every leadership team has people who contribute in certain rooms and disappear in others. The person who is vocal with you in a one-on-one and silent in the leadership team meeting is not shy. She is managing a risk calculation. What she is unwilling to say in front of the group is your most important unmeasured signal. Edmondson (1999) established that psychological safety, the belief that speaking up will not be penalized, is the precondition for honest communication in teams. In your first 30 days, you are not trying to fix the safety conditions yet. You are trying to map where they are missing, because those are the places where the alignment picture will be most wrong.
Days 31-60: Your Assumptions Are Wrong on at Least One Major Team
This is the section most CoS frameworks skip, and skipping it is expensive.
By day 30, you have a working theory of the organization. You know roughly who is aligned to the direction, who has reservations, and where the execution risk sits. That theory is wrong. Not in every detail, but on at least one thing that matters, and probably on the team you feel most confident about. That is not a failure of observation. It is a structural feature of the role.
Here is why. In the first 30 days, people are performing for the new CoS. Not dishonestly. But people know they are being evaluated, and they present the version of themselves that reflects well. Kotter (2012) described this as one of the central challenges in leading change: the signals a leader receives during a transition period are filtered through the social dynamics of that transition, not through normal operating conditions. The team that looked fully aligned in week two may look very different in week seven, when the pressure of an actual deadline surfaces the priorities that did not show up in the meeting.
Days 31-60 are when you test your read. The mechanism is simple: stop observing and start introducing low-stakes friction.
Low-stakes friction means asking questions that require the other person to take a position. Not "how are things going with the Q3 initiative?" That produces a status update. Ask instead: "If you had to choose between accelerating the Q3 initiative and holding the quality bar on the existing product line, which would you prioritize right now?" That question does not have a safe answer, which is exactly why it is useful. The response tells you whether the person's priorities are actually aligned to the strategy or whether they are managing their relationship with you.
Do this systematically. Ask the same substantive question to three or four people in different functions. Not the same wording, but the same underlying tension. The spread in their answers is a rough map of where the priority gap, the distance between what the strategy says and what people actually believe should be first, is widest.
The reasonable concern here is that this approach feels like testing people, and that it could damage trust if done clumsily. The answer to that concern is precision. You are not trying to catch anyone. You are trying to build a reliable picture before the first planning cycle, when misreads become expensive. The leaders who resist this kind of diagnostic are often the ones most comfortable with the version of alignment that looks fine in a meeting and disappears in execution. Senge (1990) called this the difference between espoused theory, what people say they believe, and theory in use, what their actual behavior reveals. Days 31-60 are where you start seeing the gap between those two things.
One more thing about this window. Someone will surprise you. There will be a person you wrote off as low-influence who turns out to be the clearest strategic thinker on the team. There will be a senior leader you expected to be fully bought in who has a fundamental disagreement with the direction that they have been carrying quietly for months. Both of these are discoveries you need before day 90, not after. The surprise is the signal. Pay attention to what contradicts your map, not just what confirms it.
A Specific Situation Worth Naming
A 200-person professional services firm, about three years into a growth phase, brought in a new CoS after a period of rapid hiring. The CEO had run the strategic planning cycle himself for the first time. The output was a clean set of OKRs. Three strategic priorities, clearly stated. Every leadership team member had signed off.
By week six of the new CoS's tenure, something was visibly wrong with one of the three priorities. The initiative existed in the tracker. The responsible leaders were attending the check-in meetings. Progress was being reported. And nothing was moving.
The CoS did not find the problem in the dashboard. She found it in a conversation with a mid-level team lead who had been in the room when the OKRs were set and had never said the thing she was about to say out loud: the priority assumed a capability the organization did not yet have, and the people responsible for executing it knew it and had decided, collectively and informally, to wait for someone else to name it first.
The alignment gap in that organization was not a comprehension gap. It was a belief gap. The team understood the priority. They did not believe it was executable in the timeframe the strategy required. The OKR tracker showed green because nobody had found a way to log "we think this is not achievable" as a status update.
The CoS spent the next three weeks building the conditions for that conversation to happen in the room. Lencioni (2012) described this as the foundational work of organizational health: creating enough trust and safety that the real conversation replaces the performed one. The honest conversation eventually happened. The initiative was restructured. The plan moved. But the six weeks before that conversation were six weeks of motion that produced nothing, and they were recoverable only because the CoS was looking for the belief gap instead of reading the green dashboard.
What the Tools Get Wrong in This Window
Most of the systems a CoS inherits were built to answer a different question.
OKR trackers tell you whether tasks are marked complete. Engagement surveys tell you how people feel about their job, their manager, and the organization. Both are useful. Neither tells you whether the people responsible for executing the strategy understand it clearly enough to make good decisions when the plan hits friction, or believe in it enough to prioritize it over the comfortable alternative.
That is the gap. And most CoS onboarding frameworks fill it with more meetings, more surveys, and more dashboards, which produces more data of the same kind the organization was already collecting, not a different kind of signal.
The honest limitation worth naming: no tool closes this gap on its own. Pulse measures whether the people in a planning initiative understand and believe in the direction, at the initiative level, monthly, without requiring a formal survey. That matters because it surfaces the belief gap before it shows in outcomes. But Pulse does not replace the conversation the CoS needs to have when the belief gap appears. It identifies where to have it. That distinction is important and worth holding precisely, because the CoS who thinks a measurement tool replaces judgment is in the same trouble as the CoS who thinks the dashboard replaces leadership.
Days 61-90: Build the First Real Picture
By day 60, you have enough to build something. Not certainty. A working picture, specific enough to act on, honest enough to be useful.
The first real picture has four components. Who understands the three strategic priorities clearly enough to explain them to someone else without prompting. Who believes in the priorities enough to prioritize them when they conflict with something more comfortable. Where the priority gap is widest between what the strategy says and where time and money are actually going. And what the leadership team will not say in the room, which is almost always the most important of the four, and the one that takes the longest to surface because it requires the CoS to have earned enough trust that silence stops feeling like the safer option.
That fourth component is the one that most measurement tools miss entirely. The nod in the room is not data. Neither is the silence. But they are signals if you know what you are watching for. Gallup research shows that only one in three employees strongly agrees they know what their organization stands for. Among the leaders responsible for making that real, the number is not much better. By day 90, you should be able to name which third of your leadership team is in that confident minority, and what is true about the other two-thirds that has not yet surfaced in any formal process.
What you are building toward is an intervention map. Not a problem list. A map that tells you where to direct your attention in the first real planning cycle, which conversation to have and with whom, which assumption needs to be tested in the room before it becomes the assumption everyone is executing against.
The 90-day window closes faster than it feels like it should. The read you build in it sets the conditions for everything that follows. Here is how Pulse helps Chiefs of Staff build and maintain that picture across the first planning cycle and beyond.
One Thing to Do Before the Window Closes
Before day 90 ends, run this exercise. Ask five people at different levels of the organization, not just the leadership team, to tell you what they understand the organization's top three priorities to be for the next quarter. Do not prompt. Do not correct. Just listen.
The spread in those answers is your alignment gap, stated plainly, without any technology required. The CoS who does this and finds near-consensus has inherited a different organization than the CoS who finds five different answers. Pulse makes that measurement ongoing and systematic rather than a one-time exercise. But the exercise itself costs nothing and takes forty minutes. Do it before anything else, because what you hear will tell you more about the organization than anything in the strategic plan.
You ran the planning session. You can know what happened after. Here is what alignment intelligence looks like for a chief of staff.