Rise of Tribes

Case study: From overwhelmed manager to high-impact leader — how AI training transformed coaching and 1:1s

When Sam (name changed) stepped into his first manager role at a mid‑stage product company, despite his role change, he continued to be hands-on with coding, 1:1s were irregular and mostly status updates, frequent ad‑hoc meetings, etc. Within three months, delivery slowed and team morale dipped. The root cause wasn’t technical ability; it was scale. Sam was not given the right support on how to move away from an Individual contributor to a Manager, there was a lack of established practices and AI skills to make coaching efficient, run focused 1:1s, and reduce coordination overhead.

Problem: Weak coaching cadence and noisy 1:1s

• One‑on‑ones were consumed by status updates rather than development conversations.
• Coaching didn’t scale; direct reports asked the same questions repeatedly.
• Sam spent evenings drafting meeting notes and follow-ups, spent too much time coding himself, limiting his bandwidth towards strategic focus.

Intervention: role‑specific AI training and redesigned 1:1 rituals
Over two weeks Sam completed targeted training: prompt design for coaching, AI tools for meeting prep and follow‑up, and structuring repeatable learning paths. The program combined short demos, paired practice with an AI coach, and three focused pilots:

• 1:1 prep prompts: automated pre‑meeting summaries that pulled recent tickets, PRs, and prioritized discussion topics from brief employee inputs.
• Coaching micro‑plans: AI‑generated, 2‑week skill micro‑tasks tailored to each report (example: refactoring mini‑exercise, focused code kata*).
• Follow‑up automation: AI-created concise action items and a 2‑line accountability note sent to the report after each 1:1.

Outcome: measurable gains in 8 weeks

• 1:1 prep time dropped by 50% because summaries and context were auto‑generated, allowing meetings to start on development topics immediately.
• Direct reports completed coaching micro‑tasks at a 70% completion rate (tracked via short checklist in the team board), and progress showed in shorter PR cycles.
• Repeated questions fell by 40%, measured as a reduction in repeated help requests logged in the team’s support channel.
• Sam reclaimed two afternoons per week for stakeholder work and strategic planning.

Why it worked

• Coaching-first integration: AI supported coaching workflows rather than replacing human judgment, enabling higher‑quality, focused 1:1s.
• Lightweight metrics: completion rate of micro-tasks and reduction in repeated help requests provided clear, operational measurements of impact.
• Small, safe pilots: incremental experiments, built trust and normalised new rituals.

Practical takeaway

Start by automating 1:1 prep and follow-up with simple prompts, pair those with 2‑week coaching micro‑tasks, and track micro‑task completion plus help‑request volume. Those two metrics will show whether coaching is scaling—and free the manager to do higher‑leverage work.

*code kata is a self-contained exercise in software development that emphasizes skill acquisition and the establishment of consistent coding routines rather than simply solving a problem. The term “kata” originates from Japanese martial arts, where it refers to a choreographed sequence of movements practiced repeatedly to achieve mastery