Manage Team Growth & Scaling

As your team grows from 5 people to 50+, your approach to career development needs to scale. Here's how to use Mentora to maintain quality development conversations at scale.

---

At 5–10 People

One-on-ones: Weekly or bi-weekly, 30 minutes

In Mentora:

• Create detailed roadmaps for each person
• Use comments for regular feedback
• Track progress weekly

Frequency: Manage everything yourself

---

At 10–25 People

One-on-ones: Every 2 weeks, 30 minutes (still manageable)

In Mentora:

• Create roadmaps for everyone
• Use the Team Page to spot people at risk
• Delegate some feedback to senior team members

New approach:

• Establish a standard roadmap template (e.g., 3 goals per year)
• Use the Import feature for bulk goal creation
• Have senior people mentor juniors — create "mentorship" goals

---

At 25–50 People

One-on-ones: Monthly check-ins, 30 minutes (focus on major milestones)

In Mentora:

• Use templates and bulk import heavily
• Focus on milestone-level conversations (not every task)
• Encourage peer feedback in comments

New structure:

• Divide team into sub-groups with senior leads
• Each lead owns 5–8 people's development
• Create a career development committee (quarterly reviews)

Example: "Frontend team (Sarah leads) → 3 people with clear frontend goals Backend team (James leads) → 4 people with clear backend goals Product team (Alex leads) → 5 people with product goals"

---

At 50+ People

One-on-ones: Quarterly check-ins, 30 minutes (status-focused)

In Mentora:

• Automate everything possible (templates, bulk import)
• Focus on outcomes, not processes
• Use dashboards for aggregate insights

New structure:

• Create a dedicated people/HR team
• Establish career development working group
• Run quarterly "all-hands career development" sessions
• Use exports for reporting to leadership

---

Scaling Best Practices

Standardize Roadmaps

Create templates for common roles:

• "Software Engineer Year 1" — 3 specific goals
• "Software Engineer → Staff" — 3-year progression
• "IC → Manager" — 2-year transition

This reduces the cognitive load of creating custom roadmaps.

Automate with Import/Export

• Import goals in bulk once per quarter
• Export progress monthly for dashboards
• Use exports to identify patterns (who's struggling? who's advancing fast?)

Delegate Development Ownership

Don't manage everyone yourself. Instead:

• Senior engineers mentor juniors (create "mentorship" goals for both)
• Team leads own their direct reports' development
• Create cross-functional development buddies

Keep Communication Visible

• Use comments for all feedback (not Slack)
• Make Audit Log part of your culture
• Celebrate progress publicly in comments

Focus on Milestones, Not Tasks

At scale, task-level tracking becomes noise. Focus on:

• Is the person making progress? (checkpoints via milestones)
• Are they on track? (status updates quarterly)
• Do they need support? (spot check at-risk items)

---

Scaling Challenges

Challenge: You can't keep up with everyone's progress

Solution:

• Delegate to team leads
• Use the Team Page to spot-check (monthly instead of weekly)
• Create a development committee that meets quarterly to discuss progress

Challenge: People feel less connected as the team grows

Solution:

• Keep monthly 1:1s (even if shorter)
• Use comments to give consistent feedback
• Run quarterly all-hands development sessions

Challenge: Goals become generic as you scale

Solution:

• Keep the template structure but allow customization
• Make team leads own the roadmap quality for their people
• Run a "goals review" where peers give each other feedback

---

Tips

• Start scaling early — Don't wait until you're drowning. By 20 people, move to monthly 1:1s and delegate
• Invest in leads and managers — The success of scaled development depends on your team leads understanding how to mentor
• Automate the busywork — Use import/export/templates to free up time for real mentorship
• Keep the culture alive — Even at 100 people, celebrate milestones and progress

---

Troubleshooting

I'm overwhelmed managing everyone's development

You're not alone. This means it's time to delegate to team leads. Have each lead own their direct reports' roadmaps.

People feel less seen at scale

Move to monthly instead of weekly 1:1s, but keep them. Use comments to give consistent feedback between meetings.

Goals feel generic and unmotivating

Go back and personalize. Have team leads add individual flavor to standard templates. A generic goal plus a personal conversation becomes motivating.