# Delegation Plan: Improve Onboarding Activation

## 1. Overview

- **Task:** Improve onboarding activation rates for our product
- **Delegate:** Product Manager (PM)
- **Timeline:** 6 weeks
- **Delegated by:** [Your Name / Title]
- **Date created:** 2026-03-17

---

## 2. Objective

Increase the percentage of new users who complete the onboarding flow and reach a defined activation milestone (e.g., completing their first key action in the product). The PM will own the end-to-end initiative—from diagnosis through solution delivery—and is expected to produce measurable improvements in onboarding activation by the end of the 6-week period.

---

## 3. Background & Context

Onboarding activation is a critical lever for growth. Users who do not activate during onboarding are significantly less likely to retain. Current activation rates and known friction points should be shared with the PM at kickoff, including:

- Current onboarding funnel metrics (sign-up to activation conversion rates)
- Existing qualitative feedback (support tickets, user interviews, NPS verbatims)
- Any prior experiments or initiatives related to onboarding
- Relevant business goals and how activation ties to company OKRs

---

## 4. Scope & Boundaries

### In Scope
- Auditing the current onboarding experience across all platforms
- Identifying drop-off points and diagnosing root causes
- Proposing and prioritizing improvement initiatives
- Designing, shipping, and measuring at least one onboarding improvement
- Coordinating with design, engineering, data, and marketing as needed

### Out of Scope
- Major pricing or packaging changes
- Fundamental changes to the core product value proposition
- Initiatives requiring more than 6 weeks of engineering effort
- Changes to post-onboarding retention flows (unless directly tied to activation)

---

## 5. Success Criteria

| Metric | Target |
|--------|--------|
| Onboarding completion rate | Increase by X% (to be baselined in Week 1) |
| Time-to-activation | Reduce by Y% from current average |
| Activation rate (new users reaching key milestone within 7 days) | Increase by Z% |
| At least 1 experiment shipped and measured | Yes/No |
| Stakeholder alignment on onboarding strategy | Documented and approved |

The PM should define specific numeric targets during Week 1 after baselining current performance.

---

## 6. Authority & Decision Rights

The PM has full authority to:
- Define the activation metric and success criteria (subject to approval in Week 1)
- Prioritize which onboarding improvements to pursue
- Make day-to-day decisions on design, copy, and flow changes
- Allocate up to [X] engineering points per sprint toward this initiative
- Schedule and run user research sessions

The PM should escalate:
- Any changes that affect other teams' roadmaps
- Requests for engineering resources beyond the allocated budget
- Decisions that could impact revenue or contractual obligations
- Significant changes to the product's core signup flow

---

## 7. Resources & Support

| Resource | Details |
|----------|---------|
| Engineering | [X] engineers allocated for [Y] sprints |
| Design | [Designer name] available for [Z] hours/week |
| Data/Analytics | Access to analytics dashboards; [Analyst name] for ad hoc queries |
| User Research | Budget for [N] user interviews or usability tests |
| Tools | Access to A/B testing platform, analytics suite, session replay tools |
| Budget | [Amount] for any third-party tools or incentives |

---

## 8. Six-Week Plan

### Week 1: Discovery & Baselining
- **Activities:**
  - Review existing onboarding funnel data and establish baseline metrics
  - Audit the current onboarding flow (all platforms, all user segments)
  - Review existing user feedback, support tickets, and churn surveys
  - Identify key drop-off points and form initial hypotheses
  - Conduct 3-5 user interviews or review session recordings
- **Deliverable:** Discovery summary document with baseline metrics, drop-off analysis, and initial hypotheses
- **Check-in:** End of Week 1 — 30-minute review with delegator

### Week 2: Diagnosis & Ideation
- **Activities:**
  - Deep-dive into top 3 drop-off points identified in Week 1
  - Run additional qualitative research if needed (usability tests, surveys)
  - Brainstorm solutions with design and engineering
  - Benchmark competitors' onboarding flows
  - Prioritize opportunities using an impact/effort framework
- **Deliverable:** Prioritized list of improvement opportunities with rationale
- **Check-in:** End of Week 2 — 30-minute review; align on which 1-2 improvements to pursue

### Week 3: Solution Design
- **Activities:**
  - Create detailed specs for the top-priority improvement(s)
  - Work with design on mockups/prototypes
  - Define experiment plan (A/B test structure, sample size, success criteria)
  - Align with engineering on implementation approach and timeline
  - Get stakeholder buy-in on the proposed changes
- **Deliverable:** Product spec with designs, experiment plan, and engineering estimates
- **Check-in:** Mid-week async update; end-of-week design review

