文字起こし 🔗
**Sanja Grbic:** I wanted to build something where everyone can go and find all of the information they need in one place, so that they can make a decision about which component to use, or whether a new component needs to be created, or who to contact, or where to find more information.
**Jesse Friedman:** What's pretty remarkable about the work that you do is that you never seem to approach it from a perspective of scale. It's always about the user first and making sure that they have a great experience.
**Sanja Grbic:** Things can be improved, but what is the price of that improvement? Is it really changing things for the better, or is it just introducing something new that might be ultimately confusing? It's much less about trying to innovate on the user interface and the patterns that people are familiar with, but giving people a feeling of safety, security, and understanding of what their expectations are going to be when they press a button or flip a toggle.
**Jesse Friedman**: Welcome to Impressive Hosting, a podcast about the role hosting plays in shaping the open web. I'm your host, Jesse Friedman. On this show, we go deeper than uptime and dashboards. We talk about hosting as infrastructure, about ownership, independence, and what it takes to build ethical, high-end WordPress hosting that actually serves creators, businesses, and the internet itself. Before we dive in, head to impressive.host. That's where you can comment on episodes, ask follow-up questions, and help shape future conversations. You'll also find links to follow, like, and subscribe wherever you listen. Today, I'm very happy to say that we have Sanja Grbic, senior product designer at Automattic and a friend, here to join us. We're gonna be talking about AI and product design and a whole bunch of other cool stuff. But Sanja, before we dive in, why don't you tell us where you are, because you have such an awesome view, and give us a little bit of information about yourself.
**Sanja Grbic:** Hi, Jesse. Thank you so much for having me on your podcast. I'm calling in from San Francisco, from Automattic's office here in the Mission. We have a fantastic view of the city and just gorgeous weather. I'm Sanja. I've been a designer for over 10 years now. I've worked on many different products at several companies. My background is in architecture and graphic design. That's how I started. So always kind of at the intersection of technology and art, or applied art and design. I've worked at agencies. I've done a freelance stint as well, and ran my own design studio in Belgrade, Serbia, where I'm from. For a few years, I worked with startups from all over the world. And then I moved into strictly product design. I worked at Blacklane, which is now acquired by Uber. I worked at Issuu, which is a product that was the number-one global PDF-to-magazine platform. And then for the last five years, I've been so lucky to be at Automattic. First of all, because of all of the wonderful people we have in our company, including you, Jesse. We work together a lot, and every time we work together, I am always super excited about what we're gonna come up with.
For the past five years, I've been on the Jetpack design team. Jetpack serves self-hosted customers within many different domains like security, growth, and analytics. More than 80 features are available on Jetpack to our self-hosted customers, but Jetpack is also the underlying technology for all of these types of features on WordPress.com as well. I worked on WP Cloud with you, Jesse, and many other products, including some WooCommerce products. So I have a very rich experience working on products of a different nature, always serving millions of customers, which is super interesting.
**Jesse Friedman:** Yeah, I think that's what's pretty remarkable about the work that you do. You never seem to approach it from a perspective of scale. It's always about the user first and making sure that they have a great experience. Every time I see you working on something, I feel like you are thinking about that individual user, that narrow focus, and what their experience is going to be. So it doesn't matter if it's used by millions or if it's used by 10 people. It's always that first user experience upfront, which is great.
**Sanja Grbic:** Yeah, I appreciate that, Jesse.
**Jesse Friedman:** So you and I embarked on something. It's now been a little more than a month and a half since we finished our RSMs. People listening at home may not know this, but Matt instituted this idea of a Radical Speed Month. Everyone at Automattic who participated paired up with somebody, and then they built something radically fast, radically cool, radically user-centric. We got to choose basically whatever it is that we wanted to work on, and we spent that month shipping something. I think if I'm correct, you worked on two projects, right?
**Sanja Grbic:** Yes, that's correct. The RSM was such a wonderful opportunity for everyone, and everyone I spoke with loved it. I feel like it kind of awakened us. We're all using AI a lot in our daily process now, also thanks to how Automattic is enabling and encouraging us to do that. Using AI and speeding up your work is one thing, but having the opportunity to choose what you wanna work on, to channel that energy you have when you're passionate about an idea, without having to spend it on persuasion, negotiation, or gathering a team, and then just going for it, that was fantastic. I couldn't help but do two projects, not just one, because it was so much fun and the time allowed for it.
So I built something called the Design System Tracker. The users in my mind, first of all, were the designers within our company, myself and my fellow designers in our design organization, when we navigate design system components. Working with design systems is always complicated everywhere. It's an evolving thing that connects and lives inside many products if the company is big enough. So
Load full transcript
I wanted to build something where everyone can go and find all of the information they need in one place, so they can make a decision about which component to use, or whether a new component needs to be created, or who to contact, or where to find more information. That was the first project. I worked in a team of three with Andrew and Melody, and it was a really great collaboration. That finished within about two and a half weeks.
And then for the second one, I paired with Philippe, and that was a fantastic demonstration of speed. Philippe and I have worked together on a team for five years. He is our design lead now, and we know each other very well. We know each other's processes very well, so we were able to align super quickly on what we wanted to build. Within six days, we came up with the idea, did the research, and built together a chat app that connects merchants with customers on the site. It was an iOS app paired with a plugin. It was a great proof of concept that we're going to work further on to get it out for our customers.
**Jesse Friedman:** That's really cool. For this podcast, the people at home are working in the hosting industry, agencies, and other people building websites. Let's double back real quick to the design systems project that you worked on. I think that's really interesting, especially for companies trying to work within an open-source system. From the perspective of people building within WordPress, they all have an understanding of how WordPress functions and what they expect in terms of design. But there's a lot for a hosting company to incorporate in terms of design. There's their panel UI, the way they build plugins specifically for WordPress, and everything from emails to the front-end marketing website and all that stuff. So I'm curious, what advice would you give to a hosting company building and launching WordPress hosting solutions around the idea of incorporating design systems? What could they expect to benefit from? What should they know?
**Sanja Grbic:** Well, regarding the WordPress design system, the open-source design system that we're actively contributing to, it's complicated. The nature of it is that it serves complicated workflows. So in itself, it's a lot of work to make sure that every component published out there for everyone to use has accessibility in place, is compatible across all versions, and in terms of UX, can serve many use cases and be flexible enough for everyone to use.
So the advice I would give to hosting companies is, if you're building an interface and you're able to use the open-source system, definitely check it out first. See what's available. And as of late, the Design System Tracker is also publicly available, so they can have a look at what's there. At the same time, either audit what they already have if they're redesigning, or have some sort of plan of what they need to build, and use as much of the simpler components as they can, like buttons and typography styles and things like that, smaller items. Then carefully consider the more complex components that might fit their use case. If something doesn't entirely fit their use case, or they have an idea for something that could work not just for them but for other people, please share that in the repository. Share thoughts, open issues, contribute to it so that we can all have those conversations together and make the design system better for everyone.
**Jesse Friedman:** Yeah. I think one thing I've run into a lot when I talk to hosting companies is that they don't necessarily know exactly where they want to put interface elements that the user interacts with, both in the panel and in the WP admin. I talk to hosting companies a lot about this. Sometimes they say they really want to pull everything into their panel, where you can do all your hosting configurations, set up SFTP, create email, bolt on features, incorporate things from their marketplace. And then they get feedback from their users saying, "I like to do everything inside the WP admin." So then you see this shift where they say, "Okay, let's put everything into a plugin." They build a must-use plugin, so you're inside the WordPress WP admin, and now all this hosting functionality exists there.
The thing I keep going back to is that you're never going to make every customer happy with one single solution. What I think makes a lot of sense, and something we incorporated into the way we built products for Jetpack, is this idea of being where the user is instead of worrying about funneling them into a specific place. We just make sure that they have a great experience wherever that is. That could be in the panel, it could be in WP admin, it could be in the app. And I've noticed more and more functionality is being brought into email as well, from two-factor logins to updating settings or confirming something. There's always a little button inside your email that enables some level of functionality.
I'm thinking a design system like this would actually be helpful in forming familiar patterns for users so that no matter where they are, if they're in the panel UI or the WP admin, it feels and looks the same. They aren't getting confused about how to set something up. I would imagine it probably reduces the product designer's workload in replicating things across surfaces, even if it requires more testing. But a design library or systems library like that feels like it would be helpful in solving that problem for the user.
**Sanja Grbic:** Definitely for the users it's way better, because in more cases than not, users know what to expect. If the patterns are familiar, they can get used to them, and they become kind of a universal experience. That's what's really great about it. In terms of spending less time on design, that is also true of course. Design systems evolve continuously, so you can never say it's ready. It never really fits entirely the use case you're working on. So there's always some work
happening to make sure you use what's available, but also keep the experience at a high standard. But systems thinking is always helpful, especially within the WordPress ecosystem, which can be very complex and is serving very complex workflows quite often. Relying on a system like that makes the most sense for sure.
**Jesse Friedman:** Yeah. Very cool. So the other thing I've noticed with hosting companies is that they're always looking at each other to see what's working. And I think that's good. Competition drives diversity in hosting, which is valuable because it makes sure we're always providing a better, more unique WordPress experience. But at the same time, from what I see in talking to hosting companies and executives, they often feel like every other hosting company has it figured out, and that they're wading through tough waters trying to sort things out themselves.
I find it funny because Automattic is a company where we feel very confident in experimenting. We run a lot of experiments, and somebody might stumble upon an experiment and think, "They're making a big paradigm shift. We need to get on board and do that too." And then all of a sudden our experiment's gone because it didn't work, and it leaves people guessing.
So I'm curious. When you think about product design across a large ecosystem like WordPress, where the WP admin has been a familiar, stable ground for users for a long time, and hosting companies are building panel UIs and making decisions around how you interact with their product, there's a lot that's exactly the same no matter who you go to. Setting up FTP credentials, adding a domain, launching a new WordPress website, these are all the same types of interactions. How do you feel a hosting company should be differentiating themselves on product design? Should they be as innovative as possible? Or is it safer and better for everybody to incorporate design patterns the entire industry uses, so everyone feels a little more familiar? How do you balance that with a large ecosystem like this?
**Sanja Grbic:** That's a really good question. My instinct tells me I would go the conservative route here. I would make sure that some basic patterns are in there and always the same. When we talk about the atoms of the design system, a toggle switch is a toggle switch, and it should work the same everywhere. There are some variations you can try, but usually when someone tries to innovate there, sometimes it doesn't serve its purpose. Like, I'm not sure if this toggle is on or off. Have you ever had that?
**Jesse Friedman:** Yeah. Oh, yeah. Yep.
**Sanja Grbic:** Right? And that's the essence of that component. It has to switch something on or off, and you should be aware of what your action just provoked. It needs to be obvious. You shouldn't have to think about it. So I think basic patterns have to work in a proven way, and then whatever innovation is happening, I feel like it should happen in terms of new features, allowing people to use new technologies, solving problems for them that they've actually expressed, not just anticipated or made up. I kind of like how with Jetpack we experimented with integrating AI features when it was just the beginning of this whole thing that became pretty big. We incorporated it into the WP admin, into the editor, into Gutenberg, by using patterns that already exist and that people know how to use. But the tools were still there. We didn't have to come up with new ways of designing interfaces in order to be innovative.
**Jesse Friedman:** Yeah. No, I think that's right. Humans in general are very familiar with patterns, and we incorporate them into our mindset in knowing how something is going to work. It's funny, because when I was growing up, my grandmother had a light switch in her dining room that, for whatever reason, was installed upside down. So every time you'd flip the switch, it would be the exact opposite of your expectation. But the thing is, you would know exactly what happened in that exact moment, regardless of your expectations.
**Sanja Grbic:** Unless the power is out.
**Jesse Friedman:** Well, yeah, right. When something goes down, everything goes out the window anyway. But what you talked about there is that it's much less about trying to innovate on the user interface and the patterns that people are familiar with, and more about giving people a feeling of safety, security, and understanding of what their expectations are going to be when they press a button or flip a toggle. The innovation can come from a different place, from providing a better user experience, better technology, giving people advanced access to new things. But the pattern libraries that allow users to interact with those tools should be familiar, with a clear understanding of how things are going to work.
Now, if we incorporate some new paradigm, like when responsive web design came out, everybody had strong opinions about the hamburger menu. Remember that?
**Sanja Grbic:** Yeah, yeah. So...
**Jesse Friedman:** Everyone felt like those three lines don't mean anything to people. But the reality is, like the light switch, the original light switch was a turn dial. It was on or off. It wasn't up or down. There was no inherent brain pattern saying up means on and down means off. That wasn't something that existed. It had to be ingrained. So when you grow up with something and you've been flipping the same light switch for as many years as we've been on this planet, you develop an expectation of how that's going to work. And I think that's the way we can think about building design systems for tools that everybody has so much familiarity with.
It makes so much more sense to design WordPress interfaces or hosting interfaces in a way that is familiar for everyone, no matter what hosting company they're with. The way you differentiate yourself is in the partnerships you create, the technology you add on, the things you bolt on. I don't think it makes
any sense to diverge from the pattern so much that you create an uncomfortable feeling when someone either arrives at or leaves your hosting company. I think that would be to the detriment of the whole system. But that's kind of what I'm interpreting from this conversation.
**Sanja Grbic:** Yes. Yeah. And I think that's a good summary. But also what you pointed out, which is actually very important, there is still room for innovation. You can do it, but it can't be just for the sake of changing things. It has to have a meaning. Someone once said, "This light switch, why am I turning this when I can..." you know, whatever. Things can be improved, but what is the price of that improvement? Is it really changing things for the better, or is it just introducing something new that might be ultimately confusing for people who switch on their light every day? If the light switch is different every time they walk into a room, that's not going to be a great experience.
**Jesse Friedman:** Yeah. Right. Exactly. It's interesting because with WP Cloud, we're 100% API-based. So when a new partner, a new hosting company, or a registrar comes on and starts using WP Cloud, they have a choice. They can incorporate it into their existing panel. But if they don't have one, they can build a new panel. Actually, with the use of AI, we've seen a couple of hosting companies develop panels. We have a partner that's going to be going live in a few weeks who had an existing panel, and they said, "We're shifting everything to WP Cloud. This feels like the right time to recreate our entire panel from the ground up and introduce something new." They were able to use AI and a couple of developers and designers to create a whole new panel UI in just a matter of days, which was remarkable.
We also have partners like Panel Alpha and RTCamp that offer white-label panels. A conversation I typically have with hosting companies is around, "Why would we want to use a white-label panel? It's going to look the same for everybody and it's not going to differentiate us." And I say, "Well, number one, you have your brand at the top. Your brand will always be first." I think that's what people are going to become more familiar with.
I think with white-label panels and other white-label software, you can kinda feel like you're in technology that you've seen before or are super familiar with. But there's also a simple argument here, which is that people are familiar with the idea of software having similar looks and feels. Samsung, Motorola, and Google are not differentiating themselves on their Android UI. They might tweak the colors and the designs, but for the most part you can bounce around between Android phones pretty easily. And in the hosting industry, cPanel and Plesk have been around long enough that a lot of people know them. Yes, hosting companies have modified things, slimmed things down, removed or added functionality. But for the most part, cPanel was cPanel, and you would know if you were in it.
**Sanja Grbic:** Justified. Yeah, and needed.
**Jesse Friedman:** But for the most part, I think it actually works really well for our partners, and for WP Cloud in particular, to say we feel very confident that you're not going to be differentiating yourself on a few pixels around an icon or whether something is designed one way or another. It's more about the user experience. It's more about the emotion the customer feels. Do they feel empowered? Do they feel like they're getting things done? It's less about the little intricacies of a design. I think that actually lends to a better solution for hosting companies, to focus on areas where they can feel comfortable leveraging these design systems and patterns, and then focus on other things to make their user experience better.
**Sanja Grbic:** Absolutely. The system is the base that you can rely on at all times, and then on top of that, you have the time to innovate where it'll actually make the biggest impact.
**Jesse Friedman:** For sure. Very cool. So that was your first RSM project, the design systems setup, and then you started working on a second one. I don't know if we have time to dive into it yet, but real quick before we have to break for this episode, what was your biggest learning from RSM in terms of being a product designer? Correct me if I'm wrong, but you haven't been a developer in the past, right? You weren't writing code before. But now with the use of AI, you're actually getting into a place where you're taking not just the work of your product design, but actually getting into the implementation of it as well, right?
**Sanja Grbic:** Yes.
**Jesse Friedman:** Tell us a little bit about how that went, what you learned, or how it feels. Does it feel weird? Does it feel cool, empowering?
**Sanja Grbic:** It feels cool and empowering. Being a developer, I always, for my entire career, worked in technology, so I always had to understand it. I took courses in HTML and CSS a hundred years ago, you know? When I build my site, I can figure out the basics. But my idea was never to be an engineer. I think code is a tool just as much as Figma is a tool, or AI is a tool, to visualize something, to represent whatever it is you're working on. My job is to take something and make it better. I have exact goals for how it needs to be improved. All of that is in my head. I'm using a tool to visualize that, communicate it, and show how it's going to work. Whether I sketch it on a piece of paper and hand it over to someone to do a detailed design, or hand it to a developer to code it, or whether I go through the entire process myself, my biggest contribution is in the thinking, and in the part where I change something to a better state to better serve the customer, to better serve the business, to optimize for whatever goal we have.
I wouldn't have minded having code in my toolbox in the past. But it's just too much work to do everything. Now with AI, I have this incredibly powerful tool in my toolbox, and I can choose, depending on the situation and the project, which tool I want to use. I might still just write a blog post and describe how something can be better. Or I can go through the entire process and even deliver it to a certain extent. Engineers have knowledge that I don't have, and of course complex features are still not something that AI can entirely handle well.
**Jesse Friedman:** I think that's really interesting though. I definitely want to press on that. I think we'll come back in the next episode and talk more about it. But it's really interesting the world we're living in right now, where you've been focusing your whole career on these ideas and trying to make the user experience better, and you're probably feeling a little limited by who you could pair up with, or who you could hand things to, or who you could ask to actually build the thing that's in your head. But now, maybe you don't have to wait anymore.
**Sanja Grbic:** That's true. If I choose to, yeah. Less friction, less negotiation, less trying to convince and figure things out. Sometimes it's super easy. Sometimes it's just not working. And it's good to know that I can push it a little further, and then...
**Jesse Friedman:** Even if it's just a prototype, you can show people how it would actually work in the real world. Yeah, very cool. All right, we're gonna...
**Sanja Grbic:** Yeah. In the next episode, I want to share a little bit more about my insights around how organizations might need to adapt and work together a little differently from now on.
**Jesse Friedman:** I love that. Yeah, for sure. All right, great. Well, thank you Sanja for being here, and we'll be back with another episode soon.
**Sanja Grbic:** Thank you, Jesse.
**Jesse Friedman:** Thanks for joining us on another episode of Impressive Hosting, where we uncover the core tenets of great WordPress hosting. Do you have a follow-up question for today's guest, a thought or comment on anything we talked about, a future guest suggestion, or a hosting horror story? What do you think makes great WordPress hosting? All your comments shape the show. Drop them on impressive.host. We also appreciate you following us on social media and subscribing to the podcast on your favorite platform. Finally, do check out our list of open-source projects that need support at impressive.host. Whether it's code, community, or cash, you can make a difference. See you next time.