--- title: A Research Summary of Where Discovery-Phase Findings Actually Land Inside Organisations description: Most discovery research never shapes decisions. This summary covers why findings get ignored and what you can do to make them land at handover. image: https://weareaffective.com/hubfs/learning-centre-images/a-research-summary-of-where-discovery-phase-findings-actually-land-inside-organisations.webp --- [Skip to content](https://weareaffective.com/learning-centre/a-research-summary-of-where-discovery-phase-findings-actually-land-inside-organi#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 # A Research Summary of Where Discovery-Phase Findings Actually Land Inside Organisations Table of Contents User research is expensive to run well. It takes time, care, and real [access to the people who will eventually use the product](https://weareaffective.com/app-user-research). So the question that follows every discovery phase is not whether the findings are good, but whether they go anywhere. That question is less comfortable than it sounds, because the honest answer, at least according to the data, is that they usually do not. > Good research rarely fails inside the process. It fails at the point of handover. The Dovetail State of User Research report from 2022-23 found that around 60% of researchers said their work was sometimes or rarely acted upon. Around 40% of those cited lack of stakeholder engagement as the primary reason. These are numbers about what happens after the research room closes and the findings get handed over to the people who commission the work in the first place. We have sat in enough debrief meetings to know that the research itself is rarely what goes wrong. What goes wrong is the conditions the research lands into: who is holding it, what they were hoping it would say, and [whether there was ever a genuine intention to act](https://weareaffective.com/learning-centre/what-does-good-ux-research-actually-look-like-at-seed-stage). This article brings together the published data on research uptake, and the patterns we have observed doing this work, to give a clearer picture of where findings actually land inside organisations and what determines whether they travel. ## What the Numbers Actually Say The published numbers on research uptake are not encouraging, and they are consistent across sources. Nielsen Norman Group data suggests that in lower-maturity organisations, fewer than 20% of research findings result in a documented product change. As organisations mature, that figure increases, but does not reach 50% even in more established companies. That means even in a well-resourced, research-aware business, the majority of findings do not produce a traceable decision. A 2022 survey by UserZoom and Ipsos found that around 72% of product decisions were made without user research informing them at all. This is a different figure from the one above. It does not mean research was conducted and then set aside. It means [most product decisions happen with no user data involved](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-) at any stage. Discovery phases and the decisions that follow them are, for most organisations, parallel tracks that rarely connect. #### What organisational maturity actually means here Research maturity is measured by whether the organisation treats findings as inputs to decisions or as outputs of a compliance exercise. Lower-maturity organisations tend to commission research as a deliverable, something to show exists, rather than as something to use. The research gets filed, the project continues on its original course, and the connection between the two is never made. The maturity gap is, at root, an attitude gap. ## Why Most Findings Die at the Handover We walked away from one engagement because the conditions for research to land were never present. A founder had very strong opinions about how a product should work, and the research commission was, in practice, a box-ticking exercise. When we showed compelling evidence that large portions of their potential user base did not want particular features and actively preferred alternatives, the findings were set aside. The founder launched a product roughly a year later that was largely unchanged from the original plan. By our account, it failed, and it failed for the same reasons the research had flagged. That story is not unusual in structure, only in how far it went before we recognised what was happening. A stakeholder who enters the research process already certain of what they want to build is not going to change course on the strength of a debrief document. The process cannot override the posture. We have never seen a research process fail because the methodology was wrong or the documentation was weak. When findings die at the handover, the cause is always political or attitudinal. The 40% of researchers in the Dovetail report who cited lack of stakeholder engagement as the primary reason their work went unused are describing the same thing: not a gap in the research, but a gap in the intention to act on it. ## Design that understands *your* users We build app experiences around real user behaviour, not assumptions. Research, psychology-driven design and technical specs that turn users into loyal advocates. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## The Difference Between Ignored Research and Research That Was Never Going to Land There is a distinction worth holding between research that gets ignored after a genuine attempt to integrate it, and research that was never going to land regardless of what it found. The second category is more common than it appears, and it is recognisable before the debrief if you know what to look for. A pre-launch founder in the football industry came to us with a colour-coded spreadsheet mapping competitor products, with the aim of merging multiple tools into one. They were visibly excited. When we began asking questions about prospective users, specifically why someone would choose an all-in-one product over specialised apps, and whether consolidation risked weakening individual features, the energy in the room dropped. The founder had not yet spoken to a single potential user. The spreadsheet provided immediate validation of their own position, and nothing in it could contradict them. That is what competitive feature mapping does when it stands in for user research: it produces a document that agrees with you. > A spreadsheet that no one can argue with is insulation, not evidence. Founders and product leads in this position are not being dishonest. There is a real fear underneath it: that research might reveal the idea is wrong, or that [nobody actually wants the product](https://weareaffective.com/learning-centre/how-to-structure-a-behavioural-risk-register-before-you-write-a-single-user-stor). Commissioning research in that state of mind produces a process designed to surface confirmatory data and route around anything that does not fit. Distinguishing that from genuine openness is something that has to happen before the research starts, not after the findings are in. ## What Happens When Discovery Is Skipped or Staged On a dating app project we ran, the decision was made to skip discovery on the messaging component and move straight into build. The reasoning at the time was practical: messaging seemed like a standard feature, the timeline was tight, and the team felt confident they understood what was needed. That confidence was wrong. The [messaging section had to be rewritten from scratch](https://weareaffective.com/learning-centre/why-product-owners-should-write-the-users-second-session-before-the-first-one), and the cost of skipping discovery on that one component was approximately £15,000 in additional budget and two months of additional work. That figure is what a single skipped discovery phase cost on a single section of one product. And it does not include the downstream cost of launching with a messaging experience that did not serve users well during the period before the rewrite was completed. #### Staged discovery is a different problem Discovery gets staged, rather than skipped, when teams go through the motions of research with no genuine intention of letting it inform decisions. This is harder to see from inside the project because the documentation exists, the sessions happen, and the debrief gets written. The problem only becomes visible when the post-research decisions look identical to the pre-research plan. Staged discovery has all the cost of real discovery and produces none of its value. The difference between them is not process structure but the attitude in the room before the first participant speaks. Before commissioning discovery, ask each decision-maker to write down, privately, what they expect the research to find. If the answers are identical to the current product plan, the conditions for the research to land are not yet present. Surface that before the sessions begin, not after. ## How Emotional Framing Changes Whether Findings Survive One of the consistent patterns we see is that findings framed purely as functional observations get deprioritised faster than findings framed around user experience and emotional state. A finding that says "users struggled to locate the navigation" is easier to dispute, defer, or shelve than one that maps the emotional arc of the experience and says "users felt confused and then embarrassed, which they attributed to the product rather than themselves." The second version is harder to set aside because it describes something human and recognisable, and because it connects to outcomes that matter to the business. Simon's reframe of the word 'intuitive' captures this well: when someone says a product is intuitive, they are almost always describing something beyond the interface mechanics. They are describing how the product made them feel, [whether they felt exasperated, whether they felt comprehended](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you), whether they felt guided or abandoned. Functional findings that miss this layer give stakeholders a narrow target to argue against. Emotional findings give them a fuller picture of what is actually happening. On the concierge app project we ran, focus groups included residents from social housing, a group that was not the target market. What we found was that these participants were having meaningful, substantive conversations with each other, not superficial exchanges, and that this depth was what produced a genuine sense of community. That finding shaped our strategic recommendation: the app should handle the transactional and mundane, maintenance requests, fire drill procedures, recycling locations, while actively encouraging the kinds of deeper human conversation that the app was at risk of replacing. When writing up discovery findings, document the emotional state of the user at each stage, not just what they did or failed to do. A finding that names a feeling, frustration, relief, embarrassment, trust, is significantly harder to dismiss than one that names a click path. ## Structuring Findings So They Travel Without You Research findings often die not because stakeholders reject them, but because they stop travelling once the researcher is out of the room. A debrief presentation works well in the moment, with context available and questions answerable, and then loses coherence as it gets forwarded, summarised, or referenced weeks later by people who were not in the original session. The findings arrive at a decision point stripped of the texture that made them compelling. Among the key artefacts we produce after a discovery phase are documents that map the emotional arc of users through a product or feature experience. These sit alongside [brand personality documents that capture how the brand communicates](https://weareaffective.com/learning-centre/why-does-our-competitor-feel-more-trusted-even-when-our-product-is-better) with people and what emotional register it operates in. The purpose is to produce something that a developer, a designer, or a product lead can pick up without us in the room and still understand what the research was saying and why it should change their next decision. #### What makes a finding portable A finding travels well when it is specific, when it names the emotional state rather than just the behaviour, when it connects to a business outcome the reader cares about, and when the action it implies is clear. Compare these two versions of the same observation: | Version | What it says | Whether it travels | | --- | --- | --- | | Functional | Users took longer than expected to find the settings menu | Deprioritised easily, no emotional weight | | Emotional arc | Users felt embarrassed when they could not find settings, which they attributed to their own competence rather than the product's design | Harder to set aside, [connects to brand trust](https://weareaffective.com/learning-centre/what-makes-users-trust-a-product-enough-to-enter-their-card-details) | The second version does not require you to be in the room to make the case. It makes it itself. ## What Brand and Experience Leads Can Control at the Point of Handover Brand and experience leads rarely control whether a stakeholder enters the research process in good faith. What they can control is the format, framing, and sequencing of findings at the point of handover, and that has a meaningful effect on whether the findings survive the first few meetings they are not present for. On the concierge app project, we recommended drip-fed, context-sensitive notifications rather than the default approach of delivering all information upfront. The client accepted the recommendation. Subsequent A/B testing and research with real users confirmed it was the right call: users who received the delayed notifications reported measurably lower stress levels than those who did not. Notifications that arrived in context were perceived as helpful prompts rather than demands for urgent attention. That recommendation came from discovery findings, and it landed because we brought the evidence in a form that the client could connect directly to a business outcome. Where a finding touches a significant or structural change, and stakeholders have concerns about sample size, the right move is to table those specific points and run large-scale quantitative validation through predefined surveys. This shifts the conversation from "how many people told you this" to "here is what a much larger sample confirmed." It is a sequencing decision that gives the finding the best possible chance of surviving into implementation. At the point of handover, present findings in order of their potential business impact rather than in the order they emerged from the research. Stakeholders who are sceptical of research will engage with a finding that connects to revenue, retention, or risk before they will engage with one that does not. ## Conclusion The research uptake problem is not primarily a research quality problem. The findings die at the handover, or before it, because the conditions for them to land were never created. A stakeholder who enters the process certain of what they want to build, a discovery phase commissioned to produce a deliverable rather than inform a decision, a set of findings formatted to survive a debrief and nothing else: these are the real causes, and none of them are solved by better methodology or more rigorous documentation. What can be changed is the framing, the format, and the sequencing of how findings are presented. Research that maps emotional arcs rather than just behaviours travels further without the researcher in the room. Findings ordered by business impact get read by people who are sceptical of research. Quantitative validation gives structural findings the weight they need to survive a stakeholder who disputes the sample. These are what research that actually lands looks like in practice. The starting point is honesty about the conditions the research is going into. Not every commission is made in good faith, and recognising that early, as we had to on the engagement we eventually walked away from, is a better outcome than completing a process that was designed to produce a document rather than a decision. Discovery that shapes what gets built is harder to run than discovery that produces a report. It is also the only kind worth running. If you are working through where your discovery findings are actually landing, and what might be getting in the way, [start the conversation with us](https://weareaffective.com/get-started). ## Frequently Asked Questions How often does user research actually lead to product changes? Nielsen Norman Group data suggests that in lower-maturity organisations, fewer than 20% of research findings result in a documented product change. Even in more established, research-aware businesses, that figure does not reach 50%, meaning the majority of findings do not produce a traceable decision. Why do so many product decisions get made without user research? A 2022 survey by UserZoom and Ipsos found that around 72% of product decisions were made with no user research involved at any stage. Discovery phases and the decisions that follow them tend to run as parallel tracks that rarely connect, rather than feeding directly into one another. What is the most common reason research findings are not acted upon? According to the Dovetail State of User Research report from 2022 to 2023, around 40% of researchers cited lack of stakeholder engagement as the primary reason their work was not acted upon. The research itself rarely fails. The conditions it lands into are what determines whether it travels. What does 'research maturity' mean in practical terms? Research maturity refers to whether an organisation treats findings as genuine inputs to decisions or simply as outputs of a compliance exercise. Lower-maturity organisations tend to commission research as a deliverable to show exists, rather than something to use, and the connection between findings and product direction is rarely made. Can good research still fail to make an impact even when the findings are strong? Yes, and this is one of the more uncomfortable patterns the data points to. Compelling evidence can be set aside entirely if stakeholders had already decided on a direction or commissioned the research as a box-ticking exercise rather than a genuine enquiry. At what point in the process do findings most commonly get lost? Findings most commonly get lost at the point of handover, after the research phase closes and the work is passed to the people who commissioned it. What happens in that handover depends on who is holding the findings, what they were hoping to hear, and whether there was ever a genuine intention to act. Is commissioning user research enough to ensure it influences a product? No. Commissioning research and actually using it are two separate things, and the data suggests they are often treated that way inside organisations. Without the right conditions in place before the work begins, research can be completed to a high standard and still have no effect on the product direction. What tends to happen in organisations where research is treated as a compliance exercise? In those organisations, the research gets filed, the project continues on its original course, and no meaningful connection is made between the findings and the decisions that follow. The pattern often repeats across projects without being recognised as a structural problem. ## 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.