Back to Playbook
Chapter 6

Delivery Pod Model

The embedded strike team structure that delivers measurable outcomes in 30 days

Chapter Highlights

Cross-Functional Pods

2-3 FDEs + 1 DS + 1 Ontology Engineer per customer

Clear Role Charters

Defined responsibilities and success metrics per role

Day 1-30 Playbook

Week-by-week checklist for fast time to value

6.1Pod Composition

Core Roles

Forward Deployed Engineer

Number per Pod

2-3 FDEs

Responsibilities

  • ✓ Data integration
  • ✓ Pipeline development
  • ✓ Application configuration
  • ✓ Performance optimization

Deployment Strategist

Number per Pod

1 DS

Responsibilities

  • ✓ Stakeholder management
  • ✓ Use case prioritization
  • ✓ Change management
  • ✓ Success metrics tracking

Ontology Engineer

Number per Pod

1 (can be remote)

Responsibilities

  • ✓ Data model design
  • ✓ Object definition
  • ✓ Semantic layer maintenance
  • ✓ Knowledge transfer

Supporting Roles

Product Manager (Remote, 20%)

  • ✓ Feature prioritization
  • ✓ Platform roadmap alignment
  • ✓ Customer feedback synthesis

Security Engineer (On-demand)

  • ✓ Security review and hardening
  • ✓ Compliance validation
  • ✓ Incident response

6.2Role Charters

Forward Deployed Engineer Charter

Mission

Own the technical delivery of customer outcomes

Key Responsibilities

1. Build and deploy data pipelines
2. Configure applications and workflows
3. Train customer technical teams
4. Optimize system performance
5. Troubleshoot production issues

Success Metrics

Time to first value<30 days
System uptime99.9%+
User adoption80%+

Required Skills

Python, SQL, JavaData EngineeringCustomer CommunicationProblem Solving

Deployment Strategist Charter

Mission

Ensure customer achieves business value from the platform

Key Responsibilities

1. Define success criteria with stakeholders
2. Drive organizational change
3. Measure and communicate ROI
4. Identify expansion opportunities
5. Manage executive relationships

Success Metrics

Customer satisfaction (NPS)70+
Value realizationDocumented ROI
Expansion revenue2x in year 1

Required Skills

Domain ExpertiseExecutive CommunicationData StorytellingPolitical Navigation

6.3Rules of Engagement

Customer Access Required

  • ✓ Admin access to relevant systems
  • ✓ Ability to provision resources
  • ✓ Direct line to decision-makers
  • ✓ Participation in planning meetings

Boundaries to Respect

  • ✓ No access to unrelated systems
  • ✓ Respect data classification
  • ✓ Follow customer security policies
  • ✓ Maintain confidentiality

Decision Rights

Pod Can Decide

✓ Technical implementation approach

✓ Daily prioritization

✓ Bug fixes and optimizations

✓ Training schedules

Customer Must Approve

✓ New use cases

✓ Data access expansions

✓ Production deployments

✓ Process changes

Escalation Required

✓ Scope changes

✓ Additional resources

✓ Contract modifications

✓ Security exceptions

6.4Day 1-30 Playbook

Week 1

Establish Foundation

Day 1-2: Onboarding

Security badging and access
Workspace setup
System accounts created
Meet key stakeholders

Day 3-5: Discovery

Stakeholder interviews
Data source inventory
Current state assessment
Use case prioritization
Week 2

Build Initial Capability

Day 6-8: Data Integration

Connect first data source
Build initial pipelines
Data quality assessment
Create base ontology

Day 9-10: First Application

Build simple workflow
Create visualization
Gather user feedback
Iterate based on input
Week 3

Demonstrate Value

Day 11-13: Refinement

Optimize performance
Enhance user interface
Add requested features
Document processes

Day 14-15: User Enablement

Conduct training sessions
Create user guides
Set up support channel
Define success metrics
Week 4

Scale and Expand

Day 16-18: Production Deployment

Security review
Performance testing
Deployment to production
Monitor stability

Day 19-20: Stakeholder Review

Present achievements
Document ROI
Gather feedback
Plan next phase

Day 30: Executive Checkpoint

Agenda

  1. Value delivered to date
  2. Metrics and KPIs
  3. User testimonials
  4. Expansion opportunities
  5. 90-day roadmap

Deliverables

  • ✓ Executive summary
  • ✓ ROI calculation
  • ✓ User adoption metrics
  • ✓ Technical architecture
  • ✓ Expansion proposal

Summary: Pod Model Essentials

Cross-functional pods: 2-3 FDEs + 1 DS + 1 Ontology Engineer embedded on-site

Clear charters: FDEs own technical delivery, DS owns business value realization

Rules of engagement: Admin access granted, decision rights defined, escalation paths clear

30-day playbook: Week-by-week checklist from onboarding to production deployment

Day 30 checkpoint: Executive review with ROI documentation and expansion roadmap

Previous: GTM & Deal Capture MotionNext: Commercial Model & Pricing

Download the Complete Playbook

Get the full 250+ page Word document with all 11 chapters, case studies, and implementation templates

Download Word Document