How to Create a 90-Day Plan – Part 2: Writing and Structure

You’ve spent 6-8 hours researching. You have a comprehensive understanding of the company, the role, and the actual problems you’ll solve.

Now comes the harder part: translating that research into a document that demonstrates strategic thinking without sounding like everyone else.

This is where most candidates fail. Not because they haven’t done the research, but because the writing process reveals whether you actually understand what you learned or whether you’re just reorganizing corporate buzzwords.

This guide walks through the 4-6 hours of focused writing time required to produce a plan worth presenting, plus another 2-3 hours of revision to remove the generic language that makes hiring managers tune out.

If you haven’t completed the research phase yet, start with Part 1: Research & Foundation first. You can’t write what you don’t understand.

The AI Problem Everyone’s Facing (And Not Talking About)

Before we get into the writing process, let’s address what’s happening right now in hiring.

Most candidates are using ChatGPT or other AI tools to write their 90-day plans. Hiring managers know this. They can tell.

Here’s what generic AI output looks like:

• “Foster cross-functional collaboration to drive alignment”
• “Leverage data-driven insights to optimize processes”
• “Create synergies across teams to accelerate execution”
• “Build relationships with key stakeholders to ensure buy-in”

These phrases appear in 80% of AI-generated plans. They sound professional. They’re grammatically correct. They’re completely meaningless.

The problem isn’t that candidates are using AI. The problem is they’re using it wrong.

What doesn’t work: “ChatGPT, write me a 90-day plan for VP of Sales Operations at a Series B SaaS company.”

You’ll get a template. It will look good. It will sound exactly like the other 47 candidates who used the same prompt.

What does work: Do the research yourself. Form your own insights. Use AI to help organize and structure YOUR thinking, not to generate thinking for you.

The depth comes from you. AI can help you articulate it clearly, but it can’t create insights you don’t have.

This matters because hiring managers aren’t evaluating whether you can prompt ChatGPT. They’re evaluating whether you understand the problem you’re walking into and how you think about solving it. That has to come from you.

From Research Notes to Document Structure (45-60 Minutes)

You have pages of research notes. Company analysis, stakeholder intelligence, Glassdoor patterns, your 12-question diagnostic framework.

The first writing task is creating an outline that organizes this into a logical flow.

The Standard Structure

Most effective 90-day plans follow this format:

1. Title slide (Your name, role, date)
2. Executive Summary (1 page/slide)
3. Days 1-30: Diagnostic Phase (1-2 pages/slides)
4. Days 31-60: Testing Phase (1-2 pages/slides)
5. Days 61-90: Scale Phase (1-2 pages/slides)
6. Success Metrics (1 page/slide – can be integrated into phase slides)
7. Close (risks, assumptions, or next steps)

Total length: 6-10 slides or pages maximum.

Anything longer signals you can’t prioritize. Anything shorter suggests you haven’t thought it through.

Mapping Research to Structure

Create a working outline document. For each section, pull the relevant research:

Executive Summary draws from:

• Your problem statement (from job description analysis)
• Your three focus areas (from diagnostic framework)
• Your phase-specific metrics (from metrics research)

Days 1-30 draws from:

• Your 12 questions that need validation
• Your stakeholder map (who to interview)
• Your hiring trigger analysis (what context you’re entering)

Days 31-60 draws from:

• Your three focus areas (which one to pilot first)
• Your risk assessment (what could go wrong)
• Your constraint analysis (what resources you have)

Days 61-90 draws from:

• Your scale strategy (how to expand the pilot)
• Your success metrics (measurable impact)
• Your sustainability plan (systems that persist)

This mapping exercise takes 45-60 minutes but prevents you from staring at a blank page wondering what to write.

Writing the Executive Summary (90-120 Minutes)

The executive summary is the hardest section to write and the most important to get right.

This is where hiring managers decide whether to keep reading or mentally check out.

What Makes an Executive Summary Work

Three components, in this order:

1. One sentence that names the actual business problem

Not the job description sanitized version. The real constraint the role exists to solve.

Weak: “The Sales Operations team needs improved processes and better alignment.”

Strong: “Sales operations can’t scale deal velocity because quote-to-cash takes 18 days due to manual handoffs between Sales, Legal, and Finance.”

