WEBVTT NOTE This file was generated by Descript 00:00:00.250 --> 00:00:03.309 Raphaël: Welcome back to our series on EC's methodology. 00:00:03.809 --> 00:00:06.989 Last time we talked about preventing major breakdowns and setting 00:00:06.989 --> 00:00:08.550 yourself up for quick recovery. 00:00:09.050 --> 00:00:12.919 Today, we'll talk about gathering data to better understand your progress. 00:00:13.419 --> 00:00:17.260 Every project has a different definition of success. 00:00:17.599 --> 00:00:21.630 In almost every case you'll need both quantitative and qualitative feedback to 00:00:21.630 --> 00:00:23.970 assess whether you've reached your goals. 00:00:24.270 --> 00:00:27.809 We need to identify metrics that correlate with success and figure 00:00:27.809 --> 00:00:29.160 out how to keep track of them. 00:00:29.660 --> 00:00:34.040 There are many types of data that you could consider for your success metrics. 00:00:34.540 --> 00:00:37.540 Here are a few that we like to consider when building an app. 00:00:38.040 --> 00:00:38.820 App data. 00:00:39.320 --> 00:00:42.439 This is just the data in your database. 00:00:42.939 --> 00:00:46.480 If you're building a task tracking app, then it might just be the number 00:00:46.480 --> 00:00:48.880 of completed tasks and the database. 00:00:49.180 --> 00:00:53.950 We like to monitor this type of data, the data that's in your internal application 00:00:53.950 --> 00:00:56.800 database with a tool called Metabase. 00:00:57.420 --> 00:01:01.980 Though there are others you could use like AWS QuickSight or Google's data studio. 00:01:02.480 --> 00:01:04.340 Next behavioural data. 00:01:04.840 --> 00:01:09.160 This is data gathered from how your users interact with the app. 00:01:09.660 --> 00:01:14.100 This is in contrast with the data that they actually submit to the app. 00:01:14.600 --> 00:01:19.160 For example, it might be which screens they've visited in a mobile app, or 00:01:19.160 --> 00:01:21.560 which pages they visited on a website. 00:01:22.060 --> 00:01:25.600 It might also be the things that they've clicked on or what step 00:01:25.600 --> 00:01:28.120 they've reached in a form or a flow. 00:01:28.619 --> 00:01:31.740 This is typically collected using analytics tools. 00:01:32.040 --> 00:01:36.720 Some of our favorites include segment, Google analytics and Mixpanel. 00:01:37.220 --> 00:01:39.439 Next up operational data. 00:01:39.939 --> 00:01:43.929 This is data like how many features did we release this quarter? 00:01:44.530 --> 00:01:48.489 We like to keep track of that type of thing in our project management tool. 00:01:48.549 --> 00:01:50.259 Currently we're using ClickUp. 00:01:50.910 --> 00:01:55.799 But other viable options include Asana, JIRA, and monday.com. 00:01:56.115 --> 00:01:57.735 Next performance data. 00:01:58.285 --> 00:02:01.495 This is the type of data that we would be pulling from the 00:02:01.495 --> 00:02:03.205 tools we discussed last time. 00:02:03.705 --> 00:02:05.685 For example, how fast is everything running? 00:02:05.715 --> 00:02:07.425 How many servers are we using? 00:02:07.455 --> 00:02:10.665 Or are there crashes happening on a regular basis? 00:02:11.165 --> 00:02:13.745 Alrighty next qualitative feedback. 00:02:14.245 --> 00:02:18.085 Feedback from users is crucial to understanding how well you're doing 00:02:18.085 --> 00:02:19.975 and where you need to go in the future. 00:02:20.475 --> 00:02:24.285 This is harder to measure, but it is absolutely crucial. 00:02:24.315 --> 00:02:26.025 You need to connect with your users. 00:02:26.525 --> 00:02:30.875 This data basically comes from reaching out to them that could be using automated 00:02:30.875 --> 00:02:35.785 systems like Customer IO or Intercom, or it could be looking at your analytics, 00:02:35.815 --> 00:02:39.505 figuring out who are the best users and reaching out to them directly. 00:02:40.005 --> 00:02:43.485 There are definitely other types of data that you can use to measure success. 00:02:43.485 --> 00:02:46.005 But these are the ones that we use most commonly. 00:02:46.505 --> 00:02:49.475 If you found this helpful and you want to learn more about app development, 00:02:49.505 --> 00:02:51.635 make sure to check out our free PDF. 00:02:51.935 --> 00:02:52.595 And let us know. 00:02:52.595 --> 00:02:56.075 How do you define success in your apps and how do you measure. 00:02:56.575 --> 00:03:00.325 Follow us if you want to keep up with this series, we have a lot more to share, and 00:03:00.325 --> 00:03:04.045 we're always updating our process from the things that we've learned along the 00:03:04.045 --> 00:03:06.445 way and our community and our partners. 00:03:06.945 --> 00:03:09.765 If you think that we could work together, we'd love to partner with you. 00:03:09.795 --> 00:03:13.185 Just reach out and we'll see if we can help you out with your next project. 00:03:13.845 --> 00:03:15.315 Thanks and see you next time.