WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:13.509 align:start position:0% [Music] 00:00:13.509 --> 00:00:13.519 align:start position:0% 00:00:13.519 --> 00:00:16.609 align:start position:0% camisa<00:00:14.519> I<00:00:14.880> work<00:00:15.059> at<00:00:15.240> element<00:00:15.360> Finance<00:00:15.960> I'm<00:00:16.440> a 00:00:16.609 --> 00:00:16.619 align:start position:0% camisa I work at element Finance I'm a 00:00:16.619 --> 00:00:19.370 align:start position:0% camisa I work at element Finance I'm a product<00:00:16.800> manager<00:00:17.340> element<00:00:18.119> Finance<00:00:18.720> is<00:00:19.020> a 00:00:19.370 --> 00:00:19.380 align:start position:0% product manager element Finance is a 00:00:19.380 --> 00:00:21.529 align:start position:0% product manager element Finance is a protocol<00:00:19.619> a<00:00:19.859> D5<00:00:20.160> protocol<00:00:20.520> for<00:00:20.880> fixed<00:00:21.359> and 00:00:21.529 --> 00:00:21.539 align:start position:0% protocol a D5 protocol for fixed and 00:00:21.539 --> 00:00:24.890 align:start position:0% protocol a D5 protocol for fixed and variable<00:00:21.900> yields<00:00:22.920> and<00:00:23.820> um<00:00:24.300> I'm<00:00:24.720> really 00:00:24.890 --> 00:00:24.900 align:start position:0% variable yields and um I'm really 00:00:24.900 --> 00:00:26.330 align:start position:0% variable yields and um I'm really excited<00:00:25.140> to<00:00:25.320> be<00:00:25.439> here<00:00:25.560> today<00:00:25.740> to<00:00:25.980> talk<00:00:26.160> to<00:00:26.279> you 00:00:26.330 --> 00:00:26.340 align:start position:0% excited to be here today to talk to you 00:00:26.340 --> 00:00:28.849 align:start position:0% excited to be here today to talk to you about<00:00:26.460> product<00:00:27.000> development<00:00:27.420> and<00:00:27.599> defy<00:00:28.439> and 00:00:28.849 --> 00:00:28.859 align:start position:0% about product development and defy and 00:00:28.859 --> 00:00:31.669 align:start position:0% about product development and defy and let's<00:00:29.039> get<00:00:29.279> started 00:00:31.669 --> 00:00:31.679 align:start position:0% let's get started 00:00:31.679 --> 00:00:33.950 align:start position:0% let's get started so<00:00:32.399> first<00:00:32.700> off<00:00:32.940> I<00:00:33.300> kind<00:00:33.360> of<00:00:33.480> wanted<00:00:33.540> a<00:00:33.840> level 00:00:33.950 --> 00:00:33.960 align:start position:0% so first off I kind of wanted a level 00:00:33.960 --> 00:00:36.410 align:start position:0% so first off I kind of wanted a level set<00:00:34.200> on<00:00:34.620> what<00:00:35.100> does<00:00:35.219> a<00:00:35.399> product<00:00:35.579> manager<00:00:36.239> do 00:00:36.410 --> 00:00:36.420 align:start position:0% set on what does a product manager do 00:00:36.420 --> 00:00:38.389 align:start position:0% set on what does a product manager do and<00:00:37.020> you<00:00:37.500> know<00:00:37.559> there's<00:00:37.860> lots<00:00:38.160> of<00:00:38.219> different 00:00:38.389 --> 00:00:38.399 align:start position:0% and you know there's lots of different 00:00:38.399 --> 00:00:40.250 align:start position:0% and you know there's lots of different definitions 00:00:40.250 --> 00:00:40.260 align:start position:0% definitions 00:00:40.260 --> 00:00:42.229 align:start position:0% definitions um and<00:00:40.980> oftentimes<00:00:41.399> people<00:00:41.700> will<00:00:41.879> think<00:00:42.059> they 00:00:42.229 --> 00:00:42.239 align:start position:0% um and oftentimes people will think they 00:00:42.239 --> 00:00:43.850 align:start position:0% um and oftentimes people will think they do<00:00:42.360> one<00:00:42.540> thing<00:00:42.719> or<00:00:42.899> another 00:00:43.850 --> 00:00:43.860 align:start position:0% do one thing or another 00:00:43.860 --> 00:00:46.010 align:start position:0% do one thing or another oftentimes<00:00:44.520> a<00:00:44.700> PM<00:00:45.000> does<00:00:45.300> a<00:00:45.600> lot<00:00:45.719> of<00:00:45.899> things 00:00:46.010 --> 00:00:46.020 align:start position:0% oftentimes a PM does a lot of things 00:00:46.020 --> 00:00:47.690 align:start position:0% oftentimes a PM does a lot of things it's<00:00:46.440> everything 00:00:47.690 --> 00:00:47.700 align:start position:0% it's everything 00:00:47.700 --> 00:00:48.290 align:start position:0% it's everything um 00:00:48.290 --> 00:00:48.300 align:start position:0% um 00:00:48.300 --> 00:00:50.270 align:start position:0% um so<00:00:48.539> the<00:00:48.780> core<00:00:48.960> area<00:00:49.260> of<00:00:49.500> responsibility<00:00:49.860> is 00:00:50.270 --> 00:00:50.280 align:start position:0% so the core area of responsibility is 00:00:50.280 --> 00:00:52.750 align:start position:0% so the core area of responsibility is shaping<00:00:50.760> the<00:00:50.879> product<00:00:51.200> shipping<00:00:52.200> the<00:00:52.320> product 00:00:52.750 --> 00:00:52.760 align:start position:0% shaping the product shipping the product 00:00:52.760 --> 00:00:55.790 align:start position:0% shaping the product shipping the product measuring<00:00:53.760> product<00:00:54.059> success<00:00:54.600> and<00:00:55.500> these<00:00:55.680> are 00:00:55.790 --> 00:00:55.800 align:start position:0% measuring product success and these are 00:00:55.800 --> 00:00:57.350 align:start position:0% measuring product success and these are things<00:00:55.980> I'm<00:00:56.219> going<00:00:56.340> to<00:00:56.460> kind<00:00:56.579> of<00:00:56.699> loosely<00:00:57.059> talk 00:00:57.350 --> 00:00:57.360 align:start position:0% things I'm going to kind of loosely talk 00:00:57.360 --> 00:00:59.689 align:start position:0% things I'm going to kind of loosely talk about<00:00:57.480> throughout<00:00:58.020> the<00:00:58.140> presentation<00:00:58.699> but 00:00:59.689 --> 00:00:59.699 align:start position:0% about throughout the presentation but 00:00:59.699 --> 00:01:00.950 align:start position:0% about throughout the presentation but synchronizing<00:01:00.300> the<00:01:00.420> team<00:01:00.600> is<00:01:00.780> really 00:01:00.950 --> 00:01:00.960 align:start position:0% synchronizing the team is really 00:01:00.960 --> 00:01:02.630 align:start position:0% synchronizing the team is really important 00:01:02.630 --> 00:01:02.640 align:start position:0% important 00:01:02.640 --> 00:01:05.509 align:start position:0% important the<00:01:03.180> product<00:01:03.619> person<00:01:04.619> will<00:01:04.920> interface<00:01:05.280> with 00:01:05.509 --> 00:01:05.519 align:start position:0% the product person will interface with 00:01:05.519 --> 00:01:07.609 align:start position:0% the product person will interface with the<00:01:05.700> rest<00:01:05.820> of<00:01:05.939> the<00:01:06.060> team<00:01:06.240> kind<00:01:06.960> of<00:01:07.080> align<00:01:07.380> on 00:01:07.609 --> 00:01:07.619 align:start position:0% the rest of the team kind of align on 00:01:07.619 --> 00:01:10.609 align:start position:0% the rest of the team kind of align on timelines<00:01:08.240> uh<00:01:09.240> hash<00:01:09.960> out<00:01:10.080> kind<00:01:10.380> of<00:01:10.500> product 00:01:10.609 --> 00:01:10.619 align:start position:0% timelines uh hash out kind of product 00:01:10.619 --> 00:01:12.770 align:start position:0% timelines uh hash out kind of product requirements<00:01:11.340> and<00:01:11.880> ensure<00:01:12.180> everyone<00:01:12.360> is<00:01:12.659> on 00:01:12.770 --> 00:01:12.780 align:start position:0% requirements and ensure everyone is on 00:01:12.780 --> 00:01:14.270 align:start position:0% requirements and ensure everyone is on the<00:01:12.960> same<00:01:13.080> page<00:01:13.260> and<00:01:13.500> kind<00:01:13.680> of<00:01:13.799> working<00:01:13.860> in<00:01:14.159> the 00:01:14.270 --> 00:01:14.280 align:start position:0% the same page and kind of working in the 00:01:14.280 --> 00:01:17.750 align:start position:0% the same page and kind of working in the same<00:01:14.400> direction 00:01:17.750 --> 00:01:17.760 align:start position:0% 00:01:17.760 --> 00:01:19.310 align:start position:0% so<00:01:18.060> I<00:01:18.180> want<00:01:18.299> to<00:01:18.420> talk<00:01:18.540> about<00:01:18.659> building<00:01:19.080> the 00:01:19.310 --> 00:01:19.320 align:start position:0% so I want to talk about building the 00:01:19.320 --> 00:01:22.609 align:start position:0% so I want to talk about building the product<00:01:19.500> roadmap<00:01:20.220> and 00:01:22.609 --> 00:01:22.619 align:start position:0% product roadmap and 00:01:22.619 --> 00:01:25.010 align:start position:0% product roadmap and um<00:01:22.680> how<00:01:22.920> I<00:01:23.460> want<00:01:23.580> to<00:01:23.700> kind<00:01:24.119> of<00:01:24.299> place<00:01:24.659> a<00:01:24.900> little 00:01:25.010 --> 00:01:25.020 align:start position:0% um how I want to kind of place a little 00:01:25.020 --> 00:01:26.810 align:start position:0% um how I want to kind of place a little bit<00:01:25.140> of<00:01:25.200> emphasis<00:01:25.619> on<00:01:25.799> R<00:01:25.979> D<00:01:26.159> and<00:01:26.460> how<00:01:26.640> that's 00:01:26.810 --> 00:01:26.820 align:start position:0% bit of emphasis on R D and how that's 00:01:26.820 --> 00:01:29.330 align:start position:0% bit of emphasis on R D and how that's really<00:01:27.119> important<00:01:27.540> to<00:01:27.720> kind<00:01:28.140> of<00:01:28.259> creating<00:01:28.619> new 00:01:29.330 --> 00:01:29.340 align:start position:0% really important to kind of creating new 00:01:29.340 --> 00:01:32.210 align:start position:0% really important to kind of creating new product<00:01:29.580> opportunities 00:01:32.210 --> 00:01:32.220 align:start position:0% product opportunities 00:01:32.220 --> 00:01:35.270 align:start position:0% product opportunities so<00:01:32.820> D5<00:01:33.299> research<00:01:33.720> teams<00:01:34.200> really<00:01:34.860> need<00:01:35.100> to 00:01:35.270 --> 00:01:35.280 align:start position:0% so D5 research teams really need to 00:01:35.280 --> 00:01:37.310 align:start position:0% so D5 research teams really need to focus<00:01:35.520> sorry<00:01:35.880> the<00:01:36.180> D5<00:01:36.420> teams<00:01:36.780> really<00:01:37.020> need<00:01:37.200> to 00:01:37.310 --> 00:01:37.320 align:start position:0% focus sorry the D5 teams really need to 00:01:37.320 --> 00:01:40.130 align:start position:0% focus sorry the D5 teams really need to focus<00:01:37.560> on<00:01:37.979> research<00:01:38.579> and<00:01:38.759> development<00:01:39.180> in 00:01:40.130 --> 00:01:40.140 align:start position:0% focus on research and development in 00:01:40.140 --> 00:01:42.530 align:start position:0% focus on research and development in order<00:01:40.320> to<00:01:40.560> succeed<00:01:40.860> in<00:01:41.100> the<00:01:41.220> space<00:01:41.400> they<00:01:42.360> got 00:01:42.530 --> 00:01:42.540 align:start position:0% order to succeed in the space they got 00:01:42.540 --> 00:01:44.450 align:start position:0% order to succeed in the space they got to<00:01:42.659> commit<00:01:42.900> to<00:01:43.079> experimentation<00:01:43.860> it's<00:01:44.280> not 00:01:44.450 --> 00:01:44.460 align:start position:0% to commit to experimentation it's not 00:01:44.460 --> 00:01:46.510 align:start position:0% to commit to experimentation it's not just<00:01:44.579> about<00:01:44.820> rehashing<00:01:45.540> existing<00:01:46.079> Solutions 00:01:46.510 --> 00:01:46.520 align:start position:0% just about rehashing existing Solutions 00:01:46.520 --> 00:01:48.830 align:start position:0% just about rehashing existing Solutions and<00:01:47.520> it's<00:01:47.759> important<00:01:48.000> to<00:01:48.119> take<00:01:48.299> an<00:01:48.479> additive 00:01:48.830 --> 00:01:48.840 align:start position:0% and it's important to take an additive 00:01:48.840 --> 00:01:50.270 align:start position:0% and it's important to take an additive approach<00:01:49.320> where 00:01:50.270 --> 00:01:50.280 align:start position:0% approach where 00:01:50.280 --> 00:01:52.969 align:start position:0% approach where you're<00:01:50.880> building<00:01:51.180> new<00:01:51.479> D5<00:01:51.780> Primitives<00:01:52.320> and 00:01:52.969 --> 00:01:52.979 align:start position:0% you're building new D5 Primitives and 00:01:52.979 --> 00:01:54.530 align:start position:0% you're building new D5 Primitives and contributing<00:01:53.460> those<00:01:53.640> Primitives<00:01:54.119> to<00:01:54.360> the 00:01:54.530 --> 00:01:54.540 align:start position:0% contributing those Primitives to the 00:01:54.540 --> 00:01:57.230 align:start position:0% contributing those Primitives to the open<00:01:54.720> source<00:01:55.259> defy<00:01:56.100> ecosystem 00:01:57.230 --> 00:01:57.240 align:start position:0% open source defy ecosystem 00:01:57.240 --> 00:02:00.249 align:start position:0% open source defy ecosystem and<00:01:57.960> at<00:01:58.079> the<00:01:58.200> same<00:01:58.320> time<00:01:58.439> you're<00:01:58.799> leveraging 00:02:00.249 --> 00:02:00.259 align:start position:0% and at the same time you're leveraging 00:02:00.259 --> 00:02:02.870 align:start position:0% and at the same time you're leveraging D5<00:02:01.259> Lego<00:02:01.500> pieces<00:02:01.979> and<00:02:02.159> this<00:02:02.340> again<00:02:02.460> fits 00:02:02.870 --> 00:02:02.880 align:start position:0% D5 Lego pieces and this again fits 00:02:02.880 --> 00:02:05.090 align:start position:0% D5 Lego pieces and this again fits within<00:02:03.119> the<00:02:03.299> whole<00:02:03.720> um<00:02:03.840> you<00:02:04.020> know<00:02:04.079> idea<00:02:04.619> or 00:02:05.090 --> 00:02:05.100 align:start position:0% within the whole um you know idea or 00:02:05.100 --> 00:02:07.370 align:start position:0% within the whole um you know idea or ethos<00:02:05.579> of<00:02:06.000> composability<00:02:06.600> within<00:02:06.960> the<00:02:07.079> D5 00:02:07.370 --> 00:02:07.380 align:start position:0% ethos of composability within the D5 00:02:07.380 --> 00:02:08.630 align:start position:0% ethos of composability within the D5 space 00:02:08.630 --> 00:02:08.640 align:start position:0% space 00:02:08.640 --> 00:02:10.609 align:start position:0% space so<00:02:09.060> having<00:02:09.300> a<00:02:09.720> pipeline<00:02:10.140> of<00:02:10.319> research 00:02:10.609 --> 00:02:10.619 align:start position:0% so having a pipeline of research 00:02:10.619 --> 00:02:12.650 align:start position:0% so having a pipeline of research projects<00:02:11.039> is<00:02:11.220> really<00:02:11.459> important<00:02:11.879> it<00:02:12.540> could 00:02:12.650 --> 00:02:12.660 align:start position:0% projects is really important it could 00:02:12.660 --> 00:02:14.330 align:start position:0% projects is really important it could really<00:02:12.840> guide<00:02:13.140> the<00:02:13.440> evolution<00:02:13.860> of<00:02:14.160> the 00:02:14.330 --> 00:02:14.340 align:start position:0% really guide the evolution of the 00:02:14.340 --> 00:02:16.070 align:start position:0% really guide the evolution of the product<00:02:14.520> or<00:02:14.819> dap<00:02:15.180> you're<00:02:15.360> working<00:02:15.540> on<00:02:15.720> within 00:02:16.070 --> 00:02:16.080 align:start position:0% product or dap you're working on within 00:02:16.080 --> 00:02:18.229 align:start position:0% product or dap you're working on within the<00:02:16.140> D5<00:02:16.379> space<00:02:16.680> and<00:02:17.580> it<00:02:17.760> could<00:02:17.879> potentially 00:02:18.229 --> 00:02:18.239 align:start position:0% the D5 space and it could potentially 00:02:18.239 --> 00:02:20.869 align:start position:0% the D5 space and it could potentially lead<00:02:18.480> to<00:02:18.720> entirely<00:02:19.140> new<00:02:19.319> products<00:02:19.860> and<00:02:20.700> so 00:02:20.869 --> 00:02:20.879 align:start position:0% lead to entirely new products and so 00:02:20.879 --> 00:02:22.070 align:start position:0% lead to entirely new products and so with<00:02:21.120> that 00:02:22.070 --> 00:02:22.080 align:start position:0% with that 00:02:22.080 --> 00:02:23.990 align:start position:0% with that um you<00:02:22.260> know<00:02:22.379> the<00:02:22.620> the<00:02:22.860> pipeline<00:02:23.459> of<00:02:23.640> research 00:02:23.990 --> 00:02:24.000 align:start position:0% um you know the the pipeline of research 00:02:24.000 --> 00:02:26.449 align:start position:0% um you know the the pipeline of research projects<00:02:24.420> can<00:02:24.720> really<00:02:24.900> form<00:02:25.140> the<00:02:25.560> basis<00:02:25.980> of 00:02:26.449 --> 00:02:26.459 align:start position:0% projects can really form the basis of 00:02:26.459 --> 00:02:28.190 align:start position:0% projects can really form the basis of the<00:02:26.760> r<00:02:26.879> d<00:02:27.060> roadmap 00:02:28.190 --> 00:02:28.200 align:start position:0% the r d roadmap 00:02:28.200 --> 00:02:30.830 align:start position:0% the r d roadmap and<00:02:28.920> the<00:02:29.220> r<00:02:29.280> d<00:02:29.459> roadmap 00:02:30.830 --> 00:02:30.840 align:start position:0% and the r d roadmap 00:02:30.840 --> 00:02:33.530 align:start position:0% and the r d roadmap is<00:02:31.500> a<00:02:31.800> critical<00:02:32.099> input<00:02:32.580> a<00:02:33.000> very<00:02:33.180> important 00:02:33.530 --> 00:02:33.540 align:start position:0% is a critical input a very important 00:02:33.540 --> 00:02:35.990 align:start position:0% is a critical input a very important input<00:02:33.840> into<00:02:34.140> the<00:02:34.379> product<00:02:34.500> roadmap<00:02:35.040> mind<00:02:35.760> you 00:02:35.990 --> 00:02:36.000 align:start position:0% input into the product roadmap mind you 00:02:36.000 --> 00:02:37.790 align:start position:0% input into the product roadmap mind you it's<00:02:36.360> not<00:02:36.540> the<00:02:36.780> only<00:02:36.900> input<00:02:37.260> into<00:02:37.440> the<00:02:37.680> product 00:02:37.790 --> 00:02:37.800 align:start position:0% it's not the only input into the product 00:02:37.800 --> 00:02:41.030 align:start position:0% it's not the only input into the product roadmap<00:02:38.280> there's<00:02:38.580> lots<00:02:39.000> of<00:02:39.060> other<00:02:39.239> things<00:02:40.040> but 00:02:41.030 --> 00:02:41.040 align:start position:0% roadmap there's lots of other things but 00:02:41.040 --> 00:02:42.850 align:start position:0% roadmap there's lots of other things but it<00:02:41.160> is<00:02:41.340> really<00:02:41.580> important 00:02:42.850 --> 00:02:42.860 align:start position:0% it is really important 00:02:42.860 --> 00:02:45.770 align:start position:0% it is really important I<00:02:43.860> want<00:02:43.980> to<00:02:44.160> talk<00:02:44.280> about<00:02:44.459> how<00:02:44.879> do<00:02:45.000> we<00:02:45.180> structure 00:02:45.770 --> 00:02:45.780 align:start position:0% I want to talk about how do we structure 00:02:45.780 --> 00:02:48.050 align:start position:0% I want to talk about how do we structure the<00:02:46.140> product<00:02:46.319> roadmap<00:02:46.860> or<00:02:47.580> lay<00:02:47.760> it<00:02:47.940> out 00:02:48.050 --> 00:02:48.060 align:start position:0% the product roadmap or lay it out 00:02:48.060 --> 00:02:49.670 align:start position:0% the product roadmap or lay it out because<00:02:48.360> oftentimes<00:02:48.959> we<00:02:49.140> think<00:02:49.379> about<00:02:49.500> it 00:02:49.670 --> 00:02:49.680 align:start position:0% because oftentimes we think about it 00:02:49.680 --> 00:02:52.490 align:start position:0% because oftentimes we think about it from<00:02:49.860> a<00:02:50.040> timing<00:02:50.340> perspective<00:02:50.780> by<00:02:51.780> month<00:02:52.019> by 00:02:52.490 --> 00:02:52.500 align:start position:0% from a timing perspective by month by 00:02:52.500 --> 00:02:53.869 align:start position:0% from a timing perspective by month by quarter 00:02:53.869 --> 00:02:53.879 align:start position:0% quarter 00:02:53.879 --> 00:02:57.110 align:start position:0% quarter um<00:02:54.480> I<00:02:55.019> think<00:02:55.200> the<00:02:55.560> now<00:02:55.800> next<00:02:56.220> later<00:02:56.640> approach 00:02:57.110 --> 00:02:57.120 align:start position:0% um I think the now next later approach 00:02:57.120 --> 00:03:00.350 align:start position:0% um I think the now next later approach works<00:02:57.660> really<00:02:57.959> really<00:02:58.140> well<00:02:58.940> especially<00:02:59.940> in 00:03:00.350 --> 00:03:00.360 align:start position:0% works really really well especially in 00:03:00.360 --> 00:03:03.050 align:start position:0% works really really well especially in the<00:03:00.720> fast-paced<00:03:01.319> environment<00:03:01.620> of<00:03:01.860> defy<00:03:02.400> or 00:03:03.050 --> 00:03:03.060 align:start position:0% the fast-paced environment of defy or 00:03:03.060 --> 00:03:04.910 align:start position:0% the fast-paced environment of defy or for<00:03:03.239> teams<00:03:03.599> that<00:03:03.660> are<00:03:03.780> working<00:03:03.959> on<00:03:04.379> new 00:03:04.910 --> 00:03:04.920 align:start position:0% for teams that are working on new 00:03:04.920 --> 00:03:07.610 align:start position:0% for teams that are working on new product<00:03:05.099> development<00:03:05.840> you<00:03:06.840> know<00:03:06.900> V1<00:03:07.319> of<00:03:07.500> a 00:03:07.610 --> 00:03:07.620 align:start position:0% product development you know V1 of a 00:03:07.620 --> 00:03:09.650 align:start position:0% product development you know V1 of a protocol<00:03:07.920> where<00:03:08.879> there's<00:03:09.239> a<00:03:09.420> lot<00:03:09.540> of 00:03:09.650 --> 00:03:09.660 align:start position:0% protocol where there's a lot of 00:03:09.660 --> 00:03:11.149 align:start position:0% protocol where there's a lot of uncertainty<00:03:10.200> and<00:03:10.379> things<00:03:10.560> are<00:03:10.739> changing 00:03:11.149 --> 00:03:11.159 align:start position:0% uncertainty and things are changing 00:03:11.159 --> 00:03:12.530 align:start position:0% uncertainty and things are changing really<00:03:11.400> fast 00:03:12.530 --> 00:03:12.540 align:start position:0% really fast 00:03:12.540 --> 00:03:14.270 align:start position:0% really fast so<00:03:13.080> everything<00:03:13.379> you're<00:03:13.620> working<00:03:13.800> on<00:03:14.040> in 00:03:14.270 --> 00:03:14.280 align:start position:0% so everything you're working on in 00:03:14.280 --> 00:03:15.890 align:start position:0% so everything you're working on in Flight<00:03:14.459> is<00:03:14.819> kind<00:03:15.000> of<00:03:15.060> in<00:03:15.180> the<00:03:15.360> now<00:03:15.480> bucket 00:03:15.890 --> 00:03:15.900 align:start position:0% Flight is kind of in the now bucket 00:03:15.900 --> 00:03:18.050 align:start position:0% Flight is kind of in the now bucket everything<00:03:16.500> that's<00:03:17.040> coming<00:03:17.280> up<00:03:17.459> is<00:03:17.700> a<00:03:17.879> next 00:03:18.050 --> 00:03:18.060 align:start position:0% everything that's coming up is a next 00:03:18.060 --> 00:03:20.390 align:start position:0% everything that's coming up is a next and<00:03:18.720> anything<00:03:18.959> that<00:03:19.260> is<00:03:19.440> low<00:03:19.620> priority<00:03:20.040> kind 00:03:20.390 --> 00:03:20.400 align:start position:0% and anything that is low priority kind 00:03:20.400 --> 00:03:21.949 align:start position:0% and anything that is low priority kind of<00:03:20.459> gets<00:03:20.700> shifted<00:03:21.000> into<00:03:21.120> the<00:03:21.360> later<00:03:21.480> bucket 00:03:21.949 --> 00:03:21.959 align:start position:0% of gets shifted into the later bucket 00:03:21.959 --> 00:03:24.530 align:start position:0% of gets shifted into the later bucket this<00:03:22.800> kind<00:03:22.920> of<00:03:23.040> gives<00:03:23.159> D5<00:03:23.640> teams<00:03:24.060> the<00:03:24.239> ability 00:03:24.530 --> 00:03:24.540 align:start position:0% this kind of gives D5 teams the ability 00:03:24.540 --> 00:03:25.610 align:start position:0% this kind of gives D5 teams the ability to 00:03:25.610 --> 00:03:25.620 align:start position:0% to 00:03:25.620 --> 00:03:28.250 align:start position:0% to not<00:03:26.280> be<00:03:26.519> kind<00:03:26.760> of<00:03:26.819> handcuffed<00:03:27.360> to<00:03:27.540> specific 00:03:28.250 --> 00:03:28.260 align:start position:0% not be kind of handcuffed to specific 00:03:28.260 --> 00:03:30.530 align:start position:0% not be kind of handcuffed to specific timelines<00:03:28.800> when<00:03:29.459> you're<00:03:29.580> developing<00:03:30.000> a<00:03:30.180> V1 00:03:30.530 --> 00:03:30.540 align:start position:0% timelines when you're developing a V1 00:03:30.540 --> 00:03:33.170 align:start position:0% timelines when you're developing a V1 and<00:03:31.379> kind<00:03:31.620> of<00:03:31.739> you<00:03:32.040> know<00:03:32.099> develop<00:03:32.640> it<00:03:32.819> right 00:03:33.170 --> 00:03:33.180 align:start position:0% and kind of you know develop it right 00:03:33.180 --> 00:03:35.449 align:start position:0% and kind of you know develop it right and<00:03:34.019> not<00:03:34.140> necessarily<00:03:34.560> take<00:03:34.739> the<00:03:34.920> shortcuts 00:03:35.449 --> 00:03:35.459 align:start position:0% and not necessarily take the shortcuts 00:03:35.459 --> 00:03:37.729 align:start position:0% and not necessarily take the shortcuts and<00:03:36.420> it<00:03:36.540> just<00:03:36.659> gives<00:03:36.840> them<00:03:36.959> the<00:03:37.140> ability<00:03:37.440> to 00:03:37.729 --> 00:03:37.739 align:start position:0% and it just gives them the ability to 00:03:37.739 --> 00:03:39.949 align:start position:0% and it just gives them the ability to have<00:03:37.920> more<00:03:38.400> flexibility<00:03:38.879> in<00:03:39.360> terms<00:03:39.540> of<00:03:39.659> how 00:03:39.949 --> 00:03:39.959 align:start position:0% have more flexibility in terms of how 00:03:39.959 --> 00:03:44.390 align:start position:0% have more flexibility in terms of how they're<00:03:40.140> developing<00:03:40.560> and<00:03:40.799> timelines<00:03:41.400> overall 00:03:44.390 --> 00:03:44.400 align:start position:0% 00:03:44.400 --> 00:03:46.250 align:start position:0% so<00:03:44.940> this<00:03:45.239> is<00:03:45.540> actually<00:03:45.720> one<00:03:45.900> of<00:03:46.019> my<00:03:46.080> favorite 00:03:46.250 --> 00:03:46.260 align:start position:0% so this is actually one of my favorite 00:03:46.260 --> 00:03:48.410 align:start position:0% so this is actually one of my favorite sections<00:03:46.799> of<00:03:47.280> the<00:03:47.459> presentation<00:03:47.879> and<00:03:48.120> I<00:03:48.299> want 00:03:48.410 --> 00:03:48.420 align:start position:0% sections of the presentation and I want 00:03:48.420 --> 00:03:50.930 align:start position:0% sections of the presentation and I want to<00:03:48.540> get<00:03:48.599> into<00:03:48.980> you<00:03:49.980> know<00:03:50.040> how<00:03:50.280> do<00:03:50.340> we<00:03:50.459> find<00:03:50.640> a 00:03:50.930 --> 00:03:50.940 align:start position:0% to get into you know how do we find a 00:03:50.940 --> 00:03:52.670 align:start position:0% to get into you know how do we find a process<00:03:51.299> a<00:03:51.599> product<00:03:51.840> development<00:03:52.319> process 00:03:52.670 --> 00:03:52.680 align:start position:0% process a product development process 00:03:52.680 --> 00:03:55.729 align:start position:0% process a product development process that<00:03:53.040> works<00:03:53.340> for<00:03:53.700> uh<00:03:54.360> for<00:03:54.659> your<00:03:54.780> team 00:03:55.729 --> 00:03:55.739 align:start position:0% that works for uh for your team 00:03:55.739 --> 00:03:57.649 align:start position:0% that works for uh for your team I<00:03:56.280> have<00:03:56.400> to<00:03:56.580> say<00:03:56.700> that<00:03:56.940> I'm<00:03:57.060> going<00:03:57.180> to<00:03:57.239> caveat 00:03:57.649 --> 00:03:57.659 align:start position:0% I have to say that I'm going to caveat 00:03:57.659 --> 00:04:00.470 align:start position:0% I have to say that I'm going to caveat this<00:03:57.900> with<00:03:58.220> there<00:03:59.220> are<00:03:59.519> lots<00:03:59.879> of<00:03:59.940> nuances 00:04:00.470 --> 00:04:00.480 align:start position:0% this with there are lots of nuances 00:04:00.480 --> 00:04:03.470 align:start position:0% this with there are lots of nuances across<00:04:00.900> different<00:04:01.140> teams<00:04:01.680> team<00:04:02.040> size<00:04:02.480> culture 00:04:03.470 --> 00:04:03.480 align:start position:0% across different teams team size culture 00:04:03.480 --> 00:04:05.390 align:start position:0% across different teams team size culture if<00:04:04.140> you're<00:04:04.260> working<00:04:04.440> on<00:04:04.620> a<00:04:04.739> D5<00:04:04.980> protocol 00:04:05.390 --> 00:04:05.400 align:start position:0% if you're working on a D5 protocol 00:04:05.400 --> 00:04:07.250 align:start position:0% if you're working on a D5 protocol versus<00:04:05.760> adapt<00:04:06.299> that's<00:04:06.480> being<00:04:06.659> built<00:04:06.959> on<00:04:07.140> top 00:04:07.250 --> 00:04:07.260 align:start position:0% versus adapt that's being built on top 00:04:07.260 --> 00:04:09.530 align:start position:0% versus adapt that's being built on top of<00:04:07.440> a<00:04:07.560> protocol<00:04:07.860> all<00:04:08.760> of<00:04:08.879> these<00:04:09.120> things<00:04:09.239> kind 00:04:09.530 --> 00:04:09.540 align:start position:0% of a protocol all of these things kind 00:04:09.540 --> 00:04:12.589 align:start position:0% of a protocol all of these things kind of<00:04:09.659> play<00:04:09.840> into<00:04:10.280> the<00:04:11.280> specific<00:04:11.640> custom<00:04:12.239> product 00:04:12.589 --> 00:04:12.599 align:start position:0% of play into the specific custom product 00:04:12.599 --> 00:04:14.210 align:start position:0% of play into the specific custom product process<00:04:13.080> that<00:04:13.319> you<00:04:13.439> should<00:04:13.560> develop<00:04:13.860> for<00:04:14.040> your 00:04:14.210 --> 00:04:14.220 align:start position:0% process that you should develop for your 00:04:14.220 --> 00:04:16.250 align:start position:0% process that you should develop for your team<00:04:14.400> so<00:04:15.239> this<00:04:15.420> is<00:04:15.540> something<00:04:15.720> that's<00:04:15.900> worked 00:04:16.250 --> 00:04:16.260 align:start position:0% team so this is something that's worked 00:04:16.260 --> 00:04:18.409 align:start position:0% team so this is something that's worked really<00:04:16.500> well<00:04:16.739> for<00:04:16.979> element<00:04:17.160> Finance 00:04:18.409 --> 00:04:18.419 align:start position:0% really well for element Finance 00:04:18.419 --> 00:04:20.330 align:start position:0% really well for element Finance and<00:04:19.320> with<00:04:19.560> that 00:04:20.330 --> 00:04:20.340 align:start position:0% and with that 00:04:20.340 --> 00:04:22.730 align:start position:0% and with that we<00:04:20.940> are<00:04:21.120> still<00:04:21.299> evolving<00:04:21.780> the<00:04:21.959> process<00:04:22.260> as<00:04:22.560> we 00:04:22.730 --> 00:04:22.740 align:start position:0% we are still evolving the process as we 00:04:22.740 --> 00:04:24.890 align:start position:0% we are still evolving the process as we should<00:04:22.919> be<00:04:23.100> to<00:04:23.820> suit<00:04:23.940> our<00:04:24.240> needs<00:04:24.479> as<00:04:24.600> we<00:04:24.780> kind 00:04:24.890 --> 00:04:24.900 align:start position:0% should be to suit our needs as we kind 00:04:24.900 --> 00:04:28.010 align:start position:0% should be to suit our needs as we kind of<00:04:24.960> evolve<00:04:25.320> as<00:04:25.440> a<00:04:25.620> team<00:04:25.740> so<00:04:26.580> stage<00:04:26.940> zero<00:04:27.479> is 00:04:28.010 --> 00:04:28.020 align:start position:0% of evolve as a team so stage zero is 00:04:28.020 --> 00:04:30.890 align:start position:0% of evolve as a team so stage zero is kind<00:04:28.199> of<00:04:28.320> the<00:04:28.440> concept<00:04:28.860> Vision<00:04:29.340> stage<00:04:29.900> and 00:04:30.890 --> 00:04:30.900 align:start position:0% kind of the concept Vision stage and 00:04:30.900 --> 00:04:32.689 align:start position:0% kind of the concept Vision stage and this<00:04:31.080> is<00:04:31.139> where<00:04:31.440> our<00:04:31.620> smart<00:04:31.860> contract<00:04:32.280> leads 00:04:32.689 --> 00:04:32.699 align:start position:0% this is where our smart contract leads 00:04:32.699 --> 00:04:34.370 align:start position:0% this is where our smart contract leads and<00:04:32.880> our<00:04:33.120> Founders<00:04:33.479> both<00:04:33.720> of<00:04:33.840> our<00:04:33.960> Founders 00:04:34.370 --> 00:04:34.380 align:start position:0% and our Founders both of our Founders 00:04:34.380 --> 00:04:38.570 align:start position:0% and our Founders both of our Founders are<00:04:35.000> either<00:04:36.080> previously<00:04:37.080> to<00:04:37.320> researchers<00:04:37.919> and 00:04:38.570 --> 00:04:38.580 align:start position:0% are either previously to researchers and 00:04:38.580 --> 00:04:40.129 align:start position:0% are either previously to researchers and come<00:04:38.759> from<00:04:39.000> a<00:04:39.240> very<00:04:39.360> intensive<00:04:39.840> research 00:04:40.129 --> 00:04:40.139 align:start position:0% come from a very intensive research 00:04:40.139 --> 00:04:42.110 align:start position:0% come from a very intensive research background<00:04:40.500> so<00:04:41.280> they'll<00:04:41.580> usually<00:04:41.820> kind<00:04:42.000> of 00:04:42.110 --> 00:04:42.120 align:start position:0% background so they'll usually kind of 00:04:42.120 --> 00:04:44.990 align:start position:0% background so they'll usually kind of come<00:04:42.240> up<00:04:42.360> with<00:04:42.660> a<00:04:42.840> new<00:04:43.020> feature 00:04:44.990 --> 00:04:45.000 align:start position:0% come up with a new feature 00:04:45.000 --> 00:04:46.730 align:start position:0% come up with a new feature um<00:04:45.060> or<00:04:45.600> something<00:04:45.840> new<00:04:46.020> whether<00:04:46.380> it's<00:04:46.500> a<00:04:46.620> new 00:04:46.730 --> 00:04:46.740 align:start position:0% um or something new whether it's a new 00:04:46.740 --> 00:04:49.310 align:start position:0% um or something new whether it's a new product<00:04:46.860> concept<00:04:47.280> altogether<00:04:47.840> and<00:04:48.840> then<00:04:49.020> the 00:04:49.310 --> 00:04:49.320 align:start position:0% product concept altogether and then the 00:04:49.320 --> 00:04:50.870 align:start position:0% product concept altogether and then the smart<00:04:49.500> contract<00:04:49.919> team<00:04:50.160> leads<00:04:50.460> will<00:04:50.639> usually 00:04:50.870 --> 00:04:50.880 align:start position:0% smart contract team leads will usually 00:04:50.880 --> 00:04:53.390 align:start position:0% smart contract team leads will usually try<00:04:51.120> to<00:04:51.240> crystallize<00:04:51.780> that<00:04:52.220> with<00:04:53.220> our 00:04:53.390 --> 00:04:53.400 align:start position:0% try to crystallize that with our 00:04:53.400 --> 00:04:55.490 align:start position:0% try to crystallize that with our Founders<00:04:53.820> and<00:04:54.540> then<00:04:54.720> in<00:04:54.900> stage<00:04:55.139> one<00:04:55.259> the 00:04:55.490 --> 00:04:55.500 align:start position:0% Founders and then in stage one the 00:04:55.500 --> 00:04:56.990 align:start position:0% Founders and then in stage one the formative<00:04:55.860> stage<00:04:56.220> will<00:04:56.460> have<00:04:56.699> our<00:04:56.820> smart 00:04:56.990 --> 00:04:57.000 align:start position:0% formative stage will have our smart 00:04:57.000 --> 00:04:58.790 align:start position:0% formative stage will have our smart contract<00:04:57.419> teams<00:04:57.780> our<00:04:58.020> front-end<00:04:58.440> teams 00:04:58.790 --> 00:04:58.800 align:start position:0% contract teams our front-end teams 00:04:58.800 --> 00:05:01.129 align:start position:0% contract teams our front-end teams product<00:04:59.160> and<00:04:59.580> design<00:04:59.840> kind<00:05:00.840> of<00:05:00.960> working 00:05:01.129 --> 00:05:01.139 align:start position:0% product and design kind of working 00:05:01.139 --> 00:05:03.469 align:start position:0% product and design kind of working together<00:05:01.580> to<00:05:02.580> really<00:05:02.759> hash<00:05:03.060> out<00:05:03.240> and 00:05:03.469 --> 00:05:03.479 align:start position:0% together to really hash out and 00:05:03.479 --> 00:05:05.390 align:start position:0% together to really hash out and understand<00:05:03.660> the<00:05:03.960> core<00:05:04.139> functionality 00:05:05.390 --> 00:05:05.400 align:start position:0% understand the core functionality 00:05:05.400 --> 00:05:08.090 align:start position:0% understand the core functionality and<00:05:06.240> then<00:05:06.360> in<00:05:06.540> stage<00:05:06.900> two 00:05:08.090 --> 00:05:08.100 align:start position:0% and then in stage two 00:05:08.100 --> 00:05:10.189 align:start position:0% and then in stage two the<00:05:08.639> smart<00:05:08.759> contract<00:05:09.180> team<00:05:09.360> usually<00:05:09.720> takes<00:05:09.960> a 00:05:10.189 --> 00:05:10.199 align:start position:0% the smart contract team usually takes a 00:05:10.199 --> 00:05:11.510 align:start position:0% the smart contract team usually takes a little<00:05:10.259> bit<00:05:10.380> of<00:05:10.500> a<00:05:10.620> step<00:05:10.800> back<00:05:10.979> and<00:05:11.220> they<00:05:11.340> take 00:05:11.510 --> 00:05:11.520 align:start position:0% little bit of a step back and they take 00:05:11.520 --> 00:05:13.670 align:start position:0% little bit of a step back and they take on<00:05:11.759> a<00:05:12.419> little<00:05:12.540> bit<00:05:12.660> more<00:05:12.840> of<00:05:12.960> a<00:05:13.199> consultative 00:05:13.670 --> 00:05:13.680 align:start position:0% on a little bit more of a consultative 00:05:13.680 --> 00:05:16.370 align:start position:0% on a little bit more of a consultative role<00:05:14.100> in<00:05:14.639> a<00:05:14.880> front-end<00:05:15.240> design<00:05:15.660> teams<00:05:16.139> and<00:05:16.259> our 00:05:16.370 --> 00:05:16.380 align:start position:0% role in a front-end design teams and our 00:05:16.380 --> 00:05:18.469 align:start position:0% role in a front-end design teams and our product<00:05:16.560> teams<00:05:17.040> will<00:05:17.880> kind<00:05:18.120> of<00:05:18.180> do<00:05:18.300> the 00:05:18.469 --> 00:05:18.479 align:start position:0% product teams will kind of do the 00:05:18.479 --> 00:05:20.210 align:start position:0% product teams will kind of do the scoping<00:05:18.780> and<00:05:18.900> prototyping<00:05:19.500> so<00:05:19.680> hashing<00:05:20.100> out 00:05:20.210 --> 00:05:20.220 align:start position:0% scoping and prototyping so hashing out 00:05:20.220 --> 00:05:23.150 align:start position:0% scoping and prototyping so hashing out the<00:05:20.400> UI<00:05:20.699> ux<00:05:21.199> the<00:05:22.199> requirements<00:05:22.740> and<00:05:22.919> of<00:05:23.039> course 00:05:23.150 --> 00:05:23.160 align:start position:0% the UI ux the requirements and of course 00:05:23.160 --> 00:05:24.650 align:start position:0% the UI ux the requirements and of course also<00:05:23.520> kind<00:05:23.699> of<00:05:23.820> creating<00:05:24.000> the<00:05:24.180> project<00:05:24.360> plan 00:05:24.650 --> 00:05:24.660 align:start position:0% also kind of creating the project plan 00:05:24.660 --> 00:05:26.029 align:start position:0% also kind of creating the project plan for<00:05:24.900> what's<00:05:25.080> to<00:05:25.380> come 00:05:26.029 --> 00:05:26.039 align:start position:0% for what's to come 00:05:26.039 --> 00:05:28.129 align:start position:0% for what's to come uh<00:05:26.699> and<00:05:26.880> then<00:05:27.000> in<00:05:27.180> stage<00:05:27.479> three<00:05:27.600> we<00:05:27.900> get<00:05:28.020> into 00:05:28.129 --> 00:05:28.139 align:start position:0% uh and then in stage three we get into 00:05:28.139 --> 00:05:30.230 align:start position:0% uh and then in stage three we get into our<00:05:28.380> development<00:05:28.740> Sprints<00:05:29.340> many<00:05:29.580> of<00:05:29.820> you<00:05:29.940> if 00:05:30.230 --> 00:05:30.240 align:start position:0% our development Sprints many of you if 00:05:30.240 --> 00:05:32.450 align:start position:0% our development Sprints many of you if you<00:05:30.360> work<00:05:30.479> on<00:05:30.660> product<00:05:30.840> teams<00:05:31.320> today<00:05:31.560> uh 00:05:32.450 --> 00:05:32.460 align:start position:0% you work on product teams today uh 00:05:32.460 --> 00:05:34.430 align:start position:0% you work on product teams today uh Sprints<00:05:32.880> can<00:05:33.000> be<00:05:33.180> typically<00:05:33.660> two<00:05:33.960> weeks<00:05:34.320> but 00:05:34.430 --> 00:05:34.440 align:start position:0% Sprints can be typically two weeks but 00:05:34.440 --> 00:05:35.749 align:start position:0% Sprints can be typically two weeks but it<00:05:34.620> could<00:05:34.740> be<00:05:34.860> a<00:05:35.039> week<00:05:35.160> it<00:05:35.340> could<00:05:35.460> be<00:05:35.580> a<00:05:35.639> month 00:05:35.749 --> 00:05:35.759 align:start position:0% it could be a week it could be a month 00:05:35.759 --> 00:05:38.150 align:start position:0% it could be a week it could be a month it<00:05:36.000> really<00:05:36.180> depends<00:05:36.479> on<00:05:36.600> the<00:05:36.780> team 00:05:38.150 --> 00:05:38.160 align:start position:0% it really depends on the team 00:05:38.160 --> 00:05:39.590 align:start position:0% it really depends on the team um<00:05:38.280> and<00:05:38.520> this<00:05:38.820> is<00:05:38.880> where<00:05:39.060> we<00:05:39.180> get<00:05:39.300> into<00:05:39.419> the 00:05:39.590 --> 00:05:39.600 align:start position:0% um and this is where we get into the 00:05:39.600 --> 00:05:41.930 align:start position:0% um and this is where we get into the execution<00:05:40.020> cycle<00:05:40.380> important<00:05:41.280> to<00:05:41.460> note<00:05:41.639> that 00:05:41.930 --> 00:05:41.940 align:start position:0% execution cycle important to note that 00:05:41.940 --> 00:05:44.689 align:start position:0% execution cycle important to note that we're<00:05:42.120> actually<00:05:42.360> running<00:05:42.720> two<00:05:44.039> um 00:05:44.689 --> 00:05:44.699 align:start position:0% we're actually running two um 00:05:44.699 --> 00:05:47.210 align:start position:0% we're actually running two um two<00:05:45.060> sprints<00:05:45.479> in<00:05:45.600> parallel<00:05:46.080> so<00:05:46.860> the<00:05:47.039> smart 00:05:47.210 --> 00:05:47.220 align:start position:0% two sprints in parallel so the smart 00:05:47.220 --> 00:05:49.730 align:start position:0% two sprints in parallel so the smart contract<00:05:47.639> team<00:05:47.940> is<00:05:48.780> is<00:05:48.840> developing<00:05:49.440> all<00:05:49.620> of 00:05:49.730 --> 00:05:49.740 align:start position:0% contract team is is developing all of 00:05:49.740 --> 00:05:52.010 align:start position:0% contract team is is developing all of this<00:05:49.919> solidity<00:05:50.340> code<00:05:50.580> their<00:05:51.300> unit<00:05:51.539> testing 00:05:52.010 --> 00:05:52.020 align:start position:0% this solidity code their unit testing 00:05:52.020 --> 00:05:54.409 align:start position:0% this solidity code their unit testing they're<00:05:52.199> doing<00:05:52.380> their<00:05:52.560> fuzz<00:05:52.979> testing<00:05:53.419> a 00:05:54.409 --> 00:05:54.419 align:start position:0% they're doing their fuzz testing a 00:05:54.419 --> 00:05:56.870 align:start position:0% they're doing their fuzz testing a formal<00:05:54.720> verification<00:05:55.199> and<00:05:55.500> Audits<00:05:56.039> and<00:05:56.759> then 00:05:56.870 --> 00:05:56.880 align:start position:0% formal verification and Audits and then 00:05:56.880 --> 00:05:59.570 align:start position:0% formal verification and Audits and then the<00:05:57.060> front<00:05:57.240> end<00:05:57.419> team<00:05:57.720> is<00:05:58.979> um 00:05:59.570 --> 00:05:59.580 align:start position:0% the front end team is um 00:05:59.580 --> 00:06:02.029 align:start position:0% the front end team is um excuse<00:06:00.060> me<00:06:00.240> the<00:06:00.660> front-end<00:06:01.020> team<00:06:01.259> is<00:06:01.620> working 00:06:02.029 --> 00:06:02.039 align:start position:0% excuse me the front-end team is working 00:06:02.039 --> 00:06:04.249 align:start position:0% excuse me the front-end team is working with<00:06:02.340> product<00:06:02.580> and<00:06:02.880> design<00:06:03.080> to<00:06:04.080> kind<00:06:04.199> of 00:06:04.249 --> 00:06:04.259 align:start position:0% with product and design to kind of 00:06:04.259 --> 00:06:06.830 align:start position:0% with product and design to kind of execute<00:06:04.680> the<00:06:05.400> development<00:06:06.120> of<00:06:06.300> the<00:06:06.360> UI<00:06:06.660> and 00:06:06.830 --> 00:06:06.840 align:start position:0% execute the development of the UI and 00:06:06.840 --> 00:06:08.810 align:start position:0% execute the development of the UI and the<00:06:06.960> ux 00:06:08.810 --> 00:06:08.820 align:start position:0% the ux 00:06:08.820 --> 00:06:10.249 align:start position:0% the ux and<00:06:09.240> of<00:06:09.360> course<00:06:09.419> we're<00:06:09.660> doing<00:06:09.840> a<00:06:10.020> lot<00:06:10.080> of 00:06:10.249 --> 00:06:10.259 align:start position:0% and of course we're doing a lot of 00:06:10.259 --> 00:06:12.070 align:start position:0% and of course we're doing a lot of internal<00:06:10.860> and<00:06:11.039> external<00:06:11.460> stakeholder 00:06:12.070 --> 00:06:12.080 align:start position:0% internal and external stakeholder 00:06:12.080 --> 00:06:14.390 align:start position:0% internal and external stakeholder feedback<00:06:13.080> throughout<00:06:13.560> that<00:06:13.680> entire<00:06:14.039> process 00:06:14.390 --> 00:06:14.400 align:start position:0% feedback throughout that entire process 00:06:14.400 --> 00:06:16.670 align:start position:0% feedback throughout that entire process to<00:06:14.699> ensure<00:06:14.940> we're<00:06:15.060> validating<00:06:15.479> assumptions 00:06:16.670 --> 00:06:16.680 align:start position:0% to ensure we're validating assumptions 00:06:16.680 --> 00:06:19.430 align:start position:0% to ensure we're validating assumptions so<00:06:16.979> when<00:06:17.100> we<00:06:17.280> get<00:06:17.400> into<00:06:17.580> the<00:06:17.820> Sprint<00:06:18.000> cycle 00:06:19.430 --> 00:06:19.440 align:start position:0% so when we get into the Sprint cycle 00:06:19.440 --> 00:06:21.770 align:start position:0% so when we get into the Sprint cycle one<00:06:20.280> thing<00:06:20.400> that's<00:06:20.639> really<00:06:21.120> really<00:06:21.300> difficult 00:06:21.770 --> 00:06:21.780 align:start position:0% one thing that's really really difficult 00:06:21.780 --> 00:06:23.749 align:start position:0% one thing that's really really difficult for<00:06:22.259> product<00:06:22.500> teams<00:06:22.979> to<00:06:23.160> do<00:06:23.280> this<00:06:23.639> is 00:06:23.749 --> 00:06:23.759 align:start position:0% for product teams to do this is 00:06:23.759 --> 00:06:25.370 align:start position:0% for product teams to do this is something<00:06:23.880> I<00:06:24.120> found<00:06:24.300> personally<00:06:25.139> very 00:06:25.370 --> 00:06:25.380 align:start position:0% something I found personally very 00:06:25.380 --> 00:06:28.550 align:start position:0% something I found personally very difficult<00:06:25.620> to<00:06:25.860> do<00:06:25.979> is<00:06:26.819> is<00:06:27.060> is<00:06:27.120> uh<00:06:28.080> agile 00:06:28.550 --> 00:06:28.560 align:start position:0% difficult to do is is is uh agile 00:06:28.560 --> 00:06:30.469 align:start position:0% difficult to do is is is uh agile estimation<00:06:29.039> so<00:06:29.280> so<00:06:29.580> estimating<00:06:30.120> the<00:06:30.300> work 00:06:30.469 --> 00:06:30.479 align:start position:0% estimation so so estimating the work 00:06:30.479 --> 00:06:33.290 align:start position:0% estimation so so estimating the work effort<00:06:30.900> that<00:06:31.020> goes<00:06:31.319> into<00:06:31.380> your<00:06:31.680> tasks<00:06:32.300> and 00:06:33.290 --> 00:06:33.300 align:start position:0% effort that goes into your tasks and 00:06:33.300 --> 00:06:35.150 align:start position:0% effort that goes into your tasks and that's<00:06:33.479> really<00:06:33.660> important<00:06:34.080> to<00:06:34.259> Velocity<00:06:34.860> and 00:06:35.150 --> 00:06:35.160 align:start position:0% that's really important to Velocity and 00:06:35.160 --> 00:06:36.529 align:start position:0% that's really important to Velocity and velocity<00:06:35.639> is<00:06:35.819> really<00:06:36.000> important<00:06:36.360> to 00:06:36.529 --> 00:06:36.539 align:start position:0% velocity is really important to 00:06:36.539 --> 00:06:37.850 align:start position:0% velocity is really important to understand<00:06:36.660> like<00:06:37.199> how<00:06:37.440> is<00:06:37.560> the<00:06:37.740> team 00:06:37.850 --> 00:06:37.860 align:start position:0% understand like how is the team 00:06:37.860 --> 00:06:40.189 align:start position:0% understand like how is the team performing<00:06:38.460> are<00:06:39.060> they<00:06:39.240> able<00:06:39.600> to<00:06:39.720> deliver<00:06:39.840> on 00:06:40.189 --> 00:06:40.199 align:start position:0% performing are they able to deliver on 00:06:40.199 --> 00:06:41.689 align:start position:0% performing are they able to deliver on time<00:06:40.380> are<00:06:40.620> they<00:06:40.740> able<00:06:40.919> to<00:06:41.100> complete<00:06:41.460> all<00:06:41.580> of 00:06:41.689 --> 00:06:41.699 align:start position:0% time are they able to complete all of 00:06:41.699 --> 00:06:44.809 align:start position:0% time are they able to complete all of the<00:06:41.819> tasks<00:06:42.180> in<00:06:42.360> the<00:06:42.479> Sprint<00:06:42.860> on<00:06:43.860> time 00:06:44.809 --> 00:06:44.819 align:start position:0% the tasks in the Sprint on time 00:06:44.819 --> 00:06:47.689 align:start position:0% the tasks in the Sprint on time poor<00:06:45.539> task<00:06:45.660> estimation<00:06:46.280> often<00:06:47.280> leads<00:06:47.580> to 00:06:47.689 --> 00:06:47.699 align:start position:0% poor task estimation often leads to 00:06:47.699 --> 00:06:50.029 align:start position:0% poor task estimation often leads to sub-optimal<00:06:48.539> Velocity<00:06:48.960> and<00:06:49.620> timeline 00:06:50.029 --> 00:06:50.039 align:start position:0% sub-optimal Velocity and timeline 00:06:50.039 --> 00:06:51.350 align:start position:0% sub-optimal Velocity and timeline slipping 00:06:51.350 --> 00:06:51.360 align:start position:0% slipping 00:06:51.360 --> 00:06:52.909 align:start position:0% slipping so<00:06:51.720> I<00:06:51.840> got<00:06:51.960> to<00:06:52.080> give<00:06:52.199> a<00:06:52.319> shout<00:06:52.440> out<00:06:52.560> to<00:06:52.680> my<00:06:52.800> front 00:06:52.909 --> 00:06:52.919 align:start position:0% so I got to give a shout out to my front 00:06:52.919 --> 00:06:54.409 align:start position:0% so I got to give a shout out to my front end<00:06:53.100> team<00:06:53.280> I<00:06:53.460> don't<00:06:53.580> know<00:06:53.639> if<00:06:53.699> I<00:06:53.819> have<00:06:53.940> any<00:06:54.060> of 00:06:54.409 --> 00:06:54.419 align:start position:0% end team I don't know if I have any of 00:06:54.419 --> 00:06:56.409 align:start position:0% end team I don't know if I have any of them<00:06:54.600> here<00:06:54.840> today<00:06:55.020> but<00:06:55.380> shout<00:06:55.740> out<00:06:55.800> to<00:06:55.979> them 00:06:56.409 --> 00:06:56.419 align:start position:0% them here today but shout out to them 00:06:56.419 --> 00:06:59.870 align:start position:0% them here today but shout out to them because<00:06:57.419> we<00:06:57.720> came<00:06:57.900> up<00:06:58.080> with<00:06:58.380> this<00:06:58.880> really 00:06:59.870 --> 00:06:59.880 align:start position:0% because we came up with this really 00:06:59.880 --> 00:07:01.730 align:start position:0% because we came up with this really interesting<00:07:00.300> framework<00:07:00.840> for<00:07:01.139> estimation 00:07:01.730 --> 00:07:01.740 align:start position:0% interesting framework for estimation 00:07:01.740 --> 00:07:04.309 align:start position:0% interesting framework for estimation that<00:07:01.979> I<00:07:02.160> think<00:07:02.340> it<00:07:02.639> works<00:07:03.060> really<00:07:03.240> well<00:07:03.539> so<00:07:04.199> we 00:07:04.309 --> 00:07:04.319 align:start position:0% that I think it works really well so we 00:07:04.319 --> 00:07:06.529 align:start position:0% that I think it works really well so we kind<00:07:04.500> of<00:07:04.560> look<00:07:04.680> at<00:07:04.860> time<00:07:05.160> rough<00:07:06.000> estimate<00:07:06.419> of 00:07:06.529 --> 00:07:06.539 align:start position:0% kind of look at time rough estimate of 00:07:06.539 --> 00:07:08.870 align:start position:0% kind of look at time rough estimate of the<00:07:06.660> time<00:07:06.840> to<00:07:07.080> complete<00:07:07.440> that<00:07:07.620> user<00:07:07.979> story<00:07:08.220> or 00:07:08.870 --> 00:07:08.880 align:start position:0% the time to complete that user story or 00:07:08.880 --> 00:07:10.550 align:start position:0% the time to complete that user story or if<00:07:09.000> it's<00:07:09.120> broken<00:07:09.360> down<00:07:09.600> into<00:07:09.840> the<00:07:10.080> into<00:07:10.319> the 00:07:10.550 --> 00:07:10.560 align:start position:0% if it's broken down into the into the 00:07:10.560 --> 00:07:12.350 align:start position:0% if it's broken down into the into the development<00:07:10.919> tasks<00:07:11.340> we<00:07:12.060> look<00:07:12.240> at 00:07:12.350 --> 00:07:12.360 align:start position:0% development tasks we look at 00:07:12.360 --> 00:07:13.969 align:start position:0% development tasks we look at collaboration<00:07:12.900> costs<00:07:13.380> and<00:07:13.500> I<00:07:13.680> think<00:07:13.800> this 00:07:13.969 --> 00:07:13.979 align:start position:0% collaboration costs and I think this 00:07:13.979 --> 00:07:15.230 align:start position:0% collaboration costs and I think this might<00:07:14.160> be<00:07:14.280> something<00:07:14.460> that<00:07:14.639> might<00:07:14.819> be<00:07:14.880> new<00:07:15.060> to 00:07:15.230 --> 00:07:15.240 align:start position:0% might be something that might be new to 00:07:15.240 --> 00:07:16.670 align:start position:0% might be something that might be new to many<00:07:15.360> of<00:07:15.600> you 00:07:16.670 --> 00:07:16.680 align:start position:0% many of you 00:07:16.680 --> 00:07:19.189 align:start position:0% many of you um<00:07:17.160> the<00:07:17.759> level<00:07:17.940> of<00:07:18.120> collaboration<00:07:18.600> with<00:07:18.900> other 00:07:19.189 --> 00:07:19.199 align:start position:0% um the level of collaboration with other 00:07:19.199 --> 00:07:21.110 align:start position:0% um the level of collaboration with other teams<00:07:19.560> for<00:07:19.860> example<00:07:20.039> if<00:07:20.280> my<00:07:20.520> design<00:07:20.759> team 00:07:21.110 --> 00:07:21.120 align:start position:0% teams for example if my design team 00:07:21.120 --> 00:07:23.930 align:start position:0% teams for example if my design team needs<00:07:21.840> to<00:07:21.960> provide<00:07:22.199> new<00:07:22.380> components<00:07:22.979> if 00:07:23.930 --> 00:07:23.940 align:start position:0% needs to provide new components if 00:07:23.940 --> 00:07:26.450 align:start position:0% needs to provide new components if there's<00:07:24.180> a<00:07:24.599> lot<00:07:24.780> of<00:07:25.080> uh<00:07:25.560> you<00:07:25.740> know<00:07:25.800> if<00:07:26.099> the 00:07:26.450 --> 00:07:26.460 align:start position:0% there's a lot of uh you know if the 00:07:26.460 --> 00:07:28.010 align:start position:0% there's a lot of uh you know if the product<00:07:26.639> requirements<00:07:27.300> are<00:07:27.780> really 00:07:28.010 --> 00:07:28.020 align:start position:0% product requirements are really 00:07:28.020 --> 00:07:30.290 align:start position:0% product requirements are really intensive<00:07:28.620> and<00:07:29.160> require<00:07:29.400> a<00:07:29.639> ton<00:07:29.819> of<00:07:29.940> time<00:07:30.060> and 00:07:30.290 --> 00:07:30.300 align:start position:0% intensive and require a ton of time and 00:07:30.300 --> 00:07:32.510 align:start position:0% intensive and require a ton of time and require<00:07:30.419> lots<00:07:30.900> of<00:07:30.960> working<00:07:31.080> sessions<00:07:31.560> all<00:07:32.400> of 00:07:32.510 --> 00:07:32.520 align:start position:0% require lots of working sessions all of 00:07:32.520 --> 00:07:33.529 align:start position:0% require lots of working sessions all of those<00:07:32.639> things<00:07:32.819> are<00:07:33.060> going<00:07:33.180> to<00:07:33.300> take<00:07:33.419> away 00:07:33.529 --> 00:07:33.539 align:start position:0% those things are going to take away 00:07:33.539 --> 00:07:35.749 align:start position:0% those things are going to take away development<00:07:34.139> time<00:07:34.380> and<00:07:35.099> that<00:07:35.340> needs<00:07:35.580> to<00:07:35.639> be 00:07:35.749 --> 00:07:35.759 align:start position:0% development time and that needs to be 00:07:35.759 --> 00:07:37.730 align:start position:0% development time and that needs to be factored<00:07:36.180> in<00:07:36.360> so<00:07:37.139> that's<00:07:37.319> part<00:07:37.500> of<00:07:37.680> the 00:07:37.730 --> 00:07:37.740 align:start position:0% factored in so that's part of the 00:07:37.740 --> 00:07:40.189 align:start position:0% factored in so that's part of the collaboration<00:07:38.220> cost<00:07:38.599> the<00:07:39.599> confidence<00:07:39.900> is 00:07:40.189 --> 00:07:40.199 align:start position:0% collaboration cost the confidence is 00:07:40.199 --> 00:07:42.050 align:start position:0% collaboration cost the confidence is really<00:07:40.440> a<00:07:40.680> score<00:07:40.919> for 00:07:42.050 --> 00:07:42.060 align:start position:0% really a score for 00:07:42.060 --> 00:07:44.570 align:start position:0% really a score for the<00:07:42.720> confidence<00:07:43.020> on<00:07:43.560> the<00:07:43.860> time<00:07:44.039> estimate 00:07:44.570 --> 00:07:44.580 align:start position:0% the confidence on the time estimate 00:07:44.580 --> 00:07:47.270 align:start position:0% the confidence on the time estimate which<00:07:45.180> also<00:07:45.479> includes<00:07:45.840> complexity<00:07:46.380> and<00:07:47.099> the 00:07:47.270 --> 00:07:47.280 align:start position:0% which also includes complexity and the 00:07:47.280 --> 00:07:49.670 align:start position:0% which also includes complexity and the collaboration<00:07:47.759> cost<00:07:48.120> and<00:07:49.020> the<00:07:49.199> key<00:07:49.319> takeaway 00:07:49.670 --> 00:07:49.680 align:start position:0% collaboration cost and the key takeaway 00:07:49.680 --> 00:07:52.010 align:start position:0% collaboration cost and the key takeaway here<00:07:50.039> is<00:07:50.460> you<00:07:50.940> want<00:07:51.060> to<00:07:51.180> avoid<00:07:51.419> your<00:07:51.660> timelines 00:07:52.010 --> 00:07:52.020 align:start position:0% here is you want to avoid your timelines 00:07:52.020 --> 00:07:55.070 align:start position:0% here is you want to avoid your timelines from<00:07:52.380> blowing<00:07:52.740> up<00:07:52.860> by<00:07:53.099> having<00:07:53.340> too<00:07:53.880> many<00:07:54.080> high 00:07:55.070 --> 00:07:55.080 align:start position:0% from blowing up by having too many high 00:07:55.080 --> 00:07:57.409 align:start position:0% from blowing up by having too many high collab<00:07:55.560> and<00:07:56.160> too<00:07:56.400> many<00:07:56.520> low<00:07:56.940> confidence 00:07:57.409 --> 00:07:57.419 align:start position:0% collab and too many low confidence 00:07:57.419 --> 00:08:00.409 align:start position:0% collab and too many low confidence scoring<00:07:58.319> tasks<00:07:58.800> in<00:07:59.160> the<00:07:59.340> same<00:07:59.460> sprint<00:07:59.699> that's 00:08:00.409 --> 00:08:00.419 align:start position:0% scoring tasks in the same sprint that's 00:08:00.419 --> 00:08:01.850 align:start position:0% scoring tasks in the same sprint that's going<00:08:00.599> to<00:08:00.660> allow<00:08:00.900> the<00:08:01.080> the<00:08:01.259> development<00:08:01.620> team 00:08:01.850 --> 00:08:01.860 align:start position:0% going to allow the the development team 00:08:01.860 --> 00:08:04.129 align:start position:0% going to allow the the development team to<00:08:02.099> to<00:08:02.280> have<00:08:02.520> enough<00:08:02.759> time<00:08:03.120> to<00:08:03.780> be<00:08:03.840> able<00:08:04.020> to 00:08:04.129 --> 00:08:04.139 align:start position:0% to to have enough time to be able to 00:08:04.139 --> 00:08:06.409 align:start position:0% to to have enough time to be able to execute<00:08:04.500> the<00:08:04.740> tasks<00:08:05.099> without<00:08:05.759> getting<00:08:06.060> bogged 00:08:06.409 --> 00:08:06.419 align:start position:0% execute the tasks without getting bogged 00:08:06.419 --> 00:08:08.089 align:start position:0% execute the tasks without getting bogged down<00:08:06.539> on<00:08:06.900> a<00:08:07.020> lot<00:08:07.139> of<00:08:07.199> working<00:08:07.440> sessions<00:08:07.860> and 00:08:08.089 --> 00:08:08.099 align:start position:0% down on a lot of working sessions and 00:08:08.099 --> 00:08:11.330 align:start position:0% down on a lot of working sessions and too<00:08:08.220> many<00:08:08.400> meetings<00:08:08.759> and<00:08:08.880> stuff<00:08:09.060> like<00:08:09.300> that 00:08:11.330 --> 00:08:11.340 align:start position:0% too many meetings and stuff like that 00:08:11.340 --> 00:08:12.890 align:start position:0% too many meetings and stuff like that um<00:08:11.400> I<00:08:11.880> don't<00:08:12.000> know<00:08:12.120> if<00:08:12.240> I<00:08:12.419> have<00:08:12.539> enough<00:08:12.660> time 00:08:12.890 --> 00:08:12.900 align:start position:0% um I don't know if I have enough time 00:08:12.900 --> 00:08:14.390 align:start position:0% um I don't know if I have enough time for<00:08:13.139> simulation<00:08:13.560> modeling<00:08:13.919> so<00:08:14.099> I'm<00:08:14.220> going<00:08:14.340> to 00:08:14.390 --> 00:08:14.400 align:start position:0% for simulation modeling so I'm going to 00:08:14.400 --> 00:08:16.850 align:start position:0% for simulation modeling so I'm going to skip<00:08:14.580> this<00:08:14.819> but<00:08:15.120> this<00:08:15.479> is<00:08:15.599> a<00:08:15.780> topic<00:08:16.500> that's 00:08:16.850 --> 00:08:16.860 align:start position:0% skip this but this is a topic that's 00:08:16.860 --> 00:08:19.369 align:start position:0% skip this but this is a topic that's very<00:08:17.580> near<00:08:17.819> and<00:08:18.060> dear<00:08:18.360> to<00:08:18.479> my<00:08:18.660> heart<00:08:18.780> so<00:08:19.020> if<00:08:19.199> you 00:08:19.369 --> 00:08:19.379 align:start position:0% very near and dear to my heart so if you 00:08:19.379 --> 00:08:21.529 align:start position:0% very near and dear to my heart so if you have<00:08:19.500> questions<00:08:19.800> we<00:08:20.759> can<00:08:20.879> address<00:08:21.060> them<00:08:21.360> a 00:08:21.529 --> 00:08:21.539 align:start position:0% have questions we can address them a 00:08:21.539 --> 00:08:23.869 align:start position:0% have questions we can address them a little<00:08:21.660> bit<00:08:21.780> later<00:08:22.220> but<00:08:23.220> I'll<00:08:23.460> just<00:08:23.639> quickly 00:08:23.869 --> 00:08:23.879 align:start position:0% little bit later but I'll just quickly 00:08:23.879 --> 00:08:25.730 align:start position:0% little bit later but I'll just quickly touch<00:08:24.060> on<00:08:24.300> tools<00:08:24.599> like<00:08:24.780> hat<00:08:25.080> cat<00:08:25.199> Gauntlet 00:08:25.730 --> 00:08:25.740 align:start position:0% touch on tools like hat cat Gauntlet 00:08:25.740 --> 00:08:27.890 align:start position:0% touch on tools like hat cat Gauntlet token<00:08:26.160> spice<00:08:26.460> all<00:08:27.120> of<00:08:27.240> these<00:08:27.419> things<00:08:27.539> I<00:08:27.780> do 00:08:27.890 --> 00:08:27.900 align:start position:0% token spice all of these things I do 00:08:27.900 --> 00:08:30.230 align:start position:0% token spice all of these things I do encourage<00:08:28.259> everyone<00:08:28.500> to<00:08:28.979> to<00:08:29.639> kind<00:08:29.879> of<00:08:30.000> take<00:08:30.120> a 00:08:30.230 --> 00:08:30.240 align:start position:0% encourage everyone to to kind of take a 00:08:30.240 --> 00:08:32.449 align:start position:0% encourage everyone to to kind of take a look<00:08:30.300> at<00:08:30.479> and<00:08:30.720> explore<00:08:30.960> on<00:08:31.139> their<00:08:31.319> own 00:08:32.449 --> 00:08:32.459 align:start position:0% look at and explore on their own 00:08:32.459 --> 00:08:35.269 align:start position:0% look at and explore on their own product<00:08:32.760> Market<00:08:33.060> fit<00:08:34.020> in<00:08:34.200> kpis<00:08:34.740> really 00:08:35.269 --> 00:08:35.279 align:start position:0% product Market fit in kpis really 00:08:35.279 --> 00:08:37.310 align:start position:0% product Market fit in kpis really important<00:08:35.640> this<00:08:35.880> is<00:08:36.000> something<00:08:36.240> my<00:08:37.020> team<00:08:37.140> has 00:08:37.310 --> 00:08:37.320 align:start position:0% important this is something my team has 00:08:37.320 --> 00:08:40.550 align:start position:0% important this is something my team has been<00:08:37.500> spending<00:08:37.860> a<00:08:38.099> lot<00:08:38.219> of<00:08:38.399> time<00:08:38.580> on<00:08:38.760> lately 00:08:40.550 --> 00:08:40.560 align:start position:0% been spending a lot of time on lately 00:08:40.560 --> 00:08:43.070 align:start position:0% been spending a lot of time on lately um<00:08:40.680> and<00:08:41.339> what's<00:08:41.880> the<00:08:42.120> common<00:08:42.240> metric<00:08:42.719> across 00:08:43.070 --> 00:08:43.080 align:start position:0% um and what's the common metric across 00:08:43.080 --> 00:08:46.310 align:start position:0% um and what's the common metric across D5<00:08:43.440> right<00:08:43.680> now<00:08:43.800> right<00:08:44.039> it's<00:08:44.219> tvl<00:08:45.200> total<00:08:46.200> value 00:08:46.310 --> 00:08:46.320 align:start position:0% D5 right now right it's tvl total value 00:08:46.320 --> 00:08:48.829 align:start position:0% D5 right now right it's tvl total value locked<00:08:46.800> right<00:08:47.100> it's<00:08:47.519> it's<00:08:47.820> a<00:08:48.060> good<00:08:48.180> metric<00:08:48.600> is 00:08:48.829 --> 00:08:48.839 align:start position:0% locked right it's it's a good metric is 00:08:48.839 --> 00:08:51.769 align:start position:0% locked right it's it's a good metric is it<00:08:49.019> a<00:08:49.140> great<00:08:49.260> metric<00:08:49.680> I<00:08:50.100> don't<00:08:50.220> think<00:08:50.399> so<00:08:50.779> it's 00:08:51.769 --> 00:08:51.779 align:start position:0% it a great metric I don't think so it's 00:08:51.779 --> 00:08:53.690 align:start position:0% it a great metric I don't think so it's a<00:08:51.959> good<00:08:52.080> metric<00:08:52.440> when<00:08:52.680> it's<00:08:52.860> taken<00:08:53.220> in<00:08:53.519> concert 00:08:53.690 --> 00:08:53.700 align:start position:0% a good metric when it's taken in concert 00:08:53.700 --> 00:08:56.690 align:start position:0% a good metric when it's taken in concert with<00:08:54.120> other<00:08:54.300> metrics<00:08:55.100> alone<00:08:56.100> I<00:08:56.519> don't<00:08:56.580> think 00:08:56.690 --> 00:08:56.700 align:start position:0% with other metrics alone I don't think 00:08:56.700 --> 00:08:58.190 align:start position:0% with other metrics alone I don't think it's<00:08:56.880> sufficient<00:08:57.240> to<00:08:57.420> give<00:08:57.540> you<00:08:57.660> a<00:08:57.899> good<00:08:57.959> good 00:08:58.190 --> 00:08:58.200 align:start position:0% it's sufficient to give you a good good 00:08:58.200 --> 00:09:01.310 align:start position:0% it's sufficient to give you a good good idea<00:08:58.560> of<00:08:58.740> product<00:08:58.860> Market<00:08:59.100> fit<00:08:59.519> so<00:09:00.360> tvl<00:09:00.899> is<00:09:01.140> not 00:09:01.310 --> 00:09:01.320 align:start position:0% idea of product Market fit so tvl is not 00:09:01.320 --> 00:09:04.190 align:start position:0% idea of product Market fit so tvl is not really<00:09:01.500> sticky<00:09:02.420> Traders<00:09:03.420> often<00:09:03.720> look<00:09:03.899> for<00:09:04.019> the 00:09:04.190 --> 00:09:04.200 align:start position:0% really sticky Traders often look for the 00:09:04.200 --> 00:09:06.350 align:start position:0% really sticky Traders often look for the best<00:09:04.320> yields<00:09:04.680> across<00:09:04.980> D5<00:09:05.399> so<00:09:05.700> loyalty<00:09:06.240> is 00:09:06.350 --> 00:09:06.360 align:start position:0% best yields across D5 so loyalty is 00:09:06.360 --> 00:09:08.449 align:start position:0% best yields across D5 so loyalty is fickle<00:09:06.839> and<00:09:07.440> that<00:09:07.560> cause<00:09:07.740> that<00:09:07.980> can<00:09:08.160> cause<00:09:08.279> a 00:09:08.449 --> 00:09:08.459 align:start position:0% fickle and that cause that can cause a 00:09:08.459 --> 00:09:12.290 align:start position:0% fickle and that cause that can cause a lot<00:09:08.580> of<00:09:08.700> volatility<00:09:09.120> in<00:09:09.420> the<00:09:09.540> tvl<00:09:10.160> tvl<00:09:11.160> is<00:09:11.519> also 00:09:12.290 --> 00:09:12.300 align:start position:0% lot of volatility in the tvl tvl is also 00:09:12.300 --> 00:09:14.329 align:start position:0% lot of volatility in the tvl tvl is also um<00:09:12.839> subject<00:09:13.560> to<00:09:13.740> a<00:09:13.920> lot<00:09:14.040> of<00:09:14.160> Market 00:09:14.329 --> 00:09:14.339 align:start position:0% um subject to a lot of Market 00:09:14.339 --> 00:09:16.190 align:start position:0% um subject to a lot of Market cyclicality 00:09:16.190 --> 00:09:16.200 align:start position:0% cyclicality 00:09:16.200 --> 00:09:17.889 align:start position:0% cyclicality bull<00:09:16.920> bear 00:09:17.889 --> 00:09:17.899 align:start position:0% bull bear 00:09:17.899 --> 00:09:20.829 align:start position:0% bull bear and<00:09:18.899> it's<00:09:19.140> just<00:09:19.380> not<00:09:19.500> a<00:09:19.740> good<00:09:19.860> long-term 00:09:20.829 --> 00:09:20.839 align:start position:0% and it's just not a good long-term 00:09:20.839 --> 00:09:22.850 align:start position:0% and it's just not a good long-term metric<00:09:21.839> to<00:09:22.140> measure<00:09:22.380> long-term 00:09:22.850 --> 00:09:22.860 align:start position:0% metric to measure long-term 00:09:22.860 --> 00:09:24.590 align:start position:0% metric to measure long-term sustainability<00:09:23.339> health<00:09:23.700> and<00:09:23.940> success<00:09:24.240> of<00:09:24.480> a 00:09:24.590 --> 00:09:24.600 align:start position:0% sustainability health and success of a 00:09:24.600 --> 00:09:26.690 align:start position:0% sustainability health and success of a protocol<00:09:24.899> so<00:09:25.440> again<00:09:25.500> it's<00:09:25.800> not<00:09:25.980> a<00:09:26.160> bad<00:09:26.279> metric 00:09:26.690 --> 00:09:26.700 align:start position:0% protocol so again it's not a bad metric 00:09:26.700 --> 00:09:29.810 align:start position:0% protocol so again it's not a bad metric but<00:09:27.480> it<00:09:27.660> should<00:09:27.779> be<00:09:27.959> taken<00:09:28.459> alongside<00:09:29.459> other 00:09:29.810 --> 00:09:29.820 align:start position:0% but it should be taken alongside other 00:09:29.820 --> 00:09:32.389 align:start position:0% but it should be taken alongside other key<00:09:30.120> metrics<00:09:30.660> which<00:09:31.500> I'll<00:09:31.680> touch<00:09:31.980> on<00:09:32.160> very 00:09:32.389 --> 00:09:32.399 align:start position:0% key metrics which I'll touch on very 00:09:32.399 --> 00:09:35.690 align:start position:0% key metrics which I'll touch on very quickly<00:09:32.959> ecosystem<00:09:33.959> engagement<00:09:34.440> metrics<00:09:35.100> are 00:09:35.690 --> 00:09:35.700 align:start position:0% quickly ecosystem engagement metrics are 00:09:35.700 --> 00:09:37.030 align:start position:0% quickly ecosystem engagement metrics are crucial 00:09:37.030 --> 00:09:37.040 align:start position:0% crucial 00:09:37.040 --> 00:09:39.530 align:start position:0% crucial understanding<00:09:38.040> Community<00:09:38.640> engagement<00:09:39.180> and 00:09:39.530 --> 00:09:39.540 align:start position:0% understanding Community engagement and 00:09:39.540 --> 00:09:41.990 align:start position:0% understanding Community engagement and frequency<00:09:40.160> developer<00:09:41.160> activity<00:09:41.580> are<00:09:41.880> there 00:09:41.990 --> 00:09:42.000 align:start position:0% frequency developer activity are there 00:09:42.000 --> 00:09:44.090 align:start position:0% frequency developer activity are there other<00:09:42.180> developers<00:09:42.720> building<00:09:43.140> on<00:09:43.620> top<00:09:43.740> of<00:09:43.980> your 00:09:44.090 --> 00:09:44.100 align:start position:0% other developers building on top of your 00:09:44.100 --> 00:09:45.550 align:start position:0% other developers building on top of your protocol 00:09:45.550 --> 00:09:45.560 align:start position:0% protocol 00:09:45.560 --> 00:09:48.110 align:start position:0% protocol Integrations<00:09:46.560> are<00:09:47.100> there<00:09:47.220> other<00:09:47.459> protocols 00:09:48.110 --> 00:09:48.120 align:start position:0% Integrations are there other protocols 00:09:48.120 --> 00:09:50.090 align:start position:0% Integrations are there other protocols integrating<00:09:48.660> with<00:09:48.959> your<00:09:49.200> protocol<00:09:49.500> those<00:09:49.920> are 00:09:50.090 --> 00:09:50.100 align:start position:0% integrating with your protocol those are 00:09:50.100 --> 00:09:51.410 align:start position:0% integrating with your protocol those are really<00:09:50.339> strong<00:09:50.519> indicators<00:09:51.060> of<00:09:51.300> product 00:09:51.410 --> 00:09:51.420 align:start position:0% really strong indicators of product 00:09:51.420 --> 00:09:53.570 align:start position:0% really strong indicators of product Market<00:09:51.660> fit<00:09:52.080> and<00:09:52.860> the<00:09:52.980> number<00:09:53.100> of<00:09:53.279> unique 00:09:53.570 --> 00:09:53.580 align:start position:0% Market fit and the number of unique 00:09:53.580 --> 00:09:56.329 align:start position:0% Market fit and the number of unique token<00:09:53.940> holders<00:09:54.300> so<00:09:55.019> if<00:09:55.440> the<00:09:55.740> the<00:09:55.920> token 00:09:56.329 --> 00:09:56.339 align:start position:0% token holders so if the the token 00:09:56.339 --> 00:09:58.910 align:start position:0% token holders so if the the token distribution<00:09:56.760> is<00:09:57.360> is<00:09:57.600> really<00:09:57.899> high<00:09:58.200> and<00:09:58.680> you 00:09:58.910 --> 00:09:58.920 align:start position:0% distribution is is really high and you 00:09:58.920 --> 00:10:01.250 align:start position:0% distribution is is really high and you know<00:09:58.980> you<00:09:59.100> have<00:09:59.279> a<00:09:59.580> very<00:09:59.700> decentralized<00:10:00.300> token 00:10:01.250 --> 00:10:01.260 align:start position:0% know you have a very decentralized token 00:10:01.260 --> 00:10:03.410 align:start position:0% know you have a very decentralized token economy<00:10:01.680> you<00:10:02.519> might<00:10:02.640> have<00:10:02.880> more 00:10:03.410 --> 00:10:03.420 align:start position:0% economy you might have more 00:10:03.420 --> 00:10:05.870 align:start position:0% economy you might have more participation<00:10:04.019> in<00:10:04.260> governance<00:10:04.680> and<00:10:05.519> you<00:10:05.700> just 00:10:05.870 --> 00:10:05.880 align:start position:0% participation in governance and you just 00:10:05.880 --> 00:10:07.070 align:start position:0% participation in governance and you just have<00:10:06.060> you<00:10:06.420> know 00:10:07.070 --> 00:10:07.080 align:start position:0% have you know 00:10:07.080 --> 00:10:09.530 align:start position:0% have you know more<00:10:07.740> participation<00:10:08.339> in<00:10:08.880> in<00:10:09.120> the<00:10:09.300> protocol 00:10:09.530 --> 00:10:09.540 align:start position:0% more participation in in the protocol 00:10:09.540 --> 00:10:12.230 align:start position:0% more participation in in the protocol that's<00:10:10.380> also<00:10:10.680> a<00:10:10.800> really<00:10:10.920> good<00:10:11.040> sign<00:10:11.220> as<00:10:11.519> well 00:10:12.230 --> 00:10:12.240 align:start position:0% that's also a really good sign as well 00:10:12.240 --> 00:10:15.350 align:start position:0% that's also a really good sign as well product<00:10:12.720> engagement<00:10:13.200> metrics<00:10:13.860> like<00:10:14.640> daily 00:10:15.350 --> 00:10:15.360 align:start position:0% product engagement metrics like daily 00:10:15.360 --> 00:10:17.630 align:start position:0% product engagement metrics like daily active<00:10:15.779> users<00:10:16.140> or<00:10:16.440> daily<00:10:16.680> active<00:10:17.100> addresses 00:10:17.630 --> 00:10:17.640 align:start position:0% active users or daily active addresses 00:10:17.640 --> 00:10:20.930 align:start position:0% active users or daily active addresses churn<00:10:18.480> and<00:10:18.720> retention<00:10:19.019> metrics<00:10:19.580> user<00:10:20.580> actions 00:10:20.930 --> 00:10:20.940 align:start position:0% churn and retention metrics user actions 00:10:20.940 --> 00:10:22.610 align:start position:0% churn and retention metrics user actions like<00:10:21.120> in<00:10:21.240> a<00:10:21.360> D5<00:10:21.600> protocol<00:10:21.959> you<00:10:22.200> often<00:10:22.500> have 00:10:22.610 --> 00:10:22.620 align:start position:0% like in a D5 protocol you often have 00:10:22.620 --> 00:10:26.570 align:start position:0% like in a D5 protocol you often have users<00:10:23.100> depositing<00:10:23.760> trading<00:10:24.480> redeeming<00:10:25.580> and 00:10:26.570 --> 00:10:26.580 align:start position:0% users depositing trading redeeming and 00:10:26.580 --> 00:10:27.829 align:start position:0% users depositing trading redeeming and other<00:10:26.760> types<00:10:27.060> of<00:10:27.120> metrics<00:10:27.480> are<00:10:27.660> really 00:10:27.829 --> 00:10:27.839 align:start position:0% other types of metrics are really 00:10:27.839 --> 00:10:29.269 align:start position:0% other types of metrics are really important 00:10:29.269 --> 00:10:29.279 align:start position:0% important 00:10:29.279 --> 00:10:30.410 align:start position:0% important um 00:10:30.410 --> 00:10:30.420 align:start position:0% um 00:10:30.420 --> 00:10:33.230 align:start position:0% um I'm<00:10:30.779> going<00:10:30.959> to<00:10:30.959> skip<00:10:31.140> over<00:10:31.260> this<00:10:31.500> for<00:10:31.680> time 00:10:33.230 --> 00:10:33.240 align:start position:0% I'm going to skip over this for time 00:10:33.240 --> 00:10:34.630 align:start position:0% I'm going to skip over this for time because<00:10:33.540> I'm<00:10:33.779> down<00:10:33.959> to<00:10:34.080> a<00:10:34.200> minute<00:10:34.320> and<00:10:34.440> a<00:10:34.620> half 00:10:34.630 --> 00:10:34.640 align:start position:0% because I'm down to a minute and a half 00:10:34.640 --> 00:10:37.550 align:start position:0% because I'm down to a minute and a half but<00:10:35.640> how<00:10:36.180> do<00:10:36.300> we<00:10:36.420> measure<00:10:36.899> some<00:10:37.320> of<00:10:37.440> these 00:10:37.550 --> 00:10:37.560 align:start position:0% but how do we measure some of these 00:10:37.560 --> 00:10:38.769 align:start position:0% but how do we measure some of these metrics 00:10:38.769 --> 00:10:38.779 align:start position:0% metrics 00:10:38.779 --> 00:10:41.449 align:start position:0% metrics it's<00:10:39.779> really<00:10:39.959> important<00:10:40.440> so<00:10:40.920> first<00:10:41.160> of<00:10:41.339> all 00:10:41.449 --> 00:10:41.459 align:start position:0% it's really important so first of all 00:10:41.459 --> 00:10:43.250 align:start position:0% it's really important so first of all you<00:10:41.940> may<00:10:42.060> not<00:10:42.240> know<00:10:42.360> this<00:10:42.540> or<00:10:42.779> maybe<00:10:42.959> you<00:10:43.140> do 00:10:43.250 --> 00:10:43.260 align:start position:0% you may not know this or maybe you do 00:10:43.260 --> 00:10:45.350 align:start position:0% you may not know this or maybe you do but<00:10:43.500> a<00:10:43.740> lot<00:10:43.860> of<00:10:43.980> D5<00:10:44.220> projects<00:10:44.700> out<00:10:44.880> there<00:10:45.000> like 00:10:45.350 --> 00:10:45.360 align:start position:0% but a lot of D5 projects out there like 00:10:45.360 --> 00:10:49.250 align:start position:0% but a lot of D5 projects out there like maker<00:10:46.200> Ave<00:10:46.380> uniswap<00:10:47.040> dydx<00:10:47.779> are<00:10:48.779> collecting 00:10:49.250 --> 00:10:49.260 align:start position:0% maker Ave uniswap dydx are collecting 00:10:49.260 --> 00:10:51.530 align:start position:0% maker Ave uniswap dydx are collecting user<00:10:49.560> data<00:10:49.800> mind<00:10:50.100> you<00:10:50.339> most<00:10:50.760> of<00:10:50.940> them<00:10:51.060> have<00:10:51.300> the 00:10:51.530 --> 00:10:51.540 align:start position:0% user data mind you most of them have the 00:10:51.540 --> 00:10:53.569 align:start position:0% user data mind you most of them have the Privacy<00:10:51.899> flag<00:10:52.200> turned<00:10:53.100> on<00:10:53.220> which<00:10:53.459> is 00:10:53.569 --> 00:10:53.579 align:start position:0% Privacy flag turned on which is 00:10:53.579 --> 00:10:55.009 align:start position:0% Privacy flag turned on which is something<00:10:53.700> you<00:10:53.940> can<00:10:54.060> do<00:10:54.180> in<00:10:54.360> Google<00:10:54.480> analytics 00:10:55.009 --> 00:10:55.019 align:start position:0% something you can do in Google analytics 00:10:55.019 --> 00:10:58.610 align:start position:0% something you can do in Google analytics and<00:10:55.260> other<00:10:55.500> tools<00:10:56.160> like<00:10:56.279> mixpanel<00:10:57.500> but<00:10:58.500> they 00:10:58.610 --> 00:10:58.620 align:start position:0% and other tools like mixpanel but they 00:10:58.620 --> 00:11:00.530 align:start position:0% and other tools like mixpanel but they are<00:10:58.740> collecting<00:10:59.160> user<00:10:59.459> data<00:10:59.700> it's<00:10:59.940> anonymized 00:11:00.530 --> 00:11:00.540 align:start position:0% are collecting user data it's anonymized 00:11:00.540 --> 00:11:03.230 align:start position:0% are collecting user data it's anonymized data<00:11:00.779> it's<00:11:00.959> really<00:11:01.260> important<00:11:01.800> for<00:11:02.399> informing 00:11:03.230 --> 00:11:03.240 align:start position:0% data it's really important for informing 00:11:03.240 --> 00:11:04.930 align:start position:0% data it's really important for informing product<00:11:03.540> decisions 00:11:04.930 --> 00:11:04.940 align:start position:0% product decisions 00:11:04.940 --> 00:11:07.730 align:start position:0% product decisions app<00:11:05.940> and<00:11:06.240> protocol<00:11:06.540> evolution 00:11:07.730 --> 00:11:07.740 align:start position:0% app and protocol evolution 00:11:07.740 --> 00:11:09.949 align:start position:0% app and protocol evolution and<00:11:08.279> optimizing<00:11:08.880> marketing<00:11:09.240> efforts<00:11:09.600> as<00:11:09.779> well 00:11:09.949 --> 00:11:09.959 align:start position:0% and optimizing marketing efforts as well 00:11:09.959 --> 00:11:12.530 align:start position:0% and optimizing marketing efforts as well what's<00:11:10.800> really<00:11:11.040> important<00:11:11.459> is<00:11:11.880> that<00:11:12.120> you've 00:11:12.530 --> 00:11:12.540 align:start position:0% what's really important is that you've 00:11:12.540 --> 00:11:14.449 align:start position:0% what's really important is that you've integrated<00:11:12.899> consent<00:11:13.380> management<00:11:13.680> right<00:11:14.220> this 00:11:14.449 --> 00:11:14.459 align:start position:0% integrated consent management right this 00:11:14.459 --> 00:11:16.130 align:start position:0% integrated consent management right this kind<00:11:14.640> of<00:11:14.760> fits<00:11:14.940> within<00:11:15.180> the<00:11:15.300> ethos<00:11:15.600> of<00:11:15.779> web3 00:11:16.130 --> 00:11:16.140 align:start position:0% kind of fits within the ethos of web3 00:11:16.140 --> 00:11:18.470 align:start position:0% kind of fits within the ethos of web3 where<00:11:16.980> users<00:11:17.339> have<00:11:17.579> full<00:11:17.760> control<00:11:18.000> over<00:11:18.240> the 00:11:18.470 --> 00:11:18.480 align:start position:0% where users have full control over the 00:11:18.480 --> 00:11:20.710 align:start position:0% where users have full control over the over<00:11:18.720> their<00:11:18.899> data<00:11:19.260> if<00:11:19.860> they<00:11:20.040> want<00:11:20.160> to<00:11:20.339> opt<00:11:20.459> out 00:11:20.710 --> 00:11:20.720 align:start position:0% over their data if they want to opt out 00:11:20.720 --> 00:11:23.269 align:start position:0% over their data if they want to opt out of<00:11:21.720> anonymous<00:11:22.140> data<00:11:22.440> collection<00:11:22.680> you<00:11:23.040> need<00:11:23.160> to 00:11:23.269 --> 00:11:23.279 align:start position:0% of anonymous data collection you need to 00:11:23.279 --> 00:11:25.430 align:start position:0% of anonymous data collection you need to give<00:11:23.399> them<00:11:23.579> that<00:11:23.820> that<00:11:24.120> opportunity<00:11:24.660> to<00:11:25.019> do 00:11:25.430 --> 00:11:25.440 align:start position:0% give them that that opportunity to do 00:11:25.440 --> 00:11:26.210 align:start position:0% give them that that opportunity to do that 00:11:26.210 --> 00:11:26.220 align:start position:0% that 00:11:26.220 --> 00:11:28.490 align:start position:0% that and<00:11:26.700> then<00:11:27.060> you<00:11:27.300> know<00:11:27.420> open<00:11:27.600> source<00:11:27.959> tooling<00:11:28.320> is 00:11:28.490 --> 00:11:28.500 align:start position:0% and then you know open source tooling is 00:11:28.500 --> 00:11:30.949 align:start position:0% and then you know open source tooling is better<00:11:28.680> I<00:11:29.100> mean<00:11:29.279> than<00:11:29.700> than<00:11:30.060> closed<00:11:30.540> source<00:11:30.839> of 00:11:30.949 --> 00:11:30.959 align:start position:0% better I mean than than closed source of 00:11:30.959 --> 00:11:32.990 align:start position:0% better I mean than than closed source of course<00:11:31.079> and 00:11:32.990 --> 00:11:33.000 align:start position:0% course and 00:11:33.000 --> 00:11:36.530 align:start position:0% course and um<00:11:33.120> the<00:11:33.660> the<00:11:33.899> kind<00:11:34.200> of<00:11:34.380> uh<00:11:35.040> uh<00:11:35.820> the<00:11:36.120> the<00:11:36.120> tech 00:11:36.530 --> 00:11:36.540 align:start position:0% um the the kind of uh uh the the tech 00:11:36.540 --> 00:11:38.810 align:start position:0% um the the kind of uh uh the the tech stack<00:11:36.839> that<00:11:36.959> I've<00:11:37.140> outlined<00:11:37.500> here<00:11:37.740> is<00:11:38.579> a 00:11:38.810 --> 00:11:38.820 align:start position:0% stack that I've outlined here is a 00:11:38.820 --> 00:11:41.389 align:start position:0% stack that I've outlined here is a typical<00:11:39.120> product<00:11:39.680> marketing<00:11:40.680> analytics<00:11:41.100> Tech 00:11:41.389 --> 00:11:41.399 align:start position:0% typical product marketing analytics Tech 00:11:41.399 --> 00:11:43.190 align:start position:0% typical product marketing analytics Tech stack<00:11:41.700> that<00:11:42.120> we<00:11:42.480> could<00:11:42.600> use<00:11:42.720> that<00:11:42.899> includes 00:11:43.190 --> 00:11:43.200 align:start position:0% stack that we could use that includes 00:11:43.200 --> 00:11:45.410 align:start position:0% stack that we could use that includes all<00:11:43.440> open<00:11:43.620> source<00:11:44.040> tools 00:11:45.410 --> 00:11:45.420 align:start position:0% all open source tools 00:11:45.420 --> 00:11:47.389 align:start position:0% all open source tools um<00:11:45.480> and<00:11:46.079> I'm<00:11:46.320> happy<00:11:46.500> to<00:11:46.680> chat<00:11:46.920> about<00:11:47.040> that<00:11:47.220> a 00:11:47.389 --> 00:11:47.399 align:start position:0% um and I'm happy to chat about that a 00:11:47.399 --> 00:11:49.009 align:start position:0% um and I'm happy to chat about that a little<00:11:47.519> bit<00:11:47.640> more<00:11:47.880> uh<00:11:48.360> later<00:11:48.540> because<00:11:48.779> I<00:11:48.899> know 00:11:49.009 --> 00:11:49.019 align:start position:0% little bit more uh later because I know 00:11:49.019 --> 00:11:50.630 align:start position:0% little bit more uh later because I know I'm<00:11:49.140> just<00:11:49.320> down<00:11:49.500> to<00:11:49.620> a<00:11:49.800> couple<00:11:49.860> a<00:11:50.459> couple 00:11:50.630 --> 00:11:50.640 align:start position:0% I'm just down to a couple a couple 00:11:50.640 --> 00:11:52.069 align:start position:0% I'm just down to a couple a couple seconds 00:11:52.069 --> 00:11:52.079 align:start position:0% seconds 00:11:52.079 --> 00:11:53.990 align:start position:0% seconds um but<00:11:52.320> yeah<00:11:52.440> feel<00:11:52.620> free<00:11:52.800> to<00:11:52.980> follow<00:11:53.459> me<00:11:53.640> on<00:11:53.820> on 00:11:53.990 --> 00:11:54.000 align:start position:0% um but yeah feel free to follow me on on 00:11:54.000 --> 00:11:56.150 align:start position:0% um but yeah feel free to follow me on on Twitter<00:11:54.240> elements<00:11:55.140> underscore<00:11:55.620> Phi<00:11:55.980> on 00:11:56.150 --> 00:11:56.160 align:start position:0% Twitter elements underscore Phi on 00:11:56.160 --> 00:11:57.949 align:start position:0% Twitter elements underscore Phi on Twitter<00:11:56.279> as<00:11:56.579> well<00:11:56.700> I'll<00:11:57.240> have<00:11:57.420> a<00:11:57.540> blog<00:11:57.839> post 00:11:57.949 --> 00:11:57.959 align:start position:0% Twitter as well I'll have a blog post 00:11:57.959 --> 00:11:59.449 align:start position:0% Twitter as well I'll have a blog post coming<00:11:58.200> out<00:11:58.380> which<00:11:58.680> will<00:11:58.800> be<00:11:59.040> very 00:11:59.449 --> 00:11:59.459 align:start position:0% coming out which will be very 00:11:59.459 --> 00:12:01.790 align:start position:0% coming out which will be very comprehensive<00:12:00.060> and<00:12:00.779> cover<00:12:00.959> all<00:12:01.320> of<00:12:01.380> this<00:12:01.560> in 00:12:01.790 --> 00:12:01.800 align:start position:0% comprehensive and cover all of this in 00:12:01.800 --> 00:12:03.949 align:start position:0% comprehensive and cover all of this in much<00:12:01.980> much<00:12:02.100> more<00:12:02.339> detail<00:12:02.760> so<00:12:03.360> stay<00:12:03.600> tuned<00:12:03.839> for 00:12:03.949 --> 00:12:03.959 align:start position:0% much much more detail so stay tuned for 00:12:03.959 --> 00:12:05.990 align:start position:0% much much more detail so stay tuned for that<00:12:04.079> as<00:12:04.260> well<00:12:04.440> and<00:12:05.160> uh<00:12:05.339> happy<00:12:05.579> to<00:12:05.760> take<00:12:05.820> any 00:12:05.990 --> 00:12:06.000 align:start position:0% that as well and uh happy to take any 00:12:06.000 --> 00:12:09.019 align:start position:0% that as well and uh happy to take any questions<00:12:06.180> if<00:12:06.420> we<00:12:06.540> have<00:12:06.660> any<00:12:06.779> time