{"id":85650,"date":"2025-09-30T18:47:33","date_gmt":"2025-09-30T17:47:33","guid":{"rendered":"https:\/\/www.prodpad.com\/?p=85650"},"modified":"2025-10-08T18:33:55","modified_gmt":"2025-10-08T17:33:55","slug":"roadmap-prototype-strategy","status":"publish","type":"post","link":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/","title":{"rendered":"Your Roadmap is a Prototype for Your Strategy"},"content":{"rendered":"\n

When I talk about Lean Roadmapping<\/a>, I always come back to the principle that makes Lean so effective: build, measure, learn. Out of those three, the real magic is in the learning. Lean isn\u2019t about rushing through build cycles. It\u2019s about capturing assumptions, testing them in small, safe ways, and using what you learn to improve the next iteration. That cycle is what helps teams adapt to change, reduce waste, and find the right solutions faster.<\/p>\n\n\n\n

Your roadmap plays the same role, but at the product strategy level.<\/strong> Too many teams treat roadmaps as rigid forecasts or delivery contracts. Once they\u2019re signed off, the roadmap becomes a millstone rather than a guide. That mindset ignores the fact that strategy itself is full of assumptions. A roadmap is not a prediction of the future. It\u2019s not a promise to deliver a fixed set of features by a certain date. A roadmap is a prototype for your strategy, a tool you use to test and improve your collective understanding of what problems matter and what direction will create the most value.<\/p>\n\n\n

\n
\n

Want to make this work for you? Book a Roadmap Clinic and we\u2019ll walk through your current roadmap and show you how to make it Lean.<\/p>\n <\/div>\n

\n Book a Clinic<\/a>\n <\/div>\n<\/div>\n\n\n\n\n

Just like the prototyping you know and love<\/h2>\n\n\n\n

If you\u2019ve ever worked in design, you already understand why prototyping matters. Nobody ships the first napkin sketch they scribble down. You start with the roughest version you can get away with making. Maybe it\u2019s a whiteboard drawing, maybe a couple of boxes in Figma. Then you put it in front of someone. A teammate says, \u201cThis button feels out of place.\u201d A customer says, \u201cThis doesn\u2019t solve my problem.\u201d You make a new sketch, slightly better, and test again.<\/p>\n\n\n\n

\"Early
An early mock-up of the Now-Next-Later roadmap \u2014 nothing polished, just a prototype sketch to capture assumptions.<\/figcaption><\/figure>\n\n\n\n

Each cycle strips away assumptions and brings you closer to a design that works. And importantly, you throw away most of the early prototypes. That\u2019s not waste. That\u2019s the process. The value of prototyping isn\u2019t in the artifacts, it\u2019s in the act of prototyping itself.<\/p>\n\n\n\n

Teresa Torres often reminds us that strong product discovery begins by visualizing possibilities and testing assumptions<\/a>. She uses Opportunity Solution Trees to show how teams can explore multiple paths side by side, quickly identify weak options, and double down on the ideas that actually hold promise.<\/p>\n\n\n\n

Designers already accept this norm. They sketch rough ideas early, put them in front of users and teammates, learn what works and what doesn\u2019t, discard what fails, and then build toward the stronger version. They don\u2019t wait until they think they have it \u201cright.\u201d They learn by doing.<\/p>\n\n\n\n

Your roadmap deserves the same treatment. It should be the place where you sketch out strategic options, test your assumptions with stakeholders, and iterate rapidly. The roadmap is not the final product. It\u2019s the prototyping process for your strategy.<\/p>\n\n\n\n

Check strategic assumptions on your roadmap<\/h2>\n\n\n\n

Roadmaps should be approached with exactly the same mindset. Your first roadmap is a prototype of your strategy. It captures your best attempt at interpreting customer needs, stakeholder pressures, and market shifts. It is a bundle of assumptions, and it will be wrong. That\u2019s the point.<\/p>\n\n\n\n

Think of your roadmap draft as your sketch. It\u2019s your attempt to say, \u201cHere are the problems we think matter. Here\u2019s the order we think they should be tackled.\u201d That version should be deliberately simple and easy to change. The mistake many teams make is trying to design a \u201cperfect\u201d roadmap on the first pass. They add color-coded swimlanes, date-based milestones, and high-fidelity visuals. All that does is give stakeholders a false sense of confidence in a plan that hasn\u2019t been validated.<\/p>\n\n\n\n

A roadmap is strongest when it\u2019s sketchy. At ProdPad, we encourage teams to start with Now-Next-Later roadmaps, because the format acknowledges uncertainty. You know a lot about what\u2019s happening right now, less about what comes next, and very little about what\u2019s further out. That\u2019s healthy. It mirrors how strategy should be treated: flexible, adaptive, and open to iteration.<\/p>\n\n\n

\n
\n

How to break free from timeline-driven roadmaps<\/p>\n <\/div>\n

\n Get the Guide<\/a>\n <\/div>\n<\/div>\n\n\n\n\n

How to prototype your roadmap<\/h2>\n\n\n\n

Treating your roadmap like a prototype means accepting that it will change and building iteration into the process from day one. The roadmap is not a sacred artifact. It\u2019s a tool for learning, just like a paper prototype or a wireframe. Here\u2019s what it looks like when you run your roadmap as a prototype instead of a plan.<\/p>\n\n\n\n

Start simple<\/h3>\n\n\n\n

The best first roadmap looks almost embarrassingly basic. Capture the problems you think are most important and lay them out in a rough order. Do not worry about dates, milestones, or dependencies yet. At this stage, you\u2019re sketching, not engineering. The beauty of a Now-Next-Later roadmap is that it forces simplicity. You can express assumptions clearly without pretending to know the future. A roadmap that says \u201cProblem A, Problem B, Problem C\u201d is enough to start the conversation.<\/p>\n\n\n\n

\"Hand-drawn
\u201cMy first roadmap\u201d, a deliberately rough, crayon-style sketch showing problems in order, not a polished plan. Your first stab at a roadmap should be equally low fidelity!<\/figcaption><\/figure>\n\n\n\n

Share it early<\/h3>\n\n\n\n

Once you have a rough draft, put it in front of people quickly. Show it to colleagues, executives, sales teams, customer success, and even a few trusted customers. The goal is not approval. The goal is critique. A roadmap hidden until it feels \u201cpolished\u201d is a missed opportunity for feedback. Every extra set of eyes is a chance to uncover blind spots, stress-test your priorities, and surface opportunities you might not have considered.<\/p>\n\n\n\n

Spot the gaps<\/h3>\n\n\n\n

Not every comment deserves a reaction, but repeated patterns matter. If three stakeholders independently point out that an important market trend is missing, or that a problem you listed isn\u2019t urgent, that\u2019s a signal. Roadmapping is about testing assumptions, and those signals are what tell you which assumptions need to change. This is where the process of prototyping shines. Just as you would update a wireframe based on usability testing, you update your roadmap based on consistent feedback.<\/p>\n\n\n\n

Throw out early versions<\/h3>\n\n\n\n

One of the hardest but most important parts of roadmapping is letting go of your first draft. The first version is not precious. If new information proves it wrong, throw it out and replace it with something stronger. That is not failure \u2014 that is the process working as intended. Think of it as version control for your strategy. Each new iteration reflects what you\u2019ve learned, and every discarded version is evidence of progress.<\/p>\n\n\n\n

Keep it flexible<\/h3>\n\n\n\n

The format you choose has a massive impact on how adaptable your roadmap is. A date-based Gantt chart locks you into commitments that don\u2019t survive contact with reality. A Now-Next-Later roadmap is intentionally flexible. It shows direction without false precision, giving you room to adapt as new information comes in. Flexibility signals to stakeholders that strategy is a living conversation, not a fixed contract.<\/p>\n\n\n\n

This is where the role of the product manager comes into sharp focus. Your job is not to dictate the strategy or to have all the answers. Your job is to facilitate the conversations that make the strategy stronger. When you present a roadmap as a prototype, you invite others to challenge your assumptions, test your thinking, and help you build alignment.<\/p>\n\n\n\n

The strongest product managers are not the ones who produce the \u201cperfect\u201d roadmap on the first try. They are the ones who lead a robust roadmapping process. They show that the value lies not in the artifact, but in the act of roadmapping itself.<\/p>\n\n\n\n

\"ProdPad's<\/a><\/figure>\n\n\n\n

The anti-patterns that derail roadmaps<\/h2>\n\n\n\n

Roadmaps are powerful when treated as prototypes, but they can just as easily go wrong. Time and again, I see teams falling into the same traps. These anti-patterns are what derail the value of roadmapping and turn it into a painful exercise instead of a learning process.<\/p>\n\n\n\n

Roadmap as contract<\/h3>\n\n\n\n

One of the most damaging habits is treating the roadmap like a delivery contract. Leadership signs it off, and suddenly every item becomes a promise. The team loses the ability to adjust as new information comes in, and the roadmap hardens into a rigid plan. This is how organizations end up shipping features nobody needs anymore, while better opportunities sit untouched.<\/p>\n\n\n\n

I\u2019ve written before about why timeline roadmaps don\u2019t work<\/a>. A timeline gives the illusion of control but traps you in commitments you can\u2019t realistically keep. The alternative is to focus on outcomes, not dates. A Lean, Now-Next-Later style roadmap that leaves space to adapt.<\/p>\n\n\n\n

Overdesigned visuals<\/h3>\n\n\n\n

Another common mistake is overdesigning the roadmap itself. A Gantt chart packed with milestones looks impressive on a slide deck, but it creates false confidence. When stakeholders see something that looks polished, they assume it\u2019s set in stone. Instead of critiquing assumptions, they nod along, thinking the details must have already been worked out.<\/p>\n\n\n\n

This kind of roadmap does more harm than good. It makes it harder for people to speak up, because who wants to poke holes in something that looks \u201cfinished\u201d? That\u2019s why I warn against customer-facing roadmap no-nos<\/a>. A roadmap isn\u2019t a marketing asset. It\u2019s a working document meant to be challenged, iterated, and reshaped.<\/p>\n\n\n\n

Feature factory lists<\/h3>\n\n\n\n

The feature factory roadmap is a classic roadmap anti-pattern<\/a>. This is where the roadmap is nothing more than a backlog of features, prioritized in order of delivery. It looks like a plan, but it\u2019s not strategy. It\u2019s output dressed up as vision. Teams who fall into this trap lose sight of the bigger picture. They ship features, but they don\u2019t solve problems.<\/p>\n\n\n\n

A good roadmap doesn\u2019t say, \u201cHere are 20 things we\u2019ll build.\u201d It says, \u201cHere are the problems we\u2019re solving, and here\u2019s the order we believe makes sense.\u201d Without that shift, you end up measuring progress by the number of boxes ticked instead of the value created.<\/p>\n\n\n\n

Secretive drafts<\/h3>\n\n\n\n

Finally, there\u2019s the problem of secrecy. Some teams build roadmaps in isolation, polishing them until they feel \u201cready,\u201d and then unveil them as if they were final. By then, it\u2019s too late for meaningful feedback. Stakeholders and colleagues feel blindsided, and the roadmap misses critical insights that could have made it stronger.<\/p>\n\n\n\n

This is the opposite of what good roadmapping looks like. A roadmap should be shared early and often<\/a>. It should invite collaboration, not discourage it. The best roadmaps evolve in the open, shaped by contributions from across the business. Transparency builds trust. Secretive drafting erodes it.<\/p>\n\n\n\n

These anti-patterns are all symptoms of treating roadmaps as final products rather than prototypes.<\/p>\n\n\n\n

What great roadmapping looks like<\/h2>\n\n\n\n

The best product managers I know don\u2019t obsess over producing the perfect roadmap. They obsess over running a strong roadmapping process. A good process is what keeps strategy adaptable and credible, even when conditions change.<\/p>\n\n\n\n

Draft lightweight, flexible versions<\/h4>\n\n\n\n

They start with a simple sketch\u2026 a rough Now-Next-Later view or a problem-theme layout. The goal is clarity, not polish. A roadmap that is too designed feels locked in before it\u2019s been tested.<\/p>\n\n\n\n

Share early and openly<\/h4>\n\n\n\n

They don\u2019t hoard drafts. They put them in front of executives, sales, customer success, delivery, and ask for critique, not approval. When roadmaps live behind closed doors until \u201cdone,\u201d they lose the chance to improve from early feedback.<\/p>\n\n\n\n

Stay focused on outcomes & problem spaces<\/h4>\n\n\n\n

They resist the urge to fill the roadmap with features. Instead, they map problems and value areas. This avoids the trap of a roadmap turning into a feature list. It keeps the team aligned around solving real issues, not just building outputs.<\/p>\n\n\n\n

Iterate often<\/h4>\n\n\n\n

Good roadmaps change. They get replaced, not just tweaked. When new information invalidates assumptions, earlier versions are discarded. That\u2019s how a roadmap improves \u2014 by being challenged, broken, and rebuilt.<\/p>\n\n\n\n

Use it as a communication tool, not a contract<\/h4>\n\n\n\n

A roadmap is how you show direction, trade-offs, and priorities. It\u2019s not a promise. Treating it like a binding contract kills flexibility and kills trust.<\/p>\n\n\n\n

Why this matters<\/h3>\n\n\n\n

A roadmap run this way builds resilience. The team isn\u2019t clinging to a brittle plan. They trust the process. They know things will change, and that\u2019s okay, because the roadmap is grounded in shared understanding and validated assumptions.<\/p>\n\n\n\n

Marty Cagan makes a critical distinction between product and feature teams<\/a>, where he explains how empowered product teams focus on outcomes while feature teams are stuck in output mode.<\/p>\n\n\n\n\n

\n

Check out these examples of good roadmaps that are actually useful in practice<\/p>\n <\/div>\n

\n <\/span>\n <\/div>\n<\/a>\n\n\n\n\n

Why this mindset is critical right now<\/h2>\n\n\n\n

Product management has always been complex, but today the pace of change is brutal. Markets shift quickly. New technologies like AI change the definition of \u201cfeasible\u201d overnight. Budgets are tighter. Stakeholders demand evidence that strategy is responsive.<\/p>\n\n\n\n

Old-school, date-driven roadmaps cannot survive this environment. They create a false sense of stability that collapses the moment reality intervenes. Teams are left scrambling to explain why their beautifully crafted timeline no longer matches the market.<\/p>\n\n\n\n

Treating your roadmap as a prototype solves this. It keeps your strategy adaptive by design. It acknowledges uncertainty instead of hiding it. And it gives stakeholders confidence that you\u2019re not just making a plan, you\u2019re running a process that will keep evolving as the world changes.<\/p>\n\n\n\n

The value lies in the process<\/h2>\n\n\n\n

A roadmap is not the value. The value is in the roadmapping process.<\/p>\n\n\n\n

Every draft you create is an opportunity to test assumptions. Every round of feedback sharpens the strategy. Every iteration makes your plan more resilient and aligned.<\/p>\n\n\n\n

As product people, we\u2019re not here to be right on the first try. We\u2019re here to lead the process that turns rough sketches of a strategy into something the entire organization can trust.<\/p>\n\n\n\n

A roadmap is a prototype for your strategy. Treat it like one, and you\u2019ll never be stuck defending a brittle plan again. You\u2019ll be leading a process that learns, adapts, and keeps the whole company moving in the right direction.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Still stuck chasing \u201cperfect\u201d roadmaps? I covered the hidden costs of polish in The Problem with the Perfect Roadmap<\/a>, including the wasted hours and brittle plans that come with chasing aesthetics instead of outcomes.<\/p>\n","protected":false},"excerpt":{"rendered":"

When I talk about Lean Roadmapping, I always come back to the principle that makes Lean so effective: build, measure, learn. Out of those three, the real magic is in…<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":true,"template":"","format":"standard","meta":{"_acf_changed":true,"footnotes":""},"categories":[5231,9],"tags":[],"pp_uni_tag":[],"class_list":["post-85650","post","type-post","status-publish","format-standard","hentry","category-latest-blogs","category-product-management-best-practice"],"acf":[],"yoast_head":"\nYour Roadmap is a Prototype for Your Strategy<\/title>\n<meta name=\"description\" content=\"Your roadmap is not the plan, it\u2019s the prototype for your strategy. Learn how to use roadmapping as an iterative process to build stronger product strategy.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Your Roadmap is a Prototype for Your Strategy | ProdPad\" \/>\n<meta property=\"og:description\" content=\"Your roadmap is not the plan, it\u2019s the prototype for your strategy. Learn how to use roadmapping as an iterative process to build stronger product strategy.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/\" \/>\n<meta property=\"og:site_name\" content=\"ProdPad\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/ProdPad\/\" \/>\n<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/bastow\" \/>\n<meta property=\"article:published_time\" content=\"2025-09-30T17:47:33+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-10-08T17:33:55+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.prodpad.com\/wp-content\/uploads\/2025\/09\/Your-Roadmap-is-a-Prototype-for-your-Strategy.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1020\" \/>\n\t<meta property=\"og:image:height\" content=\"550\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Janna Bastow\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Your Roadmap is a Prototype for Your Strategy | ProdPad\" \/>\n<meta name=\"twitter:description\" content=\"Your roadmap is not the plan, it\u2019s the prototype for your strategy. Learn how to use roadmapping as an iterative process to build stronger product strategy.\" \/>\n<meta name=\"twitter:creator\" content=\"@simplybastow\" \/>\n<meta name=\"twitter:site\" content=\"@prodpad\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Janna Bastow\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Your Roadmap is a Prototype for Your Strategy","description":"Your roadmap is not the plan, it\u2019s the prototype for your strategy. Learn how to use roadmapping as an iterative process to build stronger product strategy.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/","og_locale":"en_US","og_type":"article","og_title":"Your Roadmap is a Prototype for Your Strategy | ProdPad","og_description":"Your roadmap is not the plan, it\u2019s the prototype for your strategy. Learn how to use roadmapping as an iterative process to build stronger product strategy.","og_url":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/","og_site_name":"ProdPad","article_publisher":"https:\/\/www.facebook.com\/ProdPad\/","article_author":"https:\/\/www.facebook.com\/bastow","article_published_time":"2025-09-30T17:47:33+00:00","article_modified_time":"2025-10-08T17:33:55+00:00","og_image":[{"width":1020,"height":550,"url":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2025\/09\/Your-Roadmap-is-a-Prototype-for-your-Strategy.png","type":"image\/png"}],"author":"Janna Bastow","twitter_card":"summary_large_image","twitter_title":"Your Roadmap is a Prototype for Your Strategy | ProdPad","twitter_description":"Your roadmap is not the plan, it\u2019s the prototype for your strategy. Learn how to use roadmapping as an iterative process to build stronger product strategy.","twitter_creator":"@simplybastow","twitter_site":"@prodpad","twitter_misc":{"Written by":"Janna Bastow","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#article","isPartOf":{"@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/"},"author":{"name":"Janna Bastow","@id":"https:\/\/www.prodpad.com\/#\/schema\/person\/ceec8b615b0ad09e9199ba2fa8545e8c"},"headline":"Your Roadmap is a Prototype for Your Strategy","datePublished":"2025-09-30T17:47:33+00:00","dateModified":"2025-10-08T17:33:55+00:00","mainEntityOfPage":{"@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/"},"wordCount":2371,"commentCount":0,"publisher":{"@id":"https:\/\/www.prodpad.com\/#organization"},"image":{"@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#primaryimage"},"thumbnailUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2025\/09\/mockup-prototype.png","articleSection":["Latest Blogs","Product Management Best Practice"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/","url":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/","name":"Your Roadmap is a Prototype for Your Strategy","isPartOf":{"@id":"https:\/\/www.prodpad.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#primaryimage"},"image":{"@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#primaryimage"},"thumbnailUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2025\/09\/mockup-prototype.png","datePublished":"2025-09-30T17:47:33+00:00","dateModified":"2025-10-08T17:33:55+00:00","description":"Your roadmap is not the plan, it\u2019s the prototype for your strategy. Learn how to use roadmapping as an iterative process to build stronger product strategy.","breadcrumb":{"@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#primaryimage","url":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2025\/09\/mockup-prototype.png","contentUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2025\/09\/mockup-prototype.png","width":495,"height":369,"caption":"An early mock-up of the Now-Next-Later roadmap \u2014 nothing polished, just a prototype sketch to capture assumptions."},{"@type":"BreadcrumbList","@id":"https:\/\/www.prodpad.com\/blog\/roadmap-prototype-strategy\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Latest Blogs","item":"https:\/\/www.prodpad.com\/blog\/category\/latest-blogs\/"},{"@type":"ListItem","position":2,"name":"Your Roadmap is a Prototype for Your Strategy"}]},{"@type":"WebSite","@id":"https:\/\/www.prodpad.com\/#website","url":"https:\/\/www.prodpad.com\/","name":"ProdPad","description":"Product Management Software","publisher":{"@id":"https:\/\/www.prodpad.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.prodpad.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.prodpad.com\/#organization","name":"ProdPad","url":"https:\/\/www.prodpad.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.prodpad.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2018\/12\/blue-full.png","contentUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2018\/12\/blue-full.png","width":2050,"height":400,"caption":"ProdPad"},"image":{"@id":"https:\/\/www.prodpad.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/ProdPad\/","https:\/\/x.com\/prodpad","https:\/\/instagram.com\/prodpad","https:\/\/www.linkedin.com\/company\/prodpad\/","https:\/\/www.youtube.com\/channel\/UCXHOx5Ed-6sHPujypIlhdMA"]},{"@type":"Person","@id":"https:\/\/www.prodpad.com\/#\/schema\/person\/ceec8b615b0ad09e9199ba2fa8545e8c","name":"Janna Bastow","description":"Janna Bastow is co-founder of ProdPad, software that helps product managers plan and deliver better products. Janna also organizes ProductTank events around the world, including Mind The Product, a global community of product managers. She likes to inspire great product conversations by asking: \u201cWhat problem are you trying to solve?\u201d","sameAs":["https:\/\/www.facebook.com\/bastow","https:\/\/x.com\/simplybastow"],"url":"https:\/\/www.prodpad.com\/blog\/author\/janna-bastow\/"}]}},"_links":{"self":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/posts\/85650","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/comments?post=85650"}],"version-history":[{"count":0,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/posts\/85650\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/media?parent=85650"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/categories?post=85650"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/tags?post=85650"},{"taxonomy":"pp_uni_tag","embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/pp_uni_tag?post=85650"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}