The difference: specificity. The second version tells me you understand the bottleneck, you’ve quantified it, and you know who’s involved.

2. Your three highest-priority focus areas (one per phase)

One sentence per focus area. What you’ll DO, not what you’ll “focus on.”

Format: “Days X-Y: [Specific action] to [Specific outcome]”

Example:

• Days 1-30: Map current quote-to-cash workflow through observation and stakeholder interviews to identify the 3 highest-impact bottlenecks
• Days 31-60: Pilot automated approval workflow for deals <$50K with Northeast sales region, targeting <10 day cycle time
• Days 61-90: Scale automation to all regions for standard deals, achieving <12 day quote-to-cash for 65%+ of deal volume

Notice what’s visible: sequencing (diagnose → test → scale), scoping (specific deal size, specific region), and metrics (10 days, 12 days, 65% of volume).

3. How you’ll measure success at each phase

One metric per phase. Keep it simple.

• Day 30: Diagnostic complete, validated with VP Sales and CFO, 3 bottlenecks identified
• Day 60: Pilot shows cycle time <10 days for 70%+ of test deals, sales rep satisfaction ≥4/5
• Day 90: Rolled out to all regions, achieving <12 days for 65% of volume, 40+ hours/week time saved

This executive summary took 90+ minutes to write because every word has to be precise. You’re compressing 6-8 hours of research into half a page.

This is exactly what hiring managers actually want in a 30-60-90 day plan—evidence that you understand the problem and how you’ll approach solving it.

The AI Trap in Executive Summaries

If you ask AI to write your executive summary, you’ll get something like:

“In the first 30 days, I will build relationships with key stakeholders and develop a deep understanding of current processes. In days 31-60, I will identify opportunities for improvement and begin implementing strategic initiatives. In days 61-90, I will drive measurable results and establish systems for sustained success.”

This is useless. It could apply to any role. It demonstrates no understanding of the actual problem.

The executive summary requires YOUR synthesis of YOUR research. AI can help you polish the wording once you’ve written it, but it can’t create the insight.

Writing Days 1-30: The Diagnostic Phase (60-90 Minutes)

The first 30 days should read like investigation, not execution.

This is where senior candidates separate from junior ones. Junior candidates front-load action. Senior candidates front-load questions.

The Language That Works

Your days 1-30 section should be built around verbs like:

• Interview
• Map
• Observe
• Document
• Validate
• Synthesize
• Confirm

Not:

• Implement
• Launch
• Execute
• Deploy
• Roll out

Those action verbs belong in days 31-60 and 61-90.

Structure That Demonstrates Rigor

Break days 1-30 into weekly focus areas:

Week 1: Stakeholder Learning

• Conduct 1:1s with [specific people/roles]: ask what’s working, what’s blocked, what they wish I knew before changing anything
• Shadow [specific workflow/team] to observe current process end-to-end
• Review last 6 months of [specific data/reports] to understand historical patterns

Week 2: Process Mapping

• Document current quote-to-cash workflow, identify handoffs and delay points
• Interview [specific teams] about exception cases and workarounds
• Quantify current state: average cycle time, error rate, volume by deal size

Week 3: Root Cause Analysis

• Identify top 3 bottlenecks based on data + stakeholder input
• Validate whether bottleneck is process, tooling, or organizational (separate symptoms from causes)
• Assess what’s been tried before and why it didn’t stick

Week 4: Synthesis and Validation

• Create diagnostic summary: problem statement, root causes, proposed focus areas
• Present findings to VP Sales and CFO for validation
• Adjust based on feedback before moving to execution phase

Notice what’s visible: structure, specificity, validation checkpoints, and a clear progression from observation to diagnosis to confirmation.

This connects directly to understanding the difference between the three phases—days 1-30 isn’t “lite version of days 31-60,” it’s a fundamentally different kind of work.

What to Include vs. Exclude

Include:

• Specific stakeholders you’ll interview (by role, not by name)
• Specific processes you’ll map
• Specific data you’ll review
• How you’ll validate your understanding

Exclude:

• Generic goals like “build relationships”
• Vague learning objectives like “understand the culture”
• Execution activities that belong in later phases
• Day-by-day detail (week-level is detailed enough)

