[{"data":1,"prerenderedAt":343},["ShallowReactive",2],{"post-\u002Fblog\u002Fdiscovery-in-one-week":3,"post-related-\u002Fblog\u002Fdiscovery-in-one-week":318,"post-translations-\u002Fblog\u002Fdiscovery-in-one-week":330,"post-surround-\u002Fblog\u002Fdiscovery-in-one-week":332},{"id":4,"title":5,"body":6,"category":299,"date":300,"description":301,"draft":302,"extension":303,"featured":302,"meta":304,"navigation":305,"path":306,"readingTime":288,"segment":307,"seo":308,"stem":309,"tags":310,"translationKey":315,"updated":316,"__hash__":317},"blog_en\u002Fblog\u002Fdiscovery-in-one-week.md","Discovery in one week: from problem to testable prototype",{"type":7,"value":8,"toc":286},"minimark",[9,18,21,26,33,46,49,53,56,67,74,78,81,84,111,121,125,132,184,191,195,202,213,220,224,227,254,261,265,279,283],[10,11,12,13,17],"p",{},"There's a mistaken idea that discovery is a long, expensive process, something for big companies with research teams. In practice, the discovery that pays off most is ",[14,15,16],"strong",{},"small and frequent",": one focused week, before committing months of engineering.",[10,19,20],{},"This is the plan I use when I want to go from \"I think people need this\" to \"I watched five people try to use this and I know what to change\".",[22,23,25],"h2",{"id":24},"before-you-start-the-question-of-the-week","Before you start: the question of the week",[10,27,28,29,32],{},"Discovery without focus turns into an opinion poll. Start with ",[14,30,31],{},"one question",", written as a risk:",[34,35,36,40,43],"ul",{},[37,38,39],"li",{},"\"Would managers of small teams swap their feedback spreadsheet for a tool?\"",[37,41,42],{},"\"Will clinics accept patients booking on their own through WhatsApp?\"",[37,44,45],{},"\"Does the store owner understand the report without help?\"",[10,47,48],{},"One week, one question. If the question doesn't fit in one sentence, it's too big.",[22,50,52],{"id":51},"monday-what-we-already-know","Monday: what we already know",[10,54,55],{},"Before talking to anyone, gather what already exists:",[34,57,58,61,64],{},[37,59,60],{},"Support tickets, sales messages, comments on social media;",[37,62,63],{},"Usage data (if the product already exists): where do people drop off?",[37,65,66],{},"Competitors and alternatives: how is the problem solved today?",[10,68,69,70,73],{},"At the end of the day, write down ",[14,71,72],{},"the hypotheses"," the week will test. A good hypothesis says who, which behavior and which signal will confirm or kill it.",[22,75,77],{"id":76},"tuesday-interviews","Tuesday: interviews",[10,79,80],{},"Five 30-minute interviews with people who match the target profile. Five sounds like few, but it's enough for strong patterns to show up, and you'll have more rounds.",[10,82,83],{},"The golden rules of a discovery interview:",[85,86,87,93,99,105],"ol",{},[37,88,89,92],{},[14,90,91],{},"Ask about the past, not the future."," \"Tell me about the last time you had to do X\" is worth more than \"would you use a product that does X?\". Everyone says they would.",[37,94,95,98],{},[14,96,97],{},"Don't pitch your idea."," Not yet. You want to understand the problem, not collect compliments.",[37,100,101,104],{},[14,102,103],{},"Follow the emotion."," When the person sighs, laughs nervously or says \"this is a nightmare\", dig deeper.",[37,106,107,110],{},[14,108,109],{},"Look for what's already been tried."," People with real pain have already tried to solve it: a spreadsheet, a workaround, an abandoned tool. No attempts is a sign of weak pain.",[112,113,114],"tip",{},[10,115,116,117,120],{},"Record (with permission) and write down the ",[14,118,119],{},"literal phrases"," in real time. Later they become the raw material for your site copy and ads. Nobody describes the problem better than the person who feels it.",[22,122,124],{"id":123},"wednesday-opportunity-map-and-choice","Wednesday: opportunity map and choice",[10,126,127,128,131],{},"Pull the notes together and organize them into an ",[14,129,130],{},"opportunity map",": the outcome the customer wants at the top, the pains and needs below, grouped. For each opportunity, assess:",[133,134,135,148],"table",{},[136,137,138],"thead",{},[139,140,141,145],"tr",{},[142,143,144],"th",{},"Criterion",[142,146,147],{},"Question",[149,150,151,160,168,176],"tbody",{},[139,152,153,157],{},[154,155,156],"td",{},"Frequency",[154,158,159],{},"How often does this happen?",[139,161,162,165],{},[154,163,164],{},"Intensity",[154,166,167],{},"How much does it hurt when it happens?",[139,169,170,173],{},[154,171,172],{},"Alternative",[154,174,175],{},"How bad is the current solution?",[139,177,178,181],{},[154,179,180],{},"Reach",[154,182,183],{},"How many people in the target audience feel this?",[10,185,186,187,190],{},"Pick ",[14,188,189],{},"one"," opportunity and sketch two or three different solutions on paper. Having more than one solution keeps you from falling in love with the first idea.",[22,192,194],{"id":193},"thursday-prototype","Thursday: prototype",[10,196,197,198,201],{},"Build the ",[14,199,200],{},"cheapest prototype that lets you test the hypothesis",". It's almost never production code:",[34,203,204,207,210],{},[37,205,206],{},"Clickable Figma screens with realistic content (no lorem ipsum);",[37,208,209],{},"A sales page with an \"I want to try it\" button;",[37,211,212],{},"A manual process behind a simple interface (the famous \"Wizard of Oz\").",[10,214,215,216,219],{},"The prototype has to be good enough for the person to ",[14,217,218],{},"forget it's a prototype"," in the first few seconds. Real content makes more difference than visual polish.",[22,221,223],{"id":222},"friday-user-testing","Friday: user testing",[10,225,226],{},"Five more sessions, now with the prototype. Give a task (\"you need to give feedback to someone on your team, show me how you'd do it\") and watch in silence. The signals that matter:",[34,228,229,236,243],{},[37,230,231,232,235],{},"Did the person ",[14,233,234],{},"complete the task"," without help?",[37,237,238,239,242],{},"Where did they ",[14,240,241],{},"hesitate"," or go back?",[37,244,245,246,249,250,253],{},"Did they ask ",[14,247,248],{},"\"when can I use it?\""," or ",[14,251,252],{},"\"how much does it cost?\"","? That's the best signal there is.",[10,255,256,257,260],{},"At the end of the day, the decision: ",[14,258,259],{},"continue, adjust or drop it",". All three are good outcomes. Dropping it on Friday costs a week; dropping it after three months of development costs a quarter.",[22,262,264],{"id":263},"what-comes-out-of-the-week","What comes out of the week",[34,266,267,270,273,276],{},[37,268,269],{},"The hypothesis confirmed or killed, with evidence;",[37,271,272],{},"Your customers' literal phrases;",[37,274,275],{},"A tested prototype, with a list of what to change;",[37,277,278],{},"The scope of what's worth building first, and what stays out.",[22,280,282],{"id":281},"summary","Summary",[10,284,285],{},"Discovery is a habit, not a phase. One week per cycle, with a clear question, five conversations and a cheap prototype, completely changes the quality of what reaches engineering. And there's a bonus: when the product launches, you already know exactly which words to use to sell it.",{"title":287,"searchDepth":288,"depth":288,"links":289},"",3,[290,292,293,294,295,296,297,298],{"id":24,"depth":291,"text":25},2,{"id":51,"depth":291,"text":52},{"id":76,"depth":291,"text":77},{"id":123,"depth":291,"text":124},{"id":193,"depth":291,"text":194},{"id":222,"depth":291,"text":223},{"id":263,"depth":291,"text":264},{"id":281,"depth":291,"text":282},"discovery","2026-10-01","Discovery doesn't have to be a three-month project. A five-day plan to go from a vague idea to a prototype validated with real users, before writing any production code.",false,"md",{},true,"\u002Fblog\u002Fdiscovery-in-one-week","produto",{"title":5,"description":301},"blog\u002Fdiscovery-in-one-week",[299,311,312,313,314],"product","interviews","prototype","mvp","discovery-em-uma-semana",null,"q7Vu8EB67K2jzn5_jVtYzkuFnxLNnkVz2BenNrFgHQ8",[319],{"title":320,"description":321,"path":322,"date":323,"segment":307,"category":324,"tags":325,"featured":305,"readingTime":329},"The whole journey: why engineering, product, data and marketing need to fit in the same conversation","Good products are born when four questions are asked together: what to build, how to build it, how to know it worked and how to reach the people who need it.","\u002Fblog\u002Fthe-whole-journey-of-a-product","2026-11-10","estrategia",[311,326,327,328],"career","generalist","strategy",4,{"pt-br":331},"\u002Fpt-br\u002Fblog\u002Fdiscovery-em-uma-semana",[333,338],{"title":334,"path":335,"stem":336,"description":337,"children":-1},"Write the sentence before the website: positioning for B2B products","\u002Fblog\u002Fpositioning-before-the-website","blog\u002Fpositioning-before-the-website","If you can't explain in one sentence who your product is for and why it's the best choice, no landing page will do it for you. A practical positioning guide.",{"title":339,"path":340,"stem":341,"description":342,"children":-1},"Culture isn't a wall of values: it's ritual","\u002Fblog\u002Fculture-is-ritual","blog\u002Fculture-is-ritual","The values on the wall say what a company would like to be. The rituals (the conversations, the reviews, what gets celebrated) show what it is. How to turn culture into a recurring practice.",1795021079960]