What is a 30-60-90-day plan?
๐ **Source:** [What is a 30-60-90-day plan?](https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager)
> [!note]+ Document Notes
> tags: [management, onboarding, goal-setting]
> author: Franziska Hinkelmann
> source: LeadDev
> reference: [https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager]
> date created: 2025-11-06 00:00
>
> # ๐ท๏ธ Title: What is a 30-60-90-day plan?
>
<!-- deep-read:sections start -->
## ๐งญ Table of Contents
- [๐ Summary](#-summary)
- [๐ Main Content](#-main-content)
- [๐๏ธ Notes](#๏ธ-notes)
- [๐ References](#-references)
- [๐ฃ๏ธ Paraphrase](#๏ธ-paraphrase)
- [๐ฐ Newsletter](#-newsletter)
- [โ
Action Items](#-action-items)
- [๐งช Hypotheses](#-hypotheses)
- [๐ Methodology](#-methodology)
- [โ Questions](#-questions)
- [๐ฎ Future Research](#-future-research)
- [๐ก Implications](#-implications)
- [๐ง Learning Styles Assessment](#-learning-styles-assessment)
- [๐ Accessibility Assessment](#-accessibility-assessment)
- [๐ DEIB Assessment](#-deib-assessment)
- [โ
Logical Validity](#-logical-validity)
- [๐ก๏ธ DARVO Analysis](#-darvo-analysis)
- [๐ฏ Conclusion](#-conclusion)
### ๐ References
- Include links cited in or relevant to the article.
## ๐ Summary
- What happened: A senior engineering manager outlines how to craft a 30-60-90-day plan to align expectations, set SMART goals, and build relationships.
- Why it matters: Reduces onboarding ambiguity, accelerates impact, and creates shared expectations with leadership.
- Key stakeholders: New managers, direct managers, cross-functional partners, teams.
- Risks and tradeoffs: Over-prescription vs. flexibility; meeting load vs. execution; early commitments vs. learning time.
- Bottom line: Use a flexible, SMART, stakeholder-aligned 30-60-90 as your onboarding operating system.
## ๐ Main Content
- Core argument: A 30-60-90 plan clarifies expectations, surfaces priorities, and structures learning and delivery. Treat it as guidance, not a rigid schedule.
- Key practices:
- Think big picture: tie short-term steps to long-term org goals.
- Set SMART goals (specific, measurable, attainable, realistic, time-bound).
- Be a sponge: learn culture, OKRs, roadmaps, risks.
- Meet broadly: peers, cross-org partners, prior manager; listen with a light agenda.
- Level-set with your manager to refine scope and priorities.
- Stay flexible and iterate on the plan.
- Context/definitions:
- SMART goals: widely used goal-quality rubric.
- OKRs: objectives and key results to align focus and outcomes.
- Uncertainties: Exact milestones vary by org maturity, team health, and domain complexity.
### ๐๏ธ Notes
- โA 30-60-90-day plan... allows you to identify the largest challenges, and set goals... a guide, a resource, and a checklist.โ
- Big picture first: Why were you hired? What does leadership want to see in three months?
- SMART examples: โSchedule 5 initial 1:1s with product stakeholders in the first 30 daysโ; โSet up 3 regular 1:1s... within 60 days.โ
- Be a sponge: ask many questions; read roadmaps and OKRs across your org and partners.
- Meetings: prioritize peers, cross-functional counterparts, and, if possible, the prior manager; listen more, prep a light agenda; check LinkedIn for rapport.
- Flexibility: the value is as much the thinking as the checklist; adjust regularly.
- Manager alignment: review your plan to find gaps and deprioritize tasks; agree on short- and long-term expectations.
- Sample high-priority goals: cross-org partnership, shared key result, revenue reporting plan, testing strategy to reduce incidents by 5%.
- Sample 30/60/90:
- 30: kickoff partnership, map stakeholders, draft one-pager, first revenue reporting draft.
- 60: draft testing strategy, execute workstreams, OKR mid-quarter check-in, iterate revenue report.
- 90: implement SLO reporting, finalize Q2 OKRs and shared KR, iterate testing strategy.
## ๐ References
- What is a 30-60-90-day plan? (LeadDev) (https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager)
- SMART criteria (https://en.wikipedia.org/wiki/SMART_criteria)
- Objectives and Key Results (OKRs) overview (https://www.whatmatters.com/articles/okr-quickstart-guide)
## ๐ฃ๏ธ Paraphrase
- Paragraph A: A 30-60-90 plan clarifies expectations and priorities so new managers can learn fast and deliver meaningful early wins.
- Paragraph B: Make goals SMART, meet widely to learn context, align with your manager, and adapt the plan as you go.
## ๐ฐ Newsletter
- New role? This practical 30-60-90 guide helps managers set SMART goals, align with leadership, and build cross-functional momentum fast. Tie early deliverables to OKRs, schedule targeted 1:1s, and keep the plan flexible. Useful for PMs and WordPress leads driving release cycles and contributor onboarding. Resource picks: SMART goals primer, OKR quickstart, and meeting agenda templates for stakeholder mapping.
## โ
Action Items
#### DevRel
- Define 3 SMART onboarding goals tied to OKRs; schedule 10 stakeholder 1:1s; publish a 1-pager on priorities.
- Run a newcomer workshop; create SDK quickstarts; instrument funnel attribution.
- Launch examples repo and DX templates; set doc SLAs.
- Plan a content series and track UTM-to-activation metrics.
- Stand up community surveys; propose CoC enforcement workflow; enable feedback loops.
#### OSPO
- Draft contribution policy + decision rights; set license review cadence.
- Establish vulnerability intake and embargo policy; sign releases.
- Create SBOM ownership and freshness SLOs.
- Offer office hours for licensing/security; document legal guardrails.
- Align exec reporting and OKRs for strategic initiatives.
#### Community
- Maintainers: roadmap clinic; release checklists.
- Contributors: onboarding paths and pairing sessions.
- Sponsors: milestones with transparent budgets and impact reports.
- Ecosystem: cross-project incident drills.
#### WordPress
- Core: triage cadence, perf budgets, release criteria.
- Core Performance: dashboards, profiling plans, bounties.
- Core AI: guardrails, eval sets, pilot projects.
- Core Program Team: rituals, dependencies, retros.
- Mobile/Playground: telemetry, offline UX, browser labs.
- Community/Training/Marketing/Support: kits, paths, calendars, SLAs.
- Accessibility/Meta/CLI/Hosting/Tide/Openverse/Themes/Plugins: audits, roadmaps, provenance checks.
#### The WPOCC
- Programs: fellowships, microgrants, stipends.
- Projects: governance clinics, doc sprints.
- Funding: matched grants, milestone payouts, transparent ledgers.
### FAIR
- Independence: provenance and signature checks.
- Policies: transparent funding, sunset clauses.
- Governance artifacts: charters and scorecards.
## ๐งช Hypotheses
- Managers with SMART 30-60-90 plans achieve earlier cross-team alignment than those without.
- Early stakeholder 1:1 density correlates with faster OKR clarity.
- A quantified testing strategy within 60 days reduces incident rates by โฅ5% within a quarter.
- Manager-reviewed plans increase role expectation clarity scores.
### ๐ Methodology
- Quasi-experiment across new managers: plan vs. no-plan cohorts.
- Metrics: time to shared KR, OKR clarity survey, incident rate deltas, onboarding NPS.
- Analyses: difference-in-differences; survival analysis for โtime to alignment.โ
### โ Questions
- Which plan elements most predict early wins?
- How many 1:1s maximize learning without overload?
- Whatโs the optimal balance between learning and delivery by week?
### ๐ฎ Future Research
- Domain-specific 30-60-90 templates (infra vs. product).
- Impact of manager coaching frequency on plan outcomes.
### ๐ก Implications
- Practice: standardize 30-60-90 templates in onboarding.
- Policy: require manager sign-off within week 2.
- Education: train on SMART/OKRs and stakeholder mapping.
### ๐ง Learning Styles Assessment
- Reading level: FKGL โ 9โ10 (estimate).
#### ๐ Visual learners
- Present: example lists and structure.
- Improve: timeline and stakeholder map visuals.
#### ๐ Aural learners
- Present: none.
- Improve: 3-minute audio summary.
#### ๐ฃ๏ธ Verbal learners
- Present: definitions and examples.
- Improve: glossary and analogies.
#### ๐งฉ Kinesthetic learners
- Present: stepwise template.
- Improve: checklists and fill-in worksheets.
#### ๐ง Logical learners
- Present: phased plan and OKR logic.
- Improve: decision trees for prioritization.
#### ๐งโ๐คโ๐ง Social learners
- Present: many 1:1s.
- Improve: cohort onboarding circles.
#### ๐งโโ๏ธ Solitary learners
- Present: self-guided template.
- Improve: reflection prompts and self-checks.
#### ๐ฟ Naturalistic learners
- Present: none.
- Improve: ecosystem mapping analogies.
### ๐ Accessibility Assessment
#### Screen reader semantics
- Present: clear headings.
- Improve: alt text for figures, language attributes.
#### Keyboard navigation
- Present: logical structure.
- Improve: ensure visible focus and skip links (site-level).
#### Contrast and readability
- Present: generally readable.
- Improve: confirm 4.5:1 contrast and line-height.
#### Text resizing and reflow
- Present: responsive text.
- Improve: motion prefs and clipping checks.
#### Media and captions
- Present: none needed.
- Improve: provide captions for any future media.
#### Forms and interactions
- Present: n/a.
- Improve: accessible toasts and input targets if adding templates.
#### Standards reference
- Map to WCAG 2.2 AA for headings, contrast, nav, media.
### ๐ DEIB Assessment
- Cultural breadth: examples are tech-centric; broaden regions and functions.
- Inclusive language: mostly neutral; reduce jargon or define terms.
- Neurodiversity: structured and chunked; add icons+text labels.
- Representation: add varied personas and voices.
- Psychological safety: encourage listening-first; add escalation paths.
### โ
Logical Validity
#### Strong reasoning
- Inductive: examples show how SMART goals enable measurementโclear and actionable.
- Causal: aligning with manager -> shared expectations; plausible and widely supported.
#### Fallacies
- None notable; avoids overgeneralization by urging flexibility.
#### Tone of voice
- Supportive, pragmatic, concise.
### ๐ก๏ธ DARVO Analysis
- None present; no denial, attack, or role reversal rhetoric.
## ๐ฏ Conclusion
- Bottom line: Use a flexible 30-60-90 plan with SMART goals, stakeholder 1:1s, and manager alignment to accelerate impact.
- Next steps: Draft big-picture goals, convert to SMART monthly targets, schedule key 1:1s, review with your manager, iterate weekly.
## ๐งฑ Refactor Appendix (append after ๐ฏ Conclusion)
### ๐ Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: **H3**.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] 5โ10-word present-tense claim
> [!quote] [What is a 30-60-90-day plan?](https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager) by [[Franziska Hinkelmann]] via [[LeadDev]]. Published 2025-11-05. Accessed 2025-11-06.
> โA 30-60-90-day plan... is a guide, a resource, and a checklist.โ
Two lines: context and use. Cite data if relevant.
[view highlight](https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5โ10-word present-tense claim
> [!quote] [What is a 30-60-90-day plan?](https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager)
> โGoals should be SMART: specific, measurable, attainable, realistic, and time-bound.โ
Two lines: context and use.
[view highlight](https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager#H2) #xref ID:rw_[MISSING]
---
### ๐ Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: **H4**.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Manager alignment accelerates onboarding outcomes
- Align on plan by week 2 to reduce rework.
- Links: [[Onboarding]] [[Leadership-Communication]]
#### [Z2] Early 1:1 density improves OKR clarity
- โฅ10 targeted 1:1s in 30 days correlates with clarity.
- Links: [[Stakeholder-Mapping]] [[OKRs]]
---
### โ๏ธ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line โ โRefactor: Extract selection to new note (content only).โ
- Keep each line short and self-contained.
- [F1] Draft my 30-60-90 with three SMART goals โ context/https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager #fleeting #inbox
- [F2] Schedule 10 stakeholder 1:1s in first month โ context/https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager #fleeting #inbox
- [F3] Review plan with manager in week two โ context/https://leaddev.com/career-development/your-30-60-90-day-plan-new-manager #fleeting #inbox
---
<!-- deep-read:sections end -->