Writing this section takes 60-90 minutes because you’re balancing specificity with appropriate scope. Too vague, and you look like you haven’t thought it through. Too detailed, and you look like you don’t understand that plans adapt.

Writing Days 31-60: The Testing Phase (60 Minutes)

Days 31-60 is where you demonstrate judgment about risk management.

The key principle: test your hypothesis on limited scope before scaling.

Pilot Language That Shows Strategic Thinking

Your days 31-60 section should answer:

• What are you testing? (specific initiative)
• With whom? (limited scope—one team, one region, one product)
• Why this scope? (rationale for boundaries)
• What defines success? (measurable criteria)
• What’s the decision gate? (if X, then Y logic)

Example structure:

Initiative: Automate quote approval for deals <$50K

Scope: Pilot with Northeast sales region (15 reps, ~60% of their deals fall under $50K threshold)

Rationale: Northeast team has highest deal volume and most consistent deal structure (fewer custom terms). Strong regional VP who’s supportive of process improvements. If it works here, other regions will adopt based on proof.

Success Criteria:

• Cycle time for <$50K deals drops from 18 days to <10 days
• Sales rep satisfaction with process ≥4/5 (measured via survey)
• Error rate (deals requiring rework) stays <5%
• Finance and Legal teams confirm no increase in compliance issues

Decision Gate (Day 60):

• If all success criteria met → scale to all regions in days 61-90
• If cycle time improves but satisfaction low → iterate on UX based on rep feedback, extend pilot 2 weeks
• If compliance issues emerge → add validation checkpoints, retest with smaller scope
• If no improvement → revisit diagnosis, validate we’re solving the right bottleneck

This level of detail demonstrates:

• You know how to scope appropriately
• You’ve thought about what could go wrong
• You can make decisions with imperfect information
• You won’t scale something that doesn’t work

The Build vs. Buy Decision

If your pilot requires tools, technology, or resources, address this explicitly:

“Week 5-6: Assess whether current quote tool supports automated approval workflows. If yes, configure workflow logic. If no, evaluate low-code alternatives (estimated 2-week implementation). Budget assumption: <$10K for tooling if new tool required.”

You’re showing you’ve thought about dependencies and have contingency plans.

Writing this section takes about 60 minutes because you’re translating your research into a concrete pilot design with clear decision criteria.

Writing Days 61-90: The Scale Phase (60 Minutes)

Days 61-90 is not “bigger version of days 31-60.” It’s about making what worked sustainable.

From Pilot to System

Your days 61-90 section should show:

Expansion Strategy:

• How you’ll roll out to broader scope (all regions, all teams, full volume)
• Timeline for rollout (staggered vs. all-at-once, with rationale)
• Support structure during expansion (training, documentation, office hours)

Sustainability Plan:

• Who owns the process after you move to other priorities
• Documentation created (process guides, troubleshooting, FAQs)
• Ongoing measurement (dashboard, weekly reports, review cadence)
• Iteration mechanism (how does the process improve over time)

Impact Metrics:

• Baseline → Target (with actual numbers)
• Coverage (% of volume affected)
• Time saved (quantified hours/week)
• Secondary benefits (improved satisfaction, reduced errors, faster close rates)

Example:

Week 9-10: Rollout Preparation

• Train all regional sales managers on new workflow (2-hour sessions per region)
• Create sales rep quick-start guide and video walkthrough
• Set up Slack channel for questions/issues during rollout
• Establish weekly check-in with Finance and Legal to monitor compliance

Week 11-12: Phased Rollout

• Week 11: Expand to West and Central regions
• Week 12: Expand to remaining regions
• Monitor daily: cycle time, error rate, support volume
• Hold office hours 2x/week for first two weeks post-rollout

Week 13: Measurement and Handoff

• Baseline: 18-day average cycle time for <$50K deals
• Target achieved: 11-day average (39% improvement)
• Coverage: 65% of deal volume now processes in <12 days (vs. 15% previously)
• Time saved: Estimated 45 hours/week across sales team (based on reduced back-and-forth)
• Process ownership transferred to Sales Ops Manager, monthly review cadence established

Course-Correction Language

Include what you’ll do if the pilot revealed problems:

“Pilot feedback indicated Sales reps need reminder notifications 24 hours before approval deadlines. Added to workflow before full rollout. Legal flagged that deals with non-standard payment terms still require manual review—added flag in tool to route these appropriately.”

