 All right, everyone, here we are with Meet the Moment delivering results through webops. I believe that my screen might be showing mostly me. There we go. Thank you very much. With that, let's go ahead and get started. So, hi, I'm Drew Gorton. I'm the director of developer relations at Pantheon and I've been with Pantheon for about five years now, actually. Before that, I was an agency owner and a developer myself. And I was a Pantheon customer too along the way. I've been doing Drupally things for a long time. You can find me on Drupal.org as D Gorton as well as elsewhere on the internet. And when I'm not doing Drupally kinds of things, I enjoy languages and travel, although certainly a lot less travel than I used to do. And however, offsetting that a lot more cooking recently, just because there are a lot of adults in my family, two teenagers, two adults. And I also am into stereotypically nerdy kinds of things like science fiction and fantasy and whatnot. If any of you have dropped a reference to say Lord of the Rings into the chat, I will absolutely spot that enjoy that and appreciate it. I want to start with learning a little bit about each of you as well. And in order to do so, I'm actually just going to fire off a couple of polls here. And so if everyone could just take a moment to let me know a little bit more about that. So you should have a poll on your screen right now. And here we go. I think this will hopefully I can do two at a time. I actually didn't test that beforehand. But hopefully if everyone can just take a moment and let me know a little bit about yourselves, that would be super helpful for me. While you're doing that, I'm going to go ahead and talk a little bit about why. Why am I giving this talk and related? Why is my employer Pantheon willing to give me working time to produce it? It's because it really connects with our organization's mission, right? There's a lot to unpack here Pantheon's mission is to make the open web a first class platform that delivers results. And that's super relevant to what we're, you know, what I want to talk about today. I won't unpack all of this or really talk about Pantheon. Additionally, I will actually just mention we do have a booth here in the virtual exhibit. If any of you do have questions about Pantheon and how we might be able to help you achieve results, we'd be delighted to have those kinds of conversations. I'll also be able, I'll be there at the booth afterwards. If anyone has questions that we're not able to get to get to in the 20 minutes that we have here right now. So that open web part is something I'd like to dig into. In my opinion, as well as Pantheon's the open web is a global public good. The problems that we face as humanity are increasingly not ones that stop at borders. They can be solved by any single organization or company and non governmental organization. And if we are going to address these problems, we will need tools that allow us to communicate in ways that aren't controlled by any single organization or country. We need the open web. And that being said, the open web is under continual threat. And there are, for example, countries that don't believe in free and open access to information. They want a more controlled approach undermines their power structures. There are device makers who, if they could, if they had the ability to do so would absolutely set up their own networks of sort of excluded and walled gardens. And there are organizations that are, you know, born of the web, if you will, but would rather replace it with their own version and put all of the content and community inside their own walled garden and then sell you ads and sell your data to anybody who wants to use it. And these are threats to us as threats to the open web. And websites themselves have changed a lot, you know, once upon a time it was, you know, hey, we just, you know, we've got a website, click that checkbox. And you have, you know, you've served like mission accomplished move on to the next thing. Today, websites have jobs, right? So increasingly they have a job to do and once you find that purpose for your website, it can be really, you know, liberating an empowering moment. So that's serving constituents and forming the public raising donations, building a movement, whatever it may be selling, you know, selling tickets, or a whole host of other things. And we see this happening rapidly today. I don't know if anyone else has seen this particular graphic, but this is something that the Bank of America put together early in the days of COVID a month or two ago. And noted that like every week was more than the previous years worth of digital transformation, the amount of traffic and the shift that is happening. You know, sometimes industry kind of inflection points kind of sneak up on us. But this one we are all living through together and it is very clear what is happening. We see this in our own data as well. We see like of our largest enterprise customers, we see about 20% of them see they themselves have seen about a 20% increase in their traffic and what's happening on their websites. And a smaller fraction of them have seen in like over 50% of increase in the amount of traffic and activity happening on their sites. And increasingly the world needs websites in order to communicate to achieve their missions and serve constituents and more. And so, right now, really feels like a moment where the future is happening fast, and there's urgency in this work. You know, are we ready to meet the moment are we as a community are we as a technology as we as practitioners of the open web, ready for this and are we going to are we going to rise to the challenge. So these are things that that pantheon has been asking to think about for a while, frankly, and in your response to all the things that 2020 brought is like really highlighted for this for us. So what we've decided to do actually different like sort of obvious question was, let's ask like who's we, you know, there are a lot of people using pantheon we know who they are that we know who's driving results. Let's talk to them, let's learn what they're doing. And let's see if we can cross pollinate some good ideas and help us all succeed. And that's what I want to share with you. One of the things that we observed and learned when talking with with with our customers and the people who are doing well and really driving results with their websites is that their conception of team is larger and more cross functional than say some teams might be. In particular, the teams that include developers and designers and content authors and the stakeholders who are evaluating the work and the marketers who own the budget for the work and the, the cis admins, like if all of those people are thinking about themselves together on a team. Those teams are more effective. And this is probably not controversial or surprising. Humans are a tribal species. We do think of ourselves as members of teams and we sort of line ourselves to team goals and, you know, a corollary to that is if we think our team, like the goals of other teams are less important to us. And so, we see that teams for example that are broken along disciplines, like we're the development team, we're the front end development team, we're the back end development team. We're the designers. We're the content people were like, if, if those are your teams you are less effective than a team that says, no, we're a team driving for results. And we include people from all of these disciplines and we collaborate together. It is, it's like, it's almost like a psychological trick in some ways by just shaping your teams differently. Increasingly we see these teams self describing as web ops teams and we're very supportive of that makes a lot of sense to us as well I think, you know, naming things as hard and there's there's a name to be had here. And so again these teams are made of a mix of disciplines who are working together with focused goals and achievable and milestones and other things like that along the way. So that's how the team is made up. But as we were talking with all of these folks who saw being successful, we had lots of conversations with lots of organizations and we started listening, you know, sort of going through that and listening for what was working what wasn't what were the common words or the common things. And this mental model started to emerge and this is our attempt to sort of capture and communicate what we see high functioning web ops teams doing. If you will they they the pyramid on the left here is people tend to sort of like clump these things into several different layers of focus or value if you will. The credibility layer this is about is your server running is it perform is it secure, like those kinds of things there's a class of activity that that happens around that. And there's, you know, another class of activity which is much more about like how quickly your team is able to do work get work through the pipeline and and move on to the next task and that's much more about productivity. And then teams that are able to like handle credibility and productivity kinds of things as quickly and as efficiently as possible, have way more opportunity to spend time on the things that drive an impact for the organization. And the things that people are actually doing at this across these layers of like the verbs the actions they're doing is to maintain or optimize collaborate automate measure and iterate. These are the things the actions of these teams that these successful teams are bringing to their organizations to help drive results for them and their constituents. Thank you everyone so for for filling out the polls by the way, I'll be asking questions again a little bit I think if I click these buttons this will drop off the screen. I hope I click the right buttons. Thank you. So I want to talk about each of these things. And in a little bit more detail and each of these different activities these different actions and on the screen there's a quote from people who happen to be pantheon customers who are sort of talking about these things. I don't believe them to be, you know, these these things to be, you know, exclusively the behaviors of customers who use pantheon. I believe that pantheon can help achieve some of these things and certainly something we could talk about later but whether or not you're using pantheon. I think, you know, some of these things will will resonate. I'm not going to read quotes to you you can do that far faster than I can do that. That's the way humans work. But one of the things that every successful team is doing at some level, they are maintaining the integrity of their site and the security of it, the scalability of it, and all of those kinds of things. Successful teams spend as little time as possible which more of what this court is about, but you absolutely have to do this class of work if you are going to be a successful team. You also need to be performant. And so the like performance is user experience right and if your site is slow you will have less of an opportunity to actually accomplish the goals of your site. Just yesterday as I was preparing for this talk, one of my colleagues shared a report with me about a client who is coming to Pantheon and you know interested in our services and such and doing some load testing as much. They had a site which had a 34 second time to interactive on some of their most important pages 34 seconds before a human being can actually like scroll or click a button or you know fill out a form or do anything like that. If you have that problem that is a real problem and you must address it so again like these high performing teams are focusing on optimizations around performance and take performance very seriously. Again hopefully it doesn't take all of you, you know all of the hours in the day to do so but if you have a problem like 34 seconds before time to, you know, interactive, you absolutely need to address it. Once you've got that once you once you get your site is performing a secure it is, you know, online, you know, not failing under load etc all those kinds of things. Then we see the successful teams kind of move up to that productivity layer and and again we see a lot of automation of repetitive and error prone tasks. And this is a this is a place that, you know, in my own experience my history of starting as a developer and moving on different roles throughout time. I remember a point in time before I used version control before the team I was on used version control and I remember that one of the things that we would have conversations about was, like, how should we do version control, you know, we probably should people tell us we should have something to learn and is it going to be worth it etc etc. At some point we did it. And there was no there was no turning back that was it was clear and obvious like whoa we should have done this sooner. Similarly, we see teams that are automating tasks adding automated testing automated deployments doing, you know, adding automation to their workflows. Similarly, it's a it's a thing to learn is a thing to do is it going to be worth it. It's a game changer it really is transformative and it really allows teams to move faster, have higher reliability the same things happen in the same order because robots are doing them. You know that the things are happening. It's, it's absolutely a critical piece of these high performing teams. Another thing that we see in that productivity layer is about collaboration like again these teams are absolutely able to effectively collaborate and communicate across disciplines and some of that's you know about humans just working with humans. But some of it's about the tools that they use to make sure that they can share their work that there's a predictability for like how does work go live or how do we know what are our approval steps what are our processes do you know like, we're doing that every time we have a predictable way of working together that is well documented well laid out. And it helps us be efficient and effective. Once you've got all that flowing. We see these really high productivity, you know, high value teams producing lots of results, focusing on this impact layer and, and there's the two really closely related things activities that we see these teams doing. And, and one of them is measurement and there's a clarity around what is the purpose for your website what are the important things that happen on this website and ability to sort of measure when those things happen. And closely related to that, you know notice if something goes up or down like it goes down we should pay attention to that it goes up we should pay attention to that do more of the things that help to go up. What happens through iteration, we see again like teams who are able to deploy rapidly who are able to say like, we're here to serve constituents for example we serve 50 this week we serve 500 this week we serve 10 yesterday whatever the numbers are. If we did more, it would be better, we would, we would be providing more value for our agency for our organization, and then trying different experiments and seeing if they can help improve those numbers and doing it, you know, try something measure it, if it works, do more of it, if it doesn't. If you do that, roll back to the early state but the more often you're able to sort of run through these agile kind of quick tempo changes the more often the better the results will be for your organization. So that's, that's what I wanted to share with you today. This is a mental model I hope it is something that is helpful for all of you as you think about your work and how you can organize it and the kinds of tasks that you are are doing. One of the things I'd like to just share sort of in conclusion is, is the, if we can all focus on impact and the impact that we want, you know, for our websites and what the thing is that we are all collectively as a team, we should be focused on. The better off we will all be in making our organizations more effective, making the open web more effective, you know, bettering our own careers if you need to be sort of like selfishly interested, which also helpful. And then people do want results, not websites. I want to thank you all for attending we still have a couple of minutes here and I would love to answer questions. If anybody has some, I'm going to go ahead actually in the spirit of measurement if you don't mind. I'd love to know if I made a difference. I'm actually going to go ahead and start another couple of polls, which at your leisure, feel free to answer and I'd love to know. Again, in that spirit of measurement. Did I help explain anything. I hope I did. So, while that's happening, if anybody has questions, I will happily answer now, or you can come also to the pantheon booth because I know that we've only got a minute and 30 seconds after this and dive into any of this in more depth. I see a presenter chat. All right, that's not right. Q&A. Oh, my live Q&A is closed. I hope I didn't do that. Has questions. I'm not sure what button I need to click in order to make that better. I apologize. Well, maybe the last thing I will just say is if you, if you want to engage with me on social or you know, or over email and such, I would be happy to do so. You can find me drew at pantheon.io or D Gordon again on most social things. And again, if any of you do want to chat, I'm so sorry that I maybe screwed this up and didn't actually give you any of you the opportunity to give feedback or ask questions. But if you would like to chat further, I'd love to do so. I'd love to get to know you. Feel free to drop by the pantheon booth afterwards and we'll chat with you there. And if I don't see you, I hope you have all of you a great conference and a great day and learn lots of things and go forth and be successful. So, thanks everyone.