The onboarding process starts before your new Chief of Staff walks through the door. The CEO has homework. Most of these items take an afternoon to pull together, but they save weeks of confusion and signal to the incoming CoS that the organization is serious about making this role work. Do not skip this phase. Every hour invested here pays back tenfold in the first month.

• ✓ CEO writes a "state of the company" brief (2-3 pages). Cover current strategy, top three priorities for the next 12 months, biggest unresolved tensions, and where the CEO personally spends too much time. This document does not need to be polished. Candor matters more than formatting. It gives the CoS a mental model before they absorb a flood of meetings.
• ✓ Share the org chart, most recent board deck, and last two quarterly plans. The CoS needs to understand the formal structure, how the company talks about itself to its board, and how priorities have evolved over the past six months. If you do not have clean versions of these, that is useful information too — it tells the CoS where documentation gaps exist.
• ✓ Set up the 1:1 cadence. Daily check-ins for the first two weeks (15-30 minutes), then three times per week through the end of month one, then twice per week going forward. Put these on the calendar before day one. The single most common failure mode in CoS onboarding is the CEO not making enough time for alignment in the early weeks.
• ✓ Prepare a list of 15-20 stakeholder meetings. Include every direct report to the CEO, key board members, and two or three individual contributors who have outsized context. For each person, write one sentence on why the CoS should talk to them and what they will learn. Pre-schedule as many of these as possible for weeks one and two.
• ✓ Define the first 2-3 "observation areas" (not projects yet). These are domains or processes the CEO suspects are broken or under-optimized. Examples: "how we prepare for board meetings," "cross-functional handoffs between product and sales," or "how decisions get made and communicated after exec team meetings." The CoS will watch, ask questions, and report back — not fix anything.
• ✓ Set up all tools and access. Calendar, Slack (including executive channels), document repositories, project management tools, board portal, and any internal dashboards. The CoS should have the same information access as the CEO on day one. If there are access decisions that require discussion, have those conversations before the start date, not during the first week.

Theme: "Absorb everything, commit to nothing"

The first two weeks are for listening. This is counterintuitive for high-performers who were hired to "get things done," but it is the most important discipline in the entire onboarding process. The CoS needs to build a mental map of how the company actually operates — not how the org chart says it operates, not how the CEO wishes it operated, but how decisions really get made, where information bottlenecks live, and which relationships carry the most influence. This map can only be built through observation and conversation, not through action.

Resist the temptation to jump in and start fixing things. Even if you spot obvious inefficiencies (and you will), acting too early risks alienating people who have not yet had a chance to understand who you are and why you are there. Trust is the currency of this role, and you cannot spend it before you have earned it.

• ✓ Shadow the CEO in all meetings. Sit in on every meeting the CEO attends for the full two weeks. Take notes, but do not contribute unless directly asked. Your goal is to understand how the CEO communicates, what topics generate energy versus friction, and where the CEO is adding value versus getting pulled into operational weeds.
• ✓ Complete the stakeholder tour (15-20 meetings). Use a consistent set of questions: What are you working on? What is going well? What is frustrating? What do you wish the CEO understood better? How do decisions get made in your area? What would you change if you could? Take detailed notes and look for patterns across conversations.
• ✓ Map the current decision-making process. Who makes which decisions? Where do decisions stall? Which meetings produce decisions and which produce only discussion? Where does the CEO need to be involved and where are they involved unnecessarily? This map becomes one of the most valuable artifacts of the first month.
• ✓ Identify the top 3 things consuming the CEO's time. Through observation and your daily check-ins, pinpoint the recurring demands on the CEO's calendar and attention. Distinguish between things the CEO should be spending time on and things that could be delegated, systematized, or eliminated.
• ✓ Document your first impressions. At the end of week two, write a 2-3 page summary of what you have observed: strengths of the organization, gaps, cultural dynamics, and areas of potential leverage. Share this with the CEO. This is not a report card — it is a calibration exercise. The CEO's reaction to your observations will teach you a great deal about what they are ready to hear and where sensitivities lie.
• ✓ Do NOT try to fix anything yet. This bears repeating. The value of the first two weeks comes from observation, not intervention. If you see something urgent, flag it to the CEO in your daily check-in and let them decide whether it needs immediate action. Your job right now is to learn, not to lead.

Theme: "Name the patterns"

Weeks three and four are the transition from pure observation to structured analysis. You have spent two weeks absorbing context. Now you need to synthesize what you have learned into something actionable. This is where the CoS begins to demonstrate the pattern recognition and synthesis skills that make the role valuable. The goal is not to have all the answers, but to articulate the right questions and frame the landscape clearly enough that the CEO and CoS can align on where to focus first.

