How the team itself becomes a system.
Grow is the function nobody owns and everyone needs. It's the difference between a team that scales and a team that just gets bigger. Workforce planning, capacity, hiring rubrics, career paths.
v 02 · live
What Grow means.
Grow is the work of turning a team into a system that scales. Not the work of headcount planning. Not the work of writing job descriptions. The work of designing how capacity, hiring, career paths, and team structure evolve as the operation grows, so that growth doesn't break what was working.
Most CX teams grow by reacting. A spike in volume; we hire. A senior leaves; we backfill. A new market opens; we cobble together a pod. Workforce planning is a quarterly Excel exercise. Career paths are a wishlist on a Notion page. Hiring rubrics live in the lead's head.
That's the gap Grow names. Growth is the most expensive thing a CX team does, and the least designed. New hires arrive into structure that doesn't match the size of the team. Senior agents plateau because there's no path. Capacity planning is a fight with finance every quarter.
"We grew from 12 agents to 47 in 18 months. Nobody designed for that. We just kept adding pods. By the end I had three layers of hierarchy nobody had thought through, career paths I'd promised but couldn't deliver, and a workforce model I'd built in Excel at midnight. Growth was the hardest thing we did, and it was the least operational."
Haven's Grow module starts with naming an owner. Workforce planning, hiring rubrics, career paths, capacity model: all assigned. Then it builds the artifacts: a workforce model that responds to demand, hiring rubrics that calibrate to the rubric you already have, career paths that match the seven functions.
Growth becomes a designed event, not a reaction. The team scales as a system. The thing that breaks last is the thing nobody owned first.
The progression. Four levels.
Growth happens to you. Volume spikes trigger hiring. Senior departures trigger backfills. Workforce planning is a quarterly Excel exercise. Career paths are aspirational.
- Reactive hiring
- No workforce model
- Excel-based planning
- Aspirational career paths
Some pieces are owned. Hiring has a rubric. Capacity has a model. Career paths exist on paper. Nobody owns Grow as a function. It's split across leadership, ops, and HR.
- Hiring rubric exists
- Capacity model in spreadsheet
- Career paths on paper
- No named owner
Grow has an owner. Workforce model responds to demand. Hiring rubrics calibrate to the operation's bar. Career paths map to the seven functions. Growth is a designed event.
- Named owner
- Demand-responsive model
- Calibrated rubrics
- Function-mapped career paths
The team is a self-scaling system. Capacity flexes with demand. Hiring is continuous, not reactive. Career paths produce internal seniors. The team grows as a designed organism.
- Flexing capacity
- Continuous hiring pipeline
- Internal senior production
- Designed team organism
What Grow builds.
The workforce model
A demand-responsive capacity model that shows the team you'll need in three months, six months, twelve months. Hiring becomes proactive.
- 3-, 6-, 12-month capacity forecast
- Demand inputs from product & ops
- Hiring cadence & lead time built in
- Linked to onboarding ladder
The hiring rubric
Calibrated to the bar your operation already holds. Interview scorecards mapped to the competency tiers in Enable. Hiring quality compounds.
- Calibrated to your existing bar
- Scorecards mapped to Enable tiers
- Same dimensions across interviewers
- Quarterly recalibration
The career ladder
Career paths that map to the seven functions of CX operations. Senior agents have somewhere to go. Promotion criteria are operational, not political.
- Paths mapped to the seven functions
- Operational, not political, criteria
- Senior agents have somewhere to go
- Linked to Perform & Enable