What to focus on in the first 90 days

As a new engineering manager your initial job is to reduce unknowns, protect team delivery, and build trust with engineers and stakeholders. The checklist below breaks the first 90 days into three horizons with concrete actions, measurable signals, and decision rules you can use to choose what to change and when.

Days 0 to 30: Understand and stabilize

Primary goals

Build relationships, learn the codebase and processes at a high level, and identify immediate risks that could block delivery or damage morale.

Checklist

1. Meet every direct report one on one with a 60 minute session. Ask about recent wins, current blockers, career goals, and team norms. Signal of progress: a prioritized list of three recurring blockers across conversations.
2. Interview key stakeholders from product, design, QA, SRE, and product marketing. Confirm expectations for delivery, definition of success, and escalation paths. Signal of progress: aligned list of primary stakeholder expectations and top risks.
3. Review active work including current sprints, high priority tickets, and any critical incidents or outages from the last six months. Signal of progress: a short risk register you can share with your manager.
4. Map team responsibilities and ownership for services, libraries, and cross functional dependencies. Signal of progress: a responsibilities diagram or table you can iterate with the team.
5. Assess hiring and capacity by reviewing open roles, expected departures, and upcoming ramp needs. Signal of progress: a hiring priority list agreed with your manager.
6. Document quick wins and immediate fixes that unblock the team without large process changes. Signal of progress: two to four completed quick wins in the first month.

Days 31 to 60: Shape direction and address root causes

Primary goals

Use what you learned to adjust priorities, fix root causes of persistent problems, and begin shaping longer term team practices.

Checklist

1. Run a team health pulse focused on delivery, quality, and morale. Use a short anonymous survey or a retrospective format and look for repeating themes. Signal of progress: a ranked list of top three improvement areas with owners.
2. Set or clarify team goals for the next quarter that link to product outcomes. Ensure the goals are measurable and timebound. Signal of progress: a draft goals document shared with stakeholders for feedback.
3. Introduce or refine core routines such as planning cadence, sprint reviews, and incident postmortems. Limit changes to two or three routines in this window. Signal of progress: routines adopted in at least two cycles and documented norms.
4. Address technical bottlenecks by sponsoring focused work such as reducing high risk tech debt, improving CI stability, or reducing build times. Frame work as experiments with hypotheses and success criteria. Signal of progress: a timeboxed experiment with measurable success criteria.
5. Build a development plan with each report including short term objectives and a 6 month growth plan. Signal of progress: written plans agreed and visible to the individual.
6. Make early hiring decisions where capacity or skills are missing. Standardize interview scorecards and shortlists. Signal of progress: at least one new hire or an active candidate pipeline for critical roles.

Days 61 to 90: Cement practices and begin scaling impact

Primary goals

Convert early learning into durable team practices, show measurable improvements, and create a forward plan for the next six months.

Checklist

1. Measure impact of changes using simple signals such as cycle time, release frequency, or customer incidents depending on team scope. Use at most three metrics and track them weekly. Signal of progress: observable trend in at least one metric linked to your interventions.
2. Run a focused retrospective on onboarding and early changes with the team and stakeholders. Capture what worked, what did not, and decisions for the next quarter. Signal of progress: a short action list with owners for the next 90 days.
3. Clarify promotion and performance expectations if none exist or if they need alignment. Share promotion criteria and performance rhythms with the team. Signal of progress: at least one documented clarification applied consistently.
4. Expand delegation and leadership opportunities by naming tech leads, project owners, or area leads with clear responsibilities. Signal of progress: named owners taking visible responsibility for outcomes.
5. Agree a 6 month roadmap with stakeholders that balances new work, maintenance, and capacity for urgent issues. Signal of progress: signed off roadmap and communicated tradeoffs.
6. Sponsor at least one cross team improvement such as improving release coordination, onboarding documentation, or observability. Signal of progress: a project plan and a short pilot completed.

Daily and weekly routines to start immediately

Early routines create predictability. Keep these simple and time limited and review their value after two cycles.

• Weekly one on ones with direct reports. Keep a running shared agenda and action log.
• Weekly sync with product partner to clarify priorities and surface tradeoffs.
• Weekly leadership touchpoint such as a short status email or dashboard for your manager covering risks and decisions you need.
• Fortnightly team retro or health check to iterate on team processes.

Decision rules to choose what to change first

Use simple criteria to prioritize interventions. Ask these three questions for any proposed change: what risk does this remove, what outcome does this enable, and how reversible is it if it harms flow. Prefer changes that remove clear risks, enable measurable outcomes, and are reversible or low cost if they fail.

Common pitfalls and how to avoid them

• Rushing to restructure before you understand relationships and unspoken dependencies. Avoid by delaying structural changes until you have at least two months of insight.
• Making permanent process changes too quickly instead of running short experiments. Avoid by timeboxing pilots and defining success criteria up front.
• Acting without stakeholder alignment that creates friction for delivery. Avoid by documenting assumptions and sharing tradeoffs early.
• Neglecting career conversations which damages retention. Avoid by scheduling development planning meetings in your first 60 days.

How to use this checklist with your manager and your team

Share a trimmed version of this checklist with your manager in your 30 day and 90 day updates. Use it as a negotiation tool to set expectations for hiring, scope, and investment in platform work. With your team use the checklist as a living artifact; iterate the items with feedback and make visible the signals you are tracking so progress is clear.

Practical examples of success signals you can show at 90 days

Examples that stakeholders find credible include a published team roadmap with tradeoffs explained, a reduction in weekly high priority blockers, an agreed hiring plan for critical skills, completed experiments that reduced a significant pain point, and documented development plans for your direct reports. Each signal should map back to one of the three horizons above.

Begin each week by picking the one or two highest impact items from this checklist and protect time to do them. Revisit the checklist after 90 days and convert it into a quarterly plan focused on outcomes and sustainable team practices.