SCALING PRODUCTS AND TEAMS IN A HYPER- GROWTH ENVIRONMENT - - PowerPoint PPT Presentation
SCALING PRODUCTS AND TEAMS IN A HYPER- GROWTH ENVIRONMENT - - PowerPoint PPT Presentation
SCALING PRODUCTS AND TEAMS IN A HYPER- GROWTH ENVIRONMENT ENGINEERING AND DESIGN-DRIVEN CULTURE INCREDIBLE CUSTOMER SERVICE VIRAL GROWTH GREAT FOR THE BUSINESS, TERRIFYING FOR THOSE RUNNING IT Soaring response times Persistent mobile
ENGINEERING AND DESIGN-DRIVEN CULTURE
INCREDIBLE CUSTOMER SERVICE
Soaring response times Persistent mobile bugs Frantic fire-fighting Culture clashes
VIRAL GROWTH GREAT FOR THE BUSINESS, TERRIFYING FOR THOSE RUNNING IT
PROBLEM
MOBILE TEAM AND PLATFORM STILL IN THE “GARAGE” PHASE
FEW USERS VIRAL GROWTH
Move fast and break things Few users affected Low impact on operation Move fast and break things (carefully) Many users affected High impact on operation
STEP 1
INVEST IN CODE QUALITY
- trust your developers, don’t postpone it
- constantly reevaluating
- it will make things faster
- let you sleep at night
- devs must be responsible for their code
- everyone should know the code
- continuously improving / learning
- facilitate cooperation across platforms
TECHNICAL DEBT UNIT + FUNCTIONAL TESTING CODE REVIEW + FEATURE BRANCHES
CODE QUALITY
STEP 2
IMPROVE PROCESSES
POST /prospect/register :status 201 PATCH /account-requests/:id :status 200 GET /credit-limit :status 200 GET /card-tracking :status 200 acquisition customers topmodel sendman
END TO END TESTS E2E
build-and-test deploy-to-staging deploy-to-prod End-to-end tests acquisition customers sendman build-and-test build-and-test
CONTINUOUS INTEGRATION
release-internal release-to-store mobile end-to-end tests build-and-test
CONTINUOUS INTEGRATION MOBILE
CLOSE RELEASE OPEN BETA + CHECKLIST FEEDBACK + BUGFIX + CRASH MONITORING RELEASE
STEP 3
SCALE THE TEAM
PRODUCT / ENG TEAMS
SQUAD SQUAD SQUAD SQUAD MOBILE SQUAD
- Larger team needed to address
growing customer demands and technical debt
- Most squads have needs for
mobile resources
- Mobile engineers: are they
mission-first (the squad), or function-first (the platform)?
ISSUES
PRODUCT / ENG TEAMS
SQUAD SQUAD SQUAD SQUAD
- More autonomy for squads to
prioritize and act on their issues
- Increased velocity / fewer
barriers to decision-making
- Greater cooperation / cross-
pollination between mobile and other functions
WHAT DO WE GAIN
SQUAD
- Platform/release
coordination
- Design standardization
across the app
- Team cohesion
WHAT ARE THE RISKS
PROBLEM
ONLY WAY TO SCALE IS TO ADD HUMANS
BACKOFFICE APPS
SQUAD CHAPTER
PRODUCT / ENG TEAMS CUSTOMER SERVICE CHANNELS / APPS OPS TEAM
PRODUCT / ENG TEAMS CUSTOMER SERVICE OPS TEAM CHANNELS / APPS
Fragmented, channel-based tools Army of generalists Product / Engineering far from the front lines Different cultures BACKOFFICE APPS
STEP 1
INVEST IN INTERNAL TOOLING
PREDICTIVE MODEL
VOLUME OF "WORK"
Job Job Job Job Job Job Job Job Job Job Job Job Job
Integrated dispatch and analytics service “Proximo”
GLOBAL PRIORITY QUEUE
BACKOFFICE APPS
BADGE-SPECIFIC PRIORITY QUEUE
WHAT DO WE GAIN?
Adaptability
- Maintain and evolve the software on our own schedule
(e.g. ability to rapidly add new controls for fraud)
- In full control of prioritization of features
Security & confidentiality • Allows us to compartmentalise sensitive data
- Reduced exposure to leaks at third party vendors
Custom components
- Ability to build small, focused tools that address
specific objectives Integrated analytics
- Ease of integration of all relevant data sources for use
in appropriate applications
- Readily available metrics for managing and motivating
squads Learning / training
- Transferable skillets and frameworks
Operating leverage
- Algorithms and prioritisation queues replace line
managers and supervisors
- Workflow optimization
- Facilitates increasing levels of specialization
- Intuitive UI reduces errors, training time, frustration
STEP 2
SETTING UP OUR ORG STRUCTURE TO SCALE
PRODUCT / ENG TEAMS CUSTOMER SERVICE OPS TEAM CHANNELS / APPS
BACKOFFICE APPS
SQUAD CHAPTER SQUAD SQUAD SQUAD SQUAD
ENTIRE COMPANY
TRIBE
Sense of urgency
- Cost of failure is more tangible
Cultural unity
- Breaks down silos between functions, particularly
customer service and technical organisation
- Agile processes (stand-ups, etc) open to all
Accountability &
- wnership
- All stakeholders and functions are aligned to the mission
- “Peer pressure” within squads to do more with less
- Metrics / OKRs are generated with buy-in of all functions
Product feedback
- Close interaction between product/design,
engineering and customer service facilitates greater communication and strong feedback loops
WHAT DO WE GAIN?
Comprehensive approach to product design
- Ability to think through full process from customer
interaction to customer service support