First 90 Days Executive Coaching Plan: A Practical Roadmap

A first 90 days executive coaching plan helps a new leader examine the situation, clarify the mandate and make better-grounded choices. It is a thinking and review structure alongside the executive's organizational responsibilities. The coach does not become the person's manager, authorize resources or certify that a transition is complete.

A turnaround and a stable function need different early actions. An internal promotion can also change relationships and authority even when the leader knows the organization. Use the first three months to make learning and decisions visible, without turning an arbitrary deadline into a requirement to announce transformation.

Coachful is our #1 recommendation for organizing coaching preparation, agreed client actions and review across that period. Connect the actual sessions and resources to a clear purpose. Keep personnel files, operational decisions and employer approvals in the appropriate organizational systems.

Agree the coaching job before creating the timetable

Identify the client, sponsor and any other person with a defined role. Agree the purpose, contact, information exchange, financial arrangement and ending. A sponsor paying for coaching does not automatically receive private session notes. A leader agreeing to coaching does not automatically agree to a separate assessment or stakeholder survey.

The current ICF Code addresses agreements, information exchange, records, conflicts and accurate professional scope. Apply those responsibilities to the actual relationship. It is professional guidance within its stated scope, not a universal legal confidentiality guarantee or evidence that a particular coaching plan works. ICF Code of Ethics.

Make the support route concrete. Specify where the executive submits a question, who can see it and when the coach replies. Distinguish live sessions, preparation, administrative messages and any paid written coaching. An open chat channel should not imply an urgent-response service.

Choose the evaluation question early. “Did the leader make a clearer request and verify the response?” is different from “Did the company improve financially?” Coaching can contribute to a decision without establishing causation for the business result.

A flexible five-phase roadmap

This is an original planning aid, not a validated ninety-day protocol. Windows overlap, and urgent responsibilities cannot wait for a phase to arrive. A useful transition review can move backward when new information changes the mandate.

Michael Watkins's 2003 Harvard Business School interview emphasizes learning about a transition's situation, culture and relationships, including for internal moves. It is a practitioner interview about leadership transitions; it does not validate this five-phase coaching schedule or guarantee an early win. A Fast Start on Your New Job.

Phase 1: turn listening into questions you can verify

Begin with the appointment's purpose, current obligations and people affected. Ask what must continue, what needs attention and where the executive's assumptions come from. Learning does not mean postponing an incident response or another urgent responsibility; the appropriate organizational process still acts.

Use consistent questions without making every conversation identical: “What should I understand before changing this?”, “Which commitment is easy to overlook?” and “Where does your work depend on another person's decision?” Ask for a specific example when a description becomes a general judgment about a colleague.

Separate observation, report and interpretation. A missed handover is observable; “the team has no ownership” is an explanation requiring more examination. Write who supplied an account, its context, alternative explanations and the next source to check. The coach usually does not need a named employee file to help the leader test their reasoning.

A completed listening review should explain what changed in the executive's understanding. Ten meetings can produce useful learning or ten repetitions of the same favored account. Include the missing perspective rather than treating the meeting count as the result.

Phase 2: examine conditions before judging capability

Consider responsibilities, information, authority, workload, relevant skills and support. Apparent hesitation may reflect conflicting instructions or a dependency outside a person's control. Equally, a missing skill may need training or another intervention. Coaching inquiry should not predetermine either explanation.

HSE's Role standard concerns clarity and compatibility of responsibilities and routes for raising uncertainty. Its Demands standard includes achievable work in relation to agreed hours. These are organizational work-design considerations in a stress-management framework, not a coaching diagnosis or proof that resilience training can repair conflicting requirements. HSE Role; HSE Demands.

Ask what the person has actually had an opportunity to demonstrate. Use the authorized personnel process when formal performance assessment is needed. A coach's private impression should not become an unofficial appraisal sent to HR.

