WEBVTT slide-1 00:00:01.170 --> 00:00:04.533 My name is Jeff Jaffe, CEO of W3C. 2 00:00:05.550 --> 00:00:08.490 This year, for the first time in three years, 3 00:00:08.490 --> 00:00:10.983 we will have an in-person TPAC meeting. 4 00:00:12.180 --> 00:00:15.090 TPAC Vancouver won't be completely in-person; 5 00:00:15.090 --> 00:00:17.580 we will have substantial video capability 6 00:00:17.580 --> 00:00:19.173 for those who will be remote. 7 00:00:20.790 --> 00:00:25.140 As I am delivering these remarks three weeks prior to TPAC, 8 00:00:25.140 --> 00:00:27.330 I note that I tested positive 9 00:00:27.330 --> 00:00:30.573 after attending a W3C meeting in Berlin. 10 00:00:31.830 --> 00:00:34.320 We took all imaginable precautions 11 00:00:34.320 --> 00:00:36.333 but we don't control COVID. 12 00:00:37.380 --> 00:00:42.380 Let's hope that all that travel to Vancouver do so safely. 13 00:00:42.630 --> 00:00:45.690 And I apologize if I sound a bit under the weather 14 00:00:45.690 --> 00:00:46.893 in this pre-record. 15 00:00:48.990 --> 00:00:52.140 As we sit on the threshold of becoming a legal entity 16 00:00:52.140 --> 00:00:54.000 there will be many presentations 17 00:00:54.000 --> 00:00:56.043 given by my colleagues on that topic. 18 00:00:57.090 --> 00:01:01.080 My presentation will be about one of my favorite topics, 19 00:01:01.080 --> 00:01:04.683 W3C Strategy, past, present, and future. 20 00:01:05.940 --> 00:01:07.470 I will get to that soon 21 00:01:07.470 --> 00:01:10.563 but first some overview administrative information. 22 00:01:11.550 --> 00:01:12.933 Please turn to slide two. slide-2 00:01:14.970 --> 00:01:17.700 This meeting operates under our Code of Conduct, 24 00:01:17.700 --> 00:01:22.080 as do all of our interactions within the W3C community. 25 00:01:22.080 --> 00:01:25.833 This is part of our goal of improving inclusion within W3C. 26 00:01:27.090 --> 00:01:29.640 In this slide you will find a pointer 27 00:01:29.640 --> 00:01:32.400 to the Positive Work Environment Community Group 28 00:01:32.400 --> 00:01:34.383 for the evolution of this work. 29 00:01:36.060 --> 00:01:37.653 Please turn to slide three. slide-3 00:01:39.900 --> 00:01:44.400 Slide three recalls W3C's Antitrust Policy, 31 00:01:44.400 --> 00:01:46.830 including a reminder to all participants 32 00:01:46.830 --> 00:01:48.960 that they must ensure that their conduct 33 00:01:48.960 --> 00:01:51.510 does not violate antitrust 34 00:01:51.510 --> 00:01:53.583 and competition laws and regulation. 35 00:01:54.690 --> 00:01:56.253 Please turn to slide four. slide-4 00:01:58.920 --> 00:02:01.620 Shortly after the last AC meeting, 37 00:02:01.620 --> 00:02:04.023 prompted by an AC Forum conversation, 38 00:02:04.860 --> 00:02:08.580 I got to thinking about the need for crisper communication 39 00:02:08.580 --> 00:02:10.443 of the W3C strategy. 40 00:02:12.090 --> 00:02:14.580 In my 12 years at W3C 41 00:02:14.580 --> 00:02:18.510 W3M has successfully executed a strategy 42 00:02:18.510 --> 00:02:23.370 to grow the W3C community and its impact 43 00:02:23.370 --> 00:02:25.650 and make progress towards our mission 44 00:02:25.650 --> 00:02:28.143 of leading the web to its full potential. 45 00:02:29.370 --> 00:02:32.493 But we have not always communicated our results. 46 00:02:33.510 --> 00:02:36.000 As we sit on the threshold of the legal entity 47 00:02:36.000 --> 00:02:39.090 it is timely to explain what our strategy has been, 48 00:02:39.090 --> 00:02:42.333 what metrics we have used, and how well we have done. 49 00:02:44.880 --> 00:02:46.863 Much of this material is not new. 50 00:02:47.700 --> 00:02:49.770 We have been reporting elements of our strategy 51 00:02:49.770 --> 00:02:53.970 over the years, but we've not packaged it consistently 52 00:02:53.970 --> 00:02:55.923 and expressed it as a strategy. 53 00:02:57.510 --> 00:03:00.513 Now is an important time to have this conversation. 54 00:03:01.444 --> 00:03:04.053 W3C is pivoting to a new structure. 55 00:03:05.220 --> 00:03:07.263 First there is the new legal basis, 56 00:03:08.280 --> 00:03:11.733 but the new structure is broader than the legal foundation. 57 00:03:12.630 --> 00:03:15.930 We are moving to a member-led paradigm. 58 00:03:15.930 --> 00:03:18.510 We will have a board of directors. 59 00:03:18.510 --> 00:03:20.220 With all of this change, 60 00:03:20.220 --> 00:03:24.780 it is vital to reflect on our strategy leading up to today 61 00:03:24.780 --> 00:03:28.620 and begin a conversation ultimately decided by the Board 62 00:03:28.620 --> 00:03:30.513 of what the strategy should become. 63 00:03:32.670 --> 00:03:35.850 The word strategy is a loaded word. 64 00:03:35.850 --> 00:03:38.430 An organization can have a business strategy, 65 00:03:38.430 --> 00:03:41.430 a marketing strategy, a technical strategy, 66 00:03:41.430 --> 00:03:43.680 a financial strategy. 67 00:03:43.680 --> 00:03:46.320 Each of these terms cover different topics, 68 00:03:46.320 --> 00:03:48.060 have different objectives, 69 00:03:48.060 --> 00:03:51.330 and the appearance of the outcomes are different. 70 00:03:51.330 --> 00:03:53.823 Which definition of strategy will I talk about? 71 00:03:55.860 --> 00:03:57.360 One thing is clear: 72 00:03:57.360 --> 00:04:00.390 I do not plan to talk about our technical strategy. 73 00:04:00.390 --> 00:04:02.070 Our technical strategy, 74 00:04:02.070 --> 00:04:05.040 which relates to the underlying technology of the web 75 00:04:05.040 --> 00:04:07.050 has been member driven, 76 00:04:07.050 --> 00:04:10.683 bottom up under the guidance of the TAG and the Director. 77 00:04:11.940 --> 00:04:15.573 Instead, I plan to discuss W3C's organizational strategy. 78 00:04:16.740 --> 00:04:19.080 That is one of the highest level objectives 79 00:04:19.080 --> 00:04:21.783 that W3C has as an organization, 80 00:04:22.908 --> 00:04:25.020 and how the W3C community 81 00:04:25.020 --> 00:04:27.813 has worked together to achieve those objectives. 82 00:04:29.970 --> 00:04:33.180 As you pay attention to the strategy retrospective, 83 00:04:33.180 --> 00:04:36.540 I want you to consider the critical success factors. 84 00:04:36.540 --> 00:04:40.350 In my mind, a key critical success factor 85 00:04:40.350 --> 00:04:45.350 has been the W3C Team led by Tim Berners-Lee and W3M. 86 00:04:46.440 --> 00:04:50.910 While W3C Hosts have some formal responsibility for W3C, 87 00:04:50.910 --> 00:04:52.290 they have not been overly active 88 00:04:52.290 --> 00:04:54.243 in the last decade until recently. 89 00:04:55.530 --> 00:04:58.650 The Team has benefited from the vision, example, 90 00:04:58.650 --> 00:05:01.623 and unique insight of our Director, Tim Berners-Lee. 91 00:05:02.640 --> 00:05:06.150 As he has reduced the time he can spend working on W3C, 92 00:05:06.150 --> 00:05:08.790 W3M has stepped into leadership 93 00:05:08.790 --> 00:05:11.130 and driven enormous value for the web 94 00:05:11.130 --> 00:05:13.623 as we will see in the subsequent slides. 95 00:05:15.030 --> 00:05:16.503 Please turn to slide five. slide-5 00:05:19.650 --> 00:05:22.740 I just mentioned that we have always had a strategy, 97 00:05:22.740 --> 00:05:25.173 whether we stated it explicitly or not. 98 00:05:26.190 --> 00:05:30.330 In 2011 at one of my first AC meetings 99 00:05:30.330 --> 00:05:32.733 I described four strategic elements: 100 00:05:33.600 --> 00:05:35.280 The right topics, 101 00:05:35.280 --> 00:05:38.040 i.e, having the best set of Working Groups, 102 00:05:38.040 --> 00:05:42.630 Communications, business development, 103 00:05:42.630 --> 00:05:45.450 and broadening outreach to stakeholders. 104 00:05:45.450 --> 00:05:47.790 Over 11 years the focus has changed 105 00:05:47.790 --> 00:05:50.460 but many of these themes remain. 106 00:05:50.460 --> 00:05:52.173 Please turn to slide six. slide-6 00:05:57.000 --> 00:05:59.340 After introducing those four elements, 108 00:05:59.340 --> 00:06:04.340 I started a practice of measuring key metrics against these, 109 00:06:04.560 --> 00:06:09.560 which I introduced in my spring 2012 CEO presentation 110 00:06:10.260 --> 00:06:11.883 with a participation slide. 111 00:06:13.620 --> 00:06:15.930 You know that you are talking about a strategy 112 00:06:15.930 --> 00:06:19.530 if you define metrics and regularly measure them. 113 00:06:19.530 --> 00:06:22.170 I continued a semi-annual practice 114 00:06:22.170 --> 00:06:24.930 of reporting these metrics at AC meetings 115 00:06:24.930 --> 00:06:29.930 for 16 consecutive AC meetings until they went virtual 116 00:06:29.940 --> 00:06:33.153 and I felt a different format for reporting was required. 117 00:06:34.950 --> 00:06:36.393 Please turn to slide seven. slide-7 00:06:38.610 --> 00:06:41.130 Another way to truly appreciate a strategy 119 00:06:41.130 --> 00:06:43.143 is to see how resources are assigned. 120 00:06:44.130 --> 00:06:47.520 See slide 13 for my presentation 121 00:06:47.520 --> 00:06:50.580 at our fall 2020 AC meeting, 122 00:06:50.580 --> 00:06:53.460 and we're gonna come back to this slide later 123 00:06:53.460 --> 00:06:56.043 when I will describe what it means in detail. 124 00:06:57.540 --> 00:06:58.890 Please turn to slide eight. slide-8 00:07:02.370 --> 00:07:04.830 The last three slides summarize 126 00:07:04.830 --> 00:07:08.013 how we have communicated our strategy in past meetings. 127 00:07:08.970 --> 00:07:12.780 Today, I will describe the full impact of our strategy 128 00:07:12.780 --> 00:07:14.013 over the last decade. 129 00:07:16.230 --> 00:07:19.470 In 2010 when I joined W3C 130 00:07:19.470 --> 00:07:22.593 our organization was in desperate need of a new strategy. 131 00:07:24.090 --> 00:07:27.843 Membership was down by 50% in its previous decade. 132 00:07:28.830 --> 00:07:31.140 Revenues were off. 133 00:07:31.140 --> 00:07:33.600 We needed a bailout from the Internet Society 134 00:07:33.600 --> 00:07:34.893 to pay our bills. 135 00:07:35.790 --> 00:07:37.440 Our most important spec, 136 00:07:37.440 --> 00:07:41.730 HTML was primarily being done at the WHATWG 137 00:07:41.730 --> 00:07:43.653 with some partnership with us. 138 00:07:44.550 --> 00:07:46.683 We needed to make serious changes. 139 00:07:48.810 --> 00:07:51.060 We convened five task forces 140 00:07:51.060 --> 00:07:53.850 to look at how to create a sustainable business model 141 00:07:53.850 --> 00:07:55.083 for W3C. 142 00:07:56.640 --> 00:07:58.740 These task forces were designed to analyze 143 00:07:58.740 --> 00:08:00.990 what was wrong with W3C 144 00:08:00.990 --> 00:08:03.303 and place us on a trajectory to success. 145 00:08:04.860 --> 00:08:07.440 You can see the participants on the slide. 146 00:08:07.440 --> 00:08:10.290 Then, as now, we were member driven. 147 00:08:10.290 --> 00:08:13.200 Over 60% of the people that participated 148 00:08:13.200 --> 00:08:16.533 were from the membership and the general W3C community. 149 00:08:18.600 --> 00:08:21.900 I won't describe the task force conclusions in detail. 150 00:08:21.900 --> 00:08:24.750 That itself is somewhat dated at this point. 151 00:08:24.750 --> 00:08:28.050 But let's look at the objectives for those task forces. 152 00:08:28.050 --> 00:08:29.790 We wanted to make W3C the place 153 00:08:29.790 --> 00:08:32.400 where people would want to bring web standards. 154 00:08:32.400 --> 00:08:35.100 We wanted a sustainable business model. 155 00:08:35.100 --> 00:08:36.930 We were concerned about being global, 156 00:08:36.930 --> 00:08:40.020 being accessible, and prioritizing users. 157 00:08:40.020 --> 00:08:42.070 We were thoughtful about core technology. 158 00:08:43.560 --> 00:08:47.280 From that task force came most of the strategic elements 159 00:08:47.280 --> 00:08:49.180 that have guided us for over a decade. 160 00:08:50.130 --> 00:08:52.450 They generated the participation metrics 161 00:08:53.905 --> 00:08:55.653 that I referenced moments ago. 162 00:08:57.210 --> 00:09:00.660 Good strategy is often described as an open loose leaf. 163 00:09:00.660 --> 00:09:04.710 You have a strategy, but you respond with the times. 164 00:09:04.710 --> 00:09:08.520 You add a page to the loose leaf as you add new focus areas 165 00:09:08.520 --> 00:09:10.410 and you drop ones that are complete 166 00:09:10.410 --> 00:09:12.160 or whose importance has diminished. 167 00:09:13.470 --> 00:09:14.730 So while we have not completely 168 00:09:14.730 --> 00:09:17.340 revamped our strategy lately, 169 00:09:17.340 --> 00:09:22.340 in a real sense the 2010 strategy with agile modifications 170 00:09:24.930 --> 00:09:27.273 has been our strategy over the last decade. 171 00:09:28.230 --> 00:09:32.010 Each year we re-examine the overarching goals, 172 00:09:32.010 --> 00:09:33.300 reset the metrics, 173 00:09:33.300 --> 00:09:36.030 and make the work more relevant to the times. 174 00:09:36.030 --> 00:09:39.063 We add elements and sunset other elements. 175 00:09:41.130 --> 00:09:42.870 I said that the purpose of the task forces 176 00:09:42.870 --> 00:09:44.940 was to lead us to success. 177 00:09:44.940 --> 00:09:48.210 I hope as you review our strategy in the upcoming slides, 178 00:09:48.210 --> 00:09:50.790 you will agree that we have been successful. 179 00:09:50.790 --> 00:09:54.870 Today W3C is a dynamic exciting community. 180 00:09:54.870 --> 00:09:56.730 W3C's value to its members 181 00:09:56.730 --> 00:09:59.313 and the broader web ecosystem is immense. 182 00:10:00.270 --> 00:10:03.663 Please continue to hear the journey we have been on. 183 00:10:05.220 --> 00:10:06.633 Please turn to slide nine. slide-9 00:10:09.570 --> 00:10:11.130 With that background, 185 00:10:11.130 --> 00:10:14.190 today's presentation reviews our key strategy elements 186 00:10:14.190 --> 00:10:16.890 as they have evolved over the last decade. 187 00:10:16.890 --> 00:10:21.003 The key elements are nested under three strategic pillars. 188 00:10:22.140 --> 00:10:25.503 The first strategic pillar is the single word participation. 189 00:10:26.700 --> 00:10:30.060 For W3C to serve the web it needs to be the place 190 00:10:30.060 --> 00:10:32.310 where people come to work on web standards 191 00:10:32.310 --> 00:10:34.683 and it needs to have the right participants. 192 00:10:35.880 --> 00:10:38.310 A forum for innovation and standardization 193 00:10:38.310 --> 00:10:41.343 only works if there is critical mass in that forum. 194 00:10:42.780 --> 00:10:46.260 Under participation, first we have Global. 195 00:10:46.260 --> 00:10:47.550 The web affects everyone 196 00:10:47.550 --> 00:10:50.073 and we need the entire planet at the table. 197 00:10:51.300 --> 00:10:53.280 The second is Community. 198 00:10:53.280 --> 00:10:54.930 The web architect, developer, 199 00:10:54.930 --> 00:10:57.060 and designer communities are huge 200 00:10:57.060 --> 00:10:58.960 and we need those voices at the table. 201 00:11:00.360 --> 00:11:02.130 The third is Member Growth 202 00:11:02.130 --> 00:11:04.860 for both revenue and global reach. 203 00:11:04.860 --> 00:11:06.993 The fourth is Diversity and Inclusion. 204 00:11:08.730 --> 00:11:09.930 The second strategic pillar 205 00:11:09.930 --> 00:11:11.980 is the strength of our technical program. 206 00:11:13.440 --> 00:11:15.300 A strategy goal underneath that 207 00:11:15.300 --> 00:11:17.013 is innovation and incubation. 208 00:11:18.060 --> 00:11:20.700 We aim to be a large dynamic forum 209 00:11:20.700 --> 00:11:22.830 which attracts as many people as possible 210 00:11:22.830 --> 00:11:24.530 who can contribute to our mission. 211 00:11:26.100 --> 00:11:30.000 Another key goal is addressing societal needs. 212 00:11:30.000 --> 00:11:32.430 And we can only do that, all of this, 213 00:11:32.430 --> 00:11:34.503 with W3C Process agility. 214 00:11:36.780 --> 00:11:40.290 The third strategic pillar is Member Value. 215 00:11:40.290 --> 00:11:42.060 Some of it is ensuring that members 216 00:11:42.060 --> 00:11:44.340 are getting what they paid for. 217 00:11:44.340 --> 00:11:46.710 But some of it is in serving industry needs 218 00:11:46.710 --> 00:11:49.143 which may be different than the core web. 219 00:11:50.550 --> 00:11:52.200 The web touches everything. 220 00:11:52.200 --> 00:11:55.920 So another element is partnering with other organizations. 221 00:11:55.920 --> 00:11:58.530 These are critical to make W3C the most desirable place 222 00:11:58.530 --> 00:12:02.523 for web standards and its members the drivers of this work. 223 00:12:03.870 --> 00:12:06.660 This is how W3C members contribute ideas 224 00:12:06.660 --> 00:12:09.243 to achieve leadership for the web at W3C. 225 00:12:14.760 --> 00:12:16.470 Underneath all of this, 226 00:12:16.470 --> 00:12:19.020 I will describe how we assign resources 227 00:12:19.020 --> 00:12:21.870 because resource allocation as I said above 228 00:12:21.870 --> 00:12:23.463 is the essence of strategy. 229 00:12:26.100 --> 00:12:29.040 Beyond these ten strategies that I will talk about, 230 00:12:29.040 --> 00:12:31.920 are two strategies to reach our goals for the future: 231 00:12:31.920 --> 00:12:33.120 the creation of a legal entity 232 00:12:33.120 --> 00:12:34.720 and preparing for Director-free. 233 00:12:35.970 --> 00:12:37.620 These are such large topics 234 00:12:37.620 --> 00:12:39.360 that they are covered elsewhere in this meeting 235 00:12:39.360 --> 00:12:40.710 and not in my presentation. 236 00:12:42.480 --> 00:12:43.730 Please turn to slide ten. slide-10 00:12:47.160 --> 00:12:52.160 Historically, W3C was strong in Europe, US, Japan, and Korea 238 00:12:53.280 --> 00:12:54.980 and weak in the rest of the world. 239 00:12:56.070 --> 00:13:01.070 Our global strategy is to get us strong presence everywhere. 240 00:13:02.970 --> 00:13:05.340 I want to emphasize the work in China 241 00:13:05.340 --> 00:13:08.943 because for many years W3C was almost absent in China. 242 00:13:09.960 --> 00:13:13.140 China is a huge country with a huge market. 243 00:13:13.140 --> 00:13:16.500 China has a sizable web development community. 244 00:13:16.500 --> 00:13:20.670 In 2010, there were no large commercial Chinese companies 245 00:13:20.670 --> 00:13:22.470 in W3C. 246 00:13:22.470 --> 00:13:25.770 If that hadn't changed, it would have been a disaster 247 00:13:25.770 --> 00:13:27.963 for web architecture and interoperability. 248 00:13:29.310 --> 00:13:30.450 Whenever you have two groups 249 00:13:30.450 --> 00:13:33.450 developing the same technology without being in contact, 250 00:13:33.450 --> 00:13:35.370 you run the risk of fragmentation. 251 00:13:35.370 --> 00:13:38.823 And our primary technical mission is interoperability. 252 00:13:40.350 --> 00:13:43.740 We quickly went to work and established a host in China. 253 00:13:43.740 --> 00:13:46.020 We recruited the most important Chinese brands 254 00:13:46.020 --> 00:13:47.313 to join our community. 255 00:13:48.570 --> 00:13:51.270 But we also realized that establishing a host 256 00:13:51.270 --> 00:13:53.100 is not the end of outreach to China; 257 00:13:53.100 --> 00:13:54.990 it is only the beginning. 258 00:13:54.990 --> 00:13:56.880 We have worked so hard 259 00:13:56.880 --> 00:13:59.793 to ensure that we have one web community. 260 00:14:00.780 --> 00:14:03.360 We have increased translations to Chinese, Japanese, 261 00:14:03.360 --> 00:14:04.890 and Korean. 262 00:14:04.890 --> 00:14:08.223 Most importantly, we put focus on listening and bridging. 263 00:14:09.330 --> 00:14:11.370 We try to understand and hear the needs 264 00:14:11.370 --> 00:14:13.530 of the global community. 265 00:14:13.530 --> 00:14:16.833 We have an enormously active Chinese Web Interest Group. 266 00:14:17.760 --> 00:14:20.373 Today we have 40+ Chinese members, 267 00:14:22.350 --> 00:14:24.663 including nine Full members. 268 00:14:26.670 --> 00:14:30.123 A capstone achievement has been our work in MiniApps. 269 00:14:30.960 --> 00:14:32.550 While we prefer that applications 270 00:14:32.550 --> 00:14:34.350 run in pure web environments, 271 00:14:34.350 --> 00:14:37.470 we recognize that they will often run in hybrid mode, 272 00:14:37.470 --> 00:14:40.440 leveraging web technology and marrying it 273 00:14:40.440 --> 00:14:43.353 with outstanding native platform capabilities. 274 00:14:44.220 --> 00:14:46.530 When that became predominant in China, 275 00:14:46.530 --> 00:14:48.810 we began our MiniApps work 276 00:14:48.810 --> 00:14:51.570 to get as much interoperability as possible 277 00:14:51.570 --> 00:14:54.633 in the hybrid world and the pieces that use web technology. 278 00:14:55.830 --> 00:14:58.740 Hundreds of millions of people using MiniApps 279 00:14:58.740 --> 00:15:01.350 will benefit from our standards work. 280 00:15:01.350 --> 00:15:02.760 And across the globe, 281 00:15:02.760 --> 00:15:05.130 the web community is applying similar ideas 282 00:15:05.130 --> 00:15:08.043 to other hybrid app situations. 283 00:15:09.480 --> 00:15:10.833 Please turn to slide 11. slide-11 00:15:14.490 --> 00:15:17.220 Being global is not exclusively about China. 285 00:15:17.220 --> 00:15:19.680 We have always been strong in Japan, 286 00:15:19.680 --> 00:15:22.830 which is our second largest country by membership. 287 00:15:22.830 --> 00:15:25.410 Compared to the rest of the world, it is in Japan, 288 00:15:25.410 --> 00:15:28.350 where we have the most tight knit partnership 289 00:15:28.350 --> 00:15:30.543 between local members and our local team. 290 00:15:31.470 --> 00:15:34.710 That allows us to better incorporate unique Japanese needs 291 00:15:34.710 --> 00:15:38.250 in a range of topics from publishing, telecommunications, 292 00:15:38.250 --> 00:15:39.693 and vertical tech support. 293 00:15:41.190 --> 00:15:43.650 Our initiatives have been very successful, 294 00:15:43.650 --> 00:15:45.120 but we still have a great deal of work to do 295 00:15:45.120 --> 00:15:46.650 in the rest of the world. 296 00:15:46.650 --> 00:15:49.980 Recently we have been partnering with W3C chapters 297 00:15:49.980 --> 00:15:53.852 in Latin America, the Persian Gulf, Australia, 298 00:15:53.852 --> 00:15:57.900 Southeast Asia and elsewhere to extend our footprint. 299 00:15:57.900 --> 00:15:59.403 Please turn to slide 12. slide-12 00:16:06.780 --> 00:16:10.260 If the first strategy is to increase our global reach, 301 00:16:10.260 --> 00:16:13.800 the second strategy is to grow the W3C community, 302 00:16:13.800 --> 00:16:17.490 which ensures that W3C remains the preeminent place 303 00:16:17.490 --> 00:16:18.940 where web standards are done. 304 00:16:20.310 --> 00:16:22.460 For those who were not around ten years ago, 305 00:16:23.430 --> 00:16:27.423 I need to paint the bleak picture that we faced. 306 00:16:28.500 --> 00:16:31.623 While we had Working Groups and the Recommendation Track, 307 00:16:32.610 --> 00:16:35.100 if anyone wanted to work on something new, 308 00:16:35.100 --> 00:16:37.020 it was nearly impossible 309 00:16:37.020 --> 00:16:39.150 because new ideas were often not mature enough 310 00:16:39.150 --> 00:16:40.473 to be on the REC Track. 311 00:16:42.000 --> 00:16:43.860 When people wanted to explore something new 312 00:16:43.860 --> 00:16:48.180 they created a new organization for that exploration. 313 00:16:48.180 --> 00:16:51.300 And if the work matured they would stay outside of W3C 314 00:16:51.300 --> 00:16:52.773 to finalize their standard. 315 00:16:54.030 --> 00:16:57.000 That fragmentation was harmful to the web community 316 00:16:57.000 --> 00:16:58.923 and devastating to W3C. 317 00:17:01.890 --> 00:17:05.460 We created a new track of permissionless innovation 318 00:17:05.460 --> 00:17:06.693 called Community Groups. 319 00:17:08.280 --> 00:17:09.543 It was tough to design. 320 00:17:11.310 --> 00:17:12.750 We opened it up to non-members, 321 00:17:12.750 --> 00:17:14.500 which was a controversial decision. 322 00:17:16.530 --> 00:17:20.550 Some ask, should we as a member organization 323 00:17:20.550 --> 00:17:22.803 provide such value to non-members? 324 00:17:24.510 --> 00:17:26.670 We decided that was a requirement 325 00:17:26.670 --> 00:17:29.220 if we were to build the thriving community we needed. 326 00:17:31.410 --> 00:17:33.093 The success was extraordinary. 327 00:17:34.080 --> 00:17:38.400 Instead of being a community of 1,500 engineers 328 00:17:38.400 --> 00:17:40.083 that we were in 2010, 329 00:17:41.490 --> 00:17:45.600 we are now a community of over 15,000 engineers, 330 00:17:45.600 --> 00:17:47.073 a growth of 10x. 331 00:17:48.360 --> 00:17:50.910 There are so many ideas and so much energy 332 00:17:50.910 --> 00:17:53.410 coming out of that vastly increased participation. 333 00:17:56.520 --> 00:18:00.303 Recently I was asked, what is W3C's greatest strength? 334 00:18:02.160 --> 00:18:06.090 Without hesitation I answered, the W3C community. 335 00:18:06.090 --> 00:18:09.210 There is simply no way to replicate what we have. 336 00:18:09.210 --> 00:18:11.910 Today we have 381 Community Groups 337 00:18:11.910 --> 00:18:13.263 and three Business Groups. 338 00:18:15.480 --> 00:18:18.330 We have broadened the community in other ways. 339 00:18:18.330 --> 00:18:20.910 We provided the option of a forkable document license 340 00:18:20.910 --> 00:18:22.860 to appeal to the open source community. 341 00:18:23.880 --> 00:18:26.823 We strengthened a pattern of doing our work in public. 342 00:18:27.720 --> 00:18:29.820 And when we moved a lot of our tooling to GitHub 343 00:18:29.820 --> 00:18:31.410 it became easier for the public 344 00:18:31.410 --> 00:18:33.573 to weigh in on work in the REC Track. 345 00:18:35.490 --> 00:18:40.490 A tangible result of CGs is REC Track standards. 346 00:18:40.500 --> 00:18:42.240 That leads to the next related topic. 347 00:18:42.240 --> 00:18:43.743 Please turn to slide 13. slide-13 00:18:48.450 --> 00:18:51.120 Our CGs have been hugely productive. 349 00:18:51.120 --> 00:18:53.700 They have 900 GitHub repositories 350 00:18:53.700 --> 00:18:57.723 and have exchanged more than 8,000 messages so far in 2022. 351 00:18:59.730 --> 00:19:03.150 Some of the individual CG communities are huge. 352 00:19:03.150 --> 00:19:05.580 The WebAssembly Community Group alone 353 00:19:05.580 --> 00:19:08.313 has 1,451 participants. 354 00:19:09.930 --> 00:19:12.720 The Web Platform Incubator Community Group 355 00:19:12.720 --> 00:19:16.953 has recorded over 2,600 repository events in the last year. 356 00:19:18.570 --> 00:19:20.580 The Credentials Community Group 357 00:19:20.580 --> 00:19:24.573 generated over 1,700 list discussions in the past 12 months. 358 00:19:26.400 --> 00:19:30.060 These groups work on many topics, not only new specs. 359 00:19:30.060 --> 00:19:32.490 The W3C Process Community Group 360 00:19:32.490 --> 00:19:34.830 is where the W3C community meets 361 00:19:34.830 --> 00:19:36.933 to keep our processes agile and relevant. 362 00:19:39.000 --> 00:19:43.830 In the last few years, we have seen a novel workflow 363 00:19:43.830 --> 00:19:46.580 where a CG has a tight relationship with a Working Group. 364 00:19:47.730 --> 00:19:50.850 The CG incubates the next set of ideas, 365 00:19:50.850 --> 00:19:52.950 then passes them off to the Working Group. 366 00:19:53.880 --> 00:19:57.270 This creates a tight cycle of innovation and adoption, 367 00:19:57.270 --> 00:19:59.620 which helps us rapidly evolve our technologies. 368 00:20:01.170 --> 00:20:03.990 The slide lists some key CGs 369 00:20:03.990 --> 00:20:06.633 to exemplify several of these points. 370 00:20:11.790 --> 00:20:13.293 Please turn to slide 14. slide-14 00:20:17.850 --> 00:20:21.990 W3C has been noted for its commitment to accessibility 372 00:20:21.990 --> 00:20:25.863 since Tim Berners-Lee's letter of September 1996. 373 00:20:27.330 --> 00:20:28.740 From that early beginning 374 00:20:28.740 --> 00:20:31.530 we have increased investment and focus in many areas 375 00:20:31.530 --> 00:20:33.723 to address key society concerns. 376 00:20:35.580 --> 00:20:37.740 It starts with accessibility. 377 00:20:37.740 --> 00:20:40.143 We are a values-driven organization. 378 00:20:41.190 --> 00:20:43.740 As the web became more critical to society, 379 00:20:43.740 --> 00:20:46.473 we could not allow anyone to be left out. 380 00:20:48.120 --> 00:20:51.750 There are over 1 billion people with disabilities worldwide 381 00:20:51.750 --> 00:20:54.633 and all deserve full access to the web. 382 00:20:56.580 --> 00:21:01.170 Today, over 100 W3C member organizations 383 00:21:01.170 --> 00:21:04.259 have expressed interest in or directly participate 384 00:21:04.259 --> 00:21:07.180 in the Web Accessibility Initiative activities 385 00:21:08.430 --> 00:21:11.040 illustrating the strength of our effort. 386 00:21:11.040 --> 00:21:12.930 Our flagship Accessibility Guidelines 387 00:21:12.930 --> 00:21:14.760 are standard for the web, 388 00:21:14.760 --> 00:21:17.883 are often adopted by corporations as corporate imperatives, 389 00:21:19.800 --> 00:21:22.920 and are often adopted as regulatory requirements. 390 00:21:22.920 --> 00:21:27.920 Most notably in the EU with their EN 301 549. 391 00:21:29.640 --> 00:21:32.880 Earlier this year the longtime director of WAI, 392 00:21:32.880 --> 00:21:36.330 Judy Brewer, won a top level ACM award, 393 00:21:36.330 --> 00:21:38.133 the ACM Policy Award. 394 00:21:41.370 --> 00:21:43.980 While we are proud of our success in accessibility, 395 00:21:43.980 --> 00:21:45.033 we have more to do. 396 00:21:46.500 --> 00:21:48.630 Despite accessibility work being a core part 397 00:21:48.630 --> 00:21:52.593 of W3C's commitment, member interest, and success, 398 00:21:53.430 --> 00:21:57.150 this work has been largely externally funded, 399 00:21:57.150 --> 00:21:59.800 placing additional burden on the accessibility staff. 400 00:22:00.810 --> 00:22:03.750 It is time that W3C moves forward on a path 401 00:22:03.750 --> 00:22:06.510 towards normalizing the funding of this work 402 00:22:06.510 --> 00:22:08.190 by allocating more membership funding 403 00:22:08.190 --> 00:22:09.723 to these important activities. 404 00:22:11.760 --> 00:22:13.470 In internationalization 405 00:22:13.470 --> 00:22:15.870 we ensure that there is language enablement, 406 00:22:15.870 --> 00:22:20.370 developer support, and author support across many languages. 407 00:22:20.370 --> 00:22:25.110 We maintain a large matrix of gaps, illustrated in this slide, 408 00:22:25.110 --> 00:22:27.960 to improve the support of different languages on the web. 409 00:22:29.700 --> 00:22:33.270 Our Privacy Interest Group and our security reviews 410 00:22:33.270 --> 00:22:36.030 recognize that in the rush to get the web up and running 411 00:22:36.030 --> 00:22:39.570 there have been compromises on privacy and security. 412 00:22:39.570 --> 00:22:42.510 We aim to restore better privacy and security 413 00:22:42.510 --> 00:22:44.860 in balance with the growth of functional needs. 414 00:22:47.940 --> 00:22:49.080 We have long been sensitive 415 00:22:49.080 --> 00:22:51.270 to these horizontal review areas, 416 00:22:51.270 --> 00:22:55.563 but as we have matured we have become much more systematic. 417 00:22:56.970 --> 00:23:01.950 Only in 2012 did we add the horizontal review requirement 418 00:23:01.950 --> 00:23:04.550 into our guidebook on how to create a Working Group. 419 00:23:05.400 --> 00:23:06.240 We have spent years 420 00:23:06.240 --> 00:23:09.030 improving the tooling for horizontal reviews. 421 00:23:09.030 --> 00:23:13.200 In 2021 we actually performed 891 reviews 422 00:23:13.200 --> 00:23:15.603 across a range of charters and specs. 423 00:23:17.520 --> 00:23:19.440 Talking about reviews brings me to the TAG, 424 00:23:19.440 --> 00:23:21.540 the Technical Architecture Group. 425 00:23:21.540 --> 00:23:22.530 For several years now 426 00:23:22.530 --> 00:23:25.800 under the strong leadership of Dan Appelquist and Peter Linss, 427 00:23:25.800 --> 00:23:27.240 the TAG has been a steady hand 428 00:23:27.240 --> 00:23:29.690 in guiding the technical architecture of the web. 429 00:23:30.720 --> 00:23:34.260 The key methodology is architecture review of specs. 430 00:23:34.260 --> 00:23:36.060 They review the work of groups 431 00:23:36.060 --> 00:23:37.890 and advise in how to make it compliant 432 00:23:37.890 --> 00:23:39.213 with the rest of the web. 433 00:23:40.290 --> 00:23:44.670 In 2021 they actually closed 674 review requests, 434 00:23:44.670 --> 00:23:48.003 amounting to 128 completed design reviews. 435 00:23:49.860 --> 00:23:52.500 While on the topic of the TAG and key to our values 436 00:23:52.500 --> 00:23:55.020 is the Ethical Web Principles document 437 00:23:55.020 --> 00:23:57.660 published in May 2022. 438 00:23:57.660 --> 00:24:00.360 It's now in the W3C Statement Track 439 00:24:00.360 --> 00:24:03.960 recently introduced in the W3C Process. 440 00:24:03.960 --> 00:24:07.230 This landmark document provides important guidance 441 00:24:07.230 --> 00:24:09.390 and shows our commitment to building an architecture 442 00:24:09.390 --> 00:24:12.843 which is values-based and addresses societal needs. 443 00:24:17.400 --> 00:24:20.280 Overall, the percentage of W3C technical staff 444 00:24:20.280 --> 00:24:25.110 working on societal needs has grown from 21% to 33% 445 00:24:25.110 --> 00:24:26.163 in ten years. 446 00:24:27.750 --> 00:24:29.223 Please turn to slide 15. slide-15 00:24:32.820 --> 00:24:36.180 Over the last decade, we reversed a decline in membership 448 00:24:36.180 --> 00:24:37.833 and have shown consistent growth. 449 00:24:38.940 --> 00:24:43.940 In the last ten years, membership has grown by over 50%. 450 00:24:45.355 --> 00:24:48.613 In the previous ten years it had declined by 37%. 451 00:24:52.950 --> 00:24:57.150 Aside from the baseline numbers of total members, 452 00:24:57.150 --> 00:24:59.160 the growth has been particularly healthy 453 00:24:59.160 --> 00:25:02.010 because we have had a larger number of large companies 454 00:25:02.010 --> 00:25:03.030 that are members, 455 00:25:03.030 --> 00:25:05.643 showing a greater impact on the economy at large. 456 00:25:06.810 --> 00:25:08.220 As I will discuss momentarily, 457 00:25:08.220 --> 00:25:11.250 we are seeing greater representation across industries, 458 00:25:11.250 --> 00:25:13.263 showing a broadening of our appeal. 459 00:25:14.970 --> 00:25:15.840 On the other hand 460 00:25:15.840 --> 00:25:18.210 we have a significant number of startup members 461 00:25:18.210 --> 00:25:19.983 always bringing in new ideas. 462 00:25:21.480 --> 00:25:22.710 We achieve this growth 463 00:25:22.710 --> 00:25:25.200 despite various recessions in the economy 464 00:25:25.200 --> 00:25:27.633 and despite merger activity in some industries. 465 00:25:28.710 --> 00:25:30.000 And we achieve the growth 466 00:25:30.000 --> 00:25:33.450 despite the reduction in independent browser engines. 467 00:25:33.450 --> 00:25:35.250 So underneath the top line growth, 468 00:25:35.250 --> 00:25:38.433 we see vitality in the organization at many levels. 469 00:25:39.570 --> 00:25:41.223 Please turn to slide 16. slide-16 00:25:45.360 --> 00:25:49.380 At the outset the web facilitated access to global data 471 00:25:49.380 --> 00:25:51.330 and allowed everyone to be a publisher. 472 00:25:52.440 --> 00:25:54.510 Soon companies use this capability 473 00:25:54.510 --> 00:25:57.260 to use the web for corporate advertising and marketing. 474 00:25:59.370 --> 00:26:00.990 The technologies needed to support this 475 00:26:00.990 --> 00:26:04.470 were quite common: HTML, CSS, DOM, 476 00:26:04.470 --> 00:26:06.170 and other core specs of the web. 477 00:26:07.170 --> 00:26:09.690 But more recently 478 00:26:09.690 --> 00:26:11.850 various industries have leveraged the web 479 00:26:11.850 --> 00:26:14.100 as an infrastructure for their core business. 480 00:26:15.270 --> 00:26:18.240 For businesses as diverse as retail sales, 481 00:26:18.240 --> 00:26:21.420 telecommunications, publishing and media, 482 00:26:21.420 --> 00:26:23.280 there are unique needs for web technology 483 00:26:23.280 --> 00:26:24.783 to support those businesses. 484 00:26:26.010 --> 00:26:28.640 While W3C provided only modest support for that 485 00:26:28.640 --> 00:26:30.033 in the early years, 486 00:26:30.870 --> 00:26:34.140 that has become a key focus in recent years. 487 00:26:34.140 --> 00:26:36.210 See the bar chart on the slide, 488 00:26:36.210 --> 00:26:39.690 which describes when we introduced various industry areas 489 00:26:39.690 --> 00:26:42.483 together with some other new focus areas. 490 00:26:44.760 --> 00:26:46.923 In 2014 we took it to the next level. 491 00:26:48.150 --> 00:26:50.670 We created a Champion program. 492 00:26:50.670 --> 00:26:52.380 For each industry, 493 00:26:52.380 --> 00:26:55.320 a Team Contact was asked to work with thought leaders 494 00:26:55.320 --> 00:26:56.523 in those industries. 495 00:26:57.390 --> 00:27:00.210 The objective was to develop a common vision 496 00:27:00.210 --> 00:27:01.503 with two components. 497 00:27:02.550 --> 00:27:03.420 We wanted to learn 498 00:27:03.420 --> 00:27:06.720 how we could improve the capabilities of the industry 499 00:27:06.720 --> 00:27:09.540 with additional web standards. 500 00:27:09.540 --> 00:27:11.850 And we want to learn how those standards at times 501 00:27:11.850 --> 00:27:14.310 could enhance the Web overall, 502 00:27:14.310 --> 00:27:17.703 being a better technology base for all users and consumers. 503 00:27:19.680 --> 00:27:21.843 This has had a huge impact. 504 00:27:24.384 --> 00:27:28.020 There are over 60 REC Track specs 505 00:27:28.020 --> 00:27:29.460 that are either being developed 506 00:27:29.460 --> 00:27:32.343 or have been developed that are industry specific. 507 00:27:34.590 --> 00:27:38.700 In 2015 I reported to the AC that 55% of our Full members 508 00:27:38.700 --> 00:27:39.993 are industry specific. 509 00:27:40.860 --> 00:27:42.510 As a part of our total, 510 00:27:42.510 --> 00:27:45.633 32% of all members being industry specific. 511 00:27:47.850 --> 00:27:50.493 Some of the impact is visible in our recognition. 512 00:27:51.870 --> 00:27:56.490 In the last seven years W3C has won three Emmy Awards, 513 00:27:56.490 --> 00:27:58.840 showing the impact of our work on television. 514 00:27:59.760 --> 00:28:02.340 We've had impact on other industries as well, 515 00:28:02.340 --> 00:28:03.570 although not every industry 516 00:28:03.570 --> 00:28:06.123 has such a visible means of recognition. 517 00:28:08.010 --> 00:28:09.573 Please turn to slide 17. slide-17 00:28:15.150 --> 00:28:17.850 The web technology stack touches the technologies 519 00:28:17.850 --> 00:28:19.950 of many organizations. 520 00:28:19.950 --> 00:28:21.240 To maximize our leverage 521 00:28:21.240 --> 00:28:23.853 requires that we broadly partner with everyone. 522 00:28:25.140 --> 00:28:27.180 We don't have the bandwidth to deeply partner 523 00:28:27.180 --> 00:28:28.860 with all other groups. 524 00:28:28.860 --> 00:28:31.300 So we have simple liaisons with many partners 525 00:28:32.160 --> 00:28:34.560 and select a few to have deep partnerships with. 526 00:28:35.610 --> 00:28:38.133 We have approximately 100 liaisons overall. 527 00:28:40.140 --> 00:28:43.080 I still remember my first AC meeting in 2010 528 00:28:43.080 --> 00:28:44.313 just as I was starting. 529 00:28:45.360 --> 00:28:48.150 Members wanted a relationship with ISO 530 00:28:48.150 --> 00:28:51.093 to upstream our standards to that community at that time. 531 00:28:52.290 --> 00:28:54.540 The request had been dormant for a long time. 532 00:28:55.710 --> 00:28:56.760 I went to the microphone 533 00:28:56.760 --> 00:28:58.350 to ask whether there were any objections 534 00:28:58.350 --> 00:28:59.463 to upstreaming to ISO. 535 00:29:00.720 --> 00:29:02.010 None were offered. 536 00:29:02.010 --> 00:29:04.800 So we established a status of being a Submitter 537 00:29:04.800 --> 00:29:07.893 of our Publicly Available Specs to the ISO standards. 538 00:29:09.570 --> 00:29:11.763 Our deepest partnership is with the WHATWG. 539 00:29:12.930 --> 00:29:15.720 There was an unfortunate schism 15 years ago 540 00:29:15.720 --> 00:29:17.250 which caused a team of spec writers 541 00:29:17.250 --> 00:29:19.773 to develop HTML outside of W3C. 542 00:29:21.810 --> 00:29:24.513 When they formalized the organization in 2017, 543 00:29:25.650 --> 00:29:27.370 I provided a same-day blog post 544 00:29:28.373 --> 00:29:30.360 congratulating them for their progress 545 00:29:30.360 --> 00:29:32.313 and hoping we would work together. 546 00:29:33.240 --> 00:29:37.110 It was hard to swallow W3C's primacy for HTML, 547 00:29:37.110 --> 00:29:39.870 but we always prioritize first for the web 548 00:29:39.870 --> 00:29:41.853 and only second for W3C. 549 00:29:42.960 --> 00:29:45.990 As a result, we have since developed two MOUs 550 00:29:45.990 --> 00:29:50.610 to work with the WHATWG on HTML, DOM, Fetch, 551 00:29:50.610 --> 00:29:51.693 and other specs. 552 00:29:53.460 --> 00:29:56.160 Our broadest partnership is with the IETF 553 00:29:56.160 --> 00:29:59.130 since they provide standards that underlie the web. 554 00:29:59.130 --> 00:30:02.700 We work with them on security, privacy, IoT 555 00:30:02.700 --> 00:30:04.083 and many other areas. 556 00:30:05.190 --> 00:30:07.803 And together we are creating WebRTC standards. 557 00:30:09.210 --> 00:30:12.150 Sometimes the partnerships result in a merger, 558 00:30:12.150 --> 00:30:16.530 as when we brought IDPF folks into W3C in 2016. 559 00:30:17.970 --> 00:30:20.070 To succeed in industry verticals 560 00:30:20.070 --> 00:30:24.960 we work with EMVCo on payments, COVESA for automotive, 561 00:30:24.960 --> 00:30:28.500 CTA for media and entertainment, as well as others 562 00:30:28.500 --> 00:30:30.453 such as OGC for geospatial. 563 00:30:32.220 --> 00:30:33.633 Please turn to slide 18. slide-18 00:30:36.120 --> 00:30:41.120 At the end of the day, W3C's product is our specifications. 565 00:30:44.070 --> 00:30:46.410 So it is essential that part of our strategic focus 566 00:30:46.410 --> 00:30:48.510 relates to continuous improvement 567 00:30:48.510 --> 00:30:50.283 in how we generate standards. 568 00:30:51.810 --> 00:30:56.280 Since 2014 we have a new mechanism 569 00:30:56.280 --> 00:30:59.193 whereby we enhance our Process almost every year. 570 00:31:01.350 --> 00:31:04.110 We removed Last Call from the Process steps, 571 00:31:04.110 --> 00:31:06.480 we added a living standards track, 572 00:31:06.480 --> 00:31:09.210 we've included CEPC by reference, 573 00:31:09.210 --> 00:31:11.250 we added Registries. 574 00:31:11.250 --> 00:31:12.780 The table on this slide illustrates 575 00:31:12.780 --> 00:31:15.960 some of the key innovations in process agility 576 00:31:15.960 --> 00:31:17.763 over the last decade. 577 00:31:21.180 --> 00:31:24.450 Process agility is not limited to the formal Process steps 578 00:31:24.450 --> 00:31:25.900 on the Recommendation Track. 579 00:31:26.790 --> 00:31:28.340 It also relates to our tooling. 580 00:31:29.310 --> 00:31:30.720 In the early years of W3C 581 00:31:30.720 --> 00:31:33.450 there was no great tooling for what we do. 582 00:31:33.450 --> 00:31:34.863 So we invented our own. 583 00:31:36.060 --> 00:31:38.490 Today there are industry tools such as GitHub. 584 00:31:38.490 --> 00:31:41.253 So we customize industry tools for our own needs. 585 00:31:42.600 --> 00:31:46.740 In the W3C GitHub instance in 2021 586 00:31:46.740 --> 00:31:51.740 there were nearly 10,000 contributions per month on average, 587 00:31:52.110 --> 00:31:54.690 where a contribution is either an issue, a comment, 588 00:31:54.690 --> 00:31:55.803 or a pull request. 589 00:31:57.150 --> 00:31:57.990 There are other features 590 00:31:57.990 --> 00:32:01.170 on how we make spec development more agile, 591 00:32:01.170 --> 00:32:04.020 and we have eased the requirements on spec publishing 592 00:32:04.020 --> 00:32:05.673 so that more groups can publish. 593 00:32:07.080 --> 00:32:09.630 ClearSpec 2021 provides more clarity 594 00:32:09.630 --> 00:32:11.463 about the provenance of our specs. 595 00:32:14.250 --> 00:32:15.693 Please turn to slide 19. slide-19 00:32:19.440 --> 00:32:21.513 Next, I want to talk about Member value. 597 00:32:23.070 --> 00:32:25.830 You might find that to be strange; 598 00:32:25.830 --> 00:32:28.530 after all, every strategic element 599 00:32:28.530 --> 00:32:31.623 that I've been discussing is aimed to add Member value. 600 00:32:33.150 --> 00:32:35.043 But here I mean something specific. 601 00:32:35.970 --> 00:32:38.100 I'm talking about the way that we have held the line 602 00:32:38.100 --> 00:32:41.130 on price increases for Member dues. 603 00:32:41.130 --> 00:32:43.650 That is to say we are providing more and more 604 00:32:43.650 --> 00:32:45.243 and it is costing less. 605 00:32:46.470 --> 00:32:50.430 To be fair, this adds pressure on the Team to deliver more, 606 00:32:50.430 --> 00:32:52.650 but we have made that decision 607 00:32:52.650 --> 00:32:54.780 recognizing that Members have limited funds 608 00:32:54.780 --> 00:32:55.893 to pay for membership. 609 00:32:57.510 --> 00:33:00.180 Please look at the table on this slide. 610 00:33:00.180 --> 00:33:03.033 Our last general price increase was in 2008. 611 00:33:04.290 --> 00:33:05.520 Think about it; 612 00:33:05.520 --> 00:33:06.993 14 years ago. 613 00:33:08.430 --> 00:33:09.930 You can see in the second column 614 00:33:09.930 --> 00:33:11.643 what the fees were at that time. 615 00:33:13.380 --> 00:33:17.550 In 2015 we had a modest 12% increase 616 00:33:17.550 --> 00:33:19.203 but only for the largest firms. 617 00:33:20.340 --> 00:33:23.580 In the interim we slashed prices for mid-size companies 618 00:33:23.580 --> 00:33:25.050 and startups. 619 00:33:25.050 --> 00:33:25.890 In the fourth column 620 00:33:25.890 --> 00:33:28.500 you see that aside from the largest companies 621 00:33:28.500 --> 00:33:31.773 either there was no price increase or a marked decrease. 622 00:33:33.360 --> 00:33:35.700 We held the line despite inflation. 623 00:33:35.700 --> 00:33:40.680 The fifth column shows the real value of our current dues 624 00:33:40.680 --> 00:33:42.550 after 14 years of inflation 625 00:33:44.040 --> 00:33:47.073 using the US Consumer Price Index as the benchmark. 626 00:33:48.030 --> 00:33:50.760 And the final column shows that in real terms 627 00:33:50.760 --> 00:33:53.343 everyone's dues have become substantially lower. 628 00:33:55.170 --> 00:33:57.210 So all of the gain and function we provide 629 00:33:57.210 --> 00:34:00.423 is accompanied by a reduction in real cost. 630 00:34:02.044 --> 00:34:03.993 How do we do that? 631 00:34:04.830 --> 00:34:06.840 By cleverly relocating resources 632 00:34:06.840 --> 00:34:08.370 to where they are needed 633 00:34:08.370 --> 00:34:10.620 as we will demonstrate in a couple of slides. 634 00:34:12.060 --> 00:34:13.353 Please turn to slide 20. slide-20 00:34:18.150 --> 00:34:19.830 We have barely scratched the surface 636 00:34:19.830 --> 00:34:22.462 of the topics of diversity and inclusion 637 00:34:22.462 --> 00:34:25.233 but we have made some steady progress. 638 00:34:26.730 --> 00:34:28.860 Let's start with the requirement. 639 00:34:28.860 --> 00:34:31.050 The W3C technical community 640 00:34:31.050 --> 00:34:33.330 that sets technical standards for the web 641 00:34:33.330 --> 00:34:34.860 should look like our stakeholders 642 00:34:34.860 --> 00:34:37.863 and broadly draw inspiration from all of our stakeholders. 643 00:34:38.760 --> 00:34:40.590 Since the web serves the planet 644 00:34:40.590 --> 00:34:43.530 that means that our community must look like the planet, 645 00:34:43.530 --> 00:34:44.433 but it doesn't. 646 00:34:46.230 --> 00:34:48.360 The requirement to look like all of our stakeholders 647 00:34:48.360 --> 00:34:52.500 might be too far to reach for a member organization, 648 00:34:52.500 --> 00:34:53.490 but it's still helpful 649 00:34:53.490 --> 00:34:55.680 to keep that imperative in front of ourselves 650 00:34:55.680 --> 00:34:57.963 just to realize how far we most improve. 651 00:35:00.120 --> 00:35:01.560 Over the past several years 652 00:35:01.560 --> 00:35:02.910 we have tried to address diversity 653 00:35:02.910 --> 00:35:04.503 and inclusion in several ways. 654 00:35:06.300 --> 00:35:10.080 We are insisting on a positive work environment. 655 00:35:10.080 --> 00:35:14.340 A decade ago, our emails were loaded with snark, 656 00:35:14.340 --> 00:35:17.463 defined as snide, sarcastic, or disrespective of others. 657 00:35:18.420 --> 00:35:22.080 In 2015 we became one of the first standards organizations 658 00:35:22.080 --> 00:35:26.970 to create a Code of Conduct, but we didn't rest there. 659 00:35:26.970 --> 00:35:29.370 When we saw a more comprehensive code 660 00:35:29.370 --> 00:35:31.320 in the Geek Feminism site, 661 00:35:31.320 --> 00:35:34.413 we adapted that to improve our Code in 2021. 662 00:35:35.580 --> 00:35:37.110 That's not to say that we are perfect; 663 00:35:37.110 --> 00:35:40.380 we have more to do, but the Code has been a useful anchor 664 00:35:40.380 --> 00:35:41.763 to improve the situation. 665 00:35:43.500 --> 00:35:46.830 In 2018 we started to provide diversity scholarships 666 00:35:46.830 --> 00:35:49.290 for people from underrepresented communities 667 00:35:49.290 --> 00:35:52.683 to participate at W3C's annual conference, TPAC. 668 00:35:54.390 --> 00:35:57.180 We provide an annual report on progress and diversity 669 00:35:57.180 --> 00:35:59.133 in the senior W3C bodies. 670 00:36:00.000 --> 00:36:02.950 In the past several years, we have made measurable progress. 671 00:36:05.730 --> 00:36:07.230 Of all of our goals, 672 00:36:07.230 --> 00:36:08.970 this is one for which we have the most work 673 00:36:08.970 --> 00:36:12.300 in front of ourselves to get to where we want to be. 674 00:36:12.300 --> 00:36:16.440 How can we together make even more of a difference? 675 00:36:16.440 --> 00:36:18.640 That's something we need to keep working on. 676 00:36:19.740 --> 00:36:21.273 Please turn to slide 21. slide-21 00:36:25.230 --> 00:36:28.113 We have discussed our success in 10 strategy elements. 678 00:36:29.610 --> 00:36:32.850 How have we been so successful making so much progress 679 00:36:32.850 --> 00:36:35.310 across so many strategic elements? 680 00:36:35.310 --> 00:36:37.173 It is the power of the community. 681 00:36:39.120 --> 00:36:41.463 The W3C Team is a very small team. 682 00:36:42.420 --> 00:36:45.363 The W3C community is a very large community. 683 00:36:46.440 --> 00:36:48.510 The Team works to leverage the strength 684 00:36:48.510 --> 00:36:52.473 of the broader community by playing a key facilitation role. 685 00:36:54.000 --> 00:36:56.160 But resource allocation within the Team 686 00:36:56.160 --> 00:36:58.683 to provide the right facilitation is critical. 687 00:36:59.640 --> 00:37:02.310 If we assign people on the Team to work on a topic 688 00:37:02.310 --> 00:37:04.680 it is more likely that we bring the parties together 689 00:37:04.680 --> 00:37:06.033 to get the right solution. 690 00:37:07.950 --> 00:37:10.950 Let's get back to the table I briefly showed on slide seven. 691 00:37:11.790 --> 00:37:14.610 Two years ago at TPAC 2020 692 00:37:14.610 --> 00:37:16.050 I shared the graphic from this slide 693 00:37:16.050 --> 00:37:17.583 during my AC presentation. 694 00:37:18.510 --> 00:37:20.520 It demonstrated how W3C 695 00:37:20.520 --> 00:37:24.033 had reassigned Team technical resources over a decade. 696 00:37:25.050 --> 00:37:26.910 Initially there was enormous investment 697 00:37:26.910 --> 00:37:29.133 working on the technology of the core web. 698 00:37:30.360 --> 00:37:32.340 Tim worked closely with the Team 699 00:37:32.340 --> 00:37:34.640 to make sure that we got the technology right. 700 00:37:35.550 --> 00:37:38.280 But as Tim reduced his personal efforts, 701 00:37:38.280 --> 00:37:41.940 as the community and the TAG strengthened their own ability 702 00:37:41.940 --> 00:37:43.590 in technical architecture, 703 00:37:43.590 --> 00:37:46.740 the need for Team resources lay elsewhere. 704 00:37:46.740 --> 00:37:48.270 Team resources were required 705 00:37:48.270 --> 00:37:51.480 to support the aforementioned strategy areas. 706 00:37:51.480 --> 00:37:53.910 So we shifted Team technical resources 707 00:37:53.910 --> 00:37:56.610 to focus on issues of incubation, 708 00:37:56.610 --> 00:37:58.938 building a larger community, to industry needs, 709 00:37:58.938 --> 00:38:00.788 facilitating areas where stakeholders themselves 710 00:38:00.788 --> 00:38:05.670 have fewer technical resources. 711 00:38:05.670 --> 00:38:09.273 The societal needs of accessibility, privacy, and security, 712 00:38:10.170 --> 00:38:13.110 and to various efforts to make us more global, 713 00:38:13.110 --> 00:38:15.720 both specific work on internationalization 714 00:38:15.720 --> 00:38:18.780 as well supporting technical needs from around the globe 715 00:38:18.780 --> 00:38:20.433 such as the MiniApps work. 716 00:38:22.680 --> 00:38:25.620 To be sure, the fact that we have broadly shifted resources 717 00:38:25.620 --> 00:38:27.730 to new areas of strategy is not complete. 718 00:38:29.010 --> 00:38:31.710 At any point in time one never has perfection 719 00:38:31.710 --> 00:38:34.530 in terms of assigning resources. 720 00:38:34.530 --> 00:38:36.510 For example, from my point of view, 721 00:38:36.510 --> 00:38:38.130 while we have greatly improved the assignment 722 00:38:38.130 --> 00:38:42.450 of resources to societal needs, underneath that 723 00:38:42.450 --> 00:38:45.350 we still require more investments in security and privacy. 724 00:38:46.290 --> 00:38:49.590 Those topics have bedeviled the web for some time, 725 00:38:49.590 --> 00:38:52.540 and there is much more work to do to improve the situation. 726 00:38:54.240 --> 00:38:55.683 Please turn to slide 22. slide-22 00:38:59.610 --> 00:39:02.313 Today I provided a retrospective on our strategy. 728 00:39:03.211 --> 00:39:05.970 It is fair to say that we have succeeded in working together 729 00:39:05.970 --> 00:39:08.523 to add value to this community called W3C. 730 00:39:09.750 --> 00:39:12.630 We have made some progress on all of these elements 731 00:39:12.630 --> 00:39:16.080 and in some of them such as overall participation, 732 00:39:16.080 --> 00:39:20.490 membership, industry focus, and outreach to China, 733 00:39:20.490 --> 00:39:22.443 we have made incredible progress. 734 00:39:24.030 --> 00:39:27.003 Each strategic initiative involved choices. 735 00:39:28.260 --> 00:39:30.570 Did we make the right choices? 736 00:39:30.570 --> 00:39:33.570 Should we have emphasized different areas? 737 00:39:33.570 --> 00:39:36.470 Would different choices have made us even more successful? 738 00:39:37.410 --> 00:39:39.570 We'll never know looking backwards, 739 00:39:39.570 --> 00:39:41.580 but the reason to assemble where we have been 740 00:39:41.580 --> 00:39:42.783 is to look forward. 741 00:39:44.070 --> 00:39:45.060 So the key question is 742 00:39:45.060 --> 00:39:47.313 what should our strategy be going forward? 743 00:39:48.210 --> 00:39:50.940 Are the topics we have pursued in the past decade 744 00:39:50.940 --> 00:39:52.473 the right ones for the future? 745 00:39:53.460 --> 00:39:55.590 How will we deal with newer issues 746 00:39:55.590 --> 00:39:59.040 such as sustainability, misinformation, 747 00:39:59.040 --> 00:40:01.680 and how will we have outreach 748 00:40:01.680 --> 00:40:04.683 to a wider set of web stakeholders? 749 00:40:06.720 --> 00:40:09.900 In my April 2022 recorded presentation 750 00:40:09.900 --> 00:40:12.933 I discussed the top 10 reasons that we need a legal entity. 751 00:40:13.830 --> 00:40:15.600 Among the reasons were that a legal entity 752 00:40:15.600 --> 00:40:18.690 has a broadly based board of directors of leading lights 753 00:40:18.690 --> 00:40:20.283 to help guide the organization. 754 00:40:21.360 --> 00:40:23.580 Ultimately that new board of directors 755 00:40:23.580 --> 00:40:26.670 will provide its imprint on the organization. 756 00:40:26.670 --> 00:40:28.410 I look forward to working with the Board 757 00:40:28.410 --> 00:40:30.993 and the W3C community on that topic. 758 00:40:32.520 --> 00:40:34.053 Please turn to slide 23. slide-23 00:40:36.300 --> 00:40:38.163 Thank you for your attention today. 760 00:40:39.030 --> 00:40:41.370 I hope that my illness 761 00:40:41.370 --> 00:40:44.220 did not make my presentation too difficult with my coughing. 762 00:40:44.220 --> 00:40:46.230 I apologize for that. 763 00:40:46.230 --> 00:40:47.790 I am looking forward to your participation 764 00:40:47.790 --> 00:40:50.670 in person or remotely at TPAC. 765 00:40:50.670 --> 00:40:52.203 Thank you and have a good day.