Technical Strategy Flashcards
4 Levels of Technical Strategy
- The technical strategy portfolio
- Company and technical strategy calibration
- Generating new ideas and making trade-offs
- Strategic execution
The technical strategy portfolio
Every work can potentially be put into one of the buckets below
Product, Scale and Risk
Generating new ideas and making trade-offs
Our goals should be right on the edge of wildly ambitious but technically feasible
Scale work
- Maintenance
- Developer Efficiency
- Technical Improvements, resolving performance or availability issues.
- Velocity Enablement, creating speed in future efforts
Risk work
- Ops Improvements, improve infrastructure and product reliability
- Security Improvements
- Regulatory compliance
Metrics that matter
- Financial metrics
2. Customer metrics
Supporting metrics
Metrics that improve the north star metrics
Obstacles to creating a balanced portfolio
Root Causes Solutions
Wrong frame of reference Categorize engineering work in a portfolio
No outcomes Identify the right outcomes
No definition of good Set thresholds to assess outcomes
When to best do scale work
Early-stage - hurt product to market
At the growing stage
Mature - Open a window for competitors to catch up
Use case map
Problem: The problem the product solves in the words of the user or customer
Persona: Who faces the problem
Value Proposition: Why a user or customer chooses your product to solve their problem instead of the alternatives
Alternatives: Alternatives they consider to solve the problem
Competitive Landscape
- Direct competitors
- Indirect alternatives
- Adjacent markets
Where to set the threshold?
- What do our customers care about? Identify specific tech capabilities that can deliver it
- What experience issues do we manually fix?
- User psych explains where friction is tolerable and where it isn’t
What should the threshold be?
- Product data
1.1 Evaluate outlying 5%
1.2 Evaluate performance across persona dimensions
2 Customer data
2.1 Explore data to see where customers are having problems
2.2 Analyze problems by reviewing segments of the target persona
3 Competitor data
Risk work type
- Operational risk, Issues that impact performance or availability
- Security risk
- Regulatory risk
Risk work outcomes
Type of risk -> outcome -> impact
Operational Sliding Scale Acquisition
Security Retention
Regulatory Binary Other costs
Risk = likelihood * impact Likelihood = timeframe + probability
Risk work thresholds
Customer constraints/tolerant
Financial constraints/tolerant
Resource constraints
The strategy stack
Mission: The change your company wants to bring to the world
Company Strategy: The plan you have to bring your company’s mission into being
Function Strategy: Plan for how a specific function will drive its part of the company strategy
Functional Roadmap: The sequence of features that implement the product strategy
Functional Goals: Outcomes of the roadmap that measure product strategy progress.
Technical Strategy in the strategy stack
Mission Company Strategy Function Strategy = Technical Strategy Functional Roadmap Functional Goals
Technical Strategy Calibration Horizontally
Marketing Strategy and Product Strategy
Key to calibrating strategy
Speak the same language. Like travelling
Acquisition
Get more new users
Acquisition - Marketing Funnel
Awareness
Consideration
Conversion
Loyalty
Acquisition - Acquisition Loops
Viral: Fuel/Constraint Users
Content: Fuel/Constraint Content & Timeline
Paid: Fuel/Constraint The amount of capital available to reinvest
Acquisition - Alleviating Acquisition Constraints
Remove friction in an existing strategy
Improve the quality of users in an existing strategy
Enable new acquisition sources with a new technology