6.1Case studies
The essentials in 30 seconds
- Taking post: clear direction + listening + rituals before changing everything.
- Performance + change: figures AND people — dashboard on one side, meaning and quick wins on the other.
- Reflex: facing a real situation, chain fundamentals in order: direction, autonomy, rituals, delegation, feedback.
Salim thread — conclusion: 1 year later
One year after Level 1, Salim manages 7 people instead of 4. NPS is tracked each Monday, a new ticket tool arrives, and two recruits join the team. The three cases below replay exactly what he did: taking an expanded team, driving performance during the tool change, and adapting it all to the reality of an SME in Algiers.
Each case follows Context → Steps → Result.
Case 1 — Taking over a team you do not know
Context: a manager is appointed head of an existing team, with varied profiles and set habits. He must quickly build trust and performance — without breaking what works.
Steps:
- Clarify your role (manager, not do-it-all expert) and give direction: shared SMART goals, explained (N0.3, N1.1).
- Assess each person's autonomy, task by task, and adapt your style (direct, coach, support, delegate) (N2.1).
- Set rituals: team check-in and one-to-ones to listen, align and detect weak signals (N1.5, N2.2).
- Grow trust and psychological safety; place the team in its dynamics (Tuckman) (N2.4).
- Delegate progressively and motivate through recognition and meaning, not only instructions (N1.2, N1.3, N3.1).
- Give continuous feedback (DESC) and run reviews with no surprise (N2.2).
Result: a takeover that builds link and clarity: a team that knows where it goes, feels heard and gains autonomy — trust before performance.
Case 2 — Driving performance and leading a tool change
Context: a manager in charge of a scope must improve economic performance while a new tool shakes up team habits.
Steps:
- Understand the environment (SWOT) and link team action to created value and the business model (N3.2, N3.3).
- Read figures (P&L, margins) and build a budget tracked by variances (N4.1, N4.2).
- Build a dashboard with few KPI but the right ones (result + driving) and decide actions (N4.3).
- For the tool change: give meaning, anticipate resistance, communicate early, target quick wins (N3.5).
- Support each person along the change curve with emotional intelligence and workload care (N5.3).
- Develop needed skills (training, developmental delegation) to anchor the new way (N4.5).
Result: performance driven by figures AND a change adopted because its meaning is understood — the human side handled as much as logistics.
Case 3 — Algerian SME variant: absorbing two recruits in peak activity
Context: Salim (12-person SME, customer service in Algiers) onboards two recruits in a peak period: rising tickets, Ramadan approaching, main channel = phone + WhatsApp.
Steps:
- Tightened direction on a single quarterly OKR ("raving fans") posted and explained to recruits from day 1 (N1.1).
- Buddying: each recruit shadows a senior for 2 weeks, with progressive delegation by observed autonomy (N1.2, N2.1).
- Lightened rituals during the peak: 15-min weekly check-in + dedicated WhatsApp channel for urgent questions (N1.5).
- Targeted recognition of seniors who train, to avoid "we are given more work" resentment (N1.3).
- Hot DESC feedback after first difficult calls, no review postponed "to later" (N2.2).
Result: recruits operational without collapsing average delay, and seniors recognized as relays — the peak absorbs onboarding instead of suffering it.
Ready-to-say script — opening your takeover (3 min)
"I am here to make you succeed, not to redo everything. This week, I will listen to each of you in one-to-one: what works, what sticks, what you expect from me. Then we will set together our quarterly direction. No big change before understanding how you work."
Say at the first team check-in, then hold: listen before deciding.
Copy-paste template — 30-60-90-day takeover plan
DAYS 1-30: LISTEN
- One-to-one with each (expectations, irritants, perceived autonomy)
- Observe existing rituals before changing them
- Set 1 simple shared direction with the team
DAYS 31-60: ADJUST
- Adapt my style to each person's autonomy
- Set weekly check-in + regular one-to-ones
- Delegate 1 developmental file per person
DAYS 61-90: ANCHOR
- Regular DESC feedback, review with no surprise
- 5-8 KPI dashboard tracked with the team
- Review: what works, what we stop, nextMicro-business (2-3 people)
No big plan: one listening lunch per person + 1 direction written on one page are enough.
Remote / hybrid
Double one-to-ones the first 30 days by video; write decisions, do not rely on informal.
Algerian SME
Account for seasonal peaks, real channels (phone, WhatsApp) and administrative delays in the 90-day plan.
Intercultural
Make your style explicit ("I will listen a lot at first") so reserve is not read as distance.
Key takeaways
- Takeover: listen and frame before changing.
- Performance + change: figures and people in parallel.
- Right order: direction, autonomy, rituals, delegation, feedback.
- Adapt each case to real size and context.
48h challenge — apply tomorrow
Take 1 real situation from your team and write its steps in 5 stages (direction → autonomy → ritual → delegation → feedback). Test the 1st stage this week.
- I can chain reflexes in the right order on a real case.
- I have a 30-60-90-day plan adaptable to my next takeover.
- I did the 48h challenge or scheduled its date.
Frequently asked questions
Which case to start with?
With the one closest to your current situation. Case 1 if you take a team, case 2 if you must turn performance around during a change.
Must the steps be followed in order?
The direction → listening → rituals → delegation → feedback order is a good default. But adapt pace: a team in crisis needs direction faster, a stable team bears more listening.
What if my context matches no case?
Use the 6.2 playbook (symptom → causes → actions) to diagnose, then come back here for chaining.
Nadia takes over a 6-person team she does not know. Where to start?