Boagworld: UX, Design Leadership, Marketing & Conversion Optimization cover art

Boagworld: UX, Design Leadership, Marketing & Conversion Optimization

Boagworld: UX, Design Leadership, Marketing & Conversion Optimization

By: Paul Boag Marcus Lillington
Listen for free

Boagworld: The podcast where digital best practices meets a terrible sense of humor! Join us for a relaxed chat about all things digital design. We dish out practical advice and industry insights, all wrapped up in friendly conversation. Whether you're looking to improve your user experience, boost your conversion or be a better design lead, we've got something for you. With over 400 episodes, we're like the cool grandads of web design podcasts – experienced, slightly inappropriate, but always entertaining. So grab a drink, get comfy, and join us for an entertaining journey through the life of a digital professional.Boagworks Ltd Economics
Episodes
  • From Doer to Director, Getting Value From AI
    Jun 16 2026
    This month we dig into whether Claude Design is any good, why so many people feel like AI is costing them time rather than saving it, and what it really means to stop being a doer and start being a director. Along the way we wander into the loss of craft, the ethics of AI, and a joke so niche it needs its own history lesson. App of the Month Claude Design is the tool that grabbed our attention this month. It builds out designs for you, and it is genuinely impressive. We used it to rebuild the website for a small UK charity that funds children's education in India, going from nothing to a finished static HTML site in around eight hours, with Claude Design handling the design and Claude Code doing the build. Beyond the standard twenty pounds a month subscription, it cost roughly fifty quid in extra credits, which for a small organization is a no-brainer. Claude design and code together allowed Paul to create a fully working website in less than 8 hours. It turns out it does more than websites. It builds presentations too, and exports them to PowerPoint or PDF for offline editing. We put together a fifty three slide deck for a client in about two hours, work that would normally have eaten the best part of four days. Here is what we liked. It works with design systems, you can import one from Figma, you can make manual edits without burning tokens, and you can select elements visually to tweak them. The things that hold it back are that you can't export back to Figma, there's no easy publish button, and the usage allowance vanishes in what feels like five minutes flat. When you hit the wall it cheerfully suggests you try again on Sunday, which is no use when you're mid project and have already forgotten what you were doing. One word of warning. If you don't guide it heavily, Claude Design has tells, like a recurring decorative bar under the hero section that serves no real purpose. Then again, every designer has a style you can spot, so we're not convinced that's the criticism people think it is. From Doer to Director A lot of people tell us AI isn't saving them time, it's costing them more of it. That confused us at first. How can a tool that turns four days of slide work into two hours possibly slow anyone down? The more we coached people through it, the clearer the answer became, and it has very little to do with the tools. It comes down to how organized you already are. If you're not fundamentally efficient in how you work, and especially if you've never had to delegate to other people, AI exposes that straight away. The people struggling most are the ones who still want to be doers. They want to be in the code, pushing pixels in Figma, or typing every word themselves. To get real value from AI you have to shift from that doer mindset to a director one. Be the conductor, not the violinist It reminded us of the moment in the Steve Jobs biopic where Wozniak asks Jobs what he actually does, given that Woz writes the code and builds the hardware. Jobs answers that he conducts the orchestra. Woz is the finest violinist in the room, but someone has to bring all the players together. That conductor role is exactly the shift most of us need to make. Running agents in parallel A real example from this month. Working on a client presentation, we had three things running at once. Notion AI was drafting the outline in one window. Claude Design was studying the client's website to build a matching design system in another. A third agent was drafting video transcripts for a separate project entirely. Three workstreams all moving at the same time, where you would once have plodded through them one after another. That is a genuinely hard skill to build. The people best placed for it are those with management experience, because they're used to handing work off and holding several threads in their head at once. If you've never worked that way, it can feel distressing, and there's even a name for where it leads, which our reader of the month gets into. The micromanaging trap There's a design leadership parallel too. Talented designers get promoted, then can't resist sneaking back into Figma to do the work themselves. The same thing happens with AI. The agent produces something perfectly good, but it isn't quite what was in your head, so you fiddle and fiddle and fiddle, burning the very time you were meant to save. The upside is that you can't hurt an AI's feelings, so just say "no, that's not it" and move on. Get organized first The fix is unglamorous. Get organized before the agents fully take over. Build the digital playbooks, SOPs and policies we keep banging on about, so the AI already knows how you work and gets it right first time.Keep your knowledge in one place it can reference, so you're not repeating yourself endlessly.Run a task system it can see, and learn markdown while you're at it. It takes ten minutes and AI loves it. Tool or output, where's the joy? We didn't agree on all of this. Marcus prefers using ...
    Show More Show Less
    52 mins
  • AI Can Fix Your Broken Research Repository
    May 19 2026
    This week, Paul and Marcus dig into why traditional user research repositories fail almost everyone in an organization, and how AI is quietly changing the game. There's also an App of the Month pick that's a little too on-the-nose, some pointed Google bashing, and a sheep-based punchline. AI-Powered User Research Repositories The pattern in most organizations is depressingly familiar: user research gets done, a PowerPoint gets presented to stakeholders, everyone nods along or ignores it entirely, and then the research disappears. It might prompt some short-term action, but the knowledge evaporates. Nobody references it again six months later. The traditional solution has been to build a research repository: a central place to store everything from interviews and surveys to usability tests and diary studies. The problem is that these repositories almost always become what Paul generously describes as "dumping grounds." Dense folder structures, difficult navigation, and search tools that require you to already know what you're looking for make them practically unusable for anyone outside the UX team. And who ends up using them? Other UX professionals, the people who already understand the research anyway. Everyone else ignores them. AI changes this in three meaningful ways. First, it makes the initial build far less painful. You can throw everything at it, PDFs, old PowerPoints, interview transcripts, survey exports, and AI will structure and organize that material into something coherent. What used to be a daunting, months-long project becomes manageable. Second, it makes the repository accessible to people who aren't UX specialists. Instead of requiring a precise search query, a conversational interface lets anyone ask vague, natural questions. A product manager can ask "what do our users think about the checkout process?" and get a synthesized answer drawn from five different studies they never knew existed. That's a genuinely different kind of value. Third, and this is the part Paul finds most compelling, it can identify gaps in your research. When someone asks the repository a question and there's no relevant research to draw on, a well-configured AI won't fabricate an answer. It flags the gap and notifies the UX team that this is an area worth investigating. Over time, the questions people ask become a demand-driven research roadmap, shaped by what people in the organization actually need to know rather than what the UX team assumes they need. Marcus pushed back on the reliability question, which is fair given AI's well-documented habit of confidently inventing things. Paul's response: proper setup matters enormously. You instruct the AI explicitly not to fabricate, you add a quality gate that checks answers before they're returned, and you can even have it verify claims against source material. Even with pessimistic assumptions, say one in ten answers being wrong, that's still more useful than having nothing at all. And the failure mode is reassuring: if the AI can't find relevant research, it defaults to generic best practice rather than making something specific up about your users. Paul then connected this to something he's discussed before: AI-powered virtual personas. The repository feeds the persona generation. AI analyzes the accumulated research and builds queryable personas from it. Unlike static persona documents that go stale almost immediately, these update as new research is added. And here's the detail Paul is clearly delighted by: put a QR code on your printed persona posters. Scan it, and you're now having a conversation with a virtual version of that persona. Marcus had recently written about the value of physical personas on walls as simple reminders of who you're designing for, and this neatly bridges the physical and digital. The upshot: organizations that invest in an AI-powered research repository end up with something that prevents duplicate research, makes user insights accessible to everyone, identifies gaps in what's known, and gives the whole organization a quick way to gut-check decisions against actual user data. The reason more organizations aren't doing this, Paul notes with characteristic subtlety, is that UX teams are too small and too busy. "Hire me to do it" being the conclusion he arrived at, live on air. App of the Month Notion Paul's pick this month is Notion, which he acknowledges he's almost certainly recommended before, given that he runs his entire business on it and describes its potential failure as roughly equivalent to his own. The recommendation here is specific though: Notion as the platform for building AI-powered user research repositories. Two things make it well-suited for this. First, structural flexibility: you can organize a repository however your organization needs, and bring in almost any format of research artifact. Second, Notion has a powerful built-in AI agent that can reference, search, and synthesize across everything stored in it. ...
    Show More Show Less
    51 mins
  • AI Is Showing UI Designers the Door
    Apr 21 2026
    So this month Marcus and I get into a slightly uncomfortable question. If AI can knock out decent interfaces from a text prompt, where does that leave the people whose day job is opening Figma and making screens look nice? We start with Google Stitch, which has been getting a lot of attention lately. Then we zoom out into something I have become mildly obsessed with, which is building AI skills. Not prompt snippets, but reusable, documented processes that let you get consistent work out of AI without drowning it in context. App of the Month This month’s tool is Google Stitch (v2), Google’s AI UI generator. You describe what you want, it produces an interface, and you can do some light manual tweaking. It is not a full replacement for Figma. The editing controls are basic. The bigger story is what it represents. We are now at the point where a decent, usable UI can be generated fast enough that the real value shifts from "can you draw the screens" to "can you judge what good looks like." That is where experience, and yes, taste, starts to matter. If you want to compare approaches, I mentioned Figr again, which I still prefer for the quality of what it produces. Are UI Designers Becoming Vinyl? The question Stitch raises is not "can AI design interfaces". It clearly can. The question is what happens to the job market when "good enough" becomes cheap, fast, and widely available. I found myself telling 2 different clients recently that they could probably skip hiring a UI designer. They had tight budgets, tight timelines, and already had solid brand guidelines or a design system. In those situations, I could push the work through AI, iterate it a bit, and get something perfectly serviceable. That line of advice made me feel a bit grubby. Not because it was wrong for those clients, but because it hints at a bigger shift. My worry is that UI design becomes like vinyl records. Most people will not need it. A small number will care deeply and pay for it. The middle ground shrinks. Marcus made the important caveat here. Some designers will still be in demand because they bring something AI cannot easily fake. A distinctive visual style. Creative judgment. Brand thinking. The ability to make something feel like it came from a real point of view, not a model averaging the internet. We also talked about where UI designers can expand their value, because "I make pretty screens" is not a great long-term career plan. Broaden into UX and problem solving. Look past the interface and into the business problem, user needs, and research.Own the stuff between screens. AI still tends to think screen by screen. Humans are better at flows, journeys, and the messy reality of how people actually get from A to B.Lean into information architecture. For websites especially, the structure and content model matter as much as the visual design. We used a music analogy that will probably annoy some people, which makes it perfect. AI tools can generate "background" output that is fine for low-stakes use. They will not replace great musicians. But they will reduce the number of gigs available. AI Skills As a Career Asset After we finished terrifying UI designers, we moved on to something more useful. I think a lot of roles are going to need an AI toolkit. Not a handful of clever prompts, but a proper library of reusable skills. When I say "AI skills," I mean documented processes that an AI can follow reliably. Think SOPs you can run repeatedly, not prompt snippets you copy and paste. I now have around 60 skills in my library, and it is growing constantly. Outside of the Boagworld website, it might be the most valuable business asset I have. The reason is consistency and context management. AI can produce terrible output when you dump too much information on it at once. Skills let you break work into focused chunks and chain them. We talked about 3 levels of skills: Company-level skills Standard processes that keep things consistent. Proposals. Expense claims. Holiday booking. The sort of stuff that should not depend on one person remembering every step. Team or discipline skills For example, UX teams can create skills for personas, journey mapping, surveys, and top task analysis. That helps remove bottlenecks and lets colleagues do decent work without reinventing the wheel. Individual skills This is where it gets interesting for your career. These are the skills that capture how you do something, including all the weird little bits you have learned over the years. A key point here is that the value is not only in having the skill. It is in creating it. Writing down a process forces you to surface assumptions and explain what "good" looks like. We also got into AI agents. If you describe your skills well, an agent can chain them to complete bigger jobs. I gave a sales example where a meeting transcript can be turned into a CRM entry, follow-up tasks, company research, and a draft proposal with very little manual effort. That is ...
    Show More Show Less
    53 mins
adbl_web_anon_alc_button_suppression_t1
No reviews yet