{"id":6208,"date":"2026-06-03T09:00:00","date_gmt":"2026-06-03T07:00:00","guid":{"rendered":"https:\/\/storiesonboard.com\/blog\/?p=6208"},"modified":"2026-06-18T15:17:23","modified_gmt":"2026-06-18T13:17:23","slug":"the-history-of-mvps-from-lean-startup-to-today","status":"publish","type":"post","link":"https:\/\/storiesonboard.com\/blog\/the-history-of-mvps-from-lean-startup-to-today","title":{"rendered":"The history of mvps: from lean startup to today"},"content":{"rendered":"<p>Minimum viable products (MVPs) have evolved from a scrappy startup tactic to a mainstream product-development philosophy, now embraced by Fortune&nbsp;500 companies and student founders alike. Over almost two decades, the concept has broadened, splintered, and adapted to new technologies\u2014yet its core goal remains the same: <strong>learn as much as possible, as fast as possible, with the least possible waste<\/strong>.<\/p>\n<p>In this post, we\u2019ll trace that journey, see how each era reshaped the practice, and look ahead to where MVPs might go next.<\/p>\n<h2 class=\"wp-block-heading\">What is an MVP?<\/h2>\n<p>An MVP is <strong>not<\/strong> simply the first release of a product. It is specifically engineered to answer a <em>critical<\/em> uncertainty. Think of it as an experimentally\u2011minded slice of your vision\u2014just enough functionality that <em>real users<\/em> can interact with it and you can observe whether your riskiest assumptions hold water.<\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Purpose\u2011built:<\/strong> Every MVP should revolve around one <em>dominating question<\/em>. For Uber\u2019s founders, that question was \u201cWill people request a ride from strangers with their phone?\u201d<\/li>\n<li><strong>Externally validated:<\/strong> Data must come from <em>outside the building<\/em>\u2014clicks, sign\u2011ups, dollars spent, churn, qualitative interviews, or ethnographic observations.<\/li>\n<li><strong>Imperfect by design:<\/strong> Quality is \u2018good enough to learn.\u2019 If you polish beyond that, you\u2019re throwing time at the wrong goal.<\/li>\n<\/ul>\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Pro tip:<\/strong> Frame your riskiest assumption as a <em>falsifiable hypothesis<\/em>\u2014e.g., \u201c10% of landing\u2011page visitors will enter their email for early access.\u201d Then build just what you need to test it.<\/p>\n<\/blockquote>\n<h2 class=\"wp-block-heading\">Roots in the lean startup movement<\/h2>\n<h3 class=\"wp-block-heading\">Steve Blank and customer development<\/h3>\n<p>In the early 2000s, serial entrepreneur <strong>Steve&nbsp;Blank<\/strong> noticed a pattern: tech startups failed not from poor engineering, but from building products nobody wanted. His solution was <strong>customer development<\/strong>, a four\u2011step process (customer discovery, customer validation, customer creation, company building) that required founders to test hypotheses directly with target users before scaling. Blank didn\u2019t use the term <em>MVP<\/em>, but his insistence on \u201cminimum feature set\u201d prototypes laid the conceptual foundation.<\/p>\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>\u201cGet out of the building\u201d became the rallying cry for a generation of founders who realized business plans were guesses until proven otherwise.<\/p>\n<\/blockquote>\n<h3 class=\"wp-block-heading\">Eric Ries popularizes the MVP<\/h3>\n<p>Blank\u2019s student <strong>Eric&nbsp;Ries<\/strong> synthesized agile engineering, Lean manufacturing, and customer development into what he dubbed <strong>The Lean Startup<\/strong>. On his blog (2008) and later in the best\u2011selling 2011 book, Ries formalized the <strong>build\u2011measure\u2011learn<\/strong> loop, with the MVP at its heart. He argued that each iteration should be viewed as a scientific experiment\u2014<em>a controlled way to maximize validated learning about customers with the minimal investment of effort<\/em>.<\/p>\n<p>Within a few years, accelerators like Y&nbsp;Combinator and media outlets like TechCrunch turned \u201claunch an MVP\u201d into the default advice for software founders.<\/p>\n<h2 class=\"wp-block-heading\">MVPs in the mobile\u2011first 2010s<\/h2>\n<p>The iPhone\u2019s App Store (2008) and Android Market (2008) supercharged lean experimentation:<\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Tiny surface area, vast reach:<\/strong> A single\u2011screen app could reach millions of users. <strong>Instagram<\/strong> launched in 2010 with only three core actions\u2014take photo, apply filter, share\u2014and nevertheless onboarded 25,000 users in 24&nbsp;hours. That validated the bet on <em>mobile\u2011native<\/em> photo sharing.<\/li>\n<li><strong>Cloud plumbing:<\/strong> AWS, Heroku, and Stripe slashed backend and payment friction. Two engineers could now spin up infrastructure in an afternoon, shrinking the cost of failure.<\/li>\n<li><strong>Playbook formation:<\/strong> The rise of Crashlytics, Mixpanel, and Optimizely made data collection trivial, further codifying the <em>measure<\/em> portion of the loop.<\/li>\n<\/ul>\n<p>These forces cemented the cultural expectation that a <em>respectable<\/em> startup should launch an MVP within weeks, not months.<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"1024\" src=\"https:\/\/storiesonboard.com\/blog\/wp-content\/uploads\/2025\/06\/design-thinking.png\" alt=\"%Start story mapping today%\" class=\"wp-image-6210\" title=\"\" srcset=\"https:\/\/storiesonboard.com\/blog\/wp-content\/uploads\/2025\/06\/design-thinking.png 1024w, https:\/\/storiesonboard.com\/blog\/wp-content\/uploads\/2025\/06\/design-thinking-300x300.png 300w, https:\/\/storiesonboard.com\/blog\/wp-content\/uploads\/2025\/06\/design-thinking-150x150.png 150w, https:\/\/storiesonboard.com\/blog\/wp-content\/uploads\/2025\/06\/design-thinking-768x768.png 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\"><\/figure>\n<h2 class=\"wp-block-heading\">Design thinking meets MVPs<\/h2>\n<p>By the mid\u20112010s, product teams began marrying <strong>design thinking<\/strong>\u2014with its emphases on empathy, ideation, and rapid prototyping\u2014to lean experimentation:<\/p>\n<ol class=\"wp-block-list\">\n<li><strong>Empathize and define:<\/strong> Qualitative interviews and field studies revealed pain points before a single line of code was written.<\/li>\n<li><strong>Ideate broadly, prototype narrowly:<\/strong> Dozens of sketch concepts were distilled into a single hypothesis\u2011driven MVP.<\/li>\n<li><strong>Test user flows in hours:<\/strong> Interactive Figma prototypes or high\u2011fidelity InVision click\u2011throughs often served as \u2018MVPs\u2019 when the question was purely about <em>usability<\/em>, not technical feasibility.<\/li>\n<\/ol>\n<p>This merger shifted attention from <em>can we build it?<\/em> to <em>should we build it?<\/em>, elevating user desirability to the same tier as viability and feasibility.<\/p>\n<section class=\"sob-recommended-section\">\n<h2>Distribution\u2011first MVPs<\/h2>\n<p>As MVPs matured, one risk stayed under\u2011tested: distribution. Teams often validate desirability and feasibility, then learn too late that acquisition costs sink the business. A distribution\u2011first MVP flips the script by proving channel\u2011market fit before you scale features.<\/p>\n<p>Pick the riskiest assumption about how you\u2019ll reach users (e.g., \u201cWe can profitably acquire creators on TikTok\u201d) and set a falsifiable threshold\u2014CTR, lead rate, CAC, or partner response rate. Then run lightweight, no\u2011code tests to validate or kill the channel fast.<\/p>\n<ul>\n<li>Ad\u2011creative smoke tests: Ship 3\u20135 messages across Meta\/TikTok\/Reddit; measure click\u2011to\u2011email or waitlist rates against a target CAC.<\/li>\n<li>Content MVP: Publish one playbook or three how\u2011to posts and capture emails; watch search impressions and reply rates for signal within two weeks.<\/li>\n<li>Build\u2011in\u2011public\/community: Share weekly product updates on X\/LinkedIn and spin up a lightweight Discord; track engaged members and referral sign\u2011ups.<\/li>\n<li>Programmatic SEO probe: Generate 10 templated pages for one topic cluster to gauge impressions and clicks before committing to hundreds.<\/li>\n<li>Partner channel dry run: Co\u2011brand a landing page with a niche newsletter or tool vendor; test CTR and conversion on a small send.<\/li>\n<\/ul>\n<p>Treat distribution as a first\u2011class hypothesis and you de\u2011risk go\u2011to\u2011market early, sharpen positioning, and ensure later product iterations plug into channels that already convert.<\/p>\n<\/section>\n<h2 class=\"wp-block-heading\">No-code and low\u2011code: democratizing experimentation<\/h2>\n<p>Around 2017, <strong>no\u2011code<\/strong> and <strong>low\u2011code<\/strong> platforms reshaped who could build:<\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Bubble &amp; Webflow<\/strong> let non\u2011technical founders spin up full web apps or SaaS front\u2011ends without touching JavaScript.<\/li>\n<li><strong>Airtable &amp; Glide<\/strong> allowed operations teams to create internal tools that looked and felt custom.<\/li>\n<li><strong>Zapier &amp; Make<\/strong> stitched together payment, email, and data pipelines\u2014so a weekend hacker could accept Stripe payments, store orders in Airtable, and send confirmation emails via SendGrid.<\/li>\n<\/ul>\n<p>The upshot? <strong>Experiment volume exploded.<\/strong> Marketers, PMs, and even students could now run cheap tests, turning MVP culture from an engineering specialty into a company\u2011wide habit.<\/p>\n<h2 class=\"wp-block-heading\">AI-powered MVPs: 2020s and beyond<\/h2>\n<p>The launch of <strong>GPT\u20113 (2020)<\/strong> and subsequent commoditization of large\u2011language\u2011model APIs marked a step\u2011change:<\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Conversational front\u2011ends:<\/strong> A simple prompt\u2011engineering script plus an LLM could impersonate a concierge service, letting founders gauge demand before writing domain\u2011specific logic.<\/li>\n<li><strong>Code generation:<\/strong> GitHub Copilot and similar tools auto\u2011scaffold CRUD apps, slashing dev time from weeks to hours.<\/li>\n<li><strong>Synthetic users:<\/strong> Agent\u2011based simulations now approximate real user journeys, letting teams stress\u2011test onboarding flows before live traffic.<\/li>\n<\/ul>\n<p>AI thereby shortened the build\u2011measure cycle to the point where <strong>MVP and prototype sometimes merge<\/strong>\u2014the <em>test<\/em> is built into the generative model itself.<\/p>\n<h2 class=\"wp-block-heading\">common pitfalls and lessons learned<\/h2>\n<p>Even seasoned teams stumble. The most persistent traps include:<\/p>\n<figure class=\"wp-block-table\">\n<table class=\"has-fixed-layout\">\n<thead>\n<tr>\n<th>Pitfall<\/th>\n<th>Why it happens<\/th>\n<th>How to avoid<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Vanity mvps<\/strong><\/td>\n<td>Building something easy, not something risky<\/td>\n<td>Articulate a <em>singular risky assumption<\/em> first and refuse features that don\u2019t test it<\/td>\n<\/tr>\n<tr>\n<td><strong>Scope creep<\/strong><\/td>\n<td>Fear of negative feedback<\/td>\n<td>Set an illness\u2011style <em>timebox<\/em> (e.g., ship in 2&nbsp;weeks) and freeze scope mid\u2011sprint<\/td>\n<\/tr>\n<tr>\n<td><strong>Success theater<\/strong><\/td>\n<td>Cherry\u2011picking favorable metrics<\/td>\n<td>Pre\u2011commit to a <em>threshold metric<\/em> and shut down if it isn\u2019t met<\/td>\n<\/tr>\n<tr>\n<td><strong>Survivor bias<\/strong><\/td>\n<td>Copying mvp tactics from success stories without matching context<\/td>\n<td>Examine <em>why<\/em> a tactic worked before porting it<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<h2 class=\"wp-block-heading\">The future of MVPs<\/h2>\n<p>Looking forward, several threads are converging:<\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Continuous experimentation:<\/strong> Feature flags and remote\u2011config frameworks (LaunchDarkly, GrowthBook) enable \u2018MVPs\u2019 that live <em>inside<\/em> production apps, shipping to 1% of users at a time.<\/li>\n<li><strong>Regulated\u2011space sandboxes:<\/strong> Fintech, med\u2011tech, and ed\u2011tech companies are piloting <em>compliance\u2011first<\/em> MVPs inside isolated data enclaves, where real\u2011world constraints are simulated before live deployment.<\/li>\n<li><strong>Autonomous product agents:<\/strong> Early research demos show AI agents that can propose hypotheses, spin up a micro\u2011front\u2011end, route traffic, and analyze results, cycling autonomously until a human intervenes.<\/li>\n<\/ul>\n<p>The MVP may soon become a perpetual background process rather than a discrete pre\u2011launch phase.<\/p>\n<h2 class=\"wp-block-heading\">Key takeaways<\/h2>\n<ul class=\"wp-block-list\">\n<li>An MVP is a means to <strong>validate learning<\/strong>, not a milestone shipment.<\/li>\n<li>Each era\u2014lean startup, mobile\u2011first, design thinking, no\u2011code, and AI\u2014has <strong>expanded who can experiment<\/strong> and <strong>accelerated iteration speed<\/strong>.<\/li>\n<li>The next frontier is <strong>continuous, autonomous MVPs<\/strong> embedded inside mature products, reducing the cycle time from weeks to minutes.<\/li>\n<\/ul>\n<section class=\"sob-cta-section\">\n  Ready to streamline your MVP work? Use StoriesOnBoard&#8217;s visual story mapping to clarify the customer journey and cut clean MVP slices. Start your 14-day free trial <a href=\"https:\/\/app.storiesonboard.com\/signup\">Here<\/a>.<br \/>\n<\/section>\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Bottom line:<\/strong> Whether you\u2019re a solo hacker or a global enterprise, the surest way to de\u2011risk innovation remains the same\u2014launch something small, measure everything, and let the data shape what comes next.<\/p>\n<\/blockquote>\n<section class=\"sob-faq-section\">\n<h2>MVP FAQ: From Lean Startup to AI\u2011Powered Experimentation<\/h2>\n<div class=\"sob-faq-section__items\">\n<article class=\"sob-faq-section__item\">\n<h3>How is an MVP different from v1.0?<\/h3>\n<p>An MVP tests a single critical uncertainty, not a full release. It ships the bare minimum for real users to try so you learn fast with minimal waste. v1.0 focuses on broader value and polish.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How do I pick the single riskiest assumption?<\/h3>\n<p>List risks across desirability, feasibility, and viability. Pick the one that would kill the idea if it\u2019s wrong. Turn it into a falsifiable hypothesis with a clear threshold\u2014e.g., \u201c10% of visitors join the waitlist.\u201d Build only what you need to test it.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How should I set success metrics for an MVP?<\/h3>\n<p>Precommit to one behavioral threshold\u2014sign-ups, activation, conversion, or churn. Use data from real users, not vanity metrics. If you miss the threshold, stop or pivot.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>When is a clickable prototype enough?<\/h3>\n<p>A clickable Figma or InVision is enough when you\u2019re testing usability or desirability and don\u2019t need live data or backend work. To validate market demand or technical feasibility, ship a minimal coded slice to real users.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How can no-code\/low-code help my team?<\/h3>\n<p>Webflow, Bubble, Airtable, and Zapier let non-engineers spin up flows and integrations fast. You run more experiments for less money, making MVPs a company habit. Pair them with data and compliance guardrails.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How does AI change MVP timelines?<\/h3>\n<p>LLMs power conversational front ends and crank out code, often blurring prototype and MVP. Synthetic users can stress-test flows before real traffic. The build\u2011measure loop shrinks from weeks to hours.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How do we avoid vanity MVPs and success theater?<\/h3>\n<p>Tie scope to one make-or-break question and timebox the work. Freeze scope mid-sprint to prevent bloat, and pick a threshold metric before you ship. Report every result, not just the wins.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How do we run MVPs in regulated industries?<\/h3>\n<p>Pilot in compliance-first sandboxes or isolated data enclaves using synthetic or minimized data. Use feature flags and staged rollouts to limit exposure. Loop in legal and security early to codify guardrails.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>What does continuous experimentation look like?<\/h3>\n<p>Feature flags and remote config let you ship MVPs to small cohorts in production. Iterate with tight telemetry and instant rollback, evolving features from live signals. Learning runs in the background, all the time.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>When do we pivot or persevere after an MVP?<\/h3>\n<p>If you miss the preset threshold, stop or change the hypothesis, audience, or channel. If you meet or beat it, tackle the next riskiest assumption. Turn every outcome into the next test in the loop.<\/p>\n<\/article><\/div>\n<\/section>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How is an MVP different from v1.0?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"An MVP tests a single critical uncertainty, not a full release. It ships the bare minimum for real users to try so you learn fast with minimal waste. v1.0 focuses on broader value and polish.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do I pick the single riskiest assumption?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"List risks across desirability, feasibility, and viability. Pick the one that would kill the idea if it\u2019s wrong. Turn it into a falsifiable hypothesis with a clear threshold\u2014e.g., \u201c10% of visitors join the waitlist.\u201d Build only what you need to test it.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How should I set success metrics for an MVP?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Precommit to one behavioral threshold\u2014sign-ups, activation, conversion, or churn. Use data from real users, not vanity metrics. If you miss the threshold, stop or pivot.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"When is a clickable prototype enough?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"A clickable Figma or InVision is enough when you\u2019re testing usability or desirability and don\u2019t need live data or backend work. To validate market demand or technical feasibility, ship a minimal coded slice to real users.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How can no-code\/low-code help my team?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Webflow, Bubble, Airtable, and Zapier let non-engineers spin up flows and integrations fast. You run more experiments for less money, making MVPs a company habit. Pair them with data and compliance guardrails.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How does AI change MVP timelines?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"LLMs power conversational front ends and crank out code, often blurring prototype and MVP. Synthetic users can stress-test flows before real traffic. The build\u2011measure loop shrinks from weeks to hours.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do we avoid vanity MVPs and success theater?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Tie scope to one make-or-break question and timebox the work. Freeze scope mid-sprint to prevent bloat, and pick a threshold metric before you ship. Report every result, not just the wins.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do we run MVPs in regulated industries?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Pilot in compliance-first sandboxes or isolated data enclaves using synthetic or minimized data. Use feature flags and staged rollouts to limit exposure. Loop in legal and security early to codify guardrails.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What does continuous experimentation look like?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Feature flags and remote config let you ship MVPs to small cohorts in production. Iterate with tight telemetry and instant rollback, evolving features from live signals. Learning runs in the background, all the time.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"When do we pivot or persevere after an MVP?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"If you miss the preset threshold, stop or change the hypothesis, audience, or channel. If you meet or beat it, tackle the next riskiest assumption. Turn every outcome into the next test in the loop.\"\n      }\n    }\n  ]\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Minimum viable products (MVPs) have evolved from a scrappy startup tactic to a mainstream product-development philosophy, now embraced by Fortune&nbsp;500 companies and student founders alike. Over almost two decades, the &#8230; <a title=\"The history of mvps: from lean startup to today\" class=\"read-more\" href=\"https:\/\/storiesonboard.com\/blog\/the-history-of-mvps-from-lean-startup-to-today\" aria-label=\"Read more about The history of mvps: from lean startup to today\">Read more<\/a><\/p>\n","protected":false},"author":13,"featured_media":6209,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-6208","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-story-mapping","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/posts\/6208","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/comments?post=6208"}],"version-history":[{"count":2,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/posts\/6208\/revisions"}],"predecessor-version":[{"id":6367,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/posts\/6208\/revisions\/6367"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/media\/6209"}],"wp:attachment":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/media?parent=6208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/categories?post=6208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/tags?post=6208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}