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

About this listen

 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
  • Stop Firefighting: A Smarter Way to Prioritize UX Work

    Stop Firefighting: A Smarter Way to Prioritize UX Work
    Aug 21 2025
    One of the most important policies you can ever set for your UX team is how you prioritize work. Without it, you risk becoming a firefighter running from one blaze to another, driven by who shouts loudest or whose deadline is closest. That’s no way to deliver meaningful user experience.Most of us are outnumbered. There will always be more requests than we can handle. The only way to keep your head above water is to establish a clear, fair, and transparent prioritization process. That’s where digital triage and a scoring system come in.Why Prioritization MattersMany UX teams I encounter work on a “first come, first served” basis. Or worse, they work on whatever task has the loudest advocate or the scariest deadline. None of these methods are fair or effective. They waste energy on low-value projects and leave your most important work sidelined.You need a way to make sure your time goes into projects that matter most. That means having two lines of defense: digital triage and a prioritization backlog.Step One: Digital TriageTriage is your first filter. When a request lands on your desk, don’t dive straight in. Pause and ask a few key questions:Business alignment: Does this support core business objectives? If your company’s main goal this quarter is customer retention, a flashy microsite for a one-off campaign probably doesn’t make the cut.Audience: Does it affect a primary audience group or just a fringe one? Improving onboarding for new customers has more weight than polishing a tool used by a handful of internal staff.User need: Is this solving a real, pressing problem for users, or is it just someone’s nice-to-have idea?Feasibility: Is it realistic with the resources available, or will it swallow months of effort for limited gain?If a request fails on most of these, it doesn’t mean it disappears forever. It just doesn’t deserve your attention right now. Triage is about protecting your limited capacity from being drained by low-impact work.Step Two: Score and Build Your BacklogWhen a job comes in, score it immediately. This scoring system is your triage method and determines where each request sits in your backlog. I use four simple criteria, each ranked 1 to 5:Business alignment: 5 if it's central to strategy, 1 if it's unrelated.Effort required: 5 if trivial, 1 if it's huge.User group impact: 5 if it affects your core audience, 1 if it barely touches anyone.User need: 5 if it addresses a critical need, 1 if it's minor.Add up the scores, and you've got a clear view of where each project belongs in your prioritized backlog.As new jobs come in, they are assessed and then slotted into the appropriate place in the backlog.An ExampleSay marketing asks for a new landing page. You score it like this:Business alignment: 4 (supports acquisition, a current business goal)Effort required: 3 (will take some design and dev time, but manageable)User group impact: 2 (only affects one segment, not core users)User need: 3 (helps users, but not a burning problem)That gives a total of 12 out of 20. Useful, but not top priority. It slots into your backlog beneath projects with higher scores.The beauty of this system is that you’re not saying “no.” You’re simply placing requests in order. Lower-value work naturally slides to the bottom of the pile.Managing the BacklogKeep your backlog visible. Maintain separate lists if you handle both major projects and small “business as usual” work.I recommend most digital teams are split into two work streams. One focuses on “business as usual” (optimization), the other on larger, future focused projects (innovation.Whenever a new request comes in, score it and slot it in transparently. This takes the politics out of the process. People can see for themselves why their project sits where it does.Over time, you’ll find the backlog itself becomes a communication tool. It helps you show leadership how much demand there is and how you’re focusing on the projects that deliver the most value.Handling PushbackOf course, not everyone will like where their project lands. Here’s how to handle it and some of the common objections you’ll hear:Urgent queue-jumpers: Make it policy that deadlines are agreed with you upfront. If someone comes late in the process, they may need to go to an external supplier. A common objection here is: “But what if everything feels urgent?” The truth is, not everything can be urgent. If everything is top priority, nothing really is. Triage forces tough but necessary trade-offs.Disagreements over scoring: Define an escalation path. If stakeholders challenge your scoring, who makes the final call? Having this agreed in advance avoids endless debates.Some worry: “Doesn’t scoring everything slow us down?” In practice, scoring is quick, just minutes of work that save weeks of wasted effort on the wrong priorities.Stakeholders ignoring the backlog: Digital Triage needs to be approved as an organizational policy, not your...
    Show More Show Less
    7 mins
  • Why Your UX Needs a Trust Audit

    Why Your UX Needs a Trust Audit
    Aug 19 2025
    In this episode, we look at why trust is key to good UX, especially with scams, deepfakes, and AI blurring the line between helpful and deceptive. We also ask if emotion-reading apps are helpful or just unsettling, and explore the tricky process of turning services into products. Plus, we discuss a framework from Nielsen Norman Group, tackle a listener's question on productization, and end with Marcus's joke.App of the WeekCheck out Emotion Sense Pro—a Chrome extension that analyzes micro‑expressions and emotional tone in real time during Google Meet calls, while keeping all data safely on your device. It's privacy-first, insightful, and a bit unsettling. But if you're moderating user tests, hosting webinars, or running interviews, it gives a useful look into unseen emotional cues.Topic of the Week: Trust as Your UX SuperpowerThis week's topic dives into why trust is absolutely essential in today's digital landscape. Here's a summary of what was discussed, but we encourage you to listen to the whole show for more detailed insights.We're convinced trust isn't optional, it's foundational. Amid a haze of misinformation, broken customer promises, slick AI-generated content, and user fatigue, building trust isn't just ethical, it's strategic.Why Trust Is Harder to Earn (But More Rewarding)Trust isn't automatic anymore. Big brands used to get the benefit of the doubt. Now users are skeptical. Scams and data breaches have made people cautious. Small problems like unfamiliar checkout pages, strange wording, or awkward user flows make people suspicious.UX Choices That Build (or Break) TrustKeep your visuals and interface consistent so users don't have to work hard. When people get confused, they put their guard up. Think about clicking through to a payment page with no familiar branding. That tiny moment can kill trust. Messages like "Only 3 left in stock" can seem manipulative if users don't trust you yet.Speak Like a HumanTalking about "the company" instead of "we" creates distance. Use normal conversation with "you" and "we" instead of "students" or "customers." Skip the marketing language. And remember that if your photos don't show people like your users, they might leave without saying why.Trust-Building in ActionHere are concrete steps that showcase trust-building in real-world scenarios. Implementing these practices can transform how users perceive and interact with your digital experiences:Audit for trust breakpoints. Look for spots where your UI might confuse users.Loop in legal early. This stops compliance from ruining your tone with last-minute jargon.Test trust directly. Ask "Would you feel comfortable sharing your data here?" during testing.Use authentic social proof. Link testimonials to sources, use third-party reviews. Even better? Simple, unpolished video testimonials.Prioritize clarity over cleverness. Skip the buzzwords.Make human support obvious. This is one of the strongest trust signals you can offer.Trust runs through every part of your experience. Get it right and it becomes your biggest advantage.Read of the WeekThis week's read is "Hierarchy of Trust: The 5 Experiential Levels of Commitment" by Nielsen Norman Group. They outline a trust pyramid:Baseline trust. Can the site meet my needs?Interest & preference. Is this better than alternatives?Trust with personal info. Worth registering?Trust with sensitive data. Can I trust you with payments?Long-term commitment. Will I come back?Main point? Don't ask for level-3 or level-4 commitments before earning levels 1 and 2. Users leave when you push for sign-ups or newsletter pop-ups too early. Build trust in stages.Listener Question of the Week"Is productizing my services a good idea, and if so, how should I approach it?It depends. Productisation can add clarity but might limit your value by putting your service in a rigid box. We find it works better to focus on outcomes rather than fixed processes.If you do want to productise:Focus on the outcome, not the deliverable. Example: "Conversion rate strategy" not "5 interviews and wireframes."Stay flexible. Your process should change as the project develops.Don't use fixed pricing that punishes change.Think about your service's value, not just features.Most of us will get further with a custom toolkit and clear outcomes than a one-size-fits-all "product."Marcus’s Joke“I removed the shell from my racing snail. I thought it would make it faster, but if anything, it’s more sluggish.” Find The Latest Show Notes
    Show More Show Less
    59 mins
  • Scaling UX in a Decentralized World: Inside Oxford

    Scaling UX in a Decentralized World: Inside Oxford
    Jul 22 2025
    In this episode, we chat with Sarah Zama from the University of Oxford about how she's helping to influence UX across one of the most complex and decentralized organizations in the world.We explore how she built a UX center of excellence almost from scratch, how the team is transforming culture through coaching and community, and what it takes to push UX forward in a challenging environment. There's also a digression into Apple's questionable design choices, a fantastic app recommendation, and of course, Marcus' joke.App Of The WeekThis week’s app recommendation is Zuko Form Analytics. It’s an incredibly helpful tool for anyone involved in conversion rate optimization or form design.Zuko tracks detailed interactions with every field in a form—like how long someone spends in a field, where they drop off, and what fields trigger abandonment.You get session-level insights, and it all works via a simple JavaScript snippet. There's a free tier to get started (up to 1,000 sessions), and pricing starts around £40/month for 5,000 tracked sessions. It’s the kind of tool we wish we’d known about sooner.Topic Of The Week: Building UX Capability at Oxford UniversityWe were thrilled to be joined by Sarah Zama, UX Lead at the University of Oxford, to discuss a journey we’ve had the privilege of being part of: building a UX center of excellence in one of the most decentralized institutions in the world.Getting Started With Limited ResourcesPaul originally worked with a small team at Oxford to create the business case for a UX team, ultimately recommending a center of excellence model rather than a centralized tactical team.Why? Because hiring enough UXers to match developer headcount across such a massive organization was never going to be viable. Instead, a small, strategic team could focus on enabling others.Sarah took that vision and ran with it. She started with a written plan—not just a strategy that collects dust but a living, practical document with measurable outcomes. She quickly assembled a lean team, brought in an existing accessibility lead, and even secured a six-month secondee to help with projects and spread good UX practice further into the organization.A Consultative, Empowering ApproachThe Oxford UX team doesn’t do UX for people. Instead, they help others do UX better. Through consulting, coaching, training, and providing reusable assets (like a design system), the team makes itself useful across a broad landscape without getting dragged into execution.This consultative model includes:Workshops to support high-profile projectsGuest training sessions with external speakersCustom-built resources tailored to Oxford’s contextSupportive relationships with departments already doing good UXThey’ve also cleverly leveraged accessibility requirements as a wedge to introduce better UX thinking, combining compliance with best practices to gain traction.Growing a UX CulturePerhaps most impressively, Sarah and her team have focused on growing a UX culture through grassroots advocacy. They’ve built a UX Champions network that now includes over 150 people from across the university. This community shares knowledge, resources, and a passion for improving user experience, even when UX isn’t in their job title.It’s a smart way to scale. By empowering individuals and embedding UX thinking across departments, Sarah's team extends its reach far beyond what any centralized team could manage.The Frustrations and the WinsSarah admits the biggest challenge is visibility. Getting buy-in across such a large institution takes time and constant communication. There’s also the frustration that people still perceive UX as a cost or blocker rather than an enabler of success.But the wins are meaningful. A growing, skilled team. A network of passionate advocates. And projects where UX clearly moved the needle. Sarah credits much of the team’s progress to strong collaboration, openness to learning, and sheer persistence. It’s a long game, but one that’s already paying off.You can follow Sarah’s team and explore their resources at staff.admin.ox.ac.uk/ux. They welcome feedback, iteration, and anyone who wants to borrow from their growing UX playbook.Read Of The WeekThis episode’s recommended read is The Leadership Dilemma, an article Paul wrote for Smashing Magazine. It reflects on the exact challenges Oxford faced: how do you scale UX influence when your team is too small to do all the work? The article walks through a strategic approach to UX leadership that empowers others, shifts the organizational mindset, and creates lasting change.If you’re trying to build UX maturity in a large or slow-moving organization, this is worth your time.Question Of The WeekThis week’s question wasn’t submitted via email but came up naturally during the show: "What does a typical week look like for a small UX team in a large organization?"Sarah’s answer? There’s no such thing as a typical week. Her team ...
    Show More Show Less
    56 mins
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.