--- title: The Trade-Off Between Education and Anxiety on Any Health-Adjacent Product description: Health products trigger anxiety before results even arrive. Learn how to balance plain language with science to inform without overwhelming your audience. image: https://weareaffective.com/hubfs/learning-centre-images/the-trade-off-between-education-and-anxiety-on-any-health-adjacent-product.webp --- [Skip to content](https://weareaffective.com/learning-centre/the-trade-off-between-education-and-anxiety-on-any-health-adjacent-product#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # The Trade-Off Between Education and Anxiety on Any Health-Adjacent Product Table of Contents Someone posts off a saliva sample, waits three weeks, and then opens an app on the bus home to find out how their body is ageing. They are not relaxed. They have paid money, handed over something personal, and they are about to read a sentence about themselves that they cannot argue with. We worked on a genetics product where that exact moment was the whole design problem. The client wanted the full medical picture on the first screen, because the science behind the product was strong and they were rightly proud of it. Our concern was what a screen like that does to a person who is already tense before the app has loaded. > Language that is too simple reads as thin, and language that is too technical reads as closed. So the work became a trade-off between two real risks. Educate people enough that the result carries meaning, and stop short of the point where their [anxiety rises and they put the phone down](https://weareaffective.com/learning-centre/why-a-wellness-products-education-layer-has-to-be-designed-around-anxiety-not-ar). Both failures look the same in the data, because in both cases people leave. What follows is where we have found that line on real projects, what the testing told us, and what we do differently now on any product that sits anywhere near health. ## Why Health Products Carry Anxiety Before Anyone Opens Them Users arriving at a genetics product already carry a degree of anxiety, and nothing in the interface put it there. It travelled with them. They are thinking about their parents, their weight, a thing the doctor said two years ago, and whether this app is about to confirm it. That changes the starting point for design. A shopping app can assume a fairly neutral user who wants a jumper. A health-adjacent product has to assume someone who is braced. On a healthcare and health insurance product we designed for African markets, we built from that assumption deliberately. People open a cover app because something has happened or because they are worried something will. Every decision we made, from the screen colours to the length of a sentence, was judged on whether it brought that feeling down. Simon puts the diagnosis well. When someone says your product is not intuitive, they are almost never talking about the interface, they are talking about [how the product makes them feel using it](https://weareaffective.com/user-psychology-app-design). On a health product that feeling is usually some version of exposure. So the first question is not what the data says. The first question is what emotional state the person is in as the screen appears, because that state decides how much they can take in. ## What Too Much Medical Language Actually Does We ran user testing on a health and wellness product dealing with test results, and we went in expecting science-heavy screens to raise credibility. The opposite happened. People felt they could not trust the product because they did not understand it, so the depth we had added as proof was read as a wall. That finding reset how we think about rigour. Scientific detail only reads as credible to someone who has already understood the headline. Shown first, it reads as something written for a different person, and the user quietly decides the product is not for them. There is published work pointing the same way. In a usability study of personal genomics reports published by [PMC / National Institutes of Health](https://pmc.ncbi.nlm.nih.gov/articles/PMC4526936/), about half of participants commented on technical jargon and found it difficult to understand. Anxiety does the rest. A worried reader meeting a word they do not know assumes the worst version of what it means. So the medical register raises the emotional temperature and lowers comprehension at the same time, which is the pair of outcomes you least want on a results screen. ## UX/UI design built around *real* psychology We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## Why Oversimplifying Loses Trust Instead of Building It From our work on the genetics product, we found the other edge just as sharply. Strip the language back too far and [people stop believing there is any real science underneath](https://weareaffective.com/learning-centre/why-your-social-media-app-needs-more-than-just-pretty-design). The copy starts to sound like a horoscope, and a horoscope is free. People paid for a test. They expect the answer to feel earned. A single friendly line with nothing behind it reads as a brand talking, and they go looking for the part where someone shows their working. > Simplification that removes the science also removes the reason to believe the result. That gap is common in the category. A content analysis of 29 direct-to-consumer genetic testing websites, published by [PubMed Central / NCBI](https://pmc.ncbi.nlm.nih.gov/articles/PMC2997043/table/T2/), found only 38% provided scientific evidence or data to support the markers they tested for. Transparency about risk works the same way. Being open about what a result cannot tell you is critical, and it has to sit next to the benefit of knowing. Lead with risk alone and the transparency becomes overly transparent, and people switch off before they reach the reason the test was worth doing. ## Finding the Narrow Band Between the Two The useful register sits in a narrow band, and both walls are close. Our rule from the genetics work is that plain language carries the user through the product, while the medical depth stays available for anyone who wants to go and get it. The science lends credibility underneath without being a condition of entry. Written out, the three registers behave very differently. | Register | How it reads | What the user does | Effect on trust | | --- | --- | --- | --- | | Too plain | Thin, like marketing | Doubts the result, goes looking elsewhere | Falls, no proof in sight | | The narrow band | Clear, with depth behind it | Reads on, taps through for more | Builds with each layer | | Too medical | Closed, written for a clinician | Stops, closes the app | Falls, nothing can be checked | Take one results screen and read every element back as a question. What state is the person in as they read this, and does this line reduce that feeling or add to it? Anything that only adds complexity has a better home deeper in the journey. The band moves by product and by audience, so we [treat it as something to find by testing](https://weareaffective.com/learning-centre/why-your-app-needs-real-users-not-just-your-mums-opinion) rather than something to decide in a workshop. What stays constant is the shape. Plain first, depth within reach, nothing compulsory. ## Layering Information by Emotional State, Not Product Logic Most layering gets designed around how the data is structured, because that is how the back end is built and it feels tidy. On a health and wellness product we worked on, we built the layering around reducing anxiety instead, which produced a completely different order. The top layer used very simple metaphors about the human body. Easy pictures, no markers, no percentages. Science arrived underneath, for people who went looking. The sequence we landed on ran roughly like this. 1. What this part of the body does, in everyday terms 2. What your result says, in one sentence 3. What it means for an ordinary week 4. Why variation here is normal 5. The science, the markers and the method, on request Simon describes the principle as understanding what state somebody is coming into the product with, then [designing the layering on that emotional response](https://weareaffective.com/learning-centre/how-to-tell-whether-your-digital-problem-is-a-format-problem-or-a-brief-problem) rather than on what makes sense from a product point of view. High stress and high anxiety call for stripping back and educating, because education is what brings the level down. Joy or excitement would justify a different order entirely. A fitness product celebrating a personal best can afford to open with the number, because nobody is frightened of it. ## Plain Language First, Science on Demand On the same health and wellness product, we changed the order so the science came in slowly, after people understood their key results. Credibility went up. The detail now backed up something the user already held, so it read as confirmation rather than as a test they had failed. That is the practical form of the trade-off. One readable layer that everyone gets, and a deeper layer that a smaller group chooses. Nobody is blocked, and nobody who wants the method is denied it. The category mostly does not work this way. In the same analysis of 29 direct-to-consumer genetic testing sites from [PubMed Central / NCBI](https://pmc.ncbi.nlm.nih.gov/articles/PMC2997043/table/T4/), only 7% mostly used common language and explained their technical terms, with a mean SMOG reading level of 14.7. Real-world analogies did a lot for us on the genetics product. A sentence about how a system in the body behaves, framed around something a person already understands, carried the principle without asking anyone to learn a new word first. The medical copy still gets written. It sits one tap away, properly sourced, for the user who wants to check us. ## Pre-Framing Results So Nothing Reads as an Error On the genetics wellness app, people were hitting results that did not match how they saw themselves, and reading that mismatch as a fault in the report. A perfectly accurate screen was being received as a bug. So we rewrote the copy to get there first. Before the result appeared, the product said that variation is expected and that everyone is different, so the surprising number arrived already explained. > The best error message is the one a user never needs to see, because the copy got there first. Framing something before it happens is a quieter piece of design than an alert, and it does more. An alert tells someone there is a problem. Pre-framing means the problem never forms in their head, so their anxiety never spikes and they carry on reading. We now treat this as a standard pass on any health-adjacent results flow. Every screen gets checked for the result a person might read as wrong, alarming or personally insulting, and the copy immediately before it gets written to absorb that. List the three results your product delivers that people are most likely to reject. Write the sentence that comes before each one, not the one that comes after. ## Narrative as the Thing That Makes Data Make Sense Our audit of the genetics wellness app found something the client did not expect. The brand promise was sound. The narrative on offer, a real inside look at how your body works, how it is ageing and how you can improve it, was compelling and well built. The product had lost it. Built largely by a developer team, the app delivered the data accurately and had stripped out the storytelling along the way. Every screen worked and nothing connected. People were not forming any emotional relationship with their own results, and retention showed it. A number on a screen with no story around it is just a number, and nobody comes back to look at it twice. So the decision the audit forced was to reintroduce narrative and give people a sense of identity inside the product, rather than touching the brand promise at all. The promise was already the right one. It had simply stopped appearing after the point of purchase. Narrative also carries the educational load. A story about what a system in the body is doing teaches more, in fewer words, than a labelled chart, and it leaves the reader calmer than they were when they started. ## When the Brand Promise and the Product Say Different Things We worked on a mobile app in the health and wellness genetics sector where the brand and the product were telling two different stories. The packaging and the online presence were luxurious and aspirational, all about transformation, becoming a better version of yourself and reaching your full potential. Then the app opened, and it was cold and clinical. Functional copy, functional design, nothing of the promise that sold the kit. Think about that journey from the user's side. Aspirational marketing, a considered purchase, a kit through the letterbox, a test taken at the kitchen table, three weeks of waiting, and then a screen that speaks like a lab printout. The experience was jarring at exactly the moment it mattered most. Tonal mismatch is an anxiety problem as much as a brand problem. The person has been promised care, and the product withholds it precisely when they are most exposed. That drop registers emotionally before anyone works out why. [Consistency of tone across the whole journey](https://weareaffective.com/learning-centre/how-to-write-app-marketing-emails-that-people-actually-want-to-read) is doing more than looking neat. It tells someone the brand that talked to them warmly on the box is the same brand reading them their results. ## Testing It: Focus Groups, Five-Second Tests and Comprehension Scores None of this gets settled by opinion in a room, so on the genetics wellness app we measured it. [We ran focus groups and five-second tests](https://weareaffective.com/learning-centre/what-a-fitness-social-app-changed-when-it-realised-precise-location-was-the-wron) on the copy and narrative before and after the rewrite. The first round was sobering. The product held a great deal of content and let people fall into error states, and comprehension scores came back low. We then rewrote it into a far more narrative experience, pre-framed the results people were likely to misread, and ran a second round. Clarity, sense of purpose and retention all came back much higher after changes Simon describes as subtle but quite profound. The things worth measuring on a health product are fairly short to list. - Comprehension, in the user's own words, not multiple choice - Clarity of what the screen is asking of them - Whether they can say why the product exists - What they retain a day later - How they feel reading it, asked directly Attention is short, which makes this urgent. In a study of personal genomics reports published by [PMC / National Institutes of Health](https://pmc.ncbi.nlm.nih.gov/articles/PMC4526936/), participants spent just over 12 minutes on average exploring their reports. Run your five-second test on the results screen, not the homepage. The homepage rarely decides whether somebody trusts you. ## Handling Stakeholders Who Want the Data Shown First On the health and wellness product we worked on, there was a firm push from the people who understood the science to go straight in and show the results. Show the data, show the information, let the quality speak. That instinct comes from pride in the work, and it is usually held by the most knowledgeable person in the room. What actually needs to happen is emotional framing first, so people meet that content with the basics in place and their anxiety falling rather than climbing. > Data lands on a calm reader and bounces off an anxious one. Arguing that in the abstract rarely works. On the genetics product, the client's preference was for full medical detail as the default, and our preference was to strip it back and let people explore the depth if they wanted it. User testing settled it, and the testing pointed clearly to the layered version, which produced higher comprehension and lower anxiety among participants. So we now put the disagreement into testing early rather than debating it. Build both versions of the results screen, show them to real users, and let the comprehension scores make the case. Nobody loses an argument, and the science still gets its place. ## Tone, Colour and the Non-Verbal Signals of Calm Copy is only part of how a product sets someone's emotional state. On the healthcare and health insurance product we designed for African markets, the visual decisions were made for the same reason as the language, which was to settle a person who arrives already heightened. We went for a dark UI with green undertones. Green carries associations of calm, safety and medical support, and it does that work before anyone reads a word. We kept it deliberately away from a clinical look, because clinical reads as hospital, and hospital is the association we were trying to avoid. Language across the product was very specific and very simplified, with the medical jargon stripped out, so people came away feeling looked after rather than tested. The non-verbal signals carry more than teams expect. Spacing, pace, the weight of a typeface and the speed of a transition all tell someone whether this product is rushing them. A results screen that fades in gently says something different from one that snaps. Mute the copy on your results screen and look at it cold. If the colours and spacing alone feel like a clinic, the words are already fighting uphill. ## Applying the Trade-Off to Other Health-Adjacent Products Genetics is the clearest case, and the same trade-off runs through anything that touches the body. A supplements brand listing active ingredients and dosages faces it on every product page. Too little and the formula looks made up, too much and the shopper gives up on the fourth Latin name. Skincare has the same problem with actives and percentages. A fitness tracker has it with recovery scores, which are read as judgements on how well someone is living. Pet products carry it too, because an owner reading about their dog's joints is as anxious as any patient, and sometimes more. Food and drink hits it around allergens and nutrition, where the legal requirement to be complete sits awkwardly against the need to be calm and readable. The method transfers cleanly. Work out the emotional state someone arrives in, write the plain layer first, keep the science one tap away, pre-frame whatever people are likely to read as bad news, and test comprehension rather than preference. What changes between categories is how much anxiety there is to manage. What does not change is that the science still has to be present, visible to anyone who wants it, and never the price of entry. ## Conclusion The trade-off between education and anxiety does not resolve into a rule you can apply once. It is a band, it is narrow, and it moves with the audience and the stakes of the product. What we have taken from the genetics product, the test results product, the wellness app rewrite and the health insurance work for African markets is a consistent shape. Plain language carries everyone through. Metaphors about the body do the teaching at the top level. Science sits underneath, available and sourced, lending credibility without demanding anything. Results that people may read as errors get framed before they appear. Narrative holds the whole thing together so the data means something to the person reading it. And when the room disagrees, which it will, testing decides. Our clearest results came from running both versions past real users and watching comprehension rise while anxiety fell. If you are building something that sits near health and you are weighing how much to show and when, we are happy to talk it through. [Let's talk about your health product and where the line sits](https://weareaffective.com/get-started). ## Frequently Asked Questions Why do health-adjacent products carry anxiety before anyone even opens them? People arrive at health products already worried about something, a family history, a weight concern, or a comment a doctor made years ago. The interface did not create that feeling, it travelled with them, so design has to assume a braced user rather than a neutral one. Doesn't more scientific detail make a product look more credible? Not when it appears first. In our user testing, science-heavy screens actually lowered trust because people felt they could not understand what they were reading, so the depth we added as proof came across as a wall. Scientific detail only reads as credible once someone has already grasped the headline. What is the actual trade-off being described here? You need to educate people enough that a result carries real meaning, while stopping short of the point where anxiety rises and they abandon the product. Both failures, too little information and too much, look identical in the analytics because in both cases the user leaves. How do I know whether my language is too simple or too technical? Language that is too simple reads as thin and makes the product feel unserious, while language that is too technical reads as closed and makes the user feel the product was written for someone else. Testing with real users is the only reliable way to find the line, because the balance shifts with the subject and the audience. What happens when an anxious reader meets a word they do not understand? They assume the worst possible meaning. That is why medical register raises the emotional temperature rather than lowering it, and why unexplained jargon is particularly costly on health products compared with other categories. Is there any research backing this up, or is it just design opinion? There is published evidence pointing the same way. A usability study of personal genomics reports published through the National Institutes of Health found that around half of participants commented on technical jargon and found it difficult to understand. When someone says my product is not intuitive, what are they usually complaining about? They are almost never describing a layout or navigation problem. They are describing how the product makes them feel while using it, and on a health product that feeling is usually some form of exposure. Where should I start if I am designing a health or wellness product? Start with the emotional state of the person as the screen loads, not with what the data says. That state determines how much information they can absorb, so judge every decision, from colour to sentence length, on whether it brings the anxiety down. ## Related Articles [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.