The output is a small list of conditions and decisions, with an evidence source and owner. It might identify a training need, conflicting priority or unclear approval rule. Keep unknowns explicit rather than assigning every employee a rapid skill-and-will label.

Phase 3: make the mandate review a real decision

Compare the recruitment brief, current obligations and what the leader has learned. Which priorities can coexist? What can the leader decide? Who owns the budget or the dependency? Clarification starts immediately; the later checkpoint deliberately revisits it with better evidence.

A useful request contains the conflict, evidence, options, consequences and decision needed. “I need more support” may begin the conversation, but it does not establish what the sponsor has agreed to provide. Record a request, a review appointment and an authorization as different states.

For an internal promotion, revisit relationships with former peers. An informal arrangement that worked before may now create ambiguity or a perceived unfair advantage. Name which decisions belong to the new role and which still need consultation or approval.

The coach can help prepare the conversation and test assumptions. The executive and authorized organization members make the actual decision. A persuasive rehearsal cannot guarantee their response.

Phase 4: choose an improvement that can reveal a problem

Select a change that serves the mandate and fits actual authority. Define the intended benefit, owner, resource allowance, affected people, safeguards and review. Consider what work moves and who accepts that change before calling the idea a quick win.

Choose evidence capable of contradicting the executive's preferred story. If the improvement is a clearer handover, a completed form is insufficient when the receiving person has not accepted responsibility. If the change adds review work elsewhere, count that cost.

A small pilot can reveal a useful repair without proving the whole service has improved. Stop, revise or narrow it when appropriate. Credibility can come from reporting a failed assumption and an accurate next decision, rather than displaying an early victory at any cost.

Phase 5: produce a charter people can actually use

A working charter identifies current purpose, priorities, decision rights, dependencies, communication practices and unresolved questions. It need not be a polished three-year strategy. The test is whether it helps someone make a real choice.

Choose meeting and reporting rhythms from the work. A new weekly meeting should have a defined job; it does not automatically improve coordination. Identify which existing discussion it replaces or what cannot be resolved through a simpler written handoff.

At the closing review, distinguish learning, agreed decisions, implementation, observed behavior and business outcomes. A useful report can say a decision is still pending. Decide separately whether further coaching, another kind of support or independent continuation fits the next period.

A completed fictional ninety-day plan

Adele becomes vice president of service operations on Monday 27 July 2026. Day 90 is Saturday 24 October. Adele, coach Otto, sponsor Ilan and all colleagues and results below are fictional. The example concerns coaching around the transition, not a claim that a department can be transformed on this schedule.

The coaching arrangement has six sixty-minute private sessions on 28 July, 11 August, 25 August, 8 September, 29 September and 20 October, plus thirty-minute sponsor conversations on 27 July and 23 October. Two bounded written-question rounds are included through Adele's direct Coachful conversation with Otto. Questions are due by noon London time on 28 August and 16 October, with replies due by 17:00 on 31 August and 19 October respectively. Additional written coaching is not included. The employer pays the separately agreed fee; coaching does not give Otto operational authority.

The initial sponsor discussion establishes that Adele wants to test assumptions and make clearer priority requests. Ilan can receive session attendance and an approved summary of the development focus, decisions and unresolved support. Private notes, employee opinions and recordings are excluded from routine reporting. Each shared summary needs Adele's approval.

At the first private session Adele describes missed handovers as lack of ownership. Otto asks what evidence would distinguish unwillingness from an unclear receiving role. Adele agrees to examine the work before deciding how to address it. Her original conclusion remains a hypothesis.

Complete the listening and capacity outputs

By 10 August Adele has spoken with nine people across service, product and operations. One required regional perspective is still missing because the colleague is away. She records that gap and holds the conversation when the colleague returns rather than treating absence as reluctance.

The later conversation changes her understanding. The sending team believed a handover was complete when a ticket was assigned. The receiving team did not regard an assignment as accepted responsibility until a named person confirmed it. Adele had been interpreting the gap between those rules as an attitude problem.

