[{"data":1,"prerenderedAt":243},["ShallowReactive",2],{"writing-article-\u002Fwriting\u002Fwhen-research-stops-being-useful":3,"writing-index":166},{"id":4,"title":5,"body":6,"cover":151,"coverAlt":151,"date":152,"description":12,"draft":153,"extension":154,"featured":153,"meta":155,"navigation":156,"path":157,"readingTime":158,"seo":159,"stem":160,"summary":161,"tags":162,"__hash__":165},"writing\u002Fwriting\u002Fwhen-research-stops-being-useful.md","When Research Stops Being Useful",{"type":7,"value":8,"toc":140},"minimark",[9,13,16,21,28,31,34,38,45,51,57,63,69,73,76,79,82,86,89,95,98,104,108,111,114,117,121,124,127,130,134,137],[10,11,12],"p",{},"A research report lands in the shared drive. It is thorough, well-structured and full of quotes. It has a persona, a journey map and seven themes. Three months later, nobody can remember what it said, and the roadmap looks exactly as it did before.",[10,14,15],{},"This is not a research failure. It is a decision failure, visible through research.",[17,18,20],"h2",{"id":19},"the-decision-test","The decision test",[10,22,23,24],{},"The most useful question to ask before any research is: ",[25,26,27],"em",{},"what decision will this inform?",[10,29,30],{},"Not “what will we learn?” Learning is good, but it is not a plan. The decision might be whether to build a particular workflow, which segment to target, how to price something, whether a problem is frequent enough to justify investment. If no decision depends on the answer, the research is likely to become content rather than evidence.",[10,32,33],{},"A good brief names the decision, the options, and what answer would change the team’s choice. It also names who will act on it and when. Without that, the research is a broadcast. With it, the research is a tool.",[17,35,37],{"id":36},"symptoms-of-decorative-research","Symptoms of decorative research",[10,39,40,44],{},[41,42,43],"strong",{},"The findings confirm the roadmap."," Every study seems to validate what the team already intended. This is a sign that the questions were shaped to protect the conclusion.",[10,46,47,50],{},[41,48,49],{},"The report is the deliverable."," The team measures success by whether the report was completed, not by whether anything changed.",[10,52,53,56],{},[41,54,55],{},"“We need more research.”"," Used as a way to delay a decision that is actually blocked by disagreement, not by missing information.",[10,58,59,62],{},[41,60,61],{},"The handoff."," Research is done by a specialist, summarised, and delivered to people who were not involved. By the time it arrives, the questions have moved.",[10,64,65,68],{},[41,66,67],{},"The persona."," A composite character with a name and a stock photo, standing in for a set of behaviours nobody has observed directly.",[17,70,72],{"id":71},"match-the-method-to-the-decision","Match the method to the decision",[10,74,75],{},"Research methods are not a hierarchy. They are tools with different costs and different strengths. The right method is the cheapest one that produces a decision-grade answer.",[10,77,78],{},"If the decision is whether people understand a label, five quick tests may be enough. If the decision is whether a workflow exists in a market, you may need a broader scan and a different kind of evidence. If the decision is whether to enter a segment, desk research and a handful of expert conversations may be more useful than another round of usability sessions.",[10,80,81],{},"The common mistake is to default to a familiar method, usually interviews, regardless of the question. Interviews are excellent for understanding context and language. They are poor at estimating frequency, measuring behaviour or predicting adoption.",[17,83,85],{"id":84},"synthesis-is-an-argument","Synthesis is an argument",[10,87,88],{},"A good synthesis does not just summarise; it makes a claim. It identifies the tension, names the pattern, and explains what it means for the decision.",[10,90,91,92],{},"The weakest synthesis is a list of themes with quotes attached. The strongest is a short argument: ",[25,93,94],{},"we found this pattern, it contradicts our assumption, and here is what we should do differently.",[10,96,97],{},"That argument should be falsifiable. If no conceivable finding would have changed the conclusion, the research was not testing anything.",[99,100,101],"blockquote",{},[10,102,103],{},"Research is useful when it makes a decision cheaper to make and harder to fake.",[17,105,107],{"id":106},"keep-it-close-to-the-team","Keep it close to the team",[10,109,110],{},"The further research travels from the people who will act on it, the more context it loses. A report that crosses three handoffs is a summary of a summary.",[10,112,113],{},"The alternative is not to eliminate specialists. It is to keep the team in contact with the raw material. A short clip from an interview. A support thread with the customer’s own words. A session recording watched together. A visiting customer in a team meeting.",[10,115,116],{},"Those moments are not a substitute for rigorous research. They are what makes the rigorous research land.",[17,118,120],{"id":119},"know-the-limits","Know the limits",[10,122,123],{},"Research describes the present. It can tell you how people behave now, what language they use, where the friction is, and what they have tried. It cannot tell you whether a market will exist in three years, whether a new behaviour will become a habit, or whether a competitor will change the terms.",[10,125,126],{},"Those are judgement calls, and they should be labelled as such. Pretending research can answer them produces false confidence; refusing to decide without it produces paralysis.",[10,128,129],{},"The useful posture is to be explicit about which questions are empirical and which are bets, and to fund them differently.",[17,131,133],{"id":132},"the-habit","The habit",[10,135,136],{},"The teams that get the most from research treat it as a habit rather than an event: small, frequent, close to the decision, with a clear owner and a visible consequence.",[10,138,139],{},"They also accept that some research will be inconclusive. That is not a failure. The failure is research that was never connected to anything, produced on schedule, and quietly ignored.",{"title":141,"searchDepth":142,"depth":142,"links":143},"",2,[144,145,146,147,148,149,150],{"id":19,"depth":142,"text":20},{"id":36,"depth":142,"text":37},{"id":71,"depth":142,"text":72},{"id":84,"depth":142,"text":85},{"id":106,"depth":142,"text":107},{"id":119,"depth":142,"text":120},{"id":132,"depth":142,"text":133},null,"2025-12-02",false,"md",{},true,"\u002Fwriting\u002Fwhen-research-stops-being-useful",4,{"title":5,"description":12},"writing\u002Fwhen-research-stops-being-useful","Research becomes decorative when it is disconnected from a decision. More interviews will not fix a team that has not agreed on what it is trying to learn.",[163,164],"research","discovery","HxvouVtLfHxK4fH7uYFt5pRnK9TD5j6ESkCZxlNuEWE",[167,175,184,190,196,202,208,216,222,224,230,237],{"path":168,"title":169,"summary":170,"date":171,"tags":172,"featured":156,"readingTime":158},"\u002Fwriting\u002Fwhat-ai-changes-about-product-work","What AI Changes About Product Work, and What It Doesn’t","The cost of producing a prototype, a spec or a synthesis has collapsed. The cost of knowing what is worth building has not. That gap is where product judgement now lives.","2026-11-04",[173,174],"ai","product-thinking",{"path":176,"title":177,"summary":178,"date":179,"tags":180,"featured":153,"readingTime":183},"\u002Fwriting\u002Froadmaps-are-arguments","Roadmaps Are Arguments, Not Schedules","A roadmap is a set of claims about why these problems, in this order, with these trade-offs. When it becomes a delivery calendar, the reasoning disappears and the promises take over.","2026-10-14",[181,182],"product-strategy","decision-making",3,{"path":185,"title":186,"summary":187,"date":188,"tags":189,"featured":153,"readingTime":158},"\u002Fwriting\u002Fdiscovery-is-a-budget","Discovery Is a Budget, Not a Phase","Treating discovery as a stage before delivery assumes uncertainty is front-loaded. It isn’t. Discovery works better as a recurring spend that every cycle pays into.","2026-09-23",[164,181],{"path":191,"title":192,"summary":193,"date":194,"tags":195,"featured":153,"readingTime":158},"\u002Fwriting\u002Fcost-of-a-decision-you-didnt-make","The Cost of a Decision You Didn’t Make","Deferred decisions feel safe because nothing visible happens. But indecision charges interest, in rework, lost context, and options that quietly expire.","2026-08-19",[182,174],{"path":197,"title":198,"summary":199,"date":200,"tags":201,"featured":153,"readingTime":183},"\u002Fwriting\u002Fthe-feature-was-never-the-problem","The Feature Was Never the Problem","A feature request is a compressed problem statement with the reasoning removed. If you ship the request without unpacking it, you often solve the smallest part of the problem.","2026-06-30",[174,164],{"path":203,"title":204,"summary":205,"date":206,"tags":207,"featured":153,"readingTime":183},"\u002Fwriting\u002Fprioritisation-is-about-evidence","Prioritisation Is a Story About Evidence","Frameworks like RICE do not make decisions. They make assumptions comparable. The quality of a prioritisation is the quality of the evidence and the honesty about what gets displaced.","2026-05-12",[181,182],{"path":209,"title":210,"summary":211,"date":212,"tags":213,"featured":153,"readingTime":158},"\u002Fwriting\u002Fstakeholders-are-not-obstacles","Stakeholders Are Not Obstacles","“Stakeholder management” often frames other people as friction. But they hold information the product team lacks. Treat them as co-owners of the constraint, not gatekeepers.","2026-03-24",[214,215],"practice","leadership",{"path":217,"title":218,"summary":219,"date":220,"tags":221,"featured":153,"readingTime":158},"\u002Fwriting\u002Fthe-quiet-power-of-constraint","The Quiet Power of a Good Constraint","Constraints are usually treated as obstacles. A good one narrows the search space, forces a real choice, and makes the work more honest.","2026-02-10",[174,181],{"path":157,"title":5,"summary":161,"date":152,"tags":223,"featured":153,"readingTime":158},[163,164],{"path":225,"title":226,"summary":227,"date":228,"tags":229,"featured":153,"readingTime":158},"\u002Fwriting\u002Fthe-product-review","The Product Review That Actually Changes the Product","Most product reviews are status meetings with slides. A useful one changes a decision, and that requires a different format, a different question set and a named owner.","2025-10-21",[214,182],{"path":231,"title":232,"summary":233,"date":234,"tags":235,"featured":153,"readingTime":183},"\u002Fwriting\u002Ftools-dont-make-the-product","Tools Don’t Make the Product","A new tool cannot fix an undefined workflow. It usually makes the disagreement faster, more visible and more expensive.","2025-09-09",[236,214],"tools",{"path":238,"title":239,"summary":240,"date":241,"tags":242,"featured":153,"readingTime":158},"\u002Fwriting\u002Foutcomes-are-a-habit","Outcomes Are a Habit, Not a Metric","Teams say they are outcome-driven but manage by output because output is legible. Outcomes require a cadence of looking at behaviour and the discipline to change course.","2025-07-15",[181,214],1795010564354]