Objective

Outline how an agile, multi-disciplinary team should operate to drive a specific growth objective, creating a blueprint for cross-functional collaboration.

Instructions

1. Choose a Growth Objective

Pick an important growth objective your company is focusing on.

Examples:

• "Improve free trial to paid conversion by 15%"
• "Launch and scale new product feature X to 10k users"
• "Increase average revenue per customer through upsells by 20%"
• "Reduce customer churn from 8% to 5%"
• "Expand into enterprise segment with 25 new enterprise deals"

Be specific with metrics and timeframe.

2. Assemble Team Roles

List 4-7 roles from different departments to include on the team.

Consider which functions impact this objective:

Example for "Improve trial-to-paid conversion":

• Product Manager: Coordinate and keep customer experience in mind
• Growth Marketer: Handle onboarding campaigns and messaging
• Product Marketing: Refine positioning and value communication
• Sales/SDR Rep: Provide direct customer feedback, conduct outreach to trial users
• Data Analyst: Crunch numbers on usage patterns and conversion drivers
• Engineer/Developer: Implement product improvements and in-app messaging
• Customer Success Rep: Share insights on what makes customers successful

For each role, write 1 sentence on why they're included.

3. Define Responsibilities (RACI)

For key activities needed to reach the objective, assign responsibilities using RACI:

• R = Responsible (does the work)
• A = Accountable (final decision maker)
• C = Consulted (provides input)
• I = Informed (kept in the loop)

Create a RACI matrix:

Activity	Product Mgr	Growth Marketer	Data Analyst	Engineer	Sales Rep
Strategy/Planning	A	R	C	C	C
User Research	R	C	R	I	C
Product Changes	C	I	I	R	I
Marketing Campaigns	C	R,A	I	I	C
Sales Outreach	I	C	I	I	R,A
Measurement	C	C	R,A	I	I

4. Outline Team Rituals

Describe how the team will operate on a weekly cadence.

Agile ceremony examples:

• Sprint length: 1 or 2 weeks
• Sprint Planning: Beginning of sprint, set goals and tasks (1 hour, all team members)
• Daily Stand-ups: Quick sync on progress and blockers (15 min, daily or 3x/week)
• Weekly Review: Mid-sprint check-in with stakeholders (30 min)
• Sprint Retrospective: End of sprint, discuss what worked and what to improve (45 min)

Communication channels:

• Slack channel: #growth-trial-conversion for real-time updates
• Project board: Jira or Trello with shared visibility
• Shared docs: Google Drive folder for research, briefs, results

Decision-making process:

• Small decisions: Team lead or accountable person decides
• Major decisions (budget, strategy pivot): Team consensus or escalate to exec sponsor

Example ritual schedule:

"Team operates in 2-week sprints. Sprint Planning every other Monday (1 hour, all members). Daily stand-ups at 9:30am with PM, Marketing, Engineer (others optional). Weekly stakeholder update on Fridays. End-of-sprint Retrospective every other Friday afternoon."

5. Shared Goals and Metrics

State 2-3 key metrics the team will track together.

Requirements:

• Tie directly to growth objective
• All team members influence them
• Measurable and trackable

Example for trial-to-paid conversion:

Primary Metric:

• Trial-to-paid conversion rate: Increase from 12% to 18% in 8 weeks

Supporting Metrics:

• Trial user activation rate (completed 3+ key actions): 60% → 80%
• Trial engagement score (composite of logins, feature usage): +25%
• Sales-assisted conversion rate: 20% → 30%

OKR format:

Objective: Dramatically improve trial user conversion to drive revenue growth

Key Results:

• KR1: Increase trial-to-paid conversion rate from 12% to 18%
• KR2: Achieve 80% activation rate (users completing 3+ key actions)
• KR3: Generate $250k MRR from trial conversions this quarter

Write a brief note on how each role contributes:

• Growth Marketer: Onboarding email sequences and in-app messaging to drive activation
• Product Manager: Prioritize product improvements that reduce friction
• Engineer: Implement improvements and instrumentation for measurement
• Data Analyst: Track metrics, run experiments, identify drop-off points
• Sales Rep: High-touch outreach to high-intent trial users

6. Communication & Documentation Plan

Define how the team keeps others informed and documents work.

Internal communication:

• Weekly email update to exec team on progress vs. OKRs
• Bi-weekly demo of improvements to broader company
• Monthly all-hands presentation on learnings

Documentation:

• Experiment log (what we tested, results, learnings)
• Shared dashboard (real-time metrics)
• Sprint retrospective notes
• Decision log (major decisions made and rationale)

Transparency:

• Dashboard accessible company-wide
• Slack channel open to all (not private)
• Monthly AMA (Ask Me Anything) session for other teams

7. Define Team Governance

Team Lead:

Who is accountable for overall team performance?

Example: "Product Manager serves as Team Lead, coordinates across functions and reports to VP Product."

Executive Sponsor:

Who removes blockers and provides air cover?

Example: "VP Product is executive sponsor, attends key milestone reviews."

Team Duration:

Is this permanent or temporary?

Example: "Team operates for Q2 and Q3 (6 months), then reassess based on results."

Escalation path:

How are conflicts or blockers resolved?

Example: "Team attempts consensus first. If deadlocked, Team Lead makes call. Major issues escalated to Executive Sponsor."

8. Sketch Team Framework

Synthesize everything into a concise Team Charter (1-2 pages).

Template:

---

GROWTH TEAM CHARTER

Team Name: Trial Conversion Squad

Mission: Improve trial-to-paid conversion by 15% to accelerate revenue growth

Duration: Q2-Q3 2025 (6 months)

Team Members:

• Sarah Chen (Product Manager) – Team Lead
• Marcus Johnson (Growth Marketer)
• Priya Patel (Data Analyst)
• Alex Kim (Frontend Engineer)
• Jordan Lee (SDR/Sales Rep)

Objective & Key Results:

• Objective: Dramatically improve trial user conversion
• KR1: Trial-to-paid rate 12% → 18%
• KR2: Activation rate 60% → 80%
• KR3: $250k MRR from conversions

Working Method:

• 2-week sprints
• Daily 15-min stand-ups (9:30am)
• Bi-weekly sprint planning and retrospectives
• Shared Slack: #trial-conversion-squad
• Shared board: Jira "Trial Conversion" project

Accountability:

• Team success measured on shared OKRs
• Individual performance reviews consider team contribution
• Team Lead (Sarah) reports weekly to VP Product

Communication:

• Weekly update email to exec team
• Real-time dashboard accessible company-wide
• Monthly demo to broader company

Executive Sponsor: VP Product (removes blockers, secures resources)

Decision Rights:

• Team can make tactical decisions (test ideas, messaging changes)
• Major changes (budget >$10k, product roadmap shifts) require sponsor approval

---

Deliverable

Create a Cross-Functional Team Charter (1-2 pages) including:

1. Team name, mission, and duration
2. Team members and their roles
3. OKRs and shared metrics
4. Working method (rituals, cadence)
5. Communication and documentation plan
6. Governance (team lead, executive sponsor, decision rights)
7. RACI matrix for key activities

Outcome

You'll have a complete blueprint for an agile, cross-functional growth team including:

• Clear roles and accountability
• Defined collaboration practices
• Shared goals everyone works toward
• Governance structure for decisions and escalations

This charter can be presented to leadership as a proposal for a new working model. Even if you can't immediately form the exact team, you can start implementing elements (shared metrics, weekly syncs) as a first step.

You'll have learned to design cross-functional teams deliberately, with frameworks that ensure clarity, alignment, and accountability – key skills for modern growth leaders.