Video summary
Case study Dx with Executive VP & President of Commerce Services, Lila Snyder, Pitney Bowes
Main summary
Key takeaways
Business Transformation: From Declining Mail to Growing Shipping & E-commerce
- Context: Pitney Bowes, with roots in mailing for ~100 years, faces a secular decline in traditional mailing. Mailing “isn’t growing” and is expected to continue declining as consumers and businesses shift to digital transactions (e.g., invoices and statements).
- Strategic pivot (growth engine): Shift focus from mailing to shipping + e-commerce.
- Mailing → Shipping
- Hardware → Digital, modernizing legacy assets using the Internet of Things (IoT)
Guiding principle: Become a modern growing company by prioritizing a portfolio where underlying market dynamics are growing.
How the Pivot Is Executed (Leveraging Existing Strengths)
- Core competency: Reducing operational complexity in mailing—Pitney Bowes doesn’t originate/deliver mail directly; instead, it helps businesses make mailing operations simpler.
-
Replication in shipping/e-commerce: Shipping is inherently complex, especially for small/mid-size retailers who care more about products and customers than the mechanics of shipping.
- Win by applying complexity-reduction expertise to a new category rather than trying to “out-startup” competitors purely on innovation speed.
Technology Strategy Tied to Customer Expectations (Data + Predictive Delivery)
- Market reality: E-commerce moves very fast, with new entrants appearing frequently (e.g., “almost every week”).
-
Rising customer expectations: Consumers increasingly expect:
- Fast delivery
- Free shipping
- Door-to-door tracking
Concrete example: Predictive delivery timing
- Use transactional + tracking + delivery data to predict parcel arrival times.
- If tracking scans are missed, use data to estimate delivery timing so customers still experience “information” continuity.
Using purchase data to improve relevance
- Use data on what consumers buy to help retailers reach relevant consumers using improved technology capabilities.
Organizational / Operating Model Change for Faster Digital Delivery
The challenge
As digital products grow, teams must collaborate differently than in traditional legacy IT structures:
- Product management
- Engineering
- Tech ops/IT
The response: “Pods”
Pitney Bowes introduced an operating model called pods:
- Form cross-functional pods that include:
- product management
- engineering
- IT-related functions
- Assign pods at a more junior level, with clear ownership, including:
- Each pod owns the product’s operations
- Each pod owns core metrics, such as:
- Revenue
- Profitability
- Uptime
- Reliability
Intended outcomes
- Reduce “handoff” issues between teams
- Address the “no one looks across the whole system” problem by improving system-wide accountability
- Enable product teams to run a live 24/7 service model
Status / timeline
- The shift to pods is described as having happened “recently.”
- It’s characterized as early days: “already less issues,” but “a long way to go.”
Frameworks / Playbooks Mentioned
- Operating model: Pods
- Cross-functional product teams
- Pod ownership of product operations + core KPIs
- Alignment across PM/engineering/IT to support continuous 24/7 reliability and uptime
Key Metrics / KPIs Explicitly Referenced
- Revenue
- Profitability
- Uptime
- Reliability
(No numeric targets such as % growth, CAC/LTV, churn, or margins were provided.)
Concrete Examples / Actionable Takeaways
- Predict delivery timing using multiple data sources (transactional, tracking, delivery history), especially when tracking scans are missing.
- Invest in product capabilities driven by consumer expectations (e.g., tracking transparency, delivery speed, and “information continuity”).
- Restructure the organization so pods own end-to-end outcomes, reducing handoffs that harm operational systems.
Presenter / Source
- Lila Snyder, Executive VP & President of Commerce Services, Pitney Bowes