Case Study: How a 150-Person Team Rolled Out Coaching in 90 Days
Real results, real mistakes, and what they learned
Note: This case study is based on a real implementation. Company name and some identifying details have been changed to protect confidentiality.
Most case studies are marketing fiction—smooth rollouts, perfect adoption, executives who sound like they're reading from a script.
This one is messier and more useful. A mid-sized company tried to fix their manager coaching problem in 90 days. Some things worked immediately. Others failed until they figured out why.
Here's what actually happened.
The situation
Company: TechFlow (anonymized), a B2B SaaS company, 150 employees, 18 managers
The problem they were solving:
- 1:1s happened sporadically (some managers weekly, some monthly, some "when we have time")
- No consistent structure—meetings felt like status updates
- Feedback was rare and vague
- New managers especially struggled without frameworks
- HR couldn't measure coaching quality or prove impact
Why they chose to do this:
- New CEO wanted "coaching culture" as competitive advantage
- Attrition was ticking up (14% annually)
- Employee engagement survey showed "relationship with manager" as lowest score
- Three months until board meeting where they needed to show progress
Constraints:
- Limited budget ($25k for year one)
- No dedicated People Ops team (one HR generalist)
- Distributed team across 4 timezones
- Had already tried performance management software that nobody used
The 90-day timeline (Focus → Connect → Engage)
Weeks 1-2: Focus—Define success and baseline
What they did:
- Picked 3 pilot teams (25 people, 4 managers)
- Defined success metrics:
- 80% of managers use 1:1 templates weekly
- Average 2 feedback moments per person per month
- 1:1s with clear outcomes and next steps (measured by template completion)
- Ran baseline survey: "How useful are your 1:1s?" (avg score: 5.2/10)
- Set up Ren with Slack integration and SSO
Time investment: 8 hours total (2 hours from CEO, 6 hours from HR)
What almost went wrong: CEO wanted to pilot with "high-performing managers" to show success. HR pushed back—pilot with managers who need help most. They compromised: 2 struggling managers, 2 strong ones.
Weeks 3-4: Focus—Launch 1:1 templates
What they shipped:
- "Focus: Goal Clarity" template for Q1 kickoff
- 15-minute manager training video (not a 2-hour webinar)
- Slack channel for manager questions
- Nudges 24 hours before scheduled 1:1s
Adoption rate: Week 3: 45% of managers used template. Week 4: 75%.
What worked:
- CEO ran his 1:1s publicly using the template and shared screenshots
- Templates took 5 minutes to complete, not 30
- Slack nudges arrived at the right time (eliminated "I forgot" excuse)
What didn't work:
- First template version had too many fields—managers skipped sections
- No clear "done" state—people didn't know if they completed it correctly
- Two managers thought this was "performance management theater" and resisted
Fix: Simplified template to 5 core questions. Added example of completed template. CEO had direct conversation with resistant managers: "Try it for 3 weeks. If it's not useful, we'll kill it."
Weeks 5-6: Connect—Add feedback mechanics
What they shipped:
- "10-second feedback" Slack buttons
- Weekly manager prompt: "Who did great work this week?"
- Peer recognition channel where anyone could post kudos
Adoption rate:
- Week 5: Average 0.8 feedback moments per person
- Week 6: Average 1.4 feedback moments per person
What worked:
- 10-second feedback was genuinely quick (people used it)
- Public recognition channel created social proof
- Managers who gave feedback got feedback back (reciprocity effect)
What didn't work:
- Some feedback was too vague: "Great job on the project!"
- People waited until Friday to do feedback (instead of in-the-moment)
- Two employees worried feedback was being tracked for performance reviews
Fix:
- Shared examples of specific vs vague feedback
- Changed nudge from "weekly" to "when you see good work"
- HR published explicit statement: "Feedback data shows patterns, not individuals. It's not used for performance ratings."
Weeks 7-8: Engage—Add accountability rituals
What they shipped:
- "Engage: Accountability" template for commitments and next steps
- Automated follow-up 7 days after 1:1: "Did [commitment] happen?"
- Manager dashboard showing completion rates
Adoption rate:
- 68% of 1:1s included explicit commitments
- 52% of commitments marked complete within 7 days
What worked:
- Automated follow-up removed "I forgot" excuse
- Dashboard made accountability visible (managers are competitive)
- Template forced specific commitments ("I'll try harder" → "I'll ship proposal by Friday")
What didn't work:
- Some commitments were too ambitious (people set 5 things, completed 1)
- Follow-up felt like nagging to some employees
- Managers weren't sure what to do when commitments weren't completed
Fix:
- Coached managers to push for one commitment, not five
- Changed follow-up tone: "Did this happen? If not, what got in the way?"
- Added template for "reset conversation" when commitment fails
Weeks 9-10: Measure and iterate
What they analyzed:
- Usage data (who's using what, when)
- 1:1 quality indicators (agenda completeness, outcomes documented)
- Feedback velocity (moments per person per month)
- Anecdotal feedback from managers and employees
Manager feedback session highlights:
- "This makes 1:1s feel less awkward."
- "I thought this would take longer—it doesn't."
- "The templates help me not forget important conversations."
- "I wish we'd had this when I first became a manager."
- "Some of my team finds the Slack nudges annoying."
What they tweaked:
- Reduced nudge frequency for two managers whose teams complained
- Added "skip this week" button for 1:1 prep
- Created manager meeting ritual: share one win from using templates
What they kept:
- Core templates (Focus, Connect, Engage)
- 10-second feedback buttons
- Weekly manager summary
Weeks 11-12: Prove outcomes and plan scale
What they presented to CEO and board:
| Metric | Baseline | After 90 days | Change |
|---|---|---|---|
| Managers using templates weekly | 0% | 78% | +78pp |
| Feedback moments per person/month | 0.3 | 2.1 | +600% |
| 1:1s with documented outcomes | ~20% | 71% | +51pp |
| Employee "useful 1:1" rating (1-10) | 5.2 | 7.4 | +2.2 |
| Manager confidence in coaching | 4.8/10 | 7.1/10 | +2.3 |
Qualitative wins:
- Two employees explicitly mentioned better 1:1s in retention conversations
- New manager onboarding now includes templates (not just "figure it out")
- Three managers who were skeptical became advocates
- CEO could point to specific behavior changes in board presentation
What they decided: Scale to all 18 managers immediately. Budget approved for full year.
Artifacts they created (and you can steal)
1:1 agenda template (Final version)
**Focus area this week:**
[One sentence: What outcome matters most?]
**Wins since last check-in:**
[What went well?]
**Current blockers:**
[What's in the way?]
**One commitment:**
[What will you deliver by next week?]
**Support needed from me:**
[What can I unblock or provide?]
10-second feedback examples
- "When you caught that bug before it hit production, you saved us 2 days of customer issues. Thank you."
- "Your presentation simplified a complex idea—I understood it immediately."
- "You stayed late to help Sarah debug. That's the team culture we want."
Manager meeting agenda (monthly)
1. Template usage and patterns (5 min)
2. Share one coaching win (10 min, round-robin)
3. Discuss one challenging scenario (10 min)
4. What to start/stop/continue (5 min)
What actually moved the needle (lessons learned)
What worked
1. Rituals beat tools Embedding templates in manager meetings made them real. Announcing the tool in Slack and hoping people used it would have failed.
2. CEO modeling behavior When the CEO publicly used templates and shared screenshots, skeptical managers got on board. "Do as I say" doesn't work. "Do what I do" does.
3. Short prompts > long forms Every time they simplified a template, adoption went up. Managers don't want comprehensive frameworks—they want "what do I do right now?"
4. In-workflow delivery Slack nudges meant managers didn't have to remember to open another app. Friction kills adoption faster than bad features.
5. Visible early wins Sharing specific examples ("Sarah gave me the best feedback I've gotten all year") created momentum. Abstract benefits don't motivate—concrete stories do.
What didn't work (at first)
1. Too many fields in templates First version had 12 questions. Managers skipped half. Final version had 5. Completion rate doubled.
2. Not addressing resistance directly Two managers thought this was "corporate BS" and ignored it. Hoping they'd come around didn't work. CEO having a direct conversation did.
3. Assuming privacy was obvious Until HR explicitly published what data was tracked and how it was used, some employees worried this was surveillance. Transparency upfront would have avoided that.
4. Weekly cadence for everything Not all prompts need to be weekly. Some should be in-the-moment (feedback), some weekly (1:1 prep), some monthly (goal check-ins).
5. No "reset" template When commitments didn't happen, managers didn't know what to say. They needed a template for "what got in the way and what do we do now?"
What surprised them most
From the CEO: "I expected resistance from managers. I got the most pushback from high performers who didn't think they needed structure. Turns out everyone benefits from templates—even the strong coaches."
From HR: "I thought we'd spend time convincing people to use it. Instead, we spent time helping managers handle what came up because they were coaching more. Better problems."
From managers: "I thought templates would make conversations robotic. They actually made them more human—I wasn't scrambling for what to talk about, so I could focus on listening."
From employees: "I was skeptical about 'AI coaching.' Turns out it's just good structure delivered at the right time. My 1:1s are actually useful now."
What they'd do differently
Start with one template, not three. Focus → Connect → Engage was the right sequence, but they could have spaced it out more.
Pilot with struggling managers only. High performers joined later anyway. Starting with people who needed help most would have created better testimonials.
Publish privacy and data policy on day one. Waiting until week 3 to explain this created unnecessary anxiety.
Make "skip this week" obvious earlier. Some weeks, 1:1s should be skipped. Making that explicit reduced guilt.
Create the "reset conversation" template immediately. Accountability requires knowing what to do when things don't go as planned.
Next steps for TechFlow
Month 4-6:
- Scale to all managers (done in month 4)
- Add "Strategic Coaching" template for senior ICs
- Create manager certification program using templates
- Integrate with performance review cycle
Month 7-12:
- Expand to peer coaching (not just manager-to-report)
- Add goal alignment features
- Pilot "Async 1:1 Lite" for international teams
- Quarterly business review: tie coaching behaviors to retention and engagement
Year 2:
- Make this "how we manage people here"
- Include in new manager onboarding
- Build internal coach network
- Measure impact on business outcomes (not just behavior)
FAQ
What made adoption stick after the pilot?
Three things: (1) CEO continued modeling usage publicly, (2) they embedded templates in existing meetings instead of creating new rituals, (3) they shared specific wins weekly so people saw concrete value.
What surprised managers most about the process?
That templates made conversations more human, not less. Managers expected scripted, robotic 1:1s. Instead, having structure freed them to actually listen instead of scrambling for what to talk about.
How did you measure results with such a small pilot?
Usage data (completion rates, frequency), quality indicators (agenda completeness), and short pulse surveys. You don't need sophisticated analytics for 25 people—you need direct feedback and visible behavior change.
What if someone on our team is resistant like TechFlow's managers were?
Name it directly. The CEO told resistant managers: "Try this for 3 weeks. If it's not useful, we'll kill it." That's better than hoping they come around or forcing compliance. Give them an off-ramp and let the tool prove itself.
How much time did this actually take?
- CEO time: 2 hours setup, 30 min/week (modeling and manager check-ins) = ~8 hours total over 90 days
- HR time: 6 hours setup, 1 hour/week (monitoring and iteration) = ~18 hours total
- Manager time: 15 min/week per manager = ~15 hours per manager over 90 days
Total organizational time: ~350 person-hours over 90 days for 25 people (14 hours per person). Most of that was doing coaching, not administering tools.
Try this with your team
See what happens when you give managers structure, prompts, and accountability for coaching. Start with 2-3 teams, measure for 30 days, decide whether to scale.
Start a pilot with Ren | See implementation guide | Read our methodology
Last updated: January 2026
Related reading: