Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Product metrics for developers
Search
Salahutdinov Dmitry
June 11, 2020
Programming
0
70
Product metrics for developers
What developers need to know about product metrics
Salahutdinov Dmitry
June 11, 2020
Tweet
Share
More Decks by Salahutdinov Dmitry
See All by Salahutdinov Dmitry
Fullstack monitoring
dsalahutdinov
0
210
Kubernetes-native Ruby development
dsalahutdinov
0
480
Business Impact Driven Development
dsalahutdinov
0
350
Optimistic UI with Logux & Ruby (RubyRussia)
dsalahutdinov
0
370
bidd.pdf
dsalahutdinov
0
290
Optimistic UI with Logux & Ruby
dsalahutdinov
0
250
Optimistic UI and live updates with Logux & Ruby
dsalahutdinov
1
1.9k
Outdated browser detection with Browserslist
dsalahutdinov
1
350
Other Decks in Programming
See All in Programming
Range on Rails ―「多重範囲型」という新たな選択肢が、複雑ロジックを劇的にシンプルにしたワケ
rizap_tech
0
7.7k
CSC509 Lecture 07
javiergs
PRO
0
240
20251016_Rails News ~Rails 8.1の足音を聴く~
morimorihoge
3
740
Things You Thought You Didn’t Need To Care About That Have a Big Impact On Your Job
hollycummins
0
260
Reactive Thinking with Signals and the Resource API
manfredsteyer
PRO
0
110
What's new in Spring Modulith?
olivergierke
1
170
Google Opalで使える37のライブラリ
mickey_kubo
3
150
PHPに関数型の魂を宿す〜PHP 8.5 で実現する堅牢なコードとは〜 #phpcon_hiroshima / phpcon-hiroshima-2025
shogogg
1
340
CSC509 Lecture 08
javiergs
PRO
0
250
社会人になっても趣味開発を続けたい! / traPavilion
mazrean
1
100
CSC305 Lecture 10
javiergs
PRO
0
260
品質ワークショップをやってみた
nealle
0
640
Featured
See All Featured
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
15k
RailsConf 2023
tenderlove
30
1.3k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
140
34k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.1k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
31
2.7k
Faster Mobile Websites
deanohume
310
31k
Being A Developer After 40
akosma
91
590k
Learning to Love Humans: Emotional Interface Design
aarron
274
41k
Producing Creativity
orderedlist
PRO
347
40k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.6k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
658
61k
The Illustrated Children's Guide to Kubernetes
chrisshort
49
51k
Transcript
1 Business impact driven development Dmitry Salahutdinov 12/10/209 Salahutdinov Dmitry
Product metrics for developers What and why developers should get deep into product analytics
Hey, my name is Dmitry 2 +
AMPLIFR 3
4 Vital project: 400m2
Continuous delivery
Canary releases A/B Testing
7 Feature Toggling
Experimenting
Measuring
Analysis Reinforcement
11 Process is iterative and continuous Area, time, workers are
limited Needs are growing Persistently
12 Продакт овнер? Growth hacker? Typical weekday?
13 Продакт овнер? Growth hacker? Startup? Product owner?
14 Продакт овнер? Growth hacker? Startup? Product owner? Growth hacker?
Yep! Run experiments to increase impact Monitoring Analysis Changes
16 Using tools and techniques to turn data into meaningful
business insights Analytics
Business metrics Trial to Payment conversion Paid users outflow 17
Highest level metrics about performing product as “money maker”
18 Product metrics ↗ Feature A Usage Middle-level performance metrics
in terms of product features
19 Tech metrics Low-level metrics metrics how the technical underground
perform
20 Are numbers
That are the only one truth Measure The only One
Truth! Everyone in your team has own background and insights Product analytics works both: for developer & product owner 21
22 Analytics/Metrics - is the only one source of true
data
23 Analytics/Metrics - is the only one source of true
data - helps approve good ideas
24 Analytics/Metrics - is the only one source of true
data - helps approve good ideas - helps reject bad ideas
25 Analytics/Metrics - is the only one source of true
data - helps approve good ideas - helps reject bad ideas - works both ways
Example: main feature fails Error rates correlates with users outflow
User outflow Let developers earn money by increasing code quality: Do refactoring legacy code and give back technical debt ☺ Fail Post 26
27 Product Owner Developer Business Role distribution
28 Product Owner Developer Business Startup role distribution
Proper tools 29
Tracking events 30
Show graphical data, compare Data visualisation Scheduled Post Created Draft
31
Metadata Event metadata stores “as is” User metadata associates within
current event Pass extra user & event data to analytics 32
Metadata usage Scheduled Post by user having Billing Plan “A”
Scheduled Post by user having Billing Plan “B” 33 Extra date for details analysis
Multiple platroms support Mobile application Web(frontend/backend) 34
Track releases Release: feature deployment Release: feature improvement 35
Instrumentation ⚒ 36
Amplitude 37
10 millions events for free 38
Amplitude API 39
Backend integration Ruby sample Node JS Mobile 40
Frontend integration 41
Share user properties Render “backend” User properties Pass actual user
properties With events 42
Empirical tips 43
verb + noun (e.g. 'clicked signup’) noun + verb (e.g.
'signup clicked') Naming Scheduled Post Draft created Save post saved Fail to post ... ... ✅ ❌ Event naming convention prevents entropy 44
Separate environments To keep experiments pure and prevent testing events
mixing Overall data Testing data Very significant for low traffic experiments! 45
Organise events & properties And keep it simple 46
Use cases 47
Existing feature analysis Start to collect metrics - measure feature
performance - make a decision: improve or remove Measure business performance metrics before 48
New feature investigating/testing Start to collect metrics New feature deployment
Ensure to have previous and next metrics collected 49
Incremental improvements Do small experiments with performance analysis 50
Impact driven? For getting business impact 51
52 Every change has to do an impact
Impact work cycle 53 - collect metrics
Impact work cycle 54 - collect metrics - analyse performance/profit
Impact work cycle 55 - collect metrics - analyse performance/profit
- make a prediction (hypothesis)
Impact work cycle 56 - collect metrics - analyse performance/profit
- make a prediction (hypothesis) - run & monitor
Impact work cycle 57 - collect metrics - analyse performance/profit
- make a prediction (hypothesis) - run & monitor - repeat if ok, reject if not Experiment
58 Example: health hacking :)
Necessary conditions 59 - Statistical correctness of analytics
Necessary conditions 60 - Statistical correctness of analytics - Traffic
vs Duration
Necessary conditions 61 - Statistical correctness of analytics - Traffic
vs Duration - Prevent interception
Necessary conditions 62 - Statistical correctness of analytics - Traffic
vs Duration - Prevent interception - Overhead for small experiments
Necessary conditions 63 - Statistical correctness of analytics - Traffic
vs Duration - Prevent interception - Overhead for small experiments - Time consuming for huge ones
Analytics makes devs happy get deeper to a business process
essence to increase developer culture (awareness of feature benefits) to reduce communication blockers (distributed teams) to motivate yourself unique argumentation system to growth experience & expertise 64
Thank you ❤ @dsalahutdinov1 @dsalahutdinov https://dev.to/amplifr https://amplifr.com 65