The capacity review identifies six weekly project hours that service manager Sam can allocate after existing commitments. A proposed new-service launch needs an estimated eight of those hours and a handover pilot needs four. Both cannot fit in the same six-hour allowance.

This is a specific project-capacity estimate, not a total of everyone's contracted working hours. Adele checks it with Sam before bringing it to Ilan. She does not call the team resistant because the arithmetic conflicts with the recruitment aspiration.

Obtain the actual priority agreement

In the first written round, submitted on 28 August, Adele asks Otto to review how she frames the choice. Otto replies on 31 August through Direct, within the agreed deadline. The reply helps her distinguish a resource request from a promise to launch. It does not authorize the proposed staffing.

Adele then gives Ilan this request:

Sam has verified six weekly project hours after current commitments. The proposed launch needs eight and the handover pilot four. I recommend the pilot first and a separate launch review. Please decide whether we defer launch work or authorize another resource; I cannot commit both within the current allowance.

On 1 September Ilan approves the handover pilot for the weeks beginning 7, 14 and 21 September and defers launch work to a later review. Sam accepts responsibility for allocating work within the six-hour weekly project allowance. Adele records the actual decision and tells affected colleagues that launch work is deferred, not funded or completed.

There is a narrow but useful authority distinction: Sam may adjust pilot work inside the six hours, while extra capacity or a new launch commitment returns to Ilan. The pilot's planned use is four hours each week. The remaining two are unallocated project capacity, not a promise of another simultaneous launch.

Run the bounded improvement and preserve its exceptions

The original handover trial uses a named receiving owner, the information needed for the next action and explicit acceptance. Sam briefs the people doing the work and agrees that unresolved ownership goes to the existing operational escalation route. Otto does not become the escalation owner.

The first review examines four handovers. Three have clear accepted owners; one is assigned to a team but lacks individual acceptance. Adele initially drafts “all handovers now have owners.” In the 8 September session she checks the four records with Otto and corrects the statement before sharing it.

For the unresolved fourth case, Adele asks the receiving manager to identify who can accept it. That manager names a person, who actually accepts in the operational record. All four now have accepted owners, but only three did at the original check. The repair must not erase that initial defect.

In the third week, five new handovers produce four accepted owners and one exception outside the receiving team's delegated authority. That exception is escalated and remains pending at the pilot cutoff. Across nine distinct handovers, eight have accepted owners by that cutoff; the nine are not a controlled sample or proof of faster service.

Actual pilot work takes four, five and four hours in the respective weeks: thirteen rather than twelve planned hours. Sam authorizes the extra hour in the second week within the delegated six-hour allowance before it is used. The remaining weekly project capacity is two, one and two hours. No overtime or hidden launch work is treated as available capacity.

The observed result is a clearer acceptance condition and a visible authority exception. Adele has not demonstrated that every handover problem is fixed, that staff attitudes changed or that the postponed service can launch on the old date.

Finish the coaching review and the sponsor report

On 16 October Adele submits the second written question: can the closing report say that the pilot improved ownership? Otto replies on 19 October through Direct. He asks her to specify the observation and preserve the pending exception rather than attribute an internal attitude change. Adele acknowledges the two written replies in Direct on 31 August and 19 October respectively.

At the 20 October private review Adele chooses this development conclusion: “I am checking the receiving condition before attributing a missed handover to unwillingness.” She identifies the corrected first-four statement as evidence of that practice. She also acknowledges that she still feels impatient when decisions take longer than expected.

She does not request any additional written work. The agreed paid support does not silently extend because an organizational exception remains unresolved. The 20 October review confirms that the two written rounds were completed and identifies which work belongs to the organization after the coaching term.

On 21 October, when Ilan asks for Otto's private notes before the closing conversation, Otto refers to the actual information agreement. Adele prepares and approves this limited report on 22 October:

