{"id":8488,"date":"2026-07-02T11:12:18","date_gmt":"2026-07-02T11:12:18","guid":{"rendered":"https:\/\/nextagile.ai\/blogs\/?p=8488"},"modified":"2026-07-03T04:18:35","modified_gmt":"2026-07-03T04:18:35","slug":"difference-between-design-and-design-thinking","status":"publish","type":"post","link":"https:\/\/nextagile.ai\/blogs\/design-thinking\/difference-between-design-and-design-thinking\/","title":{"rendered":"Difference Between Design and Design Thinking: Key Differences, Examples &#038; When to Use Each"},"content":{"rendered":"<h2>Key Takeaways From This Blog<\/h2>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Design and design thinking are not interchangeable<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Design improves solutions, design thinking validates direction<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Design thinking reduces risk by challenging assumptions early<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Design delivers value when guided by clear, evidence based problem definitions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Organizations succeed when discovery and delivery are tightly integrated<\/span><\/li>\n<\/ul>\n<h2>Introduction<\/h2>\n<p><span style=\"font-weight: 400;\">Design and design thinking are often used as interchangeable terms, especially in digital transformation and product conversations. Yet they represent two very different capabilities. One focuses on shaping solutions. The other focuses on understanding what should be solved in the first place.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Design improves how something looks, feels, and works. Design thinking examines whether the solution being built actually matters to users and the business. When organizations confuse the two, they often invest in beautifully executed outcomes that fail to deliver real value.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At <\/span><b>NextAgile<\/b><span style=\"font-weight: 400;\">, we regularly see teams redesign interfaces, launch features, or rebrand experiences without ever questioning the original problem statement. The result is high execution efficiency applied to the wrong challenge.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This pillar page clarifies:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The difference between design and design thinking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How design thinking vs design affects outcomes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Where organizations lose momentum and trust<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How to combine both approaches for sustained impact<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Understanding this distinction is critical for leaders who want innovation that delivers measurable results, not just better looking outputs. Many organizations jump straight into execution without validating the problem. This confusion between design and design thinking is one of the most common reasons transformation efforts fail.<\/span><\/p>\n<h2>Definition of Design<\/h2>\n<p><span style=\"font-weight: 400;\">Design is the discipline of shaping how users experience a solution once a direction has already been chosen. It focuses on execution, usability, and clarity.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In most organizations, design begins after a problem statement is locked and budgets are approved. Designers are asked to make something usable, intuitive, and visually coherent within given constraints.<\/span><\/p>\n<h3>Core characteristics of design<\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Focuses on tangible outputs such as interfaces, products, services, or environments<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Follows a largely linear flow from brief to delivery<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Relies on specialist expertise such as UX design, UI design, industrial design, or service design<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Engages users mainly during validation or usability testing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delivers polish, consistency, and functional excellence<\/span><\/li>\n<\/ul>\n<h3>Why design alone is not enough<\/h3>\n<p><span style=\"font-weight: 400;\">Design is extremely effective at improving experiences when the problem is well understood. However, it rarely questions whether the original problem is valid.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When design operates without deeper discovery, organizations often experience:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Late feedback that forces costly rework<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Strong usability paired with weak adoption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Solutions that optimize surface issues while deeper user pain remains unresolved<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Design makes things work better. It does not always ensure that the right thing is being built.<\/span><\/p>\n<h2>Definition of Design Thinking<\/h2>\n<p><span style=\"font-weight: 400;\">Design thinking is a human centered approach to solving complex and ambiguous problems. It focuses on understanding people, reframing challenges, and learning before committing to execution.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Unlike traditional design, design thinking does not begin with solutions. It begins with curiosity, empathy, and evidence.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you&#8217;re new to the methodology, explore our complete guide on <\/span><a href=\"https:\/\/nextagile.ai\/blogs\/design-thinking\/what-is-design-thinking\/\"><b>What is Design Thinking<\/b><\/a><span style=\"font-weight: 400;\"> to understand its principles, process, and real-world applications.<\/span><\/p>\n<h3>Core principles of design thinking<\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Starts with understanding user context, behavior, and unmet needs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Treats problem definition as a hypothesis, not a given<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Uses iterative cycles of exploration, ideation, and testing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Involves users continuously, not just at the end<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Brings together cross functional teams across business, technology, and design<\/span><\/li>\n<\/ul>\n<h3>Why design thinking changes outcomes<\/h3>\n<p><span style=\"font-weight: 400;\">Design thinking helps teams avoid building solutions that are well designed but fundamentally unnecessary. It reduces the risk of investing in ideas that feel logical internally but fail externally.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In practice, design thinking helps organizations :<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Identify the real source of user frustration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Discover simpler or non obvious solutions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Align stakeholders around evidence instead of assumptions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Make better decisions earlier, when change is cheaper<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Design thinking does not replace design capability. It creates the conditions for design to succeed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Organizations adopting this approach also experience several long-term <\/span><a href=\"https:\/\/nextagile.ai\/blogs\/design-thinking\/benefits-of-design-thinking\/\"><b>benefits of Design Thinking<\/b><\/a><span style=\"font-weight: 400;\">, including faster innovation, improved collaboration, and reduced product risk.<\/span><\/p>\n<h2>Design vs Design Thinking: A Clear Comparison<\/h2>\n<table>\n<tbody>\n<tr>\n<td><b>Dimension<\/b><\/td>\n<td><b>Design<\/b><\/td>\n<td><b>Design Thinking<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Primary focus<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Execution of solutions<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Understanding and reframing problems<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Starting point<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Approved brief or requirement<\/span><\/td>\n<td><span style=\"font-weight: 400;\">User needs and unresolved questions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Process nature<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Linear and delivery driven<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Iterative and exploratory<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">User involvement<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Primarily validation focused<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Continuous and participatory<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ownership<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Design specialists<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Cross functional teams<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Value created<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Usability and visual clarity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Relevance and strategic alignment<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Risk profile<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High if problem is unclear<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Lower due to early learning<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Where organizations get confused<\/h3>\n<p><span style=\"font-weight: 400;\">Many teams assume that adding UX research or running workshops means they are doing design thinking. In reality, design thinking only works when insights influence decisions, not just presentations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The most common failure patterns we see include:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Jumping straight into solution mode after a <\/span><a href=\"https:\/\/nextagile.ai\/workshop\/design-thinking-masterclass-workshop\/\"><span style=\"font-weight: 400;\">workshop<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Treating design thinking as a one time activity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Separating discovery teams from delivery teams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Measuring success by output volume instead of outcome quality<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">This confusion leads to frustration, fatigue, and skepticism toward innovation initiatives.<\/span><\/p>\n<h2>Benefits and Limitations in Practice<\/h2>\n<h3>Strengths of design<\/h3>\n<p><span style=\"font-weight: 400;\">Design delivers clarity and quality. It ensures that solutions are usable, consistent, and aligned with brand intent.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, design depends heavily on the quality of the brief it receives. When that brief is flawed, even excellent execution cannot compensate.<\/span><\/p>\n<h3>Strengths of design thinking<\/h3>\n<p><span style=\"font-weight: 400;\">Design thinking brings relevance. It helps teams slow down at the right moment to avoid accelerating in the wrong direction.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Its limitation is not the method itself, but how it is applied. Without skilled facilitation and clear decision ownership, teams may get stuck in exploration without momentum.<\/span><\/p>\n<h3>The real issue is not choosing one<\/h3>\n<p><span style=\"font-weight: 400;\">The problem is not design versus design thinking. The real issue is using either in isolation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Design without design thinking risks irrelevance.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">Design thinking without design risks stagnation.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In many organizations, design thinking works best when combined with Agile delivery practices, allowing teams to continuously validate ideas while delivering value incrementally. Learn how <\/span><a href=\"https:\/\/nextagile.ai\/blogs\/agile\/design-thinking-vs-agile-vs-lean-startup\/\"><b>Design Thinking, Agile, and Lean Startup<\/b><\/a><span style=\"font-weight: 400;\"> complement each other in product innovation\u00a0<\/span><\/p>\n<h2>Why Most Organizations Lose Momentum<\/h2>\n<p><span style=\"font-weight: 400;\">This is where many readers disengage because the reality feels uncomfortably familiar.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In our work at NextAgile, we see a recurring pattern:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Discovery teams generate insights that never shape delivery<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delivery teams inherit decisions they did not help validate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Leaders lose patience with ambiguity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Teams default back to output driven execution<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The result is a cycle of redesigns, missed expectations, and declining trust in transformation efforts.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What is missing is not capability. It is integration.<\/span><\/p>\n<h2>A Practical Decision Framework<\/h2>\n<p><span style=\"font-weight: 400;\">To make this distinction actionable, here is a simple decision lens.<\/span><\/p>\n<h3>Use design when:<\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The problem is clearly defined<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">User needs are already validated<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Speed and consistency are priorities<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">You are refining or scaling an existing solution<\/span><\/li>\n<\/ul>\n<h3>Use design thinking when:<\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Adoption is low or declining<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">User behavior does not match expectations<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The problem feels unclear or contested<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Innovation or differentiation is required<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">A deeper understanding of customer behavior often starts with practical tools like <\/span><a href=\"https:\/\/nextagile.ai\/blogs\/design-thinking\/the-essential-guide-to-empathy-maps-and-user-personas\/\"><b>empathy maps and user personas<\/b><\/a><span style=\"font-weight: 400;\">, which help teams uncover user needs before moving into solution design.\u00a0<\/span><\/p>\n<h3>Use both when:<\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The solution must be desirable, feasible, and viable<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Long term value matters more than short term output<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Multiple stakeholders influence success<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">This clarity helps teams decide how to invest their time and energy.<\/span><\/p>\n<p><b>Combining Design and Design Thinking at Scale<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The most effective organizations treat design thinking as a decision making system and design as an execution capability. Many enterprises accelerate this transition through expert <\/span><a href=\"https:\/\/nextagile.ai\/design-thinking-consulting-services\/\"><b>Design Thinking Consulting Services<\/b><\/a><span style=\"font-weight: 400;\"> that combine customer research, facilitation, and execution support.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A practical integration looks like this:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Begin with design thinking to explore context, behavior, and unmet needs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Translate insights into clear problem statements and success criteria<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use design expertise to craft solutions that meet those criteria<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Maintain feedback loops so learning continues beyond launch<\/span><\/li>\n<\/ol>\n<h3>Real world example<\/h3>\n<p><span style=\"font-weight: 400;\">In a large enterprise transformation, a team planned to launch a new internal platform. Early design work focused on navigation and visual hierarchy. Design thinking revealed that employees did not trust the system due to past failures.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The solution shifted from interface redesign to workflow simplification and trust building through transparency. Design then played a critical role in making that experience intuitive and credible.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Without design thinking, the platform would have launched faster and failed quietly.<\/span><\/p>\n<h2>Conclusion<\/h2>\n<p><span style=\"font-weight: 400;\">Design and design thinking serve different but complementary purposes. Design ensures quality and usability. Design thinking ensures relevance and impact.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Organizations that rely only on design often execute efficiently on flawed assumptions. Organizations that rely only on design thinking often struggle to move from insight to action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">As a <\/span><a href=\"https:\/\/nextagile.ai\/design-thinking-consulting-services\/\"><span style=\"font-weight: 400;\">Design thinking consulting firm<\/span><\/a><span style=\"font-weight: 400;\">, NextAgile, we help teams integrate both capabilities so they can solve the right problems and deliver solutions that matter. This balance is what turns good ideas into sustained outcomes.<\/span><\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>1. What role does user feedback play in design versus design thinking?<\/h3>\n<p><span style=\"font-weight: 400;\">In design, feedback typically validates solutions. In design thinking, feedback shapes the problem, direction, and priorities from the start.<\/span><\/p>\n<h3>2. When should design thinking be used instead of traditional design?<\/h3>\n<p><span style=\"font-weight: 400;\">Design thinking is most effective when challenges are ambiguous, user needs are unclear, or innovation is required.<\/span><\/p>\n<h3>3. Are there limitations to design thinking?<\/h3>\n<p><span style=\"font-weight: 400;\">Yes. Without discipline, it can feel slow or vague. Its value depends on how insights influence decisions.<\/span><\/p>\n<h3>4. What is the primary difference between design and design thinking?<\/h3>\n<p><span style=\"font-weight: 400;\">Design focuses on creating solutions. Design thinking focuses on identifying the right problems to solve.<\/span><\/p>\n<h3>5. How do the processes differ?<\/h3>\n<p><span style=\"font-weight: 400;\">Design follows a linear path toward delivery. Design thinking is iterative and learning driven.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Key Takeaways From This Blog Design and design thinking are not interchangeable Design improves solutions, design thinking validates direction Design thinking reduces risk by challenging assumptions early Design delivers value when guided by clear, evidence based problem definitions Organizations succeed when discovery and delivery are tightly integrated Introduction Design and design thinking are often used&#8230;<\/p>\n","protected":false},"author":2,"featured_media":8492,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-8488","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-design-thinking"],"_links":{"self":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/8488","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/comments?post=8488"}],"version-history":[{"count":4,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/8488\/revisions"}],"predecessor-version":[{"id":8496,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/8488\/revisions\/8496"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media\/8492"}],"wp:attachment":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media?parent=8488"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/categories?post=8488"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/tags?post=8488"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}