[{"data":1,"prerenderedAt":306},["ShallowReactive",2],{"post-\u002Fblog\u002Fthe-whole-journey-of-a-product":3,"post-related-\u002Fblog\u002Fthe-whole-journey-of-a-product":282,"post-translations-\u002Fblog\u002Fthe-whole-journey-of-a-product":293,"post-surround-\u002Fblog\u002Fthe-whole-journey-of-a-product":295},{"id":4,"title":5,"body":6,"category":262,"date":263,"description":264,"draft":265,"extension":266,"featured":267,"meta":268,"navigation":267,"path":269,"readingTime":270,"segment":271,"seo":272,"stem":273,"tags":274,"translationKey":279,"updated":280,"__hash__":281},"blog_en\u002Fblog\u002Fthe-whole-journey-of-a-product.md","The whole journey: why engineering, product, data and marketing need to fit in the same conversation",{"type":7,"value":8,"toc":251},"minimark",[9,13,21,26,54,57,63,67,70,97,100,104,115,118,125,129,132,199,203,206,238,241,245],[10,11,12],"p",{},"Almost every product I've seen go wrong had one thing in common: it wasn't short on competence, it was short on conversation. The engineering team delivered what was in the ticket, product wrote the ticket from a meeting, marketing found out about the feature on launch day and, three months later, someone opened a dashboard and asked: \"did this work?\". Nobody knew, because nobody had agreed on what \"working\" meant.",[10,14,15,16,20],{},"This blog comes from a simple conviction: ",[17,18,19],"strong",{},"the best product decisions happen when four questions are asked at the same time",", by the same head or around the same table.",[22,23,25],"h2",{"id":24},"the-four-questions","The four questions",[27,28,29,36,42,48],"ol",{},[30,31,32,35],"li",{},[17,33,34],{},"What's worth building?"," That's the product question. Which pain, for whom, how often, and what happens if we don't solve it.",[30,37,38,41],{},[17,39,40],{},"How do we build it?"," That's the engineering question. What's the simplest solution that solves it, can grow and doesn't turn into debt the following month.",[30,43,44,47],{},[17,45,46],{},"How do we know it worked?"," That's the data question. Which behavior changes if the feature works, and how we'll see it.",[30,49,50,53],{},[17,51,52],{},"How do we reach the people who need it?"," That's the marketing question. Who needs to know about this, where that person is and what they need to hear to give it a try.",[10,55,56],{},"Apart, each question has an owner, a ritual and a tool. Together, they correct each other. The data question forces product to be specific. The marketing question forces engineering to think about the first use, not just the use case. The engineering question forces marketing to promise what actually exists.",[58,59,60],"tip",{},[10,61,62],{},"A quick test: take the last feature your team shipped and try to answer the four questions in one sentence each. If one of them gets stuck, that's where the product is losing money.",[22,64,66],{"id":65},"the-cost-of-not-talking","The cost of not talking",[10,68,69],{},"When these areas work in series (product hands off to engineering, which hands off to marketing, which hands off to data), every handoff loses context. The result shows up as symptoms everyone knows:",[71,72,73,79,85,91],"ul",{},[30,74,75,78],{},[17,76,77],{},"A feature shipped and not used."," The problem was real, but nobody thought about how people would discover the solution.",[30,80,81,84],{},[17,82,83],{},"Analytics events patched in later."," The question \"how do we measure this?\" arrives when the code is already in production, and the answer becomes partial tracking nobody trusts.",[30,86,87,90],{},[17,88,89],{},"A campaign that promises what the product doesn't deliver."," Expensive acquisition for an audience that cancels in the first week.",[30,92,93,96],{},[17,94,95],{},"Architecture that holds the business back."," A technical decision made without knowing where the product was going, which now costs a quarter to undo.",[10,98,99],{},"None of these problems is a lack of talent. It's a lack of someone looking at the whole journey.",[22,101,103],{"id":102},"generalist-doesnt-mean-shallow","Generalist doesn't mean shallow",[10,105,106,107,110,111,114],{},"There's an old prejudice against people who move between areas: \"does a bit of everything, nothing well\". I understand where it comes from, but I think it confuses ",[17,108,109],{},"breadth"," with ",[17,112,113],{},"superficiality",".",[10,116,117],{},"The profile I'm arguing for here has a deep base (in my case, software engineering) and real knowledge of the neighboring areas. It's not the best paid-media specialist in the room, but it can read a campaign report and ask why the cost per sign-up went up. It's not a data scientist, but it designs a measurement plan before writing the first line. It's not a designer, but it recognizes when a sign-up flow asks for too much information.",[10,119,120,121,124],{},"That breadth doesn't replace specialists. It ",[17,122,123],{},"multiplies"," their work, because it translates one area to another and sees the dependencies the org chart hides.",[22,126,128],{"id":127},"how-this-shows-up-day-to-day","How this shows up day to day",[10,130,131],{},"In practice, thinking about the whole journey changes small decisions that, added up, make all the difference:",[133,134,135,151],"table",{},[136,137,138],"thead",{},[139,140,141,145,148],"tr",{},[142,143,144],"th",{},"Decision",[142,146,147],{},"Isolated view",[142,149,150],{},"Journey view",[152,153,154,166,177,188],"tbody",{},[139,155,156,160,163],{},[157,158,159],"td",{},"Sign-up form",[157,161,162],{},"\"We need the phone number for the CRM\"",[157,164,165],{},"Every extra field lowers conversion; the phone can come after activation",[139,167,168,171,174],{},[157,169,170],{},"New feature",[157,172,173],{},"\"Done when it passes QA\"",[157,175,176],{},"Done when it has a usage event, launch copy and a way to be discovered",[139,178,179,182,185],{},[157,180,181],{},"Pricing page",[157,183,184],{},"\"Marketing handles it\"",[157,186,187],{},"It's the product screen with the biggest revenue impact; it deserves testing and measurement",[139,189,190,193,196],{},[157,191,192],{},"Architecture",[157,194,195],{},"\"Microservices to scale\"",[157,197,198],{},"A well-split monolith until the product proves it needs more",[22,200,202],{"id":201},"what-youll-find-here","What you'll find here",[10,204,205],{},"The blog is organized into five topics that mirror this journey:",[71,207,208,214,220,226,232],{},[30,209,210,213],{},[17,211,212],{},"Engineering:"," architecture, code and technical decisions that hold up as the product grows.",[30,215,216,219],{},[17,217,218],{},"Product:"," discovery, strategy and what to leave out.",[30,221,222,225],{},[17,223,224],{},"Data:"," metrics that drive decisions, measurement done right and honest experiments.",[30,227,228,231],{},[17,229,230],{},"Marketing:"," positioning, acquisition and growth.",[30,233,234,237],{},[17,235,236],{},"Business:"," leadership, culture and the system around the product.",[10,239,240],{},"The articles cross topics often, and that's on purpose. A piece about a measurement plan belongs to data, but it touches engineering (where the event is born) and marketing (which campaign it will evaluate). If you work in one of these areas and want to understand the other three better, this space is for you.",[22,242,244],{"id":243},"to-wrap-up","To wrap up",[10,246,247,248,114],{},"A product is the sum of many small decisions made by different people. The more those people see the whole journey, the fewer decisions contradict each other. My work, and the purpose of this blog, is to help build that view: ",[17,249,250],{},"from code to growth, without losing the thread along the way",{"title":252,"searchDepth":253,"depth":253,"links":254},"",3,[255,257,258,259,260,261],{"id":24,"depth":256,"text":25},2,{"id":65,"depth":256,"text":66},{"id":102,"depth":256,"text":103},{"id":127,"depth":256,"text":128},{"id":201,"depth":256,"text":202},{"id":243,"depth":256,"text":244},"estrategia","2026-11-10","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.",false,"md",true,{},"\u002Fblog\u002Fthe-whole-journey-of-a-product",4,"produto",{"title":5,"description":264},"blog\u002Fthe-whole-journey-of-a-product",[275,276,277,278],"product","career","generalist","strategy","jornada-completa-de-um-produto",null,"zal1P0ek7zWpi4024E3aD2RuTwx2W_5LM62UI7AFke0",[283],{"title":284,"description":285,"path":286,"date":287,"segment":271,"category":288,"tags":289,"featured":265,"readingTime":253},"Discovery in one week: from problem to testable prototype","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.","\u002Fblog\u002Fdiscovery-in-one-week","2026-10-01","discovery",[288,275,290,291,292],"interviews","prototype","mvp",{"pt-br":294},"\u002Fpt-br\u002Fblog\u002Fjornada-completa-de-um-produto",[296,301],{"title":297,"path":298,"stem":299,"description":300,"children":-1},"Inside this blog: Nuxt 4, Nuxt Content and markdown, fully static","\u002Fblog\u002Fstatic-blog-with-nuxt-content","blog\u002Fstatic-blog-with-nuxt-content","How this site was built: typed collections, segments and categories, code-generated covers, RSS, sitemap and full prerendering. A practical guide to building your own.",{"title":302,"path":303,"stem":304,"description":305,"children":-1},"Modular monolith first: how I structure a SaaS from scratch without regretting it later","\u002Fblog\u002Fmodular-monolith-first","blog\u002Fmodular-monolith-first","Microservices solve problems a new product doesn't have yet. The conventions I use to start with a well-split monolith that can grow and doesn't turn into a tangle.",1795021079035]