This shows you iterate based on learning, not just execute blindly.

Writing this section takes about 60 minutes because you’re designing a rollout that demonstrates you can finish what you start.

Using AI to Organize (Not Generate) Your Thinking

Now that you’ve drafted your content, AI can actually be helpful—if you use it correctly.

Where AI Adds Value

Condensing without losing meaning:

You: “I wrote this paragraph but it’s too long. Help me tighten it to 2-3 sentences without losing the key points: [paste paragraph]”

This works because YOU wrote the insight. AI is just helping you articulate it more cleanly.

Checking for clarity:

You: “Does this success criteria make sense or is it too vague: [paste criteria]”

AI can spot where you’re being imprecise and suggest more specific language.

Restructuring for flow:

You: “I have these five points I want to make in days 1-30. What’s the most logical order: [list points]”

AI can suggest sequencing, but the points themselves came from your research.

Where AI Destroys Value

Generating strategy:

“Write a 90-day plan for [role]” produces generic templates. Don’t do this.

Creating insights:

“What should my focus areas be for this role?” AI doesn’t know the company context. You do.

Writing from scratch:

If AI writes your executive summary, it will sound like everyone else’s executive summary. Hiring managers notice.

The Tell-Tale AI Phrases to Remove

When you review your draft, search for these generic phrases and replace them with specific language:

• “Foster collaboration” → Name WHO needs to work together and HOW
• “Drive alignment” → Specify what’s misaligned and what aligned would look like
• “Leverage insights” → State the actual insight and how you’ll use it
• “Create synergies” → Delete. This means nothing.
• “Optimize processes” → Specify which process and how it will improve
• “Build relationships” → Name who and why their support matters

Generic AI language destroys credibility. Your plan should sound like strategic thinking, not corporate Mad Libs.

Formatting and Presentation (45-60 Minutes)

You have strong content. Now make it readable.

Slide Deck vs. Document

Slide deck (PowerPoint/Google Slides):

• Better for visual hierarchy
• Forces conciseness
• Easier to present if asked to walk through it
• Standard for many industries

Written document (Google Doc/PDF):

• Better for detailed narrative
• Easier to email/share
• Can include more context
• Preferred in some industries (consulting, academic, healthcare)

Default to slides unless you know the company prefers documents.

Visual Hierarchy Principles

Title slide: Your name, role title, date. Clean and professional.

Each content slide:

• Clear header (e.g., “Days 1-30: Diagnostic Phase”)
• 3-5 bullet points maximum
• Each bullet can have sub-bullets, but don’t nest more than one level
• Use bold for emphasis on key metrics or deliverables

Avoid:

• Walls of text (if a bullet point is >2 lines, break it up)
• Tiny fonts (nothing smaller than 11pt for documents, 16pt for slides)
• Excessive colors or graphics (professional, not decorative)
• Stock photos (they add nothing and look amateurish)

Length Guidelines

6-10 slides/pages total:

1. Title
2. Executive Summary
3. Days 1-30 (1-2 slides if very detailed)
4. Days 31-60 (1-2 slides if pilot has multiple components)
5. Days 61-90 (1-2 slides if rollout is complex)
6. Close/Next Steps

Longer than 10 slides signals you can’t prioritize. Shorter than 6 suggests you haven’t thought it through.

The Revision Process (2-3 Hours)

Your first draft is never your final draft.

Plan for three revision passes, each with a different focus:

Pass 1: Clarity and Flow (60 minutes)

Read through as if you’re the hiring manager who knows nothing about your thought process.

• Does each section follow logically from the previous one?
• Are there gaps where you assume knowledge the reader doesn’t have?
• Do your metrics tie back to the problem statement?
• Can someone understand your plan without you explaining it?

Fix: Add transitions, clarify assumptions, connect dots explicitly.

Pass 2: Cutting Redundancy (45 minutes)

Look for places where you’re saying the same thing twice.

• Do you mention stakeholder interviews in both the executive summary and days 1-30? Pick one place.
• Are you repeating metrics across multiple sections? Consolidate.
• Have you explained your rationale three times? Once is enough.

Tight writing demonstrates clear thinking. Redundancy suggests unclear thinking.