• ✓ Present stakeholder findings to the CEO. Synthesize your 15-20 stakeholder conversations into themes. What came up repeatedly? Where are there disconnects between how different leaders see the same situation? Where does the organization's self-perception diverge from reality? Present this as a conversation, not a slide deck.
• ✓ Map the operating rhythm (or lack thereof). Document the current cadence of recurring meetings, reporting, planning cycles, and communication patterns. Identify what is working, what is performative, and what is missing. Many companies that hire a CoS do not yet have a coherent operating rhythm — defining this gap is often the single most valuable early contribution.
• ✓ Identify 3-5 quick wins. These should be concrete, completable-in-a-week improvements that are visible and appreciated. Examples: fixing a broken meeting format, creating an exec team agenda template, building a decision log, or setting up a project tracker for a stalled initiative. Quick wins build credibility and give you license to take on larger work.
• ✓ Propose your first project scope. Based on your observations and conversations with the CEO, define one medium-sized initiative you want to own in month two. Write a brief scope document: problem statement, desired outcome, key stakeholders, timeline, and what success looks like. Get the CEO's sign-off before you begin.
• ✓ Start attending leadership meetings as an observer. If you have not already been included, ask to sit in on the exec team meeting and any other leadership forums. Your role here is still primarily to listen and take notes, but you can begin contributing lightweight value — flagging follow-ups that fell through the cracks, noting decisions that were made but not communicated.
• ✓ Build your relationship with the EA and office manager. If the CEO has an executive assistant, this person is one of your most important allies. They understand the CEO's patterns, preferences, and pressure points better than almost anyone. Invest time in this relationship early. Clarify roles and boundaries so you complement each other rather than create confusion.

Theme: "Earn trust through execution"

Month two is where the CoS transitions from observer to doer. You have built a foundation of context and relationships. Now it is time to deliver. The emphasis here is on small, visible wins that demonstrate competence and build credibility across the organization. This is also the month where the CEO-CoS working relationship starts to find its natural rhythm. The daily check-ins are behind you, and you are now operating with more autonomy. Use it wisely — the trust you build in month two determines how much latitude you get in month three and beyond.

• ✓ Execute 2-3 quick wins. Deliver on the quick wins you identified in weeks three and four. Make them visible. Send a brief summary to the CEO and relevant stakeholders when each one is complete. Do not over-engineer these — speed and reliability matter more than perfection. The goal is to create a pattern of "the CoS says they will do something, and then it gets done."
• ✓ Take over meeting prep and follow-up for the exec team. This is one of the highest-leverage early responsibilities for a CoS. Own the agenda creation process, ensure pre-reads are distributed in advance, capture action items during the meeting, and follow up on commitments afterward. This single change often transforms the productivity of the exec team.
• ✓ Begin owning a recurring process. Pick one recurring workflow and make it yours — the weekly leadership sync, the monthly business review prep, or the cross-functional standup. Owning a recurring process gives you regular touchpoints with key leaders and a visible platform for demonstrating value. It also starts to embed the CoS into the operating rhythm of the company.
• ✓ Deepen relationships with 3-4 key leaders. Move beyond the introductory stakeholder meetings. Schedule informal conversations — coffee, lunch, a walk. Understand their priorities, frustrations, and communication styles. The CoS is only as effective as their relationships across the leadership team. These connections are what allow you to broker alignment, surface conflicts early, and move cross-functional work forward.
• ✓ Start building your "operating system." Create the templates, trackers, and dashboards that will become the backbone of your work. A meeting notes template, a project tracker, an initiative status dashboard, a decision log. These tools do not need to be complex, but they need to exist. The CoS who builds durable systems creates value that compounds over time.
• ✓ First formal check-in on role clarity. At the end of month two, sit down with the CEO for a structured conversation about how the role is taking shape. What is working? What is unclear? Where should the CoS spend more time? Less time? Are there areas where the CEO expected more ownership by now? This is not a performance review — it is a design conversation about the role itself.

Theme: "From observer to operator"

By month three, the CoS should be operating with real authority and clear ownership. The observation phase is over. The quick wins have established credibility. Now it is time to take on the work that justifies the role's existence: strategic initiatives, cross-functional coordination, and the operating cadence that keeps the entire executive team aligned. This is the month where the CoS goes from "the new person the CEO hired" to "someone I need to loop in on this."

• ✓ Own 1-2 strategic initiatives end-to-end. These should be cross-functional projects that matter to the CEO and require coordination across multiple teams. Examples: launching a new planning process, redesigning the company's goal-setting framework, driving a post-mortem on a failed initiative, or leading a market-entry analysis. Full ownership means you define the scope, assemble the team, run the process, and deliver the outcome.
• ✓ Establish the operating cadence. By the end of month three, there should be a clear weekly, monthly, and quarterly rhythm for the executive team — and the CoS should be the person who designed it and runs it. Weekly leadership meetings with structured agendas. Monthly business reviews. Quarterly planning cycles with defined inputs, timelines, and outputs. This cadence becomes one of the most enduring contributions a CoS makes.
• ✓ Build the board prep process. If the company has a board, the CoS should begin owning or co-owning the board meeting preparation. This includes the timeline for deck creation, the review cycle, data gathering, and logistics. Board prep is one of the CEO's most time-consuming recurring obligations, and offloading the process management (not the content) to the CoS creates immediate leverage.
• ✓ Start managing cross-functional projects. Beyond your owned initiatives, begin serving as the coordination layer for projects that span multiple teams. You do not need to manage every cross-functional effort, but you should be the person who ensures nothing falls between the cracks and that the CEO has visibility into progress without attending every meeting.
• ✓ Define your ongoing priorities and communicate them. Write a clear, concise summary of what you are focused on and share it with the CEO and the leadership team. This reduces ambiguity about your role, makes it easier for people to pull you into the right conversations, and gives the CEO confidence that you are working on the highest-leverage things.
• ✓ 90-day review with the CEO. This is the most important meeting of the entire onboarding. Sit down with the CEO and review the first three months candidly. What is working? What needs to change? What should the CoS spend more time on in the next quarter? Are there new areas of ownership to add? Use this conversation to define priorities for the next 90 days and set expectations for how the role will continue to evolve.