Meeting Modern User Expectations in WordPress

Meeting Modern User Expectations in WordPress 🔗 **Source:** [Meeting Modern User Expectations in WordPress](https://www.youtube.com/watch?v=h91da79cDDk) > [!note]+ Document Notes > tags: [wordpress, user-experience, product-management] > author: WP Product Talk > source: YouTube > reference: https://www.youtube.com/watch?v=h91da79cDDk > date created: 2024-12-19 10:30 > > # 🏷️ Title: Meeting Modern User Expectations in WordPress >  ## 🧰 Action Inbox - [H1] Implement progressive complexity in configurations — simplify default settings, allow granular customization #product-design - [H2] Develop AI-powered support that handles routine tasks while escalating complex issues to humans #customer-support - [H3] Create unified experiences between hosting environments and plugins through partnerships #collaboration ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [WP Product Talk](https://www.youtube.com/channel/WPProductTalk) - [Freemius Growth Platform](https://freemius.com) ## 📝 Summary - WordPress product owners are facing rapidly evolving user expectations that demand simpler, more intuitive experiences - Users expect SaaS-level uptime and reliability even from distributed WordPress solutions - AI is accelerating both user expectations and the ability to meet them through better prototyping and support - The solution requires closer collaboration between hosting providers, plugin developers, and theme creators - Progressive complexity and human-centered support remain critical for WordPress success ## 📖 Main Content The WordPress ecosystem is experiencing a fundamental shift in user expectations, driven largely by AI capabilities and competing platforms like Shopify, Wix, and Squarespace that offer seamless, always-available experiences. Users no longer want to navigate multiple screens to accomplish tasks or learn complex configuration systems. Key challenges include the "sassification" of user expectations - people expect WordPress sites to never go down, just like SaaS platforms. However, the distributed nature of WordPress (plugins, themes, hosting) creates complexity that standalone platforms don't face. AI is both accelerating the problem and providing solutions. It enables rapid prototyping and better support experiences, but also raises the bar for what users consider acceptable. The panel suggests that AI should handle routine support tasks while humans focus on complex problem-solving and relationship building. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/h91da79cDDk?t=0) — Introduction and Problem Definition - Key idea: WordPress user experience has traditionally involved complex form-filling and multi-screen workflows - Evidence: "So much of the product experience that people experience is filling out a bunch of settings" #### ⏱️ [05:30](https://youtu.be/h91da79cDDk?t=330) — The Acceleration Effect of AI - Key idea: AI is rapidly increasing user expectations while providing tools to meet them - Evidence: "AI alone is accelerating everything so fast. It gives us the tooling to be able to meet expectations quicker" #### ⏱️ [08:45](https://youtu.be/h91da79cDDk?t=525) — The Sassification of Expectations - Key idea: Users expect SaaS-level reliability from WordPress installations - Evidence: "When you pay for a SaaS like it never goes down. Can you imagine if a SaaS was as down as a WordPress site" #### ⏱️ [12:20](https://youtu.be/h91da79cDDk?t=740) — The Vercel Experience Standard - Key idea: Developers want simple deployment without infrastructure complexity - Evidence: "You connect your GitHub repo, it deploys it and that's it. You're done" #### ⏱️ [18:30](https://youtu.be/h91da79cDDk?t=1110) — Progressive Complexity Approach - Key idea: Start with simple configurations that work for everyone, then allow drilling down - Evidence: "I use a lot of what I call like progressive complexity in configuration" #### ⏱️ [22:15](https://youtu.be/h91da79cDDk?t=1335) — Visual and Intuitive Interfaces - Key idea: Users expect interfaces that explain themselves without requiring multiple screens - Evidence: "Whatever they're going to get done is going to be done in a very intuitive and visual-oriented way" #### ⏱️ [28:40](https://youtu.be/h91da79cDDk?t=1720) — AI-Powered Rapid Prototyping - Key idea: AI enables quick iteration on UX designs and user testing - Evidence: "Within a day or maybe two, you can have five, six, seven working prototypes and flows" #### ⏱️ [35:20](https://youtu.be/h91da79cDDk?t=2120) — Hybrid AI and Human Support - Key idea: AI should handle routine tasks while humans provide high-level problem solving - Evidence: "If you really need somebody to kind of counsel you through your hosting problem we have some folks available" #### ⏱️ [42:10](https://youtu.be/h91da79cDDk?t=2530) — The Chatbot Proliferation Problem - Key idea: Multiple plugin chatbots could create admin interface chaos - Evidence: "What if every plugin has a freaking chatbot in the admin?" #### ⏱️ [48:55](https://youtu.be/h91da79cDDk?t=2935) — The Worm Farmer Story - Key idea: Real users just want their sites to work without technical complexity - Evidence: "I'm just a simple worm farmer. Like, I should sell my worms and I can't" #### ⏱️ [52:30](https://youtu.be/h91da79cDDk?t=3150) — Managed WordPress Reality Gap - Key idea: Managed WordPress hosting often doesn't deliver on its promises - Evidence: "Managed WordPress has just become basically like more or less updating your plugins" #### ⏱️ [58:45](https://youtu.be/h91da79cDDk?t=3525) — Integration with Page Builders - Key idea: WordPress products must integrate better with visual builders like Elementor - Evidence: "We have to better integrate with Elementor and page builders" ## 📚 References - [Freemius Growth Platform](https://freemius.com/) - [Emir Serverless Technology](https://emirapp.com) - [Builtfast Hosting](https://builtfast.com) - [Gravity Kit](https://gravitykit.com) ## 🗣️ Paraphrase - WordPress users now expect the same level of simplicity and reliability they get from SaaS platforms, but the distributed nature of WordPress makes this challenging to deliver - AI is both raising user expectations and providing tools to meet them through rapid prototyping, better support, and automated problem-solving - The solution requires unprecedented collaboration between hosting providers, plugin developers, and theme creators to provide unified experiences ## 📰 Newsletter **WordPress Product Owners: Time to Level Up Your User Experience** The bar for WordPress user experiences has never been higher. Users expect SaaS-level reliability and simplicity, but our distributed ecosystem makes this challenging. **Key takeaways from industry experts:** - Implement progressive complexity: start simple, allow advanced customization - Use AI for routine support while keeping humans for complex problem-solving - Collaborate across the ecosystem - hosts, plugins, and themes must work together The "worm farmer selling $100k monthly" shouldn't have to worry about server infrastructure. Neither should your users. **Resources:** [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Develop unified admin chatbot interface to prevent plugin proliferation - Community: Create collaboration frameworks between hosts and plugin developers - Training: Develop user experience design courses focused on progressive complexity - Documentation: Create UX guidelines for plugin and theme developers #### DevRel - Developer advocacy: Promote "Vercel experience" standards for WordPress deployment - Education: Host workshops on AI-powered rapid prototyping techniques - Developer experience: Create tools for plugin integration with page builders - Community management: Facilitate host-plugin collaboration initiatives ## 🧪 Hypotheses - Progressive complexity configurations will reduce user abandonment rates - AI-powered support hybrid models will improve satisfaction while reducing costs - Unified hosting-plugin experiences will compete better against SaaS platforms - Page builder integration is critical for WordPress product success ### 📊 Methodology - A/B test progressive vs. traditional configuration interfaces - Measure support resolution times with AI-human hybrid approach - Survey user satisfaction across different hosting-plugin integration levels ### ❓ Questions - How can WordPress core facilitate better plugin-host collaboration? - What's the optimal balance between AI and human support touchpoints? - Can progressive complexity work for enterprise WordPress products? ### 🔮 Future Research - Impact of unified admin experiences on user retention - AI chatbot proliferation effects on WordPress admin usability - Cross-platform user experience expectation studies ### 💡 Implications - Practice: Product owners must prioritize visual, intuitive interfaces - Policy: WordPress community needs collaboration standards - Security: Unified experiences may require new security considerations - Education: UX design skills become critical for WordPress developers - Funding: Investment needed in cross-ecosystem collaboration tools ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade #### 👀 Visual learners - Present: Discussion format with clear examples - Improve: Add UX wireframes, before/after interface comparisons #### 🔊 Aural learners - Present: Full video discussion with multiple perspectives - Improve: Chapter markers for easier navigation #### 🗣️ Verbal learners - Present: Rich dialogue with technical term explanations - Improve: Glossary of UX and technical terms #### 🧩 Kinesthetic learners - Present: Real-world examples like the worm farmer story - Improve: Interactive UX design exercises #### 🧠 Logical learners - Present: Clear problem-solution frameworks - Improve: Decision trees for UX implementation choices #### 🧑‍🤝‍🧑 Social learners - Present: Panel discussion format with multiple experts - Improve: Community discussion prompts #### 🧘‍♀️ Solitary learners - Present: Comprehensive notes for individual study - Improve: Self-assessment UX audit checklists #### 🌿 Naturalistic learners - Present: Ecosystem thinking about WordPress community - Improve: WordPress ecosystem diagrams ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video has spoken content - Improve: Detailed timestamps and transcript formatting #### Keyboard navigation - Present: Standard YouTube controls - Improve: Custom chapter navigation #### Contrast and readability - Present: Standard YouTube player interface - Improve: High-contrast viewing options #### Media and captions - Present: Auto-generated captions available - Improve: Professional captions with speaker identification ### 🌍 DEIB Assessment #### Cultural breadth - Present: North American perspective primarily - Improve: Global WordPress community examples #### Inclusive language - Present: Professional, respectful discussion - Improve: More diverse use cases beyond tech entrepreneurs #### Representation - Present: Male-dominated panel - Improve: Include more diverse voices in future discussions ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear progression from user expectations to solution strategies - Inductive strength: Good use of specific examples to support general principles - Causal reasoning: Well-established connections between AI advancement and user expectations #### Fallacies - Anecdotal evidence: Heavy reliance on individual stories like the worm farmer - False dichotomy: Some either/or framing between WordPress and SaaS platforms #### Tone of voice - Overall tone: Professional and collaborative with practical focus ### 🛡️ DARVO Analysis - Deny: No instances of denial or minimization - Attack: No attacks on accusers - Reverse victim/offender: No victim/offender reversals - Emotional cues and rhetoric: Constructive problem-solving discussion ## 🎯 Conclusion WordPress product owners must embrace progressive complexity, AI-human hybrid support, and unprecedented collaboration across the ecosystem to meet modern user expectations. The path forward requires moving beyond traditional WordPress silos toward unified experiences that compete with SaaS platforms while maintaining WordPress's flexibility and power. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Progressive complexity reduces configuration abandonment > [!quote] [Meeting Modern User Expectations in WordPress](https://youtu.be/h91da79cDDk) by [[WP Product Talk]] via [[YouTube]]. Published 2024. Accessed 2024-12-19. > "I start with easy configurations that apply to everything and then you can drill down" Approach allows users to get started quickly while providing advanced options for power users. [view highlight](https://youtu.be/h91da79cDDk?t=1110) #ux-design #configuration-design ID:rw_progressive_complexity ### [H2] AI accelerates both problems and solutions in UX > [!quote] [Meeting Modern User Expectations in WordPress](https://youtu.be/h91da79cDDk) > "AI alone is accelerating everything so fast. It gives us tooling to meet expectations quicker" Technology creates higher user expectations while simultaneously providing tools to meet them. [view highlight](https://youtu.be/h91da79cDDk?t=330) #ai-impact #user-expectations ID:rw_ai_acceleration ### 📚 Atomic Split Pad (Zettel Candidates) #### [Z1] Users expect SaaS-level reliability from WordPress - Scope: Applies to all WordPress installations, not just managed hosting - Pointer to: 8:45 timestamp discussion - Links: [[Platform-Expectations]] [[WordPress-Hosting]] #### [Z2] Visual interfaces should eliminate multi-screen workflows - Scope: Particularly relevant for plugin and theme configuration - Pointer to: 22:15 timestamp discussion - Links: [[Interface-Design]] [[User-Experience]] ### ✏️ Fleeting Queue - [F1] Research Vercel onboarding experience for WordPress deployment — https://vercel.com #fleeting #research - [F2] Audit current plugin for multi-screen configuration issues — internal review #fleeting #audit - [F3] Investigate page builder integration APIs — Elementor, Divi documentation #fleeting #integration --- ## Full Transcript [00:06] Hey everybody. If you've been in the [00:08] WordPress space for a while, uh you know [00:12] that so much of the product experience [00:15] that people experience is filling out a [00:18] bunch of settings like going through a [00:20] form, clicking this, clicking that, and [00:23] often not even knowing what's going to [00:25] happen on the other end of it. Uh that's [00:27] the way it has been in WordPress for a [00:29] really long time. Things have been [00:31] changing quite a lot. Things are getting [00:32] a lot more visual oriented. Uh but the [00:35] thing is user expectations are quickly [00:38] outpacing the way that we're able to get [00:40] there. Today we're going to talk all [00:42] about user expectations and how to meet [00:45] and exceed them in the WordPress space. [00:52] This is WP product talk. The place where [00:56] every week we bring you insights, [00:58] product marketing, business management [01:00] and growth, customer experience, product [01:03] development, and more. It's your go-to [01:06] podcast for WordPress product owners by [01:09] WordPress product owners. And now enjoy [01:13] the show. [01:20] Hey everybody, I am Matt Cromwell uh [01:24] from WP Product Talk [01:26] >> and I'm Zach Katz from Gravity Kit [01:30] >> and uh we today are talking about user [01:34] experiences. We're having a weird fun [01:36] little formatting issue with our slide [01:38] deck here. This is fascinating. I've [01:41] never seen this happen before. So, while [01:43] Matt is figuring that out, uh, I want to [01:46] thank Fremius for being our exclusive [01:48] growth partner on the road to 10,000 [01:50] subscribers. That's that's our goal, uh, [01:53] to get 10,000 YouTube subscribers. [01:56] Fremius, haven't heard of it? Well, you [01:58] should because they help software makers [01:59] grow, monetize, and succeed. Fremius is [02:02] a merchant of record platform, and what [02:04] that means is they handle everything [02:05] surrounding selling software. Checkout, [02:08] payments, subscriptions, licensings, [02:09] updates, everything you need to know. [02:11] global tax compliance even so you can [02:14] focus on building amazing products. So [02:15] check out Fremius. Huge thanks for [02:17] sponsoring uh WP product talk. [02:21] >> Awesome. Awesome. Thanks, Zach. And for [02:24] today's subject of talking about user [02:26] experiences um and amazing user [02:29] experiences, we are bringing on two [02:30] folks. [02:32] longtime friend of mine, Carl Alexander [02:34] is here and a new friend, CEO of [02:38] BuiltWith, Paul Carter as well. Hey [02:43] folks, thanks for being here. [02:45] >> Hey Matt. Hey, Zach. [02:47] >> Yeah, thanks for coming on. Uh, so Carl [02:50] Ven Paul, please tell everybody a little [02:52] bit about yourself. [02:54] >> Oh my goodness. Uh, I don't know where [02:57] to start, but uh, longtime WordPress [02:59] developer, freelancer, [03:02] uh, love basically building crazy [03:05] things, which is what I'm doing with [03:06] Emir. I'm working on Emir, which is [03:08] bringing serverless technology to [03:11] WordPress, [03:12] uh, and the PHP space. Um, that I think [03:16] that's a good short explanation. [03:18] >> Cool. [03:20] >> Uh, so my name's Paul Carter. I've been [03:21] in the web hosting and SAS space for [03:24] last couple of decades. Uh most recently [03:27] uh myself and my two co-founders Justin [03:29] Mazy and Josh Priddle were at A2. Uh and [03:32] after leaving there after the sale [03:34] recently uh we founded uh Builtfast uh [03:36] which is sort of a modern web hosting [03:39] company focused on uh best experience uh [03:42] for WordPress folks as well as other [03:45] hosting traditional hosting. So this is [03:47] appropriate for us. [03:49] >> Awesome. Love having you both here. If [03:51] you are watching right now on YouTube, [03:54] then uh feel free to use that comment [03:56] section and ask your questions. Um any [03:59] and all questions about embarrassing [04:01] stories about Carl, I can answer. Um I [04:05] cannot answer those questions about [04:06] Paul, but um you know, we'll see how [04:08] things go. [04:09] >> Paul is much more respectable than Carl. [04:10] >> I don't know. Zach and I could probably [04:12] have a couple word camp days. [04:15] >> Yeah. [04:16] >> Yeah. Maybe today we get to create those [04:18] embarrassing stories. Paul maybe. So [04:21] >> I mean there's one of them right behind [04:22] me. So there just like there's countless [04:25] countless stories. [04:27] >> Yes. So first up um we I want to talk a [04:31] little bit about just the problem that [04:33] we're trying to address right now. Uh [04:35] this whole idea that we want to create [04:38] amazing uh product experiences, user [04:41] experiences, but customer expectations [04:45] are racing and getting higher and [04:47] higher. Um what I'd love to hear a [04:50] little bit about what is your zeitgeist [04:53] about this situation at the moment. [04:54] Paul, I'd love to hear your take. Um [04:57] talk talk a little bit about what you're [04:58] seeing in the space and uh what this [05:01] problem is exactly. [05:02] >> Yeah, I think well I think one you know [05:05] you guys probably hear it all the time [05:06] but AI alone is is accelerating [05:09] everything so fast. Um, it gives us the [05:11] tooling to be able to meet expectations [05:13] quicker through rapid prototyping or [05:15] trying new things and even building [05:17] faster, throwing away stuff and and [05:20] keeping stuff that is is great. Um, but [05:22] in terms of, you know, like our process [05:24] and things that we've worked on, uh, you [05:26] know, trying to get as close to the [05:28] customer or the partner while you're [05:30] having those conversations, literally [05:32] making them in putting them in the room [05:34] or having the conversation with them on [05:36] a weekly basis, um, and really watching [05:39] them go through it. I think those things [05:41] combined with the speed that we're [05:42] seeing right now are probably the the [05:44] best way I've seen in the current uh [05:47] environment to get the best sort of user [05:49] experience uh out of whatever we're [05:51] building. And that's what we're trying [05:52] to do. And it's hard, right? You know, [05:55] it's hard to get feedback. It's hard to [05:56] get people in the in the room to have [05:58] the conversation. Uh but the tooling [06:01] allows us to move very very quickly. So [06:03] I think that's what we've been focused [06:04] on recently. [06:05] >> Yeah. Yeah. I love it. Um Carl, what's [06:08] your take? Are you facing the same [06:10] thing? I mean, Yamir is a very different [06:12] product. Um, not very customerf facing [06:16] overall, but like what's your take on [06:17] this situation? [06:18] >> I mean, so you've known me a long time. [06:21] And Zach too, like Zach, a funny story, [06:24] Zach, so the domain's like emirapp.com [06:27] and Zach was like so frustrated I didn't [06:30] have emir.app that he bought it for me [06:32] and transferred it to me. [06:33] >> I got so I got so mad. [06:36] >> So mad. so mad about it. I still I still [06:38] might use it. Uh [06:40] >> you're still not using it? Oh my god. [06:42] >> No, I'm still not using it. Uh but so [06:45] I've been I've been talking about this [06:47] tech I started working on this in 2019 [06:50] to give you an idea. Right. So I've been [06:51] I've been talking about this and working [06:54] in Canada this year and Cloudfest USA. I [06:57] started I'm preparing for a rebrand and [07:00] I've been changing a bit about talking [07:02] about customer expectation and the view [07:06] on this technology or the the interest [07:09] has gone through the roof basically like [07:12] both times I could not finish my talk in [07:14] time because I was getting so many [07:16] questions either it went over or I got I [07:19] had to stop it. Um, so it it really [07:25] speaks to the moment where I think the [07:27] customer expectations around hosting and [07:30] like uptime like from a developer from [07:34] developers to customers, nobody wants to [07:36] hear about their site going down for any [07:39] reason whatsoever like like it doesn't [07:42] matter. And that's why like platforms [07:46] like uh Shopify and Wix and Squarespace [07:49] have a huge like foothold on that [07:51] because when you're on that platform you [07:54] never go down, right? Like executives [07:56] talk about like sassification [07:58] of software but not sacification in [08:00] terms of like the pricing model [08:01] sassification in terms of expectation. [08:03] When you pay for a SAS [08:06] like it never goes down. Can you imagine [08:08] if you if a SAS was as down as a [08:10] WordPress site like their turn rate [08:12] would be like 20 30%. Like it's [08:15] impossible, right? So I'm seeing it even [08:17] in tech talks. So it's crazy. [08:20] >> Yeah. I was thinking about a little bit [08:23] in terms of the kind of evolution of the [08:26] way that we do work on computers and [08:29] whatnot. Um I you know for the longest [08:32] time if you were going to accomplish [08:34] anything on your computer it was going [08:36] to be with a locally hosted application. [08:39] You got to download the thing and [08:40] install it and then it's running on your [08:42] machine. And in that environment of [08:45] course it's like it's always going to [08:48] you know more or less it's always going [08:50] to work. It's it's on your machine. It [08:52] you pull it up and it doesn't matter [08:54] whether you have the internet or not. Um [08:56] it's going to work. But now so much of [08:59] the work that we do and accomplish [09:02] actually is on the web um and physically [09:05] requires the internet in so many [09:06] different ways. Uh and folks's [09:09] expectations though have stayed the [09:11] same. They're still expecting to have a [09:13] desktop like feel and a desktop like [09:17] stability even though they're depending [09:19] 100% on gigabytes of data going through [09:22] there all the time. I think of like a [09:24] platform like Figma. I could never never [09:27] comprehend something like Figma existing [09:30] uh for me uh like six seven years ago [09:33] actually it did launch I think six seven [09:35] years ago at this point 10 years ago [09:37] let's say um uh you know doing Adobe [09:41] Illustrator and whatnot was the only way [09:42] to get that kind of work done and now [09:44] you can do all of that in the browser [09:46] it's insane um so that and they're [09:49] expecting more and more th those types [09:51] of experiences I think I don't know Zach [09:53] what's it what's it make you think about [09:55] right now. [09:56] >> Well, uh, in terms of 10 years ago, [09:58] Gravity Kit's 11 years old, turning 12 [10:01] this year. Uh, and that's a long time, [10:03] right? And the difference between the [10:05] customer expectations then and now, um, [10:09] it's it's it's exponentially people are, [10:12] I think, frustrated by the level of [10:14] customization that's required to get [10:16] something done. And so, Gravity Kit has [10:19] a lot of settings, a lot of [10:20] configuration. You drag and drop fields, [10:22] you configure the field layouts. It's [10:24] it's like a little page builder for [10:26] Gravity Forms data. And people just want [10:28] solutions and they also want powerful [10:31] applications at the same time. And [10:33] Gravity Kit can do that, but it still [10:35] requires way too much customization. And [10:38] so internally at Gravity Kit, we're [10:40] talking a lot about how to provide [10:41] solutions rather than how to provide [10:44] explainers for how to build those [10:46] solutions. Like we want to make it [10:48] easier for people to get from I've [10:50] bought and installed your plugin to I am [10:52] done. And reducing that is really I [10:55] think the goal of should be the goal of [10:58] all product owners at the at the moment [10:59] because we are under threat from AI and [11:02] under threat from Shopify and Wix and [11:04] Squarespace who provide uh simpler even [11:09] if it's not as thorough uh [11:11] implementations. [11:14] Yeah, I I think similar to what Zach was [11:16] just saying, like even in the hosting [11:17] space, you know, if you look at 10 years [11:19] ago, you could literally just keep [11:21] throwing hardware at something to keep [11:23] it keep it up and running. And even now [11:25] with everyone being online, you know, [11:27] the distributed model or trying to keep [11:29] things online uh and responsive has [11:32] become a real challenge even just for [11:34] large e-commerce websites. I think to [11:36] what Carl was saying, you'd never expect [11:38] Shopify to be down for some extended [11:41] period of time or Matt was mentioning [11:42] Figma, any of the tools that we use, but [11:44] certainly as a user, my website or my my [11:48] application online being down or not [11:50] accessible or not scalable has just left [11:53] the the mindset of people like that just [11:56] isn't acceptable anymore. And I think [11:58] that's where we're seeing a lot of the [11:59] shift. And then you have folks like Carl [12:02] who spent all of his time for the last [12:04] five six years just focusing on how to [12:05] keep the website up and scalable [12:08] indefinitely. And I think that's where [12:09] we see a lot of the benefit from subject [12:11] subject matter experts um who are deeply [12:14] trying to understand that problem [12:15] whether it's like Zach's team trying to [12:17] make it really simple one button one [12:19] button push to get something up and [12:21] running easy or or Carl with you know [12:23] how do I make it just uh simple to keep [12:25] the site scalable. [12:27] Yeah, I mean I'm seeing it like just you [12:31] know when I gave the talk at CloudFest [12:33] like I had these young JavaScript [12:35] developers in the back and I have a [12:38] slide that says like I wanted the [12:39] Versell experience and you should have [12:41] seen their heads not like I think their [12:43] heads were going to fall off their you [12:45] know their shoulders like like [12:47] developers don't want to hear about this [12:49] stuff like nobody wants everybody has [12:51] this expectation that you deploy code [12:54] and then it just stays there it scales. [12:57] It does what it needs to do. And also [12:59] like even for me for Emir, I try to keep [13:02] it simple like you know it's still a [13:04] developer product but I use a lot of [13:06] what I call like progressive complexity [13:09] like in configuration. So I start with [13:10] easy configurations that that apply to [13:13] everything and then you can kind of [13:15] drill down and and customize it more [13:17] granularly if you want to. But um yeah, [13:22] so um but that's like really important [13:26] basically to have this kind of simple [13:28] experience and that's what devs want and [13:30] that's part of the Verscell experience [13:31] right because the Verscell when we talk [13:33] about the Verscell experience for those [13:35] who don't know Verscell is the company [13:37] that runs that built Nex.js which is a [13:40] very popular uh JavaScript framework and [13:43] they basically make it super simple to [13:46] host a Nex.js JS application like you [13:47] connect your GitHub repo, it deploys it [13:50] and that's it. You're done. [13:52] >> That's it. Yeah. [13:54] >> And you're done, right? Um there's no [13:57] questions of like how much RAM you have, [14:00] how many CPUs you need. Like nobody [14:02] wants to hear about this. Like nobody [14:04] nobody nobody wants to hear about it. [14:06] Like they want it the same thing as as [14:08] for regular products. Developers want [14:11] simple experiences. Like I'm an old [14:13] boomer who started like basically [14:15] managing servers when he was like 15, [14:18] but nobody's growing up managing servers [14:21] anymore. Like you know, nobody wants to [14:23] SSH in and like tinker with stuff. Like [14:26] they just wanted to just grow and scale. [14:29] And like Paul was saying, like I've been [14:31] working on that for like a long time, [14:33] but the message just really started [14:35] hitting this year because I think [14:36] there's been a critical kind of point in [14:39] user expectations that's been hit this [14:41] year, like an inflection point where [14:43] this stuff just matters now. [14:45] >> Absolutely. I think the other aspect um [14:49] that is really significant when it comes [14:51] to um plugins and themes and whatnot um [14:55] is just also that the UI of whatever [14:58] you're interacting with should explain [14:59] itself intuitively. Uh folks really are [15:03] tired of being like, "Okay, I'm going to [15:05] go and work on this one thing in this [15:07] one screen, and then in order for me to [15:10] have success, I need to go over to a [15:11] whole another screen and do something [15:12] else over there, and then I need to go [15:15] and check out, make sure that it [15:16] actually works on the front end the way [15:18] I'm expecting it to. Uh I mean, this has [15:20] been that in so many ways is the [15:23] WordPress way for a really long time. [15:26] Not only just that you do something in [15:28] the admin and then you have to go and [15:29] make sure it still looks okay. Uh but [15:31] sometimes you have to do it across [15:32] multiple different screens before [15:34] anything is is actually working real uh [15:36] correctly. Um but uh I don't know [15:39] exactly the best way to describe uh the [15:42] path forward under those circumstances [15:44] but I can say clearly that the users are [15:47] more and more expecting that whatever [15:49] they're going to get done is going to be [15:51] done in a in a very uh intuitive and [15:54] visualoriented way and not only should [15:57] be up and functioning all the time it [16:00] also should actually uh make sense to [16:02] them visually immediately. [16:04] Does that resonate with you, Zach, as [16:06] well? [16:07] >> Yeah, it does. Um, one of the things [16:10] that that Carl was saying and Paul was [16:13] about uptime expectations, and I thought [16:15] that was really funny that one of the [16:17] other things that's come in and and I [16:19] think this applies in other ways to the [16:21] plug-in space. While we while [16:23] expectations have increased in [16:25] surrounding uptime, the understanding [16:27] that when Cloudflare is down or Amazon [16:29] is down, it's okay. It's not your fault. [16:33] that that shift and the like the public [16:35] understanding that everything is so [16:36] hyperconnected [16:38] um has really evolved um at least what I [16:41] saw as the reaction to the downtime that [16:43] Cloudflare and and and Amazon had. Um in [16:46] terms of the questions about like [16:49] configuration, I do think Matt that the [16:51] trend is toward hyper simplicity. Uh but [16:54] part of the problem there is that uh we [16:57] get down to like the AI chatbot like the [17:00] the single prompt box as the simplest [17:02] thing that people could do. Yet that is [17:04] just like a a facade for unlimited [17:07] complexity. And so the goal is like Carl [17:10] was saying progressive enhancement and [17:12] progressive disclosure for as you master [17:16] one thing we can present you with the [17:18] next level of of of skill. And there's a [17:21] great book called making oh it's over [17:24] there making your users awesome. Um I [17:27] think it's the the main title is badass [17:29] making your users awesome. It's all [17:31] about this where it's like your job as a [17:33] plug-in owner as a product owner is to [17:37] guide your users to expert toward [17:39] expertise uh progressively. So it's not [17:42] like okay you're going to go from being [17:44] afraid of heights to bungee jumping. [17:46] It's you're going to ease into this uh [17:48] process of learning this tool and [17:50] becoming masterful in it. [17:54] >> Paul, I'd love to hear um some uh [17:57] examples or if you have things top of [17:59] mind. It looked like you had something [18:00] on top of mind already. So, [18:02] >> I did. Yeah. Like you brought up a great [18:04] experience. Sorry, I apologize. Go [18:06] ahead. [18:06] >> No, no, no, no. It's all you. I was [18:08] going to say you brought up a great [18:09] experience like um one of the things [18:11] that we got to do when we relaunched [18:13] Builtfast was to rethink about how a [18:15] control panel would work. We're all sort [18:17] of very familiar with the the primary [18:18] control panels are out there. They're [18:20] very task focused like let me let me [18:22] find the button that does the thing I [18:24] want it to do and then I'm going to do [18:25] that thing in here and then I got to go [18:27] over here to this other button to do [18:28] that thing. Um, and it's it's powerful [18:31] because you have a lot of features, but [18:34] the workflow uh can be really difficult [18:36] on users. And sometimes that's similar [18:38] even in WordPress if I'm trying to do [18:39] multiple steps and I want to do multiple [18:42] things inside of there. And so, um, one [18:44] of the things our product team, you [18:45] know, we're working with Carl on a new [18:46] product called Vector that that takes [18:48] his product and and makes it usable. And [18:50] one of the things that our product team [18:52] can do is actually use AI to develop [18:55] quick UX. um uh not just even [18:59] wireframes, but usable functional [19:02] separate apps or internal uh pages or [19:05] flows. And it's much easier for us to go [19:08] through. There used to be a pretty high [19:10] bar to say like, "All right, I'm going [19:13] to throw a designer at this. I'm going [19:14] to throw a UI person at this. I'm going [19:16] to then have it coded up and try it." [19:19] And now, like within a day or maybe two, [19:22] you can have five, six, seven working [19:24] prototypes and flows. You can put those [19:26] in front of users. You can put those in [19:28] front of your teams and get feedback and [19:30] go what feels the most intuitive. How [19:32] does and and even real time now where if [19:35] you're even if you're willing to do some [19:37] vibe vibe coding, you can put a user in [19:39] there, have them walk through it, and [19:41] then say, "Oh, he he ran into a a cold [19:44] sack here. Let me make a quick change. [19:46] Now, walk through it again. Oh, that [19:48] didn't happen again." Um, so I think [19:50] when we're talking about the [19:51] expectations again, the speed and the [19:53] the level of expectation like Zach's [19:55] like it's all interconnected, everything [19:57] should stay up and you know, uh, [19:59] whatever. Uh, but it's very high bar. At [20:02] the same time, we now have tooling that [20:04] allows us to get much much closer to say [20:07] the Figma experience or the Shopify [20:09] experience or whatever, even for small [20:11] businesses or or you know, hosting [20:13] companies or whoever. [20:15] One of the things we've done at Gravity [20:17] Kit over the years is we really focused [20:19] on having great text documentation and [20:22] some good onboarding videos, but those [20:25] videos show how to create a simple [20:28] application uh that are complex but not [20:31] really complex. And one of the things we [20:33] just were talking about in team in a [20:34] team call was we need to show from start [20:37] to finish all the nitty-gritty. uh so to [20:41] to expose to ourselves uh how much [20:45] complexity there is so we can simplify [20:47] the process and we can also demonstrate [20:49] to users what the current experience is. [20:51] We need to simplify that uh so much the [20:54] use of any short codes is a kind of uh [20:57] failure state that should be represented [21:00] by a user interface uh or like a an AI [21:04] prompt like there there should not be uh [21:08] as many places in our plugins or our [21:10] settings for misunderstanding for uh [21:13] errors to be introduced for like it's [21:16] easy to fail all across WordPress by [21:19] clicking a button and that's [21:20] unacceptable. [21:21] And I do think that when you can just [21:24] say to GPT uh you know that's not [21:26] working fix it. That's where the user [21:28] experience has been shifting so much so [21:31] rapidly like why is Google so bad? Why [21:34] can't I just ask it a question and get [21:36] an answer like chat GPT? Like that same [21:39] question people are asking across [21:40] WordPress. Why am I having to do all [21:43] this stuff and how can it be simpler and [21:45] like how can I get out of this as soon [21:47] as possible and just get what I want [21:50] done? And for us like that is a process. [21:54] I don't think there's a single answer. I [21:56] think it's every episode of WP product [21:58] talk where we talk about onboarding, we [22:01] talk about marketing, we talk about like [22:03] uh user accessibility, we talk about [22:06] like all the all the different aspects [22:09] of running a business are going to be [22:11] coming into play here as people expect [22:13] more and better from from their web [22:16] experience. [22:17] >> 100%. 100%. [22:21] Carl. [22:23] >> Yeah, I mean AI is changing a lot. Like [22:28] I can't I mean Google has good AI [22:31] answers now, but I one of the I mean I [22:34] use it some like but uh I'm a big Gemini [22:40] stand actually. So I was just like [22:42] >> I'm a big Gemini stand. Their AI if I [22:44] see an AI answer something instantly I [22:46] assume it's wrong. I mean, but the AI [22:49] stuff is hard. Like I talk a lot about I [22:52] mean, we're talking product, but on the [22:54] marketing side, it's it's decimating [22:57] >> everything. Um, like, you know, I, [23:02] >> you know, I didn't do that much content [23:03] marketing and I'm like, I don't feel I [23:05] missed out, you know, like it's like [23:07] because it I don't know if it matters. [23:09] Like I feel like having the community [23:11] and stuff like that matters for products [23:14] and stuff like for user expectations. [23:17] they want to talk with somebody if they, [23:19] you know, if AI can't solve it, they [23:20] want to talk with someone. Uh, you know, [23:22] like I think support's as important as [23:25] ever. Uh, things like that. But yeah, [23:28] it's like it's really hard. Like you can [23:31] solve so much that way. [23:34] >> Let's talk about that a little bit [23:36] because and Matt, I'd love to hear your [23:39] thoughts on this. Like one of the things [23:40] we're considering is as AI is taking [23:43] more and more support responses, maybe [23:45] we bring on some phone support or we [23:48] bring in like a tier 2, tier three one- [23:51] on-one like Zoom calls. Like how are uh [23:55] how is is that how is AI shifting the [23:59] customer expectation of support? [24:01] >> Yeah, I'm sure Paul has some good [24:03] thoughts on this too. I mean, the whole [24:05] aspect of how AI can benefit um the [24:09] customer support environment, I think is [24:12] something we've talked about on the show [24:13] quite a bit. Um and I do think I do [24:16] think that AI is is a good way to [24:20] provide solutions to customers faster, [24:23] faster than an agent can. And if you're [24:26] not trying to make sure that your AI is [24:29] providing solutions to your customers [24:30] faster, you're you're in the wrong [24:32] business. like you you have to do that. [24:35] Um, but I love the the note that you [24:38] brought in there too, Zach, in the sense [24:40] that like sometimes folks don't care [24:43] that your bot can give them faster [24:45] answers. They just want to talk to a [24:47] human. Like there is this aspect in [24:49] which it doesn't they don't actually [24:51] want a fast resolution. They want to [24:54] feel heard [24:57] and that's just never going to go away. [25:00] So bringing in an intentional like white [25:03] glove feeling of like you know our bots [25:06] can help you so you should use them as [25:08] much as you can but if you really need [25:10] somebody to kind of counsel you through [25:12] your hosting problem we have some folks [25:15] available to you. I think that's a nice [25:18] hybrid approach for sure but especially [25:20] in the hosting environment where [25:22] essentially they own the whole [25:25] environment AI can go to town. um like [25:29] if you have like a simple thing like uh [25:32] for example a an SSL certificate just [25:35] gets borked on renewal in one way or [25:37] another the hosting environment you know [25:39] it's just like AI should be able to be [25:40] like oh yeah let me renew that for you [25:42] right now you don't need to have a [25:44] person to like interrogate you for five [25:48] minutes over live chat to figure out [25:50] whether or not it's an SSL certificate [25:52] or not yeah it's an SSL certificate [25:54] renew something like right now like it [25:58] That's not hard. That's not rocket [25:59] science anymore. Um, and it doesn't [26:01] require a person. And the person who [26:03] does that kind of support, they don't [26:05] enjoy that kind of support. They're just [26:07] like, "Oh my gosh, here's like the three [26:09] dozen um SSL renewal thing that I've had [26:12] to do this week." Um, that's not a [26:14] enjoyable uh work environment to have. [26:17] Um, so I I find support technicians are [26:20] excited by AI that solves the dumb [26:23] support um and are really motivated uh [26:27] to help people at a higher level. So [26:29] that that hybrid thing I think is ideal. [26:31] Anyway, I don't want to steal all of the [26:34] insights that Paul has in the hosting [26:35] environment and AI and support, but the [26:37] that's been my experiences too. So [26:39] >> yeah, I couldn't agree more. I think you [26:41] know it's a it's a stepped process, [26:42] right? which is that if you build a [26:44] product well at first by meeting those [26:46] expectations, you just generally have [26:48] less uh support coming in. But I've also [26:50] seen now that AI is out there, you see [26:53] some people clumsily trying to cram AI [26:55] as the frontline agent. And that just [26:58] it's like calling a a 1-800 number for [27:00] support when you desperately need it. If [27:02] you're calling the 1-800 number, most [27:05] people now have probably done some level [27:07] of due diligence or it's not obvious [27:09] that it's it needs to be they can be [27:11] fixed uh easily. And so the last thing [27:13] you want to do is put them through 15 [27:16] variations of like press two for so and [27:18] so. And same thing on AI chat. Now what [27:20] I do think and this is where I think uh [27:23] you're 100% right is um similarly to [27:26] developers who are using AI. If you put [27:29] um a tool like AI in someone who doesn't [27:31] know how to code in their hands, they [27:33] might get some stuff done, but really [27:35] putting AI into to a subject matter [27:37] experts hands, a developer that [27:39] understands, you turn them into a ninja [27:42] or a you know whatever a monster in [27:45] terms of producing. It's the same thing [27:47] for for um I think our agents, right? So [27:50] you have fewer level two, level three [27:52] agents versus these level one agents. [27:55] Um, and by default, you're bringing up [27:57] an account. It immediately does the [27:59] scanning. It can uh parse the [28:01] information. It can pull out the [28:02] relevant information. So, the agent [28:03] doesn't have to spend 10 minutes reading [28:06] a response or talking to the customer up [28:08] front. It can automatically do a lot of [28:10] that pre pre-work. Um, and then you get [28:13] to do the the thing that it really, like [28:15] you were saying, Matt, that humans [28:16] really enjoy doing, which is I just want [28:18] to help. I want to solve this problem [28:19] for you without frustrating you or [28:21] frustrating me doing the menial tasks. [28:24] And I think that's where if you can get [28:26] it right, the AI does a phenomenal job [28:28] of of coming alongside uh support people [28:31] >> 100%. I'll I'll add one more thing that [28:34] I I also do think the hosting [28:36] environments, SAS applications, they [28:38] have the benefit that they own all the [28:40] code um and can control that environment [28:43] um basically 100%. WordPress plugins and [28:47] themes are distributed. it's a lot [28:49] harder, but there's a lot of really [28:50] smart folks doing a lot of things to try [28:52] to bring the support experience into the [28:54] WordPress admin. And as we build out our [28:57] MCP for WordPress and the core AI team [28:59] is building more uh AI into WordPress [29:02] core itself, I think that's going to [29:04] empower plugins to have a lot better [29:06] access to the environment that the [29:08] customer lives in uh and to be able to [29:10] provide a lot better support in that [29:13] environment. That's one thing we were [29:15] doing at StellarWP is putting the [29:18] support into the WordPress envir [29:20] environment with the benefit of AI being [29:23] able to provide a lot more context than [29:25] what the user is saying purely in a [29:27] little chatbot. Um I I think that that's [29:30] also the future for uh WordPress [29:32] products because it's been our Achilles [29:34] heel for too long. We just we we can't [29:36] see their environment. We don't know [29:37] everything about it and the customer [29:39] doesn't know how to explain what's going [29:41] on in their environment. uh they often [29:44] don't even know where their system info [29:45] is in order to provide it to you. Um so [29:48] having all those things at your [29:49] fingertips um is is something that's [29:52] going to become more and more common, [29:53] more and more normal for WordPress [29:55] plugins, too, I think, going forward. [30:00] >> Yeah, I mean, oh my god, I have so many [30:02] thoughts. First, I want to shout out to [30:03] Zach, my co-host, for for saying like I [30:07] think I agree with him. Legendary human [30:10] support I think is critical. I think [30:12] that's why I want to [30:15] >> writes wholeheartedly believe that all [30:17] the way to stand out is to provide [30:18] legendary human support as fast as AI [30:21] can without the AI fluff. [30:22] >> Yeah. I mean I also believe in like this [30:25] idea of community and people helping [30:27] each other out and like having things [30:30] escalate uh like keeping that human [30:33] stuff. One thing I was thinking about [30:34] and I had kind of a kind of terrorizing [30:38] thought about as you were talking Matt [30:41] is what if we get the the chatbot [30:45] problem that we have with this the admin [30:49] notifications? What if every plugin has [30:51] a freaking chatbot in the in the admin? [30:56] >> Like [30:56] >> Yeah. I mean [30:59] cross my mind till till you were [31:00] talking. I'm like yeah but now like [31:03] That's where it's headed already. That's [31:05] what I'm saying. That's what we That's [31:06] what That's what I was physically [31:08] implementing at Stellar before I took [31:09] off. [31:10] >> The command pallet is really going to be [31:12] the interface that everybody needs to [31:14] implement otherwise it's going to be a [31:16] mess. [31:17] >> Yeah, they almost need a unified chat [31:20] solution that the plugins hook into [31:22] basically. And then but to me that's [31:25] like a disastrous scenario because again [31:27] like that's part of the part of the [31:30] challenges with the user experience like [31:33] is is this disjointedness [31:37] >> of of everything you know every and that [31:42] doesn't make for a good user expect [31:44] experience or user expectations right [31:46] like it's just it doesn't and [31:49] >> that's been an Achilles Hill of the [31:51] admin for a long time like people have [31:53] been pushing really hard to have like a [31:55] kind of unified design language and [31:57] whatnot, but it but you know can you you [32:00] know how are you gonna fight all the [32:02] chat bots the chat bubbles on on your [32:05] admin? There's going to be like a whole [32:07] row you know whole row at the bottom of [32:09] chat bubbles and it's just like which [32:11] one do you click on? Like it's [32:13] >> I mean I think that's going to be a huge [32:15] problem. Uh I was just hearing you [32:18] thought and I was like oh my god that's [32:19] like terrible. Like for me, I just think [32:23] I really like there's this um email [32:26] marketing software. It's one guy, but [32:28] he's like so talented. It's called [32:30] Bento. [32:32] Uh and he's building like a chatbot [32:35] thing, but he still has a very active [32:36] like he has a Discord and stuff, but [32:38] like the idea is like the chat should [32:40] definitely [32:42] the AI chat should be basically about [32:45] getting things done too. Like it's it's [32:48] I like so so much of it is about like [32:51] answering questions, but I I I view the [32:53] chatbot should be more as a yes, you can [32:56] ask questions about what why things [32:58] aren't working, but I think the power of [33:00] the chatbot is to get you to do things, [33:03] right? We talked about like, oh, it [33:06] sucks that you have to go through three [33:07] windows, three different windows to get [33:09] something done, but the chatbot doesn't [33:11] care. Like, it knows which settings to [33:13] go toggle. It just does it and then it's [33:15] like, "Oh, it's done." and then you can [33:17] just go back to the home screen. Like [33:19] it's about customer empowerment, not [33:22] >> so is that that is that a current [33:24] expectation of of modern WordPress users [33:28] though? Like is [33:29] >> I think that's where it's going. [33:31] >> That's where it's going. Yeah, I I [33:32] agree. I I I'm actually really curious, [33:35] Paul, your take because I for me coming [33:38] from uh the experience of like trying to [33:42] get support into a plug-in environment, [33:44] working at a hosting company, uh my kind [33:47] of like hail Mary was that I want [33:50] hosting companies to own this problem [33:52] because the bottom line is that you all [33:55] do in uh control that environment a ton [33:58] more than the plugins do. And often, [34:01] unfortunately, sometimes uh the customer [34:04] is going to reach out to the hosting [34:05] company for support and the hosting [34:07] company is like, "Oh, that's a plug-in. [34:09] That's not our problem." Uh, and that [34:11] just ends up being also a terrible [34:13] experience. You you know exactly where [34:15] I'm going, Paul. I'd love to hear your [34:16] thoughts. [34:17] >> Yeah, I I agree. Look, the worst thing [34:19] for a customer is to say the the agency [34:21] says that's a hosting problem, the [34:23] hosting company says that's an agency [34:25] problem, and then the customer is left [34:26] to go like, "I don't I don't know where [34:28] to go now." So that's the worst case [34:30] scenario. And um a lot of times the [34:33] let's go back to the support um the the [34:36] superb support piece which is no one [34:38] wants to take responsibility. The the [34:40] agency doesn't want to mess up something [34:42] in the the uh the environment and the [34:45] hosting company doesn't want to screw [34:46] something up in the plug-in and be [34:47] responsible for fixing it. And I think [34:49] again this is where real-time triaging [34:51] using AI tools um in in hand with anme [34:55] means that they can go like oh I've pin [34:57] it could run a bunch of tests it could [34:59] do a bunch of stuff and and pull back a [35:01] lot of data that would have not been [35:03] available. Um, you know, it's [35:04] interesting. Carla has been working on [35:06] some logging stuff for us and just [35:08] having access to that real-time stream [35:10] of data um will make us be able to [35:13] troubleshoot problems on the platform [35:15] infinitely faster, right? And ultimately [35:17] we can apply um AI or other types of [35:20] things that will either proactively or [35:22] dynamically give us like, oh, this has [35:24] been seen before. This is probably your [35:26] solution. Um, and how how can you get to [35:28] a self-healing environment is is a [35:30] different different thing. Um I you know [35:33] the struggle I think that we're going to [35:35] see is that you know Zach asked is this [35:39] the expectation of a modern WordPress [35:41] user? I think the answer is that we're [35:44] losing some of the people off of [35:46] WordPress because they go, "Oh, my [35:48] friend's using Shopify or my friend's [35:50] using this other Wix, Weebly, whatever [35:52] the other thing is." And I never have [35:54] that problem, [35:56] >> right? They have the full control of it. [35:57] And so they go, you know, WordPress was [36:01] uh and is hugely powerful and hugely [36:03] dynamic, but if you can't meet the user [36:06] where they're at, they will find another [36:08] solution. And I think that's where we've [36:10] been struggling a little bit honestly um [36:12] in those areas. And so is it an [36:15] expectation? Yes, Zach. I think it is an [36:17] expectation. I don't think that they um [36:20] I don't think that they think it's going [36:21] to get solved fast. And that's why we're [36:22] losing some of those users off to other [36:25] platforms right now. [36:26] >> Yeah. [36:27] >> Yeah. What do you think, Matt? [36:29] >> I I'm going to do another little tiny [36:32] spicy poke at the hosting guy. Um [36:36] um I think and part of the reason why we [36:39] have that dilemma where it's like oh I'm [36:41] on Wix, I'm on Squarespace, it's all [36:43] roses over here and WordPress is all [36:45] like, oh man, things are broken. It's [36:48] because of the at the end of the day [36:50] kind of like the false promises that the [36:52] managed WordPress hosting environment [36:54] promised uh that and if you're going to [36:56] be on managed WordPress, you're going to [36:58] pay a little bit more and that's because [37:00] we're going to manage your WordPress for [37:01] you so you don't have those problems. [37:04] But the truth is, manage WordPress has [37:06] just become basically like more or less [37:09] updating your plugins maybe at the best, [37:12] you know, um or yeah, will let you know [37:15] if there's a new PHP version that you [37:17] can upgrade to. Uh it's not at all what [37:20] it was ever intended to be in the first [37:22] place. Again, just poking at the hosting [37:25] guy. Not to turn on my brethren, but I [37:27] would say that I would agree 100%. And I [37:29] think one of the things you see in the [37:31] hosting space right now is this race to [37:34] the bottom where plans are $1.99 a month [37:37] or a managed WP is $4.99 a month. And um [37:41] and realistically at scale you're not [37:43] going to be able to provide the level of [37:45] support that a quote unquote managed [37:47] environment will be able to provide. [37:49] Right? When you say managed um you're [37:52] talking about somebody helping you do. I [37:54] mean, maybe it's automated in some way, [37:55] but you're expecting that somebody can [37:57] help you when you run into a problem. [37:59] Um, and so I've worked in other other [38:01] hosting companies over the years and [38:03] been through a number of them. And what [38:05] ends up happening is that you lose [38:07] customers off to price and they they [38:09] care less and less about the actual [38:11] service until the service becomes so bad [38:15] that they go, I it doesn't matter how [38:17] cheap you sell me this product, I'm [38:19] going to go spend it somewhere else. And [38:20] then now you have that's why you have [38:22] third you have some dedicated host who [38:24] are $35 to $50 a month for a website [38:27] that is you know three pages five pages [38:30] on a hosting thing. It's not it's not [38:32] about the need of the requirements or [38:33] the resources of the the site. It's [38:36] about about the fact that they want to [38:37] pick up a phone and get someone on there [38:38] that knows what they're doing when [38:40] something doesn't work. And so I think [38:42] we're in this uh you know not uh they're [38:45] in this pushpull like where you can't [38:47] sell something that cheap. uh it's a [38:49] marketing ploy to say it's managed when [38:51] it's not really managed but the end user [38:53] doesn't really know that right but as a [38:56] host if you're not being competitive and [38:58] offering competitive pricing uh on [39:00] similar products as everyone sort of [39:02] moves down to the bottom then it becomes [39:04] really difficult until someone has a [39:06] real problem and they're like oh no uh [39:09] you mean my $1.99 a month managed [39:11] hosting doesn't come with somebody who's [39:12] going to help me fix my plug-in problem [39:15] oh [39:16] >> now now maybe I should be looking for [39:18] something that actually does support [39:19] that. So, um yeah, you can poke at it. I [39:22] think it's I think it's a f a very valid [39:24] criticism. Um but I think it's a a mix, [39:27] right? Because again, there's infinite [39:29] number of plugins and for me to train my [39:32] staff or or our team to understand every [39:34] theme, every plugin th those that are [39:37] using modern building tools, those are [39:40] not using modern tools, the updated [39:42] security patches, it gets really [39:44] difficult. Um, and I think that's where [39:46] AI could help us scale quickly on those [39:49] areas and not use up a bunch of [39:50] resources, make it more expensive. [39:53] >> Yeah, love it. [39:54] >> So, one of the issues I think we're [39:56] facing is redefining who WordPress is [39:59] for. Uh, and that that's happening by [40:02] self- sorting like you were talking [40:03] about, Paul, that it's not for everybody [40:06] and it's never should have been for [40:08] everybody. like uh the people who should [40:11] have had a static site all along, they [40:14] should have a static site. That [40:15] shouldn't be what WordPress is for. If [40:17] it's just a markdown file that they can [40:19] edit, uh the proverbial markdown file, [40:22] um I wouldn't use WordPress today if I [40:25] didn't build on WordPress. I just [40:27] wouldn't. I would write in Markdown and [40:29] I would have a a you know, GitHub pages [40:31] site. Like that's all I need for my [40:33] personal blog. That's what I would use, [40:35] right? So that's a like if we're not for [40:38] blogging and if we're not for um you [40:41] know small sites like brochure sites [40:43] maybe like who is WordPress for? I think [40:45] that question is going to come into [40:47] focus um as AI progresses as well. But I [40:52] think right now the answer for meeting [40:54] modern WordPress user experiences as [40:56] product owners is Elementor. [41:00] I think we have to better integrate with [41:02] Elementor and page builders like Divvy, [41:05] Elementor, BeaverBuilder. Like we've got [41:08] to address those users because those are [41:10] the users who expect things to work in a [41:14] certain way that is consistent [41:15] throughout Elementor. There is [41:17] consistency outside of Elementor. It's [41:20] just WordPress and it's the wild west [41:21] out there. [41:22] >> Can I can I just respond real quick to [41:24] what Zach says? I 100% agree what you're [41:25] saying, but now the AI is available [41:28] because before the the markdown file was [41:30] sort of seemed too technical, even [41:32] though it's just text file, it seemed [41:33] too technical to users. Now I can use my [41:35] chat GBT or my cloud or Gemini or [41:37] whatever and I can just tell it like [41:39] just add this to this page. [41:40] >> It doesn't even need to know. Yeah, the [41:42] user doesn't need to know. [41:43] >> Nope. And so now I can use AI to just [41:45] update those pages and put things on [41:48] there quickly, [41:48] >> which is also a great hope for WordPress [41:50] in that like the WordPress MCP will [41:53] allow chat DPT will be the WordPress [41:56] interface where people just say like [41:57] write a new blog post for me about XYZ [42:00] and it it will automatically publish and [42:02] like uh or schedule it or whatever. I do [42:04] think that [42:05] >> that the interface to WordPress has [42:08] expanded uh even though the complexity [42:11] remains. [42:12] >> Yeah. Was [42:15] that a bit of where you were headed to, [42:16] Paul? [42:18] >> Say again. [42:19] >> Is that a bit of where you were headed [42:20] to? [42:21] >> Yeah, a little bit. I you know, I think [42:23] um I think as a host, we want to provide [42:27] as close to what Shopify or or Wix or [42:30] Weebly is pro, but for WordPress folks, [42:33] right? And we can only sol we can only [42:35] solve one part of that equation. I think [42:36] this is why the the Carl, you know, the [42:38] Amir and the Builtfast partnership on [42:41] this new product we're putting out, it [42:42] makes sense. You know, he deeply [42:44] understands the the scaling part of it. [42:46] We deeply understand the product and the [42:48] user and the support side of it, but at [42:50] the end of the day, what we're trying to [42:52] accomplish is making WordPress that sort [42:55] of click button uh and scalable, right? [42:58] Because again, we're on the hosting [43:00] side, so less on the theme and plugin, [43:02] but there's the same kind of thing where [43:04] do you have I mean, Carl can talk. Carl, [43:06] you should tell the story about the worm [43:07] guy because it's the best story ever, [43:09] but like uh you know, normal users don't [43:13] need or want to know about the hosting [43:16] infrastructure either. They don't even [43:18] less so than how to update their page. [43:21] They care less about the infrastructure [43:22] side of things. So we have the same [43:24] problem on the hosting side. Um trying [43:27] to provide that same like infinitely [43:29] scalable but still you know easily [43:31] approachable environment. [43:34] Worm guy, let's go. Okay. Worm story. [43:37] Yeah. So that was at work camp and um [43:42] basically somebody came up to me and he [43:44] was talking about this WooCommerce site [43:46] about this this farmer who sells believe [43:50] it or not $100,000 [43:53] worth of worms per month. [43:56] >> Per month. [43:57] >> Worms. [43:58] >> It's a lot of worms. But his site goes [44:00] down all the time. You know, well, not [44:02] all the time, but they the the person [44:04] managing the site struggles sometimes to [44:06] keep it up. and he's like, "I'm just a [44:09] simple worm farmer. Like, I should sell [44:11] my worms and I can't, you know, and and [44:17] this isn't a dig on like, oh, they [44:20] should go to use Shopify [44:22] because Shopify has limitations. Shopify [44:26] is doesn't let you spell what worms here [44:28] is okay, but there's like gray market [44:29] stuff and [44:30] >> you probably Yeah, there's some probably [44:32] international trade bans on worms. I [44:34] don't even like to think about worms." [44:36] Yeah. [44:36] >> Yeah. Exactly. Yeah. So, but there's a [44:39] reason why I think WooCommerce has a [44:41] bright future because it's like a [44:42] there's not a lot of alternatives to [44:44] Shopify if you can't sell on Shopify for [44:46] some reason. But it doesn't change that. [44:49] Again, it goes back to this expectation [44:52] of like why can I why can't I do this [44:57] thing? And every marketing executives [45:00] knows it. Every every person knows it. [45:03] Like I've talked with marketing [45:05] executives from all the big hosting [45:06] companies. Like they know it. They don't [45:08] want to they the last thing they want is [45:10] somebody to go on Reddit and say like [45:12] don't use WooCommerce. Don't use this [45:14] because like it just falls over the [45:16] minute I have like my lightning in a [45:19] bottle [45:20] moment, right? Like I make it to the [45:22] front page of Reddit and it's like you [45:24] know that that's like their lightning in [45:26] a bottle and then their site goes down [45:28] and they don't even know why and they're [45:30] like what's going on? like, oh, CPU's [45:33] disc. What? Like, what is going on, you [45:36] know? And uh it's just [45:39] >> Yeah. [45:39] >> To me, it's [45:40] >> Tell us how you got the worm guys [45:42] website running. Paul, uh Paul and Carl, [45:44] did you guys get it going? [45:46] >> No, no, no. It's not I know who hosts [45:48] it, but it's just uh and he's brilliant, [45:51] but it's it's just the story is so good [45:54] because it it talks to this user [45:56] expectation thing. [45:58] >> Yeah. where it's like, and the thing is [46:00] is it's the same thing with developers [46:02] now. They're like, what's a PHP worker? [46:05] Why do I need to care about how many [46:07] workers I have? Like, [46:09] >> what is this? Like, [46:10] >> yeah, [46:11] >> it's all gone. Like, it's not like, [46:14] >> yeah, [46:15] >> I think that's a transition from like [46:16] the nerd culture. We've won. The nerds [46:19] have won. Congratulations. Uh but we [46:22] also need to know that now that we're [46:24] mass like we're in charge of the culture [46:27] uh nobody cares about what we actually [46:29] are talking about. [46:30] >> But also it's layers of abstractions, [46:32] right? [46:32] >> Yeah. So we need to abstract it away. We [46:34] don't need to explain how the TV gets [46:37] streamed like through your your Apple TV [46:40] or your Roku or whatever or like built [46:43] into the TV itself. We don't explain the [46:45] bit rate. They just want the program to [46:48] run. Right. [46:48] >> Correct. Exactly. They just want to they [46:51] want to deploy and have it run [46:54] >> and that's kind of anti antithetical to [46:56] how WordPress is set up. So how do we as [46:59] individual product owners [47:01] >> how do we make this better for for for [47:03] product uh for our customers? [47:06] >> I I think it has you we need to find and [47:08] this is something we're focused on. So [47:10] small plug for us is we want to work [47:12] with agencies and theme and plug-in [47:14] developers to create more of a unified [47:16] experience between the hosting [47:19] environment and the product whether it's [47:21] a productized uh you know WordPress as a [47:24] SAS solution or if it's just hey we want [47:27] this to just work well on our product on [47:29] our on our platform. Um, that's that is [47:31] the thing we think we're doing slightly [47:33] differently. And so I think that's that [47:35] is the way forward regardless it's with [47:37] us or any hosting like developers and [47:40] and theme designers have to get closer [47:42] to the environment and the environment [47:44] folks have to get closer to the [47:46] development work that's being done. Um, [47:49] so that we're all working on that same [47:51] example which is it should just be push [47:53] button, right? Boom. I deploy it and it [47:56] just works and the product works and [47:57] it's easy to use. Um, but and this is [48:00] why I'm a big fan of like again when we [48:02] work with Carl, he's a subject matter [48:04] expert on scalability in in the AWS [48:06] environment. My team doesn't have to [48:08] think about that. Our team has to think [48:10] about how we do all the other things [48:12] that we do as a host, but we don't have [48:14] to think about the scalability. Working [48:16] with people who are subject matter [48:17] experts is the key to us being able to [48:20] overcome these things versus just being [48:22] in a silo or Matt, you and I throwing uh [48:25] fruit at each other like it's the [48:26] hosters's problem. No, it's not. it's [48:28] the other guy's problem. If we can [48:29] figure out how to honestly work together [48:31] in that environment and build solutions [48:33] around that, um I think that's how we we [48:35] overcome it and meet those expectations [48:36] for customers. Now, [48:38] >> 100% 100%. I love it. I mean, the idea [48:42] that uh any of us could have gotten to a [48:45] spot at which we can provide a unified [48:48] experience for our customers was always [48:50] a pipe dream unless hosts actually get [48:53] that vision. uh it really like none of [48:56] it works at all unless the hosts are in [48:58] first uh in the in the [49:00] >> in case the WordPress community will [49:01] have their their pitchforks out for that [49:04] host because they're providing too good [49:05] an experience that's not WordPress. [49:08] I mean, if you're if if I it's an [49:12] interesting um aspect that we didn't [49:15] talk about at all so far, but like if [49:16] you're talking about like hosting WAS [49:20] like WordPress as a service offerings on [49:23] Builtfast, that's a whole separate [49:25] episode that we're going to have to [49:26] bring you back for probably. [49:28] >> Yeah. Um, [49:29] >> yeah, the product we're building is [49:30] called I'm going to do that pitch, but [49:32] it it's built on the fact that Carl can [49:34] his his technology can scale infinitely [49:37] and then we can work really closely to [49:38] provide that experience and other hosts [49:40] can do it. [49:41] >> It's not it's not, you know, like we we [49:44] have the ability to scale, but that [49:46] regardless if you're putting this on a [49:47] box in the cloud on something else, it's [49:50] the the host has to want to work on on [49:54] making the experience better with the [49:55] developer, the plugin or whatever. 100%. [49:59] Cool. Cool. Well, uh, this has been [50:01] great. Um, really lively. I mean, I'm [50:04] gonna have a conversation with Carl [50:05] Alexander on. It's always going to be [50:07] lively. Always. Um, thank God for the [50:10] worm guy. Oh my gosh. Um, [50:14] >> save the show. [50:17] >> Let's do best advice. Uh we're going to [50:20] go around uh the circle here and the [50:22] question is what is your best advice for [50:25] advising a product owner uh on how to [50:29] provide excellent user experiences? Uh [50:33] Carl, you're up first. [50:35] >> Oh my goodness. I mean, I don't know if [50:37] I should I'm an expert on that, but I [50:39] really believe like what Zach said, like [50:42] I think what's kept me going over the [50:45] years is just having the human touch, [50:47] right? Like it's just like being in [50:50] being responsive like like um there's a [50:54] guy recently like uh Justin Walsh he [50:57] writes a thing but he was talking about [50:59] service in general in the west there's [51:02] like this whether you go to a hotel or a [51:05] restaurant like the bar now is like so [51:08] low like nobody just shows up and gives [51:10] you good service anymore like answering [51:14] an email on time like just anything. So [51:17] I was just like I just think that's like [51:20] a user expectation thing and the bar is [51:22] still low. So if you can clear that like [51:25] that's how I've gotten some customers is [51:27] just by being there and answering [51:28] questions you know. [51:30] >> Yeah that's awesome. I live in Germany [51:32] so I resonate with that uh criticism [51:35] probably a little bit more than the rest [51:37] of you honestly. Um Zach what about you? [51:41] What's your best advice? [51:43] Well, uh, as I mentioned, I think the [51:45] finding out what page builders your [51:47] users are using and make sure to support [51:50] them. That's one of our focuses for [51:52] Gravity Kit in 2026. Um, I also have [51:55] Zoom calls and my I make myself [51:57] available for people to schedule [51:58] consultation calls with me and I love to [52:00] see them using their own website and I [52:03] cringe every time I see a what other [52:05] things they have running and how [52:06] horrible it is and b how horrible [52:09] anything is that like our software isn't [52:12] perfect and it's so good to see our [52:15] customers using it in order to expose [52:16] that. So, make sure you're staying in [52:18] touch with your customers in that way. [52:20] And like Carl was saying about uh [52:21] support, um, one of the best things for [52:24] user experience, if somebody requests a [52:27] feature years ago and you implement it, [52:30] email them, no matter how long ago it [52:32] was, they will be so surprised and [52:34] thrilled. The the little moments of [52:36] delight, uh, is is where it's at in [52:40] terms of [52:40] >> I absolutely love that advice. Yeah. [52:42] >> Absolutely love it. [52:44] >> Yeah. [52:44] >> So, those are those are quick three. How [52:46] about uh how about you, Matt? [52:48] >> Yeah. Oh, we'll save you best for last. [52:50] Um, I'm gonna say that um user great [52:55] user experiences are born out of company [52:57] culture. You all have to actually [53:00] believe in great user experiences. Uh, [53:04] individually, each department, it can't [53:06] just be a marketing responsibility, [53:07] can't just be a CX responsibility, can't [53:09] just be a development responsibility. [53:12] Everybody has to believe in um great [53:15] customer experiences and be looking for [53:17] those opportunities all the time. Um and [53:20] not in terms of like well is this great [53:22] marketing or is this a great support [53:24] experience. You have to think about the [53:26] whole entire uh experience across the [53:29] whole uh customer uh journey. Um and [53:33] that only happens if if that's part of [53:35] everything you think about as as a team. [53:38] Um, so that's that's my best advice. [53:42] Think about it holistically from all the [53:44] angles. Paul, you're up. [53:47] >> Yeah, I'd say mine's two points. The the [53:49] first one being if you're a product [53:50] manager or someone building like reach [53:52] out to subject matter experts in the [53:54] area. I've I've never I've never been [53:56] turned down. If I reach out to somebody, [53:58] I say like, I'm really struggling with [53:59] this issue and I and I know you're [54:01] already solving it or you solved it in a [54:03] real smart way. Explain to me that. I've [54:05] literally never had somebody not. So I [54:07] think product owners, product managers [54:09] rarely leverage outside experience. Um [54:13] maybe it's because they want it to feel [54:14] like it's coming from them. I guess [54:16] that's it. Um but I would say le [54:17] leverage that. And then I would say get [54:19] really really comfortable with the [54:20] technology that's available today [54:22] because rapid prototyping real life [54:24] creation of a tool even if it's outside [54:27] of the tool you're building if you can [54:29] replicate what you're trying to build [54:30] through UX you know AIUX and U AI actual [54:35] building of those apps um putting [54:37] customers through real world experience [54:39] tells you so many more times faster [54:41] where they're going to run into a [54:42] culde-sac or dead end and um you just [54:45] you know you're going to shave weeks and [54:47] months months and sometimes sometimes [54:49] years off of your development time if [54:51] you can do do that with your users. One [54:54] of the cool things that we've been doing [54:55] recently and it's it was really [54:57] validating because it ended up creating [54:58] something exactly like we had already [55:00] designed through a lot of iteration was [55:02] explaining what our one of our apps one [55:05] of our plugins does and then uh in [55:08] detail and then saying to the to AI look [55:11] you know research all the other tools [55:12] that might do this come up with a [55:14] synthesized spec for how this might work [55:16] create a mockup based on that uh with [55:19] the different screens that are required [55:21] for the for the configuration and came [55:23] up with it pretty much exactly what we [55:25] had designed. Uh so like that's a great [55:28] way to validate what you're doing. Uh [55:30] >> yeah, [55:31] >> that's cool. That's a cool idea. [55:34] >> All right, folks. Well, this has been [55:35] great. Carl and Paul, thanks so much for [55:38] being here. Tell everybody where uh we [55:41] can find you online. [55:44] >> I'll go first. Uh I'm starting to go on [55:47] the X a bit more, so Twick Press on [55:50] there. Otherwise, uh, LinkedIn or post [55:54] status or my own emir discord. Uh, I'm [55:59] I'm all around the interwebs. Uh, [56:01] >> and how do you spell amir, Carl? [56:05] >> Why am I [56:07] r [56:11] >> How about you? [56:12] >> Uh, you find me on LinkedIn, uh, [56:14] primarily. That's also where our main [56:16] site is for stuff. Uh, and, uh, reach [56:19] out to us that way. Okay. And then [56:20] builtfast.com [56:22] uh is our website and check it out and [56:24] uh reach out to us if you have any [56:25] questions. paulbillfast.com if you want [56:27] to reach me directly. [56:29] >> Love it. [56:30] >> And if you're enjoying our shows uh [56:32] please do us a favor and hit that [56:33] subscribe button on YouTube. It's [56:35] totally free and it does a great service [56:37] to the show. So please uh we're trying [56:39] to get to 10,000 likes and you can be [56:41] one of those. Please uh like and [56:42] subscribe. And special thanks again to [56:44] Fremius for being a WP product talk uh [56:48] sponsor. [56:49] >> And next week folks, we have a special [56:51] friend of mine on the show who is now [56:54] one of the team leads for the core AI [56:56] team at Automatic. Uh Jason Adams. He's [56:59] going to join us to talk about the [57:00] WordPress plugins and themes and how [57:02] they can leverage the work that the core [57:05] AI team is doing right now already u and [57:08] uh all the things they're doing to bring [57:10] MCP and AI and the abilities API into [57:12] WordPress core and what plug-in uh [57:15] owners can do with those things. Uh [57:17] we'll talk all about those stuff and I [57:19] think it's going to be really practical [57:21] uh really useful. So mark your calendars [57:23] for next week. And uh everybody have a [57:26] good one and we will see you next time.