### Week 4: Build & Prepare
- **Activities:**
  - Engineering builds the onboarding improvement(s)
  - QA and internal testing
  - Set up A/B test infrastructure and tracking
  - Prepare any supporting content (emails, tooltips, help docs)
  - Coordinate with marketing/growth if changes affect acquisition flows
- **Deliverable:** Feature complete, tested, and ready for launch
- **Check-in:** End of Week 4 — quick status update; go/no-go decision for launch

### Week 5: Launch & Monitor
- **Activities:**
  - Launch the experiment to a subset of new users
  - Monitor key metrics daily (activation rate, completion rate, error rates)
  - Triage any bugs or unexpected issues
  - Collect early qualitative feedback
  - Begin planning follow-up iterations based on early signals
- **Deliverable:** Launch confirmed; daily monitoring dashboard shared
- **Check-in:** Mid-week data review; end-of-week preliminary results

### Week 6: Analyze & Report
- **Activities:**
  - Analyze full experiment results with statistical rigor
  - Conduct post-launch user interviews (3-5) to gather qualitative feedback
  - Document learnings, both what worked and what didn't
  - Make ship/no-ship decision based on results
  - Create a roadmap for further onboarding improvements
  - Present results and recommendations to stakeholders
- **Deliverable:** Final report with results, learnings, and recommended next steps
- **Check-in:** End of Week 6 — final presentation and retrospective

---

## 9. Communication Plan

| Cadence | Format | Participants | Purpose |
|---------|--------|--------------|---------|
| Weekly (Fridays) | 30-min meeting | PM + Delegator | Progress review, blocker removal, course correction |
| Bi-weekly | Written update (email/Slack) | PM + Broader stakeholders | Status update on initiative progress |
| Ad hoc | Slack/DM | PM + Delegator | Escalations, quick questions, blockers |
| Week 1, Week 6 | Presentation | PM + Leadership | Kickoff alignment; final results and recommendations |

### Escalation Protocol
1. PM attempts to resolve independently
2. If blocked for more than 24 hours, raise via Slack with delegator
3. If cross-team conflict, delegator facilitates resolution
4. If scope change needed, formal discussion at next weekly check-in

---

## 10. Risk & Mitigation

| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| Insufficient engineering bandwidth | Medium | High | Pre-allocate resources; have a lightweight "no-code" backup plan |
| Baseline data is unreliable or incomplete | Medium | Medium | Validate data sources in Week 1; instrument additional tracking if needed |
| Experiment results are inconclusive | Medium | Medium | Ensure adequate sample size; plan for extending the test if needed |
| Scope creep beyond onboarding | High | Medium | Clear scope boundaries documented above; weekly check-ins to monitor |
| PM needs more domain context | Low | Medium | Provide access to relevant stakeholders and historical documents at kickoff |
| Cross-team dependencies cause delays | Medium | High | Identify dependencies early in Week 1; build buffer into the timeline |

---

## 11. Feedback & Growth Plan

This delegation is also a development opportunity for the PM. Key growth areas to focus on:

- **Data-driven decision-making:** Strengthening ability to diagnose problems using quantitative and qualitative data
- **Experimentation rigor:** Designing and running well-structured A/B tests
- **Cross-functional leadership:** Driving alignment across design, engineering, and marketing without direct authority
- **Stakeholder communication:** Presenting findings and recommendations to leadership

### Feedback Touchpoints
- **Week 2:** Informal feedback on discovery work and hypothesis quality
- **Week 4:** Mid-point feedback on project management, communication, and solution quality
- **Week 6:** Comprehensive feedback on end-to-end execution, results, and areas for growth

---

## 12. Handoff Checklist

Before starting, ensure the PM has:

- [ ] Access to analytics dashboards and data tools
- [ ] Access to session replay / user research tools
- [ ] Introduction to key stakeholders (engineering lead, designer, data analyst)
- [ ] Historical context documents shared (prior experiments, research, roadmap)
- [ ] Calendar invites for all check-ins scheduled
- [ ] Clear understanding of the activation metric definition
- [ ] This delegation plan reviewed and agreed upon

---

## 13. Post-Initiative Wrap-Up

At the end of 6 weeks, the PM should deliver:

1. **Results report** — Quantitative results of the experiment(s), including statistical significance
2. **Learnings document** — Key insights about user onboarding behavior and what drives activation
3. **Recommendations** — Prioritized list of next steps for continued onboarding improvement
4. **Retrospective** — What went well, what could be improved in the process
5. **Knowledge transfer** — Ensure all documentation, data, and context is accessible to the team going forward