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:16.730 align:start position:0% [Music] 00:00:16.730 --> 00:00:16.740 align:start position:0% 00:00:16.740 --> 00:00:20.450 align:start position:0% hello<00:00:17.340> everyone 00:00:20.450 --> 00:00:20.460 align:start position:0% 00:00:20.460 --> 00:00:24.950 align:start position:0% we<00:00:21.119> have<00:00:21.300> encountered<00:00:22.020> some<00:00:22.880> issues<00:00:23.880> but 00:00:24.950 --> 00:00:24.960 align:start position:0% we have encountered some issues but 00:00:24.960 --> 00:00:27.769 align:start position:0% we have encountered some issues but as<00:00:25.740> designers<00:00:26.340> and<00:00:26.640> researchers<00:00:27.240> we<00:00:27.599> are 00:00:27.769 --> 00:00:27.779 align:start position:0% as designers and researchers we are 00:00:27.779 --> 00:00:29.929 align:start position:0% as designers and researchers we are accustomed<00:00:28.260> to<00:00:28.380> this<00:00:28.619> basically<00:00:29.460> we<00:00:29.760> have 00:00:29.929 --> 00:00:29.939 align:start position:0% accustomed to this basically we have 00:00:29.939 --> 00:00:36.049 align:start position:0% accustomed to this basically we have iterated<00:00:30.539> so 00:00:36.049 --> 00:00:36.059 align:start position:0% 00:00:36.059 --> 00:00:39.770 align:start position:0% good<00:00:36.660> to<00:00:36.780> see<00:00:36.960> so<00:00:37.200> many<00:00:37.380> new<00:00:37.739> faces<00:00:38.239> uh<00:00:39.239> I<00:00:39.480> am<00:00:39.600> a 00:00:39.770 --> 00:00:39.780 align:start position:0% good to see so many new faces uh I am a 00:00:39.780 --> 00:00:42.110 align:start position:0% good to see so many new faces uh I am a product<00:00:39.960> designer<00:00:40.559> and<00:00:40.860> a<00:00:41.040> researcher<00:00:41.520> I<00:00:41.940> am 00:00:42.110 --> 00:00:42.120 align:start position:0% product designer and a researcher I am 00:00:42.120 --> 00:00:45.410 align:start position:0% product designer and a researcher I am one<00:00:42.360> of<00:00:42.480> the<00:00:42.719> co-founders<00:00:43.500> of<00:00:43.860> the<00:00:44.219> web3<00:00:44.940> ux 00:00:45.410 --> 00:00:45.420 align:start position:0% one of the co-founders of the web3 ux 00:00:45.420 --> 00:00:48.650 align:start position:0% one of the co-founders of the web3 ux user<00:00:45.899> research<00:00:46.260> panels<00:00:46.820> and<00:00:47.820> I<00:00:48.120> am<00:00:48.300> leading 00:00:48.650 --> 00:00:48.660 align:start position:0% user research panels and I am leading 00:00:48.660 --> 00:00:51.709 align:start position:0% user research panels and I am leading the<00:00:48.960> ux<00:00:49.379> design<00:00:49.860> and<00:00:50.219> ux<00:00:50.579> research<00:00:51.120> for<00:00:51.480> the 00:00:51.709 --> 00:00:51.719 align:start position:0% the ux design and ux research for the 00:00:51.719 --> 00:00:54.350 align:start position:0% the ux design and ux research for the threshold<00:00:52.140> Network<00:00:52.460> which<00:00:53.460> was<00:00:53.700> formerly 00:00:54.350 --> 00:00:54.360 align:start position:0% threshold Network which was formerly 00:00:54.360 --> 00:00:57.709 align:start position:0% threshold Network which was formerly known<00:00:54.719> as<00:00:55.199> keep<00:00:55.440> Network<00:00:55.739> and<00:00:56.160> new<00:00:56.340> Cipher<00:00:56.820> I 00:00:57.709 --> 00:00:57.719 align:start position:0% known as keep Network and new Cipher I 00:00:57.719 --> 00:01:00.970 align:start position:0% known as keep Network and new Cipher I am<00:00:57.899> also<00:00:58.379> part<00:00:58.860> of<00:00:59.160> the<00:00:59.579> team<00:01:00.120> who's<00:01:00.539> building 00:01:00.970 --> 00:01:00.980 align:start position:0% am also part of the team who's building 00:01:00.980 --> 00:01:03.950 align:start position:0% am also part of the team who's building tbtc<00:01:01.980> which<00:01:02.940> is<00:01:03.120> the<00:01:03.420> first<00:01:03.539> fully 00:01:03.950 --> 00:01:03.960 align:start position:0% tbtc which is the first fully 00:01:03.960 --> 00:01:06.950 align:start position:0% tbtc which is the first fully decentralized<00:01:04.799> Bitcoin<00:01:05.339> to<00:01:05.460> ethereum<00:01:05.939> bridge 00:01:06.950 --> 00:01:06.960 align:start position:0% decentralized Bitcoin to ethereum bridge 00:01:06.960 --> 00:01:11.149 align:start position:0% decentralized Bitcoin to ethereum bridge I<00:01:07.799> like<00:01:08.040> to<00:01:08.340> say<00:01:08.700> about<00:01:09.240> my<00:01:09.659> job<00:01:09.840> that<00:01:10.260> is<00:01:10.680> to 00:01:11.149 --> 00:01:11.159 align:start position:0% I like to say about my job that is to 00:01:11.159 --> 00:01:13.969 align:start position:0% I like to say about my job that is to transform<00:01:11.720> extremely<00:01:12.720> complex<00:01:13.380> products 00:01:13.969 --> 00:01:13.979 align:start position:0% transform extremely complex products 00:01:13.979 --> 00:01:17.890 align:start position:0% transform extremely complex products into<00:01:14.220> palatable<00:01:14.880> bits<00:01:15.720> I've<00:01:16.619> been<00:01:16.799> designing 00:01:17.890 --> 00:01:17.900 align:start position:0% into palatable bits I've been designing 00:01:17.900 --> 00:01:21.890 align:start position:0% into palatable bits I've been designing for<00:01:18.900> around<00:01:19.200> 10<00:01:19.500> years<00:01:19.740> now<00:01:20.520> and 00:01:21.890 --> 00:01:21.900 align:start position:0% for around 10 years now and 00:01:21.900 --> 00:01:24.469 align:start position:0% for around 10 years now and um I've<00:01:22.500> been<00:01:22.680> in<00:01:22.920> the<00:01:23.100> ethereum<00:01:23.640> space<00:01:24.000> since 00:01:24.469 --> 00:01:24.479 align:start position:0% um I've been in the ethereum space since 00:01:24.479 --> 00:01:26.330 align:start position:0% um I've been in the ethereum space since 2018. 00:01:26.330 --> 00:01:26.340 align:start position:0% 2018. 00:01:26.340 --> 00:01:30.289 align:start position:0% 2018. my<00:01:27.119> goal<00:01:27.479> is<00:01:27.540> to<00:01:27.900> make<00:01:28.140> explorative<00:01:28.979> research 00:01:30.289 --> 00:01:30.299 align:start position:0% my goal is to make explorative research 00:01:30.299 --> 00:01:32.510 align:start position:0% my goal is to make explorative research part<00:01:30.900> of 00:01:32.510 --> 00:01:32.520 align:start position:0% part of 00:01:32.520 --> 00:01:37.910 align:start position:0% part of all<00:01:33.180> of<00:01:33.299> the<00:01:33.540> web<00:01:33.780> 3<00:01:34.200> products 00:01:37.910 --> 00:01:37.920 align:start position:0% 00:01:37.920 --> 00:01:40.550 align:start position:0% yeah 00:01:40.550 --> 00:01:40.560 align:start position:0% 00:01:40.560 --> 00:01:46.010 align:start position:0% Okay<00:01:41.159> so 00:01:46.010 --> 00:01:46.020 align:start position:0% 00:01:46.020 --> 00:01:47.690 align:start position:0% today's<00:01:46.560> talk<00:01:46.860> is<00:01:47.100> about<00:01:47.340> a<00:01:47.579> new 00:01:47.690 --> 00:01:47.700 align:start position:0% today's talk is about a new 00:01:47.700 --> 00:01:49.670 align:start position:0% today's talk is about a new collaboration<00:01:48.299> flow<00:01:48.720> between<00:01:49.020> designers 00:01:49.670 --> 00:01:49.680 align:start position:0% collaboration flow between designers 00:01:49.680 --> 00:01:52.429 align:start position:0% collaboration flow between designers developers<00:01:50.340> and<00:01:50.640> business<00:01:50.939> developers<00:01:51.720> it's 00:01:52.429 --> 00:01:52.439 align:start position:0% developers and business developers it's 00:01:52.439 --> 00:01:54.770 align:start position:0% developers and business developers it's a<00:01:52.680> critique<00:01:53.040> brought<00:01:53.520> to<00:01:53.820> the<00:01:54.000> way<00:01:54.180> things<00:01:54.479> are 00:01:54.770 --> 00:01:54.780 align:start position:0% a critique brought to the way things are 00:01:54.780 --> 00:01:56.990 align:start position:0% a critique brought to the way things are currently<00:01:55.079> handled<00:01:55.560> we'll<00:01:56.340> try<00:01:56.640> to<00:01:56.820> go 00:01:56.990 --> 00:01:57.000 align:start position:0% currently handled we'll try to go 00:01:57.000 --> 00:01:59.630 align:start position:0% currently handled we'll try to go together 00:01:59.630 --> 00:01:59.640 align:start position:0% 00:01:59.640 --> 00:02:01.670 align:start position:0% um<00:01:59.759> over<00:02:00.060> what<00:02:00.420> could<00:02:00.600> be<00:02:00.780> the<00:02:00.960> issues<00:02:01.320> of<00:02:01.500> the 00:02:01.670 --> 00:02:01.680 align:start position:0% um over what could be the issues of the 00:02:01.680 --> 00:02:04.310 align:start position:0% um over what could be the issues of the present<00:02:01.979> building<00:02:02.220> process<00:02:02.780> how<00:02:03.780> they<00:02:03.960> affect 00:02:04.310 --> 00:02:04.320 align:start position:0% present building process how they affect 00:02:04.320 --> 00:02:07.069 align:start position:0% present building process how they affect the<00:02:04.740> product<00:02:04.860> life<00:02:05.340> cycle<00:02:05.659> and<00:02:06.659> we<00:02:06.960> will 00:02:07.069 --> 00:02:07.079 align:start position:0% the product life cycle and we will 00:02:07.079 --> 00:02:09.710 align:start position:0% the product life cycle and we will explore<00:02:07.680> how<00:02:08.160> might<00:02:08.340> we<00:02:08.640> collaborate<00:02:09.300> better 00:02:09.710 --> 00:02:09.720 align:start position:0% explore how might we collaborate better 00:02:09.720 --> 00:02:12.290 align:start position:0% explore how might we collaborate better from<00:02:10.140> the<00:02:10.319> start<00:02:10.500> and<00:02:11.340> how<00:02:11.640> to<00:02:11.819> be<00:02:12.000> more 00:02:12.290 --> 00:02:12.300 align:start position:0% from the start and how to be more 00:02:12.300 --> 00:02:14.630 align:start position:0% from the start and how to be more inclusive<00:02:12.780> today's<00:02:13.500> talk<00:02:13.920> is<00:02:14.280> an<00:02:14.520> open 00:02:14.630 --> 00:02:14.640 align:start position:0% inclusive today's talk is an open 00:02:14.640 --> 00:02:17.210 align:start position:0% inclusive today's talk is an open conversation<00:02:15.360> hopefully<00:02:16.140> this<00:02:16.440> subject<00:02:16.800> will 00:02:17.210 --> 00:02:17.220 align:start position:0% conversation hopefully this subject will 00:02:17.220 --> 00:02:19.970 align:start position:0% conversation hopefully this subject will set<00:02:17.459> the<00:02:17.640> wheels<00:02:17.879> in<00:02:18.060> motion<00:02:18.360> and<00:02:19.319> I<00:02:19.560> would<00:02:19.739> be 00:02:19.970 --> 00:02:19.980 align:start position:0% set the wheels in motion and I would be 00:02:19.980 --> 00:02:23.089 align:start position:0% set the wheels in motion and I would be happy<00:02:20.280> to<00:02:20.520> hear<00:02:20.879> any<00:02:21.360> ideas<00:02:21.720> suggestions<00:02:22.560> on 00:02:23.089 --> 00:02:23.099 align:start position:0% happy to hear any ideas suggestions on 00:02:23.099 --> 00:02:24.290 align:start position:0% happy to hear any ideas suggestions on how<00:02:23.520> we 00:02:24.290 --> 00:02:24.300 align:start position:0% how we 00:02:24.300 --> 00:02:31.430 align:start position:0% how we better<00:02:25.280> the<00:02:26.280> proposed<00:02:26.760> approach 00:02:31.430 --> 00:02:31.440 align:start position:0% 00:02:31.440 --> 00:02:35.270 align:start position:0% okay 00:02:35.270 --> 00:02:35.280 align:start position:0% 00:02:35.280 --> 00:02:39.290 align:start position:0% so<00:02:35.879> the<00:02:36.540> future<00:02:36.660> of<00:02:37.020> Wave<00:02:37.319> 3<00:02:37.500> ux<00:02:38.400> why<00:02:39.000> do<00:02:39.120> we 00:02:39.290 --> 00:02:39.300 align:start position:0% so the future of Wave 3 ux why do we 00:02:39.300 --> 00:02:44.210 align:start position:0% so the future of Wave 3 ux why do we even<00:02:39.420> talk<00:02:40.140> about<00:02:40.319> this<00:02:40.680> is<00:02:41.040> there<00:02:41.280> an<00:02:41.400> issue 00:02:44.210 --> 00:02:44.220 align:start position:0% 00:02:44.220 --> 00:02:47.990 align:start position:0% so<00:02:44.760> anecdotally<00:02:45.540> 70<00:02:46.200> of<00:02:46.920> the<00:02:47.099> user<00:02:47.459> experience 00:02:47.990 --> 00:02:48.000 align:start position:0% so anecdotally 70 of the user experience 00:02:48.000 --> 00:02:51.710 align:start position:0% so anecdotally 70 of the user experience of<00:02:48.300> a<00:02:48.540> web<00:02:48.720> 3<00:02:48.959> protocol<00:02:49.560> ordap<00:02:50.459> is<00:02:50.700> dictated<00:02:51.120> by 00:02:51.710 --> 00:02:51.720 align:start position:0% of a web 3 protocol ordap is dictated by 00:02:51.720 --> 00:02:54.050 align:start position:0% of a web 3 protocol ordap is dictated by the<00:02:51.959> smart<00:02:52.080> contract<00:02:52.620> smart<00:02:53.340> contracts<00:02:53.940> are 00:02:54.050 --> 00:02:54.060 align:start position:0% the smart contract smart contracts are 00:02:54.060 --> 00:02:56.930 align:start position:0% the smart contract smart contracts are usually<00:02:54.480> not<00:02:55.200> upgradable<00:02:55.800> so<00:02:56.340> the<00:02:56.580> experience 00:02:56.930 --> 00:02:56.940 align:start position:0% usually not upgradable so the experience 00:02:56.940 --> 00:02:59.630 align:start position:0% usually not upgradable so the experience should<00:02:57.300> be<00:02:57.420> Flawless<00:02:57.900> from<00:02:58.319> the<00:02:58.500> start<00:02:58.680> if<00:02:59.519> you 00:02:59.630 --> 00:02:59.640 align:start position:0% should be Flawless from the start if you 00:02:59.640 --> 00:03:02.449 align:start position:0% should be Flawless from the start if you are<00:02:59.760> not<00:02:59.940> familiar<00:03:00.420> with<00:03:01.260> how<00:03:01.920> this<00:03:02.099> could<00:03:02.280> be 00:03:02.449 --> 00:03:02.459 align:start position:0% are not familiar with how this could be 00:03:02.459 --> 00:03:06.470 align:start position:0% are not familiar with how this could be translated<00:03:03.000> to<00:03:03.360> then 00:03:06.470 --> 00:03:06.480 align:start position:0% 00:03:06.480 --> 00:03:09.890 align:start position:0% um<00:03:06.540> the<00:03:07.319> user<00:03:07.680> experience<00:03:08.160> in<00:03:08.459> web<00:03:08.700> 3<00:03:09.000> is<00:03:09.599> made 00:03:09.890 --> 00:03:09.900 align:start position:0% um the user experience in web 3 is made 00:03:09.900 --> 00:03:13.130 align:start position:0% um the user experience in web 3 is made of<00:03:10.200> the<00:03:10.739> entire<00:03:10.980> user<00:03:11.459> flow<00:03:11.819> and<00:03:12.180> user<00:03:12.780> Journey 00:03:13.130 --> 00:03:13.140 align:start position:0% of the entire user flow and user Journey 00:03:13.140 --> 00:03:16.190 align:start position:0% of the entire user flow and user Journey the<00:03:13.920> number<00:03:14.040> of<00:03:14.280> transactions<00:03:15.180> until<00:03:15.959> the 00:03:16.190 --> 00:03:16.200 align:start position:0% the number of transactions until the 00:03:16.200 --> 00:03:19.490 align:start position:0% the number of transactions until the goal<00:03:16.500> is<00:03:16.620> reached<00:03:17.000> which<00:03:18.000> in<00:03:18.540> web<00:03:19.200> 2 00:03:19.490 --> 00:03:19.500 align:start position:0% goal is reached which in web 2 00:03:19.500 --> 00:03:21.890 align:start position:0% goal is reached which in web 2 e-commerce<00:03:20.220> means<00:03:20.879> the<00:03:21.060> number<00:03:21.239> of<00:03:21.420> clicks 00:03:21.890 --> 00:03:21.900 align:start position:0% e-commerce means the number of clicks 00:03:21.900 --> 00:03:25.850 align:start position:0% e-commerce means the number of clicks the<00:03:22.739> gas<00:03:22.920> spent<00:03:23.340> by<00:03:23.640> the<00:03:23.879> users<00:03:24.560> and<00:03:25.560> the 00:03:25.850 --> 00:03:25.860 align:start position:0% the gas spent by the users and the 00:03:25.860 --> 00:03:29.390 align:start position:0% the gas spent by the users and the displayed<00:03:26.340> information 00:03:29.390 --> 00:03:29.400 align:start position:0% 00:03:29.400 --> 00:03:30.530 align:start position:0% so 00:03:30.530 --> 00:03:30.540 align:start position:0% so 00:03:30.540 --> 00:03:33.110 align:start position:0% so what<00:03:31.019> is<00:03:31.260> the<00:03:31.440> current<00:03:31.620> ux<00:03:32.099> situation<00:03:32.580> in<00:03:32.879> web 00:03:33.110 --> 00:03:33.120 align:start position:0% what is the current ux situation in web 00:03:33.120 --> 00:03:35.570 align:start position:0% what is the current ux situation in web 3 00:03:35.570 --> 00:03:35.580 align:start position:0% 00:03:35.580 --> 00:03:37.970 align:start position:0% the<00:03:36.060> products<00:03:36.540> are<00:03:36.659> extremely<00:03:37.319> complex<00:03:37.680> and 00:03:37.970 --> 00:03:37.980 align:start position:0% the products are extremely complex and 00:03:37.980 --> 00:03:40.430 align:start position:0% the products are extremely complex and difficult<00:03:38.400> and<00:03:39.060> the<00:03:39.300> development<00:03:39.720> teams<00:03:40.200> are 00:03:40.430 --> 00:03:40.440 align:start position:0% difficult and the development teams are 00:03:40.440 --> 00:03:42.649 align:start position:0% difficult and the development teams are more<00:03:40.680> focused<00:03:41.099> on<00:03:41.340> solving<00:03:41.879> the<00:03:42.180> problems 00:03:42.649 --> 00:03:42.659 align:start position:0% more focused on solving the problems 00:03:42.659 --> 00:03:44.750 align:start position:0% more focused on solving the problems which<00:03:43.319> are<00:03:43.560> localized<00:03:44.040> at<00:03:44.400> the<00:03:44.580> Smart 00:03:44.750 --> 00:03:44.760 align:start position:0% which are localized at the Smart 00:03:44.760 --> 00:03:47.030 align:start position:0% which are localized at the Smart contract 00:03:47.030 --> 00:03:47.040 align:start position:0% contract 00:03:47.040 --> 00:03:49.070 align:start position:0% contract um<00:03:47.099> and<00:03:47.580> there<00:03:47.940> are<00:03:48.060> many<00:03:48.360> levels<00:03:48.780> in<00:03:48.900> between 00:03:49.070 --> 00:03:49.080 align:start position:0% um and there are many levels in between 00:03:49.080 --> 00:03:51.229 align:start position:0% um and there are many levels in between the<00:03:49.319> smart<00:03:49.500> contract<00:03:49.920> and<00:03:50.159> the<00:03:50.340> user<00:03:50.700> so<00:03:51.000> this 00:03:51.229 --> 00:03:51.239 align:start position:0% the smart contract and the user so this 00:03:51.239 --> 00:03:53.570 align:start position:0% the smart contract and the user so this is<00:03:51.299> what's<00:03:51.480> happening<00:03:51.959> the<00:03:52.860> development<00:03:53.280> team 00:03:53.570 --> 00:03:53.580 align:start position:0% is what's happening the development team 00:03:53.580 --> 00:03:56.930 align:start position:0% is what's happening the development team meets<00:03:54.120> decides<00:03:55.080> how<00:03:55.440> to<00:03:55.680> uh<00:03:56.159> how<00:03:56.459> the<00:03:56.640> protocol 00:03:56.930 --> 00:03:56.940 align:start position:0% meets decides how to uh how the protocol 00:03:56.940 --> 00:03:59.270 align:start position:0% meets decides how to uh how the protocol or<00:03:57.239> dap<00:03:57.599> will<00:03:57.780> work<00:03:58.019> they<00:03:58.680> write<00:03:58.920> the<00:03:59.099> smart 00:03:59.270 --> 00:03:59.280 align:start position:0% or dap will work they write the smart 00:03:59.280 --> 00:04:00.890 align:start position:0% or dap will work they write the smart contract 00:04:00.890 --> 00:04:00.900 align:start position:0% contract 00:04:00.900 --> 00:04:03.289 align:start position:0% contract um<00:04:00.959> and<00:04:01.620> afterwards<00:04:02.220> they<00:04:02.640> send<00:04:02.819> it<00:04:02.940> to<00:04:03.120> the 00:04:03.289 --> 00:04:03.299 align:start position:0% um and afterwards they send it to the 00:04:03.299 --> 00:04:05.210 align:start position:0% um and afterwards they send it to the audit<00:04:03.599> usually<00:04:04.200> there<00:04:04.500> are<00:04:04.680> multiple<00:04:04.980> all 00:04:05.210 --> 00:04:05.220 align:start position:0% audit usually there are multiple all 00:04:05.220 --> 00:04:07.610 align:start position:0% audit usually there are multiple all these<00:04:05.519> done<00:04:05.700> in<00:04:05.879> average<00:04:06.060> two<00:04:06.360> to<00:04:06.599> four<00:04:06.780> and 00:04:07.610 --> 00:04:07.620 align:start position:0% these done in average two to four and 00:04:07.620 --> 00:04:09.830 align:start position:0% these done in average two to four and after<00:04:07.980> the<00:04:08.340> code<00:04:08.519> has<00:04:08.879> been<00:04:09.120> audited<00:04:09.659> and 00:04:09.830 --> 00:04:09.840 align:start position:0% after the code has been audited and 00:04:09.840 --> 00:04:12.110 align:start position:0% after the code has been audited and fixed<00:04:10.200> it<00:04:10.319> fixed<00:04:10.980> the<00:04:11.459> development<00:04:11.879> team 00:04:12.110 --> 00:04:12.120 align:start position:0% fixed it fixed the development team 00:04:12.120 --> 00:04:14.530 align:start position:0% fixed it fixed the development team decides<00:04:12.840> to<00:04:13.140> bring<00:04:13.379> the<00:04:13.620> design<00:04:13.799> to<00:04:14.099> the<00:04:14.280> table 00:04:14.530 --> 00:04:14.540 align:start position:0% decides to bring the design to the table 00:04:14.540 --> 00:04:17.990 align:start position:0% decides to bring the design to the table so<00:04:15.540> basically<00:04:16.199> design<00:04:16.680> is<00:04:17.040> brought<00:04:17.459> when<00:04:17.639> all 00:04:17.990 --> 00:04:18.000 align:start position:0% so basically design is brought when all 00:04:18.000 --> 00:04:19.729 align:start position:0% so basically design is brought when all the<00:04:18.180> user<00:04:18.479> Journeys<00:04:18.900> all<00:04:19.320> the<00:04:19.440> user 00:04:19.729 --> 00:04:19.739 align:start position:0% the user Journeys all the user 00:04:19.739 --> 00:04:21.770 align:start position:0% the user Journeys all the user interactions<00:04:20.400> all<00:04:21.000> of<00:04:21.120> the<00:04:21.299> interaction 00:04:21.770 --> 00:04:21.780 align:start position:0% interactions all of the interaction 00:04:21.780 --> 00:04:24.170 align:start position:0% interactions all of the interaction experience<00:04:22.380> has<00:04:22.680> been<00:04:22.860> set<00:04:23.100> in<00:04:23.280> stone<00:04:23.520> and 00:04:24.170 --> 00:04:24.180 align:start position:0% experience has been set in stone and 00:04:24.180 --> 00:04:30.730 align:start position:0% experience has been set in stone and there<00:04:24.419> is<00:04:24.600> no<00:04:24.840> way<00:04:25.139> to<00:04:25.620> go<00:04:25.800> back<00:04:26.040> at<00:04:26.400> this<00:04:26.580> point 00:04:30.730 --> 00:04:30.740 align:start position:0% 00:04:30.740 --> 00:04:34.010 align:start position:0% so<00:04:31.740> there<00:04:32.100> is<00:04:32.280> a<00:04:32.400> tendency<00:04:32.820> for<00:04:33.180> technology<00:04:33.600> to 00:04:34.010 --> 00:04:34.020 align:start position:0% so there is a tendency for technology to 00:04:34.020 --> 00:04:35.930 align:start position:0% so there is a tendency for technology to lead<00:04:34.199> the<00:04:34.440> product<00:04:34.620> versus<00:04:35.220> the<00:04:35.580> other<00:04:35.699> way 00:04:35.930 --> 00:04:35.940 align:start position:0% lead the product versus the other way 00:04:35.940 --> 00:04:39.710 align:start position:0% lead the product versus the other way around<00:04:36.199> this<00:04:37.199> means<00:04:37.560> that<00:04:37.979> there<00:04:38.820> is<00:04:39.000> a<00:04:39.540> high 00:04:39.710 --> 00:04:39.720 align:start position:0% around this means that there is a high 00:04:39.720 --> 00:04:42.469 align:start position:0% around this means that there is a high likelihood<00:04:40.320> of<00:04:40.680> over<00:04:40.919> engineering<00:04:41.639> and 00:04:42.469 --> 00:04:42.479 align:start position:0% likelihood of over engineering and 00:04:42.479 --> 00:04:45.950 align:start position:0% likelihood of over engineering and unfortunately<00:04:43.080> ux<00:04:43.680> becomes<00:04:44.220> the<00:04:44.460> a<00:04:44.759> byproduct 00:04:45.950 --> 00:04:45.960 align:start position:0% unfortunately ux becomes the a byproduct 00:04:45.960 --> 00:04:48.350 align:start position:0% unfortunately ux becomes the a byproduct tech<00:04:46.320> people<00:04:46.620> do<00:04:46.919> not<00:04:47.100> have<00:04:47.280> the<00:04:47.580> priority<00:04:48.000> to 00:04:48.350 --> 00:04:48.360 align:start position:0% tech people do not have the priority to 00:04:48.360 --> 00:04:51.110 align:start position:0% tech people do not have the priority to put<00:04:48.540> themselves<00:04:48.960> in<00:04:49.320> the<00:04:49.560> user's<00:04:50.100> shoes<00:04:50.280> which 00:04:51.110 --> 00:04:51.120 align:start position:0% put themselves in the user's shoes which 00:04:51.120 --> 00:04:53.629 align:start position:0% put themselves in the user's shoes which is<00:04:51.300> not<00:04:51.540> really<00:04:51.720> an<00:04:52.020> issue<00:04:52.320> unless<00:04:53.100> the<00:04:53.400> entire 00:04:53.629 --> 00:04:53.639 align:start position:0% is not really an issue unless the entire 00:04:53.639 --> 00:04:56.689 align:start position:0% is not really an issue unless the entire experience<00:04:54.180> depends<00:04:54.660> on<00:04:54.840> them 00:04:56.689 --> 00:04:56.699 align:start position:0% experience depends on them 00:04:56.699 --> 00:04:59.990 align:start position:0% experience depends on them so<00:04:57.540> this<00:04:58.020> is<00:04:58.080> the<00:04:58.320> current<00:04:58.440> flow<00:04:58.919> and<00:04:59.580> let's 00:04:59.990 --> 00:05:00.000 align:start position:0% so this is the current flow and let's 00:05:00.000 --> 00:05:02.270 align:start position:0% so this is the current flow and let's check<00:05:00.479> what<00:05:01.080> are<00:05:01.199> the<00:05:01.380> downsides<00:05:01.919> of<00:05:02.100> this 00:05:02.270 --> 00:05:02.280 align:start position:0% check what are the downsides of this 00:05:02.280 --> 00:05:05.570 align:start position:0% check what are the downsides of this flow 00:05:05.570 --> 00:05:05.580 align:start position:0% 00:05:05.580 --> 00:05:07.490 align:start position:0% so 00:05:07.490 --> 00:05:07.500 align:start position:0% so 00:05:07.500 --> 00:05:10.310 align:start position:0% so the<00:05:08.040> teams<00:05:08.280> are<00:05:08.400> siled<00:05:09.000> which<00:05:09.479> means<00:05:09.780> there<00:05:10.139> is 00:05:10.310 --> 00:05:10.320 align:start position:0% the teams are siled which means there is 00:05:10.320 --> 00:05:12.830 align:start position:0% the teams are siled which means there is zero<00:05:10.680> collaboration<00:05:11.160> any<00:05:12.000> findings<00:05:12.479> from 00:05:12.830 --> 00:05:12.840 align:start position:0% zero collaboration any findings from 00:05:12.840 --> 00:05:15.830 align:start position:0% zero collaboration any findings from research<00:05:13.380> design<00:05:14.100> research<00:05:14.699> that<00:05:15.600> require 00:05:15.830 --> 00:05:15.840 align:start position:0% research design research that require 00:05:15.840 --> 00:05:18.170 align:start position:0% research design research that require redesigning<00:05:16.680> the<00:05:16.919> experience<00:05:17.340> is<00:05:17.639> impossible 00:05:18.170 --> 00:05:18.180 align:start position:0% redesigning the experience is impossible 00:05:18.180 --> 00:05:20.570 align:start position:0% redesigning the experience is impossible because<00:05:18.660> the<00:05:19.199> smart<00:05:19.440> contract<00:05:19.919> has<00:05:20.340> been 00:05:20.570 --> 00:05:20.580 align:start position:0% because the smart contract has been 00:05:20.580 --> 00:05:23.510 align:start position:0% because the smart contract has been audited<00:05:21.479> and<00:05:21.660> fixed<00:05:22.080> so<00:05:22.380> there<00:05:22.740> is<00:05:22.860> no<00:05:23.039> turning 00:05:23.510 --> 00:05:23.520 align:start position:0% audited and fixed so there is no turning 00:05:23.520 --> 00:05:24.290 align:start position:0% audited and fixed so there is no turning back 00:05:24.290 --> 00:05:24.300 align:start position:0% back 00:05:24.300 --> 00:05:26.689 align:start position:0% back design<00:05:24.840> can<00:05:25.199> improve<00:05:25.620> the<00:05:25.800> experience<00:05:26.280> only 00:05:26.689 --> 00:05:26.699 align:start position:0% design can improve the experience only 00:05:26.699 --> 00:05:29.810 align:start position:0% design can improve the experience only by<00:05:27.000> adding<00:05:27.479> explanations<00:05:28.199> and<00:05:28.979> ux<00:05:29.400> writing 00:05:29.810 --> 00:05:29.820 align:start position:0% by adding explanations and ux writing 00:05:29.820 --> 00:05:33.830 align:start position:0% by adding explanations and ux writing gimmicks 00:05:33.830 --> 00:05:33.840 align:start position:0% 00:05:33.840 --> 00:05:36.170 align:start position:0% um<00:05:33.960> design<00:05:34.560> unfortunately<00:05:35.400> can<00:05:35.880> only 00:05:36.170 --> 00:05:36.180 align:start position:0% um design unfortunately can only 00:05:36.180 --> 00:05:38.150 align:start position:0% um design unfortunately can only cosmetize<00:05:36.840> the<00:05:37.139> product<00:05:37.320> it<00:05:37.800> cannot 00:05:38.150 --> 00:05:38.160 align:start position:0% cosmetize the product it cannot 00:05:38.160 --> 00:05:40.490 align:start position:0% cosmetize the product it cannot fundamentally<00:05:38.880> improve<00:05:39.360> the<00:05:39.539> experience 00:05:40.490 --> 00:05:40.500 align:start position:0% fundamentally improve the experience 00:05:40.500 --> 00:05:42.950 align:start position:0% fundamentally improve the experience product<00:05:41.100> building<00:05:41.460> time<00:05:41.940> is<00:05:42.240> longer<00:05:42.660> because 00:05:42.950 --> 00:05:42.960 align:start position:0% product building time is longer because 00:05:42.960 --> 00:05:46.129 align:start position:0% product building time is longer because everything<00:05:43.320> is<00:05:43.680> cascading<00:05:44.360> and<00:05:45.360> onboarding 00:05:46.129 --> 00:05:46.139 align:start position:0% everything is cascading and onboarding 00:05:46.139 --> 00:05:49.670 align:start position:0% everything is cascading and onboarding and<00:05:46.380> retention<00:05:46.740> of<00:05:47.280> new<00:05:47.580> web3<00:05:48.240> users<00:05:48.960> is<00:05:49.380> low 00:05:49.670 --> 00:05:49.680 align:start position:0% and retention of new web3 users is low 00:05:49.680 --> 00:05:52.310 align:start position:0% and retention of new web3 users is low due<00:05:50.580> to<00:05:50.699> the<00:05:50.880> unfortunate<00:05:51.600> and<00:05:51.840> clunky 00:05:52.310 --> 00:05:52.320 align:start position:0% due to the unfortunate and clunky 00:05:52.320 --> 00:05:56.930 align:start position:0% due to the unfortunate and clunky experience<00:05:52.800> and<00:05:53.160> steep<00:05:53.460> learning<00:05:53.880> curve 00:05:56.930 --> 00:05:56.940 align:start position:0% 00:05:56.940 --> 00:06:00.350 align:start position:0% so 00:06:00.350 --> 00:06:00.360 align:start position:0% 00:06:00.360 --> 00:06:03.170 align:start position:0% we<00:06:00.840> learned<00:06:01.199> why<00:06:01.500> most<00:06:01.860> of<00:06:02.039> the<00:06:02.160> ux<00:06:02.460> resides<00:06:03.060> in 00:06:03.170 --> 00:06:03.180 align:start position:0% we learned why most of the ux resides in 00:06:03.180 --> 00:06:05.390 align:start position:0% we learned why most of the ux resides in the<00:06:03.360> smart<00:06:03.539> contract<00:06:04.020> we<00:06:04.680> learn<00:06:04.860> the<00:06:05.160> current 00:06:05.390 --> 00:06:05.400 align:start position:0% the smart contract we learn the current 00:06:05.400 --> 00:06:07.550 align:start position:0% the smart contract we learn the current situation<00:06:06.000> in<00:06:06.660> the<00:06:06.900> ethereum<00:06:07.320> product 00:06:07.550 --> 00:06:07.560 align:start position:0% situation in the ethereum product 00:06:07.560 --> 00:06:10.430 align:start position:0% situation in the ethereum product building<00:06:08.180> and<00:06:09.180> the<00:06:09.600> issues<00:06:09.960> of<00:06:10.139> the<00:06:10.320> current 00:06:10.430 --> 00:06:10.440 align:start position:0% building and the issues of the current 00:06:10.440 --> 00:06:13.550 align:start position:0% building and the issues of the current flow<00:06:10.860> so<00:06:11.639> how<00:06:12.300> might<00:06:12.479> we<00:06:12.720> improve<00:06:13.139> the<00:06:13.320> state 00:06:13.550 --> 00:06:13.560 align:start position:0% flow so how might we improve the state 00:06:13.560 --> 00:06:17.270 align:start position:0% flow so how might we improve the state of<00:06:13.800> web<00:06:14.039> 3<00:06:14.340> ux 00:06:17.270 --> 00:06:17.280 align:start position:0% 00:06:17.280 --> 00:06:19.969 align:start position:0% so<00:06:17.940> first<00:06:18.240> of<00:06:18.419> all<00:06:18.600> we<00:06:19.080> all<00:06:19.320> need<00:06:19.500> to<00:06:19.680> be 00:06:19.969 --> 00:06:19.979 align:start position:0% so first of all we all need to be 00:06:19.979 --> 00:06:22.790 align:start position:0% so first of all we all need to be open-minded<00:06:20.880> and<00:06:21.300> flexible<00:06:21.720> to<00:06:22.259> replace<00:06:22.380> our 00:06:22.790 --> 00:06:22.800 align:start position:0% open-minded and flexible to replace our 00:06:22.800 --> 00:06:25.670 align:start position:0% open-minded and flexible to replace our common<00:06:23.039> behaviors<00:06:23.759> this<00:06:24.660> means<00:06:25.020> stepping<00:06:25.500> out 00:06:25.670 --> 00:06:25.680 align:start position:0% common behaviors this means stepping out 00:06:25.680 --> 00:06:27.950 align:start position:0% common behaviors this means stepping out of<00:06:25.919> our<00:06:26.100> comfort<00:06:26.400> zones<00:06:26.819> by<00:06:27.240> changing<00:06:27.720> this 00:06:27.950 --> 00:06:27.960 align:start position:0% of our comfort zones by changing this 00:06:27.960 --> 00:06:30.650 align:start position:0% of our comfort zones by changing this bit<00:06:28.139> on<00:06:28.440> track 00:06:30.650 --> 00:06:30.660 align:start position:0% 00:06:30.660 --> 00:06:32.230 align:start position:0% the<00:06:31.199> deliverable 00:06:32.230 --> 00:06:32.240 align:start position:0% the deliverable 00:06:32.240 --> 00:06:35.510 align:start position:0% the deliverable the<00:06:33.240> deliverable<00:06:34.080> is<00:06:34.620> the<00:06:34.860> user-facing 00:06:35.510 --> 00:06:35.520 align:start position:0% the deliverable is the user-facing 00:06:35.520 --> 00:06:38.029 align:start position:0% the deliverable is the user-facing product<00:06:35.759> not<00:06:36.600> the<00:06:36.840> technical<00:06:37.139> not<00:06:37.740> the<00:06:37.919> smart 00:06:38.029 --> 00:06:38.039 align:start position:0% product not the technical not the smart 00:06:38.039 --> 00:06:40.430 align:start position:0% product not the technical not the smart contract<00:06:38.520> not<00:06:39.060> the<00:06:39.240> back-end<00:06:39.539> product 00:06:40.430 --> 00:06:40.440 align:start position:0% contract not the back-end product 00:06:40.440 --> 00:06:43.909 align:start position:0% contract not the back-end product so<00:06:41.160> having<00:06:41.880> a<00:06:42.120> goal<00:06:42.419> a<00:06:42.660> Target<00:06:42.840> to<00:06:43.139> get<00:06:43.380> to<00:06:43.560> a 00:06:43.909 --> 00:06:43.919 align:start position:0% so having a goal a Target to get to a 00:06:43.919 --> 00:06:46.189 align:start position:0% so having a goal a Target to get to a desired<00:06:44.340> ideal<00:06:44.759> outcome<00:06:45.240> is<00:06:45.660> a<00:06:45.840> great<00:06:45.960> place 00:06:46.189 --> 00:06:46.199 align:start position:0% desired ideal outcome is a great place 00:06:46.199 --> 00:06:47.749 align:start position:0% desired ideal outcome is a great place to<00:06:46.500> start<00:06:46.680> from 00:06:47.749 --> 00:06:47.759 align:start position:0% to start from 00:06:47.759 --> 00:06:48.950 align:start position:0% to start from so 00:06:48.950 --> 00:06:48.960 align:start position:0% so 00:06:48.960 --> 00:06:52.309 align:start position:0% so this<00:06:49.500> is<00:06:49.680> not<00:06:49.800> the<00:06:50.039> product 00:06:52.309 --> 00:06:52.319 align:start position:0% 00:06:52.319 --> 00:06:56.930 align:start position:0% this<00:06:53.220> is<00:06:53.520> the<00:06:53.699> product 00:06:56.930 --> 00:06:56.940 align:start position:0% 00:06:56.940 --> 00:06:59.809 align:start position:0% so<00:06:57.600> let's<00:06:58.259> try<00:06:58.560> to<00:06:58.740> find<00:06:58.979> out<00:06:59.160> about<00:06:59.460> a 00:06:59.809 --> 00:06:59.819 align:start position:0% so let's try to find out about a 00:06:59.819 --> 00:07:03.110 align:start position:0% so let's try to find out about a different<00:07:00.000> way<00:07:00.539> of<00:07:00.660> thinking 00:07:03.110 --> 00:07:03.120 align:start position:0% 00:07:03.120 --> 00:07:05.150 align:start position:0% first<00:07:03.539> of<00:07:03.660> all<00:07:03.780> I<00:07:04.080> would<00:07:04.199> like<00:07:04.380> to<00:07:04.560> start<00:07:04.800> from 00:07:05.150 --> 00:07:05.160 align:start position:0% first of all I would like to start from 00:07:05.160 --> 00:07:07.189 align:start position:0% first of all I would like to start from a<00:07:05.400> process<00:07:05.699> that<00:07:06.060> has<00:07:06.240> been<00:07:06.419> proven<00:07:06.780> to<00:07:07.020> work 00:07:07.189 --> 00:07:07.199 align:start position:0% a process that has been proven to work 00:07:07.199 --> 00:07:10.610 align:start position:0% a process that has been proven to work very<00:07:07.560> well<00:07:07.800> this<00:07:08.340> is<00:07:08.520> the<00:07:08.819> Double<00:07:09.240> Diamond 00:07:10.610 --> 00:07:10.620 align:start position:0% very well this is the Double Diamond 00:07:10.620 --> 00:07:12.890 align:start position:0% very well this is the Double Diamond process<00:07:11.160> the<00:07:11.460> Double<00:07:11.639> Diamond<00:07:12.240> which<00:07:12.600> was 00:07:12.890 --> 00:07:12.900 align:start position:0% process the Double Diamond which was 00:07:12.900 --> 00:07:14.870 align:start position:0% process the Double Diamond which was popularized<00:07:13.800> by<00:07:14.039> the<00:07:14.280> British<00:07:14.639> design 00:07:14.870 --> 00:07:14.880 align:start position:0% popularized by the British design 00:07:14.880 --> 00:07:17.870 align:start position:0% popularized by the British design Council<00:07:15.479> in<00:07:15.780> 2005. 00:07:17.870 --> 00:07:17.880 align:start position:0% Council in 2005. 00:07:17.880 --> 00:07:18.590 align:start position:0% Council in 2005. um 00:07:18.590 --> 00:07:18.600 align:start position:0% um 00:07:18.600 --> 00:07:21.230 align:start position:0% um this<00:07:19.380> process<00:07:19.620> is<00:07:19.979> based<00:07:20.340> on<00:07:20.460> a<00:07:20.639> diverge 00:07:21.230 --> 00:07:21.240 align:start position:0% this process is based on a diverge 00:07:21.240 --> 00:07:23.390 align:start position:0% this process is based on a diverge converge<00:07:21.660> process<00:07:22.139> developed<00:07:22.860> by<00:07:23.220> the 00:07:23.390 --> 00:07:23.400 align:start position:0% converge process developed by the 00:07:23.400 --> 00:07:26.210 align:start position:0% converge process developed by the linguist<00:07:23.840> Bella<00:07:24.840> vanity 00:07:26.210 --> 00:07:26.220 align:start position:0% linguist Bella vanity 00:07:26.220 --> 00:07:28.850 align:start position:0% linguist Bella vanity this<00:07:26.580> methodology<00:07:27.060> suggests<00:07:27.840> that<00:07:28.319> a<00:07:28.680> product 00:07:28.850 --> 00:07:28.860 align:start position:0% this methodology suggests that a product 00:07:28.860 --> 00:07:31.330 align:start position:0% this methodology suggests that a product process<00:07:29.340> should<00:07:29.639> have<00:07:29.880> four<00:07:30.120> phases 00:07:31.330 --> 00:07:31.340 align:start position:0% process should have four phases 00:07:31.340 --> 00:07:34.490 align:start position:0% process should have four phases Discovery<00:07:32.340> and<00:07:33.120> definition<00:07:33.360> which<00:07:34.199> together 00:07:34.490 --> 00:07:34.500 align:start position:0% Discovery and definition which together 00:07:34.500 --> 00:07:37.309 align:start position:0% Discovery and definition which together make<00:07:35.400> the<00:07:35.639> explorative<00:07:36.180> and<00:07:36.479> Divergent<00:07:37.080> phase 00:07:37.309 --> 00:07:37.319 align:start position:0% make the explorative and Divergent phase 00:07:37.319 --> 00:07:40.490 align:start position:0% make the explorative and Divergent phase and<00:07:38.220> then<00:07:38.400> development<00:07:39.180> and<00:07:39.599> delivery<00:07:40.080> which 00:07:40.490 --> 00:07:40.500 align:start position:0% and then development and delivery which 00:07:40.500 --> 00:07:42.650 align:start position:0% and then development and delivery which together<00:07:40.740> make<00:07:41.280> the<00:07:41.580> iterative<00:07:42.180> and 00:07:42.650 --> 00:07:42.660 align:start position:0% together make the iterative and 00:07:42.660 --> 00:07:48.409 align:start position:0% together make the iterative and convergent<00:07:43.199> phase 00:07:48.409 --> 00:07:48.419 align:start position:0% 00:07:48.419 --> 00:07:51.890 align:start position:0% so<00:07:49.199> explorative<00:07:49.979> design<00:07:50.400> helps<00:07:51.300> us<00:07:51.360> do<00:07:51.660> the 00:07:51.890 --> 00:07:51.900 align:start position:0% so explorative design helps us do the 00:07:51.900 --> 00:07:55.490 align:start position:0% so explorative design helps us do the right<00:07:52.139> thing<00:07:52.639> iterative<00:07:53.639> design<00:07:54.000> helps<00:07:54.960> us<00:07:55.080> do 00:07:55.490 --> 00:07:55.500 align:start position:0% right thing iterative design helps us do 00:07:55.500 --> 00:07:58.730 align:start position:0% right thing iterative design helps us do the<00:07:55.740> thing<00:07:55.979> right<00:07:56.400> this<00:07:57.240> is<00:07:57.360> my<00:07:57.539> Mantra<00:07:57.960> and<00:07:58.560> I 00:07:58.730 --> 00:07:58.740 align:start position:0% the thing right this is my Mantra and I 00:07:58.740 --> 00:08:00.350 align:start position:0% the thing right this is my Mantra and I think<00:07:58.979> this<00:07:59.460> should<00:07:59.639> become<00:07:59.940> everybody 00:08:00.350 --> 00:08:00.360 align:start position:0% think this should become everybody 00:08:00.360 --> 00:08:02.150 align:start position:0% think this should become everybody else's<00:08:00.900> mantra 00:08:02.150 --> 00:08:02.160 align:start position:0% else's mantra 00:08:02.160 --> 00:08:05.689 align:start position:0% else's mantra so<00:08:03.000> what<00:08:03.840> could<00:08:04.020> be<00:08:04.199> a<00:08:04.440> flow<00:08:04.800> that<00:08:05.039> respects 00:08:05.689 --> 00:08:05.699 align:start position:0% so what could be a flow that respects 00:08:05.699 --> 00:08:07.430 align:start position:0% so what could be a flow that respects the<00:08:05.940> two<00:08:06.120> important<00:08:06.539> phases<00:08:06.960> in<00:08:07.139> a<00:08:07.319> product 00:08:07.430 --> 00:08:07.440 align:start position:0% the two important phases in a product 00:08:07.440 --> 00:08:10.189 align:start position:0% the two important phases in a product development<00:08:08.039> cycle<00:08:08.460> and<00:08:09.240> it<00:08:09.360> can<00:08:09.720> also 00:08:10.189 --> 00:08:10.199 align:start position:0% development cycle and it can also 00:08:10.199 --> 00:08:14.749 align:start position:0% development cycle and it can also respond<00:08:10.680> to<00:08:10.919> the<00:08:11.099> web<00:08:11.280> 3<00:08:11.520> environment<00:08:12.180> needs 00:08:14.749 --> 00:08:14.759 align:start position:0% respond to the web 3 environment needs 00:08:14.759 --> 00:08:17.510 align:start position:0% respond to the web 3 environment needs so<00:08:15.360> this<00:08:15.840> is<00:08:15.900> a<00:08:16.080> product<00:08:16.259> flow<00:08:16.680> I<00:08:16.919> am<00:08:17.039> proposing 00:08:17.510 --> 00:08:17.520 align:start position:0% so this is a product flow I am proposing 00:08:17.520 --> 00:08:19.490 align:start position:0% so this is a product flow I am proposing that<00:08:17.940> follows<00:08:18.360> the<00:08:18.539> explorative<00:08:19.080> and 00:08:19.490 --> 00:08:19.500 align:start position:0% that follows the explorative and 00:08:19.500 --> 00:08:22.010 align:start position:0% that follows the explorative and iterative<00:08:20.039> phases<00:08:20.580> and<00:08:21.419> which<00:08:21.599> I<00:08:21.840> believe 00:08:22.010 --> 00:08:22.020 align:start position:0% iterative phases and which I believe 00:08:22.020 --> 00:08:24.830 align:start position:0% iterative phases and which I believe with<00:08:22.319> would<00:08:23.099> definitely<00:08:23.639> improve<00:08:24.300> a<00:08:24.419> lot<00:08:24.539> the 00:08:24.830 --> 00:08:24.840 align:start position:0% with would definitely improve a lot the 00:08:24.840 --> 00:08:27.290 align:start position:0% with would definitely improve a lot the web<00:08:25.020> 3<00:08:25.259> product<00:08:25.560> development<00:08:26.220> so<00:08:26.759> what<00:08:26.940> let's 00:08:27.290 --> 00:08:27.300 align:start position:0% web 3 product development so what let's 00:08:27.300 --> 00:08:31.010 align:start position:0% web 3 product development so what let's break<00:08:27.539> it<00:08:27.720> down 00:08:31.010 --> 00:08:31.020 align:start position:0% 00:08:31.020 --> 00:08:34.130 align:start position:0% so<00:08:31.740> in<00:08:32.339> the<00:08:32.520> explorative<00:08:33.060> Divergent<00:08:33.779> phase 00:08:34.130 --> 00:08:34.140 align:start position:0% so in the explorative Divergent phase 00:08:34.140 --> 00:08:36.050 align:start position:0% so in the explorative Divergent phase everyone<00:08:34.560> is<00:08:34.919> brought<00:08:35.159> to<00:08:35.339> the<00:08:35.520> table<00:08:35.640> from 00:08:36.050 --> 00:08:36.060 align:start position:0% everyone is brought to the table from 00:08:36.060 --> 00:08:38.449 align:start position:0% everyone is brought to the table from the<00:08:36.240> start<00:08:36.419> design<00:08:37.080> development<00:08:37.979> and 00:08:38.449 --> 00:08:38.459 align:start position:0% the start design development and 00:08:38.459 --> 00:08:39.230 align:start position:0% the start design development and business 00:08:39.230 --> 00:08:39.240 align:start position:0% business 00:08:39.240 --> 00:08:41.870 align:start position:0% business a<00:08:39.779> designer<00:08:40.200> will<00:08:40.440> facilitate<00:08:41.099> stakeholder 00:08:41.870 --> 00:08:41.880 align:start position:0% a designer will facilitate stakeholder 00:08:41.880 --> 00:08:44.510 align:start position:0% a designer will facilitate stakeholder interviews<00:08:42.419> and<00:08:42.899> each<00:08:43.260> team<00:08:43.440> will<00:08:43.919> map<00:08:44.159> out 00:08:44.510 --> 00:08:44.520 align:start position:0% interviews and each team will map out 00:08:44.520 --> 00:08:46.910 align:start position:0% interviews and each team will map out their<00:08:44.820> requirements<00:08:45.480> the<00:08:46.260> user<00:08:46.560> needs 00:08:46.910 --> 00:08:46.920 align:start position:0% their requirements the user needs 00:08:46.920 --> 00:08:49.430 align:start position:0% their requirements the user needs technical<00:08:47.459> constraints<00:08:48.060> business<00:08:48.899> goals 00:08:49.430 --> 00:08:49.440 align:start position:0% technical constraints business goals 00:08:49.440 --> 00:08:51.650 align:start position:0% technical constraints business goals they<00:08:49.920> are<00:08:50.100> all<00:08:50.339> considered<00:08:50.880> and<00:08:51.180> taken<00:08:51.540> into 00:08:51.650 --> 00:08:51.660 align:start position:0% they are all considered and taken into 00:08:51.660 --> 00:08:54.350 align:start position:0% they are all considered and taken into account 00:08:54.350 --> 00:08:54.360 align:start position:0% 00:08:54.360 --> 00:08:56.870 align:start position:0% user<00:08:55.019> Journeys<00:08:55.380> are<00:08:55.620> created<00:08:55.980> based<00:08:56.519> on<00:08:56.580> each 00:08:56.870 --> 00:08:56.880 align:start position:0% user Journeys are created based on each 00:08:56.880 --> 00:08:59.509 align:start position:0% user Journeys are created based on each team's<00:08:57.300> insights<00:08:57.839> and<00:08:57.959> requirements<00:08:58.620> evm 00:08:59.509 --> 00:08:59.519 align:start position:0% team's insights and requirements evm 00:08:59.519 --> 00:09:03.290 align:start position:0% team's insights and requirements evm constraints<00:09:00.080> security<00:09:01.080> issues<00:09:01.980> user<00:09:02.940> needs 00:09:03.290 --> 00:09:03.300 align:start position:0% constraints security issues user needs 00:09:03.300 --> 00:09:05.329 align:start position:0% constraints security issues user needs pain<00:09:03.660> points<00:09:04.140> kpis<00:09:04.740> and<00:09:05.160> business 00:09:05.329 --> 00:09:05.339 align:start position:0% pain points kpis and business 00:09:05.339 --> 00:09:07.910 align:start position:0% pain points kpis and business requirements<00:09:06.120> all<00:09:06.720> of<00:09:06.839> these<00:09:07.080> elements<00:09:07.500> are 00:09:07.910 --> 00:09:07.920 align:start position:0% requirements all of these elements are 00:09:07.920 --> 00:09:09.889 align:start position:0% requirements all of these elements are Incorporated<00:09:08.580> in<00:09:08.940> a<00:09:09.060> high-level<00:09:09.540> user 00:09:09.889 --> 00:09:09.899 align:start position:0% Incorporated in a high-level user 00:09:09.899 --> 00:09:13.070 align:start position:0% Incorporated in a high-level user Journey<00:09:10.260> map<00:09:10.440> that<00:09:11.279> will<00:09:11.519> Mark<00:09:11.820> each<00:09:12.300> step<00:09:12.600> a 00:09:13.070 --> 00:09:13.080 align:start position:0% Journey map that will Mark each step a 00:09:13.080 --> 00:09:15.050 align:start position:0% Journey map that will Mark each step a user<00:09:13.380> needs<00:09:13.680> to<00:09:13.740> take<00:09:13.980> in<00:09:14.279> order<00:09:14.399> to<00:09:14.700> achieve 00:09:15.050 --> 00:09:15.060 align:start position:0% user needs to take in order to achieve 00:09:15.060 --> 00:09:17.690 align:start position:0% user needs to take in order to achieve their<00:09:15.300> desired<00:09:15.779> goal<00:09:16.140> the<00:09:16.800> user<00:09:17.100> Journeys 00:09:17.690 --> 00:09:17.700 align:start position:0% their desired goal the user Journeys 00:09:17.700 --> 00:09:20.930 align:start position:0% their desired goal the user Journeys assumed<00:09:18.540> needs<00:09:19.019> and<00:09:19.320> pain<00:09:19.620> points<00:09:20.100> are<00:09:20.459> probed 00:09:20.930 --> 00:09:20.940 align:start position:0% assumed needs and pain points are probed 00:09:20.940 --> 00:09:23.269 align:start position:0% assumed needs and pain points are probed in<00:09:21.180> explorative<00:09:21.779> research<00:09:22.260> by<00:09:22.740> speaking<00:09:23.100> to 00:09:23.269 --> 00:09:23.279 align:start position:0% in explorative research by speaking to 00:09:23.279 --> 00:09:25.490 align:start position:0% in explorative research by speaking to real<00:09:23.459> people 00:09:25.490 --> 00:09:25.500 align:start position:0% real people 00:09:25.500 --> 00:09:28.610 align:start position:0% real people this<00:09:26.040> is<00:09:26.220> a<00:09:26.399> very<00:09:26.519> impactful<00:09:27.060> moment<00:09:27.540> in<00:09:28.500> the 00:09:28.610 --> 00:09:28.620 align:start position:0% this is a very impactful moment in the 00:09:28.620 --> 00:09:30.710 align:start position:0% this is a very impactful moment in the process<00:09:28.860> since<00:09:29.339> we<00:09:29.580> are<00:09:29.700> moving<00:09:30.060> from<00:09:30.360> merely 00:09:30.710 --> 00:09:30.720 align:start position:0% process since we are moving from merely 00:09:30.720 --> 00:09:32.690 align:start position:0% process since we are moving from merely assuming<00:09:31.200> things<00:09:31.440> to<00:09:31.860> actually<00:09:32.100> spending 00:09:32.690 --> 00:09:32.700 align:start position:0% assuming things to actually spending 00:09:32.700 --> 00:09:35.210 align:start position:0% assuming things to actually spending time<00:09:32.940> and<00:09:33.180> observing<00:09:33.779> the<00:09:34.080> people<00:09:34.260> who<00:09:35.100> will 00:09:35.210 --> 00:09:35.220 align:start position:0% time and observing the people who will 00:09:35.220 --> 00:09:37.790 align:start position:0% time and observing the people who will in<00:09:35.399> the<00:09:35.519> end<00:09:35.640> use<00:09:35.820> our<00:09:36.060> product<00:09:36.420> so<00:09:37.320> in<00:09:37.680> this 00:09:37.790 --> 00:09:37.800 align:start position:0% in the end use our product so in this 00:09:37.800 --> 00:09:40.070 align:start position:0% in the end use our product so in this type<00:09:37.980> of<00:09:38.160> the<00:09:38.339> process<00:09:38.700> we're<00:09:39.480> testing<00:09:39.959> our 00:09:40.070 --> 00:09:40.080 align:start position:0% type of the process we're testing our 00:09:40.080 --> 00:09:42.410 align:start position:0% type of the process we're testing our ideas<00:09:40.440> and<00:09:41.100> this<00:09:41.339> may<00:09:41.459> be<00:09:41.640> the<00:09:41.820> moment<00:09:42.120> in 00:09:42.410 --> 00:09:42.420 align:start position:0% ideas and this may be the moment in 00:09:42.420 --> 00:09:44.810 align:start position:0% ideas and this may be the moment in which<00:09:42.600> we<00:09:42.899> might<00:09:43.200> need<00:09:43.620> to<00:09:43.800> Pivot<00:09:44.160> we<00:09:44.640> might 00:09:44.810 --> 00:09:44.820 align:start position:0% which we might need to Pivot we might 00:09:44.820 --> 00:09:47.090 align:start position:0% which we might need to Pivot we might find<00:09:45.300> out<00:09:45.480> that<00:09:45.779> maybe<00:09:45.959> this<00:09:46.320> is<00:09:46.440> not<00:09:46.620> the<00:09:46.920> way 00:09:47.090 --> 00:09:47.100 align:start position:0% find out that maybe this is not the way 00:09:47.100 --> 00:09:48.530 align:start position:0% find out that maybe this is not the way to<00:09:47.279> go 00:09:48.530 --> 00:09:48.540 align:start position:0% to go 00:09:48.540 --> 00:09:49.910 align:start position:0% to go so 00:09:49.910 --> 00:09:49.920 align:start position:0% so 00:09:49.920 --> 00:09:52.550 align:start position:0% so afterwards<00:09:50.700> all<00:09:51.000> of<00:09:51.180> the<00:09:51.300> Unearthed<00:09:51.839> insights 00:09:52.550 --> 00:09:52.560 align:start position:0% afterwards all of the Unearthed insights 00:09:52.560 --> 00:09:55.070 align:start position:0% afterwards all of the Unearthed insights and<00:09:52.740> findings<00:09:53.279> will<00:09:53.580> be<00:09:53.760> incorporated<00:09:54.420> into 00:09:55.070 --> 00:09:55.080 align:start position:0% and findings will be incorporated into 00:09:55.080 --> 00:09:58.070 align:start position:0% and findings will be incorporated into the<00:09:55.380> new<00:09:55.560> user<00:09:55.920> Journeys 00:09:58.070 --> 00:09:58.080 align:start position:0% the new user Journeys 00:09:58.080 --> 00:10:00.370 align:start position:0% the new user Journeys so<00:09:58.800> research<00:09:59.399> has<00:09:59.580> been<00:09:59.760> conducted 00:10:00.370 --> 00:10:00.380 align:start position:0% so research has been conducted 00:10:00.380 --> 00:10:03.530 align:start position:0% so research has been conducted assumptions<00:10:01.380> have<00:10:01.680> been<00:10:01.920> probed<00:10:02.760> findings 00:10:03.530 --> 00:10:03.540 align:start position:0% assumptions have been probed findings 00:10:03.540 --> 00:10:05.870 align:start position:0% assumptions have been probed findings had<00:10:03.899> been<00:10:04.080> Incorporated<00:10:04.740> in<00:10:05.160> the<00:10:05.279> into<00:10:05.580> the 00:10:05.870 --> 00:10:05.880 align:start position:0% had been Incorporated in the into the 00:10:05.880 --> 00:10:08.090 align:start position:0% had been Incorporated in the into the new<00:10:06.060> user<00:10:06.420> journey<00:10:06.779> and<00:10:07.560> all<00:10:07.740> of<00:10:07.920> the 00:10:08.090 --> 00:10:08.100 align:start position:0% new user journey and all of the 00:10:08.100 --> 00:10:10.790 align:start position:0% new user journey and all of the stakeholders<00:10:08.760> have<00:10:09.120> validated<00:10:09.600> them<00:10:09.959> now<00:10:10.500> the 00:10:10.790 --> 00:10:10.800 align:start position:0% stakeholders have validated them now the 00:10:10.800 --> 00:10:15.530 align:start position:0% stakeholders have validated them now the interactive<00:10:11.399> phase<00:10:11.880> can<00:10:12.480> start 00:10:15.530 --> 00:10:15.540 align:start position:0% 00:10:15.540 --> 00:10:17.570 align:start position:0% so<00:10:15.959> the<00:10:16.080> new<00:10:16.260> user<00:10:16.620> journey<00:10:16.920> is<00:10:17.040> validated 00:10:17.570 --> 00:10:17.580 align:start position:0% so the new user journey is validated 00:10:17.580 --> 00:10:19.550 align:start position:0% so the new user journey is validated with<00:10:17.940> the<00:10:18.120> users<00:10:18.480> and<00:10:18.660> with<00:10:18.839> the<00:10:19.019> stakeholders 00:10:19.550 --> 00:10:19.560 align:start position:0% with the users and with the stakeholders 00:10:19.560 --> 00:10:22.370 align:start position:0% with the users and with the stakeholders on<00:10:19.860> our<00:10:20.160> are<00:10:20.459> now<00:10:20.700> becoming<00:10:21.180> the<00:10:21.540> backbone<00:10:22.080> of 00:10:22.370 --> 00:10:22.380 align:start position:0% on our are now becoming the backbone of 00:10:22.380 --> 00:10:25.070 align:start position:0% on our are now becoming the backbone of the<00:10:22.560> Project<00:10:23.060> based<00:10:24.060> on<00:10:24.120> these<00:10:24.420> documents<00:10:24.959> and 00:10:25.070 --> 00:10:25.080 align:start position:0% the Project based on these documents and 00:10:25.080 --> 00:10:27.290 align:start position:0% the Project based on these documents and artifacts<00:10:25.740> the<00:10:26.040> development<00:10:26.459> team<00:10:26.760> and<00:10:27.120> the 00:10:27.290 --> 00:10:27.300 align:start position:0% artifacts the development team and the 00:10:27.300 --> 00:10:29.150 align:start position:0% artifacts the development team and the design<00:10:27.420> team<00:10:27.779> can<00:10:28.200> start<00:10:28.380> working<00:10:28.740> in 00:10:29.150 --> 00:10:29.160 align:start position:0% design team can start working in 00:10:29.160 --> 00:10:30.710 align:start position:0% design team can start working in parallel 00:10:30.710 --> 00:10:30.720 align:start position:0% parallel 00:10:30.720 --> 00:10:33.350 align:start position:0% parallel the<00:10:31.440> design<00:10:31.620> prototype<00:10:32.519> and<00:10:32.760> smart<00:10:32.940> contract 00:10:33.350 --> 00:10:33.360 align:start position:0% the design prototype and smart contract 00:10:33.360 --> 00:10:35.449 align:start position:0% the design prototype and smart contract writing<00:10:33.839> is<00:10:34.080> a<00:10:34.320> very<00:10:34.440> important<00:10:34.860> step<00:10:35.160> in 00:10:35.449 --> 00:10:35.459 align:start position:0% writing is a very important step in 00:10:35.459 --> 00:10:37.250 align:start position:0% writing is a very important step in which<00:10:35.640> the<00:10:35.880> two<00:10:36.060> teams<00:10:36.420> will<00:10:36.600> need<00:10:36.779> to<00:10:37.019> have 00:10:37.250 --> 00:10:37.260 align:start position:0% which the two teams will need to have 00:10:37.260 --> 00:10:39.829 align:start position:0% which the two teams will need to have constant<00:10:37.860> check-ins<00:10:38.339> and<00:10:39.240> will<00:10:39.420> need<00:10:39.600> to 00:10:39.829 --> 00:10:39.839 align:start position:0% constant check-ins and will need to 00:10:39.839 --> 00:10:42.530 align:start position:0% constant check-ins and will need to accommodate<00:10:40.380> each<00:10:40.740> other's<00:10:41.100> findings<00:10:41.580> so 00:10:42.530 --> 00:10:42.540 align:start position:0% accommodate each other's findings so 00:10:42.540 --> 00:10:44.509 align:start position:0% accommodate each other's findings so basically 00:10:44.509 --> 00:10:44.519 align:start position:0% basically 00:10:44.519 --> 00:10:46.850 align:start position:0% basically the<00:10:45.060> design<00:10:45.240> team<00:10:45.540> will<00:10:45.839> test<00:10:46.079> the<00:10:46.260> Prototype 00:10:46.850 --> 00:10:46.860 align:start position:0% the design team will test the Prototype 00:10:46.860 --> 00:10:48.530 align:start position:0% the design team will test the Prototype will<00:10:47.100> have<00:10:47.339> some<00:10:47.579> findings<00:10:47.940> they<00:10:48.360> will 00:10:48.530 --> 00:10:48.540 align:start position:0% will have some findings they will 00:10:48.540 --> 00:10:50.449 align:start position:0% will have some findings they will communicate<00:10:49.200> them<00:10:49.440> to<00:10:49.680> the<00:10:49.860> smart<00:10:49.980> contract 00:10:50.449 --> 00:10:50.459 align:start position:0% communicate them to the smart contract 00:10:50.459 --> 00:10:52.790 align:start position:0% communicate them to the smart contract developers<00:10:51.000> the<00:10:51.600> smart<00:10:51.839> contract<00:10:52.320> developers 00:10:52.790 --> 00:10:52.800 align:start position:0% developers the smart contract developers 00:10:52.800 --> 00:10:55.009 align:start position:0% developers the smart contract developers will<00:10:53.100> incorporate<00:10:53.760> these<00:10:54.120> findings<00:10:54.420> into<00:10:54.779> the 00:10:55.009 --> 00:10:55.019 align:start position:0% will incorporate these findings into the 00:10:55.019 --> 00:10:57.350 align:start position:0% will incorporate these findings into the smart<00:10:55.200> contract<00:10:55.680> and<00:10:56.459> then<00:10:56.640> they<00:10:56.940> will<00:10:57.120> find 00:10:57.350 --> 00:10:57.360 align:start position:0% smart contract and then they will find 00:10:57.360 --> 00:10:59.810 align:start position:0% smart contract and then they will find Solutions<00:10:57.899> of<00:10:58.500> course<00:10:58.680> maybe<00:10:59.040> some<00:10:59.459> Technical 00:10:59.810 --> 00:10:59.820 align:start position:0% Solutions of course maybe some Technical 00:10:59.820 --> 00:11:02.290 align:start position:0% Solutions of course maybe some Technical Solutions<00:11:00.420> will<00:11:00.839> won't<00:11:01.140> be<00:11:01.440> necessarily 00:11:02.290 --> 00:11:02.300 align:start position:0% Solutions will won't be necessarily 00:11:02.300 --> 00:11:05.569 align:start position:0% Solutions will won't be necessarily perfectly<00:11:03.620> answering<00:11:04.620> to<00:11:04.800> the<00:11:04.980> new<00:11:05.160> needs 00:11:05.569 --> 00:11:05.579 align:start position:0% perfectly answering to the new needs 00:11:05.579 --> 00:11:07.610 align:start position:0% perfectly answering to the new needs that<00:11:05.820> have<00:11:06.000> been<00:11:06.180> discovered<00:11:06.660> so<00:11:07.140> they<00:11:07.440> will 00:11:07.610 --> 00:11:07.620 align:start position:0% that have been discovered so they will 00:11:07.620 --> 00:11:08.769 align:start position:0% that have been discovered so they will also 00:11:08.769 --> 00:11:08.779 align:start position:0% also 00:11:08.779 --> 00:11:11.449 align:start position:0% also communicate<00:11:09.779> these<00:11:10.500> new<00:11:10.800> issues<00:11:11.279> and 00:11:11.449 --> 00:11:11.459 align:start position:0% communicate these new issues and 00:11:11.459 --> 00:11:14.210 align:start position:0% communicate these new issues and findings<00:11:11.880> to<00:11:12.120> the<00:11:12.360> design<00:11:12.720> team<00:11:13.079> so<00:11:13.800> there 00:11:14.210 --> 00:11:14.220 align:start position:0% findings to the design team so there 00:11:14.220 --> 00:11:16.910 align:start position:0% findings to the design team so there needs<00:11:14.519> to<00:11:14.579> be<00:11:14.700> a<00:11:15.120> constant<00:11:15.420> back<00:11:15.660> and<00:11:15.899> forth<00:11:16.200> in 00:11:16.910 --> 00:11:16.920 align:start position:0% needs to be a constant back and forth in 00:11:16.920 --> 00:11:19.310 align:start position:0% needs to be a constant back and forth in between<00:11:17.040> these<00:11:17.519> teams<00:11:17.880> and<00:11:18.540> there<00:11:18.959> needs<00:11:19.260> to 00:11:19.310 --> 00:11:19.320 align:start position:0% between these teams and there needs to 00:11:19.320 --> 00:11:22.009 align:start position:0% between these teams and there needs to be<00:11:19.500> constant<00:11:19.980> collaboration<00:11:20.660> between<00:11:21.660> the 00:11:22.009 --> 00:11:22.019 align:start position:0% be constant collaboration between the 00:11:22.019 --> 00:11:27.250 align:start position:0% be constant collaboration between the design<00:11:22.140> team<00:11:22.500> and<00:11:22.740> the<00:11:22.920> development<00:11:23.339> team 00:11:27.250 --> 00:11:27.260 align:start position:0% 00:11:27.260 --> 00:11:28.970 align:start position:0% so 00:11:28.970 --> 00:11:28.980 align:start position:0% so 00:11:28.980 --> 00:11:32.569 align:start position:0% so the<00:11:29.579> benefits<00:11:29.940> of<00:11:30.120> the<00:11:30.360> proposed<00:11:30.839> flow<00:11:31.579> are 00:11:32.569 --> 00:11:32.579 align:start position:0% the benefits of the proposed flow are 00:11:32.579 --> 00:11:34.670 align:start position:0% the benefits of the proposed flow are the<00:11:32.760> following<00:11:33.120> the<00:11:33.959> team<00:11:34.140> is<00:11:34.380> fully 00:11:34.670 --> 00:11:34.680 align:start position:0% the following the team is fully 00:11:34.680 --> 00:11:37.310 align:start position:0% the following the team is fully integrated<00:11:35.100> and<00:11:35.459> not<00:11:35.700> siled<00:11:36.240> there<00:11:37.140> is 00:11:37.310 --> 00:11:37.320 align:start position:0% integrated and not siled there is 00:11:37.320 --> 00:11:39.530 align:start position:0% integrated and not siled there is constant<00:11:37.740> collaboration<00:11:38.459> and<00:11:39.120> back<00:11:39.360> and 00:11:39.530 --> 00:11:39.540 align:start position:0% constant collaboration and back and 00:11:39.540 --> 00:11:41.389 align:start position:0% constant collaboration and back and forth<00:11:39.839> between<00:11:40.200> the<00:11:40.500> design<00:11:40.620> team<00:11:40.980> and<00:11:41.220> the 00:11:41.389 --> 00:11:41.399 align:start position:0% forth between the design team and the 00:11:41.399 --> 00:11:43.670 align:start position:0% forth between the design team and the development<00:11:41.820> team<00:11:42.079> there<00:11:43.079> are<00:11:43.260> shorter 00:11:43.670 --> 00:11:43.680 align:start position:0% development team there are shorter 00:11:43.680 --> 00:11:46.490 align:start position:0% development team there are shorter building<00:11:43.980> times<00:11:44.459> and<00:11:45.420> of<00:11:45.779> course<00:11:45.899> more<00:11:46.320> time 00:11:46.490 --> 00:11:46.500 align:start position:0% building times and of course more time 00:11:46.500 --> 00:11:49.490 align:start position:0% building times and of course more time for<00:11:46.800> research<00:11:47.160> and<00:11:47.279> testing 00:11:49.490 --> 00:11:49.500 align:start position:0% for research and testing 00:11:49.500 --> 00:11:53.269 align:start position:0% for research and testing so<00:11:50.220> if<00:11:51.060> this<00:11:51.300> sounds<00:11:51.480> like<00:11:51.779> a<00:11:52.079> good<00:11:52.260> approach<00:11:52.860> I 00:11:53.269 --> 00:11:53.279 align:start position:0% so if this sounds like a good approach I 00:11:53.279 --> 00:11:56.210 align:start position:0% so if this sounds like a good approach I invite<00:11:53.579> you<00:11:53.700> to<00:11:53.820> adopt<00:11:54.240> the<00:11:54.360> methodology<00:11:55.220> and 00:11:56.210 --> 00:11:56.220 align:start position:0% invite you to adopt the methodology and 00:11:56.220 --> 00:11:58.910 align:start position:0% invite you to adopt the methodology and adapt<00:11:56.700> it<00:11:56.880> to<00:11:57.120> your<00:11:57.360> organization<00:11:58.079> we<00:11:58.620> need<00:11:58.800> to 00:11:58.910 --> 00:11:58.920 align:start position:0% adapt it to your organization we need to 00:11:58.920 --> 00:12:00.889 align:start position:0% adapt it to your organization we need to think<00:11:59.040> of<00:11:59.279> this<00:11:59.519> proposal<00:12:00.060> as<00:12:00.360> a<00:12:00.540> work<00:12:00.660> in 00:12:00.889 --> 00:12:00.899 align:start position:0% think of this proposal as a work in 00:12:00.899 --> 00:12:04.430 align:start position:0% think of this proposal as a work in progress<00:12:01.260> which<00:12:01.800> will<00:12:01.980> be<00:12:02.160> shaped<00:12:02.579> up<00:12:02.839> by<00:12:03.839> our 00:12:04.430 --> 00:12:04.440 align:start position:0% progress which will be shaped up by our 00:12:04.440 --> 00:12:07.009 align:start position:0% progress which will be shaped up by our experiences<00:12:05.100> and<00:12:05.459> needs<00:12:05.820> let's<00:12:06.420> consider 00:12:07.009 --> 00:12:07.019 align:start position:0% experiences and needs let's consider 00:12:07.019 --> 00:12:10.490 align:start position:0% experiences and needs let's consider this<00:12:07.440> our<00:12:07.860> explorative<00:12:08.700> phase 00:12:10.490 --> 00:12:10.500 align:start position:0% this our explorative phase 00:12:10.500 --> 00:12:12.530 align:start position:0% this our explorative phase um<00:12:10.560> if<00:12:10.980> you<00:12:11.100> plan<00:12:11.279> to<00:12:11.459> adopt<00:12:11.880> this<00:12:12.060> methodology 00:12:12.530 --> 00:12:12.540 align:start position:0% um if you plan to adopt this methodology 00:12:12.540 --> 00:12:14.569 align:start position:0% um if you plan to adopt this methodology and<00:12:12.899> implement<00:12:13.320> it<00:12:13.560> in<00:12:13.740> your<00:12:13.920> organization 00:12:14.569 --> 00:12:14.579 align:start position:0% and implement it in your organization 00:12:14.579 --> 00:12:16.790 align:start position:0% and implement it in your organization please<00:12:15.180> let<00:12:15.480> me<00:12:15.660> know<00:12:15.899> what<00:12:16.440> were<00:12:16.620> your 00:12:16.790 --> 00:12:16.800 align:start position:0% please let me know what were your 00:12:16.800 --> 00:12:18.530 align:start position:0% please let me know what were your struggles 00:12:18.530 --> 00:12:18.540 align:start position:0% struggles 00:12:18.540 --> 00:12:20.389 align:start position:0% struggles um<00:12:18.600> which<00:12:18.959> parts<00:12:19.200> of<00:12:19.380> the<00:12:19.500> process<00:12:19.800> worked<00:12:20.220> and 00:12:20.389 --> 00:12:20.399 align:start position:0% um which parts of the process worked and 00:12:20.399 --> 00:12:21.410 align:start position:0% um which parts of the process worked and which<00:12:20.579> didn't 00:12:21.410 --> 00:12:21.420 align:start position:0% which didn't 00:12:21.420 --> 00:12:23.750 align:start position:0% which didn't what<00:12:22.019> did<00:12:22.200> you<00:12:22.320> have<00:12:22.500> to<00:12:22.680> do<00:12:22.860> to<00:12:23.160> adapt<00:12:23.459> it<00:12:23.640> to 00:12:23.750 --> 00:12:23.760 align:start position:0% what did you have to do to adapt it to 00:12:23.760 --> 00:12:26.030 align:start position:0% what did you have to do to adapt it to your<00:12:24.000> own<00:12:24.300> company<00:12:24.600> needs<00:12:25.140> what<00:12:25.680> were<00:12:25.860> the 00:12:26.030 --> 00:12:26.040 align:start position:0% your own company needs what were the 00:12:26.040 --> 00:12:28.730 align:start position:0% your own company needs what were the struggles<00:12:26.459> or<00:12:27.180> of<00:12:27.660> challenging<00:12:28.260> the<00:12:28.560> status 00:12:28.730 --> 00:12:28.740 align:start position:0% struggles or of challenging the status 00:12:28.740 --> 00:12:33.650 align:start position:0% struggles or of challenging the status quo<00:12:29.220> did<00:12:29.940> you<00:12:30.060> encounter<00:12:30.480> any<00:12:30.779> any<00:12:31.320> resistance 00:12:33.650 --> 00:12:33.660 align:start position:0% quo did you encounter any any resistance 00:12:33.660 --> 00:12:36.530 align:start position:0% quo did you encounter any any resistance all<00:12:34.320> in<00:12:34.500> all<00:12:34.680> I<00:12:35.279> would<00:12:35.399> love<00:12:35.700> to<00:12:36.000> hear<00:12:36.300> from 00:12:36.530 --> 00:12:36.540 align:start position:0% all in all I would love to hear from 00:12:36.540 --> 00:12:38.269 align:start position:0% all in all I would love to hear from your<00:12:36.779> experiences<00:12:37.380> with<00:12:37.740> this<00:12:37.920> process 00:12:38.269 --> 00:12:38.279 align:start position:0% your experiences with this process 00:12:38.279 --> 00:12:42.170 align:start position:0% your experiences with this process because<00:12:38.880> the<00:12:39.600> goal<00:12:39.899> is<00:12:39.959> to<00:12:40.380> evolve<00:12:40.980> it<00:12:41.100> into<00:12:41.459> an 00:12:42.170 --> 00:12:42.180 align:start position:0% because the goal is to evolve it into an 00:12:42.180 --> 00:12:45.530 align:start position:0% because the goal is to evolve it into an adoptable<00:12:42.980> adaptable<00:12:43.980> and<00:12:44.700> helpful<00:12:45.120> process 00:12:45.530 --> 00:12:45.540 align:start position:0% adoptable adaptable and helpful process 00:12:45.540 --> 00:12:49.190 align:start position:0% adoptable adaptable and helpful process to<00:12:45.899> the<00:12:46.139> entire<00:12:46.440> web<00:12:46.860> 3<00:12:47.160> space 00:12:49.190 --> 00:12:49.200 align:start position:0% to the entire web 3 space 00:12:49.200 --> 00:12:51.889 align:start position:0% to the entire web 3 space so<00:12:49.980> some<00:12:50.399> great<00:12:50.579> news<00:12:50.940> from<00:12:51.300> the<00:12:51.540> threshold 00:12:51.889 --> 00:12:51.899 align:start position:0% so some great news from the threshold 00:12:51.899 --> 00:12:56.110 align:start position:0% so some great news from the threshold Network<00:12:52.260> and<00:12:52.680> the<00:12:52.860> tbtc<00:12:53.519> team 00:12:56.110 --> 00:12:56.120 align:start position:0% 00:12:56.120 --> 00:12:59.030 align:start position:0% my<00:12:57.120> team<00:12:57.240> was<00:12:57.540> convinced<00:12:58.019> about<00:12:58.200> the<00:12:58.560> benefits 00:12:59.030 --> 00:12:59.040 align:start position:0% my team was convinced about the benefits 00:12:59.040 --> 00:13:01.370 align:start position:0% my team was convinced about the benefits of<00:12:59.220> this<00:12:59.399> new<00:12:59.579> methodology<00:13:00.180> so<00:13:00.899> it<00:13:01.260> was 00:13:01.370 --> 00:13:01.380 align:start position:0% of this new methodology so it was 00:13:01.380 --> 00:13:03.470 align:start position:0% of this new methodology so it was decided<00:13:01.860> to<00:13:02.100> adopt<00:13:02.519> it<00:13:02.639> and<00:13:02.820> implement<00:13:03.240> it 00:13:03.470 --> 00:13:03.480 align:start position:0% decided to adopt it and implement it 00:13:03.480 --> 00:13:05.810 align:start position:0% decided to adopt it and implement it into<00:13:04.019> our<00:13:04.380> product<00:13:04.620> development<00:13:05.220> process 00:13:05.810 --> 00:13:05.820 align:start position:0% into our product development process 00:13:05.820 --> 00:13:10.670 align:start position:0% into our product development process starting<00:13:06.920> 2023<00:13:08.060> and<00:13:09.060> this<00:13:09.420> means<00:13:09.839> I<00:13:10.139> will<00:13:10.320> also 00:13:10.670 --> 00:13:10.680 align:start position:0% starting 2023 and this means I will also 00:13:10.680 --> 00:13:12.710 align:start position:0% starting 2023 and this means I will also share<00:13:11.040> with<00:13:11.220> you<00:13:11.399> my<00:13:11.760> experiences<00:13:12.300> of 00:13:12.710 --> 00:13:12.720 align:start position:0% share with you my experiences of 00:13:12.720 --> 00:13:14.930 align:start position:0% share with you my experiences of adopting<00:13:13.200> and<00:13:13.560> adopting<00:13:14.100> adapting<00:13:14.700> the 00:13:14.930 --> 00:13:14.940 align:start position:0% adopting and adopting adapting the 00:13:14.940 --> 00:13:18.170 align:start position:0% adopting and adopting adapting the process 00:13:18.170 --> 00:13:18.180 align:start position:0% 00:13:18.180 --> 00:13:20.150 align:start position:0% um<00:13:18.360> some<00:13:18.660> thoughts<00:13:19.019> of<00:13:19.200> from<00:13:19.560> my<00:13:19.920> colleague 00:13:20.150 --> 00:13:20.160 align:start position:0% um some thoughts of from my colleague 00:13:20.160 --> 00:13:23.030 align:start position:0% um some thoughts of from my colleague Doug<00:13:20.399> who<00:13:20.820> is<00:13:20.940> a<00:13:21.180> great<00:13:21.300> supporter<00:13:21.779> of<00:13:22.320> ux<00:13:22.680> in 00:13:23.030 --> 00:13:23.040 align:start position:0% Doug who is a great supporter of ux in 00:13:23.040 --> 00:13:25.370 align:start position:0% Doug who is a great supporter of ux in our<00:13:23.220> organization 00:13:25.370 --> 00:13:25.380 align:start position:0% our organization 00:13:25.380 --> 00:13:28.129 align:start position:0% our organization um<00:13:25.920> he's<00:13:26.760> talking<00:13:27.120> about<00:13:27.360> this<00:13:27.660> methodology 00:13:28.129 --> 00:13:28.139 align:start position:0% um he's talking about this methodology 00:13:28.139 --> 00:13:30.949 align:start position:0% um he's talking about this methodology and<00:13:28.680> he<00:13:28.920> says<00:13:29.279> there<00:13:29.880> is<00:13:30.000> no<00:13:30.180> hoping<00:13:30.600> and 00:13:30.949 --> 00:13:30.959 align:start position:0% and he says there is no hoping and 00:13:30.959 --> 00:13:33.590 align:start position:0% and he says there is no hoping and guessing<00:13:31.380> only<00:13:32.100> principled<00:13:32.820> aligned 00:13:33.590 --> 00:13:33.600 align:start position:0% guessing only principled aligned 00:13:33.600 --> 00:13:36.290 align:start position:0% guessing only principled aligned movement<00:13:33.959> that<00:13:34.560> values<00:13:34.980> the<00:13:35.160> user<00:13:35.519> Above<00:13:36.000> All 00:13:36.290 --> 00:13:36.300 align:start position:0% movement that values the user Above All 00:13:36.300 --> 00:13:37.850 align:start position:0% movement that values the user Above All Else 00:13:37.850 --> 00:13:37.860 align:start position:0% Else 00:13:37.860 --> 00:13:41.509 align:start position:0% Else and<00:13:38.639> some<00:13:39.120> more<00:13:39.540> good<00:13:40.380> news 00:13:41.509 --> 00:13:41.519 align:start position:0% and some more good news 00:13:41.519 --> 00:13:44.870 align:start position:0% and some more good news um<00:13:42.060> threshold<00:13:42.660> network<00:13:42.899> has<00:13:43.320> open<00:13:43.560> source<00:13:44.100> its 00:13:44.870 --> 00:13:44.880 align:start position:0% um threshold network has open source its 00:13:44.880 --> 00:13:48.190 align:start position:0% um threshold network has open source its entire<00:13:45.120> ux<00:13:45.480> research<00:13:45.959> and<00:13:46.260> past<00:13:46.800> ux<00:13:47.279> studies 00:13:48.190 --> 00:13:48.200 align:start position:0% entire ux research and past ux studies 00:13:48.200 --> 00:13:51.650 align:start position:0% entire ux research and past ux studies you<00:13:49.200> can<00:13:49.320> find<00:13:49.760> here<00:13:50.760> user<00:13:51.300> research 00:13:51.650 --> 00:13:51.660 align:start position:0% you can find here user research 00:13:51.660 --> 00:13:53.990 align:start position:0% you can find here user research guidelines<00:13:52.139> all<00:13:52.620> of<00:13:52.800> the<00:13:52.980> past<00:13:53.160> studies<00:13:53.760> that 00:13:53.990 --> 00:13:54.000 align:start position:0% guidelines all of the past studies that 00:13:54.000 --> 00:13:56.210 align:start position:0% guidelines all of the past studies that I've<00:13:54.180> conducted<00:13:54.779> for<00:13:55.200> keep<00:13:55.560> and<00:13:55.860> threshold 00:13:56.210 --> 00:13:56.220 align:start position:0% I've conducted for keep and threshold 00:13:56.220 --> 00:14:01.250 align:start position:0% I've conducted for keep and threshold Network<00:13:56.480> and<00:13:57.480> different<00:13:57.720> helpful<00:13:58.380> artifacts 00:14:01.250 --> 00:14:01.260 align:start position:0% Network and different helpful artifacts 00:14:01.260 --> 00:14:04.310 align:start position:0% Network and different helpful artifacts never<00:14:01.860> forget<00:14:02.160> this<00:14:02.519> love<00:14:02.880> your<00:14:03.120> users<00:14:03.540> thank 00:14:04.310 --> 00:14:04.320 align:start position:0% never forget this love your users thank 00:14:04.320 --> 00:14:04.880 align:start position:0% never forget this love your users thank you 00:14:04.880 --> 00:14:04.890 align:start position:0% you 00:14:04.890 --> 00:14:13.250 align:start position:0% you [Applause] 00:14:13.250 --> 00:14:13.260 align:start position:0% [Applause] 00:14:13.260 --> 00:14:16.310 align:start position:0% [Applause] thank<00:14:13.860> you<00:14:13.980> Sasha<00:14:14.459> amazing<00:14:15.060> presentation<00:14:15.540> so 00:14:16.310 --> 00:14:16.320 align:start position:0% thank you Sasha amazing presentation so 00:14:16.320 --> 00:14:17.930 align:start position:0% thank you Sasha amazing presentation so there's<00:14:16.680> a<00:14:16.860> few<00:14:17.040> minutes<00:14:17.220> left<00:14:17.579> maybe 00:14:17.930 --> 00:14:17.940 align:start position:0% there's a few minutes left maybe 00:14:17.940 --> 00:14:25.069 align:start position:0% there's a few minutes left maybe somebody<00:14:18.660> has<00:14:19.260> questions 00:14:25.069 --> 00:14:25.079 align:start position:0% 00:14:25.079 --> 00:14:27.889 align:start position:0% yes<00:14:25.620> I<00:14:25.920> always<00:14:26.040> have<00:14:26.339> questions<00:14:26.779> how<00:14:27.779> long 00:14:27.889 --> 00:14:27.899 align:start position:0% yes I always have questions how long 00:14:27.899 --> 00:14:30.829 align:start position:0% yes I always have questions how long would<00:14:28.139> you<00:14:28.260> expect<00:14:28.560> this<00:14:28.980> to<00:14:29.220> take<00:14:29.660> on<00:14:30.660> average 00:14:30.829 --> 00:14:30.839 align:start position:0% would you expect this to take on average 00:14:30.839 --> 00:14:33.290 align:start position:0% would you expect this to take on average I<00:14:31.320> understand<00:14:31.560> it's<00:14:31.980> an<00:14:32.220> exploration<00:14:32.820> by 00:14:33.290 --> 00:14:33.300 align:start position:0% I understand it's an exploration by 00:14:33.300 --> 00:14:35.930 align:start position:0% I understand it's an exploration by nature<00:14:33.660> but<00:14:33.959> do<00:14:34.500> you<00:14:34.620> have<00:14:34.740> any<00:14:34.920> Intuition<00:14:35.519> or 00:14:35.930 --> 00:14:35.940 align:start position:0% nature but do you have any Intuition or 00:14:35.940 --> 00:14:37.670 align:start position:0% nature but do you have any Intuition or feeling<00:14:36.180> for<00:14:36.480> how<00:14:36.720> long<00:14:36.839> you<00:14:37.139> would<00:14:37.320> take<00:14:37.440> an 00:14:37.670 --> 00:14:37.680 align:start position:0% feeling for how long you would take an 00:14:37.680 --> 00:14:40.009 align:start position:0% feeling for how long you would take an exploration<00:14:38.160> versus<00:14:38.519> iteration 00:14:40.009 --> 00:14:40.019 align:start position:0% exploration versus iteration 00:14:40.019 --> 00:14:44.090 align:start position:0% exploration versus iteration so<00:14:40.860> you<00:14:41.399> mean<00:14:41.660> explorative<00:14:42.660> phase<00:14:43.019> what<00:14:43.620> like 00:14:44.090 --> 00:14:44.100 align:start position:0% so you mean explorative phase what like 00:14:44.100 --> 00:14:46.970 align:start position:0% so you mean explorative phase what like okay<00:14:44.639> so<00:14:45.060> generative<00:14:45.660> user<00:14:46.199> research<00:14:46.620> should 00:14:46.970 --> 00:14:46.980 align:start position:0% okay so generative user research should 00:14:46.980 --> 00:14:47.930 align:start position:0% okay so generative user research should take 00:14:47.930 --> 00:14:47.940 align:start position:0% take 00:14:47.940 --> 00:14:51.590 align:start position:0% take two<00:14:48.360> three<00:14:49.160> weeks<00:14:50.160> at<00:14:50.760> most 00:14:51.590 --> 00:14:51.600 align:start position:0% two three weeks at most 00:14:51.600 --> 00:14:54.530 align:start position:0% two three weeks at most which<00:14:52.079> is<00:14:52.380> not<00:14:52.560> a<00:14:52.740> lot<00:14:52.860> and<00:14:53.279> it's<00:14:53.459> very 00:14:54.530 --> 00:14:54.540 align:start position:0% which is not a lot and it's very 00:14:54.540 --> 00:14:56.569 align:start position:0% which is not a lot and it's very easy<00:14:55.019> to<00:14:55.380> implement<00:14:55.740> the<00:14:56.279> findings 00:14:56.569 --> 00:14:56.579 align:start position:0% easy to implement the findings 00:14:56.579 --> 00:14:58.730 align:start position:0% easy to implement the findings afterwards<00:14:57.300> so<00:14:57.839> you<00:14:57.959> need<00:14:58.139> to<00:14:58.320> start<00:14:58.440> with 00:14:58.730 --> 00:14:58.740 align:start position:0% afterwards so you need to start with 00:14:58.740 --> 00:15:02.030 align:start position:0% afterwards so you need to start with this<00:14:58.980> it<00:14:59.399> can<00:14:59.579> take<00:14:59.880> even<00:15:00.120> less<00:15:00.540> than<00:15:00.959> that<00:15:01.199> but 00:15:02.030 --> 00:15:02.040 align:start position:0% this it can take even less than that but 00:15:02.040 --> 00:15:04.730 align:start position:0% this it can take even less than that but the<00:15:02.639> most<00:15:02.699> time<00:15:03.000> that<00:15:03.300> it<00:15:03.779> takes<00:15:03.899> is<00:15:04.139> finding 00:15:04.730 --> 00:15:04.740 align:start position:0% the most time that it takes is finding 00:15:04.740 --> 00:15:07.150 align:start position:0% the most time that it takes is finding the<00:15:05.279> the 00:15:07.150 --> 00:15:07.160 align:start position:0% the the 00:15:07.160 --> 00:15:09.889 align:start position:0% the the participants<00:15:08.160> that<00:15:08.760> are<00:15:09.060> meeting<00:15:09.240> the<00:15:09.540> user 00:15:09.889 --> 00:15:09.899 align:start position:0% participants that are meeting the user 00:15:09.899 --> 00:15:11.990 align:start position:0% participants that are meeting the user profile<00:15:10.320> that<00:15:10.680> you're<00:15:10.800> trying<00:15:11.220> to<00:15:11.519> to<00:15:11.699> build 00:15:11.990 --> 00:15:12.000 align:start position:0% profile that you're trying to to build 00:15:12.000 --> 00:15:14.569 align:start position:0% profile that you're trying to to build for<00:15:12.720> yeah 00:15:14.569 --> 00:15:14.579 align:start position:0% for yeah 00:15:14.579 --> 00:15:17.210 align:start position:0% for yeah so<00:15:15.240> it<00:15:15.779> doesn't<00:15:16.019> add<00:15:16.500> to<00:15:16.860> the<00:15:17.040> building 00:15:17.210 --> 00:15:17.220 align:start position:0% so it doesn't add to the building 00:15:17.220 --> 00:15:19.670 align:start position:0% so it doesn't add to the building process<00:15:17.699> it's<00:15:18.360> actually 00:15:19.670 --> 00:15:19.680 align:start position:0% process it's actually 00:15:19.680 --> 00:15:20.269 align:start position:0% process it's actually um 00:15:20.269 --> 00:15:20.279 align:start position:0% um 00:15:20.279 --> 00:15:23.389 align:start position:0% um it<00:15:20.940> shortens<00:15:21.360> it<00:15:21.600> because<00:15:22.079> you<00:15:22.500> know<00:15:22.740> what<00:15:23.220> to 00:15:23.389 --> 00:15:23.399 align:start position:0% it shortens it because you know what to 00:15:23.399 --> 00:15:25.610 align:start position:0% it shortens it because you know what to build<00:15:23.579> from<00:15:23.940> the<00:15:24.120> start<00:15:24.300> and<00:15:24.839> you<00:15:25.019> know<00:15:25.260> what 00:15:25.610 --> 00:15:25.620 align:start position:0% build from the start and you know what 00:15:25.620 --> 00:15:28.850 align:start position:0% build from the start and you know what people<00:15:25.860> are<00:15:26.220> needing<00:15:26.639> and<00:15:27.300> you<00:15:27.540> know<00:15:27.720> if<00:15:28.320> your 00:15:28.850 --> 00:15:28.860 align:start position:0% people are needing and you know if your 00:15:28.860 --> 00:15:32.810 align:start position:0% people are needing and you know if your ideas<00:15:29.160> are<00:15:29.940> actually<00:15:30.180> viable<00:15:30.720> and<00:15:32.220> I<00:15:32.699> don't 00:15:32.810 --> 00:15:32.820 align:start position:0% ideas are actually viable and I don't 00:15:32.820 --> 00:15:36.410 align:start position:0% ideas are actually viable and I don't know<00:15:33.019> responding<00:15:34.019> to<00:15:34.199> the<00:15:34.380> market<00:15:34.500> need 00:15:36.410 --> 00:15:36.420 align:start position:0% know responding to the market need 00:15:36.420 --> 00:15:39.230 align:start position:0% know responding to the market need yeah 00:15:39.230 --> 00:15:39.240 align:start position:0% 00:15:39.240 --> 00:15:43.370 align:start position:0% I<00:15:39.720> have<00:15:39.779> a<00:15:39.959> question<00:15:40.079> thank<00:15:40.680> you<00:15:41.240> uh<00:15:42.380> basically 00:15:43.370 --> 00:15:43.380 align:start position:0% I have a question thank you uh basically 00:15:43.380 --> 00:15:47.170 align:start position:0% I have a question thank you uh basically on<00:15:44.100> the<00:15:44.220> face<00:15:44.399> of<00:15:44.639> integrating<00:15:45.360> users 00:15:47.170 --> 00:15:47.180 align:start position:0% on the face of integrating users 00:15:47.180 --> 00:15:50.930 align:start position:0% on the face of integrating users what's<00:15:48.180> your<00:15:48.420> proposal<00:15:49.079> for<00:15:49.980> testnet<00:15:50.639> versus 00:15:50.930 --> 00:15:50.940 align:start position:0% what's your proposal for testnet versus 00:15:50.940 --> 00:15:53.150 align:start position:0% what's your proposal for testnet versus mainnet<00:15:51.839> or 00:15:53.150 --> 00:15:53.160 align:start position:0% mainnet or 00:15:53.160 --> 00:15:55.610 align:start position:0% mainnet or of<00:15:53.699> inclusion<00:15:54.540> of<00:15:54.660> the<00:15:54.839> users<00:15:55.079> because<00:15:55.320> we 00:15:55.610 --> 00:15:55.620 align:start position:0% of inclusion of the users because we 00:15:55.620 --> 00:15:57.829 align:start position:0% of inclusion of the users because we realize<00:15:56.100> that<00:15:56.339> when<00:15:56.579> users<00:15:57.060> are<00:15:57.240> on<00:15:57.420> test<00:15:57.600> net 00:15:57.829 --> 00:15:57.839 align:start position:0% realize that when users are on test net 00:15:57.839 --> 00:16:00.650 align:start position:0% realize that when users are on test net and<00:15:58.440> we<00:15:58.620> when<00:15:58.980> we<00:15:59.160> are<00:15:59.279> on<00:15:59.399> this<00:15:59.579> kind<00:15:59.820> of<00:15:59.940> user 00:16:00.650 --> 00:16:00.660 align:start position:0% and we when we are on this kind of user 00:16:00.660 --> 00:16:03.430 align:start position:0% and we when we are on this kind of user testing<00:16:01.079> the<00:16:01.800> users<00:16:02.220> as<00:16:02.579> they<00:16:02.820> are<00:16:03.060> not 00:16:03.430 --> 00:16:03.440 align:start position:0% testing the users as they are not 00:16:03.440 --> 00:16:05.810 align:start position:0% testing the users as they are not integrating<00:16:04.440> with<00:16:04.860> real<00:16:05.040> money<00:16:05.339> or<00:16:05.579> real 00:16:05.810 --> 00:16:05.820 align:start position:0% integrating with real money or real 00:16:05.820 --> 00:16:11.449 align:start position:0% integrating with real money or real assets<00:16:06.240> their<00:16:06.959> concerns<00:16:07.620> are<00:16:08.579> Way<00:16:09.620> Beyond<00:16:10.620> the 00:16:11.449 --> 00:16:11.459 align:start position:0% assets their concerns are Way Beyond the 00:16:11.459 --> 00:16:13.550 align:start position:0% assets their concerns are Way Beyond the when<00:16:11.880> they<00:16:12.060> are<00:16:12.180> on<00:16:12.300> my<00:16:12.420> net<00:16:12.660> but<00:16:13.019> when<00:16:13.139> you<00:16:13.380> are 00:16:13.550 --> 00:16:13.560 align:start position:0% when they are on my net but when you are 00:16:13.560 --> 00:16:15.530 align:start position:0% when they are on my net but when you are on<00:16:13.680> minute<00:16:13.920> you<00:16:14.579> should<00:16:14.699> have<00:16:14.880> already<00:16:15.180> a 00:16:15.530 --> 00:16:15.540 align:start position:0% on minute you should have already a 00:16:15.540 --> 00:16:17.449 align:start position:0% on minute you should have already a functional<00:16:16.199> solution<00:16:16.500> that<00:16:16.740> should<00:16:16.980> work<00:16:17.160> so 00:16:17.449 --> 00:16:17.459 align:start position:0% functional solution that should work so 00:16:17.459 --> 00:16:20.569 align:start position:0% functional solution that should work so what's<00:16:17.880> your<00:16:18.120> take<00:16:18.360> on<00:16:18.540> that<00:16:18.720> so<00:16:19.440> I<00:16:20.100> think<00:16:20.220> it's 00:16:20.569 --> 00:16:20.579 align:start position:0% what's your take on that so I think it's 00:16:20.579 --> 00:16:24.710 align:start position:0% what's your take on that so I think it's best<00:16:21.120> to<00:16:21.540> to<00:16:21.899> do<00:16:22.740> usability<00:16:23.279> tests<00:16:23.880> on<00:16:24.180> testnet 00:16:24.710 --> 00:16:24.720 align:start position:0% best to to do usability tests on testnet 00:16:24.720 --> 00:16:27.470 align:start position:0% best to to do usability tests on testnet but<00:16:25.620> try<00:16:25.920> to<00:16:26.100> make<00:16:26.279> it<00:16:26.459> as<00:16:26.639> real<00:16:26.880> as<00:16:27.120> possible 00:16:27.470 --> 00:16:27.480 align:start position:0% but try to make it as real as possible 00:16:27.480 --> 00:16:30.170 align:start position:0% but try to make it as real as possible like<00:16:28.440> what<00:16:29.220> you're<00:16:29.399> testing<00:16:29.760> will<00:16:30.000> be 00:16:30.170 --> 00:16:30.180 align:start position:0% like what you're testing will be 00:16:30.180 --> 00:16:31.670 align:start position:0% like what you're testing will be mirroring<00:16:30.660> your<00:16:30.959> product<00:16:31.139> that<00:16:31.560> you're 00:16:31.670 --> 00:16:31.680 align:start position:0% mirroring your product that you're 00:16:31.680 --> 00:16:34.970 align:start position:0% mirroring your product that you're deploying<00:16:32.220> on<00:16:32.760> mainnet<00:16:33.360> and<00:16:34.199> the<00:16:34.620> thing<00:16:34.800> is 00:16:34.970 --> 00:16:34.980 align:start position:0% deploying on mainnet and the thing is 00:16:34.980 --> 00:16:37.610 align:start position:0% deploying on mainnet and the thing is that<00:16:35.339> if<00:16:35.880> you're<00:16:35.940> giving<00:16:36.240> the<00:16:36.540> users<00:16:36.959> testnet 00:16:37.610 --> 00:16:37.620 align:start position:0% that if you're giving the users testnet 00:16:37.620 --> 00:16:39.650 align:start position:0% that if you're giving the users testnet tokens<00:16:38.040> and<00:16:38.399> everything<00:16:38.579> and<00:16:39.000> they<00:16:39.240> will<00:16:39.420> go 00:16:39.650 --> 00:16:39.660 align:start position:0% tokens and everything and they will go 00:16:39.660 --> 00:16:42.470 align:start position:0% tokens and everything and they will go to<00:16:39.839> to<00:16:40.259> the<00:16:40.560> entire<00:16:40.860> experience<00:16:41.519> at<00:16:42.360> some 00:16:42.470 --> 00:16:42.480 align:start position:0% to to the entire experience at some 00:16:42.480 --> 00:16:44.749 align:start position:0% to to the entire experience at some point<00:16:42.660> they<00:16:42.959> will<00:16:43.199> forget<00:16:43.860> that<00:16:44.339> they<00:16:44.579> are 00:16:44.749 --> 00:16:44.759 align:start position:0% point they will forget that they are 00:16:44.759 --> 00:16:48.230 align:start position:0% point they will forget that they are actually<00:16:45.060> testing<00:16:45.660> so<00:16:46.560> you<00:16:46.980> will<00:16:47.100> get<00:16:47.579> very 00:16:48.230 --> 00:16:48.240 align:start position:0% actually testing so you will get very 00:16:48.240 --> 00:16:50.329 align:start position:0% actually testing so you will get very good<00:16:48.420> insights<00:16:48.959> you<00:16:49.199> will<00:16:49.320> find<00:16:49.620> what's 00:16:50.329 --> 00:16:50.339 align:start position:0% good insights you will find what's 00:16:50.339 --> 00:16:52.490 align:start position:0% good insights you will find what's fearful<00:16:50.940> and<00:16:51.300> scary<00:16:51.540> for<00:16:51.959> them<00:16:52.139> because 00:16:52.490 --> 00:16:52.500 align:start position:0% fearful and scary for them because 00:16:52.500 --> 00:16:56.389 align:start position:0% fearful and scary for them because basically<00:16:52.860> we<00:16:52.980> are<00:16:53.160> designing<00:16:54.000> for<00:16:54.180> fear<00:16:54.600> so<00:16:55.500> I 00:16:56.389 --> 00:16:56.399 align:start position:0% basically we are designing for fear so I 00:16:56.399 --> 00:16:59.269 align:start position:0% basically we are designing for fear so I really<00:16:56.579> I'm<00:16:57.000> a<00:16:57.480> big<00:16:57.600> champion<00:16:57.839> of<00:16:58.320> testing<00:16:58.980> on 00:16:59.269 --> 00:16:59.279 align:start position:0% really I'm a big champion of testing on 00:16:59.279 --> 00:17:03.650 align:start position:0% really I'm a big champion of testing on test<00:16:59.759> Nets<00:17:00.540> yeah<00:17:01.019> okay<00:17:01.500> thank<00:17:01.860> you<00:17:02.040> yep 00:17:03.650 --> 00:17:03.660 align:start position:0% test Nets yeah okay thank you yep 00:17:03.660 --> 00:17:06.530 align:start position:0% test Nets yeah okay thank you yep yo<00:17:04.260> great<00:17:04.559> presentation 00:17:06.530 --> 00:17:06.540 align:start position:0% yo great presentation 00:17:06.540 --> 00:17:08.390 align:start position:0% yo great presentation um<00:17:06.600> is<00:17:07.260> there<00:17:07.439> a<00:17:07.559> generative<00:17:07.919> research 00:17:08.390 --> 00:17:08.400 align:start position:0% um is there a generative research 00:17:08.400 --> 00:17:10.730 align:start position:0% um is there a generative research supposed<00:17:08.699> to<00:17:08.939> align<00:17:09.360> with<00:17:09.720> the<00:17:09.959> Sprint<00:17:10.260> cycles 00:17:10.730 --> 00:17:10.740 align:start position:0% supposed to align with the Sprint cycles 00:17:10.740 --> 00:17:12.650 align:start position:0% supposed to align with the Sprint cycles that<00:17:10.919> a<00:17:11.400> product<00:17:11.520> team<00:17:11.699> might<00:17:11.939> have<00:17:12.059> or<00:17:12.419> is<00:17:12.540> it 00:17:12.650 --> 00:17:12.660 align:start position:0% that a product team might have or is it 00:17:12.660 --> 00:17:14.750 align:start position:0% that a product team might have or is it something<00:17:12.839> that<00:17:13.140> goes<00:17:13.500> like<00:17:13.679> again<00:17:14.280> like<00:17:14.579> in 00:17:14.750 --> 00:17:14.760 align:start position:0% something that goes like again like in 00:17:14.760 --> 00:17:16.909 align:start position:0% something that goes like again like in parallel<00:17:15.120> and<00:17:15.299> doesn't<00:17:15.480> have<00:17:15.720> to<00:17:16.079> match<00:17:16.740> up 00:17:16.909 --> 00:17:16.919 align:start position:0% parallel and doesn't have to match up 00:17:16.919 --> 00:17:19.429 align:start position:0% parallel and doesn't have to match up with<00:17:17.160> agile<00:17:17.579> I<00:17:18.179> think<00:17:18.240> it<00:17:18.540> it<00:17:18.780> should<00:17:19.020> be<00:17:19.140> part 00:17:19.429 --> 00:17:19.439 align:start position:0% with agile I think it it should be part 00:17:19.439 --> 00:17:21.650 align:start position:0% with agile I think it it should be part of<00:17:19.620> this<00:17:19.860> Prince<00:17:20.160> cycle<00:17:20.579> or<00:17:21.000> it<00:17:21.240> can<00:17:21.419> be 00:17:21.650 --> 00:17:21.660 align:start position:0% of this Prince cycle or it can be 00:17:21.660 --> 00:17:24.049 align:start position:0% of this Prince cycle or it can be agnostic<00:17:22.500> of<00:17:22.679> the<00:17:22.860> Sprint<00:17:23.100> cycle 00:17:24.049 --> 00:17:24.059 align:start position:0% agnostic of the Sprint cycle 00:17:24.059 --> 00:17:26.510 align:start position:0% agnostic of the Sprint cycle so<00:17:24.540> you<00:17:24.720> would<00:17:24.839> like<00:17:25.020> start<00:17:25.319> up<00:17:25.559> a<00:17:25.980> like<00:17:26.459> a 00:17:26.510 --> 00:17:26.520 align:start position:0% so you would like start up a like a 00:17:26.520 --> 00:17:28.429 align:start position:0% so you would like start up a like a regenerative<00:17:27.000> research<00:17:27.480> campaign<00:17:27.900> even<00:17:28.260> if 00:17:28.429 --> 00:17:28.439 align:start position:0% regenerative research campaign even if 00:17:28.439 --> 00:17:30.169 align:start position:0% regenerative research campaign even if it's<00:17:28.679> even<00:17:28.919> if<00:17:29.160> it's<00:17:29.280> outside<00:17:29.520> of<00:17:29.820> the<00:17:29.940> cycles 00:17:30.169 --> 00:17:30.179 align:start position:0% it's even if it's outside of the cycles 00:17:30.179 --> 00:17:32.450 align:start position:0% it's even if it's outside of the cycles of<00:17:30.360> the<00:17:30.480> product<00:17:30.600> yeah<00:17:30.960> yeah<00:17:31.200> exactly<00:17:31.799> I<00:17:32.340> think 00:17:32.450 --> 00:17:32.460 align:start position:0% of the product yeah yeah exactly I think 00:17:32.460 --> 00:17:36.169 align:start position:0% of the product yeah yeah exactly I think it<00:17:32.640> should<00:17:32.820> be<00:17:32.940> in<00:17:33.179> parallel<00:17:33.540> okay<00:17:34.140> cool<00:17:34.440> cool 00:17:36.169 --> 00:17:36.179 align:start position:0% it should be in parallel okay cool cool 00:17:36.179 --> 00:17:39.230 align:start position:0% it should be in parallel okay cool cool uh<00:17:36.780> I<00:17:37.020> have<00:17:37.140> a<00:17:37.320> question<00:17:37.559> yeah<00:17:38.100> I<00:17:38.760> want<00:17:38.940> to<00:17:39.059> ask 00:17:39.230 --> 00:17:39.240 align:start position:0% uh I have a question yeah I want to ask 00:17:39.240 --> 00:17:41.570 align:start position:0% uh I have a question yeah I want to ask how<00:17:39.600> do<00:17:39.720> you<00:17:39.840> reach<00:17:40.140> out<00:17:40.320> to<00:17:40.679> the<00:17:40.919> correct 00:17:41.570 --> 00:17:41.580 align:start position:0% how do you reach out to the correct 00:17:41.580 --> 00:17:43.190 align:start position:0% how do you reach out to the correct personas 00:17:43.190 --> 00:17:43.200 align:start position:0% personas 00:17:43.200 --> 00:17:47.090 align:start position:0% personas how<00:17:43.679> we<00:17:43.860> find<00:17:44.160> them<00:17:44.660> and<00:17:45.660> how<00:17:46.200> many 00:17:47.090 --> 00:17:47.100 align:start position:0% how we find them and how many 00:17:47.100 --> 00:17:49.610 align:start position:0% how we find them and how many different<00:17:47.640> personas<00:17:48.600> are<00:17:48.900> you<00:17:49.020> considering 00:17:49.610 --> 00:17:49.620 align:start position:0% different personas are you considering 00:17:49.620 --> 00:17:52.190 align:start position:0% different personas are you considering to<00:17:50.100> make<00:17:50.340> a<00:17:50.520> research<00:17:50.880> it's<00:17:51.660> very<00:17:51.900> difficult 00:17:52.190 --> 00:17:52.200 align:start position:0% to make a research it's very difficult 00:17:52.200 --> 00:17:54.529 align:start position:0% to make a research it's very difficult uh<00:17:53.039> in<00:17:53.280> my<00:17:53.460> point<00:17:53.640> of<00:17:53.820> view 00:17:54.529 --> 00:17:54.539 align:start position:0% uh in my point of view 00:17:54.539 --> 00:17:55.850 align:start position:0% uh in my point of view so 00:17:55.850 --> 00:17:55.860 align:start position:0% so 00:17:55.860 --> 00:17:58.610 align:start position:0% so we<00:17:56.640> don't<00:17:56.760> have<00:17:57.179> a<00:17:57.480> huge<00:17:57.780> pool<00:17:58.020> of 00:17:58.610 --> 00:17:58.620 align:start position:0% we don't have a huge pool of 00:17:58.620 --> 00:18:01.370 align:start position:0% we don't have a huge pool of participants<00:17:59.340> so<00:18:00.000> first<00:18:00.360> of<00:18:00.539> all<00:18:00.660> I<00:18:00.960> think<00:18:01.080> we 00:18:01.370 --> 00:18:01.380 align:start position:0% participants so first of all I think we 00:18:01.380 --> 00:18:04.010 align:start position:0% participants so first of all I think we should<00:18:01.880> stick<00:18:02.880> to<00:18:03.059> the<00:18:03.360> most<00:18:03.600> important 00:18:04.010 --> 00:18:04.020 align:start position:0% should stick to the most important 00:18:04.020 --> 00:18:06.529 align:start position:0% should stick to the most important Persona<00:18:04.559> that<00:18:04.799> we<00:18:04.919> have<00:18:05.100> and<00:18:05.940> then<00:18:06.120> after 00:18:06.529 --> 00:18:06.539 align:start position:0% Persona that we have and then after 00:18:06.539 --> 00:18:08.630 align:start position:0% Persona that we have and then after you're<00:18:06.900> building<00:18:07.200> your<00:18:07.620> user<00:18:07.980> profile<00:18:08.400> and 00:18:08.630 --> 00:18:08.640 align:start position:0% you're building your user profile and 00:18:08.640 --> 00:18:11.570 align:start position:0% you're building your user profile and you<00:18:09.000> know<00:18:09.419> who<00:18:09.720> you<00:18:09.840> want<00:18:10.020> to<00:18:10.200> build<00:18:10.440> for<00:18:10.740> then 00:18:11.570 --> 00:18:11.580 align:start position:0% you know who you want to build for then 00:18:11.580 --> 00:18:14.210 align:start position:0% you know who you want to build for then I<00:18:11.940> think<00:18:12.059> you<00:18:12.299> should<00:18:12.419> use<00:18:12.660> a<00:18:12.840> screener<00:18:13.320> and 00:18:14.210 --> 00:18:14.220 align:start position:0% I think you should use a screener and 00:18:14.220 --> 00:18:17.630 align:start position:0% I think you should use a screener and also<00:18:14.820> web3<00:18:15.360> ux<00:18:15.840> which<00:18:16.320> is<00:18:16.440> our<00:18:16.679> user<00:18:17.160> research 00:18:17.630 --> 00:18:17.640 align:start position:0% also web3 ux which is our user research 00:18:17.640 --> 00:18:20.870 align:start position:0% also web3 ux which is our user research panel<00:18:18.380> it<00:18:19.380> actually<00:18:19.559> started<00:18:20.160> from<00:18:20.460> this<00:18:20.700> need 00:18:20.870 --> 00:18:20.880 align:start position:0% panel it actually started from this need 00:18:20.880 --> 00:18:23.750 align:start position:0% panel it actually started from this need and<00:18:21.299> this<00:18:21.600> hurdle<00:18:22.080> that<00:18:22.860> is<00:18:23.039> very<00:18:23.220> hard<00:18:23.520> to 00:18:23.750 --> 00:18:23.760 align:start position:0% and this hurdle that is very hard to 00:18:23.760 --> 00:18:28.370 align:start position:0% and this hurdle that is very hard to find<00:18:24.380> participants<00:18:25.380> so<00:18:26.160> yeah<00:18:26.780> screeners<00:18:27.780> and 00:18:28.370 --> 00:18:28.380 align:start position:0% find participants so yeah screeners and 00:18:28.380 --> 00:18:31.010 align:start position:0% find participants so yeah screeners and then<00:18:28.620> a<00:18:29.039> pool<00:18:29.220> where<00:18:29.580> these<00:18:29.940> people<00:18:30.059> are<00:18:30.419> and 00:18:31.010 --> 00:18:31.020 align:start position:0% then a pool where these people are and 00:18:31.020 --> 00:18:34.070 align:start position:0% then a pool where these people are and try<00:18:31.559> to<00:18:31.880> invite<00:18:32.880> them<00:18:33.059> can't<00:18:33.419> wait<00:18:33.660> to<00:18:33.840> talk 00:18:34.070 --> 00:18:34.080 align:start position:0% try to invite them can't wait to talk 00:18:34.080 --> 00:18:38.870 align:start position:0% try to invite them can't wait to talk about<00:18:34.260> this<00:18:34.620> more<00:18:34.860> after<00:18:35.160> the<00:18:35.460> con<00:18:35.580> okay<00:18:36.000> sure 00:18:38.870 --> 00:18:38.880 align:start position:0% 00:18:38.880 --> 00:18:41.810 align:start position:0% amazing<00:18:39.720> thank<00:18:40.140> you<00:18:40.260> so<00:18:40.500> much<00:18:40.740> Sasha<00:18:41.400> thank 00:18:41.810 --> 00:18:41.820 align:start position:0% amazing thank you so much Sasha thank 00:18:41.820 --> 00:18:42.180 align:start position:0% amazing thank you so much Sasha thank you 00:18:42.180 --> 00:18:42.190 align:start position:0% you 00:18:42.190 --> 00:18:46.609 align:start position:0% you [Applause]