The coaching focus was to test explanations and make clearer priority requests. The launch and handover work were separated by an actual priority decision. Nine pilot handovers were reviewed: eight had accepted receiving owners by the cutoff, including one repaired after the first check; one authority exception remains pending. Pilot work used thirteen hours against twelve planned, within Sam's delegated weekly capacity. No service-speed or revenue effect has been established. The next launch and authority decisions remain organizational responsibilities.

Otto sends only the approved report to Ilan for the 23 October sponsor conversation. Ilan confirms receiving it, accepts that the launch remains deferred and agrees to review the pending authority exception and launch options on 13 November. Adele confirms that she understands that next decision route.

The final sponsor conversation is the second thirty-minute meeting already in the arrangement. It does not add another private session or authorize new coaching. Day 90 arrives with a completed coaching review and an actual next organizational review date, not with the launch or authority exception falsely declared resolved.

Adele's working charter at the end of the period

The charter does not pretend the whole department now shares one interpretation. It names decisions colleagues can use and questions that remain open. A later revision can be a response to new evidence rather than proof that the ninety-day plan failed.

Organize the work in Coachful

1. Record the coaching purpose. Use a client goal for the agreed development focus, with language the executive can correct.
2. Prepare a short original worksheet. Ask what changed, which assumption needs checking and what decision or support is needed.
3. Assign it deliberately. Use the client's Worksheets & resources and the normal Assign workflow. A copied private link alone is not access.
4. Track the executive's actions. Use the normal client plan for a chosen request or review. A task tick does not establish external approval.
5. Keep the agreed reply route. Adele and Otto use their Direct conversation; Otto opens All messages, Direct and Adele's conversation.
6. Review before sharing. Keep the sponsor-facing document separate and send only the exact account approved under the agreement.

Unshared journal and takeaway pages can hold personal reflection. Explain that an enabled Share with coach control deliberately exposes the selected page through the relevant coaching access. A private reflection is not an automatic sponsor update; a separate minimal action summary may be more appropriate.

The employer's authoritative handover, staffing and escalation records stay with the employer. Coachful holds only the permitted coaching preparation and actions. A clean client dashboard is not evidence that a workstream is approved, funded or delivered.

For other possible structures, compare the executive coaching frameworks guide. Use the executive coaching ROI guide before making stronger contribution or financial claims. The Coachful feature overview supports the operational preparation and review workflow.

Troubleshoot the plan before adding more activity

The listening tour produces a fixed verdict. Ask which observation would change it and whose account is missing. Adele's absent regional perspective changed an attitude explanation into a role-condition question.

The sponsor wants incompatible priorities. Present the verified constraint, options and actual decision needed. Rehearsing a confident promise cannot create the missing capacity.

The early win has an exception. Keep the exception, initial defect and actual repair visible. Eight accepted owners out of nine is different from “ownership is fixed.”

The sponsor requests private material. Return to the agreement and obtain the appropriate exact sharing decision. Do not assume payment authorizes all notes or promise that every record can never be lawfully disclosed.

Frequently asked questions

Must the plan start before the executive joins?

No. It can start before appointment where appropriate or after the person arrives. Use the information, agreement and access actually available. A coach should not gather confidential employer information simply because a prospective executive wants an early start.

How many sessions are needed?

Choose contact from the purpose, transition, capacity and budget. The example uses six private sessions and two separately agreed sponsor meetings; it is not an evidence-based universal dose or a promise that six conversations produce success.

Should the executive avoid making changes early?

No. Respond to urgent responsibilities through the appropriate processes while learning before unnecessary change. A listening phase is a review structure, not permission to defer a serious operational issue.

Does this fit an internal promotion?

Yes, with adaptation. Revisit expectations, authority and relationships with former peers. Familiarity can conceal assumptions about the new role, so check them rather than treating organizational knowledge as complete.

What counts as a successful ninety-day review?

An accurate account of learning, decisions, implementation, evidence and remaining support needs. It need not announce transformation. Adele's review closes the agreed coaching work while leaving a genuine launch and authority decision with the organization.