product centric delivery teams
TRANSCRIPT
PRODUCT-CENTRIC DELIVERY TEAMSDELIVER ON VALUE NOT DATES
TEAM PROCESS
2
PRODUCT TEAM PROCESS
BACKLOGGOAL
Research
OpportunityHypothesis
Opportunity Opportunity
G
O O O
##Metric
##Metric
M##
M##
Research Research
Hypothesis Hypothesis
DESIGN
DEVELOP
TEST
RELEASE
W E EK S
TWO
DEFINE IDEATE DEVELOP
GOAL
Opportunity Opportunity Opportunity
##Metric
##Metric
DEFINE _ The team will align their understanding with leadership’s business goals.
_ We will select metrics whose performance can be tracked as quantifiable outcomes—revenue, conversion rate, etc.
_ Next, we’ll analyze the performance of customer behavior specific to product discovery—search, navigation, refinement—and identify opportunities of value to explore.
_ Our analysis won’t just include current reporting, but also user interviews, observation, and peer-research.
PRODUCT TEAM PROCESS
Research
Hypothesis
G
O O O
M##
M##
Research Research
Hypothesis Hypothesis
IDEATE _ From the identified opportunities, the team will research potential avenues to leverage value.
_ Through the research, discussion, and collaborative design, we will have produced a set of promising hypothesis for experimentation.
_ The hypothesis will be prioritized by it’s potential impact and assumed effort—our aim being to build for highest value at lowest cost.
_ Not all hypothesis will be proven by development and release—some might be tested as rapid prototypes, surveys, even interviews with users.
_ Together, our Goals, Metrics, Opportunities, Research, and Hypothesis make up our Product Backlog
PRODUCT TEAM PROCESS
DEVELOP _ Hypothesis prioritized highest will move into development, placed into our team’s Development Backlog organized by epics—themes defined as desired outcomes
_ A cross-functional group, led by UX, will collaboratively design the implementation—ensuring clarity of technical delivery, testability, business + user validation, and measurable feedback to determine proof of the hypothesis after release.
_ A Hypothesis should be small enough to prove value in a short time frame, simply understood in terms of development, and capable of moving through the four stages within a two-week sprint.
BACKLOG
DESIGN
DEVELOP
TEST
RELEASE
W E EK S
TWO
_ Feedback from users and reporting are brought as learning back into the
PRODUCT TEAM PROCESS
THE PRODUCT TEAM
7
ENABLED
8
_ Small, autonomous, dedicated, collaborative team
_ Soup to nuts—include Data/ETLs/MerchOps tools
_ EVERYONE is a Product Owner
DATA-DRIVEN
9
_ Success measured on KPIs—Conversion, Relevancy
_ Use analytics to make decisions
_ Feed data back into product—personalization, performance
USER EXPERIENCE @ CORE
10
_ Rely on feedback, A/B experiments
_ Less hi-fi comps, iterate on lo-fi designs
SMALL MVP
11
_ Start with a narrow slice of the site—e.g. Type Ahead
_ Low bar to deployment—one browser, small set of users
_ Early initial release—1 month
_ Move into regular sprint-release cadence—2 weeks
STRONG TECHNICAL FOUNDATION
12
_ POC major initiatives vs. direct development
_ Start with public cloud—auto-scaling for ease of operations
_ Simplify tech stack
_ Establish dev + delivery enabling tooling + infrastructure
THE PRODUCT TEAM
13
_ Small, autonomous, dedicated, collaborative team
_ Soup to nuts—include Data/ETLs/MerchOps tools
_ EVERYONE is a Product Owner
ENABLED_ Success measured on KPIs—Conversion, Relevancy
_ Use analytics to make decisions
_ Feed data back into product—personalization, performance
DATA-DRIVEN
_ Rely on feedback, A/B experiments
_ Less hi-fi comps, iterate on lo-fi designs
USER EXPERIENCE @ CORE SMALL MVP_ Start with a narrow slice of the site—e.g. Type Ahead
_ Low bar to deployment—one browser, small set of users
_ Early initial release—1 month
_ Move into regular sprint-release cadence—2 weeksSTRONG TECHNICAL FOUNDATION_ POC major initiatives vs. direct development
_ Public cloud—auto-scaling for ease of operations
_ Simplify tech stack
_ Establish dev + delivery enabling tooling + infra
QUESTIONS?On anything we covered
APPENDIXKey Documents
15
PRODUCT TEAM PROCESS
BACKLOGGOAL
Research
OpportunityHypothesis
Opportunity Opportunity
G
O O O
##Metric
##Metric
M##
M##
Research Research
Hypothesis Hypothesis
DESIGN
DEVELOP
TEST
RELEASE
W E EK S
TWO
DEFINE IDEATE DEVELOP
THE PRODUCT TEAM
17
_ Small, autonomous, dedicated, collaborative team
_ Soup to nuts—include Data/ETLs/MerchOps tools
_ EVERYONE is a Product Owner
ENABLED_ Success measured on KPIs—Conversion, Relevancy
_ Use analytics to make decisions
_ Feed data back into product—personalization, performance
DATA-DRIVEN
_ Rely on feedback, A/B experiments
_ Less hi-fi comps, iterate on lo-fi designs
USER EXPERIENCE @ CORE SMALL MVP_ Start with a narrow slice of the site—e.g. Type Ahead
_ Low bar to deployment—one browser, small set of users
_ Early initial release—1 month
_ Move into regular sprint-release cadence—2 weeksSTRONG TECHNICAL FOUNDATION_ POC major initiatives vs. direct development
_ Public cloud—auto-scaling for ease of operations
_ Simplify tech stack
_ Establish dev + delivery enabling tooling + infra