{"id":21148,"date":"2019-02-01T09:28:25","date_gmt":"2019-02-01T15:28:25","guid":{"rendered":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/"},"modified":"2019-02-01T09:28:25","modified_gmt":"2019-02-01T15:28:25","slug":"why-we-need-a-shared-understanding-of-technical-debt","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/","title":{"rendered":"Why we need a shared understanding of technical debt"},"content":{"rendered":"
\n
\"Why<\/div>\n<\/figure>\n

Helping business leaders and technologists to speak the same language is a key purpose of Project to Product<\/em><\/a> and the goal of the Flow Framework™<\/a>. After all, both IT leaders and business executives share the same objective; to bring more value to the internal and external customers that we serve. Given the massive investment that organizations are making in software, we need a common understanding of the key concepts that define whether software platforms will succeed or fail. In my experience, one of the concepts that has the least shared understanding is one of the most fundamental to software delivery, and that is the concept of tech debt.<\/p>\n

Developers understand tech debt because they make daily decisions that require them to continually strike a balance between taking multiple shortcuts to get a feature completed, or investing time in generalizing the concepts of that feature to make features of that sort easier to build in the future. Due to customer pull for features, the shortcuts often win, and tech debt builds up. The challenge is that the pressure from the customer and the business rarely prioritizes tech debt reduction. Some forward-looking tech companies apply coarse principles, such as assigning 20 percent of work from each release to tech debt reduction. But nobody seems quite sure whether that number is what will deliver the most customer value at the end of the day.<\/p>\n

Frameworks such as SAFe try to elevate the concept of tech debt through Refactor story types to ensure that these get first class visibility on backlog prioritization. But what I learned through the research that led up to Project to Product is that not even that is enough. For companies to avoid the fate of the Nokia story told in the book, the concept of tech debt needs to be elevated right to the top level of the business and the executive team. Without the understanding of tech debt in strategic planning, the executive team cannot direct and protect the company through the Age of Software. That was the motivation of making Debt items a first-class part of the Flow Framework™.<\/p>\n

We need to fill this gap. A CEO should care, or at least be shown why they should care. Whether the boardroom likes it or not, tech debt can be just as lethal to a company’s success as financial debt and should be assessed and treated accordingly. In my article How to budget for your company’s technical debt<\/em><\/a>, I explain how technical debt impacts the business, how we can make it visible to improve the flow of business value across the software delivery process, and why we should budget for it to achieve the business and customer outcomes that we seek.<\/p>\n

To learn more, grab yourself a copy of Project to Product <\/em><\/a>(<\/em>available in print, digital and audio).<\/p>\n

Project to Product <\/em>is available in print, digital and audio. Order a copy today by clicking on the front cover:<\/p>\n

<\/a>
Click image to pre-order a copy of the book.<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"

Helping business leaders and technologists to speak the same language is a key purpose of Project to Product and the goal of the Flow Framework™. After all, both IT leaders and business executives share the same objective; to bring more value to the internal and external customers that we serve. Given the massive investment that organizations are making…<\/p>\n","protected":false},"author":222,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_editorskit_title_hidden":false,"_editorskit_reading_time":0,"_editorskit_is_block_options_detached":false,"_editorskit_block_options_position":"{}","footnotes":""},"categories":[9544,9543],"tags":[],"class_list":["post-21148","post","type-post","status-publish","format-standard","hentry","category-project-to-product-shift","category-value-stream-management"],"acf":[],"yoast_head":"\nWhy we need a shared understanding of technical debt | Tasktop Blog<\/title>\n<meta name=\"description\" content=\"Tech debt can be just as lethal to a company's success as financial debt and should be managed accordingly to survive and thrive in the Age of Software.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why we need a shared understanding of technical debt\" \/>\n<meta property=\"og:description\" content=\"Tech debt can be just as lethal to a company's success as financial debt and should be managed accordingly to survive and thrive in the Age of Software.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/\" \/>\n<meta property=\"og:site_name\" content=\"Planview Blog\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772\" \/>\n<meta property=\"article:published_time\" content=\"2019-02-01T15:28:25+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/media.planview.com\/tasktop_blog\/wp-content\/uploads\/2019\/02\/tasktop-technical-debt.png\" \/>\n<meta name=\"author\" content=\"Mik Kersten\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Planview\" \/>\n<meta name=\"twitter:site\" content=\"@Planview\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Mik Kersten\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/\"},\"author\":{\"name\":\"Mik Kersten\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#\\\/schema\\\/person\\\/6be5164e0beb8c6fe553a8baed3610c1\"},\"headline\":\"Why we need a shared understanding of technical debt\",\"datePublished\":\"2019-02-01T15:28:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/\"},\"wordCount\":520,\"publisher\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/media.planview.com\\\/tasktop_blog\\\/wp-content\\\/uploads\\\/2019\\\/02\\\/tasktop-technical-debt.png\",\"articleSection\":[\"Project to Product Shift\",\"Value Stream Management\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/\",\"name\":\"Why we need a shared understanding of technical debt | Tasktop Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/media.planview.com\\\/tasktop_blog\\\/wp-content\\\/uploads\\\/2019\\\/02\\\/tasktop-technical-debt.png\",\"datePublished\":\"2019-02-01T15:28:25+00:00\",\"description\":\"Tech debt can be just as lethal to a company's success as financial debt and should be managed accordingly to survive and thrive in the Age of Software.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/#primaryimage\",\"url\":\"https:\\\/\\\/media.planview.com\\\/tasktop_blog\\\/wp-content\\\/uploads\\\/2019\\\/02\\\/tasktop-technical-debt.png\",\"contentUrl\":\"https:\\\/\\\/media.planview.com\\\/tasktop_blog\\\/wp-content\\\/uploads\\\/2019\\\/02\\\/tasktop-technical-debt.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/why-we-need-a-shared-understanding-of-technical-debt\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.planview.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why we need a shared understanding of technical debt\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#website\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/\",\"name\":\"Planview Blog\",\"description\":\"Leading the conversation on digital connected work\",\"publisher\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blog.planview.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#organization\",\"name\":\"Planview\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/wp-content\\\/uploads\\\/2015\\\/06\\\/planview-logo-black.png\",\"contentUrl\":\"https:\\\/\\\/blog.planview.com\\\/wp-content\\\/uploads\\\/2015\\\/06\\\/planview-logo-black.png\",\"width\":280,\"height\":66,\"caption\":\"Planview\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"http:\\\/\\\/www.facebook.com\\\/pages\\\/Planview-Inc\\\/89422974772\",\"https:\\\/\\\/x.com\\\/Planview\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blog.planview.com\\\/#\\\/schema\\\/person\\\/6be5164e0beb8c6fe553a8baed3610c1\",\"name\":\"Mik Kersten\",\"description\":\"Dr. Mik Kersten started his career as a Research Scientist at Xerox PARC where he created the first aspect-oriented development environment. He then pioneered the integration of development tools with Agile and DevOps as part of his Computer Science PhD at the University of British Columbia. Founding Tasktop out of that research, Mik has written over one million lines of open source code that are still in use today, and he has brought seven successful open-source and commercial products to market. Mik\u2019s experiences working with some of the largest digital transformations in the world has led him to identify the critical disconnect between business leaders and technologists. Since then, Mik has been working on creating new tools and a new framework - the Flow Framework\u2122 - for connecting software value stream networks and enabling the shift from project to product. Mik lives with his family in Vancouver, Canada, and travels globally, sharing his vision for transforming how software is built, and is the author of Project To Product, a book that helps IT organizations survive and thrive in the Age of Software.\",\"url\":\"https:\\\/\\\/blog.planview.com\\\/author\\\/mik-kersten\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Why we need a shared understanding of technical debt | Tasktop Blog","description":"Tech debt can be just as lethal to a company's success as financial debt and should be managed accordingly to survive and thrive in the Age of Software.","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:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/","og_locale":"en_US","og_type":"article","og_title":"Why we need a shared understanding of technical debt","og_description":"Tech debt can be just as lethal to a company's success as financial debt and should be managed accordingly to survive and thrive in the Age of Software.","og_url":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/","og_site_name":"Planview Blog","article_publisher":"http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772","article_published_time":"2019-02-01T15:28:25+00:00","og_image":[{"url":"https:\/\/media.planview.com\/tasktop_blog\/wp-content\/uploads\/2019\/02\/tasktop-technical-debt.png","type":"","width":"","height":""}],"author":"Mik Kersten","twitter_card":"summary_large_image","twitter_creator":"@Planview","twitter_site":"@Planview","twitter_misc":{"Written by":"Mik Kersten","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/#article","isPartOf":{"@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/"},"author":{"name":"Mik Kersten","@id":"https:\/\/blog.planview.com\/#\/schema\/person\/6be5164e0beb8c6fe553a8baed3610c1"},"headline":"Why we need a shared understanding of technical debt","datePublished":"2019-02-01T15:28:25+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/"},"wordCount":520,"publisher":{"@id":"https:\/\/blog.planview.com\/#organization"},"image":{"@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/#primaryimage"},"thumbnailUrl":"https:\/\/media.planview.com\/tasktop_blog\/wp-content\/uploads\/2019\/02\/tasktop-technical-debt.png","articleSection":["Project to Product Shift","Value Stream Management"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/","url":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/","name":"Why we need a shared understanding of technical debt | Tasktop Blog","isPartOf":{"@id":"https:\/\/blog.planview.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/#primaryimage"},"image":{"@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/#primaryimage"},"thumbnailUrl":"https:\/\/media.planview.com\/tasktop_blog\/wp-content\/uploads\/2019\/02\/tasktop-technical-debt.png","datePublished":"2019-02-01T15:28:25+00:00","description":"Tech debt can be just as lethal to a company's success as financial debt and should be managed accordingly to survive and thrive in the Age of Software.","breadcrumb":{"@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/#primaryimage","url":"https:\/\/media.planview.com\/tasktop_blog\/wp-content\/uploads\/2019\/02\/tasktop-technical-debt.png","contentUrl":"https:\/\/media.planview.com\/tasktop_blog\/wp-content\/uploads\/2019\/02\/tasktop-technical-debt.png"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.planview.com\/why-we-need-a-shared-understanding-of-technical-debt\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.planview.com\/"},{"@type":"ListItem","position":2,"name":"Why we need a shared understanding of technical debt"}]},{"@type":"WebSite","@id":"https:\/\/blog.planview.com\/#website","url":"https:\/\/blog.planview.com\/","name":"Planview Blog","description":"Leading the conversation on digital connected work","publisher":{"@id":"https:\/\/blog.planview.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.planview.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/blog.planview.com\/#organization","name":"Planview","url":"https:\/\/blog.planview.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.planview.com\/#\/schema\/logo\/image\/","url":"https:\/\/blog.planview.com\/wp-content\/uploads\/2015\/06\/planview-logo-black.png","contentUrl":"https:\/\/blog.planview.com\/wp-content\/uploads\/2015\/06\/planview-logo-black.png","width":280,"height":66,"caption":"Planview"},"image":{"@id":"https:\/\/blog.planview.com\/#\/schema\/logo\/image\/"},"sameAs":["http:\/\/www.facebook.com\/pages\/Planview-Inc\/89422974772","https:\/\/x.com\/Planview"]},{"@type":"Person","@id":"https:\/\/blog.planview.com\/#\/schema\/person\/6be5164e0beb8c6fe553a8baed3610c1","name":"Mik Kersten","description":"Dr. Mik Kersten started his career as a Research Scientist at Xerox PARC where he created the first aspect-oriented development environment. He then pioneered the integration of development tools with Agile and DevOps as part of his Computer Science PhD at the University of British Columbia. Founding Tasktop out of that research, Mik has written over one million lines of open source code that are still in use today, and he has brought seven successful open-source and commercial products to market. Mik\u2019s experiences working with some of the largest digital transformations in the world has led him to identify the critical disconnect between business leaders and technologists. Since then, Mik has been working on creating new tools and a new framework - the Flow Framework\u2122 - for connecting software value stream networks and enabling the shift from project to product. Mik lives with his family in Vancouver, Canada, and travels globally, sharing his vision for transforming how software is built, and is the author of Project To Product, a book that helps IT organizations survive and thrive in the Age of Software.","url":"https:\/\/blog.planview.com\/author\/mik-kersten\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts\/21148","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/users\/222"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/comments?post=21148"}],"version-history":[{"count":0,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/posts\/21148\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/media?parent=21148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/categories?post=21148"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.planview.com\/wp-json\/wp\/v2\/tags?post=21148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}