Historically, product managers spent a lot of their time in reactive mode, which made staying strategic increasingly difficult. That is no longer the case. Product teams today must measure and iterate throughout the product creation process to build products that are sticky, delightful and deliver obvious and immediate value to users. We will discuss best practices for agile product management, where user insight, guidance and experimentation come together as continuous process. We will also explore how product teams can pair deeper user insights with product experimentation to onboard new users, release new products and features, understand user feedback and continuously improve their products and user experience.

1. Experiment-led Agile
Product Management
How data-driven product teams leverage experimentation to build better products

2. Introductions
Experiment-led Agile Product Management
Trevor Stuart, Co-founder and Head of Product at Split Software
Before Split Software, Trevor was a product lead at Salesforce
Prior to that, Trevor worked on Product at RelateIQ (which was
purchased by Salesforce in 2014)
Michael Peach is Head of Product Marketing at Pendo
Before Pendo, Michael was a marketing director at IBM for seven
years.
Prior to that, Michael was a product lead for Quadbase Systems, and
had various software product, marketing, and sales roles
2

3. Agenda
Experiment-led Agile Product Management
- The Evolution of the PM role
- Experimentation & Data, Your Secret Weapon
- Use Case #1:
Trial Experience
- Use Case #2:
Feature Roll Out and Awareness
- Use Case #3:
Continuous Product Experience and Education
- Q&A

4. 4
Digital Products Today Are...
Experiment-led Agile Product Management
Multi-channel
90% of consumers “multi-
screen” - using 2.42
devices at the same time
Fueled by data
By 2021, 75% of software
providers will rely on
insights from embedded
software usage analytics
Subscription-based
By 2020, 73% of
organizations plan to shift
all of their apps to SaaS

5. 5
Product Management is Moving
From “Gut-driven” to Data-driven
Experiment-led Agile Product Management

6. 6
Resulting in an iterative product creation lifecycle
Experiment-led Agile Product Management
PRODUCT
TEAM
Products and features are
scoped, prioritized and
success metrics are defined
PLAN
Product and feature plans
and goals are adjusted
based on analysis
REFINE
Initial ideation is brought to
life and tested for viability
DESIGN
Features and feature variations
are rolled out to users along
with training and education
TEST & DEPLOY
User behavior and feedback is captured,
analyzed, and benchmarked against
success metrics
SURVEY & MEASURE
USERS

8. Powering Better Product Decisions Through
Experimentation and Data
Experiment-led Agile Product Management
Use Pendo analytics to
● Understand user awareness
(do your customers know what
you have launched)
● Accurately measure user
adoption (how much of your
customer base is using your
new feature)
● Evaluate if customer value is
being delivered (how satisfied
are your customers with your
new feature?)
Use Split product experimentation to
● Rollout functionality to
percentages of your customer
base
● Ensure a stable customer
experience while increasing
product delivery cadence
● Measure both product,
engineering and business data,
to test for quality, performance,
adoption, and overall impact
Trial Experience | Feature Rollouts and Analytics | Continuous Product Improvements
0%
100%
50%
Track
Feature
Impact
8

9. Use Case 1 - Trial Experience
Experiment-led Agile Product Management
With
PM teams can utilize:
• In-app guidance
• User surveys
• Onboarding
• Analytics - helping sales and
marketing see what modules users
are using,
With
PM teams can:
• Change onboarding flow and
measure impact of new functionality
on key metrics
• Roll-out functionality to trial users
first to understand their impact
before rolling out to entire customer
base
9

10. Use Case 2 - Feature Rollout and Analytics
Experiment-led Agile Product Management
With
PM teams can:
• Capture feature usage data to
understand discoverability and
engagement
• Use Goals to set measurable goals
and track them accordingly
With
PM teams can:
• Release new functionality to
targeted customers
• Measure NPS and survey data from
Pendo in Split
• Measure product usage data from
Pendo in Split
10

11. Use Case 3 - Continuous Product Improvement
Experiment-led Agile Product Management
With
PM teams can utilize:
• Analytics to understand usage
• Guide center to provide continued
education
∙ You can show a different guide
based on those who have
adopted new functionality
versus those who haven’t
With
PM teams can:
• Increase deployment and testing
frequency
• Lower time to production
• Release with confidence
• Maintain hold out sets for future
testing
11

12. How This Works in Practice
12

13. Experimenting With Starring Using Split
Experiment-led Agile Product Management
Establishing different treatments
13

14. Collecting Usage Data Using Pendo
Experiment-led Agile Product Management
Collecting usage data in Pendo
14

15. Creating Metrics Using Split
Experiment-led Agile Product Management
Creating custom metrics to
measure discoverability and
engagement
15

16. Deriving Results using Split
Experiment-led Agile Product Management
Less
Discoverability
Fewer users discovered or clicked the star
when it was smaller
Increased
Engagement
For those that starred, they starred
a lot of small stars
Understanding impact
of each treatment
16

17. Questions
17

18. Thank You!
18

19. Agenda
Experiment-led Agile Product Management
- Split.io Overview
- Pendo Overview
- Evolution of the PM role
- Use Case #1:
Trial Experience
- Use Case #2:
Feature Roll Out and Awareness
- Use Case #3:
Continuous Product Experience and Education
- Q&A

20. Pendo is a product cloud that
helps product teams deliver
software that users love.
20