100 Day Plan

100-Day Plan

When to use

Use whenever someone is entering a new leadership role, a deal has just closed and needs an integration start plan, or a transformation is kicking off and needs its opening sequence — especially when the instinct is to announce major structural changes immediately, before any credibility or diagnostic groundwork has been laid. The first 100 days set the tone for everything that follows; moving too fast on structural change before understanding the organization is one of the most common causes of new-leader failure.

What it does

Sequences the first 100 days into three distinct phases with different objectives — days 1-30 (listen and diagnose), days 31-60 (decide and communicate direction), days 61-100 (launch first initiatives) — deliberately front-loading a structured listening tour and at least one credible quick win before any major structural or personnel decision is announced.

Method

1. Days 1-30: Listen and diagnose, decide nothing major yet. Run a structured listening tour — a defined list of the 15-25 people (direct reports, key influencers across levels, a sample of frontline staff, key customers/partners if relevant) whose perspective materially shapes the diagnosis, each with the same core questions asked consistently so answers can be compared. Pair this with a fast fact base (using situation-assessment discipline) on performance, not just impressions. Resist the pressure — internal or self-imposed — to announce a direction in week one; doing so before real diagnosis undermines the credibility of whatever comes next.
2. Identify one or two credible quick wins during the listening phase — visible, achievable within 30-60 days, genuinely valued by the organization (not a change that looks good to the leader but means nothing to the people doing the work). This does double duty: it builds momentum and it demonstrates the new leadership actually listened, since the best quick wins usually surface directly from the listening tour itself.
3. Days 31-60: Synthesize the diagnosis into a stated direction. Turn the fact base and listening-tour themes into a small number of clear priorities (3-5, not fifteen) and communicate them explicitly — a new leader who never states a clear direction by day 60 reads as adrift, not as thoughtful.
4. Make the hard structural or personnel decisions in this window, not the first 30 days and not delayed past day 60. Waiting too long past the diagnosis creates its own credibility problem — organizations read prolonged ambiguity as weak leadership. The right window is after real diagnosis, not before it and not indefinitely after it.
5. Days 61-100: Launch the first real initiatives tied to the stated priorities, each with a named owner and an early milestone the organization can see — the goal by day 100 is visible motion on the stated direction, not a completed transformation.
6. Build the operating rhythm during this window: the recurring meetings, reporting cadence, and decision-rights structure the leader will run going forward — established deliberately in the first 100 days rather than accreting informally over the following year.
7. Set a day-100 checkpoint explicitly: what does the leader want to be able to say has changed by day 100, stated at day 1 so it can be honestly assessed rather than retrofitted into a success narrative later.

Inputs

• The role/situation context (new executive, post-acquisition integration, transformation kickoff)
• Known organizational context: recent history, known pain points, key stakeholders
• Any hard constraints already known (board expectations, deal terms, existing commitments)

Output format

Three-phase plan (days 1-30 / 31-60 / 61-100) with the specific objective of each phase; structured listening-tour list and question set; named quick win(s) with owner and timeline; the 3-5 stated priorities to be communicated at day 60; first initiatives launching in days 61-100 with owners and milestones; day-100 checkpoint stated in advance.

Example

A new COO joining post-acquisition resists the board's pressure to announce a reorg in week two. Instead, a structured 25-person listening tour across both legacy organizations surfaces a specific, low-risk process fix (a shared reporting template both sides already wanted) as the day-30 quick win, while the real structural integration decision — informed by what the listening tour revealed about where the two cultures genuinely differ versus where they don't — lands at day 45 with far less resistance than an immediate top-down reorg would have generated.

Common pitfalls

• Announcing major structural or personnel changes in the first 30 days, before real diagnosis, which undermines trust in the eventual direction.
• Skipping the listening tour or running it informally, missing both the diagnostic value and the credibility value of being seen to genuinely listen.
• Letting days 31-60 slip past without stating a clear direction, which reads as drift rather than thoughtfulness.
• Treating day 100 as a finish line instead of a checkpoint — the plan should hand off cleanly into the ongoing operating rhythm, not end abruptly.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Natan-Mohart
• Source: Natan-Mohart/24-strategy-skills-for-claude
• License: MIT

Install and usage instructions live in the source repository linked above.