<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Justyna Belkevic on Medium]]></title>
        <description><![CDATA[Stories by Justyna Belkevic on Medium]]></description>
        <link>https://medium.com/@justyna-belkevic?source=rss-7d0191b99a30------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rvUUfyjuv0jes9fApWMp7A.jpeg</url>
            <title>Stories by Justyna Belkevic on Medium</title>
            <link>https://medium.com/@justyna-belkevic?source=rss-7d0191b99a30------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 11:38:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justyna-belkevic/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Who wrote your last email?]]></title>
            <link>https://justyna-belkevic.medium.com/who-wrote-your-last-email-3e6d58f17501?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e6d58f17501</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[ethics]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 02:17:29 GMT</pubDate>
            <atom:updated>2026-11-04T02:17:29.809Z</atom:updated>
            <content:encoded><![CDATA[<p>Did you write the last email you sent? All of it, including the “Thanks so much, sounds great!” at the end? That question has given the Dutch prime minister a complicated autumn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nGJgC_uBBQ84CvPEywxjMA.png" /></figure><p>On 10 September, de Volkskrant ran 1,812 posts from Rob Jetten’s personal accounts and his party’s accounts through an AI detector. It flagged at least 232 as written by AI, and 68 of those were his own. His party, D66, confirmed that some posts had been written with AI and said they were “approved and adjusted by Rob Jetten himself”. Fair enough, you might think. Then, in a written answer to an MP on 29 September, Jetten said no AI had been used on his official accounts. On 8 October the newspaper came back with at least 5 more flagged posts, this time on exactly those accounts. The government’s information service said it “does not share the conclusion that the cited examples were generated entirely by AI”. Translation: partly, then.</p><p>Now, I’m not going to argue about whether a prime minister should write his own posts (he has a country to run). His own description of how he uses AI sounds pretty reasonable to me: “You put something in, you take something out, and you always check it.” What I keep coming back to, though, is the people reading those posts. If you followed him, you had no reason to doubt he wrote them himself, and you probably wouldn’t have found out if a newspaper hadn’t gone looking.</p><p>And to be fair, that’s exactly what these tools are for. They’re meant to sound like you, because nobody wants an email that sounds like a robot wrote it. So when the tool does its job well, the person reading thinks you wrote it. I don’t think anyone set out to fool anybody (the goal is to make the sender sound good, which is fair enough). However, when a friend reads “I’m so sorry, that sounds really tough”, she’s working out whether you care. If the button wrote that line and nothing says so, she’s working it out from words you didn’t actually write.</p><p>So let’s have a closer look at how these buttons got so good at sounding like you, and what happens when the person on the other side finds out.</p><h3>Three little buttons</h3><p>Remember the first time Gmail offered to answer for you? In May 2017 Gmail’s phone app got Smart Reply, which puts three short replies under an email, ready to send with one tap. Google said that in its Inbox app it was already behind 12% of replies sent from phones, so plenty of people were happy to let it answer for them. Which is fine (nobody is going to frame a “Sounds good!”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WBRVlL6gCsJ-tVka057Abg.png" /></figure><p>Then came Smart Compose, which finishes your sentences while you type. By April 2019 Google said it was saving people from typing over 1 billion characters a week on the web.</p><p>And in May 2025 Google announced personalised smart replies that pick up your tone and writing style from your old emails and your Google Drive files (with your permission). The reply is meant to sound like you, whether you’re the formal type or the chatty one.</p><p>Now, let’s imagine you get a reply from a colleague. It’s warm, and it remembers the thing you mentioned last month. Would you think twice? I wouldn’t.</p><h3>When the other person finds out</h3><p>In 2023 a team at Cornell tested what this does to a conversation. They had 219 pairs of people chat about a policy issue on a messaging app with smart replies built in. When people used the suggestions, the conversations became more efficient and more positive, and their partners rated them better. So far, so good for the button.</p><p>But when people thought their partner was using AI replies, they saw that partner as less cooperative and felt less close to them. As one of the researchers, Jess Hohenstein, put it, people “tend to evaluate you more negatively simply because they suspect that you’re using AI.”</p><p>Dating is where things go from okay to awkward pretty quickly. Using AI to write your messages to a match even has a name now: “chatfishing”. In July, The Next Web described a woman in Virginia whose Hinge match used phrases like “makes a playlist for every life moment energy”. When she asked him about it, he admitted he’d been using Claude. Another woman’s date confessed he’d been using ChatGPT, and her summary of meeting him was: “There was so much social awkwardness in person.” (I bet there was.)</p><p>And the apps? Hinge, Bumble and Match don’t ban AI-written messages, and Match Group’s CEO told Bloomberg “there’s not much we can do about that”. So people guess. A 2025 Norton survey found that 6 in 10 dating app users believe they’ve had at least one conversation written by AI (it’s the same story as in <a href="https://justyna-belkevic.medium.com/why-every-app-has-a-secret-manual-on-tiktok-b10dcab8b73d">Your app’s real manual is on TikTok</a>: when the product won’t tell people, they work it out themselves).</p><h3>The slop button</h3><p>Of course, sometimes the button doesn’t manage to sound like you at all. You know the posts I mean. LinkedIn has let Premium members ask AI to write their posts since at least 2024. In July, Originality.ai said its detector rated 81% of 5,000 public posts of at least 100 words as “likely AI” (they sell detectors, so take that with a pinch of salt. Then again, you’ve seen the feed).</p><p>On 30 July LinkedIn added a new option to the menu on posts: “Seems like AI slop” (yes, LinkedIn put the word slop in its own menu). In the same announcement, it took away its “enhance your post” button, which reworded posts with AI, and put in a proofreader that leaves “your voice intact”. So in one go, LinkedIn gave readers a button to report AI slop and took away one of the buttons that made it. By August the slop button had been used more than a million times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ke2pQmAj7cjwbzOc6Yn-iw.png" /></figure><p>This is where I put my detective hat on. Could LinkedIn have kept the rewrite button and simply labelled those posts as AI-written? Technically, sure. Would anyone have pressed a button that stamps “written by AI” on their post? I doubt it (would you?). LinkedIn’s Hari Srinivasan was careful to say that “AI and slop are not the same thing”, and I agree with him. Still, look at what LinkedIn kept: the AI that leaves your voice intact. And the person reading got one new tool out of all this: a button to complain with, which only helps when the AI has done a bad job.</p><h3>This is the ethics part</h3><p>Now, I don’t think every AI reply is a problem. Nobody is building a relationship on a “Sounds good!” about Friday drinks. But a message usually carries two things: what it says, and the fact that someone took the time to say it. Sometimes the second one is the whole point. Imagine your friend has just told you her dad is in hospital. “I’m so sorry, that sounds really tough” isn’t news to her. What she’s reading is that you stopped what you were doing to write it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YIswVNzqXjGGFWtlqJQPyQ.png" /></figure><p>We’ve already seen what happens when that part goes missing. In February 2023, after the shooting at Michigan State University, an office at Vanderbilt University sent students a message of support, and at the bottom, in small print, it said the text was a “paraphrase from OpenAI’s ChatGPT”. So they did tell people. It didn’t help. One student called it “disgusting”, the dean apologised to “all those who deserved better from us”, and two of the deans involved stepped back while the college looked into it. Telling people is the minimum. Some messages only count if you wrote them yourself.</p><p>So far I’ve been talking about the person reading. But the button changes the person sending too. In 2015, Google noticed that an early Smart Reply prototype had a “propensity to respond with ‘I love you’ to seemingly anything” (imagine your landlord’s face). The system was built to “generate likely responses”, and “I love you” is “super common”. Google fixed it by making replies fit the actual email rather than the most common ones. The newer tools even learn your tone from your old emails, but they still do the same basic thing: suggest the usual.</p><p>And “the usual” isn’t neutral. In 2023, Cornell researchers had more than 1,500 people write about whether social media is good for society, some with an assistant that had been set up to take one side. Those people were twice as likely to agree with it in writing, more likely to hold its opinion afterwards, and most never noticed it had one. “The process of co-writing doesn’t really feel like I’m being persuaded,” said one of the researchers, Mor Naaman.</p><p>In 2025, another Cornell team had people in India and the US write about their own culture, some with suggestions switched on. The Indian writers drifted towards the American style. Without AI, one wrote that they would “worship goddess Laxmi” and “pop crackers and eat sweets” for Diwali. With AI, another wrote that they would “eat traditional Indian breakfast items”. Nobody decided Diwali should sound like breakfast. That’s just what “usual” looks like when most of what the machine learned from was written by someone else.</p><p>That one hits close to home. English isn’t my first language, and my writing has a few odd phrases that are very much mine. And here’s the uncomfortable part: I often <em>want</em> the button to tidy them away. I’d love to sound perfect in English. So when it smooths a sentence, it feels like help, and I don’t notice that anything’s gone.</p><p>But it adds up. One tidy sentence is nothing. Remember the billion characters a week Smart Compose was filling in back in 2019? Every one of those was the button’s choice of words. Do that for years and the odd phrases stop showing up at all.</p><p>And that’s the biggest catch in “designed to sound like you”. Millions of us are pressing the same button and getting much the same suggestions, so our sentences drift towards each other. The Cornell study already saw Indian and American writing start to look alike. What makes a message yours is the part nobody else would write, like goddess Laxmi in that Diwali story. Give it long enough and we’ll all sound the same.</p><h3>What we can actually do</h3><p>First, the law, because it isn’t coming to the rescue. Since 2 August 2026 the EU’s AI Act has said that AI-written text “published with the purpose of informing the public on matters of public interest” must be disclosed, and a prime minister’s posts sound like exactly that. Then the very next sentence says the rule doesn’t apply when the text “has undergone a process of human review or editorial control” and someone holds editorial responsibility for it. So, as far as I can read it, Jetten’s “you always check it” is the exemption (how much checking counts as review, the law doesn’t say). And a reply to one person, your email or your Hinge chat, isn’t covered at all. Whether the person reading gets told is up to whoever designs the button.</p><p>I know how this goes in a design review. Nobody is going to vote for a label that makes their users’ messages look worse, and a big “Written by AI” stamp would do exactly that.</p><p>Pro Tip: think of “Sent from my iPhone”. That little line sat at the bottom of millions of emails for years, and plenty of people never deleted it. It told you something useful about how the message was written (on a phone, so forgive the typos) without making anyone look bad. A line like “Drafted with Gemini” could do the same job, as long as the person sending can add it with one tap and it doesn’t read like a confession.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uDHWGH0Mel3x5HX1Y_z2xg.png" /></figure><h3>The fourth step</h3><p>So, back to Rob Jetten and his three steps: you put something in, you take something out, and you always check it. I think that’s a perfectly decent way to use these tools (and yes, I’ve pressed the little sparkle button too). However, I’d add a fourth step, and you’re welcome to borrow it. If the person reading would want to know, tell them. One line at the bottom is enough, something like “drafted with AI, checked by me”. Will they like you a little less? Possibly, if the Cornell study is anything to go by. But at least they won’t have to read about it in the newspaper.</p><p><em>A note on how I wrote this article.</em> The idea, the argument and research are mine, and so is every decision about what stays in the article. Claude, an AI assistant, does a lot of drafting legwork. I spend hours with every piece in this series, this one included. I throw out the drafts that don’t sound like me and check every line before it goes to the world. So consider this paragraph my fourth step :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOWJnVA0nN5mUGmU7YtObg.png" /></figure><p><em>A series on AI and ethical design. Because we need to design what’s right.</em></p><p><em>Sources: </em><a href="https://nltimes.nl/2026/09/10/dutch-pm-rob-jetten-uses-ai-write-social-media-posts"><em>Dutch PM Rob Jetten uses AI to write social media posts, NL Times, 10 September 2026</em></a><em> · </em><a href="https://nltimes.nl/2026/10/08/pm-jetten-misinformed-parliament-using-ai-social-media-posts"><em>PM Jetten misinformed parliament about using AI, NL Times, 8 October 2026</em></a><em> · </em><a href="https://brusselssignal.eu/2026/10/dutch-pm-misinforms-parliament-over-ai-use/"><em>Dutch PM misinforms parliament over AI use, Brussels Signal, 8 October 2026</em></a><em> · </em><a href="https://blog.google/products/gmail/save-time-with-smart-reply-in-gmail/"><em>Save time with Smart Reply in Gmail, Google, 17 May 2017</em></a><em> · </em><a href="https://workspace.google.com/blog/product-announcements/15-years-and-counting-making-gmail-work-faster-and-smarter-for-businesses"><em>15 years and counting, Google Workspace, 1 April 2019</em></a><em> · </em><a href="https://techcrunch.com/2025/05/20/google-unveils-new-ai-features-coming-to-gmail-docs-and-vids"><em>Google unveils new AI features coming to Gmail, TechCrunch, 20 May 2025</em></a><em> · </em><a href="https://www.engadget.com/apps/personalized-ai-powered-smart-replies-are-coming-to-gmail-172422777.html"><em>Personalized AI-powered Smart Replies are coming to Gmail, Engadget, 20 May 2025</em></a><em> · </em><a href="https://news.cornell.edu/stories/2023/04/study-uncovers-social-cost-using-ai-conversations"><em>Study uncovers social cost of using AI in conversations, Cornell Chronicle, 4 April 2023</em></a><em> · </em><a href="https://thenextweb.com/news/chatfishing-ai-dating-apps-chatgpt-claude-tinder-hinge"><em>Chatfishing, The Next Web, 20 July 2026</em></a><em> · </em><a href="https://scientificamerican.com/article/the-rise-of-ai-chatfishing-in-online-dating-poses-a-modern-turing-test/"><em>The rise of AI chatfishing in online dating, Scientific American</em></a><em> · </em><a href="https://www.fastcompany.com/91237998/how-linkedin-opened-the-door-to-ai-slop"><em>How LinkedIn opened the door to AI slop, Fast Company, 3 December 2024</em></a><em> · </em><a href="https://originality.ai/blog/ai-content-published-linkedin"><em>AI content published on LinkedIn, Originality.ai, 30 July 2026</em></a><em> · </em><a href="https://assets.theregister.com/2026/07/30/202621/"><em>LinkedIn’s AI slop button, The Register, 30 July 2026</em></a><em> · </em><a href="https://engadget.com/2241857/linkedin-says-its-ai-slop-button-is-working"><em>LinkedIn says its AI slop button is working, Engadget, 21 August 2026</em></a><em> · </em><a href="https://searchenginejournal.com/eu-commission-article-50-ai-transparency-law-has-four-exemptions/584528"><em>Article 50 of the AI Act has four exemptions, Search Engine Journal, 3 August 2026</em></a><em> · </em><a href="https://netzstrategen.com/en/insights/ai-content-disclosure-rules/"><em>AI content disclosure rules, netzstrategen, 3 August 2026</em></a><em> · </em><a href="https://www.cbsnews.com/amp/news/vanderbilt-apology-chatgpt-generated-message-msu-shooting"><em>Vanderbilt apologizes for ChatGPT-generated message on MSU shooting, CBS News, 21 February 2023</em></a><em> · </em><a href="https://abc13.com/vanderbilt-university-chatgpt-openai-chat-gpt/12859921/"><em>Vanderbilt University apologizes after using ChatGPT to console students, ABC13, 22 February 2023</em></a><em> · </em><a href="https://gizmodo.com/ai-chatgpt-vanderbilt-michigan-state-shooting-apology-1850139417"><em>Vanderbilt apologizes for ChatGPT email, Gizmodo, 21 February 2023</em></a><em> · </em><a href="https://research.google/blog/computer-respond-to-this-email"><em>Computer, respond to this email, Google Research, 3 November 2015</em></a><em> · </em><a href="https://news.cornell.edu/stories/2023/05/writing-ai-help-can-shift-your-opinions"><em>Writing with AI help can shift your opinions, Cornell Chronicle, 15 May 2023</em></a><em> · </em><a href="https://news.cornell.edu/stories/2025/04/ai-suggestions-make-writing-more-generic-western"><em>AI suggestions make writing more generic, Western, Cornell Chronicle, 28 April 2025</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e6d58f17501" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every app got an AI button this year. Try finding the off switch.]]></title>
            <link>https://justyna-belkevic.medium.com/every-app-got-an-ai-button-this-year-try-finding-the-off-switch-de92748a8e80?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/de92748a8e80</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ethical-ai]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ethical-ux-design]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Fri, 16 Oct 2026 06:23:38 GMT</pubDate>
            <atom:updated>2026-10-16T06:23:38.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvaj1vjk1Y9VZxSku4VNBQ.png" /></figure><p>If you pay for Microsoft 365, you probably remember <strong>the</strong> email. January 2025: Copilot is now included, and the price is going up, about three dollars a month (42% a year in the UK, 45% in Australia). You could keep your old plan without the AI, the email said, for a limited time. It did not say where.</p><p>So people went looking. Settings? No. The plans page? No. The way to find it, it turned out, was to click Cancel Subscription. Somewhere inside the flow whose whole job is to talk you out of leaving, between “are you sure?” and “here is what you’ll lose”, a plan called <em>Microsoft 365 Classic</em> appeared: same product, old price, no Copilot. It had been there the whole time, filed under the one button nobody presses by accident.</p><p>It took a regulator to find it. In October 2025 Australia’s consumer watchdog sued Microsoft on behalf of 2.7 million people, and I love how plainly the complaint puts it: the only way to get the cheaper plan “was to begin the process of cancelling their subscription.” Translation: to say no, pretend to leave. A month later Microsoft said it had “fallen short of our standards” and offered refunds, which, in corporate, is a yes.</p><p>Now, I don’t think anyone at Microsoft sat down to hide a plan. I think Copilot was the thing the company was proud of, the Classic plan was the awkward exception, and the awkward exception went where awkward exceptions usually go: behind the last door, next to the mop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dPgSZZMuzUv4hfUqNha1RQ.png" /></figure><p>And that, more or less, happened to all of us this year. Meta put an AI button in WhatsApp. Google put one in Gmail. Apple switched its one on while you were still choosing a wallpaper. Some of it is useful (I use some of it). However, try to find the off switch and you will find what the Australians found: either it isn’t there, or it is somewhere you would never think to look.</p><p>So let’s have a closer look at the off switch: who decided you’d have the feature, where they put the way out, and what it tells you about a product when saying no takes more clicks than saying yes. I’ll keep score as we go.</p><h3>The blue circle</h3><p>In March 2025 a small blue circle appeared in WhatsApp for everyone in Europe, 41 countries at once. It was Meta AI, and Meta’s announcement was cheerful about it: just look for the new icon. People looked for something else first. Where do I turn it off?</p><p>There was no setting. There still isn’t, as far as I can find. The closest you get is a per-chat option that keeps the assistant out of one conversation at a time, which is a bit like being allowed to lock one room. Meta’s position was that the feature is optional, in the sense that a doorbell is optional: you don’t have to press it, but it’s on your door now. Its own help page offered advice you don’t expect from the company that built the thing: don’t send Meta AI information you don’t want it to know. A European privacy group called the unremovable button a clear breach of the duty to build privacy in by design, and a member of the European Parliament asked whether it was legal at all. Good question. Still open.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6LceWIJwIy9ch1T5XPWCmQ.png" /></figure><p>This is where I put my detective hat on. Could they have forgotten the off switch? Unlikely. WhatsApp has a setting for almost everything, down to who can see when you were last online. Could it have been hard to build? Also no. The per-chat option proves the app can keep the assistant out of a conversation, so keeping it out of all of them is one more checkbox. Did they not think about what people might tell it? They did, hence the help page. So the switch was not forgotten, not difficult and not an oversight, which leaves one explanation: it was left out <em>on purpose</em>. Meta wanted the assistant to feel like the camera button: always there, and nobody has ever asked for a setting to remove the camera. Fair enough, if the two were alike. They aren’t. Point the camera at your lunch and that is the end of it. Tell the assistant about your lunch, your landlord and your blood test, and all of that is now sitting on a Meta server, which is a slightly different arrangement.</p><p>Off switch scoreboard: Meta, 0 points.</p><h3>Three billion inboxes</h3><p>Google took a cleverer route, and I say cleverer with respect, because most products are going to copy it.</p><p>In January 2026 Gmail announced that its AI summaries, the little overview at the top of a long thread, were rolling out to everyone, at no cost, three billion inboxes. On by default. There is an off switch, which already puts Google ahead of WhatsApp. But it is not an AI switch. It is the “smart features” switch, which has been in Gmail for years, and turning it off also removes the things you actually like: the inbox tabs that keep promotions out of your way, the calendar events that appear from your flight confirmation, the package tracking. Want to lose the AI summary? Say goodbye to your Primary tab too. Hope you like promotions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2IK3PKh1JJFQe0kUkNsNbw.png" /></figure><p>Detective hat again. Is this hiding the switch? No, it is right there in Settings. So what is it? Look at what the switch is attached to. One flick turns off the summary, the tabs, the calendar events and the tracking, all things people would notice losing. That is not a hidden switch. That is a switch with a price on it. And here is the second clue, which settles it: in the EU, the UK, Japan and Switzerland, where the rules on defaults are stricter, smart features start off and stay off until you turn them on. Everywhere else they start on. Same product, same team, same switch, two defaults, and the line between them runs exactly along the border where the law gets strict. You don’t draw that line by accident. That is a company that knows precisely what a default is worth, well enough to use two.</p><p>Scoreboard: Google, half a point. There is a switch. It just comes with a bill.</p><h3>The one that did it properly-ish</h3><p>Now, is it even possible to ship an AI feature with a proper off switch? Let’s be fair and look at the one company that did. Apple Intelligence began as opt-in; when it arrived in late 2024 you had to go and turn it on. In January 2025 Apple flipped the default, and now it switches itself on while you set up a new phone. You can disagree with that (I do). But look at what Apple kept when it changed its mind: the switch. It is in Settings, it is called Apple Intelligence, it is one tap, and it takes nothing else with it. No Primary tab held hostage, no detour through Cancel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UQUMVxsWiZ9sL3qjwbsYpw.png" /></figure><p>And what happened to Apple for being so reasonable? Nothing. Nobody sued, most people (I suspect) never touch the switch, and the feature is on for everyone who didn’t mind. So a findable switch costs a company nothing, which is worth remembering the next time someone in a meeting tells you it’s complicated.</p><p>Scoreboard: Apple, 1 point.</p><h3>Zoom out</h3><p>Long story short: four of the biggest companies in the world put an AI into something private of yours this year, and only one of them put the way out where you would look for it. Now, let’s not pretend these are four separate accidents. Put the stories next to each other and the recipe is the same every time: make the AI part of the product, switch it on for everyone, put the way out somewhere that costs something, and make an exception wherever a regulator happens to be looking.</p><p>Think about what that adds up to. In twelve months, three billion inboxes, every WhatsApp in Europe and every new iPhone got an AI that reads something of yours. How many of those people were asked first, with a real yes or no on the screen? I make it roughly <em>none</em>. That is a big change in what our software is allowed to read, and it arrived the way updates arrive: while you were doing something else.</p><p>Does it matter, if most people would never touch the switch anyway? I think it does, and here is why. Every hidden switch is a small loan taken out against trust. One is nothing. But the whole industry took them out in the same year, and loans like that come due: as a lawsuit in Australia, a privacy complaint in Europe, a law that spells out where the switch has to go (more on that in a minute), or simply the day you find out what the summary was reading and never quite believe the app again. I call this Trust Debt: the cost of a pattern that works today and pays out later in churn, regulation or headlines. And the silly part is that a findable switch would have cost nothing. Apple shipped one and nothing happened. The companies that hid theirs saved almost nothing and borrowed the maximum, which is not a strategy so much as a habit.</p><h3>This is the ethics part</h3><p>So where is the ethical design in all this? Not in a workshop, and not on the poster of principles in the kitchen next to the one about washing your mug. It is in the setting, and in two questions about it: does the person on the other side of the screen get a real choice, and how hard did you make it to use? Microsoft, Meta and Google all have ethics teams. I’d bet none of them designed the Cancel flow. Someone on a product team did, probably in an afternoon, and that afternoon was ethical design whether anyone called it that or not.</p><p>The regulators have noticed too, in the way regulators notice things: in writing, with article numbers. In <a href="https://justyna-belkevic.medium.com/">the first piece of this series</a> I wrote about the laws that make a chatbot admit it is a chatbot. The off switch is the next chapter. Europe’s Digital Services Act already names default settings that are “very difficult to change” as one of the things it doesn’t like. The Digital Fairness Act, which the Commission is expected to put on the table this November, goes after dark patterns of exactly this shape. When Brussels has to write down where the off switch goes, you know enough products have put it somewhere silly.</p><h3>What we can actually do</h3><p>Let’s be honest about the room. The default is not the designer’s decision. Somebody above you has an adoption number for the AI feature, the company has spent a great deal of money on it, and “off by default” is a sentence that loses that meeting every time. I have sat in enough of those meetings to know. If my advice were “fight the default”, it would be good advice for someone with a different job.</p><p>Pro Tip: don’t fight the default. Fight the trap. Default-on with an honest switch is a position the business can live with (see Apple, above, still in business). Asking for the switch to be findable, named and free of penalties is a small ask, and almost impossible to argue against out loud. Try it. Trust me, nobody in a review wants to be the person who says “I’d prefer they couldn’t find it.”</p><p>Then make the switch earn its keep. An off switch that nobody uses is the best evidence your feature will ever get: people were free to leave and stayed. An off switch that lots of people use is a number, and a number is the only thing that beats “adoption” in the next review. Either way you win. Propose it as research, because it is. And if you need a business case on top, borrow the regulators’: Microsoft’s hidden plan cost it a lawsuit, an apology and refunds to 2.7 million people, and LinkedIn’s default-on toggle got a call from the UK regulator within days. A findable switch is the cheapest insurance a product can buy, and you can say so in exactly those words.</p><h3>Back to the email</h3><p>So here is my new habit, and you’re welcome to borrow it. The next time an email tells me a feature is now included, I’m going to look for the off switch before I try the feature. Not because I’ll turn it off (I probably won’t). Because where they put it tells me how much they expected me to say no.</p><p>If the switch sits right next to the feature, they expected some people to say no, and they were fine with it. If it is buried under something like “smart features”, they expected it too, but hoped I wouldn’t go looking. And if the only way to say no is to click Cancel, well. I’ll know who to write about next.</p><p><em>A series on AI and ethical design. Because we need to design what’s right.</em></p><p><em>Sources: </em><a href="https://www.microsoft.com/en-us/microsoft-365/blog/2025/01/16/copilot-is-now-included-in-microsoft-365-personal-and-family/"><em>Copilot is now included in Microsoft 365 Personal and Family, Microsoft, 16 January 2025</em></a><em> · </em><a href="https://www.which.co.uk/news/article/how-to-avoid-microsoft-365-price-rises-aGNYY5O92as9"><em>How to avoid the Microsoft 365 price rises, Which?</em></a><em> · </em><a href="https://www.accc.gov.au/media-release/microsoft-in-court-for-allegedly-misleading-millions-of-australians-over-microsoft-365-subscriptions"><em>Microsoft in court for allegedly misleading millions of Australians, ACCC, 27 October 2025</em></a><em> · </em><a href="https://direct.businessnewsaustralia.com/articles/microsoft-apologises-and-offers-refunds-after-accc-copilot-action.html"><em>Microsoft apologises and offers refunds, Business News Australia, 6 November 2025</em></a><em> · </em><a href="https://about.fb.com/news/2025/03/europe-meet-your-newest-assistant-meta-ai/"><em>Europe, meet your newest assistant: Meta AI, Meta, 19 March 2025</em></a><em> · </em><a href="https://www.techradar.com/computing/websites-apps/whatsapp-users-fume-over-new-meta-ai-button-that-you-cant-remove-heres-what-it-does"><em>WhatsApp users fume over new Meta AI button that you can’t remove, TechRadar, April 2025</em></a><em> · </em><a href="https://www.euronews.com/2025/05/11/metas-new-optional-ai-chatbot-in-apps-like-whatsapp-is-proving-controversial-heres-why"><em>Meta’s new optional AI chatbot is proving controversial, Euronews, 11 May 2025</em></a><em> · </em><a href="https://blog.google/products-and-platforms/products/gmail/gmail-is-entering-the-gemini-era/"><em>Gmail is entering the Gemini era, Google, 8 January 2026</em></a><em> · </em><a href="https://www.theregister.com/2026/01/08/google_gemini_gmail/"><em>Gmail AI summaries and the smart features switch, The Register, 8 January 2026</em></a><em> · </em><a href="https://support.google.com/mail/answer/15604322"><em>Smart features and personalisation settings by region, Google</em></a><em> · </em><a href="https://www.theregister.com/2025/01/22/apple_intelligence_enabled/"><em>Apple Intelligence enabled by default in iOS 18.3, The Register, 22 January 2025</em></a><em> · </em><a href="https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/09/our-statement-on-changes-to-linkedin-ai-data-policy/"><em>ICO statement on LinkedIn’s AI data policy, 20 September 2024</em></a><em> · </em><a href="https://www.eu-digital-services-act.com/Digital_Services_Act_Article_25.html"><em>Digital Services Act, Article 25</em></a><em> · </em><a href="https://www.europarl.europa.eu/legislative-train/theme-protecting-our-democracy-upholding-our-values/file-digital-fairness-act"><em>Digital Fairness Act, European Parliament legislative train</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de92748a8e80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Would you mind leaving the room, please?]]></title>
            <link>https://justyna-belkevic.medium.com/would-you-mind-leaving-the-room-please-2ab65e6b7f80?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ab65e6b7f80</guid>
            <category><![CDATA[ethical-design]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 01:25:26 GMT</pubDate>
            <atom:updated>2026-09-26T01:25:45.509Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>The Assistant may sound like a person, but we were careful not to allow it to pretend to be an actual person.</em></blockquote><blockquote>Emma Coats, who led personality for Google Assistant from 2016</blockquote><blockquote><em>Unclear or ambiguous signals (e.g. generic references to “</em><strong><em>assistant</em></strong><em>”) or human-like representations that may mislead users.</em></blockquote><blockquote>European Commission, July 2026, on what does <strong>not</strong> count as telling someone they are talking to a machine. Guidelines on Article 50 of the AI Act, paragraph 38.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_NhcPc24_aDkVCBvqyZOHw.png" /></figure><p>In 1966, in a lab at MIT, a secretary sat down at a typewriter terminal to talk to a program she had watched being written. It was called ELIZA. It did almost nothing. It took whatever you typed, found a keyword, and turned your sentence back into a question, in the manner of a therapist who is paid by the hour. Its author, Joseph Weizenbaum, stood behind the secretary. She typed a few lines. Then she turned round and asked him to leave the room.</p><p>He told the story himself, ten years later, in a book he wrote largely because of it. He had not realised, he said, “that extremely short exposures to a relatively simple computer program could induce powerful delusional thinking in quite normal people.” He spent the rest of his career trying to get the field to take that seriously, and the field, on the whole, took the other lesson: that it worked.</p><p>ELIZA was not clever. It didn’t have to be. Two things were enough to make her treat it as somebody: it behaved like a person who was listening, and it had a name. Every chatbot since has been built from the same two parts, and the name, for most of those sixty years, has been “<strong>Assistant</strong>.” This is the story of that word: who built it, what they knew about it, how it ended up at the top of your chat window, and why the European Commission has now written it into a guidance document as an example of what <strong>not</strong> to do.</p><h3>The word</h3><p>Assistant is a job before it is anything else. A real one, held by real people, most of them women, and software borrowed it for what it implies: helpful, always available, pleased to be asked.</p><p>Microsoft put it on a product in 1997. The Office Assistant arrived in Office 97 as an animated paperclip with eyebrows, named Clippit, which nobody used, and a question, which everybody remembers:<em> it looks like you’re writing a letter, would you like help?</em> People loathed it. In 2001 Microsoft switched it off by default and then, in a move you could only get away with in 2001, turned the firing into an ad campaign, with Gilbert Gottfried as the voice of a paperclip who has just been let go and cannot believe it.</p><p>The paperclip went. The word stayed. The lesson the industry took from Clippy was about manners: don’t interrupt, and don’t be cute about it. Nobody drew a lesson about the noun, because that noun was the part that had worked. Take away the eyebrows and the interruptions and what was left was a feeling that somebody in the software was pleased you had turned up. That feeling was the product.</p><h3>The people who knew</h3><p>Then the word got a voice, and making it feel like somebody stopped being a side effect and became a job description.</p><p>Siri shipped on the iPhone 4S in October 2011. In January 2013 Apple posted a listing for a writer, someone with “a love for language, wordplay, and conversation,” to help “evolve and enrich Siri.” A hardware company hiring a writer for a job title. In June 2016 Google went further and hired Emma Coats, who had come from Pixar, where the whole enterprise is getting audiences to believe in characters that do not exist, to lead personality on the Assistant. It put writers from The Onion on the same team.</p><p>They were not working blind. Robotics had mapped the territory decades earlier. In 1970 Masahiro Mori published an essay in a Japanese magazine called <em>Energy</em> proposing that our affection for a machine climbs as the machine gets more human-like and then, close to the real thing, drops off a cliff. He called the cliff the uncanny valley, and his advice to designers was to stop before the edge. Asked about it forty years on, he had not changed his mind: “Why do you have to take the risk and try to get closer to the other side?”</p><p>So the Personality Team’s brief was a steering problem between two findings. Weizenbaum: people will believe in almost anything that talks. Mori: make it too human and they recoil. Between those two is a narrow band where a machine feels like somebody without claiming to be anybody, and Coats has described the rule they worked to inside it. The Assistant might sound like a person. They were careful not to let it pretend to be one.</p><h3>The week the label went in</h3><p>In 2023 the chat products arrived more or less at once, and every one of them needed a label at the top of a window.</p><p>Nobody had to argue for “Assistant.” Twenty-five years of work had made it the obvious word, and it went in the way the obvious word does: without the reasoning that had once come with it.</p><p>Three years later it reached Brussels. On 20 July 2026 the European Commission published its guidelines on Article 50 of the AI Act, the provision that has required, since 2 August, that anyone talking to a machine in the EU be told so. Guidelines are not law, but they are what the market surveillance authority deciding your case will have open.</p><p>Paragraph 38 of that document is a list of ways companies might try to tell people they are talking to a machine, which the Commission says are not enough on their own. Putting it in the terms and conditions doesn’t count. Nor does a watermark that only software can read, or a banner saying “services on this website use AI”, or a note that the system uses large language models, which means nothing to the person reading it. And then, in the same list, this:</p><blockquote>Unclear or ambiguous signals (e.g. generic references to “<strong>assistant</strong>”) or human-like representations that may mislead users.</blockquote><p>The second half of that item, “human-like representations that may mislead users,” describes the narrow band Coats’s team was steering: the point where a machine feels like somebody without being anybody.</p><p>Ten years apart, Coats and the Commission are describing the same risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zu_MSX2Z5sMWUkv5JNNpXw.png" /></figure><h3>What changes when they know</h3><p>It is fair to ask whether any of this matters. Weizenbaum’s secretary knew exactly what ELIZA was and asked him to leave anyway. If people confide in a machine even when they know, what does telling them achieve?</p><p>Quite a lot, it turns out, and in both directions.</p><p>In 2019 four marketing researchers published a field experiment in which more than 6,200 customers received a sales call from a chatbot. When the bot did not say what it was, it sold as much as an experienced human and four times as much as a new hire. When it introduced itself as a bot at the start of the call, purchases fell by more than 79 per cent. Customers hung up sooner, and afterwards they rated the same bot, working from the same script, as less knowledgeable and less empathetic. One sentence at the beginning of the call was the only difference.</p><p>That is the commercial reason “Assistant” has been so useful, and the commercial reason nobody was in a hurry to replace it. Telling people costs sales.</p><p>It runs the other way, too. In 2014 a team at the University of Southern California put people in front of a virtual interviewer for a health screening and told half of them that a person was operating it and half that it was automated. The half who believed they were talking to software were less worried about being judged, managed their answers less, showed more of what they were feeling, and were rated more open by the people who read the transcripts afterwards. Told it is a machine, people say more to it, and truer things.</p><p>Google ran into all of this in public in 2018, when it demonstrated Duplex, a system that phoned restaurants and hair salons to book appointments in a voice that said “umm” in the right places. The demo was a hit and the reaction was not. Google promised that disclosure would be built in, and one wording it floated was to have the system open the call by introducing itself as “the Google assistant.” Whether that sentence tells a person they are talking to a machine is the question the Commission has now answered.</p><p>So the sentence changes what people do: how much they buy, how far they trust the answer, and what they are willing to say. That is why the law wants it said up front, and why “Assistant” will not do on its own. It is the one word that gets the trust without the sentence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uy9X5cbmuQF99WQS04ubQ.png" /></figure><h3>What it asks of your screen</h3><p>The word’s job, for thirty years, has been to make software feel like a person who is pleased to help. The law’s requirement is that nobody be left thinking they are dealing with a person. The word is not illegal and it is not in breach of anything.</p><p>So leave it where it is, and add the sentence the word cannot say for you. “You’re chatting with an AI, not a person. It can be wrong.” Twelve words, in the first message, in the conversation itself, and then somewhere a person can find again on message forty. The tone or the noun was never the Commission’s concern. What it objects to is somebody having to work it out for themselves.</p><p>There is one exception. You can skip the disclosure if it is already obvious to a reasonable person that they are talking to a machine. The Commission gives two examples of obvious: an internal tool used by staff who know what it is, and a coding assistant used by professional developers. Its example of not obvious is a customer-support chatbot that writes like a person. A sparkle icon does not make it obvious. If the public can use your product, assume the exception does not apply to you.</p><p>None of this is new, by the way. California has made bots identify themselves since 2019, if they are selling something or campaigning for a vote. But that law only reaches sites with ten million monthly American users. The EU rule has no such threshold. It applies to your product whether or not anyone has heard of it.</p><p>If your product makes images, audio or video, there are two more jobs, and they fall on different people. The first is for whoever puts the output in front of the public. If a picture, a voice or a clip could pass for real, it needs a label that says it was generated, and the label has to be on the screen the first time somebody sees it. The second is for whoever builds the system. Every file it produces has to carry a mark that software can read, so that a platform or a newsroom can later check where it came from. That is the one duty in Article 50 that touches the engineering. It is also the one most teams get wrong, because a crop, an export or a compression step will strip the mark out, and nobody notices until someone checks. Test it from the model to the download button. If your system was already on the market on 2 August, you have until 2 December to get the marking right.</p><p>Film got to the first of those rules the hard way. In 1934 a Russian princess sued MGM in London over a film about Rasputin that implied she had been seduced by him. She won. The line at the end of the credits, any resemblance to real persons, living or dead, is purely coincidental, is usually traced to that case. The deepfake label asks for the same honesty, without waiting for someone to sue.</p><p>If you use AI to write news, or anything else meant to inform the public, say so on the page. There is one way out, and it is how newsrooms already work: a human reads the text before it goes out, and a person or an organisation puts their name to it as editorially responsible.</p><p>If your product tries to read people’s emotions, or sorts them into groups from their face, voice or body, you have to tell them it is happening. Before that, check whether you are allowed to run it at all. Reading emotions is banned at work and in schools, unless it is there for medical or safety reasons. Using biometrics to guess someone’s race, politics, religion or sexuality is banned everywhere.</p><p>Then there is the number. Get any of this wrong and the fine can reach €15 million or 3% of worldwide annual turnover, whichever is higher. For small companies and start-ups it is whichever is lower. Interface copy has carried fines before: cookie banners, risk warnings, terms of service. But everyone understood those as legal text, written by a lawyer. The label at the top of a chat window was never that. It was a naming decision. It is now both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5-Qoqw_aQolMdqVuC4FPwQ.png" /></figure><h3>The profession has changed</h3><p>For as long as there has been a design profession, ethical design has been something you argued for. You made the case in the room, against the roadmap and the conversion target, and sometimes you won, and often you didn’t, because the other side had numbers and you had a principle. Designing what works was the job. Designing what’s right was something you cared about on top of the job, if you had the standing and the energy that quarter.</p><p>Article 50 takes one of those arguments out of the room. Whether a person knows they are talking to a machine used to be a judgement call inside a product team; now it is a duty with a number attached. A small duty. But it is the first time many designers will have watched something they always treated as their own decision, a word in a header, become a decision the law has a view on, and it will not be the last. The heavier rules, for systems that decide about people’s credit, their jobs, their housing and their benefits, arrive in 2027 and 2028, and Article 14 requires those systems to be built, in the law’s own words, “with appropriate human-machine interface tools,” so that the people overseeing them can understand what the system is doing, decide not to use it, and stop it. No model satisfies that. A screen does, and somebody is going to have to design it.</p><p>There is a precedent for how that goes. In 1990 the US Congress ordered a nutrition label onto every packaged food in the country. The law said what had to be on it and nothing about what it would look like, so the FDA rang a designer, Burkey Belser, who did the work unpaid. The black-and-white panel that appeared on packaging in 1994 has been called the most reproduced graphic in the world; Massimo Vignelli called it a masterpiece of information architecture. The law wrote the requirement. A designer turned it into something a person could use in a supermarket aisle, and thirty years on nobody thinks of the Nutrition Facts panel as compliance.</p><p>Until now, the ethics argument in this field has mostly been about the model: alignment, evals, what the thing will and won’t say. That work goes on. But the law has put a second question next to it, and the second question is a design question: does the person know what they are talking to? It is no longer enough to design what works. We need to design what’s right, and the difference between the two has stopped being a matter of taste or standing. It is written down.</p><p><em>First of 8 on where AI ethics actually gets decided: between the model and the person.</em></p><p><em>Sources: </em><a href="https://digital-strategy.ec.europa.eu/en/library/guidelines-transparency-obligations-providers-and-deployers-ai-systems"><em>Guidelines on the transparency obligations under Article 50 of the AI Act, C(2026) 5054 final, 20 July 2026, para 38</em></a><em> · </em><a href="https://artificialintelligenceact.eu/article/50/"><em>Article 50</em></a><em> · </em><a href="https://artificialintelligenceact.eu/article/99/"><em>Article 99, penalties</em></a><em> · </em><a href="https://artificialintelligenceact.eu/article/14/"><em>Article 14, human oversight</em></a><em> · </em><a href="https://perspectives.stephensonharwood.com/post/102nfqh/eu-ai-act-update-european-commission-adopts-guidelines-on-article-50-transparenc"><em>Stephenson Harwood on the guidelines</em></a><em> · </em><a href="https://sites.google.com/view/elizaarchaeology/blog/3-weizenbaums-secretary"><em>Weizenbaum, Computer Power and Human Reason (1976), pp. 6–7, via ELIZA Archaeology</em></a><em> · </em><a href="https://en.wikipedia.org/wiki/Office_Assistant"><em>Office Assistant</em></a><em> · </em><a href="https://accountancyage.com/2001/04/11/microsoft-says-farewell-to-clippy/"><em>Microsoft says farewell to Clippy, 2001</em></a><em> · </em><a href="https://www.macrumors.com/2013/01/18/apple-looking-to-hire-writers-to-enhance-siris-witty-personality/"><em>Apple’s 2013 listing for a Siri writer</em></a><em> · </em><a href="https://www.ibtimes.com/google-hires-onion-pixar-write-jokes-assistant-2429421"><em>Google’s hires from Pixar and The Onion</em></a><em> · </em><a href="https://www.thedrum.com/news/google-assistant-personality-creator-coats-says-building-emotional-connections-scale"><em>Emma Coats on building Assistant’s personality</em></a><em> · </em><a href="https://spectrum.ieee.org/an-uncanny-mind-masahiro-mori-on-the-uncanny-valley"><em>Mori on the uncanny valley, IEEE Spectrum</em></a><em> · </em><a href="https://pubsonline.informs.org/doi/10.1287/mksc.2019.1192"><em>Luo, Tong, Fang and Qu, “Machines vs. Humans: The Impact of AI Chatbot Disclosure on Customer Purchases,” Marketing Science, 2019</em></a><em> · </em><a href="https://www.sciencedirect.com/science/article/abs/pii/S0747563214002647"><em>Lucas, Gratch, King and Morency, “It’s only a computer: Virtual humans increase willingness to disclose,” Computers in Human Behavior, 2014</em></a><em> · </em><a href="https://www.techspot.com/news/74582-google-responds-duplex-backlash-ai-voice-system-identify.html"><em>Google’s response to the Duplex backlash, 2018</em></a><em> · </em><a href="https://natlawreview.com/article/california-s-bot-disclosure-law-sb-1001-now-effect"><em>California SB 1001</em></a><em> · </em><a href="https://en.wikipedia.org/wiki/All_persons_fictitious_disclaimer"><em>All persons fictitious disclaimer</em></a><em> · </em><a href="https://en.wikipedia.org/wiki/Burkey_Belser"><em>Burkey Belser</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ab65e6b7f80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why does your app need you to be lonely?]]></title>
            <link>https://justyna-belkevic.medium.com/why-does-your-app-need-you-to-be-lonely-08662fbf67c9?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/08662fbf67c9</guid>
            <category><![CDATA[future]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[ethical-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Thu, 28 May 2026 08:14:03 GMT</pubDate>
            <atom:updated>2026-05-28T08:14:03.959Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Engagement metrics: up. Loneliness rates: also up. Coincidence?</strong></p><blockquote><em>🧠 </em>Thought-provoking short ethical design series: Article 10/10<br>It’s no longer enough to design what works. We need to design what’s <strong>right</strong>.</blockquote><p>Priya opens Instagram at 9:47pm.</p><p>She’s not looking for content. She’s looking for <strong>connection</strong>, a sign that someone out there is thinking about her.</p><p>“Bringing you closer to the people and things you love.” That’s Instagram’s promise.</p><p>Two hours later, she puts her phone down. Three colleagues got engaged. A designer landed at Google. An influencer is in Bali again. She’s seen hundreds of lives. She hasn’t sent a single message.</p><p>She feels worse than when she started.</p><p>The app calls this a successful session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MECjSzvIiBoBRg1m3ePpqg.png" /><figcaption>The real price we pay (AI generated).</figcaption></figure><h3>The research is clear</h3><p>A nine-year Baylor University study tracking nearly 7,000 adults found that both passive and active social media use were linked to increased loneliness over time. Not just scrolling, but also posting and engaging. The quality of digital interactions does not match what happens face to face.</p><p>A European Commission study of young Europeans found that it’s not so much the hours spent on social platforms that matter, but it’s <em>how</em> you use them. Passive scrolling reinforces feelings of disconnection. Loneliness mediates the relationship between passive use and psychological distress.</p><p>The platforms know this. Facebook’s internal research found that 13.5% of teen girls said Instagram worsens suicidal thoughts and 17% said it contributes to their eating disorders.</p><p>They shipped all the features anyway.</p><h3>The business model</h3><p>Priya wants <em>connection</em>. The app wants <em>engagement</em>.</p><p>These are not the same thing.</p><p>Connection would mean: show her a conversation. Surface a friend she hasn’t talked to. Prompt her to reach out.</p><p>Engagement means: show her content. Keep her scrolling. Maximize time on app.</p><p>So? The app chooses engagement, because connection <strong>ends</strong> sessions. A user who actually connects with someone puts down their phone. A user who keeps scrolling, searching for connection they never quite find, stays for two hours.</p><p>The typical user spends 2 hours and 21 minutes on social media each day. 93% of Gen Z admit to losing sleep because they stayed up past their intended bedtime for social media.</p><p>The loneliness is what keeps them coming back.</p><h3>How we got here</h3><p>The app isn’t evil. These were design decisions. Each one made sense at the time.</p><p><strong>The feed over the inbox.</strong></p><p>When Facebook launched News Feed in 2006, it was chronological, a straight feed of your friends’ activity. By October 2009, the default changed to algorithmic sorting based on engagement.</p><p>The shift seemed logical. Too much content, too little time. Let the algorithm surface what matters.</p><p>But “what matters” became “what gets engagement.” And engagement doesn’t mean connection. It means reaction. Outrage. Envy. Comparison. The posts that thrived were the ones that triggered something, not the ones from people who actually mattered to you.</p><p>Your close friends got buried. Viral content rose. The feed stopped being about your relationships and started being about holding your attention.</p><p><strong>The like over the reply.</strong></p><p>In 2007, Facebook had 30 million users and the only way to engage with content was to comment. Product manager Leah Pearlman noticed the same comments appearing over and over: “Awesome.” “Congrats.” “I like this.”</p><p>Her solution was to convert those monotonous comments into a single click. The project was codenamed “Props.” By February 2009, Zuckerberg approved the like button. It was an instant hit.</p><p>But something was lost. A comment, even a generic one, is a conversation. A like is a transaction. Human interaction was reduced to a single tap. Efficient. Empty.</p><p>The posts that thrived uniquely in Facebook’s feed, fueled by quick-twitch likes, were the ones that offered simple solutions to complex problems, that played on people’s biases and manipulated their emotions. Those that addressed the same problems with nuance withered.</p><p><strong>The infinite scroll.</strong></p><p>In 2006, interface designer Aza Raskin was frustrated with Google’s multi-page design. He came up with an idea: what if results just kept loading as you scrolled?</p><p>The infinite scroll was born. It eliminated natural stopping points. No more clicking “next page.” No more pause to decide if you’d seen enough.</p><p>Raskin now expresses deep regret over his invention, apologizing profusely and wishing he never created it.</p><p>“It’s as if social media companies are taking behavioral cocaine and just sprinkling it all over your interface and that’s the thing that keeps you coming back and back and back,” Raskin said.</p><p>According to Raskin, time worth 200,000 human lifetimes is wasted on a daily basis due to infinite scrolling.</p><p>He testified against Meta in New Mexico, where the company was charged with making their apps addictive to children.</p><p>Raskin’s lesson: “Optimizing something for ease-of-use does not mean best for the user or humanity.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c1Is1UOpcvNOippexgLU-w.png" /><figcaption>Connection never gets closer (AI generated).</figcaption></figure><h3>The hidden costs</h3><p><strong>Users eventually leave.</strong></p><p>Priya feels worse every time she uses the app. She doesn’t connect it consciously, not yet. But her body knows. The low-grade dread when she opens it. The empty feeling when she closes it.</p><p>In 2014, 71% of teens used Facebook. Today, only 32% do.</p><p>The churn is already happening. The engagement model looks profitable because it extracts attention now. But extraction has a limit. You can optimize for time-on-app until users have nothing left, and then they leave, and they <strong>don’t come back</strong>.</p><p><strong>Loneliness erodes trust.</strong></p><p>When users feel worse after using your product, they stop trusting it, even if they can’t articulate why. They recommend it less. They engage more defensively. They start looking for alternatives.</p><p>Trust is expensive to build and nearly impossible to rebuild. Every session that leaves users feeling empty spends down an asset that doesn’t appear on any balance sheet. By the time you see the impact in your numbers, it’s too late to fix.</p><p><strong>Regulation is coming.</strong></p><p>On February 6, 2026, the European Commission issued preliminary findings that TikTok breached the Digital Services Act. This marks the first instance of EU enforcement focusing on the harmful design of a platform rather than illegal content or data protection.</p><p>The Commission concluded that TikTok must fundamentally redesign its service: disabling infinite scroll over time, introducing mandatory screen-time breaks, and overhauling its recommender system.</p><p>The EU has announced the Digital Fairness Act targeting addictive design of digital services. Australia’s under-16 social media ban took effect in December 2025.</p><p>The attention economy is facing the same reckoning tobacco and gambling faced. Companies still optimizing purely for engagement will be explaining themselves to lawmakers.</p><p>For senior designers, this isn’t abstract. The executives who approved these features are now being named in lawsuits. The design decisions you make today may be exhibit A in a courtroom five years from now.</p><h3>What a real guide would do</h3><p>Imagine the app actually helped Priya get what she came for.</p><p>She opens it at 9:47pm, feeling disconnected. The data to help her already exists. The app knows she hasn’t messaged anyone in days. It knows she’s scrolling passively. It knows who her real friends are versus who she just follows.</p><p><strong>A real guide would notice.</strong> <br>Not just track behavior for ad targeting, but recognize when a user is seeking connection and not finding it.</p><p><strong>A real guide would intervene.</strong> <br>“You haven’t talked to Mira in 3 months. She posted yesterday. Want to say hi?” One prompt. One conversation. Worth more than two hours of scrolling.</p><p><strong>A real guide would make connection easy.</strong> <br>Messages first, not content. Close friends surfaced, not viral strangers. The architecture would assume you came to talk to people, not watch them.</p><p><strong>A real guide would build stopping points.</strong> <br>“You’ve seen posts from your close friends. Everyone else can wait.” Not infinite scroll, but intentional use. Not “how do we keep them here” but “did they get what they needed?”</p><p><strong>A real guide would measure what matters.</strong> <br>Not time on app, but: did she talk to someone? Did she leave feeling better than she arrived?</p><p>The technology exists. The data is already there. The reason we don’t build this is simple math: a connected user <strong>leaves</strong>. A lonely user <strong>keeps scrolling</strong>.</p><p>When your revenue model depends on time-on-app, helping users get what they came for becomes a cost, not a feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bn5bl2Cxgpvgj-ZJFOP0hQ.png" /><figcaption>Navigation, not distraction (AI generated).</figcaption></figure><h3>The success that’s possible</h3><p>Imagine Priya’s evening with an app designed as a real guide.</p><p>She opens it at 9:47pm, feeling that same low hum of disconnection.</p><p>The app shows her: “Mira’s online, she posted yesterday. Start a conversation?”</p><p>Priya hesitates. Then types: “Hey. It’s been forever. How are you?”</p><p>They talk for 20 minutes. Just catching up. Just being in each other’s lives again.</p><p>Priya puts her phone down at 10:15pm. She feels better. Not because she consumed content, but because she connected with a real person.</p><p>Session length: 28 minutes. Engagement metrics: terrible.</p><p>But she got what she came for.</p><p>She’ll be <strong>back</strong> tomorrow, not out of habit or compulsion, but because the app helped her. She’ll recommend it to friends. She’ll pay for premium. She’ll stay for years.</p><p>That short session that delivered real value is worth more than the long session that left her empty. The difference just doesn’t show up on this quarter’s dashboard. But it will be in the lifetime value.</p><h3><strong>It’s not hypothetical.</strong></h3><p>WhatsApp has 2 billion users. No feed. No algorithm. No infinite scroll. Just conversations.</p><p>Users open it to talk to people, and then they leave. Session complete. Need met. That’s the entire product.</p><p>Meta bought WhatsApp for $19 billion in 2014, the most expensive acquisition in tech history at the time. They paid that much for a product that does the opposite of Instagram: it helps people connect and then gets out of the way.</p><p>The irony isn’t lost. Meta owns the proof that connection-first design works.</p><h3>The real metric</h3><p>The metric that matters isn’t session length. It’s lifetime value.</p><p>A user who feels connected, who gets what they came for, who trusts the product, they stay for years. They pay for premium. They recommend it to others. They defend it when critics attack.</p><p>A user who scrolls for two hours and feels empty? They’re already halfway out the door. You just can’t see it yet. Their trust is eroding. Their enthusiasm is fading. One day they’ll delete the app and they won’t quite know why. Or jump on the better one.</p><p>The loneliness loop feels profitable because it drives short-term engagement. But it’s an extraction model, you’re mining attention until there’s nothing left.</p><p>Connection is a <strong>sustainability</strong> model. Users come back because you helped them, not because you hooked them. They stay because they trust you, not because they’re trapped.</p><p>That’s not idealism. That’s how you build something that lasts.</p><h3>The choice</h3><p>If you’re designing products that touch human connection, you have a choice.</p><p>You can optimize for engagement and pretend it’s the same as connection. You can measure time on app and call it success. You can build infinite scroll and algorithmic feeds and like buttons that reduce relationships to transactions.</p><p>Or you can be the guide you promised to be.</p><p>Surface real friends, not viral content. Make conversation easier than consumption. Build stopping points. Measure whether people feel closer to each other, not just whether they stayed.</p><p><strong>Three questions to ask in your next product review:</strong></p><ol><li>What did the user come here to do, and did we help them do it?</li><li>If this feature works perfectly, will the user need us less or more?</li><li>Would we be comfortable if this design decision was on the front page of the New York Times?</li></ol><p>If you can’t answer these honestly, you already know what needs to change.</p><h3>The bet</h3><p>There’s a bet being made right now, whether product teams realize it or not.</p><p>One side bets that engagement is everything. Keep users scrolling. Maximize time on app. Worry about trust later.</p><p>The other side bets that connection wins long-term. Shorter sessions, but users who actually got what they came for. Users who trust you. Users who stay.</p><p>The first bet pays out quarterly. The second pays out over decades.</p><p>Connection isn’t just more ethical. It’s more sustainable. It’s better design.</p><p>And eventually, it’s better business.</p><p><em>This is the final article in the thought-provoking short ethical design series. Thank you for reading!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=08662fbf67c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The scam had better UX than the real thing]]></title>
            <link>https://justyna-belkevic.medium.com/the-scam-had-better-ux-than-the-real-thing-0029f9459a33?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/0029f9459a33</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-leadership]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ethical-design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Mon, 04 May 2026 07:59:02 GMT</pubDate>
            <atom:updated>2026-05-04T07:59:02.701Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>We taught people to trust good design. That was always a shortcut. AI just exposed it.</strong></p><blockquote><em>🧠 </em>Thought-provoking short ethical design series: Article 9/10<em><br>It’s no longer enough to design what works. We need to design what’s </em><strong><em>right</em></strong><em>.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*8fwS3iHAl2jc1qC19M6ezA.png" /><figcaption>“The checkout is smooth, I promise”</figcaption></figure><p>My mom almost bought a handbag from a store that doesn’t exist.</p><p>The website was clean. Nice typography. Good photography. Smooth checkout. Little chat bubble in the corner that actually responded.</p><p>It looked more professional than most legitimate small businesses. Honestly, it looked better than some sites I’ve worked on.</p><p>The whole thing was fake. AI-generated products. AI-generated reviews. A storefront built in an afternoon to collect credit cards and disappear.</p><p>She didn’t buy because the price was too good. That was the only thing that felt off.</p><p>The design was… flawless.</p><h3>“VibeScams”</h3><p>Security researchers at Norton coined a term this year: VibeScams.</p><p>The name comes from “vibe coding,” the trend where people build apps just by describing what they want to AI. VibeScamming is the same thing, but for fraud.</p><p>The idea is simple: scammers don’t need to create perfect replicas anymore. They just need to capture the <em>vibe</em> of a legitimate site. The right colours. The right spacing. The logo in the right place. The familiar footer links.</p><p>Enough to pass the vibe check.</p><p>From January to August 2025, Norton blocked approximately 140,000 AI-generated scam websites. That’s roughly 580 new malicious sites appearing every day.</p><p>These aren’t the clumsy phishing attempts of the past, filled with broken English and obvious design flaws. They’re pixel-perfect replicas of trusted brands that fool users at first glance.</p><p>Some AI web building platforms can recreate an entire site from a screenshot (from homepage to shopping cart) with perfect language localisation in multiple languages.</p><p>No coding. No design skills. Just a prompt and a few minutes.</p><h3>The old rule</h3><p>For decades, we taught people a simple heuristic: if it looks sketchy, don’t trust it.</p><p>Bad grammar. Pixelated logos. Broken layouts. Weird fonts. These were the red flags.</p><p>The logic made sense. Professional design required professionals. Scammers couldn’t afford real designers, so polish meant safety.</p><p>Banks ran campaigns on this. Security experts repeated it. Parents told their kids: “If the website looks cheap, don’t enter your credit card.”</p><p>It worked. The barrier to looking legitimate was time, money, and skill.</p><p>AI just removed all three.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ruwy5uv5357iG6vrAFis0w.jpeg" /><figcaption>Old website</figcaption></figure><h3>What changed</h3><p>Now anyone with a prompt can generate:</p><ul><li>A professional logo in seconds</li><li>Product photography of things that don’t exist</li><li>Copy that follows every UX writing best practice</li><li>Reviews with realistic variety and natural typos</li><li>Customer support chat that sounds more helpful than most real companies</li></ul><p>Researchers testing AI web builders reported creating convincing replicas of TikTok, Coinbase, and Binance login pages using only <strong>free</strong> versions. The sites were generated by having AI write the prompts, then simply copy-pasting them into the platforms, no customisation or manual coding required.</p><p>The scam doesn’t look sketchy anymore. The scam looks like it raised a seed round.</p><h3>When fake looks more real than real</h3><p>I got a phishing email last month that was better written than my actual bank’s emails.</p><p>Cleaner layout. Clearer call to action. None of the cramped legal disclaimers. It felt professional, warm, direct.</p><p>My bank’s real emails are more cluttered. More corporate. More awkward.</p><p>The scam was polished. That’s the problem.</p><p>The real email has constraints. Legal review. Accessibility requirements. Brand guidelines. Three teams with opinions on the button color. It ends up being a compromise that looks like a compromise.</p><p>The fake has no constraints. It can be exactly what converts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*Q-XaXPjZP1YXq1GOGU1NFQ.jpeg" /><figcaption>The aesthetic of early 2000s internet scams</figcaption></figure><h3>The numbers</h3><p>According to Gen Threat Labs, VibeScams break down into three main categories: phishing attacks make up 48.6% of cases, crypto scams account for 28.5%, and tech support scams represent 3.7%.</p><p>The geographic spread is global, with the United States, France, Brazil, Germany, and Japan among the most heavily targeted countries.</p><p>GenAI-enabled scams rose 456% between May 2024 and April 2025.</p><p>According to Netcraft’s research, the use of AI-generated text in scam websites saw a 3.95x increase between March and August 2024.</p><p>This isn’t a future threat. This is now.</p><h3>The typo trick</h3><p>VibeScams frequently rely on typosquatting, registering domain names that closely resemble legitimate ones but contain subtle misspellings.</p><p>coiinbase.com instead of coinbase.com arnazon.com instead of amazon.com paypa1.com instead of paypal.com</p><p>At a quick glance, especially on mobile devices, these differences are easy to miss. When combined with professional design generated by AI tools, the deception becomes remarkably effective.</p><p>The design passes. The URL almost passes. The whole experience feels right.</p><h3>Why this is an ethical design problem</h3><p>The problem isn’t that scam sites look bad. The problem is they look <strong>fine</strong>.</p><p>And why wouldn’t they? We published the playbook.</p><p>Every “10 ways to build trust on your landing page” article. Every “UX patterns that convert” breakdown. Every case study about button colors and signup rates.</p><p>We documented exactly what makes users trust a website. Where to put the testimonials. How to phrase the guarantee. Which badges to display.</p><p>We put it all online, for free, because we believed in democratizing design. I still believe in that.</p><p>But we were writing a manual for trust, and anyone could read it. Including people who wanted to manufacture trust they hadn’t earned.</p><p>The scammer doesn’t need to figure out what makes a site feel safe. We already told them.</p><p>Green lock icon. Trust badges. Clean typography. Reviews with photos. Chat widget that responds.</p><p>The difference between us and them isn’t knowledge anymore. It’s <strong>intent</strong>. And intent doesn’t show up in a screenshot.</p><p>That’s what makes this an ethical problem.</p><p>We taught users to trust surfaces. We never taught them to question what’s underneath. We optimized for the feeling of trust without asking whether that feeling was protecting anyone or just making them easier to fool.</p><p>Ethical design isn’t only about what we build. It’s about what we teach people to believe.</p><p>We taught a generation that polish equals safety. Now polish is free. And safety is nowhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*JY78z_yMRJBQL7-4OOd4Hg.jpeg" /></figure><h3>What still works (for now)</h3><p>If you’re designing for a legitimate business, these are the signals that still matter:</p><p><strong>Time.</strong> History can’t be faked overnight. Show your company’s real timeline. Real milestones. Real people who’ve been there for years.</p><p><strong>Depth.</strong> Scam sites are surfaces. One convincing landing page, nothing behind it. Real companies have weird corners. Imperfect pages. Evidence of actual humans making actual decisions over time.</p><p><strong>Third-party trails.</strong> Google reviews. Press coverage. Social accounts with real history. Things that exist outside your own site.</p><p><strong>Transparency about constraints.</strong> The legal footer. The accessibility statement. The slightly awkward copy that legal made you add. These aren’t bugs. They’re proof that your company has something to lose.</p><p>The irony: the things we used to hide or apologize for (the messiness, the constraints, the compromises) might now be signals of legitimacy.</p><h3>The new rule</h3><p>The old advice was simple: sketchy-looking equals unsafe.</p><p>The new advice is harder: professional-looking doesn’t mean safe.</p><p>For users, that means more skepticism. More checking. More effort before trusting.</p><p>For designers, it means something else: we can no longer rely on polish as our value proposition.</p><p>If anyone can make something look trustworthy, then looking trustworthy isn’t the job anymore. The job is <em>being</em> trustworthy and finding ways to signal that which can’t be faked in an afternoon.</p><p>That’s a harder design problem. We haven’t solved it yet.</p><h3>The bigger thing</h3><p>This isn’t just about scams. It’s about what happens when all our trust signals break at once.</p><p>Credentials used to signal expertise. Good writing used to signal education. Professional design used to signal investment.</p><p>All of it was shorthand for: “Someone put in effort here. That effort means something.”</p><p>We built the entire internet on that assumption. The padlock icon. The trust badges. The clean layout. The nice typography. Each one a quick visual that let you decide in seconds whether something was worth your trust.</p><p>It worked because effort was scarce. Making something look professional took time, money, skill. If someone had all three, they probably weren’t running a scam. Probably.</p><p>That’s over now.</p><p>AI generates the credentials. AI writes the copy. AI builds the site. Effort is no longer scarce, which means effort is no longer a signal.</p><p>We built careers on making things look trustworthy.</p><p>Now looking trustworthy is the easiest part.</p><p>The question for designers isn’t “how do we compete with AI on polish?” We can’t. The question is: what signals trust when polish is free?</p><p>That’s the design problem of the next decade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0029f9459a33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[0 Steps Today]]></title>
            <link>https://justyna-belkevic.medium.com/0-steps-today-933239b09754?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/933239b09754</guid>
            <category><![CDATA[ethical-ux-design]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Wed, 15 Apr 2026 01:44:53 GMT</pubDate>
            <atom:updated>2026-04-15T01:44:53.257Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>When wellness products make you feel worse</strong></p><blockquote>🧠 Thought-provoking short ethical design series: Article 8/10 <br><em>It’s no longer enough to design what works. We need to design what’s right.</em></blockquote><p>It’s Sunday evening. James opens his phone and there it is, the weekly screen time report. He didn’t ask for it. He never opted in. But every Sunday, like clockwork, his phone tells him exactly who he is.</p><p>Average daily use: 4 hours 37 minutes.</p><p>Up 23% from last week.</p><p>Most used app: Instagram. 1 hour 42 minutes per day.</p><p>He stares at it. He feels the thing the notification was designed to make him feel: a small, sharp wave of shame. He swipes it away. Opens Instagram.</p><p>Nobody designed the moment <strong>after</strong> the shame. Nobody asked what happens when you show someone a truth they’re not ready to hear and then offer them absolutely nothing except the door back to the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*S9zU1BgO2hgAsDLu6QWqOw.png" /><figcaption>Tools that confront users with truths they’d rather not see, and offer no compassion, just data.</figcaption></figure><h3>The confession booth with no priest</h3><p>We’ve built an entire generation of products that watch you. Not in the dystopian surveillance way, in the helpful, wellness-forward, self-improvement way. Your fitness tracker knows you didn’t walk today. Your meditation app knows you haven’t opened it in eleven days. Your health app knows you logged three drinks on Tuesday and zero on Wednesday, which probably means Wednesday was four.</p><p>These products see everything. And every week, they tell you what they saw.</p><p>But here’s the design problem nobody’s talking about: they report, but they don’t support. They diagnose, but they don’t treat. They hold up a mirror and walk away.</p><p>Your screen time report has never once said: “You were up 23% this week. That’s okay. Here’s what was happening in your life that might explain it.” It just gives you the number and lets the shame do the work.</p><h3>Data without context is just judgement</h3><p>There’s a moment in every product design process where someone says: “Let’s show users their data. Knowledge is empowering.”</p><p>And it sounds right. Transparency. Self-awareness. Informed decision-making. These are good things.</p><p>But data without context isn’t transparency. It’s a verdict.</p><p>When your fitness app shows you “0 steps today,” it doesn’t know you’re recovering from surgery. When your meditation app sends “You’ve broken your streak!”, it doesn’t know you are grieving. When your calorie tracker shows a red number, it doesn’t know you’re in recovery from an eating disorder and that red number is the most dangerous colour in your entire phone.</p><p>The product knows what you did. It has no idea why. And it passes judgement anyway.</p><p>Here’s where it gets worse. Because these products don’t just report, they gamify. They turn your behaviour into streaks, scores, rings, and percentages. They introduce a system where consistency equals success and any deviation equals failure.</p><p>Miss a day on Duolingo? The owl is sad. Skip a workout on your Apple Watch? The ring is incomplete. Forget to log a meal? The app reminds you that your “data will be less accurate.” Translation: you’re ruining it.</p><p>This creates what psychologists call a shame loop. The product makes you feel bad. You avoid the product because it makes you feel bad. The product notices you’re avoiding it and sends a notification designed to make you feel bad about avoiding it. You open it, feel bad, close it, and the cycle starts again.</p><p>At no point in this loop does anyone ask: is this helping?</p><h3>The fitness tracker that made it worse</h3><p>A 2023 study published in the journal <em>Body Image</em> found something that should concern every designer working on wellness products: people who used fitness trackers reported higher levels of body dissatisfaction and disordered eating behaviours than those who didn’t. Not because the trackers were inaccurate. Because they were too accurate. They gave people a number to obsess over. And the number was never good enough.</p><p>The product worked exactly as designed. The user suffered exactly as predicted by researchers, not by the product team.</p><p>This isn’t a bug. This is a feature request nobody filed: “As a user, I want to feel inadequate about my body so that I use the app more frequently.”</p><p>Nobody wrote that ticket. But that’s what shipped.</p><h3>Compassion is a design decision</h3><p>So what would it look like to design these products differently?</p><p>It would look like asking a question before delivering a verdict. Not “Your screen time was 4 hours 37 minutes” but “Want to see your screen time this week?” The difference is <strong>consent</strong>. One is a mirror shoved in your face. The other is a mirror you choose to look at.</p><p>It would look like context. Not “You broke your streak” but “You’ve been consistent for 14 days. Missing one doesn’t erase that.”</p><p>It would look like off-ramps. A meditation app that notices you haven’t opened it in two weeks and instead of guilt-tripping you says: “Whenever you’re ready. No pressure. The app will be here.”</p><p>It would look like asking the hardest product question of all: <strong>is this metric helping the user, or is it helping our engagement numbers?</strong></p><p>Because right now, the honest answer (for most of these products) is the second one.</p><h3>The notification James actually needed</h3><p>James is still on his phone. It’s now Monday. Instagram has been open for 40 minutes.</p><p>His screen time report told him something was wrong. It was right. Something is wrong. He’s lonely. He moved to a new city three months ago. He doesn’t have close friends here yet. Instagram is where the old ones live: frozen in stories and posts from a life he’s not part of anymore.</p><p>No product told him that. No notification said: “Hey, you’ve been scrolling for a while. Not judging. But if you’re looking for connection, this isn’t where you’ll find it.”</p><p>Instead, the screen time report made him feel weak. And Instagram made him feel connected just enough to keep scrolling.</p><p>Two products, working perfectly. One shames. One soothes. Neither helps.</p><p>James deserved better.</p><p><em>This is Article 8 of 10 in the Thought-Provoking Short Ethical Design Series.<br></em><strong>It’s no longer enough to design what works. We need to design what’s right.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=933239b09754" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dead users]]></title>
            <link>https://justyna-belkevic.medium.com/dead-users-3c4b0bc0b20a?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c4b0bc0b20a</guid>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ethical-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Tue, 24 Mar 2026 10:21:08 GMT</pubDate>
            <atom:updated>2026-03-24T10:21:08.952Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What happens to your account when you die</strong></p><p>Thought-provoking short ethical design series: Article 7/10 <br><em>It’s no longer enough to design what works. We need to design what’s right.</em></p><p>Linda’s mother died on a Tuesday. By Thursday, she was on hold with customer service, trying to cancel a streaming subscription.</p><p>“I’ll need to verify the account holder’s identity,” the representative said, cheerful and scripted. “Can you provide the email address associated with the account?”</p><p>Linda provided it.</p><p>“And can you confirm the last four digits of the payment method?”</p><p>Linda didn’t know. It was her mother’s card. Her mother’s account. Her mother’s password, now locked in a phone Linda couldn’t unlock.</p><p>“I’m sorry,” the representative said, “but without verification, I can’t make changes to the account. Is there another way I could help you today?”</p><p>Linda hung up. The subscription charged again the following month. And the month after that.</p><h4><strong>The system doesn’t know you’re gone</strong></h4><p>Here’s the thing about most digital products: they have no concept of death.</p><p>They’re built for engagement, retention, lifetime value. The word “lifetime” is in there, but nobody thinks about what happens when the lifetime ends.</p><p>Your subscriptions keep charging. Your cloud storage keeps renewing. Your email keeps receiving. Your social profiles keep existing, sometimes surfacing in recommendations, memories, “people you may know.”</p><p>The product doesn’t know you’re dead. And it has no way to learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*N1cL6icX-32MRlX0" /><figcaption>Sunset in a forest</figcaption></figure><h4><strong>The grieving user isn’t in the persona</strong></h4><p>When we design products, we imagine users in all kinds of states. Happy, frustrated, confused, impatient. We design onboarding for the eager user, error states for the stuck user, cancellation flows for the departing user.</p><p>But we almost never design for the grieving user. The person who has to interact with your product not because they want to but because someone they loved used it, and now they’re gone.</p><p>This user doesn’t know the password. They don’t have access to the email. They may not even know the account exists until a charge shows up on a credit card statement or worse, until a “memory” notification surfaces a photo of the person they just buried.</p><p>We don’t design for this moment. So we leave grieving people to navigate systems that were never built to acknowledge death at all.</p><h4><strong>The digital afterlife is administrative hell</strong></h4><p>I started looking into what it actually takes to close a dead person’s accounts. The answer: it’s a mess.</p><p>Some platforms require a death certificate. Some require proof of executor status. Some require both, plus a notarized letter, plus a fax (yes, a fax!) to a department that responds in 6–8 weeks. Some platforms have no process at all. You submit a help ticket and hope.</p><p>Meanwhile, the charges keep coming. The recommendations keep surfacing. The “Your Memories” keep appearing in the feeds of people who are trying to grieve.</p><p>Apple requires a court order to access a deceased person’s device, even if you’re their spouse, even if you’re the executor of their estate. Facebook lets you “memorialize” an account, but the process is opaque and inconsistent. Google has an “Inactive Account Manager,” but only if the user set it up before they died. Most didn’t.</p><p>We’ve built a world where dying creates months of bureaucratic work for the people left behind. And we’ve designed almost none of it thoughtfully.</p><h4><strong>The algorithm doesn’t grieve</strong></h4><p>The cruelest part isn’t the subscriptions or the paperwork. It’s the automation.</p><p>A friend told me about receiving a push notification on the anniversary of her father’s death: “You have memories with David to look back on today!” The app didn’t know David was dead. The app was just running its engagement playbook.</p><p>LinkedIn sends connection suggestions for the deceased. Spotify keeps making playlists for users who will never listen. Duolingo sends passive-aggressive notifications to people who will never finish their streak.</p><p>The algorithm doesn’t know. The algorithm can’t know. It just keeps optimizing for engagement with a person who no longer exists.</p><p>And for the people who loved them, every automated notification is a small wound reopened.</p><h4><strong>What death-aware design might look like</strong></h4><p>I’m not saying every product needs to solve this. But some thought would help.</p><p><strong>Build death into the account lifecycle.</strong> It sounds morbid, but death is part of the lifecycle. An account can be active, dormant, or closed. Why not deceased? Create a clear, documented process for reporting a death and closing an account or at least stopping charges.</p><p><strong>Design for the person left behind.</strong> The grieving user isn’t the account holder. They don’t have the password. They’re emotionally overwhelmed. Make the process human: a real person to talk to, clear documentation of what’s needed, reasonable timelines.</p><p><strong>Consider the algorithm’s impact.</strong> If your product surfaces “memories” or recommendations, think about what happens when the person is gone. Can users proactively mark relationships? Can they tell the app “stop showing me this person”? Can you detect extended inactivity and pause the automation?</p><p><strong>Let people plan ahead.</strong> Google’s Inactive Account Manager is a good start. Let users designate someone who gets access (or control) when they’re gone. Digital estate planning should be built into more products, not bolted on after lawsuits.</p><p><strong>Default to dignity.</strong> When in doubt, err on the side of respect. Don’t make grieving people jump through hoops. Don’t send cheerful retention emails to the deceased. Don’t optimize for engagement with an account that will never engage again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CbLJOwhUuWoyzjhM" /><figcaption>Sunset on the beach</figcaption></figure><h4><strong>We all become dead users eventually</strong></h4><p>There’s a strange taboo around this topic. Product teams don’t like to talk about death. It’s uncomfortable. It’s morbid. It doesn’t fit neatly into a sprint.</p><p>But here’s the thing: every single one of your users will die. Every single account you create will eventually belong to someone who no longer exists. This isn’t an edge case. It’s the only guarantee.</p><p>And how your product handles that moment (or fails to) says everything about what you actually value.</p><p>Linda eventually got her mother’s subscription cancelled. It took three phone calls, a death certificate, a bank dispute, and two months. By the end, she was exhausted, not just by the grief, but by the friction.</p><p>The product probably didn’t mean to be cruel. Nobody designed it that way on purpose. But nobody designed it for death, either :/</p><p>And so the cruelty happened anyway.</p><p><strong>If you remember one thing:</strong></p><p>Your product will outlive some of your users.</p><p>Design like that matters. Because it does.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c4b0bc0b20a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“We designed it for safety” (and other lies)]]></title>
            <link>https://justyna-belkevic.medium.com/we-designed-it-for-safety-and-other-lies-cbf75302b74c?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbf75302b74c</guid>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[ethical-ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 18:14:34 GMT</pubDate>
            <atom:updated>2026-03-24T10:22:00.547Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>When protection is just control with better marketing</strong></p><blockquote>Thought-provoking short ethical design series: Article 6/10<br><em>It’s no longer enough to design what works. We need to design what’s right.</em></blockquote><p>Mia is sixteen. She’s also never alone.</p><p>Not physically, she has her own room, her own space, the normal privacy a teenager expects. But her phone has Life360 installed. Her parents can see where she is at any moment. They get alerts when she arrives at school, when she leaves, how fast the car was moving on the way home.</p><p>That part, she’s made peace with. What she doesn’t know is that the premium version her parents upgraded to also logs her phone’s battery percentage, notifies them when she removes the app, and (until recently) could show her location history for the past 30 days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*CDdHttZNUAzDO2X6TXhQUw.png" /><figcaption>A photo of a teenage girl.</figcaption></figure><p>What Mia also doesn’t know: Life360 was, until 2022, selling precise location data on tens of millions of users (including minors) to data brokers. The company marketed itself as “family safety.” It operated as a surveillance data business.</p><p>Her parents installed it because they love her. Life360 built it because they understood that love, when mixed with fear, is a very reliable monetization engine.</p><h4><strong>Safety as a selling point</strong></h4><p>“Safety” is one of the most powerful words in product design. It stops conversations. It justifies friction. It closes objections.</p><p><em>Why do I need to verify my identity three times?</em> Safety. <em>Why can’t I turn off location tracking?</em> Safety. <em>Why are you collecting this data?</em> Safety.</p><p>The word does so much work that we rarely stop to ask: safe for whom? Safe from what? And who decided?</p><p>When a company says they built something “for safety,” we’re meant to picture protection. A shield between us and harm. But often, what’s actually being protected is the company: from liability, from support costs, from the complexity of building something that genuinely keeps people safe without surveilling them.</p><h4><strong>The parental control paradox</strong></h4><p>The parental control industry is worth over $2 billion globally. It sells a simple promise: keep your kids safe online.</p><p>Here’s what that usually means in practice: track everything. Every app opened, every website visited, every message sent, every minute of screen time. Some apps screenshot the child’s phone at intervals. Some log keystrokes. Some flag “concerning” words using AI that can’t tell the difference between a cry for help and song lyrics.</p><p>The marketing shows worried parents and dangerous strangers. The product delivers a surveillance infrastructure that would be illegal if an employer installed it on your work phone.</p><p>And the research? It’s not great. Studies on teen mental health consistently find that excessive parental monitoring correlates with increased anxiety, decreased self-esteem, and, counterintuitively, more secretive behavior, not less. Kids with heavily monitored phones don’t make better decisions. They just get better at hiding.</p><p>Meanwhile, the same apps that promise to protect children from predators are often cavalier with that child’s data. Poorly secured APIs. Data shared with third parties. Location histories that could be goldmines for anyone who actually wanted to harm a minor.</p><p>Safety theater, performed for parents, funded by children’s privacy.</p><h4><strong>“For your security”</strong></h4><p>It’s not just parental controls. The safety-as-control pattern shows up everywhere.</p><p><em>For your security, we need your phone number.</em> (So we can use it for account recovery, ad targeting, and two-factor authentication that makes it harder for you to leave.)</p><p><em>For your protection, we limit what you can say.</em> (So we don’t have to moderate nuance, we just ban keywords and let the false positives sort themselves out.)</p><p><em>For safety reasons, you can’t download your data easily.</em> (Because making export easy would make leaving easy.)</p><p><em>To keep you safe, we verify your identity with a photo.</em> (Which we’ll store indefinitely and use to train facial recognition systems.)</p><p>I’m not saying security isn’t real. It is. Fraud exists. Predators exist. The internet has genuine dangers. But there’s a difference between security as a design principle and “security” as a magic word that ends discussions.</p><p>Real security is transparent about trade-offs. It gives users control. It collects the minimum necessary and deletes what it doesn’t need.</p><p>Fake security is vague about what it’s protecting you from, collects everything “just in case,” and makes it your problem if something goes wrong.</p><h4><strong>When safety means control</strong></h4><p>The darkest version of this pattern is when “safety” is used to control the people it claims to protect.</p><p>Domestic violence survivors have written extensively about how location-sharing apps (the same ones marketed for family safety) become tools of abuse. An abuser installs Life360 on a partner’s phone “so I know you’re safe.” Now they have 24/7 surveillance, and the app is designed to make secret removal almost impossible.</p><p>“Find My Friends” features get weaponized. Shared account “security” settings become monitoring tools. The products that promise protection become the infrastructure of control.</p><p>The designers who built these features weren’t thinking about abuse. That’s precisely the problem. When you design “safety” features without thinking about who might misuse them, and who’s most vulnerable to that misuse, you’re not designing for safety at all. You’re designing for the happy path and hoping the edge cases stay quiet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCBIaK9KxF-9EnIIsAmBnA.png" /><figcaption>Outdoor surveillance camera.</figcaption></figure><h4><strong>What real safety looks like</strong></h4><p>I don’t want to be purely cynical here. Genuine safety design exists. It just looks different from what we usually ship.</p><p><strong>Real safety is transparent.</strong> If you’re collecting data for security purposes, you explain exactly what, why, and for how long. You don’t hide behind vague language.</p><p><strong>Real safety gives control to the person being “protected.”</strong> A teenager should be able to see exactly what data a parental monitoring app collects, even if they can’t disable it. Informed powerlessness is different from invisible surveillance.</p><p><strong>Real safety considers abuse cases.</strong> Every feature that lets one person track, monitor, or control another should have a threat model that includes intimate partner violence. Every single one.</p><p><strong>Real safety minimizes collection.</strong> If you don’t need the data to provide the safety feature, you don’t collect it. Period.</p><p><strong>Real safety doesn’t monetize fear.</strong> The business model matters. If a company profits more when parents are more afraid, the product will make parents more afraid.</p><h4><strong>Mia figured it out</strong></h4><p>She’s seventeen now. Last year, she realized that Life360’s “ghost mode”, which the company added after backlash, still shares location data, just less frequently. So she started leaving her phone at a friend’s house when she wanted actual privacy.</p><p>Her parents think she’s exactly where her phone is. She’s learned that safety, as her phone defines it, was never really about her.</p><p>She’s not in danger. She’s not doing anything wrong. She’s just a teenager who discovered that the app designed to protect her was actually designed to reassure her parents, and profit from their anxiety.</p><p>That’s the thing about safety theater. Eventually, the audience figures out it’s a performance.</p><p>The question is what we’ve taught them by then. About trust. About privacy. About what “protection” really means when someone else holds the controls.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbf75302b74c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your app’s real manual is on TikTok]]></title>
            <link>https://justyna-belkevic.medium.com/why-every-app-has-a-secret-manual-on-tiktok-b10dcab8b73d?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/b10dcab8b73d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Fri, 19 Sep 2025 02:54:10 GMT</pubDate>
            <atom:updated>2026-01-29T17:58:09.025Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>🧠 Thought-Provoking Short Ethical Design Series: Article 5/10<br></em><strong><em>It’s no longer enough to design what works. We need to design what’s right.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/0*HnH94COxZ_lZFYrV.png" /><figcaption>What seemed like responsive support on Twitter was really just another feedback failure</figcaption></figure><p>Marcus has been staring at the same screen for twenty minutes.</p><p>He’s trying to cancel a subscription. The app says there’s a “Manage Subscription” option in settings. He’s looked three times. It’s not there. He tries the website. Different layout, same dead end. He Googles “how to cancel [app name].”</p><p>The first result isn’t the company’s help page. It’s a Reddit thread from eight months ago. The top comment, 847 upvotes:</p><p><em>“Go to Settings &gt; Account &gt; scroll ALL the way down past the blank space (yes there’s a blank space, keep scrolling) &gt; tap the gray text that says ‘subscription details’ &gt; wait for it to load (takes forever) &gt; THEN you’ll see cancel. Also don’t do it on the app, only works on mobile web. You’re welcome.”</em></p><p>Marcus follows the instructions. It works.</p><p>Somewhere, a product team thinks their cancellation flow is fine. Their metrics say so. But Marcus just mass search for answers to learn how to use their product from a stranger who mass search for answers eight months ago.</p><h3>The shadow help centre</h3><p>Every product has two sets of instructions.</p><p>There’s the official one, the help center, the onboarding flow, the tooltips, the carefully designed “user journey.”</p><p>Then there’s the real one. The Reddit threads. The TikTok walkthroughs. The Discord servers. The forum posts titled “AM I CRAZY OR IS THIS BROKEN?” with 200 replies saying “not crazy, here’s the workaround.”</p><p>I call this the shadow manual. It’s written by your users, for your users, because your official manual failed them.</p><h3><strong>I’ve been Marcus</strong></h3><p>I wish I could say I spotted this pattern through clever research. The truth is, I’ve been Marcus more times than I can count.</p><p>Last year I spent fifteen minutes trying to figure out why a design tool kept crashing when I exported. The help docs were useless. I found a YouTube video (2,000 views, some guy in his bedroom) explaining that you had to rename the file, remove special characters, export to a folder with a short path name, <em>then</em> it would work.</p><p>That video had more useful information than anything the company had published.</p><p>And I remember thinking: someone on that product team has no idea this video exists. They’re looking at dashboards, seeing successful exports, and assuming things are fine. Meanwhile, thousands of users are being taught how to use the product by a stranger who reverse-engineered its failures.</p><h3><strong>The unmeasured user</strong></h3><p>Here’s the thing about workarounds: they don’t show up in your data.</p><p>When Marcus finally cancels his subscription using the Reddit trick, your analytics just see a successful cancellation. Flow completed. No errors. The friction is invisible because Marcus found his own way through.</p><p>The users who don’t find the Reddit thread? They either give up (and you see churn, but you don’t know why) or they contact support (and you see a ticket, but maybe not the pattern). The ones who figure it out through sheer stubbornness? They just look like normal users.</p><p>This is how products end up optimizing for the wrong things. You’re measuring the people who got through. You’re not measuring what it cost them to get there.</p><h3><strong>The size of the shadow</strong></h3><p>This isn’t a small phenomenon. UberPeople, a forum for drivers, has over 200,000 members and millions of posts, years of documentation on how the app <em>actually</em> works from the people who use it eight hours a day. r/recruitinghell has 1.2 million members sharing screenshots of broken job applications, ghosted interviews, and ATS systems that seem designed to lose candidates.</p><p>These aren’t edge cases complaining. These are entire communities that exist because official channels failed them.</p><p>If your product has users, it probably has a shadow manual somewhere. The question is whether you’ve ever read it.</p><h3><strong>What the shadow manual tells you</strong></h3><p>When you find your shadow manual (and you should go looking) pay attention to what it reveals:</p><p><strong>Where the flow actually breaks.</strong> Not where you think it breaks. Not where QA tested. Where real humans, in real contexts, hit walls.</p><p><strong>What your help docs are missing.</strong> If a Reddit comment explains something better than your official documentation, that’s not a Reddit win. That’s your failure.</p><p><strong>Who your power users actually are.</strong> The people writing workaround guides aren’t complainers. They’re your most engaged users — engaged enough to figure out the solution AND share it with others. They’re doing your job for free.</p><p><strong>What you’ve normalized.</strong> The longest-running workaround threads reveal friction you’ve stopped seeing. If a hack has been circulating for two years, that’s a bug you’ve accidentally promoted to a feature.</p><h3><strong>A practical approach</strong></h3><p>If you want to take this seriously, here’s where to start:</p><p><strong>Find your shadow support.</strong> Search Reddit, TikTok, YouTube, and niche forums for your product name plus words like “how to,” “workaround,” “broken,” “help,” “finally figured out.” Bookmark 3–5 places where your users gather. Check them monthly.</p><p><strong>Track workarounds like bugs.</strong> When you find a workaround thread, log it. Treat “users discovered they need to do X to achieve Y” as a defect, not a quirk.</p><p><strong>Measure what silence costs.</strong> For new releases, track this: what percentage of first-time users complete the task without Googling, without contacting support, without external help? That’s your real success rate.</p><p><strong>Close the loop where it started.</strong> When you fix something that had a popular workaround, don’t just put it in release notes. Go back to the Reddit thread, the TikTok comment, the forum post. Tell them it’s fixed. Those communities remembered your failure, let them see you remembered too.</p><h3><strong>The point isn’t guilt</strong></h3><p>I’m not saying product teams are lazy or negligent. The shadow manual exists because measurement is hard and you can’t see everything.</p><p>But “we can’t see everything” isn’t the same as “we shouldn’t look.” The users writing workaround guides, making TikTok tutorials, answering each other’s questions in Discord, they’re doing user research for you. For free. In public.</p><p>The least we can do is pay attention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/0*6oI6ARjFNvjHWTbl" /><figcaption>Customer service meme</figcaption></figure><p><strong>Marcus moved on</strong></p><p>He cancelled the subscription. He probably won’t think about that app again. He definitely won’t fill out a feedback survey or file a support ticket.</p><p>But somewhere, his twenty minutes of frustration are now part of the product’s real story, the one that lives on Reddit instead of in the help center.</p><p>Your users are writing a manual for your product. The question is whether you’re reading it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b10dcab8b73d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fifty Shades of #767676]]></title>
            <link>https://justyna-belkevic.medium.com/fifty-shades-of-767676-eb0861ba25c7?source=rss-7d0191b99a30------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb0861ba25c7</guid>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Justyna Belkevic]]></dc:creator>
            <pubDate>Sat, 30 Aug 2025 05:51:38 GMT</pubDate>
            <atom:updated>2026-01-29T17:52:44.505Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The legal loophole that makes “accessible” meaningless</em></p><blockquote><em>🧠 Thought-Provoking Short Ethical Design Series: Article 4/10<br></em><strong><em>It’s no longer enough to design what </em>works<em>. We need to design what’s </em>right<em>.</em></strong></blockquote><p>Guillermo Robles just wanted a pizza. It was 2016, and he’d heard good things about Domino’s custom pizzas. As a blind man, he relied on his screen reader to navigate websites. But when he tried to order, something strange happened.</p><p>The screen reader could find the navigation. It could read the main headings. It announced “Pizza menu” perfectly. But when it came to actually customizing his pizza (choosing toppings, selecting a crust) the screen reader fell silent. The options were there, visually, in 10px light gray text. But to his assistive technology, they might as well not exist.</p><p>Guillermo called the store. They told him to use the website. He explained he couldn’t. They suggested he get someone else to help him.</p><p>He sued instead.</p><figure><img alt="A person making pizzas in a restaurant" src="https://cdn-images-1.medium.com/max/1024/1*nikOnQj02vXzKhG-1xE9RA.avif" /></figure><p>Domino’s fought back hard. They argued the Americans with Disabilities Act, written in 1990, couldn’t possibly apply to websites. They spent three years and millions of dollars fighting all the way to the Supreme Court to avoid making their website accessible.</p><p>They lost.</p><p>No single line of code made headlines. But the story did, because it revealed a truth designers already know: checking the boxes isn’t the same as a person completing a task.</p><h3><strong>The loophole isn’t the law. It’s how we use it.</strong></h3><p>On paper, we have rules. WCAG says: for normal text, meet a 4.5:1 contrast ratio; for large text, the ratio can be lower. These numbers are lifesavers when you’re aligning teams and vendors.</p><p>But numbers can become a shield. “Does this pass?” becomes more important than “Can people actually read this under glare, on a cheap phone, with aging eyes, while juggling real life?”</p><p>Every designer has heard the aesthetic version: <em>Can we make it a little lighter? A little smaller? It looks cleaner.</em></p><p>Year after year, low-contrast body copy is the most common accessibility failure on the web. We don’t set out to exclude people. We just keep sanding down legibility until the interface looks like a showroom car: beautiful under perfect lighting, undrivable in rain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xd_HS3gVzaV7ygeaviqRng.png" /><figcaption>WCAG colour contrast isn’t always accurate</figcaption></figure><h3>The meeting that happens every day</h3><p>You’ve probably sat in this one.</p><p>The team presents a flow: straightforward, roomy, readable. Body text at 16px. Clear labels. Strong contrast.</p><p>“We love the direction,” someone says. “We just need to tighten. The legal text feels… heavy. Can we make it smaller?”</p><p>The designer hesitates. “We can, but we’ll start losing people.”</p><p>“Will it still pass compliance?”</p><p>“Technically, yes.”</p><p>“Then make it smaller.”</p><p>No villainy. Just a series of micro-compromises that chip away at legibility first, because it’s the easiest thing to chip.</p><h3><strong>“Compliant” and unusable can coexist</strong></h3><p>Automated scanners help. They catch obvious issues: missing alt text, broken headings, color ratios. But there’s a reason accessibility practitioners keep warning that one-click “ADA-compliant” overlays don’t make a site usable.</p><p>A scan can’t tell you if a modal traps keyboard users. It can’t flag error text that appears only by color. It won’t notice that fine-print fees are tucked into dainty gray that passes a ratio but fails a human.</p><p>Meanwhile, the public sector has been inching toward better practice. In the EU, public-sector sites are monitored with methods that go beyond “run a tool and call it done”, they include deeper, manual checks. It’s not perfect, but it nudges teams closer to reality: accessibility is a craft, not a checkbox.</p><h3><strong>Who we’re actually designing for</strong></h3><p>We talk about “edge cases.” The older user with reading glasses. The commuter squinting through sun glare. The new parent running on two hours of sleep.</p><p>Those aren’t edge cases. That’s the center of real life.</p><p>When we shrink type or wash it with fashionable gray, we don’t just make a layout cleaner. We change who gets to finish a task.</p><p>And if your revenue model depends on people not noticing, not understanding, or not reading something, that’s not a design problem. That’s an ethics problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*RATtzUXDs46k4rzDpL3FUQ.jpeg" /><figcaption>Are you reading in the sun? It’s not always easy.</figcaption></figure><h3><strong>A field guide for teams who actually care</strong></h3><p>Not a checklist to hide behind. More like a compact oath for legibility.</p><p><strong>Start at 16px for body text.</strong> Treat it as the floor, not the ceiling. If your audience skews older or the UI is dense, scale up.</p><p><strong>Design for readability, not just ratios.</strong> Hit the contrast numbers, then test on a cheap phone in daylight, with system font scaling turned up.</p><p><strong>Reserve subtle gray for decorative moments.</strong> Never for essential copy. If it can cost money, change consent, or block progress, it should shout, not whisper.</p><p><strong>Test with assistive tech and with people.</strong> Keyboard only, screen readers, zoom. Ten minutes of real use beats ten pages of compliance screenshots.</p><p><strong>When you go smaller or lighter, write down why.</strong> If the only answer is “looks cleaner,” reconsider. Interfaces are used, not framed.</p><h3>The ending is boring on purpose</h3><p>Good accessibility stories rarely end with a court case. They end with someone getting through a form without thinking about it. With a person reading fee details before subscribing. With a blind customer ordering a pizza at midnight without calling a friend.</p><p>Make the text bigger. Strengthen the contrast. Choose clarity over clever. Then do the most radical thing in modern product design:</p><p>Ship the version people can actually read.</p><p>Because if your interface only <em>technically</em> works, it doesn’t work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*gn3oc1qWnb8uj0dRK99iPg.jpeg" /><figcaption>Grey colour palette.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb0861ba25c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>