Skip to content
Skip to the tool
  1. 1Stage 1
  2. 2Stage 2
  3. 3Stage 3
← All tools

First 90 Days Plan

L9Project ManagementExecutionexecutionStages 1 to 2

Reference model

The First 90 Days planA banner names the biggest risk the plan attacks. Below, three sequenced blocks: days 1 to 30, set up; days 31 to 60, build and test; days 61 to 90, prove and decide. Each block has one outcome that is done or not done, two or three actions, and one owner. A timeline from day 1 to day 90 runs underneath, and a note says to graduate to quarterly OKRs when the team matures.THE BIGGEST RISK THIS PLAN ATTACKSEvery block should make it smaller. A plan that does not name the risk is a checklist.Days 1–30Set upOUTCOMEOne thing that is done or not doneACTIONSTwo or three, one per lineOWNEROne nameDays 31–60Build and testOUTCOMEOne thing that is done or not doneACTIONSTwo or three, one per lineOWNEROne nameDays 61–90Prove and decideOUTCOMEOne thing that is done or not doneACTIONSTwo or three, one per lineOWNEROne nameDay 1Day 30Day 60Day 90When the team and its rhythm mature, graduate to quarterly OKRs.

Three 30-day blocks, each with one done-or-not-done outcome, two or three actions and an owner.

About this model

For a young team, a quarterly OKR cycle asks for more structure than it has. A first-90-days plan breaks the next three months into three sequenced 30-day blocks, each with one outcome that is either done or not done, the two or three actions that get there, and the person who owns them — aimed at the single biggest risk.

The 30-60-90 day plan, a standard near-term planning format for new teams, new leaders and new ventures · Standard practice

How to read it

  • Start with the direction the team has committed to and the single biggest risk or opportunity. The plan should attack that, not be a generic checklist.
  • For each 30-day block write one outcome that can be marked done or not done (if it cannot, rewrite it), then the two or three actions that get there and who does them.
  • Review at the end of each block: done, on track or behind. When the team and the cadence mature, graduate to quarterly OKRs.

What this does

Breaks the next 90 days into three specific, sequenced blocks of work — lighter than a full quarterly OKR cycle, which assumes more structure than a very early team has yet.

When to use it

Startup phase, right after a founding team commits to a direction and needs a concrete near-term plan rather than a long-range one.

Not when: Once the team is running a real quarterly cadence with multiple contributors — move to OKRs, which formalises objectives and ownership across more than one or two people.

What happens next

As the team and cadence mature, this graduates into quarterly OKRs.

Golden thread

Builds on ←

    A starting point: it needs no earlier tool.

    Feeds into →

    • okrs

    Framework library: Execution (layer L9), lifecycle stages 1 to 2.

    Use this tool, free

    Sign in to open the worksheet. Your work saves as you type, the AI can draft the parts you have not filled in, and you finish with an analysis and a 30/60/90-day action plan.

    Sign inCreate a free account

    Hand-built by Eccellere and reviewed by Eccellere on 02/11/2026. Guidance, not advice: apply your own judgement.