{"id":9484,"date":"2026-09-28T09:00:00","date_gmt":"2026-09-28T05:00:00","guid":{"rendered":"https:\/\/matsh.co\/en\/?p=9484"},"modified":"2026-09-14T20:36:46","modified_gmt":"2026-09-14T16:36:46","slug":"leading-a-team-you-inherited","status":"publish","type":"post","link":"https:\/\/matsh.co\/en\/leading-a-team-you-inherited\/","title":{"rendered":"Leading a Team You Inherited: Diagnosing What You Actually Walked Into"},"content":{"rendered":"<style>\n.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}\n<\/style>\n<p>Building a team from scratch and inheriting one that already exists are treated as the same skill by most leadership training, and they aren&#8217;t. A new team has no history to account for. An inherited team arrives with established habits, existing relationships, unresolved tension, and a collective memory of how the previous manager operated, all before you&#8217;ve said a word. Walking in and applying a generic leadership playbook, without first understanding what you actually inherited, is how good managers make avoidable early mistakes. This guide covers the diagnostic work that has to come first, with one team&#8217;s real handover as the throughline.<\/p>\n<div class=\"pull-fact\">The single most common mistake when inheriting a team: assuming the previous manager&#8217;s approach was either entirely right or entirely wrong, and acting accordingly from day one. Both assumptions skip the diagnostic step that would tell you which parts of the existing dynamic are actually worth preserving.<\/div>\n<div class=\"worked\">\n<h4>Starting point: inheriting a team after an abrupt departure<\/h4>\n<p><span class=\"label\">The situation<\/span> Omar takes over a 15-person operations team in Dubai after the previous manager left suddenly, with two weeks&#8217; notice, following what HR describes only as &#8220;a values misalignment.&#8221; The team is visibly guarded in his first meeting, answers are short, and nobody volunteers information. He has no context on what actually happened, only a functioning team that seems wary of leadership generally. This example continues through the diagnostic and rebuilding process below.<\/p>\n<\/div>\n<h2 class=\"section-h\">Step one: diagnose before you act<\/h2>\n<div class=\"step\">\n<div class=\"num\">1<\/div>\n<div>\n<h4>Get the full picture from multiple sources before assuming anything<\/h4>\n<p>Your own manager, HR, and eventually the team itself all hold different pieces of context. Don&#8217;t rely on a single account, especially of a difficult departure, since it&#8217;s rarely the complete story. Approach early conversations as genuinely curious rather than already certain what happened.<\/p>\n<\/div>\n<\/div>\n<div class=\"step\">\n<div class=\"num\">2<\/div>\n<div>\n<h4>Observe before intervening<\/h4>\n<p>Sit in on existing meetings and workflows as they currently run before changing anything. What looks dysfunctional from outside sometimes has a real reason behind it; what looks fine sometimes conceals a problem the team has simply stopped mentioning because raising it never changed anything before.<\/p>\n<\/div>\n<\/div>\n<div class=\"step\">\n<div class=\"num\">3<\/div>\n<div>\n<h4>Have individual conversations focused on listening, not evaluating<\/h4>\n<p>The goal in week one isn&#8217;t to assess who&#8217;s a strong performer. It&#8217;s to understand how the team experienced the previous leadership, what they&#8217;re worried about now, and what they actually need from you. A team that&#8217;s been through a difficult transition is often more guarded than a new team would be, and rushing this step tends to confirm their wariness rather than ease it.<\/p>\n<\/div>\n<\/div>\n<div class=\"worked\">\n<h4>Applied: the first two weeks<\/h4>\n<p><span class=\"label\">What Omar actually did<\/span> Rather than accepting HR&#8217;s brief characterisation, he asked his own manager for more context and learned the previous manager had been let go partly over inconsistent, favouritism-driven decisions that the team had noticed and resented, but never had a safe channel to raise. In individual conversations, several team members mentioned, carefully and indirectly at first, feeling that some colleagues got easier assignments and more flexibility than others for reasons nobody could explain. This reframed the team&#8217;s guardedness entirely: it wasn&#8217;t wariness of leadership in general, it was a specific, justified distrust of decisions that felt arbitrary.<\/p>\n<\/div>\n<h2 class=\"section-h\">Step two: distinguish what to keep from what to change<\/h2>\n<div class=\"step\">\n<div class=\"num\">1<\/div>\n<div>\n<h4>Identify what&#8217;s actually working, and say so explicitly<\/h4>\n<p>Even a team that inherited real problems usually has genuine strengths, a strong process, real technical capability, good peer relationships among the team itself. Naming these explicitly early signals that you&#8217;re not arriving to tear everything down, which matters especially after a difficult transition.<\/p>\n<\/div>\n<\/div>\n<div class=\"step\">\n<div class=\"num\">2<\/div>\n<div>\n<h4>Address the specific, named problem directly<\/h4>\n<p>Vague reassurances, &#8220;things will be different now&#8221;, carry no weight. If the core issue was inconsistent, unexplained decision-making, the fix is building visibly consistent, explained decision-making from your very first decisions onward, not simply asserting that you&#8217;re different.<\/p>\n<\/div>\n<\/div>\n<div class=\"step\">\n<div class=\"num\">3<\/div>\n<div>\n<h4>Rebuild trust through demonstrated consistency, not declared intent<\/h4>\n<p>Trust damaged by a predecessor doesn&#8217;t transfer to you automatically just because you&#8217;re new, and it also doesn&#8217;t automatically distrust you either. It has to be actively rebuilt through visible, consistent behaviour over weeks, not through a single reassuring speech in the first meeting.<\/p>\n<\/div>\n<\/div>\n<div class=\"worked\">\n<h4>Applied: rebuilding<\/h4>\n<p><span class=\"label\">What Omar actually did<\/span> He identified that the team&#8217;s technical processes were genuinely strong and said so directly and specifically in a team meeting, naming what was working and why he had no intention of changing it. For the trust issue, he introduced a simple, visible practice: any decision affecting workload or assignment distribution would be explained briefly to the team, in writing, with the reasoning behind it. This was a small, low-cost change, and it directly targeted the specific harm the team had actually experienced, rather than a generic trust-building gesture disconnected from what had gone wrong.<\/p>\n<\/div>\n<h2 class=\"section-h\">Step three: build your own relationship with the team going forward<\/h2>\n<div class=\"step\">\n<div class=\"num\">1<\/div>\n<div>\n<h4>Don&#8217;t try to replicate the previous manager, good or bad<\/h4>\n<p>Whether the predecessor was well-liked or the source of real problems, trying to copy or deliberately invert their style both keep you reacting to someone else&#8217;s leadership rather than establishing your own. Build your approach from what the team actually needs now, not from a contrast to what came before.<\/p>\n<\/div>\n<\/div>\n<div class=\"step\">\n<div class=\"num\">2<\/div>\n<div>\n<h4>Give the relationship genuine time<\/h4>\n<p>A team recovering from a difficult transition, in particular, often needs longer than a fresh team would to extend real trust. Expect a slower build, and don&#8217;t read early caution as a personal verdict on you specifically.<\/p>\n<\/div>\n<\/div>\n<div class=\"step\">\n<div class=\"num\">3<\/div>\n<div>\n<h4>Check in explicitly on whether the original problem has actually improved<\/h4>\n<p>Don&#8217;t assume your fix worked because you can&#8217;t see ongoing complaints. Ask directly: has this actually gotten better from where you sit? Silence isn&#8217;t the same as resolution, particularly with a team that has already learned raising issues didn&#8217;t used to change anything.<\/p>\n<\/div>\n<\/div>\n<h2 class=\"section-h\">Common failure patterns when inheriting a team<\/h2>\n<div class=\"fail-box\"><strong>Assuming a difficult predecessor means everything needs to change.<\/strong> Often specific things went wrong, not everything, and wholesale change creates unnecessary disruption on top of an already unsettled team.<\/div>\n<div class=\"fail-box\"><strong>Assuming a well-liked predecessor means nothing needs to change.<\/strong> Even good managers leave gaps, and a team&#8217;s fondness for a previous leader doesn&#8217;t mean every practice they ran was sound.<\/div>\n<div class=\"fail-box\"><strong>Moving too fast to prove yourself.<\/strong> Especially after a difficult transition, urgency reads as more of the same instability the team just went through, rather than as competence.<\/div>\n<div class=\"fail-box\"><strong>Taking early guardedness personally.<\/strong> A team&#8217;s caution is very often about their history, not a judgement on you specifically. Reacting defensively to it tends to confirm whatever wariness exists rather than ease it.<\/div>\n<div class=\"artifact\">\n<h4>A diagnostic sequence to work from<\/h4>\n<ul>\n<li>Gather context from multiple sources before forming a view on what actually happened<\/li>\n<li>Observe existing workflows and meetings before changing anything<\/li>\n<li>Hold individual listening conversations, focused on understanding, not evaluation<\/li>\n<li>Explicitly name what&#8217;s working and intend to keep it<\/li>\n<li>Address the specific, named problem directly rather than with a generic reassurance<\/li>\n<li>Rebuild trust through weeks of consistent, demonstrated behaviour, not a single speech<\/li>\n<\/ul>\n<\/div>\n<div class=\"related-wrap\">\n<h3>Related reading<\/h3>\n<div class=\"related-grid\">\n<a class=\"related-card\" href=\"\/en\/leadership-strategic-management-training-guide\/\"><strong>Leadership and Strategic Management Training: A Complete Guide<\/strong><span>Where inheriting a team fits into the wider leadership cluster<\/span><\/a><br \/>\n<a class=\"related-card\" href=\"\/en\/first-90-days-as-a-manager\/\"><strong>Your First 90 Days as a Manager<\/strong><span>The general new-manager sequence this guide adapts for an inherited team specifically<\/span><\/a>\n<\/div>\n<\/div>\n<div class=\"cta-wrap\">\n<h3>An Inherited Team Needs Diagnosis Before It Needs Direction<\/h3>\n<p>The Team Building and Team Development course is built around exactly this diagnostic skill: identifying what&#8217;s actually limiting a team before choosing an intervention.<\/p>\n<div class=\"cta-links\">\n<a href=\"\/en\/course\/team-building-and-team-development-course\/\">Team Building and Team Development<\/a><br \/>\n<a href=\"\/en\/course\/supervisory-skills-development-course\/\">Supervisory Skills Development<\/a>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Building a team and inheriting one are different skills. The diagnostic work that has to come first, worked through a team recovering from a difficult, abrupt departure.<\/p>\n","protected":false},"author":1,"featured_media":10917,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[404],"tags":[],"class_list":["post-9484","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-professional-development"],"_links":{"self":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9484","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/comments?post=9484"}],"version-history":[{"count":1,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9484\/revisions"}],"predecessor-version":[{"id":9509,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9484\/revisions\/9509"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/media\/10917"}],"wp:attachment":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/media?parent=9484"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/categories?post=9484"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/tags?post=9484"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}