bidd.pdf - Speaker Deck

Slide 1

Slide 1 text

Business analytics driven development Dmitry Salahutdinov metrics impact 1

Slide 2

Slide 2 text

Hey, my name is Dmitry + 2

Slide 3

Slide 3 text

AMPLIFR !3

Slide 4

Slide 4 text

Part 1: Introduce  Business analytics !4

Slide 5

Slide 5 text

metrics ↗ “Trial to Payment” conversion ↘ “Paid users outﬂow” !5

Slide 6

Slide 6 text

Advanced analytics Payment funnel Trial Retention !6

Slide 7

Slide 7 text

Numbers are the only one truth Measure The only One Truth! Everyone in your team has own background and insights Business analytics works both: for developer & product owner !7

Slide 8

Slide 8 text

Example: Stick header & footer Average user screen height is ~600px !8

Slide 9

Slide 9 text

Example: Publication fails Error rates correlates with users outﬂow Scheduled Posts User outﬂow Let developers earn money by increasing code quality: Do refactoring legacy code and give back technical debt ☺ Failed !9

Slide 10

Slide 10 text

Part 2: requirements !10

Slide 11

Slide 11 text

Tracking events !11

Slide 12

Slide 12 text

Show graphical data, compare Data visualisation Scheduled Post Created Draft !12

Slide 13

Slide 13 text

Metadata Event metadata stores “as is” User metadata associates within current event Pass extra user & event data to analytics !13

Slide 14

Slide 14 text

Metadata usage Scheduled Post  by user having Billing Plan “A” Scheduled Post  by user having Billing Plan “B” !14

Slide 15

Slide 15 text

Multiple platroms support Mobile application Web(frontend/backend) !15

Slide 16

Slide 16 text

Track releases Release:  feature deployment Release:  feature improvement !16

Slide 17

Slide 17 text

Part 3: Instrumentation ⚒ !17

Slide 18

Slide 18 text

Amplitude !18

Slide 19

Slide 19 text

10 millions events for free !19

Slide 20

Slide 20 text

Amplitude API !20

Slide 21

Slide 21 text

Backend integration Ruby sample Node JS Mobile !21

Slide 22

Slide 22 text

Frontend integration !22

Slide 23

Slide 23 text

Share user properties Render “backend” User properties Pass actual user properties With events !23

Slide 24

Slide 24 text

Part 4: empirical tips !24

Slide 25

Slide 25 text

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 prevent entropy !25

Slide 26

Slide 26 text

Separate environments To keep experiments pure and prevent testing events mixing Overall data Testing data Very signiﬁcant for low traﬃc experiments! !26

Slide 27

Slide 27 text

Organise events & properties And keep it simple !27

Slide 28

Slide 28 text

Part 5: Use cases !28

Slide 29

Slide 29 text

Existing feature analysis Start to collect metrics - measure feature performance - make a decision: improve or remove Measure business performance metrics before !29

Slide 30

Slide 30 text

New feature investigating/testing Start to collect metrics New feature deployment Ensure to have previous and next metrics collected !30

Slide 31

Slide 31 text

Incremental improvements Do small experiments with performance analysis !31

Slide 32

Slide 32 text

Part 6: workﬂow - For getting business impact !32

Slide 33

Slide 33 text

Success steps •Collect product metrics with analytics that is easy to use and accessible to everyone. •Analyze feature performance and user interaction with the product •Build predictions and hypotheses of features to increase key/ﬁnancial application metrics •Monitor metrics changes after releases, repeat successful ones, increase expertise !33

Slide 34

Slide 34 text

Necessary conditions ✅ Ensure you have enough analytics before & after ✅ Traffic vs time ✅ Prevent hypothesis interception ✅ Overhead for small experiments !34

Slide 35

Slide 35 text

Part 5: Amplifr stories !35

Slide 36

Slide 36 text

Green errors 6%↗ post popup cancellation !36

Slide 37

Slide 37 text

Settings => Subscription ~20% Change Project Name => Activate Subscription Let just force people to change project name and earn !37

Slide 38

Slide 38 text

Collaboration feature visibility Unexpected ideas could work ↗ feature visibility with ugly ↗ adding another user ↗ billing plan 4 !38

Slide 39

Slide 39 text

For developers? get deeper to a business process essence 5 to increase developer culture (awareness of feature benefits) to reduce communication blockers (distributed teams) to motivate yourself Unique argumentation system to growth experience & expertise Do small experiments with performance analysis !39

Slide 40

Slide 40 text

Pet project? !40

Slide 41

Slide 41 text

SAINTPRUBY 30% discount coupon ❤ !41

Slide 42

Slide 42 text

Thank you ❤ @dsalahutdinov1 @dsalahutdinov https://dev.to/amplifr https://amplifr.com We are looking for passionate Ruby developer ❤ Write us to [email protected] See you! !42