Pass 3: Strengthening Specificity (45-60 minutes)

This is where you hunt down and replace generic language.

Search for:

• “Key stakeholders” → Name specific roles
• “Improve processes” → Name the process and how it improves
• “Drive results” → State the specific result and metric
• “Build alignment” → Specify who needs to align on what
• “Create impact” → Quantify the impact

Every vague phrase is an opportunity to demonstrate you actually understand what you’re talking about.

Getting Feedback (Optional but Valuable)

If you know someone who’s hired for similar roles, show them your plan and ask:

• Does this demonstrate strategic thinking or does it feel templated?
• What’s unclear or confusing?
• Do the metrics seem realistic?
• Where does it sound like generic AI vs. genuine insight?

Fresh eyes catch what you miss because you’re too close to it.

Common Writing Mistakes That Undermine Credibility

Mistake #1: Leading with credentials instead of problem

Weak opening: “With 10 years of experience in sales operations and a proven track record of driving results…”

Strong opening: “Sales operations can’t scale deal velocity because quote-to-cash takes 18 days…”

Get to the problem immediately. Your credentials are in your resume.

Mistake #2: Promising outcomes you can’t control

Weak: “Increase revenue by 25% in first quarter”

Strong: “Reduce sales cycle by 15 days for enterprise deals, enabling reps to close 2-3 additional deals per quarter”

You can’t control revenue in 90 days. You can control cycle time, which influences revenue.

Mistake #3: Generic goals without company specificity

If your plan could work at any company in the industry, it’s too generic.

Reference something specific: recent leadership change, product launch, market shift, funding round, competitive pressure.

Mistake #4: No decision points or contingencies

Plans that assume everything will work perfectly signal naivety.

Include “if/then” logic. Show you’ve thought about what happens when reality diverges from plan.

Mistake #5: Trying to solve everything

Three focused areas beats seven scattered ones.

If you try to fix everything, hiring managers assume you can’t prioritize.

Quality Checklist: Before You Share Your Plan

Run through this checklist before sending your plan to anyone:

Content Quality:

• ☐ Executive summary names specific business problem (not generic challenge)
• ☐ Each phase has measurable success criteria
• ☐ Days 1-30 focuses on diagnosis, not execution
• ☐ Days 31-60 includes pilot scope and decision criteria
• ☐ Days 61-90 shows scale plan and sustainability
• ☐ Plan references company-specific context (not generic to industry)
• ☐ Metrics are scoped to what you can influence in 90 days

Language Quality:

• ☐ No generic AI phrases (“foster collaboration,” “drive alignment,” “create synergies”)
• ☐ Specific stakeholders named by role, not “key stakeholders”
• ☐ Vague verbs replaced with concrete actions
• ☐ Decision points and contingencies included
• ☐ Reads like strategic thinking, not template filling

Format Quality:

• ☐ Length is 6-10 slides/pages
• ☐ Visual hierarchy is clear (headers, bullets, white space)
• ☐ No typos or grammatical errors
• ☐ Font size readable (11pt+ for docs, 16pt+ for slides)
• ☐ Professional appearance without unnecessary graphics

Strategic Quality:

• ☐ Demonstrates you understand the actual problem (not just job description version)
• ☐ Shows judgment about risk management (test before scale)
• ☐ Includes systems thinking (sustainability, not just execution)
• ☐ Reflects your experience and insights (not generic best practices)

The Time Investment Reality

Let’s be honest about what you’ve committed to:

• Part 1 (Research): 6-8 hours
• Part 2 (Writing): 4-6 hours
• Revision: 2-3 hours
• Total: 12-17 hours

That’s significant. But here’s why it matters:

A well-researched, well-written 90-day plan differentiates you from every candidate who used ChatGPT to generate a template in 10 minutes.

Hiring managers can tell the difference. They read dozens of plans. The ones built on actual research and strategic thinking stand out immediately.

This is why hiring managers care more about your first 30 days than your resume. Your resume proves you can do the job. Your plan proves how you think.

Alternatively, our platform completes the research, writing, and revision process in about 10 minutes—producing a customized plan that incorporates your experience without sounding like generic AI output.

In Part 3, we’ll cover how to present and use your plan effectively in interviews. But first, you need a plan worth presenting.