This is a transcript. For the video, see James Rutherford talks about 20 Years of Drupal.
[00:00:00] Michael Meyers: Hello, and welcome to Tag1 Team Talks, the blog and podcast of Tag1 Consulting. We're commemorating the 20th anniversary of Drupal with an interview series, featuring community leaders, talking about their Drupal experiences, how Drupal has impacted their personal and professional lives, what Drupal means to them and their thoughts on the future of the platform and community.
I'm Michael Meyers, the managing director of Tag1, and I'm joined today by James Rutherford, the senior manager of strategic partnerships at Pantheon. Welcome James. Thank you so much for joining me today. Really appreciate it.
[00:00:35] James Rutherford: Uh, thanks, Mike. I'm really, I'm really excited to be here. It's been, um, something I've been looking forward to and, uh, excited on kind of looking back throughout, uh, what we've done in Drupal and, uh, to, to have this conversation,
[00:00:49] Michael Meyers: Definitely. You are a longtime member of the community. Uh, you got involved around 2007, which is around 14 years ago. And if memory serves me correctly, that's right about when Drupal 5 was being released, you are one of the first 200,000 or so people to create an account on drupal.org.
Uh, tell me, how did you first discover drupal?
[00:01:16] James Rutherford: Yeah. So at the time that we first discovered Drupal, I was just a few years out of college working at, uh, Georgia Public Broadcasting, which is a public media company, uh, serves to the state of Georgia. And, um, as a public media company, it actually serves multiple functions.
There's an education function and there's a television function and radio function, all of which serve the needs of the citizens of Georgia. And they actually have a need for a robust, digital presence to help communicate with, um, the citizens and serve their mission. And when I was hired there, they were, uh, just like a lot of organizations at the time, running on a custom home built Java JSP-based CMS.
I had, uh, focused on Java in school and come out and had [00:02:00] started working on a Java JSP based website. So it was a good fit to join that team. But, um, you know, for a lot of the same reasons why, uh, Drupal and the open-source movement have grown, it's tremendously difficult to serve the needs of an organization that big with a homegrown CMS.
So every ask from internal teams was met with like really long timelines to do development. The stack was really fragile and we, um, right around the time that I discovered Drupal embarked on an internal project to evaluate what the next technologies we should rebuild the site in should be. And, um, as, as part of that exercise, we did many projects.
I did my first Rails project. We built like, a little video site in Rails. We evaluated Joomla, did a microsite in Joomla and, uh, spent a lot of time there. And, you know, in hindsight that seems maybe like, Hmm, why would you do that? But at the time, Joomla also had a lot of adoption. Was considered an extensible CMS and seemed to have some, uh, some motion.
And then we did, we did a mini project in Drupal 5. I felt [00:03:00] really strongly that, um, that was going to be the platform of choice and we, uh, rebuilt GPB's website, uh, and Drupal 5. And I mean, it was really, uh, I think a little bit of luck for us because the team was pretty inexperienced. So we were maybe not evaluating it with the level of expertise that, um, would be desired, but at the same time, It was an incredible project because even at that state for Drupal 5 level, what Drupal brought to the table really empowered a small, younger team to deliver a ton of value for Georgia Public Broadcasting.
Um, and we had a ton of false starts who probably talk about this a little bit more, but if you look at my d.o history, um, there was a whole bunch of hilarious, like how does this thing work? We added this module and all of a sudden performance is struggling and I can't figure out why. Um, but what was tremendous about that is that we were able to interact with the community and very quickly solve problems.
Like that's a huge value add that I think a lot of organizations, um, either overlook or are so used to, [00:04:00] they don't get the value of that. Like the empowerment for, you know, it was, uh, basically a less experienced team to be able to meet the needs of a larger organization and do so really effectively from a cost and a quality of the final product.
[00:04:12] Michael Meyers: I don't know if the earliest Drupal forums are still around, but I would be grateful if they were not. I need to look back at some of the questions I asked.
[00:04:26] James Rutherford: I actually really enjoy it. I mean, it's, um, it's funny, but, uh, occasionally I will go back and look at my D.O profile and even like other forums stuff at the time, because it's just amazing, like timestamp of my own career progression and everybody starts, you know, everybody's new at some point.
Um, and it's like my entire working record on Drupal is there, uh, on D.O, which is kind of cool to look back on.
[00:04:51] Michael Meyers: You remember, you know, what do you remember about the project and your earliest experiences with Drupal? You know, I remember when I first installed it, I was like, oh my God, look at all of these SQL queries on a single page.
Like this thing is gonna fall over and die. Like, what am I doing?
Like, why did I use this.
[00:05:13] James Rutherford: I, um, uh, I love that quote or that, that anecdote. Um, for me, it was a reconfiguring of my mindset around best practices and having to, uh, and it took me a little while. I think my team adopted it earlier than I did feeling very comfortable molding the requirements of the project to what Drupal was giving me and what the community was leading with versus, um, enforcing my own idea of what I thought was best and then trying to bend Drupal to my will. And a lot of my early posts and comments are areas where, like, I kind of struggled with that. And when I let go and started to really dive in and understand why Drupal was solving a problem in the way that it did, and then help, you know, the people that I was serving, um, to understand that value that's when [00:06:00] we that's, when you know, my Drupal, uh, proficiency took off and that's when we started to get the most value out of it.
So it took a little while to like, um, and I was a little horrified by like some of the choices around the way modules worked, but like after awhile it clicks, you know.
[00:06:16] Michael Meyers: Do you remember what your first contribution was to the community or code? I know it was a long time ago, but one of the first contributions.
[00:06:24] James Rutherford: Yeah. Um, I think I do, uh, so fast forward from Georgia Public Broadcasting. I, um, I worked there for a couple of years. Did that Drupal 5 site. It was really, really successful. Um, the state of Georgia was awesome. They loved the site. So we were able to go to DrupalCon and immerse our team in Drupal. And that led to me, um, I think at DrupalCon Boston, but then again in San Francisco running into the founders of Mediacurrent, and, um, them knowing that I was from Atlanta and, uh, being interested in getting me to work for them.
So when I went to work for them, one of my first big projects was for a company in Atlanta called Manhattan [00:07:00] associates. And they had a, a fairly complex site that was trying to solve problems around translation in D6 as well as, um, leveraging some aspects of domain access to create microsites and some efficiencies from the, um, theming layer that we built for them.
Which added a ton of complexity at the time in D6. That was, that was tough. So I think my first module was, uh, something called language code alias, uh, which basically tokenize, uh, the, the path prefix code so that we could use it in some of the, uh, workaround modules that we were developing. So very, very niche, but, um, Manhattan Associates and the leadership there really bought into our vision of the fact that, um, they they're going to need this type of functionality for a long time.
And it would be valuable for us to take time, to put it, um, put it on D.O and support it.
[00:07:48] Michael Meyers: I want to talk more about Mediacurrent and your time there, but before we jump into that, there are many ways to contribute to Drupal, code is just one of them. Uh, could you tell us, you know, [00:08:00] what are some of your community contributions that you've made outside of the code base over the years.
[00:08:05] James Rutherford: Yeah. Um, this, we could do 4 hours on this and maybe it's the most important thing to talk about on this type of conversation. Um, I, I look back at all of the time that I've spent working in the Drupal community, which has been the vast majority of my career, all the DrupalCons that I went to. And if I think of my own personal contributions, I'd like to think that, um, you know, uh, frankly, a lot of it has come through mentoring.
Like once I was started down my career path and, um, was really convinced of the value of Drupal and thinking about how to leverage it correctly, thinking about how to communicate to customers or new people in the community, how to be successful in Drupal, whether that's career path, whether that's, um, thought leadership.
That is, um, where I think I spent most of my time making an impact. So that was like taking the time to do presentations at DrupalCon, which I don't, I'm not a public [00:09:00] speaker. I mean, getting ready for a single presentation is hours and hours of agonizing work. And I can't sleep, uh, leading up to that. And I'm sure I didn't have the most memorable presentations, but every person that does that in the Drupal community does put a lot of time and effort into educating our peers.
That's extremely valuable. Um, other areas of impact would be like, participating in birds of a feather sessions, helping to connect thought leaders in the space that, you know, through my own professional circle, I see them working on the same problem and saying like, Hey, you know, we should be working. We should all be working on this together, even if we're we're different organizations.
Um, and then from a more like immediate, uh, contribute back aspect, the team at Mediacurrent at the time that I was there. And through most of the time I was there sort of like that core group that a lot of agencies have that all grow together. Had a very real emphasis on, um, code contribution. And that's not something that just happens at the individual developer level.
Like I want to contribute code. So I'll find time in my spare time to do that. There's a lot of great people that do that [00:10:00] and they drive our community, but not everyone has the time to do that. Or, you know, not everyone has the time to do that over time. You might do that for a couple of years, but then you have kids, your life changes your, you know, you have constraints around your free time.
And so, uh, for our perspective, and this is still how I think Mediacurrent operates today, but I can definitely say the time that I was there, we made a concerted effort. From the first time we talked to a customer to how we manage our internal employees to try to drive time for the team to contribute back.
So that's something like, you know, during the initial, um, Sales process and helping a prospect understand why they should be investing in Drupal or choosing Mediacurrent to uh, leverage Drupal to solve their problems, educating them to how the open source community works, what the benefits are contributing and really helping them understand the long-term impact on their own organization, as well as, um, their, you know, the problems that they can't see in the future, but by contributing and creating a healthy community, [00:11:00] uh, from an open-source perspective.
And then internally that's things like, you know, um, marking time for the team to have during the working day to do that, asking ourselves like on a given project, did we contribute back the things that are most impactful? What did we miss? Um, and then there's also some, like there's some luck and financial aspect to it too.
As agencies move up market and they work with organizations that have larger budgets, like there's more of an opportunity to do that and they should be taking that opportunity.
[00:11:28] Michael Meyers: Mediacurrent is one of the most well-known and, uh, I think influential agencies in the, in the Drupal world, uh, and they've consistently, you know, uh, throughout their history have been one of the top 20 agencies contributing to Drupal.
Um, they were acquired by Code and Theory around 2015, uh, which was really one of the first, you know, major, you know, agency acquisitions and consolidations. Um, how much of this, you know, contribution driven methodology do you think drives the success of Mediacurrent, you know, led to its acquisition, you know, the client base.
[00:12:08] James Rutherford: I mean, I think it's a huge part of Mediacurrent's success. Um, when you develop a culture and a mindset around, um, empowering the team to contribute back, you attract another level of talent. I think that that's very, very important too. And then you attract another level of expertise when, um, a good section of your engineering team or even, you know, part of project management are contributors or thought leaders, which is just another type of contribution in this space.
Um, there's a tremendous impact on, uh, your business, which I think a lot of top agencies see. All things being equal when an organization has evaluating um, a digital agency having that frontline expertise where you have multiple members of the team are shaping the path to the community and the project.
That's a huge value add, I think, um, and our customers thought so as well. And then there's some continuity there. I think, you know, if you look at long time, uh, Mediacurrent members like Damien McKenna, who are also massive community leaders and really care about the project, their like, expertise.
They're focused, their understanding of open source permeates throughout the organization. And they kind of make everyone better around them, um, from the, uh, all aspects, but especially from understanding why it's important to contribute. So I think we were really fortunate to get the right internal team and then have the leadership at Mediacurrent sort of coalesce around the idea that this was really positive and impactful.
And that had like a multi-year effect for, for Mediacurrent as an agency.
[00:13:37] Michael Meyers: Definitely. Um, I think everybody knows that I am, uh, you know, worked very hard to get organizations to contribute, you know, it's, it's near and dear to my heart. And I think, you know, in everyone's mutual best interests. Um, I don't want to put you on the spot here.
Uh, but you know, your role at Pantheon as the manager for strategic partnerships, you have a lot of [00:14:00] influence over agencies. You know, all of us want to work with Pantheon. Everybody wants to have a great relationship with Pantheon. So you're in a really unique position to influence agencies and agency behaviors.
Um, you know, how would you like to see agencies contribute more to Drupal? And is there a way that, you know, you and your role, and Pantheon, um, as an organization can do more to influence, you know, how agencies contribute, and the amount that they contribute to.
[00:14:31] James Rutherford: Yeah, I love, I love that question.
Um, I'll start with, uh, frankly, I don't think that, uh, the team, my team at Pantheon is doing a good enough job of communicating that value out to the agencies. Um, but it's definitely something that we consider to be important. And it's an opportunity as the team and the program there grows. When you think about, um, the role of a Pantheon in a, in a partnership with an agency, our goal, our whole role is to make agencies better, to help them be more successful, to get a good understanding of what they're trying to achieve.
And part of that is almost always education. Like, one of the most challenging parts of running an agency or being part of an agency is that you’re heads down doing the work. And it's very difficult to pop your head up in the air and say, how are, how are things changing in the industry? How are things, how are my peers doing things?
And if you've been successful with your way of execution, you tend to stay in that way of execution. So I, you know, my personal belief is that there's a ton of agencies that could execute. The same way a Mediacurrent does and gain those benefits and just aren't doing it. Not because they don't believe in it, not because they don't have the capabilities to do it.
It's because they haven't been exposed to what the benefits will be. And, you know, sort of have the ability to make that real and communicate that to their own customers so that they can get the buy-in to do that. And I think, you know, Pantheon's role, uh, now and in the future, uh, and increasingly in the future is to help be, um, a thought leader in that space and help educate our [00:16:00] agencies so that they can educate their customers and get that buy-in on, on why it's valuable.
[00:16:06] Michael Meyers: Definitely, um, one area that I, that I, you know, that we're struggling with, is always, how to convince our clients in the contract stage. You know, we're going through a, one of those massive MSAs become an approved vendor, 40 page contract, and it is not open source friendly. And, you know, obviously we're going to work with these big enterprises and we know they can have a big impact, but it takes a tremendous amount of effort and energy upfront to kind of educate them, their legal team.
Um, and it's, you know, it's always a struggle and challenge and I'd imagine an area where, you know, organizations could use a lot of help because it sets that- that foundation.
It's the biggest challenge in our industry. Um, it's not just a challenge from helping them understand the value of open source.
[00:16:52] James Rutherford: It's a tremendous challenge around helping organizations take the correct mindset when approaching their website. We have a legacy from, um, enterprise systems from years and years and years ago where the idea of purchasing software or building an application follows a rigid structure of upfront requirements.
There's a legal need to protect the, the delivery of what gets finished and define, uh, the, the project ahead of time. And even as the industry's evolved, and I think for the most part, we have to - this idea of understanding that agile is important and that we can define an MVP. I think we still have an industry that thinks of success in terms of was the project delivered on time, was the project delivered on budget and is, I'm not as interested in what is the impact of this project a month from now three months from now a year from now? And that's a combination of, it's really hard to measure that impact sometimes, uh, it can be scary to measure that impact sometimes. You spend a significant amount of money rebuilding your website or replatforming, and no one wants to look and see if engagement is up or down, or if they do, you kind of want to massage the numbers [00:18:00] cause you might not be getting the story that you want. And that, that aligns really closely with the why, uh, behind, uh, open source, right?
Like if you're looking at your investment in digital as a single project that then you go away from, and it just sort of runs away. And you're not thinking about total cost of ownership. You're not taking a long view of the, uh, your organization's objectives. And when you start to change that story, when you start to look at like the platform that I'm building as an investment for the next 4 or 5 years, not six months, not this time that I'm here, then you start to look at, um, things like contributing back the code that we're doing, letting the community embrace it, iterate on it and prove it as a tremendously valuable investment.
Right. Um, I think like just crazy, the free expertise that you're getting, looking at your code iterating on it, contributing back, like probably key aspects of your own internal stack. Um, so for organizations that can take that long view, which are rare, I think they get it. Um, and it's easier to communicate and [00:19:00] then maybe more tactically for organizations that don't get that.
I think, um, my experience has always been that. As a, as an agency, as a consultative partner, we have to be okay with meeting them on their terms for the initial project, even if we don't desire it, but then like be working from day one to help them understand the why of the way that we work and have our most successful projects so that you can really knock that first one out of the park and gain the trust from that organization.
That the next thing that we do the next phase for us is going to consider things like contributions from open source or take that longer view where we're, um, you know, comfortable understanding that it's just as important to understand if the website is, is impacting the business or the organization in three months and six months and nine months, um, when you get, uh, teams and organizations to adopt that mindset, then the, the open-source contribution aspect of it is it is a natural component of it.
[00:19:58] Michael Meyers: I think it's a really important point, you know, gaining the trust, building success for your clients, and then having an opportunity to help them be more successful. And I'd love to see more organizations focus on long-term success and total cost of ownership as, as you put it. And, and, and not just on the upfront build costs because their success is really dependent upon making that shift.
Um, speaking of shifts, uh, I wanna, I wanna change gears a minute here. Um, what's been the best part about being part of the Drupal community for you.
[00:20:36] James Rutherford: Oh, um, there's so many like, ways to answer that question. I'll tell you through a couple of like mini-stories, I can't see the Drupal logo without, uh, thinking of my kids, playing with Drupal Drops that I would bring back from DrupalCon where my children know what a Drupal Drop is.
It's like they have a couple of Drupal plushes that are part of their, um, you know, you know, [00:21:00] things that they've kept since childhood. And, um, they confidently say that Daddy does Drupal. It's like, it's, it's pretty amazing to think of the technology in a community that you're part of within the context of your family, but that's absolutely, um, what's happened to me.
And then outside of my own personal family, Uh, my professional career, I would not be where I am today. I would not have got to work with the great people and amazing teams that I've gotten to work on without Drupal. And I think it's because the Drupal that the concept of open source as a project and Drupal is a, you know, obviously an open source project attracts a certain type of person that's collaborative, um, that is here to do great work.
Um, but you know, also is the type of person that you make connections with. That lasts a really long time. I still talk to a team that I worked with at Georgia Public Broadcasting. I'm still close with the team that I worked with at Mediacurrent. I have, um, uh, amazing colleagues at Pantheon that get that same vision.
[00:22:00] So there's like a, a mindset that makes it so that your involvement in Drupal, I think, becomes a bigger part of your life and it's my job. Um, and it also at the same time, it's a very comfortable thing. You don't. It's not a club where I have to, you know, be measured by how many commits I have. Right. If it was you, wouldn't be, you wouldn't be having you on this podcast from my, um, you know, two sandboxes in, uh, in a abandoned project.
Um, and so, uh, sorry, if it's about impact. I mean, it's impacted literally every facet of my life. Um, maybe another important part of it is professional career growth. Like, the Drupal community is such an amazing place for people to come and learn and get better in every single way. Every DrupalCon, every camp is your peers, helping you understand what to focus on, what matters in the industry, what the impact can be, and then coming in, you know, I've never, ever seen a, um, interaction in the Drupal community.
I'm not sure like with thousands of us that happens occasionally, but from my own [00:23:00] personal experience where someone can be brand new, um, and they get guidance and direction. What are the next steps? How to focus, what to think about if they want to make a career here, or someone could have been in the community for 10 years, and we're just sharing anecdotes or even, you know, the latest thing that we're focusing on.
So it's a pretty, pretty impactful, um, mindset that I think the community has and something that I'm really grateful that I got to be and continue to be part of.
[00:23:27] Michael Meyers: The pervasive influence and impact of Drupal on our lives, personal and professional, always amazes me. Um, I remember, you know, vividly those Drupal Drops and the Digital Echidna, you know, those Echidna puck plushies so many things that I've brought back for my nieces and whatnot.
Um, do you have, you know, uh, another, you know, favorite, Drupal memory or experience that stands out in your mind?
[00:23:59] James Rutherford: Yeah. Um, I have a ton of them. Um, but just because of my own personal career and the time and effort that went into the project, I think for me, like the highlight of my Drupal experience is probably, um, launch day for the Weather.com project that Mediacurrent did with Acquia and with, um, the amazing, amazing team at Weather. That was a, I think, a nine month project.
Um, uh, really, at the time advanced, uh, partially decoupled architecture with Drupal 7 multiple teams, I was embedded at Weather working alongside those folks for months, and it was just one of those amazing projects where it's like high stakes, high stress, but everyone pulls together, you know, everyone's rowing in the same direction.
We just had, we had brilliant people working on there at the time. Um, a guy named Jason Smith who was a solutions architect and Mediacurrent now works for Red Hat, just incredibly brilliant guy. Um, the weather.com team was, uh, also just full of [00:25:00] brilliant engineers and people leaders. And, um, we were all sort of in the, like a mission command room when, uh, we turned the dial and all of the traffic started to hit Weather and that's a like a, you know, sort of make or break moment. It's really hard to simulate that level of traffic with the complexity of the system. And, uh, you know, the launch went really well. It's the first time in the history of weather, weather.com that they tried a new CMS and it didn't fall over on the first try. That's a great feeling, you know, you love, um, you love those projects where it's a big win, but more importantly, like to me, uh, it became like lifelong friendships, uh, again, associated with Drupal.
I still talk to a lot of that team at Weather, even though they're onto different things and different projects and maybe even different technologies. So yeah, that was a big one.
[00:25:45] Michael Meyers: That was a standout moment in the history of Drupal. I think, I mean, Weather, yeah, I think it was a first top 10 website. Maybe the only top 10 website to use Drupal.
There were a couple of top one hundreds, but, uh, that was by [00:26:00] far, in a way, you know, the, you know, one of the biggest public launches ever, if not the biggest, uh, and a marquee, you know, for, for Drupal. So, um, we talked a lot about, you know, positive impacts and, and, and your favorite things about Drupal. Uh, I'm curious, you know, we'll get a little controversial here, maybe.
What is your least favorite aspect of Drupal or the Drupal community?
[00:26:26] James Rutherford: Ooh, least favorite aspects? Um,
I, you know, I don't think it's unique to Drupal, but I think it's, um, it's something that I think that we should have more community awareness around and think about how we proactively manage it. And that is, um, so it's definitely not unique to Drupal, but Drupal empowers it in a way that maybe a lot of other software frameworks don't, which is the idea that like, you know, uh, when you have Drupal as a hammer, everything looks like a [00:27:00] nail.
Um, and that's, that's not good. We should be thinking about, uh, what are the organizations we're working for, or our customers or the users that we're serving what their needs are. And we should be okay with, um, understanding when and where Drupal is the right fit. Um, and that's something that I think maybe I know I'm definitely guilty of in the past.
Uh, but as a community, because Drupal is so powerful and so extensible, um, it's something that, uh, maybe we could get better at. And it's really important for the life of the community. You know, every. If we misuse Drupal and we don't create, um, tooling and websites and, uh, projects that drive value for organizations, then the team that invested the money and their, their effort and their time.
And maybe sometimes the mission critical aspects of what they're trying to do. They walk away and say like, Drupal's a terrible technology. That's not, I don't like Drupal. I'm going to try something else. And, um, I think it's important that we [00:28:00] don't set up organizations for like high risk projects when, when or where Drupal might not be the right fit and, or, uh, you know, maybe an extension of that is like Drupal will allow you to architect and over architect your way into a corner, um, in a way that many other technologies don't.
And it's really important that we, as a community, focus on our customers and our users' needs and feel very comfortable pushing back. I could do that. Drupal would allow us to do that, but that doesn't really solve your problem. And also we'd be creating a lot of code debt and, um, I don't think it's intentional, but I think there's a lot of money spent and maybe over-engineering some things in Drupal to get it exactly the way that a stakeholder wanted it versus something that will impact the users and that, uh, you know, it can be negatively impactful on the community and on the perception of Drupal, which is really important for us to consider.
[00:28:53] Michael Meyers: So what do you think the biggest threat to Drupal is right now?
[00:29:00] James Rutherford: Um, I think some of it is the same vein of what I talked about earlier, which is, you know, the people that are working in driving decisions around Drupal, safeguarding, the understanding that it's really important that, um, you know, all things being equal there there's always, um, some projects and teams that just don't understand the technology, uh, that the, the sites that we're building, the projects that we're doing in Drupal are impactful and are thoughtful.
And we're not just building whatever we're being asked to build because the money is there. Um, because ultimately then we're measuring the value of Drupal and its ability to serve the needs of, um, the world, like the potential, uh, uh, users of Drupal, like a project at a time. So that's a threat, I think.
Um, and the second is good stewardship of the open source. Uh, ethos and contributions to the community. Like we have a amazing when you look at the history of Drupal from 4 to 5 to 6, there are a number of names that stand out [00:30:00] where we're really standing on the shoulders of giants that contributed so much time and code and effort into making Drupal better, like one version, one contrib module at a time.
Um, but those people are not inexhaustible resources. So there has to be a pattern of, you know, educating new people into the community, helping them contribute, helping them understand why it's valuable, helping them understand why it's valuable in the context of their career, their customers, and making it really easy to participate.
And I, I mean, I say this and say like, maybe it's something that even I haven't paid as much attention to. Not even, I, that sounds ridiculous, but it's definitely something I haven't paid as much attention to. It's really easy to drift away from, which is why I'm super grateful that you invited me to talk today.
And, you know, organizations like Tag1 are carrying the banner. Um, but it's important. Like if we stagnant as a community, um, then I think the project itself will, will falter.
[00:30:56] Michael Meyers: Definitely. It takes a lot of effort and energy to, to keep contributing. And it's okay for folks, if it waxes and wanes, we have busy lives, you know, I think like you said, we just need to remember the positive benefits that we get out of it, you know, do it because it benefits you not altruistically necessarily, you know, there's a lot of value in it for you.
You're going to grow, you're going to benefit your organization is going to benefit. Um, and yeah, it's okay. If it waxes and wanes, we're, we're all super busy. Um, You know, you talked about all of these amazing people in the community, you know, uh, a community isn't a single person. Uh, and I'm sure that, you know, like you said, standing on the shoulder of giants, there are many people who helped and supported you over the years.
Uh, but if you had to highlight one, you know, maybe two people that had a really big impact on your success and growth, you know, in the community, you know, whether it's personal or professional, uh, who'd you give a shout out to.
[00:31:58] James Rutherford: Ah, it's hard to do that because there are so many people and I'll be leaving. I'm leaving people out, but, um, I guess I'll, I'll pick one. And, uh, uh, because, uh, well, there are many, many, many people, and that could be its own podcast, but I'm definitely one of the most impactful people for me is, um, a colleague of mine from Mediacurrent named Dawn Aly and Dawn, um, came on to the Mediacurrent team, uh, with agency experience and came on to be a senior project manager and joined Mediacurrent around the time that most of the enterprise Drupal agencies in the space were uh, engineering teams first and foremost, you know, companies would come to us and say, we'd like to build a website, we've got some ideas. We would design and architect and build the website and hand back the code, maybe stay close with them to do maintenance, but it was very, very code focused feature function focused.
Um, and that was, I think a lot of it in a lot of ways, that's where the industry was, especially in the [00:33:00] Drupal, um, uh, space and Dawn relentlessly drove a customer first perspective that I think I had already had a seed of internally, but, uh, it, it affected me in a way that has positively impacted my career since then, and had a tremendous amount of impact on Mediacurrent.
And it's in its high growth phase and really helped us, um, to evolve and become a better agency for our customers. Not that we weren't thinking customer first, but it was really. Um, maturation of the customer facing team to be able to feel very comfortable. To say. Well, hold up. Why are we doing this? You know, why are we doing this request?
How is this going to impact you? Does this, does this align with the goals that you set as your organization? And when you have those conversations, um, and you help teams, you help your customers realize their goals and, and, you know, uh, kind of stop being an order taker. That's when you build long-term partnerships.
Absolutely. And that's the [00:34:00] only way to do it. And that, um, that affects everything from, uh, you know, your, for me, my own personal satisfaction, we want not just successful projects, but like really, really happy customers that you build long-term relationships with. It helps me encourage growth as an agency.
Um, you get when you're not going project to project, and you're in long-term partnerships with customers with, uh, forecasted revenues and goals, then you get to take more control over your agency. You get to, uh, hire at the right pace. You get to say like, where else can we extend our capabilities? And not everything has to be based around, like how many hours did we bill, uh, or, you know, if only we can land this next big project we can grow. Uh, so this is this tremendous impact on the customer and on the agency. And Dawn, um, was relentless and helping us all focus on that, built out an amazing digital strategy team. And, um, at the same time, uh, even though she wasn't contributing code to the Drupal project was making us all think through the lens of Drupal of how we're, uh, [00:35:00] better serving our customer's needs.
So she was tremendously impactful.
[00:35:04] Michael Meyers: It's really important to remember that there's so much more than code that makes Drupal, uh, and there are ways for everybody to get involved and to contribute in ways that everybody can learn and benefit. Before we wrap up, um, I want to ask you to pass the torch. You know, you mentioned all these great people that have made contributions to Drupal.
Uh, when you think of someone who's had a lot of influence, a lot of impact on the platform and the community over the years, what's one of the first names that comes to mind. And why do you think I should reach out to them.
[00:35:37] James Rutherford: Um, Dawn doesn't have a commit to her name, but I absolutely think that you should reach out to Dawn.
She, um, actually works at Red Hat now and works with the Drupal team there. Has, you know, spent the same amount of time. I think we have for thereabouts directly focused on Drupal projects and her lens and understanding of how to help teams and non-technical [00:36:00] stakeholder holders realize the value of Drupal and an open source approach.
And then just the broader application of how to think about creating success for the website. Um, and she's a great speaker and, uh, uh, I think she'd be valuable for you to interview. So I would recommend Dawn.
[00:36:18] Michael Meyers: Awesome. Thank you. I will definitely reach out to her. Uh, James really appreciate you joining me today, uh, to all our viewers.
We really appreciate you joining us as well. If you like this talk, please remember to upvote subscribe and share it out. You can check out all our interviews in this series at tag1.com/20 that's two zero. You can also check out our past Tag1 Team Talks and the latest technology topics at tag1.com/talks. As always.
We'd love your feedback and any topic suggestions you can write to us at email@example.com. That's tag the number one.com. Thanks again for tuning in take care, everybody.
[00:36:57] James Rutherford: Thanks Mike..