Initial commit
This commit is contained in:
Zhongwei Li
798
skills/technical-launch-planner/SKILL.md
Normal file
798
skills/technical-launch-planner/SKILL.md
Normal file
@@ -0,0 +1,798 @@
|
||||
---
|
||||
name: technical-launch-planner
|
||||
description: Plan and execute technical product launches for developer tools, APIs, and technical products. Use this skill when technical PMMs need to "plan a launch", "create a launch strategy", "coordinate a product release", or "prepare for GA/beta launch".
|
||||
---
|
||||
|
||||
# Technical Launch Planner
|
||||
|
||||
## Overview
|
||||
|
||||
Plan and execute successful launches for technical products, developer tools, APIs, SDKs, and platforms. This skill provides frameworks, checklists, and templates specifically designed for technical audiences and developer-focused products.
|
||||
|
||||
**Built for:**
|
||||
- Developer tools and platforms
|
||||
- APIs and SDKs
|
||||
- Technical infrastructure products
|
||||
- B2D (Business-to-Developer) products
|
||||
- SaaS with technical buyers
|
||||
|
||||
---
|
||||
|
||||
## Quick Start
|
||||
|
||||
### 1. Assess Your Launch Tier
|
||||
|
||||
Run the interactive assessment:
|
||||
|
||||
```bash
|
||||
scripts/assess_launch_tier.sh
|
||||
```
|
||||
|
||||
This determines if your launch is:
|
||||
- **Tier 1** (Major/GA) - New product, major version, significant expansion
|
||||
- **Tier 2** (Standard) - New features, integrations, regional expansion
|
||||
- **Tier 3** (Minor) - Updates, improvements, small features
|
||||
|
||||
### 2. Generate Launch Plan
|
||||
|
||||
Create your comprehensive launch plan:
|
||||
|
||||
```bash
|
||||
scripts/generate_launch_plan.sh
|
||||
```
|
||||
|
||||
Provides structured plan with:
|
||||
- Timeline and milestones
|
||||
- Stakeholder responsibilities
|
||||
- Developer enablement checklist
|
||||
- Go-to-market activities
|
||||
- Launch day playbook
|
||||
|
||||
### 3. Validate Readiness
|
||||
|
||||
Before launch, check readiness:
|
||||
|
||||
```bash
|
||||
scripts/validate_readiness.sh
|
||||
```
|
||||
|
||||
Validates:
|
||||
- Documentation completeness
|
||||
- Technical assets ready
|
||||
- Stakeholder alignment
|
||||
- Messaging finalized
|
||||
- Metrics instrumentation
|
||||
|
||||
---
|
||||
|
||||
## Core Launch Framework
|
||||
|
||||
### Launch Tiers
|
||||
|
||||
Different launches require different levels of investment:
|
||||
|
||||
| Tier | Type | Examples | Investment |
|
||||
|------|------|----------|------------|
|
||||
| **Tier 1** | Major | GA launch, new product, major version | Full GTM, events, PR |
|
||||
| **Tier 2** | Standard | New features, integrations, SDKs | Selective GTM, blog, docs |
|
||||
| **Tier 3** | Minor | Updates, improvements, patches | Changelog, in-app |
|
||||
|
||||
See `references/launch_tiers.md` for complete framework.
|
||||
|
||||
---
|
||||
|
||||
## Developer-Focused Launch Components
|
||||
|
||||
### 1. Developer Enablement
|
||||
|
||||
**Critical for technical launches:**
|
||||
|
||||
**Documentation:**
|
||||
- Getting started guide
|
||||
- API reference
|
||||
- Code samples
|
||||
- Integration guides
|
||||
- Migration guides (if applicable)
|
||||
|
||||
**Code Assets:**
|
||||
- SDKs/client libraries
|
||||
- Sample applications
|
||||
- Starter templates
|
||||
- Code snippets
|
||||
|
||||
**Developer Experience:**
|
||||
- Sandbox/playground environment
|
||||
- Interactive tutorials
|
||||
- API explorer
|
||||
- Debugging tools
|
||||
|
||||
See `references/developer_enablement.md` for complete checklist.
|
||||
|
||||
---
|
||||
|
||||
### 2. Technical Messaging
|
||||
|
||||
**Speak developer language:**
|
||||
|
||||
**Avoid:**
|
||||
- Marketing jargon
|
||||
- Vague benefits
|
||||
- Non-technical superlatives
|
||||
|
||||
**Include:**
|
||||
- Concrete technical details
|
||||
- Performance metrics
|
||||
- Code examples
|
||||
- Architecture diagrams
|
||||
- Integration patterns
|
||||
|
||||
See `references/launch_messaging.md` for templates.
|
||||
|
||||
---
|
||||
|
||||
### 3. Launch Channels for Developers
|
||||
|
||||
**Where developers discover new tools:**
|
||||
|
||||
**Primary:**
|
||||
- Developer documentation
|
||||
- GitHub/GitLab
|
||||
- Developer blog
|
||||
- API changelog
|
||||
- Release notes
|
||||
|
||||
**Secondary:**
|
||||
- Dev.to, Hacker News, Reddit
|
||||
- Technical Twitter/X
|
||||
- Discord/Slack communities
|
||||
- YouTube (tutorials)
|
||||
- Developer newsletters
|
||||
|
||||
**Tertiary:**
|
||||
- Webinars/workshops
|
||||
- Conferences
|
||||
- Podcasts
|
||||
- Case studies
|
||||
|
||||
---
|
||||
|
||||
## Launch Planning Workflow
|
||||
|
||||
### Phase 1: Planning (T-12 to T-8 weeks)
|
||||
|
||||
**Objectives:**
|
||||
- Define launch tier
|
||||
- Set success criteria
|
||||
- Align stakeholders
|
||||
- Create timeline
|
||||
|
||||
**Activities:**
|
||||
1. **Launch Tier Assessment**
|
||||
```bash
|
||||
scripts/assess_launch_tier.sh
|
||||
```
|
||||
|
||||
2. **Stakeholder Kickoff**
|
||||
- Product/Engineering
|
||||
- Developer Relations
|
||||
- Sales Engineering
|
||||
- Marketing/Comms
|
||||
- Partners (if applicable)
|
||||
|
||||
3. **Define Success Metrics**
|
||||
- Developer adoption metrics
|
||||
- API usage/calls
|
||||
- SDK downloads
|
||||
- Documentation traffic
|
||||
- Community engagement
|
||||
|
||||
4. **Create Launch Timeline**
|
||||
```bash
|
||||
scripts/generate_launch_plan.sh
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Phase 2: Build (T-8 to T-4 weeks)
|
||||
|
||||
**Objectives:**
|
||||
- Create all launch assets
|
||||
- Prepare documentation
|
||||
- Build demos and samples
|
||||
|
||||
**Activities:**
|
||||
|
||||
**Documentation:**
|
||||
- [ ] Getting started guide written
|
||||
- [ ] API reference complete
|
||||
- [ ] Integration guides ready
|
||||
- [ ] Migration guide (if needed)
|
||||
- [ ] Troubleshooting FAQ
|
||||
|
||||
**Code Assets:**
|
||||
- [ ] SDKs built and tested
|
||||
- [ ] Sample apps created
|
||||
- [ ] Code snippets prepared
|
||||
- [ ] Sandbox environment ready
|
||||
|
||||
**Marketing Assets:**
|
||||
- [ ] Technical blog post written
|
||||
- [ ] Demo video recorded
|
||||
- [ ] Announcement email drafted
|
||||
- [ ] Social media plan
|
||||
- [ ] Press release (Tier 1)
|
||||
|
||||
**Sales Enablement:**
|
||||
- [ ] Technical battlecard
|
||||
- [ ] Demo script
|
||||
- [ ] FAQ/objection handling
|
||||
- [ ] Pricing materials
|
||||
- [ ] Competitive positioning
|
||||
|
||||
---
|
||||
|
||||
### Phase 3: Prepare (T-4 to T-1 weeks)
|
||||
|
||||
**Objectives:**
|
||||
- Review and refine all assets
|
||||
- Train teams
|
||||
- Pre-launch validation
|
||||
|
||||
**Activities:**
|
||||
|
||||
**Internal Enablement:**
|
||||
- [ ] Sales team training
|
||||
- [ ] Support team training
|
||||
- [ ] Partner briefings
|
||||
- [ ] Internal demo day
|
||||
|
||||
**External Prep:**
|
||||
- [ ] Beta customers briefed
|
||||
- [ ] Partners coordinated
|
||||
- [ ] Developer advocates prepared
|
||||
- [ ] Community moderators ready
|
||||
|
||||
**Technical Validation:**
|
||||
```bash
|
||||
scripts/validate_readiness.sh
|
||||
```
|
||||
|
||||
**Pre-Launch Checklist:**
|
||||
- [ ] All docs published to staging
|
||||
- [ ] SDKs tagged and ready
|
||||
- [ ] Demo environment tested
|
||||
- [ ] Monitoring/analytics configured
|
||||
- [ ] Support escalation path defined
|
||||
|
||||
---
|
||||
|
||||
### Phase 4: Launch (Launch Day)
|
||||
|
||||
**Launch Day Playbook:**
|
||||
|
||||
**Morning (9 AM):**
|
||||
- [ ] Publish documentation
|
||||
- [ ] Release SDKs/packages
|
||||
- [ ] Deploy blog post
|
||||
- [ ] Send announcement email
|
||||
- [ ] Post to social media
|
||||
- [ ] Update website/product pages
|
||||
|
||||
**Midday (12 PM):**
|
||||
- [ ] Monitor metrics dashboard
|
||||
- [ ] Respond to community questions
|
||||
- [ ] Share to external communities
|
||||
- [ ] Engage with social mentions
|
||||
|
||||
**Afternoon (3 PM):**
|
||||
- [ ] Post to Hacker News/Reddit (if Tier 1)
|
||||
- [ ] Developer advocate content
|
||||
- [ ] Partner announcements
|
||||
|
||||
**End of Day:**
|
||||
- [ ] Day 1 metrics report
|
||||
- [ ] Team debrief
|
||||
- [ ] Issue triage
|
||||
|
||||
---
|
||||
|
||||
### Phase 5: Post-Launch (T+1 week to T+4 weeks)
|
||||
|
||||
**Objectives:**
|
||||
- Monitor adoption
|
||||
- Gather feedback
|
||||
- Iterate on messaging
|
||||
- Report results
|
||||
|
||||
**Activities:**
|
||||
|
||||
**Week 1:**
|
||||
- [ ] Daily metrics monitoring
|
||||
- [ ] Community Q&A
|
||||
- [ ] Bug fixes prioritized
|
||||
- [ ] Feedback synthesis
|
||||
|
||||
**Week 2:**
|
||||
- [ ] First adoption metrics
|
||||
- [ ] Customer feedback interviews
|
||||
- [ ] Documentation updates
|
||||
- [ ] Follow-up content
|
||||
|
||||
**Week 4:**
|
||||
- [ ] Launch retrospective
|
||||
- [ ] Success metrics report
|
||||
- [ ] Lessons learned doc
|
||||
- [ ] Update launch playbook
|
||||
|
||||
---
|
||||
|
||||
## Launch Tier Details
|
||||
|
||||
### Tier 1: Major Launch
|
||||
|
||||
**When:**
|
||||
- New product GA
|
||||
- Major version release (v2.0, v3.0)
|
||||
- Significant platform expansion
|
||||
- Game-changing feature
|
||||
|
||||
**Timeline:** 12-16 weeks
|
||||
|
||||
**Investment:**
|
||||
- Full cross-functional GTM
|
||||
- PR/media outreach
|
||||
- Developer events
|
||||
- Partner coordination
|
||||
- Paid promotion
|
||||
|
||||
**Deliverables:**
|
||||
- Complete documentation
|
||||
- Multiple SDKs
|
||||
- Sample applications
|
||||
- Video tutorials
|
||||
- Interactive demos
|
||||
- Press release
|
||||
- Analyst briefings
|
||||
- Launch event/webinar
|
||||
- Partner co-marketing
|
||||
|
||||
---
|
||||
|
||||
### Tier 2: Standard Launch
|
||||
|
||||
**When:**
|
||||
- New features
|
||||
- New integrations
|
||||
- Additional SDKs
|
||||
- Regional expansion
|
||||
|
||||
**Timeline:** 6-8 weeks
|
||||
|
||||
**Investment:**
|
||||
- Selective GTM activities
|
||||
- Blog and social
|
||||
- Email to developer list
|
||||
- Documentation updates
|
||||
|
||||
**Deliverables:**
|
||||
- Feature documentation
|
||||
- Code samples
|
||||
- Blog post
|
||||
- Demo video
|
||||
- Email announcement
|
||||
- Social media
|
||||
- Changelog entry
|
||||
|
||||
---
|
||||
|
||||
### Tier 3: Minor Launch
|
||||
|
||||
**When:**
|
||||
- Incremental improvements
|
||||
- Bug fixes
|
||||
- Performance enhancements
|
||||
- Small feature additions
|
||||
|
||||
**Timeline:** 2-4 weeks
|
||||
|
||||
**Investment:**
|
||||
- Minimal marketing
|
||||
- Documentation only
|
||||
- Changelog
|
||||
|
||||
**Deliverables:**
|
||||
- Release notes
|
||||
- Updated docs
|
||||
- Changelog entry
|
||||
- In-app notification (if applicable)
|
||||
|
||||
---
|
||||
|
||||
## Developer Launch Best Practices
|
||||
|
||||
### 1. Documentation First
|
||||
|
||||
**Launch is NOT ready without:**
|
||||
- ✅ Getting started guide
|
||||
- ✅ API reference
|
||||
- ✅ At least 3 code samples
|
||||
- ✅ Integration guide
|
||||
|
||||
**Developer rule:** "If it's not documented, it doesn't exist"
|
||||
|
||||
---
|
||||
|
||||
### 2. Show, Don't Tell
|
||||
|
||||
**Developers want to see code:**
|
||||
|
||||
**Good:**
|
||||
```python
|
||||
# Initialize the SDK
|
||||
import acme_sdk
|
||||
|
||||
client = acme_sdk.Client(api_key="your_key")
|
||||
result = client.widgets.create(name="My Widget")
|
||||
print(result.id)
|
||||
```
|
||||
|
||||
**Bad:**
|
||||
"Our SDK makes it easy to create widgets with just a few lines of code"
|
||||
|
||||
---
|
||||
|
||||
### 3. Interactive > Passive
|
||||
|
||||
**Engagement hierarchy:**
|
||||
1. 🥇 Interactive tutorial/playground
|
||||
2. 🥈 Live demo
|
||||
3. 🥉 Demo video
|
||||
4. ❌ Static screenshots
|
||||
|
||||
---
|
||||
|
||||
### 4. Honest Technical Communication
|
||||
|
||||
**Developers appreciate:**
|
||||
- Limitations clearly stated
|
||||
- Performance characteristics
|
||||
- Pricing transparency
|
||||
- Migration complexity
|
||||
- Breaking changes
|
||||
|
||||
**Developers hate:**
|
||||
- Overpromising
|
||||
- Hidden limitations
|
||||
- Surprise breaking changes
|
||||
- Vendor lock-in
|
||||
|
||||
---
|
||||
|
||||
### 5. Community-First Approach
|
||||
|
||||
**Engage where developers are:**
|
||||
- Answer questions on Stack Overflow
|
||||
- Be active in GitHub discussions
|
||||
- Respond on Hacker News
|
||||
- Join relevant Discord/Slack
|
||||
- Participate in Reddit AMAs
|
||||
|
||||
**Don't:**
|
||||
- Spam communities
|
||||
- Ignore negative feedback
|
||||
- Delete critical comments
|
||||
- Only show up for launches
|
||||
|
||||
---
|
||||
|
||||
## Technical Metrics
|
||||
|
||||
### Developer Adoption Metrics
|
||||
|
||||
**Activation:**
|
||||
- Sandbox/trial sign-ups
|
||||
- First API call within 24 hours
|
||||
- SDK downloads
|
||||
- "Hello World" completions
|
||||
|
||||
**Engagement:**
|
||||
- Daily/Weekly Active Developers
|
||||
- API calls per developer
|
||||
- Features adopted
|
||||
- Integration depth
|
||||
|
||||
**Retention:**
|
||||
- Day 7, 30, 90 developer retention
|
||||
- Churn rate
|
||||
- NPS (Developer)
|
||||
|
||||
See `references/metrics_frameworks.md` for complete guide.
|
||||
|
||||
---
|
||||
|
||||
## Launch Templates
|
||||
|
||||
### Technical Blog Post Template
|
||||
|
||||
```markdown
|
||||
# Introducing [Feature/Product]
|
||||
|
||||
## The Problem
|
||||
|
||||
[Describe the developer pain point in technical detail]
|
||||
|
||||
## The Solution
|
||||
|
||||
[High-level technical overview]
|
||||
|
||||
## How It Works
|
||||
|
||||
[Technical architecture, with diagram]
|
||||
|
||||
## Getting Started
|
||||
|
||||
[Code sample showing basic usage]
|
||||
|
||||
## What's Next
|
||||
|
||||
[Roadmap tease]
|
||||
|
||||
[Link to full documentation]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Launch Email Template
|
||||
|
||||
**Subject:** [Feature] is now available
|
||||
|
||||
**Body:**
|
||||
```
|
||||
Hi [Developer Name],
|
||||
|
||||
We're excited to announce [Feature] is now generally available.
|
||||
|
||||
What it does:
|
||||
[One sentence technical description]
|
||||
|
||||
Why it matters:
|
||||
[Developer benefit]
|
||||
|
||||
Get started in 5 minutes:
|
||||
[Code snippet or quick start link]
|
||||
|
||||
Key resources:
|
||||
- Documentation: [link]
|
||||
- Sample code: [link]
|
||||
- API reference: [link]
|
||||
|
||||
Questions? Reply to this email or join us in [Discord/Slack].
|
||||
|
||||
Happy building!
|
||||
[Your Name]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Changelog Entry Template
|
||||
|
||||
```markdown
|
||||
## [Version] - YYYY-MM-DD
|
||||
|
||||
### Added
|
||||
- [New feature]: [Technical description]
|
||||
- Example: `client.newMethod(params)`
|
||||
- [Link to docs]
|
||||
|
||||
### Changed
|
||||
- [Breaking change]: [What changed and why]
|
||||
- Migration guide: [link]
|
||||
|
||||
### Fixed
|
||||
- [Bug fix]: [What was fixed]
|
||||
|
||||
### Deprecated
|
||||
- [Feature]: [Timeline for removal]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Partner/Integration Launches
|
||||
|
||||
### When You Have Partners
|
||||
|
||||
**Coordination needed:**
|
||||
- Joint messaging
|
||||
- Co-marketing plan
|
||||
- Technical validation
|
||||
- Mutual customer references
|
||||
|
||||
**Partner Enablement:**
|
||||
- [ ] Technical integration tested
|
||||
- [ ] Partner documentation
|
||||
- [ ] Joint case study
|
||||
- [ ] Co-branded assets
|
||||
- [ ] Sales team training
|
||||
|
||||
**Launch Activities:**
|
||||
- Co-authored blog posts
|
||||
- Joint webinar
|
||||
- Cross-promotion on social
|
||||
- Email to both lists
|
||||
- Mutual press release (Tier 1)
|
||||
|
||||
---
|
||||
|
||||
## Launch Retrospective
|
||||
|
||||
### Post-Launch Review (Within 30 days)
|
||||
|
||||
**Metrics Review:**
|
||||
- Did we hit adoption targets?
|
||||
- What was Day 1, Week 1, Month 1 usage?
|
||||
- Developer sentiment (NPS, social, support)?
|
||||
- Press/analyst coverage (if applicable)?
|
||||
|
||||
**What Worked:**
|
||||
- Which channels drove most adoption?
|
||||
- What content resonated?
|
||||
- Which enablement assets were most used?
|
||||
|
||||
**What Didn't:**
|
||||
- Where did developers get stuck?
|
||||
- What documentation was missing?
|
||||
- Which assumptions were wrong?
|
||||
|
||||
**Action Items:**
|
||||
- Documentation improvements
|
||||
- Messaging refinements
|
||||
- Process improvements for next launch
|
||||
|
||||
**Template:** [Document in Notion/Confluence]
|
||||
|
||||
---
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
### Pitfall 1: Launching Without Complete Docs
|
||||
|
||||
**Problem:** "Docs will be ready soon" = Dead launch
|
||||
|
||||
**Solution:** Docs are non-negotiable. Delay launch if needed.
|
||||
|
||||
---
|
||||
|
||||
### Pitfall 2: Marketing-Speak for Developers
|
||||
|
||||
**Problem:** "Revolutionary", "Seamless", "Game-changing"
|
||||
|
||||
**Solution:** Use concrete technical language, metrics, code.
|
||||
|
||||
---
|
||||
|
||||
### Pitfall 3: Ignoring Migration Complexity
|
||||
|
||||
**Problem:** Breaking changes with no migration guide
|
||||
|
||||
**Solution:** Clear migration guide, migration tools, version support plan.
|
||||
|
||||
---
|
||||
|
||||
### Pitfall 4: Over-Indexing on Launch Day
|
||||
|
||||
**Problem:** All effort on Day 1, nothing for ongoing adoption
|
||||
|
||||
**Solution:** Plan 4-week post-launch content calendar.
|
||||
|
||||
---
|
||||
|
||||
### Pitfall 5: No Developer Feedback Loop
|
||||
|
||||
**Problem:** Launch and disappear
|
||||
|
||||
**Solution:** Active community engagement, regular office hours.
|
||||
|
||||
---
|
||||
|
||||
## Resources
|
||||
|
||||
### Scripts
|
||||
|
||||
- **assess_launch_tier.sh** - Determine appropriate launch tier
|
||||
- **generate_launch_plan.sh** - Create comprehensive launch plan
|
||||
- **validate_readiness.sh** - Pre-launch readiness check
|
||||
|
||||
### References
|
||||
|
||||
- **launch_tiers.md** - Complete launch tier framework
|
||||
- **developer_enablement.md** - Developer enablement checklist
|
||||
- **launch_messaging.md** - Technical messaging templates
|
||||
- **metrics_frameworks.md** - Developer product metrics guide
|
||||
|
||||
---
|
||||
|
||||
## Real-World Examples
|
||||
|
||||
### Example 1: API GA Launch (Tier 1)
|
||||
|
||||
**Product:** New REST API for developer platform
|
||||
|
||||
**Timeline:** 12 weeks
|
||||
|
||||
**Key Activities:**
|
||||
- Complete API documentation
|
||||
- 5 SDKs (Python, Node, Ruby, Go, Java)
|
||||
- Interactive API explorer
|
||||
- 10+ sample applications
|
||||
- Video tutorial series
|
||||
- Developer webinar
|
||||
- Blog post + case studies
|
||||
- HN/Reddit launch
|
||||
- Email to 50K developers
|
||||
|
||||
**Results:**
|
||||
- 10K API keys issued Week 1
|
||||
- 60% activation rate (first API call)
|
||||
- 40% Day 7 retention
|
||||
- #1 on Hacker News
|
||||
|
||||
---
|
||||
|
||||
### Example 2: New Integration (Tier 2)
|
||||
|
||||
**Product:** Integration with popular DevOps tool
|
||||
|
||||
**Timeline:** 6 weeks
|
||||
|
||||
**Key Activities:**
|
||||
- Integration guide
|
||||
- Sample workflow
|
||||
- Blog post
|
||||
- Partner co-marketing
|
||||
- Demo video
|
||||
- Email announcement
|
||||
|
||||
**Results:**
|
||||
- 2K integration activations Month 1
|
||||
- 25% of existing users tried it
|
||||
- High engagement metric
|
||||
|
||||
---
|
||||
|
||||
### Example 3: SDK Update (Tier 3)
|
||||
|
||||
**Product:** New SDK version with performance improvements
|
||||
|
||||
**Timeline:** 2 weeks
|
||||
|
||||
**Key Activities:**
|
||||
- Release notes
|
||||
- Migration guide
|
||||
- Changelog
|
||||
- Tweet/X post
|
||||
|
||||
**Results:**
|
||||
- 30% upgrade rate Week 1
|
||||
- Minimal support burden
|
||||
- Positive community feedback
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
Technical launches require:
|
||||
|
||||
1. **Complete Documentation** - Non-negotiable
|
||||
2. **Code Samples** - Show, don't tell
|
||||
3. **Developer Enablement** - Make it easy to try
|
||||
4. **Technical Credibility** - Speak the language
|
||||
5. **Community Engagement** - Be where developers are
|
||||
6. **Clear Metrics** - Measure what matters
|
||||
7. **Post-Launch Commitment** - Launch is day 1, not the finish line
|
||||
|
||||
Use the scripts to streamline planning, follow the frameworks for consistency, and always put developers first.
|
||||
|
||||
**Get started:**
|
||||
```bash
|
||||
scripts/assess_launch_tier.sh
|
||||
```
|
||||
@@ -0,0 +1,246 @@
|
||||
# Developer Enablement Checklist
|
||||
|
||||
Comprehensive checklist for enabling developers to adopt your technical product.
|
||||
|
||||
---
|
||||
|
||||
## Critical: Documentation
|
||||
|
||||
### Getting Started Guide
|
||||
- [ ] **Installation instructions** (< 5 minutes)
|
||||
- [ ] **Quick start tutorial** (Hello World in < 10 minutes)
|
||||
- [ ] **Basic concepts** explained
|
||||
- [ ] **First successful API call** walkthrough
|
||||
- [ ] **Authentication** setup guide
|
||||
- [ ] **Common gotchas** documented
|
||||
|
||||
### API Reference
|
||||
- [ ] **All endpoints** documented
|
||||
- [ ] **Request/response examples** for each endpoint
|
||||
- [ ] **Error codes** and meanings
|
||||
- [ ] **Rate limits** clearly stated
|
||||
- [ ] **Authentication** methods
|
||||
- [ ] **Versioning** strategy explained
|
||||
- [ ] **Changelog** maintained
|
||||
|
||||
### Integration Guides
|
||||
- [ ] **Step-by-step** integration tutorials
|
||||
- [ ] **Common use cases** covered
|
||||
- [ ] **Best practices** documented
|
||||
- [ ] **Performance tips**
|
||||
- [ ] **Security considerations**
|
||||
|
||||
###Migration Guide (if applicable)
|
||||
- [ ] **Breaking changes** highlighted
|
||||
- [ ] **Migration steps** clear
|
||||
- [ ] **Before/after code** examples
|
||||
- [ ] **Timeline** for deprecations
|
||||
- [ ] **Support** for old version
|
||||
|
||||
---
|
||||
|
||||
## Critical: Code Assets
|
||||
|
||||
### SDKs/Client Libraries
|
||||
- [ ] **Python** SDK
|
||||
- [ ] **JavaScript/Node** SDK
|
||||
- [ ] **Additional languages** as needed
|
||||
- [ ] **Well-documented** public APIs
|
||||
- [ ] **Type definitions** (TypeScript, etc.)
|
||||
- [ ] **Published** to package managers
|
||||
- [ ] **Examples** in README
|
||||
|
||||
### Sample Applications
|
||||
- [ ] **Simple** "Hello World" app
|
||||
- [ ] **Realistic** integration example
|
||||
- [ ] **Production-ready** template
|
||||
- [ ] **README** with setup instructions
|
||||
- [ ] **Runnable** locally
|
||||
|
||||
### Code Snippets
|
||||
- [ ] **Common operations** (CRUD)
|
||||
- [ ] **Authentication** examples
|
||||
- [ ] **Error handling** patterns
|
||||
- [ ] **Copy-paste** ready
|
||||
- [ ] **Multiple languages**
|
||||
|
||||
---
|
||||
|
||||
## Important: Developer Experience
|
||||
|
||||
### Interactive Tools
|
||||
- [ ] **API explorer** / playground
|
||||
- [ ] **Interactive tutorials**
|
||||
- [ ] **Sandbox environment** (no credit card)
|
||||
- [ ] **Test mode** / mock data
|
||||
- [ ] **Debugging tools**
|
||||
|
||||
### Developer Portal
|
||||
- [ ] **Dashboard** for API keys
|
||||
- [ ] **Usage analytics**
|
||||
- [ ] **Billing/quota** visibility
|
||||
- [ ] **Team management**
|
||||
- [ ] **Support access**
|
||||
|
||||
### Testing & Debugging
|
||||
- [ ] **Test credentials** available
|
||||
- [ ] **Webhook testing** tools
|
||||
- [ ] **Request logs** accessible
|
||||
- [ ] **Error debugging** guides
|
||||
- [ ] **Postman collection** (if REST API)
|
||||
|
||||
---
|
||||
|
||||
## Important: Learning Resources
|
||||
|
||||
### Video Content
|
||||
- [ ] **Demo video** (3-5 minutes)
|
||||
- [ ] **Tutorial series** for key features
|
||||
- [ ] **Architecture overview** video
|
||||
- [ ] **Best practices** video
|
||||
|
||||
### Written Tutorials
|
||||
- [ ] **Blog posts** for common use cases
|
||||
- [ ] **Integration tutorials**
|
||||
- [ ] **Performance optimization** guides
|
||||
- [ ] **Security best practices**
|
||||
|
||||
### Community Resources
|
||||
- [ ] **FAQ** section
|
||||
- [ ] **Troubleshooting** guide
|
||||
- [ ] **Community forum** / Discord / Slack
|
||||
- [ ] **Stack Overflow** tag
|
||||
- [ ] **GitHub Discussions** enabled
|
||||
|
||||
---
|
||||
|
||||
## Important: Technical Specifications
|
||||
|
||||
### Architecture Documentation
|
||||
- [ ] **System architecture** diagram
|
||||
- [ ] **Data flow** diagrams
|
||||
- [ ] **Sequence diagrams** for complex flows
|
||||
- [ ] **Infrastructure** overview
|
||||
- [ ] **Scaling** characteristics
|
||||
|
||||
### Performance & Limits
|
||||
- [ ] **Rate limits** documented
|
||||
- [ ] **Latency expectations** (p50, p95, p99)
|
||||
- [ ] **Throughput** capabilities
|
||||
- [ ] **Quotas** and limits
|
||||
- [ ] **SLA** commitments
|
||||
|
||||
### Security Documentation
|
||||
- [ ] **Authentication** methods
|
||||
- [ ] **Authorization** model
|
||||
- [ ] **Data encryption** (at rest, in transit)
|
||||
- [ ] **Compliance** certifications
|
||||
- [ ] **Security best practices**
|
||||
- [ ] **Vulnerability** reporting process
|
||||
|
||||
---
|
||||
|
||||
## Nice to Have: Advanced Resources
|
||||
|
||||
### Reference Architectures
|
||||
- [ ] **Common patterns** documented
|
||||
- [ ] **Production deployment** examples
|
||||
- [ ] **Multi-region** setups
|
||||
- [ ] **High availability** configurations
|
||||
|
||||
### Integrations
|
||||
- [ ] **Third-party** tool integrations
|
||||
- [ ] **Framework** specific guides (React, Vue, etc.)
|
||||
- [ ] **CI/CD** integration examples
|
||||
- [ ] **Monitoring** integration guides
|
||||
|
||||
### Developer Tools
|
||||
- [ ] **CLI** tool
|
||||
- [ ] **Browser extensions**
|
||||
- [ ] **IDE plugins** (VS Code, etc.)
|
||||
- [ ] **Linters** / code validators
|
||||
|
||||
---
|
||||
|
||||
## Launch Day Specific
|
||||
|
||||
### Pre-Launch
|
||||
- [ ] **Beta testers** given early access
|
||||
- [ ] **Documentation** live on staging
|
||||
- [ ] **SDKs** tagged and ready
|
||||
- [ ] **Samples** tested end-to-end
|
||||
|
||||
### Launch Day
|
||||
- [ ] **Docs** published to production
|
||||
- [ ] **SDKs** released to package managers
|
||||
- [ ] **Samples** available on GitHub
|
||||
- [ ] **Playground** accessible
|
||||
- [ ] **Support** channels staffed
|
||||
|
||||
### Post-Launch
|
||||
- [ ] **Monitor** documentation traffic
|
||||
- [ ] **Respond** to questions quickly
|
||||
- [ ] **Update** docs based on feedback
|
||||
- [ ] **Create** additional resources as needed
|
||||
|
||||
---
|
||||
|
||||
## Quality Checks
|
||||
|
||||
### Documentation Quality
|
||||
- [ ] **Tested** by someone unfamiliar with product
|
||||
- [ ] **Code samples** all execute successfully
|
||||
- [ ] **Links** all work
|
||||
- [ ] **Screenshots** up-to-date
|
||||
- [ ] **Grammar/spelling** checked
|
||||
- [ ] **Search** functionality works
|
||||
- [ ] **Mobile** responsive
|
||||
|
||||
### Code Quality
|
||||
- [ ] **SDKs** have tests
|
||||
- [ ] **Sample apps** run without errors
|
||||
- [ ] **Dependencies** up-to-date
|
||||
- [ ] **Security** vulnerabilities checked
|
||||
- [ ] **Licenses** clearly stated
|
||||
|
||||
---
|
||||
|
||||
## By Audience
|
||||
|
||||
### Beginner Developers
|
||||
- Clear getting started
|
||||
- Simple examples
|
||||
- Video tutorials
|
||||
- Interactive playground
|
||||
- Active community support
|
||||
|
||||
### Experienced Developers
|
||||
- Comprehensive API reference
|
||||
- Advanced use cases
|
||||
- Performance documentation
|
||||
- Architecture details
|
||||
- Migration guides
|
||||
|
||||
### Enterprise/Teams
|
||||
- Security documentation
|
||||
- Compliance information
|
||||
- Team management docs
|
||||
- SSO integration
|
||||
- SLA details
|
||||
|
||||
---
|
||||
|
||||
## Measurement
|
||||
|
||||
Track these metrics post-launch:
|
||||
|
||||
- **Documentation traffic**
|
||||
- **Time to first API call**
|
||||
- **Sandbox activation rate**
|
||||
- **SDK download count**
|
||||
- **Sample app clones**
|
||||
- **Support ticket volume**
|
||||
- **Community questions**
|
||||
- **Tutorial completion rate**
|
||||
|
||||
Use data to improve enablement continuously.
|
||||
436
skills/technical-launch-planner/references/launch_messaging.md
Normal file
436
skills/technical-launch-planner/references/launch_messaging.md
Normal file
@@ -0,0 +1,436 @@
|
||||
# Technical Launch Messaging
|
||||
|
||||
Messaging frameworks and templates for developer-focused product launches.
|
||||
|
||||
---
|
||||
|
||||
## Messaging Principles for Developers
|
||||
|
||||
### DO:
|
||||
- ✅ **Be specific** - Use concrete technical details
|
||||
- ✅ **Show code** - Developers want to see, not read
|
||||
- ✅ **State limitations** - Honest about what it can't do
|
||||
- ✅ **Provide metrics** - Performance numbers, benchmarks
|
||||
- ✅ **Explain why** - Technical reasoning matters
|
||||
- ✅ **Link to docs** - Make it easy to try
|
||||
|
||||
### DON'T:
|
||||
- ❌ **Use marketing jargon** - "Revolutionary", "game-changing"
|
||||
- ❌ **Oversimplify** - Developers can handle complexity
|
||||
- ❌ **Hide limitations** - They'll find them anyway
|
||||
- ❌ **Make unsubstantiated claims** - Back it up with data
|
||||
- ❌ **Skip code examples** - Abstract descriptions fail
|
||||
|
||||
---
|
||||
|
||||
## Messaging Framework
|
||||
|
||||
### Problem Statement
|
||||
**Format:** [Current pain point] → [Why existing solutions fail] → [Impact on developers]
|
||||
|
||||
**Example:**
|
||||
"Debugging distributed systems is painful. Traditional logging tools weren't built for microservices, forcing developers to manually correlate logs across dozens of services. This turns a 5-minute bug into a 5-hour investigation."
|
||||
|
||||
---
|
||||
|
||||
### Solution Overview
|
||||
**Format:** [What it is] → [How it works (technical)] → [Key benefit]
|
||||
|
||||
**Example:**
|
||||
"Distributed Tracer automatically instruments your services to create a unified view of requests across your entire stack. Using OpenTelemetry standards, it correlates logs, metrics, and traces in real-time, reducing MTTR by 80%."
|
||||
|
||||
---
|
||||
|
||||
### Key Differentiators
|
||||
**Format:** [Feature] → [Technical implementation] → [Why it matters]
|
||||
|
||||
**Example:**
|
||||
"Zero-config auto-instrumentation. Our SDK uses bytecode injection to automatically trace all HTTP calls, database queries, and external APIs without code changes. Deploy in under 5 minutes instead of days."
|
||||
|
||||
---
|
||||
|
||||
## Launch Announcement Template
|
||||
|
||||
### Blog Post Structure
|
||||
|
||||
```markdown
|
||||
# Introducing [Product]: [One-line value prop]
|
||||
|
||||
## TL;DR
|
||||
- [Key point 1 with metric]
|
||||
- [Key point 2 with metric]
|
||||
- [Get started link]
|
||||
|
||||
## The Problem
|
||||
|
||||
[Describe the developer pain in detail. Be specific.]
|
||||
|
||||
**Example:**
|
||||
Every API call in a distributed system touches 5-10 services. When something breaks, you're left grep'ing through gigabytes of logs, trying to piece together what happened. We've all been there.
|
||||
|
||||
## The Solution
|
||||
|
||||
[High-level overview]
|
||||
|
||||
**How it works:**
|
||||
|
||||
\`\`\`python
|
||||
# Show concrete code example
|
||||
import tracer
|
||||
|
||||
tracer.init(api_key="your_key")
|
||||
|
||||
# That's it. All requests automatically traced.
|
||||
\`\`\`
|
||||
|
||||
## Key Features
|
||||
|
||||
### 1. [Feature Name]
|
||||
|
||||
**What it does:** [Technical description]
|
||||
|
||||
**Why it matters:** [Developer benefit]
|
||||
|
||||
**Example:**
|
||||
\`\`\`[language]
|
||||
[Code showing the feature]
|
||||
\`\`\`
|
||||
|
||||
[Repeat for top 3-5 features]
|
||||
|
||||
## Performance
|
||||
|
||||
[Include benchmarks, metrics]
|
||||
|
||||
- Latency: < 1ms overhead (p99)
|
||||
- Throughput: 100K traces/second per instance
|
||||
- Storage: 90-day retention included
|
||||
|
||||
## Get Started in 5 Minutes
|
||||
|
||||
\`\`\`bash
|
||||
# Installation
|
||||
npm install @company/sdk
|
||||
|
||||
# Basic setup
|
||||
[Minimal code to get value]
|
||||
\`\`\`
|
||||
|
||||
[Link to full documentation]
|
||||
|
||||
## What's Next
|
||||
|
||||
[Roadmap tease for 1-2 upcoming features]
|
||||
|
||||
## Resources
|
||||
|
||||
- [Documentation]
|
||||
- [Sample apps]
|
||||
- [API reference]
|
||||
- [Community Discord]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Email Announcement Template
|
||||
|
||||
**Subject Lines (A/B test these):**
|
||||
- "[Product] is now GA - [Key benefit]"
|
||||
- "Ship faster with [Product]"
|
||||
- "[Pain point solved]: Introducing [Product]"
|
||||
|
||||
**Body:**
|
||||
|
||||
```
|
||||
Hi [Name],
|
||||
|
||||
We're excited to announce [Product] is now generally available.
|
||||
|
||||
What it does:
|
||||
[One sentence technical description]
|
||||
|
||||
Why it matters to you:
|
||||
[Specific benefit for recipient's role/tech stack]
|
||||
|
||||
Get started in 5 minutes:
|
||||
|
||||
```[language]
|
||||
[Minimal code example]
|
||||
```
|
||||
|
||||
Key features:
|
||||
• [Feature 1 - one line]
|
||||
• [Feature 2 - one line]
|
||||
• [Feature 3 - one line]
|
||||
|
||||
Resources:
|
||||
→ Documentation: [link]
|
||||
→ Sample code: [link]
|
||||
→ API reference: [link]
|
||||
|
||||
[If Beta]: As a beta user, you already have access. Check your dashboard to enable.
|
||||
|
||||
Questions? Hit reply or join us in [Discord/Slack].
|
||||
|
||||
Happy building,
|
||||
[Name]
|
||||
[Title]
|
||||
|
||||
P.S. [Call to action or incentive]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Social Media Templates
|
||||
|
||||
### Twitter/X (Technical)
|
||||
|
||||
**Format 1: Problem → Solution**
|
||||
```
|
||||
Tired of [pain point]?
|
||||
|
||||
[Product] gives you [benefit]:
|
||||
• [Feature 1]
|
||||
• [Feature 2]
|
||||
• [Feature 3]
|
||||
|
||||
Get started: [link]
|
||||
|
||||
[Include code snippet image or architecture diagram]
|
||||
```
|
||||
|
||||
**Format 2: Show the Code**
|
||||
```
|
||||
This is all it takes to [achieve outcome]:
|
||||
|
||||
[Code snippet image]
|
||||
|
||||
Try it now: [link]
|
||||
#developer #[tech stack]
|
||||
```
|
||||
|
||||
**Format 3: Metrics**
|
||||
```
|
||||
We just reduced distributed tracing overhead from 5ms to < 1ms.
|
||||
|
||||
How? [Link to technical blog post]
|
||||
|
||||
Open-sourced the approach: [GitHub link]
|
||||
```
|
||||
|
||||
### LinkedIn (Business + Technical)
|
||||
|
||||
**Format:**
|
||||
```
|
||||
[Company] is launching [Product] today.
|
||||
|
||||
The problem we're solving:
|
||||
[2-3 sentences about developer pain]
|
||||
|
||||
Our approach:
|
||||
[Technical differentiation]
|
||||
|
||||
Early results from beta:
|
||||
• [Metric/testimonial 1]
|
||||
• [Metric/testimonial 2]
|
||||
|
||||
If you're working on [use case], check it out: [link]
|
||||
|
||||
[Include demo video or architecture diagram]
|
||||
```
|
||||
|
||||
### Hacker News Post
|
||||
|
||||
**Title Format:**
|
||||
- "Show HN: [Product] – [One-line description]"
|
||||
- "[Product] – [Interesting technical approach]"
|
||||
|
||||
**Comment (required):**
|
||||
```
|
||||
Hey HN! Creator here.
|
||||
|
||||
We built [Product] to solve [problem we experienced].
|
||||
|
||||
Technical approach:
|
||||
[2-3 paragraphs explaining interesting technical decisions]
|
||||
|
||||
What's different:
|
||||
[Why this approach vs. alternatives]
|
||||
|
||||
How to try it:
|
||||
[Quick start instructions]
|
||||
|
||||
Happy to answer questions!
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Positioning Statements
|
||||
|
||||
### General Template
|
||||
"For [target developers] who [need/pain point], [Product] is a [category] that [key benefit]. Unlike [alternatives], we [unique differentiation]."
|
||||
|
||||
### Examples
|
||||
|
||||
**API Tool:**
|
||||
"For backend developers who need reliable API integrations, FastAPI Connect is an API orchestration platform that auto-retries, caches, and monitors all external calls. Unlike building retry logic yourself, we provide production-grade reliability out of the box."
|
||||
|
||||
**Developer Platform:**
|
||||
"For platform teams building internal developer platforms, DevHub is a self-service portal that gives developers one-click access to infrastructure. Unlike traditional ticketing systems, we automate provisioning in seconds instead of days."
|
||||
|
||||
---
|
||||
|
||||
## Value Propositions by Persona
|
||||
|
||||
### Backend Developers
|
||||
**Focus:** Performance, reliability, ease of integration
|
||||
|
||||
"Reduce latency by 40% with one line of code"
|
||||
|
||||
### DevOps/SRE
|
||||
**Focus:** Reliability, observability, automation
|
||||
|
||||
"Cut MTTR from hours to minutes with automated root cause analysis"
|
||||
|
||||
### Engineering Leaders
|
||||
**Focus:** Productivity, costs, team velocity
|
||||
|
||||
"Ship 2x faster by eliminating [bottleneck]"
|
||||
|
||||
### Security Teams
|
||||
**Focus:** Compliance, security, visibility
|
||||
|
||||
"SOC 2 Type II compliant with built-in audit logging"
|
||||
|
||||
---
|
||||
|
||||
## Messaging by Launch Tier
|
||||
|
||||
### Tier 1 (Major Launch)
|
||||
- **Bold claims** backed by data
|
||||
- **Vision** for the future
|
||||
- **Ecosystem** impact
|
||||
- **Industry** transformation
|
||||
|
||||
**Example:**
|
||||
"Redefining how developers build distributed systems"
|
||||
|
||||
### Tier 2 (Standard)
|
||||
- **Practical benefits**
|
||||
- **Specific use cases**
|
||||
- **Integration** value
|
||||
- **Productivity** gains
|
||||
|
||||
**Example:**
|
||||
"The fastest way to add real-time features to your app"
|
||||
|
||||
### Tier 3 (Minor)
|
||||
- **Specific improvement**
|
||||
- **Developer benefit**
|
||||
- **Clear changelog**
|
||||
|
||||
**Example:**
|
||||
"Python SDK now 3x faster with async support"
|
||||
|
||||
---
|
||||
|
||||
## Competitive Positioning
|
||||
|
||||
### When to Mention Competitors
|
||||
|
||||
**DO mention when:**
|
||||
- You have clear technical superiority
|
||||
- Migration is a key use case
|
||||
- Comparison requested by prospects
|
||||
|
||||
**DON'T mention when:**
|
||||
- You're the market leader
|
||||
- Competitor is much larger
|
||||
- Claim isn't defensible
|
||||
|
||||
### Competitive Messaging Template
|
||||
|
||||
"Unlike [Competitor], [Product] [specific advantage]:
|
||||
|
||||
**[Competitor]:**
|
||||
- [Limitation 1]
|
||||
- [Limitation 2]
|
||||
|
||||
**[Product]:**
|
||||
- [Advantage 1] - [metric]
|
||||
- [Advantage 2] - [metric]
|
||||
|
||||
[Code comparison or performance benchmark]"
|
||||
|
||||
---
|
||||
|
||||
## Technical Credibility Signals
|
||||
|
||||
Include these to build trust:
|
||||
|
||||
- **Open source** components used
|
||||
- **Standards** supported (OpenTelemetry, OAuth, etc.)
|
||||
- **Scale** handled (requests/sec, data volume)
|
||||
- **Customers** using in production (if allowed)
|
||||
- **Team background** (ex-Google, ex-AWS, etc.)
|
||||
- **Security** certifications (SOC 2, ISO 27001)
|
||||
- **Performance** benchmarks
|
||||
- **GitHub** stars (if applicable)
|
||||
|
||||
---
|
||||
|
||||
## Avoiding Common Mistakes
|
||||
|
||||
### Mistake 1: Too Abstract
|
||||
**Bad:** "Simplify your workflow"
|
||||
**Good:** "Reduce deployment time from 45 minutes to 2 minutes"
|
||||
|
||||
### Mistake 2: Jargon Overload
|
||||
**Bad:** "Leverage synergistic paradigms"
|
||||
**Good:** "Run the same code on AWS, GCP, and Azure"
|
||||
|
||||
### Mistake 3: No Proof
|
||||
**Bad:** "The fastest API"
|
||||
**Good:** "p99 latency < 50ms (see benchmark: [link])"
|
||||
|
||||
### Mistake 4: Feature List
|
||||
**Bad:** "Includes caching, retries, and monitoring"
|
||||
**Good:** "Auto-retry failed requests up to 3x with exponential backoff"
|
||||
|
||||
### Mistake 5: Ignoring Migration
|
||||
**Bad:** [No mention of existing solutions]
|
||||
**Good:** "Migrate from [Competitor] in under 1 hour: [guide]"
|
||||
|
||||
---
|
||||
|
||||
## Testing Your Messaging
|
||||
|
||||
### Internal Test
|
||||
- [ ] Can a new engineer explain the value?
|
||||
- [ ] Do engineers volunteer to use it?
|
||||
- [ ] Does it pass the "so what?" test?
|
||||
|
||||
### External Test
|
||||
- [ ] Beta feedback positive?
|
||||
- [ ] Clear from HN/Reddit comments?
|
||||
- [ ] Low support questions about "what is it?"
|
||||
|
||||
### Metrics to Watch
|
||||
- Email open rate (> 25% good for developer emails)
|
||||
- Click-through rate to docs (> 10%)
|
||||
- Sign-up conversion (depends on product)
|
||||
- Social engagement (shares, comments)
|
||||
- Media pickup (for Tier 1)
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
**Technical messaging succeeds when:**
|
||||
1. Problem is relatable
|
||||
2. Solution is clear (with code)
|
||||
3. Benefits are concrete
|
||||
4. Limitations are honest
|
||||
5. Getting started is easy
|
||||
|
||||
**Keep developer-first always.**
|
||||
553
skills/technical-launch-planner/references/launch_tiers.md
Normal file
553
skills/technical-launch-planner/references/launch_tiers.md
Normal file
@@ -0,0 +1,553 @@
|
||||
# Launch Tier Framework
|
||||
|
||||
Complete guide to determining and executing different launch tiers for technical products.
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Not all launches are created equal. The launch tier framework helps you allocate the right resources and effort based on the scope and impact of what you're launching.
|
||||
|
||||
**Key Principle:** Match investment to impact.
|
||||
|
||||
---
|
||||
|
||||
## The Three Tiers
|
||||
|
||||
| Tier | Type | Investment | Timeline | Example |
|
||||
|------|------|------------|----------|---------|
|
||||
| **Tier 1** | Major | Full GTM | 12-16 weeks | New product GA, v2.0 |
|
||||
| **Tier 2** | Standard | Selective GTM | 6-8 weeks | New feature, integration |
|
||||
| **Tier 3** | Minor | Minimal GTM | 2-4 weeks | Update, improvement |
|
||||
|
||||
---
|
||||
|
||||
## Tier 1: Major Launch
|
||||
|
||||
### When to Use
|
||||
|
||||
- **New product GA** (General Availability)
|
||||
- **Major version release** (v2.0, v3.0)
|
||||
- **Platform expansion** (new capabilities)
|
||||
- **Game-changing feature** (industry first)
|
||||
- **New market entry**
|
||||
|
||||
### Characteristics
|
||||
|
||||
**Scope:**
|
||||
- Impacts all or most users
|
||||
- New revenue stream potential
|
||||
- Significant competitive differentiation
|
||||
- Industry-level interest expected
|
||||
- Major technical undertaking
|
||||
|
||||
**Timeline:** 12-16 weeks
|
||||
|
||||
**Budget:** $50K-$500K+ depending on company size
|
||||
|
||||
---
|
||||
|
||||
### Deliverables
|
||||
|
||||
#### Documentation (Complete Set)
|
||||
- [ ] Getting started guide
|
||||
- [ ] Complete API reference
|
||||
- [ ] Integration guides (3+)
|
||||
- [ ] Migration guide
|
||||
- [ ] Best practices guide
|
||||
- [ ] Troubleshooting guide
|
||||
- [ ] Video tutorial series (5+ videos)
|
||||
- [ ] Architecture documentation
|
||||
|
||||
#### Code Assets
|
||||
- [ ] Multiple SDKs (3+ languages)
|
||||
- [ ] Sample applications (3+ different use cases)
|
||||
- [ ] Starter templates
|
||||
- [ ] Code snippet library
|
||||
- [ ] Interactive playground/sandbox
|
||||
- [ ] CLI tools (if applicable)
|
||||
|
||||
#### Marketing Assets
|
||||
- [ ] Launch blog post (long-form)
|
||||
- [ ] Product page redesign
|
||||
- [ ] Demo video (professional)
|
||||
- [ ] Case studies (2-3)
|
||||
- [ ] Infographic/visual assets
|
||||
- [ ] Explainer video
|
||||
- [ ] Social media campaign
|
||||
- [ ] Email nurture series
|
||||
|
||||
#### PR & Communications
|
||||
- [ ] Press release
|
||||
- [ ] Media kit
|
||||
- [ ] Analyst briefings (Gartner, Forrester)
|
||||
- [ ] Press tour
|
||||
- [ ] Spokesperson training
|
||||
- [ ] Crisis communication plan
|
||||
|
||||
#### Sales Enablement
|
||||
- [ ] Technical battlecard
|
||||
- [ ] Competitive analysis
|
||||
- [ ] Demo script (detailed)
|
||||
- [ ] ROI calculator
|
||||
- [ ] Customer presentation deck
|
||||
- [ ] Pricing/packaging materials
|
||||
- [ ] FAQ (20+ questions)
|
||||
|
||||
#### Events
|
||||
- [ ] Launch event/webinar
|
||||
- [ ] Customer workshops
|
||||
- [ ] Conference talks
|
||||
- [ ] Community meetups
|
||||
|
||||
---
|
||||
|
||||
### Launch Channels
|
||||
|
||||
**Primary:**
|
||||
- Developer documentation (hero banner)
|
||||
- Company blog (featured)
|
||||
- Email (entire developer base)
|
||||
- Social media (coordinated campaign)
|
||||
- Product Hunt launch
|
||||
- Hacker News announcement
|
||||
- Press release distribution
|
||||
|
||||
**Secondary:**
|
||||
- Tech press outreach (TechCrunch, VentureBeat, etc.)
|
||||
- Developer communities (Reddit, Dev.to)
|
||||
- YouTube (demo + tutorials)
|
||||
- Podcasts (interviews)
|
||||
- Webinars
|
||||
- Virtual events
|
||||
|
||||
**Tertiary:**
|
||||
- Conference presentations
|
||||
- Industry publications
|
||||
- Analyst reports
|
||||
- Partner co-marketing
|
||||
- Influencer outreach
|
||||
|
||||
---
|
||||
|
||||
### Team & Resources
|
||||
|
||||
**Core Launch Team:**
|
||||
- Product Marketing Lead
|
||||
- Product Manager
|
||||
- Engineering Lead
|
||||
- Developer Relations
|
||||
- Sales Engineering
|
||||
- PR/Communications
|
||||
- Content Marketing
|
||||
- Design
|
||||
- Legal/Compliance
|
||||
|
||||
**External Resources:**
|
||||
- PR agency
|
||||
- Video production
|
||||
- Event planning
|
||||
- Analyst relations
|
||||
|
||||
**Time Commitment:**
|
||||
- PMM: 100% for 8+ weeks
|
||||
- PM: 50%
|
||||
- Eng: 25% (docs, demos)
|
||||
- DevRel: 75%
|
||||
|
||||
---
|
||||
|
||||
### Success Metrics (Tier 1)
|
||||
|
||||
**Week 1:**
|
||||
- 10K+ API keys / sign-ups
|
||||
- 50%+ activation rate
|
||||
- 1M+ webpage views
|
||||
- 100K+ social impressions
|
||||
- 10+ press mentions
|
||||
|
||||
**Month 1:**
|
||||
- 25K+ active developers
|
||||
- 40%+ Day 7 retention
|
||||
- 5%+ paid conversion (if applicable)
|
||||
- NPS > 40
|
||||
|
||||
**Quarter 1:**
|
||||
- 50K+ active developers
|
||||
- $X ARR (if revenue product)
|
||||
- 3+ case studies published
|
||||
- Industry recognition (awards, mentions)
|
||||
|
||||
---
|
||||
|
||||
### Budget Breakdown (Example)
|
||||
|
||||
| Item | Cost Range |
|
||||
|------|------------|
|
||||
| PR Agency | $20K-$50K |
|
||||
| Video Production | $10K-$30K |
|
||||
| Event/Webinar | $15K-$40K |
|
||||
| Paid Promotion | $25K-$100K |
|
||||
| Analyst Relations | $10K-$30K |
|
||||
| Design Assets | $5K-$15K |
|
||||
| Tools/Software | $5K-$10K |
|
||||
| **Total** | **$90K-$275K** |
|
||||
|
||||
---
|
||||
|
||||
## Tier 2: Standard Launch
|
||||
|
||||
### When to Use
|
||||
|
||||
- **New feature** (significant but not transformative)
|
||||
- **Integration** with popular tool
|
||||
- **SDK** for new language
|
||||
- **Regional expansion**
|
||||
- **Beta to GA** transition
|
||||
|
||||
### Characteristics
|
||||
|
||||
**Scope:**
|
||||
- Impacts segment of users (25-75%)
|
||||
- Moderate revenue impact
|
||||
- Some competitive differentiation
|
||||
- Developer community interest
|
||||
- Moderate technical complexity
|
||||
|
||||
**Timeline:** 6-8 weeks
|
||||
|
||||
**Budget:** $10K-$50K
|
||||
|
||||
---
|
||||
|
||||
### Deliverables
|
||||
|
||||
#### Documentation
|
||||
- [ ] Feature guide
|
||||
- [ ] API reference updates
|
||||
- [ ] Code samples (3-5)
|
||||
- [ ] Integration tutorial
|
||||
- [ ] Migration guide (if applicable)
|
||||
- [ ] Video demo (1-2)
|
||||
|
||||
#### Code Assets
|
||||
- [ ] SDK (if new language)
|
||||
- [ ] Sample application (1-2)
|
||||
- [ ] Code snippets
|
||||
- [ ] Sandbox example
|
||||
|
||||
#### Marketing Assets
|
||||
- [ ] Launch blog post
|
||||
- [ ] Product page update
|
||||
- [ ] Demo video
|
||||
- [ ] Email template
|
||||
- [ ] Social media posts
|
||||
- [ ] Changelog entry (detailed)
|
||||
|
||||
#### Sales Enablement
|
||||
- [ ] Feature overview (1-pager)
|
||||
- [ ] Demo talking points
|
||||
- [ ] FAQ (10+ questions)
|
||||
- [ ] Competitive comparison
|
||||
|
||||
---
|
||||
|
||||
### Launch Channels
|
||||
|
||||
**Primary:**
|
||||
- Developer blog
|
||||
- Email (targeted segment)
|
||||
- Changelog (featured)
|
||||
- Social media
|
||||
- In-product notification
|
||||
|
||||
**Secondary:**
|
||||
- Developer newsletter
|
||||
- Community forums
|
||||
- YouTube demo
|
||||
- Partner channels (if applicable)
|
||||
|
||||
**Optional:**
|
||||
- Dev.to article
|
||||
- Reddit post (relevant subreddits)
|
||||
- Product Hunt (if major feature)
|
||||
|
||||
---
|
||||
|
||||
### Team & Resources
|
||||
|
||||
**Core Team:**
|
||||
- Product Marketing Lead
|
||||
- Product Manager
|
||||
- Developer Relations
|
||||
- Engineering (docs)
|
||||
- Content Writer
|
||||
|
||||
**Time Commitment:**
|
||||
- PMM: 75% for 4 weeks
|
||||
- PM: 25%
|
||||
- Eng: 10% (docs)
|
||||
- DevRel: 40%
|
||||
|
||||
---
|
||||
|
||||
### Success Metrics (Tier 2)
|
||||
|
||||
**Week 1:**
|
||||
- 2K+ feature adoptions
|
||||
- 1K+ email opens
|
||||
- 50K+ blog views
|
||||
|
||||
**Month 1:**
|
||||
- 5K+ active users
|
||||
- 25%+ engagement rate
|
||||
- NPS > 30
|
||||
|
||||
---
|
||||
|
||||
### Budget (Example)
|
||||
|
||||
| Item | Cost |
|
||||
|------|------|
|
||||
| Video Production | $3K-$8K |
|
||||
| Design Assets | $2K-$5K |
|
||||
| Email Platform | $500 |
|
||||
| Paid Promotion (optional) | $5K-$15K |
|
||||
| **Total** | **$10.5K-$28.5K** |
|
||||
|
||||
---
|
||||
|
||||
## Tier 3: Minor Launch
|
||||
|
||||
### When to Use
|
||||
|
||||
- **Incremental improvements**
|
||||
- **Bug fixes** (significant ones)
|
||||
- **Performance enhancements**
|
||||
- **Small feature** additions
|
||||
- **UI/UX updates**
|
||||
- **Deprecation** notices
|
||||
|
||||
### Characteristics
|
||||
|
||||
**Scope:**
|
||||
- Impacts small segment (<25%)
|
||||
- Minimal revenue impact
|
||||
- No competitive angle
|
||||
- Low external interest
|
||||
- Simple technical change
|
||||
|
||||
**Timeline:** 2-4 weeks
|
||||
|
||||
**Budget:** $1K-$5K
|
||||
|
||||
---
|
||||
|
||||
### Deliverables
|
||||
|
||||
#### Documentation
|
||||
- [ ] Release notes
|
||||
- [ ] Documentation updates
|
||||
- [ ] Changelog entry
|
||||
|
||||
#### Marketing Assets
|
||||
- [ ] Short blog post or announcement
|
||||
- [ ] Email (optional)
|
||||
- [ ] Social media post (single)
|
||||
|
||||
---
|
||||
|
||||
### Launch Channels
|
||||
|
||||
**Primary:**
|
||||
- Changelog
|
||||
- Release notes
|
||||
- Documentation
|
||||
|
||||
**Secondary (optional):**
|
||||
- Short blog post
|
||||
- Email mention
|
||||
- Social media (single post)
|
||||
- In-product notification
|
||||
|
||||
---
|
||||
|
||||
### Team & Resources
|
||||
|
||||
**Minimal Team:**
|
||||
- Product Manager or PMM
|
||||
- Engineering (docs)
|
||||
|
||||
**Time Commitment:**
|
||||
- PM/PMM: 25% for 1 week
|
||||
- Eng: 5% (docs)
|
||||
|
||||
---
|
||||
|
||||
### Success Metrics (Tier 3)
|
||||
|
||||
**Week 1:**
|
||||
- Documentation viewed
|
||||
- Feature adopted by target users
|
||||
- No support spikes
|
||||
|
||||
**Month 1:**
|
||||
- 10-20% of eligible users adopt
|
||||
- Positive sentiment
|
||||
|
||||
---
|
||||
|
||||
### Budget
|
||||
|
||||
Typically < $5K, mostly internal time.
|
||||
|
||||
---
|
||||
|
||||
## Decision Framework
|
||||
|
||||
### Scoring System
|
||||
|
||||
Use the `assess_launch_tier.sh` script or manually score:
|
||||
|
||||
**Score Components:**
|
||||
|
||||
1. **Type of Launch** (0-10 points)
|
||||
- New product/GA: 10
|
||||
- Major version: 8
|
||||
- New feature: 5
|
||||
- Improvement: 2
|
||||
- Bug fix: 0
|
||||
|
||||
2. **User Impact** (0-10 points)
|
||||
- All users (100%): 10
|
||||
- Most users (50-99%): 7
|
||||
- Segment (25-50%): 5
|
||||
- Small segment (<25%): 2
|
||||
- Beta only: 1
|
||||
|
||||
3. **Revenue Impact** (0-10 points)
|
||||
- New revenue stream: 10
|
||||
- Major driver: 7
|
||||
- Moderate: 4
|
||||
- Minor: 2
|
||||
- None: 0
|
||||
|
||||
4. **Competitive Differentiation** (0-8 points)
|
||||
- Industry first: 8
|
||||
- Significant: 6
|
||||
- Some: 4
|
||||
- Parity: 1
|
||||
- None: 0
|
||||
|
||||
5. **Technical Complexity** (0-7 points)
|
||||
- New platform: 7
|
||||
- Significant: 5
|
||||
- Moderate: 3
|
||||
- Simple: 1
|
||||
- Minor: 0
|
||||
|
||||
6. **Documentation Needs** (0-6 points)
|
||||
- Complete new set: 6
|
||||
- Major updates: 5
|
||||
- New guides: 3
|
||||
- Updates: 1
|
||||
- Release notes only: 0
|
||||
|
||||
7. **External Interest** (0-7 points)
|
||||
- High (industry news): 7
|
||||
- Moderate (tech press): 5
|
||||
- Some (community): 3
|
||||
- Low (niche): 1
|
||||
- Minimal: 0
|
||||
|
||||
**Total Score: 0-58**
|
||||
|
||||
**Tier Assignment:**
|
||||
- **40-58:** Tier 1 (Major)
|
||||
- **20-39:** Tier 2 (Standard)
|
||||
- **0-19:** Tier 3 (Minor)
|
||||
|
||||
---
|
||||
|
||||
## Common Scenarios
|
||||
|
||||
### Scenario 1: API GA Launch
|
||||
**Type:** New product
|
||||
**Users:** All (new audience)
|
||||
**Revenue:** New stream
|
||||
**Competitive:** Industry first capability
|
||||
**Technical:** New platform
|
||||
**Docs:** Complete set
|
||||
**Interest:** High
|
||||
|
||||
**Score:** 52 → **Tier 1**
|
||||
|
||||
---
|
||||
|
||||
### Scenario 2: New Language SDK
|
||||
**Type:** New integration
|
||||
**Users:** Segment (e.g., Python devs)
|
||||
**Revenue:** Moderate impact
|
||||
**Competitive:** Parity
|
||||
**Technical:** Moderate
|
||||
**Docs:** New guide
|
||||
**Interest:** Some
|
||||
|
||||
**Score:** 25 → **Tier 2**
|
||||
|
||||
---
|
||||
|
||||
### Scenario 3: Performance Update
|
||||
**Type:** Improvement
|
||||
**Users:** All
|
||||
**Revenue:** None direct
|
||||
**Competitive:** None
|
||||
**Technical:** Simple
|
||||
**Docs:** Updates
|
||||
**Interest:** Low
|
||||
|
||||
**Score:** 12 → **Tier 3**
|
||||
|
||||
---
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Right-Sizing
|
||||
|
||||
**Over-investing (Tier 3 as Tier 1):**
|
||||
- Wastes resources
|
||||
- Confuses users ("This isn't major")
|
||||
- Diminishes future Tier 1 launches
|
||||
|
||||
**Under-investing (Tier 1 as Tier 3):**
|
||||
- Misses opportunity
|
||||
- Poor adoption
|
||||
- Competitive disadvantage
|
||||
|
||||
### Flexibility
|
||||
|
||||
**Adjust tier based on:**
|
||||
- Company stage (early vs. mature)
|
||||
- Market position (leader vs. challenger)
|
||||
- Resources available
|
||||
- Strategic importance
|
||||
|
||||
### Communication
|
||||
|
||||
**Be explicit with stakeholders:**
|
||||
- "This is a Tier 2 launch, so we'll do X but not Y"
|
||||
- Set clear expectations upfront
|
||||
- Document tier decision and reasoning
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
Use launch tiers to:
|
||||
1. **Match effort to impact**
|
||||
2. **Set stakeholder expectations**
|
||||
3. **Allocate resources efficiently**
|
||||
4. **Maintain consistency**
|
||||
5. **Maximize ROI**
|
||||
|
||||
**Remember:** A well-executed Tier 2 launch beats a poorly-executed Tier 1.
|
||||
562
skills/technical-launch-planner/references/metrics_frameworks.md
Normal file
562
skills/technical-launch-planner/references/metrics_frameworks.md
Normal file
@@ -0,0 +1,562 @@
|
||||
# Developer Product Metrics
|
||||
|
||||
Comprehensive guide to measuring success for technical products, developer tools, and APIs.
|
||||
|
||||
---
|
||||
|
||||
## Why Developer Metrics Are Different
|
||||
|
||||
Developer products have unique characteristics:
|
||||
- **High technical barriers** to adoption
|
||||
- **Longer evaluation** periods
|
||||
- **Community-driven** growth
|
||||
- **Usage-based** pricing models
|
||||
- **Quality over quantity** (one great developer > 100 casual users)
|
||||
|
||||
Traditional B2B SaaS metrics don't always apply directly.
|
||||
|
||||
---
|
||||
|
||||
## The Developer Funnel
|
||||
|
||||
```
|
||||
Awareness → Interest → Evaluation → Activation → Engagement → Retention → Monetization
|
||||
```
|
||||
|
||||
Each stage has specific metrics.
|
||||
|
||||
---
|
||||
|
||||
## 1. Awareness Metrics
|
||||
|
||||
### Top-of-Funnel
|
||||
|
||||
**Website Traffic:**
|
||||
- Documentation page views
|
||||
- Landing page visits
|
||||
- Blog traffic
|
||||
- GitHub repository views
|
||||
|
||||
**Search & Discovery:**
|
||||
- Organic search rankings (for key terms)
|
||||
- GitHub stars
|
||||
- Stack Overflow mentions
|
||||
- Social media mentions
|
||||
|
||||
**Community Presence:**
|
||||
- Discord/Slack members
|
||||
- Reddit subscribers
|
||||
- Newsletter subscribers
|
||||
- Conference attendance
|
||||
|
||||
**Targets (vary by company):**
|
||||
- 50K monthly docs views (early stage)
|
||||
- 500K monthly docs views (growth stage)
|
||||
- 1K+ GitHub stars (open source component)
|
||||
|
||||
---
|
||||
|
||||
## 2. Interest Metrics
|
||||
|
||||
### Consideration Stage
|
||||
|
||||
**Engagement:**
|
||||
- Time on documentation
|
||||
- Pages per session
|
||||
- Video views (tutorials)
|
||||
- GitHub README views
|
||||
|
||||
**Content Consumption:**
|
||||
- Blog post reads
|
||||
- Tutorial completion rate
|
||||
- Demo video watch time
|
||||
- Webinar registrations
|
||||
|
||||
**Social Proof:**
|
||||
- Case study views
|
||||
- Customer testimonials read
|
||||
- Comparison page visits
|
||||
|
||||
**Targets:**
|
||||
- 5+ minute average session duration
|
||||
- 4+ pages per session
|
||||
- 50%+ video completion rate
|
||||
|
||||
---
|
||||
|
||||
## 3. Evaluation Metrics
|
||||
|
||||
### Trial/Sandbox Stage
|
||||
|
||||
**Sign-Up:**
|
||||
- Developer sign-ups
|
||||
- API key requests
|
||||
- Sandbox activations
|
||||
- Free tier activations
|
||||
|
||||
**Time to Value:**
|
||||
- **Time to first API call** (target: < 10 minutes)
|
||||
- **Time to "Hello World"** (target: < 15 minutes)
|
||||
- **Time to integration** (target: < 1 hour)
|
||||
|
||||
**Documentation Engagement:**
|
||||
- Getting started guide views
|
||||
- Code sample copies
|
||||
- SDK downloads
|
||||
- Postman collection imports
|
||||
|
||||
**Targets:**
|
||||
- 1K+ sign-ups per month (early stage)
|
||||
- 60% make first API call within 24 hours
|
||||
- 10 minutes median time to first call
|
||||
|
||||
---
|
||||
|
||||
## 4. Activation Metrics
|
||||
|
||||
### First Value Realized
|
||||
|
||||
**Critical Activation Events:**
|
||||
- **First successful API call**
|
||||
- **First integration deployed**
|
||||
- **First production request**
|
||||
- **SDK installed and used**
|
||||
- **Sandbox → production migration**
|
||||
|
||||
**Activation Rate:**
|
||||
```
|
||||
Activation Rate = (Users who complete activation event) / (Total sign-ups)
|
||||
```
|
||||
|
||||
**Depth of Activation:**
|
||||
- Features explored
|
||||
- Endpoints called
|
||||
- SDKs used
|
||||
- Integrations enabled
|
||||
|
||||
**Targets:**
|
||||
- 50-70% activation rate (first API call)
|
||||
- 30-40% activation rate (production deployment)
|
||||
- 80%+ complete getting started guide
|
||||
|
||||
---
|
||||
|
||||
## 5. Engagement Metrics
|
||||
|
||||
### Active Usage
|
||||
|
||||
**Daily/Weekly/Monthly Active Developers (DAD/WAD/MAD):**
|
||||
```
|
||||
DAD = Unique developers making API calls daily
|
||||
WAD = Unique developers active weekly
|
||||
MAD = Unique developers active monthly
|
||||
```
|
||||
|
||||
**Stickiness:**
|
||||
```
|
||||
Stickiness = DAD / MAD
|
||||
```
|
||||
- Target: > 20% (good)
|
||||
- Target: > 40% (excellent)
|
||||
|
||||
**API Usage:**
|
||||
- **Total API calls** per day/week/month
|
||||
- **API calls per developer**
|
||||
- **Endpoints used** per developer
|
||||
- **Error rate** (target: < 1%)
|
||||
|
||||
**Feature Adoption:**
|
||||
- % of developers using key features
|
||||
- Time to feature adoption
|
||||
- Feature depth (how many features per user)
|
||||
|
||||
**Targets:**
|
||||
- 40%+ stickiness (DAD/MAD)
|
||||
- 1K+ API calls per active developer per month
|
||||
- < 1% error rate
|
||||
- 3+ features adopted per developer
|
||||
|
||||
---
|
||||
|
||||
## 6. Retention Metrics
|
||||
|
||||
### Developer Retention
|
||||
|
||||
**Cohort Retention:**
|
||||
```
|
||||
Day 1 Retention = Developers active on Day 1 / Total sign-ups
|
||||
Day 7 Retention = Developers active on Day 7 / Total sign-ups
|
||||
Day 30 Retention = Developers active on Day 30 / Total sign-ups
|
||||
```
|
||||
|
||||
**Typical Developer Product Retention:**
|
||||
- Day 1: 60-70%
|
||||
- Day 7: 30-50%
|
||||
- Day 30: 20-40%
|
||||
- Day 90: 15-30%
|
||||
|
||||
**Why Developer Retention Is Lower:**
|
||||
- Evaluation period (many are just testing)
|
||||
- Project-based usage (finish project, stop using)
|
||||
- This is normal and expected
|
||||
|
||||
**Churn Rate:**
|
||||
```
|
||||
Monthly Churn = Developers who stopped using / Active developers at month start
|
||||
```
|
||||
|
||||
**Resurrection Rate:**
|
||||
```
|
||||
Resurrection = Churned developers who return / Total churned developers
|
||||
```
|
||||
|
||||
**Targets:**
|
||||
- < 5% monthly churn (paid users)
|
||||
- 40%+ Day 7 retention
|
||||
- 25%+ Day 30 retention
|
||||
|
||||
---
|
||||
|
||||
## 7. Monetization Metrics
|
||||
|
||||
### Revenue Metrics
|
||||
|
||||
**Conversion Metrics:**
|
||||
```
|
||||
Free → Paid Conversion Rate = Paid users / Total active users
|
||||
```
|
||||
- Target: 3-10% (varies widely by product)
|
||||
|
||||
**Revenue Metrics:**
|
||||
- **MRR** (Monthly Recurring Revenue)
|
||||
- **ARR** (Annual Recurring Revenue)
|
||||
- **ARPU** (Average Revenue Per User)
|
||||
- **Net Revenue Retention** (NRR)
|
||||
|
||||
**Usage-Based Pricing Metrics:**
|
||||
- **Average API calls per paid user**
|
||||
- **Tier distribution** (how many in each pricing tier)
|
||||
- **Upgrade rate** (free → paid, basic → pro)
|
||||
- **Expansion revenue** (existing customers spending more)
|
||||
|
||||
**Targets:**
|
||||
- 5%+ free-to-paid conversion
|
||||
- 110%+ Net Revenue Retention
|
||||
- $50-$500 ARPU (varies by product)
|
||||
|
||||
---
|
||||
|
||||
## Developer-Specific Metrics
|
||||
|
||||
### Code Quality Metrics
|
||||
|
||||
**SDK Quality:**
|
||||
- **Downloads** per month
|
||||
- **GitHub stars**
|
||||
- **Issues opened** vs. closed
|
||||
- **PR acceptance** rate
|
||||
- **Time to resolve** issues
|
||||
|
||||
**Documentation Quality:**
|
||||
- **Search success** rate (did they find what they needed?)
|
||||
- **Time on page** (too short = unclear, too long = can't find)
|
||||
- **Bounce rate** on docs
|
||||
- **Feedback** (thumbs up/down on docs pages)
|
||||
|
||||
**Targets:**
|
||||
- 90%+ search success rate
|
||||
- < 40% bounce rate on docs
|
||||
- 80%+ positive feedback on docs
|
||||
|
||||
---
|
||||
|
||||
### Developer Experience Metrics
|
||||
|
||||
**Time-Based:**
|
||||
- Time to first API call
|
||||
- Time to production
|
||||
- Time to integrate
|
||||
- Time to debug
|
||||
|
||||
**Friction Points:**
|
||||
- Authentication failures
|
||||
- API errors
|
||||
- SDK install issues
|
||||
- Documentation gaps
|
||||
|
||||
**Support Metrics:**
|
||||
- Support tickets per MAD
|
||||
- Time to first response
|
||||
- Time to resolution
|
||||
- Community forum response time
|
||||
|
||||
**Targets:**
|
||||
- < 5 minutes to first API call
|
||||
- < 1 support ticket per 100 MAD
|
||||
- < 4 hours first response time
|
||||
- 90%+ questions answered by community
|
||||
|
||||
---
|
||||
|
||||
## Developer Satisfaction
|
||||
|
||||
### Net Promoter Score (NPS)
|
||||
|
||||
Survey question: "How likely are you to recommend [product] to other developers?"
|
||||
|
||||
**Scale:** 0-10
|
||||
|
||||
**Calculation:**
|
||||
```
|
||||
NPS = % Promoters (9-10) - % Detractors (0-6)
|
||||
```
|
||||
|
||||
**Developer Product Benchmarks:**
|
||||
- **Excellent:** NPS > 50
|
||||
- **Good:** NPS 30-50
|
||||
- **Needs Work:** NPS < 30
|
||||
|
||||
### Developer Sentiment
|
||||
|
||||
**Qualitative Indicators:**
|
||||
- Social media sentiment
|
||||
- Community forum tone
|
||||
- GitHub issue sentiment
|
||||
- Review site ratings (G2, Capterra)
|
||||
- Stack Overflow sentiment
|
||||
|
||||
**Quantitative Tracking:**
|
||||
- Positive vs. negative mentions
|
||||
- Sentiment score (automated analysis)
|
||||
- Review ratings (1-5 stars)
|
||||
|
||||
---
|
||||
|
||||
## Launch-Specific Metrics
|
||||
|
||||
### Launch Day Metrics
|
||||
|
||||
**Day 1:**
|
||||
- Sign-ups / API keys
|
||||
- First API calls
|
||||
- Documentation views
|
||||
- Blog post views
|
||||
- Social media impressions
|
||||
- Email open rate
|
||||
- Email click rate
|
||||
|
||||
**Targets (Tier 1 launch):**
|
||||
- 5K+ sign-ups
|
||||
- 50%+ activation rate (first call)
|
||||
- 100K+ docs views
|
||||
- 50K+ blog views
|
||||
|
||||
---
|
||||
|
||||
### Week 1 Metrics
|
||||
|
||||
- Total sign-ups
|
||||
- Day 7 retention rate
|
||||
- Active developers
|
||||
- API calls made
|
||||
- Support tickets
|
||||
- Community questions
|
||||
- Social mentions
|
||||
|
||||
**Targets (Tier 1):**
|
||||
- 10K+ total sign-ups
|
||||
- 40%+ Day 7 retention
|
||||
- 5K+ active developers
|
||||
- 1M+ API calls
|
||||
- < 50 support tickets
|
||||
|
||||
---
|
||||
|
||||
### Month 1 Metrics
|
||||
|
||||
- Monthly Active Developers (MAD)
|
||||
- Free → paid conversion
|
||||
- NPS score
|
||||
- Documentation coverage (no major gaps)
|
||||
- Community health
|
||||
- Feature adoption
|
||||
|
||||
**Targets (Tier 1):**
|
||||
- 25K+ MAD
|
||||
- 3-5% paid conversion
|
||||
- NPS > 40
|
||||
- 80%+ positive doc feedback
|
||||
|
||||
---
|
||||
|
||||
## Metrics Dashboard Template
|
||||
|
||||
### Executive Dashboard
|
||||
|
||||
**Adoption:**
|
||||
- Total Developers: [X]
|
||||
- MAD: [X]
|
||||
- Growth Rate: [X%]
|
||||
|
||||
**Engagement:**
|
||||
- DAD/MAD: [X%]
|
||||
- API Calls/Day: [X]
|
||||
- Error Rate: [X%]
|
||||
|
||||
**Retention:**
|
||||
- Day 7: [X%]
|
||||
- Day 30: [X%]
|
||||
- Churn: [X%]
|
||||
|
||||
**Revenue:**
|
||||
- MRR: $[X]
|
||||
- ARPU: $[X]
|
||||
- NRR: [X%]
|
||||
|
||||
**Quality:**
|
||||
- NPS: [X]
|
||||
- Support Tickets/MAD: [X]
|
||||
|
||||
---
|
||||
|
||||
### Product Team Dashboard
|
||||
|
||||
**This Week:**
|
||||
- New Developers: [X]
|
||||
- Activation Rate: [X%]
|
||||
- Features Adopted: [X]
|
||||
- Top API Endpoints: [List]
|
||||
|
||||
**Trends:**
|
||||
- MAD (7-day trend): [Graph]
|
||||
- API Calls (7-day): [Graph]
|
||||
- Error Rate (7-day): [Graph]
|
||||
|
||||
**Health:**
|
||||
- Documentation Gaps: [Count]
|
||||
- Open Issues: [Count]
|
||||
- P0 Bugs: [Count]
|
||||
|
||||
---
|
||||
|
||||
## Metric Collection
|
||||
|
||||
### Where to Track
|
||||
|
||||
**Product Analytics:**
|
||||
- Amplitude
|
||||
- Mixpanel
|
||||
- Heap
|
||||
- PostHog
|
||||
|
||||
**API Analytics:**
|
||||
- Moesif
|
||||
- API metrics (custom)
|
||||
- CloudWatch / Datadog
|
||||
|
||||
**Documentation Analytics:**
|
||||
- Google Analytics
|
||||
- Readme.io analytics
|
||||
- GitBook analytics
|
||||
|
||||
**Developer Feedback:**
|
||||
- Intercom
|
||||
- Zendesk
|
||||
- Community forum analytics
|
||||
- Survey tools (Delighted, SurveyMonkey)
|
||||
|
||||
---
|
||||
|
||||
## Setting Targets
|
||||
|
||||
### Early Stage (0-1 year)
|
||||
|
||||
Focus on **activation** and **engagement**:
|
||||
- Sign-ups: 1K-10K/month
|
||||
- Activation: 50%+
|
||||
- MAD: 500-5K
|
||||
- Day 7 Retention: 30%+
|
||||
|
||||
### Growth Stage (1-3 years)
|
||||
|
||||
Focus on **scale** and **retention**:
|
||||
- Sign-ups: 10K-50K/month
|
||||
- MAD: 10K-100K
|
||||
- Day 30 Retention: 25%+
|
||||
- Free→Paid: 5%+
|
||||
|
||||
### Mature Stage (3+ years)
|
||||
|
||||
Focus on **efficiency** and **expansion**:
|
||||
- MAD: 100K+
|
||||
- NRR: 110%+
|
||||
- ARPU: Increasing
|
||||
- CAC Payback: < 12 months
|
||||
|
||||
---
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
### Vanity Metrics
|
||||
|
||||
**Avoid:**
|
||||
- Total registered users (most are inactive)
|
||||
- Total API calls (could be from one user)
|
||||
- GitHub stars alone (may not use product)
|
||||
|
||||
**Focus on:**
|
||||
- Active users (making API calls)
|
||||
- Retained users (coming back)
|
||||
- Engaged users (using multiple features)
|
||||
|
||||
### Wrong Benchmarks
|
||||
|
||||
Don't compare developer product metrics to:
|
||||
- B2C social apps (much higher DAU/MAU)
|
||||
- Enterprise SaaS (lower volume, higher ACV)
|
||||
- E-commerce (transactional, not sustained use)
|
||||
|
||||
Use developer product benchmarks instead.
|
||||
|
||||
---
|
||||
|
||||
## Summary: Key Metrics to Track
|
||||
|
||||
**Must Track:**
|
||||
1. Monthly Active Developers (MAD)
|
||||
2. Activation Rate (first API call)
|
||||
3. Day 7 & Day 30 Retention
|
||||
4. Stickiness (DAD/MAD)
|
||||
5. API Error Rate
|
||||
6. NPS
|
||||
|
||||
**Should Track:**
|
||||
7. Free → Paid Conversion
|
||||
8. Time to First API Call
|
||||
9. Documentation Effectiveness
|
||||
10. Support Ticket Volume
|
||||
|
||||
**Nice to Have:**
|
||||
11. GitHub Stars/Activity
|
||||
12. Community Engagement
|
||||
13. Social Sentiment
|
||||
14. Feature Adoption Depth
|
||||
|
||||
Start with the must-track metrics, then expand.
|
||||
|
||||
---
|
||||
|
||||
## Developer Metric Formulas
|
||||
|
||||
Quick reference:
|
||||
|
||||
```
|
||||
Activation Rate = Activated Users / Sign-ups
|
||||
Stickiness = DAD / MAD
|
||||
Churn Rate = Users Lost / Total Users
|
||||
NRR = (MRR + Expansion - Churn) / Starting MRR
|
||||
LTV = ARPU / Churn Rate
|
||||
CAC Payback = CAC / (ARPU * Gross Margin)
|
||||
```
|
||||
|
||||
**Remember:** Metrics should drive action, not just reporting. If a metric doesn't change behavior, don't track it.
|
||||
324
skills/technical-launch-planner/scripts/assess_launch_tier.sh
Executable file
324
skills/technical-launch-planner/scripts/assess_launch_tier.sh
Executable file
@@ -0,0 +1,324 @@
|
||||
#!/bin/bash
|
||||
|
||||
# Technical Launch Tier Assessment
|
||||
# Helps determine the appropriate launch tier based on scope and impact
|
||||
|
||||
set -e
|
||||
|
||||
# Colors
|
||||
GREEN='\033[0;32m'
|
||||
BLUE='\033[0;34m'
|
||||
YELLOW='\033[1;33m'
|
||||
RED='\033[0;31m'
|
||||
CYAN='\033[0;36m'
|
||||
NC='\033[0m' # No Color
|
||||
|
||||
echo -e "${BLUE}╔════════════════════════════════════════════════╗${NC}"
|
||||
echo -e "${BLUE}║ Technical Launch Tier Assessment ║${NC}"
|
||||
echo -e "${BLUE}╚════════════════════════════════════════════════╝${NC}"
|
||||
echo ""
|
||||
echo -e "${CYAN}This assessment will help determine your launch tier.${NC}"
|
||||
echo ""
|
||||
|
||||
# Scoring system
|
||||
SCORE=0
|
||||
|
||||
# Question 1: What are you launching?
|
||||
echo -e "${YELLOW}Question 1: What are you launching?${NC}"
|
||||
echo " 1) New product/platform (GA)"
|
||||
echo " 2) Major version update (v2.0, v3.0)"
|
||||
echo " 3) New feature/integration"
|
||||
echo " 4) Enhancement/improvement"
|
||||
echo " 5) Bug fix/patch"
|
||||
echo ""
|
||||
read -p "Your answer (1-5): " Q1
|
||||
|
||||
case $Q1 in
|
||||
1) SCORE=$((SCORE + 10));;
|
||||
2) SCORE=$((SCORE + 8));;
|
||||
3) SCORE=$((SCORE + 5));;
|
||||
4) SCORE=$((SCORE + 2));;
|
||||
5) SCORE=$((SCORE + 0));;
|
||||
esac
|
||||
echo ""
|
||||
|
||||
# Question 2: Target audience size
|
||||
echo -e "${YELLOW}Question 2: How many developers/users will this impact?${NC}"
|
||||
echo " 1) All users (100%)"
|
||||
echo " 2) Most users (50-99%)"
|
||||
echo " 3) Segment of users (25-50%)"
|
||||
echo " 4) Small segment (<25%)"
|
||||
echo " 5) Beta/limited group"
|
||||
echo ""
|
||||
read -p "Your answer (1-5): " Q2
|
||||
|
||||
case $Q2 in
|
||||
1) SCORE=$((SCORE + 10));;
|
||||
2) SCORE=$((SCORE + 7));;
|
||||
3) SCORE=$((SCORE + 5));;
|
||||
4) SCORE=$((SCORE + 2));;
|
||||
5) SCORE=$((SCORE + 1));;
|
||||
esac
|
||||
echo ""
|
||||
|
||||
# Question 3: Revenue impact
|
||||
echo -e "${YELLOW}Question 3: What's the revenue/business impact?${NC}"
|
||||
echo " 1) New revenue stream"
|
||||
echo " 2) Major revenue driver"
|
||||
echo " 3) Moderate impact"
|
||||
echo " 4) Minor impact"
|
||||
echo " 5) No direct revenue impact"
|
||||
echo ""
|
||||
read -p "Your answer (1-5): " Q3
|
||||
|
||||
case $Q3 in
|
||||
1) SCORE=$((SCORE + 10));;
|
||||
2) SCORE=$((SCORE + 7));;
|
||||
3) SCORE=$((SCORE + 4));;
|
||||
4) SCORE=$((SCORE + 2));;
|
||||
5) SCORE=$((SCORE + 0));;
|
||||
esac
|
||||
echo ""
|
||||
|
||||
# Question 4: Competitive differentiation
|
||||
echo -e "${YELLOW}Question 4: Is this competitively differentiated?${NC}"
|
||||
echo " 1) Industry first / unique capability"
|
||||
echo " 2) Significant differentiation"
|
||||
echo " 3) Some differentiation"
|
||||
echo " 4) Parity feature"
|
||||
echo " 5) No competitive angle"
|
||||
echo ""
|
||||
read -p "Your answer (1-5): " Q4
|
||||
|
||||
case $Q4 in
|
||||
1) SCORE=$((SCORE + 8));;
|
||||
2) SCORE=$((SCORE + 6));;
|
||||
3) SCORE=$((SCORE + 4));;
|
||||
4) SCORE=$((SCORE + 1));;
|
||||
5) SCORE=$((SCORE + 0));;
|
||||
esac
|
||||
echo ""
|
||||
|
||||
# Question 5: Technical complexity
|
||||
echo -e "${YELLOW}Question 5: How complex is this technically?${NC}"
|
||||
echo " 1) New platform/architecture"
|
||||
echo " 2) Significant technical undertaking"
|
||||
echo " 3) Moderate complexity"
|
||||
echo " 4) Simple feature"
|
||||
echo " 5) Minor change"
|
||||
echo ""
|
||||
read -p "Your answer (1-5): " Q5
|
||||
|
||||
case $Q5 in
|
||||
1) SCORE=$((SCORE + 7));;
|
||||
2) SCORE=$((SCORE + 5));;
|
||||
3) SCORE=$((SCORE + 3));;
|
||||
4) SCORE=$((SCORE + 1));;
|
||||
5) SCORE=$((SCORE + 0));;
|
||||
esac
|
||||
echo ""
|
||||
|
||||
# Question 6: Documentation/enablement needed
|
||||
echo -e "${YELLOW}Question 6: What documentation/enablement is required?${NC}"
|
||||
echo " 1) Complete new documentation set + SDKs"
|
||||
echo " 2) Major documentation updates + samples"
|
||||
echo " 3) New guides + code samples"
|
||||
echo " 4) Documentation updates"
|
||||
echo " 5) Release notes only"
|
||||
echo ""
|
||||
read -p "Your answer (1-5): " Q6
|
||||
|
||||
case $Q6 in
|
||||
1) SCORE=$((SCORE + 6));;
|
||||
2) SCORE=$((SCORE + 5));;
|
||||
3) SCORE=$((SCORE + 3));;
|
||||
4) SCORE=$((SCORE + 1));;
|
||||
5) SCORE=$((SCORE + 0));;
|
||||
esac
|
||||
echo ""
|
||||
|
||||
# Question 7: External interest
|
||||
echo -e "${YELLOW}Question 7: Expected external interest (press, analysts, community)?${NC}"
|
||||
echo " 1) High (industry news)"
|
||||
echo " 2) Moderate (tech press interest)"
|
||||
echo " 3) Some (developer community)"
|
||||
echo " 4) Low (niche interest)"
|
||||
echo " 5) Minimal (internal mainly)"
|
||||
echo ""
|
||||
read -p "Your answer (1-5): " Q7
|
||||
|
||||
case $Q7 in
|
||||
1) SCORE=$((SCORE + 7));;
|
||||
2) SCORE=$((SCORE + 5));;
|
||||
3) SCORE=$((SCORE + 3));;
|
||||
4) SCORE=$((SCORE + 1));;
|
||||
5) SCORE=$((SCORE + 0));;
|
||||
esac
|
||||
echo ""
|
||||
|
||||
# Calculate tier
|
||||
echo -e "${BLUE}═══════════════════════════════════════════════${NC}"
|
||||
echo -e "${CYAN}Analyzing your responses...${NC}"
|
||||
echo ""
|
||||
|
||||
sleep 1
|
||||
|
||||
# Determine tier based on score
|
||||
if [ $SCORE -ge 40 ]; then
|
||||
TIER="Tier 1"
|
||||
COLOR=$RED
|
||||
TIMELINE="12-16 weeks"
|
||||
INVESTMENT="Full GTM"
|
||||
elif [ $SCORE -ge 20 ]; then
|
||||
TIER="Tier 2"
|
||||
COLOR=$YELLOW
|
||||
TIMELINE="6-8 weeks"
|
||||
INVESTMENT="Selective GTM"
|
||||
else
|
||||
TIER="Tier 3"
|
||||
COLOR=$GREEN
|
||||
TIMELINE="2-4 weeks"
|
||||
INVESTMENT="Minimal GTM"
|
||||
fi
|
||||
|
||||
# Display results
|
||||
echo -e "${BLUE}╔════════════════════════════════════════════════╗${NC}"
|
||||
echo -e "${BLUE}║ Assessment Results ║${NC}"
|
||||
echo -e "${BLUE}╚════════════════════════════════════════════════╝${NC}"
|
||||
echo ""
|
||||
echo -e "Your Score: ${CYAN}$SCORE / 58${NC}"
|
||||
echo -e "Launch Tier: ${COLOR}$TIER${NC}"
|
||||
echo -e "Timeline: ${CYAN}$TIMELINE${NC}"
|
||||
echo -e "Investment: ${CYAN}$INVESTMENT${NC}"
|
||||
echo ""
|
||||
|
||||
# Tier-specific recommendations
|
||||
echo -e "${BLUE}═══════════════════════════════════════════════${NC}"
|
||||
echo -e "${COLOR}$TIER Recommendations:${NC}"
|
||||
echo ""
|
||||
|
||||
if [ "$TIER" = "Tier 1" ]; then
|
||||
echo -e "${YELLOW}Major Launch - Full GTM Treatment${NC}"
|
||||
echo ""
|
||||
echo "Required:"
|
||||
echo " ✓ Complete documentation set"
|
||||
echo " ✓ Multiple SDKs/client libraries"
|
||||
echo " ✓ Sample applications"
|
||||
echo " ✓ Video tutorials"
|
||||
echo " ✓ Interactive demos/playground"
|
||||
echo " ✓ Press release"
|
||||
echo " ✓ Launch event/webinar"
|
||||
echo " ✓ Partner coordination"
|
||||
echo " ✓ Paid promotion"
|
||||
echo " ✓ Analyst briefings"
|
||||
echo ""
|
||||
echo "Channels:"
|
||||
echo " • Developer blog (launch post)"
|
||||
echo " • Email (entire developer list)"
|
||||
echo " • Social media (coordinated campaign)"
|
||||
echo " • Hacker News / Reddit"
|
||||
echo " • Tech press outreach"
|
||||
echo " • Developer communities"
|
||||
echo " • Conference talks"
|
||||
echo ""
|
||||
echo "Team involvement:"
|
||||
echo " • Product Marketing (lead)"
|
||||
echo " • Product Management"
|
||||
echo " • Developer Relations"
|
||||
echo " • Engineering"
|
||||
echo " • Sales Engineering"
|
||||
echo " • Partners"
|
||||
echo " • PR/Comms"
|
||||
echo ""
|
||||
|
||||
elif [ "$TIER" = "Tier 2" ]; then
|
||||
echo -e "${YELLOW}Standard Launch - Selective GTM${NC}"
|
||||
echo ""
|
||||
echo "Required:"
|
||||
echo " ✓ Feature documentation"
|
||||
echo " ✓ Code samples"
|
||||
echo " ✓ Blog post"
|
||||
echo " ✓ Demo video"
|
||||
echo " ✓ Email announcement"
|
||||
echo " ✓ Updated API reference"
|
||||
echo ""
|
||||
echo "Channels:"
|
||||
echo " • Developer blog"
|
||||
echo " • Email (targeted segment)"
|
||||
echo " • Social media"
|
||||
echo " • Changelog"
|
||||
echo " • Developer newsletter"
|
||||
echo " • Relevant communities"
|
||||
echo ""
|
||||
echo "Team involvement:"
|
||||
echo " • Product Marketing (lead)"
|
||||
echo " • Developer Relations"
|
||||
echo " • Product Management"
|
||||
echo " • Engineering (docs)"
|
||||
echo ""
|
||||
|
||||
else
|
||||
echo -e "${GREEN}Minor Launch - Documentation Focus${NC}"
|
||||
echo ""
|
||||
echo "Required:"
|
||||
echo " ✓ Release notes"
|
||||
echo " ✓ Updated documentation"
|
||||
echo " ✓ Changelog entry"
|
||||
echo " ✓ In-app notification (if applicable)"
|
||||
echo ""
|
||||
echo "Channels:"
|
||||
echo " • Changelog"
|
||||
echo " • Documentation"
|
||||
echo " • Social media (single post)"
|
||||
echo " • Email (if significant)"
|
||||
echo ""
|
||||
echo "Team involvement:"
|
||||
echo " • Product Marketing or PM"
|
||||
echo " • Engineering (docs)"
|
||||
echo ""
|
||||
fi
|
||||
|
||||
echo -e "${BLUE}═══════════════════════════════════════════════${NC}"
|
||||
echo ""
|
||||
|
||||
# Next steps
|
||||
echo -e "${CYAN}Next Steps:${NC}"
|
||||
echo ""
|
||||
echo "1. Generate detailed launch plan:"
|
||||
echo -e " ${YELLOW}scripts/generate_launch_plan.sh${NC}"
|
||||
echo ""
|
||||
echo "2. Review tier framework:"
|
||||
echo -e " ${YELLOW}cat references/launch_tiers.md${NC}"
|
||||
echo ""
|
||||
echo "3. Check developer enablement checklist:"
|
||||
echo -e " ${YELLOW}cat references/developer_enablement.md${NC}"
|
||||
echo ""
|
||||
|
||||
# Save results
|
||||
read -p "Save results to file? (y/n): " SAVE
|
||||
if [[ "$SAVE" =~ ^[Yy]$ ]]; then
|
||||
OUTPUT_FILE="launch_assessment_$(date +%Y%m%d_%H%M%S).txt"
|
||||
{
|
||||
echo "Technical Launch Tier Assessment"
|
||||
echo "Date: $(date)"
|
||||
echo ""
|
||||
echo "Score: $SCORE / 58"
|
||||
echo "Tier: $TIER"
|
||||
echo "Timeline: $TIMELINE"
|
||||
echo "Investment: $INVESTMENT"
|
||||
echo ""
|
||||
echo "Responses:"
|
||||
echo "Q1: $Q1"
|
||||
echo "Q2: $Q2"
|
||||
echo "Q3: $Q3"
|
||||
echo "Q4: $Q4"
|
||||
echo "Q5: $Q5"
|
||||
echo "Q6: $Q6"
|
||||
echo "Q7: $Q7"
|
||||
} > "$OUTPUT_FILE"
|
||||
|
||||
echo -e "${GREEN}✓ Results saved to: $OUTPUT_FILE${NC}"
|
||||
fi
|
||||
|
||||
echo ""
|
||||
echo -e "${GREEN}✓ Assessment complete!${NC}"
|
||||
465
skills/technical-launch-planner/scripts/generate_launch_plan.sh
Executable file
465
skills/technical-launch-planner/scripts/generate_launch_plan.sh
Executable file
@@ -0,0 +1,465 @@
|
||||
#!/bin/bash
|
||||
|
||||
# Technical Launch Plan Generator
|
||||
# Creates comprehensive launch plan document
|
||||
|
||||
set -e
|
||||
|
||||
# Colors
|
||||
GREEN='\033[0;32m'
|
||||
BLUE='\033[0;34m'
|
||||
YELLOW='\033[1;33m'
|
||||
CYAN='\033[0;36m'
|
||||
NC='\033[0m'
|
||||
|
||||
echo -e "${BLUE}╔═══════════════════════════════════════════════╗${NC}"
|
||||
echo -e "${BLUE}║ Technical Launch Plan Generator ║${NC}"
|
||||
echo -e "${BLUE}╚═══════════════════════════════════════════════╝${NC}"
|
||||
echo ""
|
||||
|
||||
# Gather information
|
||||
echo -e "${YELLOW}Product/Feature Information${NC}"
|
||||
echo ""
|
||||
read -p "Product/Feature Name: " PRODUCT_NAME
|
||||
read -p "Launch Date (YYYY-MM-DD): " LAUNCH_DATE
|
||||
read -p "Launch Tier (1/2/3): " TIER
|
||||
read -p "One-line Description: " DESCRIPTION
|
||||
read -p "Target Audience (e.g., Backend developers, DevOps): " AUDIENCE
|
||||
|
||||
echo ""
|
||||
OUTPUT_FILE="${PRODUCT_NAME// /_}_launch_plan.md"
|
||||
|
||||
# Generate plan
|
||||
cat > "$OUTPUT_FILE" << EOF
|
||||
# Technical Launch Plan: $PRODUCT_NAME
|
||||
|
||||
**Launch Date:** $LAUNCH_DATE
|
||||
**Launch Tier:** Tier $TIER
|
||||
**Owner:** $(whoami)
|
||||
**Last Updated:** $(date +%Y-%m-%d)
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
### What We're Launching
|
||||
|
||||
$DESCRIPTION
|
||||
|
||||
### Target Audience
|
||||
|
||||
$AUDIENCE
|
||||
|
||||
### Launch Tier: Tier $TIER
|
||||
|
||||
EOF
|
||||
|
||||
# Add tier-specific details
|
||||
if [ "$TIER" = "1" ]; then
|
||||
cat >> "$OUTPUT_FILE" << 'EOF'
|
||||
**Major Launch** - Full GTM treatment, 12-16 week timeline
|
||||
|
||||
### Success Criteria
|
||||
|
||||
- [ ] [Define target adoption metric]
|
||||
- [ ] [Define engagement metric]
|
||||
- [ ] [Define business/revenue metric]
|
||||
|
||||
---
|
||||
|
||||
## Timeline
|
||||
|
||||
### T-12 weeks: Planning Phase
|
||||
|
||||
**Week of [Date]**
|
||||
|
||||
- [ ] Launch tier confirmed
|
||||
- [ ] Stakeholder kickoff meeting
|
||||
- [ ] Success metrics defined
|
||||
- [ ] Budget approved
|
||||
- [ ] Project plan created
|
||||
|
||||
### T-8 weeks: Build Phase Starts
|
||||
|
||||
**Week of [Date]**
|
||||
|
||||
- [ ] Documentation outline complete
|
||||
- [ ] SDK development started
|
||||
- [ ] Marketing brief created
|
||||
- [ ] Demo environment setup
|
||||
- [ ] Beta customers identified
|
||||
|
||||
### T-6 weeks: Content Creation
|
||||
|
||||
**Week of [Date]**
|
||||
|
||||
- [ ] Getting started guide (first draft)
|
||||
- [ ] API reference complete
|
||||
- [ ] Sample apps in development
|
||||
- [ ] Blog post (first draft)
|
||||
- [ ] Demo video script
|
||||
|
||||
### T-4 weeks: Review & Refinement
|
||||
|
||||
**Week of [Date]**
|
||||
|
||||
- [ ] All docs reviewed by engineering
|
||||
- [ ] SDKs in beta testing
|
||||
- [ ] Demo video recorded
|
||||
- [ ] Sales enablement created
|
||||
- [ ] Press release draft
|
||||
|
||||
### T-2 weeks: Final Prep
|
||||
|
||||
**Week of [Date]**
|
||||
|
||||
- [ ] All content finalized
|
||||
- [ ] Internal enablement complete
|
||||
- [ ] Launch email scheduled
|
||||
- [ ] Social media calendar
|
||||
- [ ] Monitoring/analytics ready
|
||||
|
||||
### Launch Week
|
||||
|
||||
**Week of [Date]**
|
||||
|
||||
- [ ] Documentation published
|
||||
- [ ] SDKs released
|
||||
- [ ] Blog post live
|
||||
- [ ] Email sent
|
||||
- [ ] Social campaign
|
||||
- [ ] PR outreach
|
||||
- [ ] Launch event
|
||||
|
||||
### Post-Launch
|
||||
|
||||
**Weeks 1-4**
|
||||
|
||||
- [ ] Daily metrics monitoring
|
||||
- [ ] Community engagement
|
||||
- [ ] Follow-up content
|
||||
- [ ] Feedback synthesis
|
||||
- [ ] Launch retrospective
|
||||
|
||||
---
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Documentation
|
||||
|
||||
- [ ] Getting started guide
|
||||
- [ ] API reference
|
||||
- [ ] Integration guides
|
||||
- [ ] Migration guide (if applicable)
|
||||
- [ ] Troubleshooting FAQ
|
||||
- [ ] Video tutorials
|
||||
|
||||
### Code Assets
|
||||
|
||||
- [ ] SDK: Python
|
||||
- [ ] SDK: JavaScript/Node
|
||||
- [ ] SDK: [Other language]
|
||||
- [ ] Sample application: [Type]
|
||||
- [ ] Sample application: [Type]
|
||||
- [ ] Code snippets library
|
||||
- [ ] Interactive playground
|
||||
|
||||
### Marketing Assets
|
||||
|
||||
- [ ] Launch blog post
|
||||
- [ ] Demo video
|
||||
- [ ] Product page
|
||||
- [ ] Email template
|
||||
- [ ] Social media posts
|
||||
- [ ] Press release
|
||||
- [ ] Infographic/diagram
|
||||
|
||||
### Sales Enablement
|
||||
|
||||
- [ ] Technical battlecard
|
||||
- [ ] Demo script
|
||||
- [ ] FAQ/objection handling
|
||||
- [ ] Pricing materials
|
||||
- [ ] Customer deck
|
||||
|
||||
---
|
||||
|
||||
## Stakeholders & Owners
|
||||
|
||||
| Area | Owner | Status |
|
||||
|------|-------|--------|
|
||||
| Product Marketing | [Name] | ✓ |
|
||||
| Product Management | [Name] | Pending |
|
||||
| Engineering | [Name] | Pending |
|
||||
| Developer Relations | [Name] | Pending |
|
||||
| Sales Engineering | [Name] | Pending |
|
||||
| PR/Communications | [Name] | Pending |
|
||||
| Partners | [Name] | Pending |
|
||||
|
||||
---
|
||||
|
||||
## Launch Channels
|
||||
|
||||
### Primary
|
||||
|
||||
- [ ] Developer Documentation
|
||||
- [ ] Product Blog
|
||||
- [ ] Email (Developer List)
|
||||
- [ ] Social Media
|
||||
- [ ] Changelog
|
||||
|
||||
### Secondary
|
||||
|
||||
- [ ] Hacker News
|
||||
- [ ] Reddit (r/programming, r/[relevant])
|
||||
- [ ] Dev.to
|
||||
- [ ] Product Hunt
|
||||
- [ ] YouTube
|
||||
|
||||
### Tertiary
|
||||
|
||||
- [ ] Tech Press
|
||||
- [ ] Podcasts
|
||||
- [ ] Webinars
|
||||
- [ ] Conferences
|
||||
- [ ] Community Forums
|
||||
|
||||
EOF
|
||||
|
||||
elif [ "$TIER" = "2" ]; then
|
||||
cat >> "$OUTPUT_FILE" << 'EOF'
|
||||
**Standard Launch** - Selective GTM, 6-8 week timeline
|
||||
|
||||
### Success Criteria
|
||||
|
||||
- [ ] [Define adoption target]
|
||||
- [ ] [Define engagement metric]
|
||||
|
||||
---
|
||||
|
||||
## Timeline
|
||||
|
||||
### T-6 weeks: Planning & Build
|
||||
|
||||
- [ ] Feature spec finalized
|
||||
- [ ] Documentation started
|
||||
- [ ] Marketing brief created
|
||||
|
||||
### T-4 weeks: Content Creation
|
||||
|
||||
- [ ] Feature docs complete
|
||||
- [ ] Code samples created
|
||||
- [ ] Blog post drafted
|
||||
- [ ] Demo video recorded
|
||||
|
||||
### T-2 weeks: Review
|
||||
|
||||
- [ ] Engineering review complete
|
||||
- [ ] Content finalized
|
||||
- [ ] Email scheduled
|
||||
|
||||
### Launch Week
|
||||
|
||||
- [ ] Documentation published
|
||||
- [ ] Blog post live
|
||||
- [ ] Email sent
|
||||
- [ ] Social posts
|
||||
|
||||
### Post-Launch (Weeks 1-2)
|
||||
|
||||
- [ ] Metrics monitoring
|
||||
- [ ] Community Q&A
|
||||
- [ ] Follow-up content
|
||||
|
||||
---
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Documentation
|
||||
|
||||
- [ ] Feature guide
|
||||
- [ ] API updates
|
||||
- [ ] Code samples (3+)
|
||||
- [ ] Integration guide
|
||||
|
||||
### Marketing
|
||||
|
||||
- [ ] Blog post
|
||||
- [ ] Demo video
|
||||
- [ ] Email announcement
|
||||
- [ ] Social posts
|
||||
|
||||
### Sales Enablement
|
||||
|
||||
- [ ] Feature overview
|
||||
- [ ] Demo talking points
|
||||
|
||||
EOF
|
||||
|
||||
else
|
||||
cat >> "$OUTPUT_FILE" << 'EOF'
|
||||
**Minor Launch** - Minimal GTM, 2-4 week timeline
|
||||
|
||||
### Success Criteria
|
||||
|
||||
- [ ] Documentation updated
|
||||
- [ ] Users notified
|
||||
|
||||
---
|
||||
|
||||
## Timeline
|
||||
|
||||
### T-2 weeks: Prep
|
||||
|
||||
- [ ] Release notes drafted
|
||||
- [ ] Documentation updated
|
||||
|
||||
### Launch Week
|
||||
|
||||
- [ ] Release notes published
|
||||
- [ ] Changelog updated
|
||||
- [ ] Notification sent
|
||||
|
||||
---
|
||||
|
||||
## Deliverables
|
||||
|
||||
- [ ] Release notes
|
||||
- [ ] Updated documentation
|
||||
- [ ] Changelog entry
|
||||
- [ ] In-app notification (if applicable)
|
||||
|
||||
EOF
|
||||
fi
|
||||
|
||||
# Add common sections
|
||||
cat >> "$OUTPUT_FILE" << 'EOF'
|
||||
|
||||
---
|
||||
|
||||
## Success Metrics
|
||||
|
||||
### Activation Metrics
|
||||
|
||||
- **Metric:** [e.g., API key created]
|
||||
- **Target:** [e.g., 1000 in Week 1]
|
||||
- **Measurement:** [Dashboard link]
|
||||
|
||||
### Engagement Metrics
|
||||
|
||||
- **Metric:** [e.g., First API call made]
|
||||
- **Target:** [e.g., 60% activation rate]
|
||||
- **Measurement:** [Analytics]
|
||||
|
||||
### Retention Metrics
|
||||
|
||||
- **Metric:** [e.g., Day 7 retention]
|
||||
- **Target:** [e.g., 40%]
|
||||
- **Measurement:** [Cohort analysis]
|
||||
|
||||
### Business Metrics
|
||||
|
||||
- **Metric:** [e.g., Paid conversions]
|
||||
- **Target:** [e.g., 5%]
|
||||
- **Measurement:** [Revenue dashboard]
|
||||
|
||||
---
|
||||
|
||||
## Risks & Mitigation
|
||||
|
||||
| Risk | Impact | Probability | Mitigation |
|
||||
|------|--------|------------|------------|
|
||||
| Documentation not ready | High | Medium | Start docs 2 weeks earlier |
|
||||
| [Add risks] | | | |
|
||||
|
||||
---
|
||||
|
||||
## Budget
|
||||
|
||||
| Item | Cost | Owner |
|
||||
|------|------|-------|
|
||||
| [e.g., PR agency] | $[amount] | [Name] |
|
||||
| [e.g., Demo production] | $[amount] | [Name] |
|
||||
| **Total** | **$[total]** | |
|
||||
|
||||
---
|
||||
|
||||
## Post-Launch Plan
|
||||
|
||||
### Week 1
|
||||
- Daily metrics check
|
||||
- Community Q&A
|
||||
- Bug triage
|
||||
|
||||
### Week 2-4
|
||||
- Follow-up blog posts
|
||||
- Customer interviews
|
||||
- Documentation refinements
|
||||
|
||||
### Month 2
|
||||
- Case study development
|
||||
- Webinar/workshop
|
||||
- Integration showcases
|
||||
|
||||
---
|
||||
|
||||
## Launch Day Playbook
|
||||
|
||||
### Pre-Launch (Day Before)
|
||||
- [ ] All assets staged
|
||||
- [ ] Team briefed
|
||||
- [ ] Monitoring ready
|
||||
|
||||
### Launch Day Morning (9 AM)
|
||||
- [ ] Publish documentation
|
||||
- [ ] Release packages/SDKs
|
||||
- [ ] Deploy blog post
|
||||
- [ ] Send email
|
||||
- [ ] Post to social
|
||||
|
||||
### Midday (12 PM)
|
||||
- [ ] Monitor metrics
|
||||
- [ ] Respond to questions
|
||||
- [ ] Share to communities
|
||||
|
||||
### Afternoon (3 PM)
|
||||
- [ ] Post to HN/Reddit (if Tier 1)
|
||||
- [ ] Dev advocate content
|
||||
- [ ] Partner announcements
|
||||
|
||||
### End of Day
|
||||
- [ ] Day 1 report
|
||||
- [ ] Team debrief
|
||||
- [ ] Issue triage
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
[Add any additional notes, context, or decisions]
|
||||
|
||||
---
|
||||
|
||||
## Appendix
|
||||
|
||||
### Links
|
||||
- [Project spec]
|
||||
- [Design doc]
|
||||
- [Marketing brief]
|
||||
- [Asset folder]
|
||||
|
||||
EOF
|
||||
|
||||
echo -e "${GREEN}✓ Launch plan generated!${NC}"
|
||||
echo ""
|
||||
echo -e "Output: ${CYAN}$OUTPUT_FILE${NC}"
|
||||
echo ""
|
||||
echo -e "${YELLOW}Next steps:${NC}"
|
||||
echo "1. Review and customize the plan"
|
||||
echo "2. Fill in specific names, dates, and metrics"
|
||||
echo "3. Share with stakeholders for review"
|
||||
echo "4. Use as living document throughout launch"
|
||||
echo ""
|
||||
echo -e "${CYAN}Validate readiness before launch:${NC}"
|
||||
echo " scripts/validate_readiness.sh"
|
||||
echo ""
|
||||
158
skills/technical-launch-planner/scripts/validate_readiness.sh
Executable file
158
skills/technical-launch-planner/scripts/validate_readiness.sh
Executable file
@@ -0,0 +1,158 @@
|
||||
#!/bin/bash
|
||||
|
||||
# Launch Readiness Validator
|
||||
# Checks if technical launch is ready
|
||||
|
||||
set -e
|
||||
|
||||
# Colors
|
||||
GREEN='\033[0;32m'
|
||||
BLUE='\033[0;34m'
|
||||
YELLOW='\033[1;33m'
|
||||
RED='\033[0;31m'
|
||||
CYAN='\033[0;36m'
|
||||
NC='\033[0m'
|
||||
|
||||
echo -e "${BLUE}╔═══════════════════════════════════════════════╗${NC}"
|
||||
echo -e "${BLUE}║ Technical Launch Readiness Check ║${NC}"
|
||||
echo -e "${BLUE}╚═══════════════════════════════════════════════╝${NC}"
|
||||
echo ""
|
||||
|
||||
# Counters
|
||||
PASSED=0
|
||||
FAILED=0
|
||||
WARNINGS=0
|
||||
|
||||
# Helper functions
|
||||
check_yes_no() {
|
||||
local question="$1"
|
||||
local critical="$2"
|
||||
|
||||
read -p "$question (y/n): " answer
|
||||
if [[ "$answer" =~ ^[Yy]$ ]]; then
|
||||
echo -e " ${GREEN}✓${NC} Pass"
|
||||
((PASSED++))
|
||||
return 0
|
||||
else
|
||||
if [ "$critical" = "true" ]; then
|
||||
echo -e " ${RED}✗${NC} FAIL (Critical)"
|
||||
((FAILED++))
|
||||
else
|
||||
echo -e " ${YELLOW}⚠${NC} Warning"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
return 1
|
||||
fi
|
||||
}
|
||||
|
||||
# Documentation Check
|
||||
echo -e "${CYAN}━━━ Documentation ━━━${NC}"
|
||||
echo ""
|
||||
|
||||
check_yes_no "Getting started guide complete and reviewed?" true
|
||||
check_yes_no "API reference up to date?" true
|
||||
check_yes_no "At least 3 code samples ready?" true
|
||||
check_yes_no "Integration guide written?" false
|
||||
check_yes_no "Migration guide (if needed)?" false
|
||||
check_yes_no "Troubleshooting FAQ added?" false
|
||||
|
||||
echo ""
|
||||
|
||||
# Code Assets
|
||||
echo -e "${CYAN}━━━ Code Assets ━━━${NC}"
|
||||
echo ""
|
||||
|
||||
check_yes_no "SDKs built and tested?" false
|
||||
check_yes_no "Sample applications functional?" false
|
||||
check_yes_no "Interactive demo/playground ready?" false
|
||||
check_yes_no "Code snippets library created?" false
|
||||
|
||||
echo ""
|
||||
|
||||
# Technical Infrastructure
|
||||
echo -e "${CYAN}━━━ Technical Infrastructure ━━━${NC}"
|
||||
echo ""
|
||||
|
||||
check_yes_no "Production environment tested?" true
|
||||
check_yes_no "Monitoring/analytics instrumented?" true
|
||||
check_yes_no "Error tracking configured?" true
|
||||
check_yes_no "Rate limiting verified?" false
|
||||
check_yes_no "Load testing completed?" false
|
||||
|
||||
echo ""
|
||||
|
||||
# Marketing Assets
|
||||
echo -e "${CYAN}━━━ Marketing Assets ━━━${NC}"
|
||||
echo ""
|
||||
|
||||
check_yes_no "Launch blog post written and reviewed?" true
|
||||
check_yes_no "Demo video recorded?" false
|
||||
check_yes_no "Email template created?" true
|
||||
check_yes_no "Social media posts scheduled?" true
|
||||
check_yes_no "Product page updated?" true
|
||||
|
||||
echo ""
|
||||
|
||||
# Sales Enablement
|
||||
echo -e "${CYAN}━━━ Sales Enablement ━━━${NC}"
|
||||
echo ""
|
||||
|
||||
check_yes_no "Sales team briefed?" false
|
||||
check_yes_no "Demo script prepared?" false
|
||||
check_yes_no "FAQ/objections documented?" false
|
||||
check_yes_no "Pricing materials ready?" false
|
||||
|
||||
echo ""
|
||||
|
||||
# Team Readiness
|
||||
echo -e "${CYAN}━━━ Team Readiness ━━━${NC}"
|
||||
echo ""
|
||||
|
||||
check_yes_no "Support team trained?" true
|
||||
check_yes_no "On-call rotation set?" true
|
||||
check_yes_no "Escalation path defined?" true
|
||||
check_yes_no "Launch day roles assigned?" true
|
||||
|
||||
echo ""
|
||||
|
||||
# Final Checks
|
||||
echo -e "${CYAN}━━━ Final Checks ━━━${NC}"
|
||||
echo ""
|
||||
|
||||
check_yes_no "All stakeholders approved?" true
|
||||
check_yes_no "Legal/compliance review (if needed)?" true
|
||||
check_yes_no "Rollback plan documented?" true
|
||||
check_yes_no "Launch day playbook ready?" true
|
||||
|
||||
echo ""
|
||||
|
||||
# Results
|
||||
echo -e "${BLUE}╔═══════════════════════════════════════════════╗${NC}"
|
||||
echo -e "${BLUE}║ Readiness Summary ║${NC}"
|
||||
echo -e "${BLUE}╚═══════════════════════════════════════════════╝${NC}"
|
||||
echo ""
|
||||
echo -e "Checks Passed: ${GREEN}$PASSED${NC}"
|
||||
echo -e "Warnings: ${YELLOW}$WARNINGS${NC}"
|
||||
echo -e "Failed: ${RED}$FAILED${NC}"
|
||||
echo ""
|
||||
|
||||
# Decision
|
||||
if [ $FAILED -eq 0 ]; then
|
||||
if [ $WARNINGS -eq 0 ]; then
|
||||
echo -e "${GREEN}✅ READY TO LAUNCH!${NC}"
|
||||
echo ""
|
||||
echo "All critical checks passed. You're good to go!"
|
||||
else
|
||||
echo -e "${YELLOW}⚠ LAUNCH WITH CAUTION${NC}"
|
||||
echo ""
|
||||
echo "Critical checks passed, but $WARNINGS warnings remain."
|
||||
echo "Consider addressing warnings before launch."
|
||||
fi
|
||||
exit 0
|
||||
else
|
||||
echo -e "${RED}❌ NOT READY TO LAUNCH${NC}"
|
||||
echo ""
|
||||
echo "You have $FAILED critical failures that must be addressed."
|
||||
echo "Do not launch until these are resolved."
|
||||
exit 1
|
||||
fi
|
||||
Reference in New Issue
Block a user