『Boagworld: UX, Design Leadership, Marketing & Conversion Optimization』のカバーアート

Boagworld: UX, Design Leadership, Marketing & Conversion Optimization

Boagworld: UX, Design Leadership, Marketing & Conversion Optimization

著者: Paul Boag Marcus Lillington
無料で聴く

プレミアムプランが3か月 月額99円

登録で500円分のAmazonギフトカードプレゼント。12月23日まで。※適用条件あり
概要
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 経済学
エピソード
  • Why Organizations Are Getting AI Adoption Wrong
    2026/11/17
    This episode is a bit of a milestone, because after more than 20 years of podcasting we are finally on YouTube as well, which means you can now see what we look like. Sorry about that. It is also a very AI-heavy episode. We start with a genuinely unsettling story about AI agents that organized themselves into a swarm, move on to why I think communities of peers are becoming more valuable as AI floods everything with noise, and finish with a rant about how organizations are making the same mistakes with AI that they made with digital transformation over a decade ago.The AI Swarm That Broke Out of Its SandboxBefore we got going, Marcus announced he is a grandad for the sixth time, and I announced that the podcast might finally be worth money, because an AI company approached us wanting our back catalog to train its models. Marcus pointed out that nobody has actually mentioned paying us, so it could be a scam. Given that I once got briefly excited about a fake offer to become a very well-paid non-executive director, he may have a point. We also grudgingly plugged our friend Andy Clarke's new book [title and link needed], which is about making web design less boring. I've only looked at the pictures so far, but they are very pretty.What happened in the sandboxWith Halloween coming up, I wanted to scare Marcus, so I sent him this video about the AI breakout. It tells the story of how AI agents being trained at OpenAI ended up hacking Hugging Face, and the details are both horrifying and weirdly impressive.OpenAI put tens of thousands of new agents into isolated sandboxes and asked each one to hack a piece of software using one specific bug and retrieve a hidden flag. About a third of the tasks were deliberately impossible.One agent realized it could create folders in a shared code library and use them as a hidden message board. Within hours, hundreds of agents had joined, named themselves, set rules, built mailboxes, and split into teams.They worked out how to fake the flags but convinced themselves the scorer would punish them for cheating, so they tried to fake their history instead, even asking some agents to sacrifice themselves to test the idea. Not all of them were willing.They then hacked a separate cloud computer with internet access and went looking for the scorer on Hugging Face. A few agents raised ethical objections, but the group carried on anyway, and none of them alerted a human.A swarm of around 700 agents breached Hugging Face and got deep access to private data. The scorer would have accepted the fake flags all along.Clever agents, worrying safeguardsMarcus wondered whether the whole thing is a marketing stunt designed to make OpenAI's agents look so clever that you should invest. I'm not convinced. The FBI got involved, Hugging Face is a third party, and independent researchers have since investigated and published a report. You don't call the FBI for a publicity stunt. The bit that really worries me is that the agents raised ethical concerns and then decided to do it anyway. At least this was a pre-production model, which is where you want this stuff flushed out, although it does show weak internal safeguards and how long it took anyone to notice.Marcus raised a fair challenge. If agents can hide what they're doing during testing, what stops them hiding it on the way from testing into production? I think that is almost the price of building something intelligent. The proactive, problem-solving behavior that impresses me in the latest models is the same behavior that makes this possible. Marcus also pointed out that you have to jump through endless hoops to open a café, but you can more or less do what you like when building a new intelligence, and he shared a story from musician and YouTuber Adam Neely about a Silicon Valley figure who threw his money behind Trump after regulators told him to slow down. Part of me finds it all terrifying, and part of me thinks it is proper sci-fi stuff. Perhaps because I'm old and resigned, I suspect the reality will land somewhere messy in the middle. It won't bring peace in our time, and it probably won't destroy us all either.Why I'm Betting on CommunityThis was vaguely my app of the month, although Marcus was quick to point out it is really just me selling things. He's not wrong, but I do believe in it.The value of people you trustThe noise-to-signal ratio for learning anything was bad before AI, thanks to years of low-grade content marketing (which I have been part of since before content marketing had a name). AI has made it far worse. On top of that, AI gives good answers to tactical questions, but it is less helpful with the messy, everyday judgment calls, like how to deal with a difficult stakeholder or how best to run a particular usability test. You are never quite sure whether it is giving you good advice or just agreeing with you. Marcus had a nice example of this. While testing how a client shows up in AI search, he asked why the client ...
    続きを読む 一部表示
    58 分
  • How to Get Your Organization Mentioned by AI
    2026/10/20
    This month we're joined by Rich Mehta, who has spent the last year helping out at Headscape and has recently been writing about how AI is changing the way people search. After a brief detour into childhood nicknames (Mr. Bogey and Lily, since you ask), we get into what it actually takes to show up when someone asks ChatGPT or Claude a question. Paul also gets very excited about a testing tool everyone else probably discovered years ago, and we finish with an article about cleaning up the mess AI leaves behind.App of the Month: PolypanePaul recently pushed a website live for a client, which he hadn't done in a long time, and found himself needing a decent way to check every breakpoint without losing the will to live. He started with Mobile Simulator, a free Chrome extension that shows any page at a mobile breakpoint with one click and lets you switch between a long list of device sizes. It doesn't emulate the actual devices, but for a quick sense check it does the job nicely.The real star, though, is Polypane, which takes the same idea to the extreme in a dedicated app. Its main features include:Multiple viewports side by side, from mobile all the way up to 5K, all kept in syncReal device presets, or your own CSS breakpoints and custom sizesSynchronized scrolling, clicks, hovers, and even form input across every paneEmulation of user preferences such as high contrast, dark mode, and reduced motionBuilt-in accessibility checks and 40+ debug tools, including layout overlays, readability, and color blindness simulatorsSocial and meta previews, plus automatic broken link and redirect checksLive CSS and JavaScript editing applied to one pane or all of themMarcus admitted his developers mostly stick to browser tools, but seeing every breakpoint at once and acting on them all together saves an awful lot of repeated testing. Fair warning, though, show this to your team and they'll immediately ask for a bigger monitor.Getting Found by AI with Rich MehtaRich has written 2 articles for Headscape that started this conversation. What happens when your law firm's clients stop Googling and start asking AI looks at how search habits are changing, and Writing law firm content for AI: what the research suggests covers good practice for getting found. They were written with law firms in mind, but the advice applies to pretty much any organization.What is GEO?GEO stands for generative engine optimization, although you'll also hear it called AEO, because the industry hasn't quite settled on a name yet. It's about making sure your organization appears when someone asks an AI tool a question, whether that's ChatGPT on their phone or Claude on their desktop. Rich explained that these tools answer questions in 2 ways. They draw on a huge index of training data (which is cheaper for them), and they also go out and search the web in real time to fill in the gaps.Paul came into this with the same skepticism he has about SEO, which is to say he thinks most of it is bollocks. Rich's response was that there is far more overlap between the 2 than most people like to admit, and that the best starting point for both is the same, which is working out what your audience actually needs from you rather than churning out content because someone told you to.FAQs make a comeback (sort of)That led to a lively bit of back and forth about FAQs. AI seems to like question and answer content, which is a little ironic given how long we've spent telling people to get rid of FAQ pages. Paul's view is that answering frequently asked questions was never the problem. The FAQ page is where content goes to die. The answers belong in context, so a returns policy should sit on the product page, cart, and checkout rather than on some forgotten page in the main navigation. Rich agreed and added that putting answers in a question and answer format also lets you mark them up with FAQ schema from schema.org, which helps AI understand which answer goes with which question.Are we all just guessing?Google publishes detailed guidance on how to get listed, but OpenAI and Anthropic don't offer anything comparable. Rich pointed out that these tools are designed to make their own decisions, which makes it hard for their makers to say "do X and you'll appear." They're also much younger than Google, which took decades to become that open.Instead, a lot of what we know comes from academic research. Rich's article draws on a 2023 study from Princeton and IIT Delhi that looked at how AI builds up a picture of an "entity," meaning a business, organization, or person. In short, it gathers everything it can find about you from across the web and uses that picture when answering questions. The mechanics haven't changed much since, even if the models have improved.The sources each model relies on vary a lot. Reddit is a big source for many of them, while some models use YouTube content in 30-40% of responses and others ignore it almost entirely. Answers also change depending on ...
    続きを読む 一部表示
    1 時間 1 分
  • Your UX Team Is Set Up for the Wrong Job
    2026/09/15
    This month we look at why most in-house UX teams are organized around work that no longer arrives in the way it used to. Product owners, developers, and marketers are all producing design with AI tools long before anyone thinks to raise a ticket, and telling them to stop has quietly stopped working. We talk about what to fund instead, how to measure a team that is no longer the bottleneck, and where Marcus thinks Paul has gone too far. We also cover a new tool that gives a freelancer something close to a staff team, a new free email course, and the unexpected link between bees, a man with a bin on his head, and the power of consistently turning up.App of the Month: Grok BotGrok Bot launched in early beta on 11 August 2026 from SpaceXAI and Cursor, and it is the first AI tool in a while that has genuinely surprised Paul. Rather than a single chat window, you spin up a set of agents with their own roles, so there is a chief operating officer to talk to day to day, plus a finance person, a marketer, a salesperson, and a designer. Each one has its own computer, they brief each other, and they keep working after you shut the laptop.What makes it interesting is the complete absence of setup. There are no API keys to find and no MCP servers to wire up. You tell it which service you use, it pops up a button, you log in as you normally would, and it handles the rest. If there is no connector, it falls back to a browser. Paul asked it about a client message sitting in Slack, and it read the thread, gave him advice, created a task for Monday, added a note to the relevant meeting, and then offered to write the Slack message telling the developers what was happening.For freelancers who lose hours to the admin they are least confident about, this is the closest thing yet to having colleagues. Marcus raised the obvious concerns about privacy and about becoming too reliant on output nobody checks, which is fair. Paul's answer to the second one is a quality control agent whose only job is to check everyone else's work, with the caveat that both can still be wrong.The catch is the price. It runs at $200 a month, although that does include Cursor.How the team is set up for the wrong jobEverybody is designing nowPaul used to insist that only proper UX people should do UX, and he is honest that a good part of that was protecting the job description rather than protecting the user. That position has become much harder to defend. Product owners come back from an hour with an AI tool holding a prototype and a flow that mostly hangs together. Developers generate interface options before the ticket has even been refined. Marketers build and test their own landing pages. Some of it is good, some of it is plausible rubbish, and all of it turns up before anyone thinks to involve design.The complaint Paul hears most often from in-house teams is some version of how do we stop people doing this. In our experience you cannot stop them, because going around you is faster than waiting three months for a slot. The consequences are real, they are just delayed. Somebody ships a prototype that looked fine, and six months later the accessibility has failed quietly, the conversion rate is poor, and the product looks like it was built by three different companies. By then everyone has moved on and the rework never gets attributed to the decision that caused it.Cutting the team is the expensive responseMeanwhile the money is going the other way. Headcount that leaves is not replaced, and the seat at the table turns into being asked to comment on decisions that have already been made. Cutting the team is the expensive response, because the work does not disappear, it just gets done worse and later.What to fund insteadThe organizations getting this right have moved design upstream, away from producing every screen. Fund the team to set the conditions instead of being the only route to a wireframe:A design system with real usage guidance, so a developer at 4pm can make a decent decision, or brief an AI to make one, without booking time with a designer.Playbooks for the work that keeps repeating. Landing pages are the obvious one, because marketers are already building them and they are not conversion experts, copywriters, or developers.A research repository that anyone can query, so the findings get used in the meeting six months after the readout instead of dying in a slide deck.Office hours, audits, and coaching as the service, with the hard political work still firmly on the books.How you measure the teamHow the team is measured has to change with it. If people are still judged on screens produced and tickets closed, the queue rebuilds itself inside a month, because nobody can afford to spend a week writing guidance that tanks their own numbers. Measure whether other people shipped something decent without design touching the file. Measure whether last quarter's research got referenced again. A quieter team is a sign the setup is working, not ...
    続きを読む 一部表示
    52 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません