{"id":9483,"date":"2026-09-25T09:00:00","date_gmt":"2026-09-25T05:00:00","guid":{"rendered":"https:\/\/matsh.co\/en\/?p=9483"},"modified":"2026-09-28T16:55:59","modified_gmt":"2026-09-28T12:55:59","slug":"first-90-days-as-a-manager","status":"publish","type":"post","link":"https:\/\/matsh.co\/en\/first-90-days-as-a-manager\/","title":{"rendered":"Your First 90 Days as a Manager: A Practical Sequence"},"content":{"rendered":"

.section-h{border-left:4px solid #c0561b;padding-left:14px;margin:40px 0 18px;font-size:1.3rem;color:#3d2408}
\n.pull-fact{border-left:4px solid #c0561b;background:#fdf5ee;padding:20px 26px;margin:28px 0;font-size:1.08rem;font-weight:600;color:#3d2408;line-height:1.6}
\n.step{border:1.5px solid #ecd0a8;border-radius:14px;padding:22px 26px;margin:16px 0;display:flex;gap:18px}
\n.step .num{background:#c0561b;color:#fff;width:34px;height:34px;border-radius:50%;display:flex;align-items:center;justify-content:center;font-weight:800;flex-shrink:0;font-size:.95rem}
\n.step h4{margin:0 0 6px;color:#3d2408;font-size:1rem}
\n.step p{margin:0;color:#4a5568;font-size:.9rem;line-height:1.75}
\n.worked{background:#fdf5ee;border-radius:12px;padding:26px 30px;margin:24px 0}
\n.worked h4{margin:0 0 10px;color:#3d2408;font-size:1rem}
\n.worked p{margin:0 0 12px;color:#3a4a5e;font-size:.9rem;line-height:1.8}
\n.worked .label{font-weight:700;color:#c0561b;font-size:.82rem;text-transform:uppercase;letter-spacing:.03em}
\n.fail-box{background:#fdf3f8;border-radius:10px;padding:16px 20px;margin:10px 0;font-size:.88rem;color:#4a1030}
\n.artifact{border:2px dashed #ecd0a8;border-radius:12px;padding:22px 26px;margin:20px 0}
\n.artifact h4{margin:0 0 10px;color:#3d2408;font-size:.98rem}
\n.artifact ul{margin:0;padding-left:20px;color:#3a4a5e;font-size:.88rem;line-height:1.9}
\n.related-wrap{background:#f8fafc;border:1.5px solid #dde3ec;border-radius:14px;padding:28px 32px;margin:36px 0}
\n.related-wrap h3{margin:0 0 16px;font-size:1.05rem;color:#122f42}
\n.related-grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(240px,1fr));gap:14px}
\n.related-card{background:#fff;border:1px solid #dde3ec;border-radius:10px;padding:14px 16px;text-decoration:none;display:block}
\n.related-card strong{display:block;color:#122f42;font-size:.9rem;margin-bottom:4px}
\n.related-card span{color:#6b7a99;font-size:.8rem}
\n.cta-wrap{background:linear-gradient(135deg,#c0561b,#3d2408);border-radius:16px;padding:36px 40px;margin:36px 0;color:#fff}
\n.cta-wrap h3{color:#fff;margin:0 0 10px;font-size:1.25rem}
\n.cta-wrap p{opacity:.9;margin:0 0 20px;font-size:.95rem;line-height:1.7}
\n.cta-links{display:flex;flex-wrap:wrap;gap:10px}
\n.cta-links a{background:rgba(255,255,255,.15);border:1px solid rgba(255,255,255,.3);border-radius:8px;padding:10px 18px;font-size:.85rem;color:#fff;text-decoration:none;font-weight:600}<\/p>\n

Moving into a management role changes the work. A new manager must learn the team, clarify expectations, handle relationships differently, make decisions with incomplete information and build the habits needed for regular people management. A 90-day sequence can help organise that transition, but it should be treated as a practical planning framework rather than a scientifically fixed window or a guarantee of later success.<\/p>\n

UK research from the Chartered Management Institute found that many people enter management roles without formal management and leadership training. CIPD guidance likewise emphasises that line managers need people-management capability, support and development, not just technical expertise.<\/p>\n

Source: Chartered Management Institute, Better Management Report<\/a><\/p>\n

Source: CIPD, Line managers’ role in supporting the people profession<\/a><\/p>\n

A useful first-quarter principle is to learn before making unnecessary changes. Listening, clarifying expectations and understanding the team’s work give a new manager better information for later decisions.<\/div>\n
\n

Starting point: promoted from the team she’s now leading<\/h4>\n

Illustrative scenario<\/span> Consider Layla, a fictional composite example of a strong individual contributor promoted to lead a 12-person customer-support team in Riyadh. Her former peers now report to her, including one colleague, Faisal, who also applied for the role. The scenario is used throughout this guide to show how the sequence might work in practice; it is not presented as a real MATSH client case or measured outcome.<\/p>\n<\/div>\n

Days 1 to 30: Listen before you act<\/h2>\n
\n
1<\/div>\n
\n

Have a genuine one-on-one with every direct report, early<\/h4>\n

Not a performance conversation, a listening one: what’s working, what’s frustrating, what they’d change if they could. This does two things simultaneously: it surfaces real information before you’ve formed premature opinions, and it signals that you value their perspective before asking anything of them.<\/p>\n<\/div>\n<\/div>\n

\n
2<\/div>\n
\n

Resist the urge to change things immediately<\/h4>\n

New managers often feel pressure to demonstrate impact fast, which frequently means changing a process before understanding why it exists. Something that looks inefficient from outside often has a reason that becomes clear only after a few weeks of actually running it.<\/p>\n<\/div>\n<\/div>\n

\n
3<\/div>\n
\n

Clarify expectations explicitly, both directions<\/h4>\n

What does your manager expect from you in this role, specifically, in the first quarter? What do your direct reports need clarified about how you’ll operate differently than your predecessor, or than you did as a peer? Ambiguity here compounds; address it directly and early.<\/p>\n<\/div>\n<\/div>\n

\n

Applied: the first 30 days<\/h4>\n

Illustrative scenario<\/span> In the example, Layla meets each team member individually during the first few weeks, including Faisal, and asks what is working, what is getting in the way and what they need from her as their new manager. She also delays two proposed process changes until she understands why the existing process works as it does. One turns out to be linked to a compliance requirement she had not previously encountered.<\/p>\n<\/div>\n

Days 31 to 60: Establish how you’ll actually operate<\/h2>\n
\n
1<\/div>\n
\n

Set a consistent rhythm for one-on-ones and team communication<\/h4>\n

Weekly or biweekly one-on-ones, a clear channel for urgent issues and a predictable cadence for team updates can make communication easier to plan and reduce uncertainty about when issues will be discussed.<\/p>\n<\/div>\n<\/div>\n

\n
2<\/div>\n
\n

Make your first real decision, and make it well<\/h4>\n

By now you have enough context to act. Choose one specific, visible problem your team actually raised in the listening phase, and address it properly, with a clear rationale communicated back to the team. This is where credibility genuinely starts to build, through demonstrated follow-through rather than promises.<\/p>\n<\/div>\n<\/div>\n

\n
3<\/div>\n
\n

Address the hardest relational dynamic directly, not by avoiding it<\/h4>\n

If there’s tension, a colleague who wanted the role, an existing conflict you’ve inherited, it doesn’t resolve itself by being ignored. A direct, respectful conversation about it early prevents it from calcifying into something harder to address in month six.<\/p>\n<\/div>\n<\/div>\n

\n

Applied: days 31 to 60<\/h4>\n

Illustrative scenario<\/span> In the example, the team repeatedly raises an unclear escalation path for difficult customer cases. Layla works with two experienced team members to clarify it, explains the change and then monitors whether the process is easier to use. She also has a direct conversation with Faisal about the changed working relationship rather than assuming the promotion outcome will never affect how they work together.<\/p>\n<\/div>\n

Days 61 to 90: Solidify and look forward<\/h2>\n
\n
1<\/div>\n
\n

Set clear goals for the next quarter, collaboratively<\/h4>\n

Not goals imposed unilaterally, but developed with input from the team on what’s realistic and what matters. This is also where you start setting individual development goals for direct reports, based on what you’ve learned about each of them.<\/p>\n<\/div>\n<\/div>\n

\n
2<\/div>\n
\n

Ask for honest feedback on your own performance so far<\/h4>\n

Directly: “What’s working about how I’m leading, and what would you change?” Few new managers do this, and it signals genuine openness rather than defensiveness about your own learning curve.<\/p>\n<\/div>\n<\/div>\n

\n
3<\/div>\n
\n

Reflect honestly on what you’d do differently<\/h4>\n

Not for anyone else’s benefit, for your own. What decisions held up well? What would you handle differently now with more context? This reflection is what turns a first 90 days into genuine learning rather than just survival.<\/p>\n<\/div>\n<\/div>\n

Use a 30-60-90 management operating rhythm<\/h2>\n

The first 90 days work better when the manager treats the transition as a sequence of evidence, decisions and routines rather than a list of quick wins. Each phase should produce a small number of visible outputs that make the next phase easier.<\/p>\n

First 90 days operating rhythm<\/figcaption>
\n
Days 1\u201330<\/strong>
Listen, map expectations, understand work and relationships<\/span><\/div>\n
Days 31\u201360<\/strong>
Clarify priorities, decision rights, routines and feedback<\/span><\/div>\n
Days 61\u201390<\/strong>
Strengthen accountability, test improvements and plan the next quarter<\/span><\/div>\n<\/div>\n<\/figure>\n

At the end of the first month, the manager should be able to explain what the team is responsible for, where work gets stuck, which stakeholders matter and what employees expect from the role. By day 60, those observations should be turning into clearer priorities, meeting rhythms, delegation rules and one-to-one conversations.<\/p>\n

By day 90, the manager should not have \u201cfixed everything.\u201d The better test is whether the team has clearer expectations, a more predictable way to surface problems, visible ownership of priorities and a small number of improvements based on evidence rather than first impressions.<\/p>\n

This rhythm also protects against two opposite mistakes: changing too much before understanding the system, and spending so long listening that the team never sees a decision. The sequence gives both diagnosis and action a defined place.<\/p>\n

Common failure patterns in the first 90 days<\/h2>\n
Trying to be liked instead of trusted.<\/strong> Avoiding necessary but uncomfortable decisions to preserve popularity usually backfires, since teams generally respect competent fairness more than constant agreeableness.<\/div>\n
Changing everything at once.<\/strong> Even well-intentioned changes, introduced too fast and without context, read as disruptive rather than improving, and burn credibility you haven’t built yet.<\/div>\n
Avoiding the awkward relational dynamic.<\/strong> A colleague who wanted your role, tension inherited from a previous manager, an existing conflict. Ignoring it doesn’t make it disappear, it just delays and usually worsens the eventual reckoning.<\/div>\n
Managing former peers exactly as you did before the promotion.<\/strong> The relationship has genuinely changed, and pretending it hasn’t, avoiding necessary managerial conversations to preserve the old peer dynamic, creates confusion about where you actually stand.<\/div>\n
\n

A 90-day structure to work from<\/h4>\n