{"id":430,"date":"2018-05-29T06:00:55","date_gmt":"2018-05-29T11:00:55","guid":{"rendered":"https:\/\/rb-sns.com\/RB\/blog\/?p=430"},"modified":"2018-05-28T14:28:13","modified_gmt":"2018-05-28T19:28:13","slug":"incremental-vs-all-in-change-and-enhancement-strategies","status":"publish","type":"post","link":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/","title":{"rendered":"Incremental vs. All-in Change and Enhancement Strategies"},"content":{"rendered":"<p>Sooner or later we have to consider how to\u00a0change our systems.\u00a0 This situation can come from growth in business, changes in technology (or requirements), or systems that have aged poorly.\u00a0 When we reach the point of deciding on a move we often have to decide on the incremental vs. all-in approach to achieve our goal.\u00a0 There are times when one choice or the other is obvious.\u00a0 However, I have found that we almost always have both of these options available.\u00a0 So let&#8217;s look at the risks and rewards commonly available to each decision.<\/p>\n<h2>An Incremental Approach<\/h2>\n<p>I find this option to be the most popular.\u00a0 In fact, you might be able to rattle off some rewards and a few risks faster than it takes to read this article.\u00a0 Nevertheless, it is helpful to go through the exercise and maybe a few items from either list will be new to your experience.<\/p>\n<h3 style=\"text-align: center;\">Pros<\/h3>\n<ul>\n<li>The Risk is Reduced: Less change and more options to bail out or adapt.<\/li>\n<li>Less Time Before Starting: Smaller changes can allow for less upfront planning.<\/li>\n<li>Time To Bake In: Users have small changes to learn rather than large ones.<\/li>\n<li>Less to Consider: Small scope of changes means less to worry about with each change cycle.<\/li>\n<li>Easier to Budget: Tighter range of change and time frames make it easier to budget for changes and cash flow the project.<\/li>\n<li>Avoid Re-inventing the Wheel: This approach allows pieces of the original system to survive\u00a0and remain untouched.\u00a0 Thus, business rules and proven validations do not have to be re-created.<\/li>\n<\/ul>\n<h3 style=\"text-align: center;\">Cons<\/h3>\n<ul>\n<li>Total Cost is Higher: Overhead for each cycle adds up.\u00a0 Therefore, more testing, deployment, and other phases will be repeated for each incremental\u00a0change.<\/li>\n<li>Longer Schedule: Much like the above item, the time to be done with changes is going to further in the future with an\u00a0incremental\u00a0approach.<\/li>\n<li>Legacy Decisions\/Constraints of the System: An incremental\u00a0approach will always be tied to the original system in some way.\u00a0 It does not allow for a fresh start or utterly new thinking.<\/li>\n<li>System Stability: Regular change can make the system appear unstable to users and might be the reality as repeated touching of the core system offers opportunities for simple mistakes and human error to degrade the system.<\/li>\n<li>Integrate Changes: No system is static.\u00a0 Changes are required for a variety of reasons, and an incremental approach does not allow us to ignore change requests.\u00a0 Extra effort is needed to manage change requirements and fixes along with the new\/improved features being implemented.<\/li>\n<\/ul>\n<h2>An All-In Approach<\/h2>\n<p>This is a more courageous decision in almost every case.\u00a0 In fact, this approach often results (directly or indirectly) as one that makes or breaks a job (or career).\u00a0 The rewards are higher when this is correctly executed as there is more freedom to make huge strides.\u00a0 That said, there is a lot to worry about as well.\u00a0 Here are some of the pros and cons of this decision.<\/p>\n<h3 style=\"text-align: center;\">Pros<\/h3>\n<ul>\n<li>Total Cost is Lower: A significant change requires a lot of testing and deployment work.\u00a0 However, it amounts to fewer cycles and general overhead than an incremental approach.<\/li>\n<li>Freedom to Innovate: The lack of ties to a legacy system allows us to learn from past successes while avoiding past mistakes.\u00a0Substantial and meaningful changes can be made in this effort.<\/li>\n<li>Shorter Time to Completion: There is not a need to run in serial as is needed in the incremental approach.\u00a0 Resources can be poured into the all-in solution.\u00a0 Thus, progress can be made in parallel with the current systems continuing to run.<\/li>\n<li>More Stability For Users: This approach will result in a significant change when it goes live.\u00a0 However, other than that point in time, the users will experience a stable and reliable system.<\/li>\n<li>Less Elegant Utilities: A one-time step of significant change means the tools and utilities to do so only need to work once.\u00a0 This is the opposite of the design required to make the same tools work when you know there will be multiple, smaller, executions of them.<\/li>\n<\/ul>\n<h3 style=\"text-align: center;\">Cons<\/h3>\n<ul>\n<li>The Risk is Higher: When you make a significant change and choose wrong, it can result in a crippling loss to the company.\u00a0 This can have productivity and financial repercussions.<\/li>\n<li>More Time Before Starting: Planning and design are needed for the entire system to properly execute the all-in approach.\u00a0 Every little detail needs to be addressed to reduce the risk of a complete failure.<\/li>\n<li>More significant and Impactful Change: The substantial change of an all-in approach is hard to hide.\u00a0 Often it will require training for the users to help them utilize the new system.\u00a0 Alterations of business rules and procedures are often part of the content for\u00a0deploying this solution.<\/li>\n<li>Total Review and Design: The broad scope of changes require the entire system to be reviewed and understood.<\/li>\n<li>Large Budget: A substantial project like this is harder to estimate and often includes more funding in a short period.\u00a0 Incremental allows us to stretch out costs.<\/li>\n<li>Re-inventing the Wheel: Often this approach requires core functionality to be rebuilt or re-coded and tested again.\u00a0 This amounts to re-inventing the wheel for business rules and other functions.<\/li>\n<\/ul>\n<p>As you can see, there is a lot to consider with either approach.\u00a0 The pros and cons balance out more often than we think they do.\u00a0 Therefore, it is worth it to leave both options on the table on at least a periodic basis.\u00a0 This will ensure we avoid knee-jerk reactions to one approach or the other.\u00a0 As always, the more we know, the more we consider, the higher the likelihood of a successful decision.<\/p>\n<h2>Going Deeper<\/h2>\n<h3 style=\"text-align: center;\">Incremental Changes<\/h3>\n<p>When you look at the pros and cons of this approach, there are some essential assumptions made.\u00a0 If you take a path that does not follow the premises, then the pros and cons will differ.\u00a0 The &#8220;time before starting&#8221; and &#8220;less to consider&#8221;\u00a0pros, in particular, are impacted by your approach to design. The assumption for incremental changes is that you will plan and design as you go.\u00a0 This may not be the case.\u00a0 Some organizations prefer to create and plan out their entire series of changes up front.\u00a0 While this is a good approach, there are also valid reasons to hold off on a complete design when you are not sure far you want to progress.<\/p>\n<p>Similarly, the time to bake in and system stability items may vary in your experience.\u00a0 There are ways to drag out an incremental approach so that the users do not experience noticeable changes.\u00a0 Instead, they see undergo the changes as occasional enhancements.\u00a0 However, this approach can significantly increase the time to completion and may increase the limits to what can be done (due to ties to the current system).<\/p>\n<p>Finally, let&#8217;s look at the re-inventing the wheel item.\u00a0 An incremental approach can do this as well.\u00a0 Typically, an organization will avoid touching the things that &#8220;work.&#8221;\u00a0 The argument is that there is no reason to put effort into fixing something that is not broken.\u00a0 On the other hand, when a core functionality can be improved, then it may be worth taking on that change at some point.\u00a0 There is also the side effect that can occur where a core and stable piece of functionality is changed or even broken through changing other areas of the application.<\/p>\n<h3 style=\"text-align: center;\">All-In Advances<\/h3>\n<p>It should be clear that the all-in approach, in this case, is deploying all the changes in virtually a single push to production.\u00a0 This can be a large number of changes to an existing solution, replacing one with another system, or starting from scratch.\u00a0 Each of these three options has a very different set of pros and cons along with those mentioned.<\/p>\n<p>An important note about the all-in approach is that the sunk-cost fallacy should always be avoided.\u00a0 There are many cases where companies dismiss an all-in change because they start with the idea of value for the existing solution.\u00a0 Yes, there is knowledge and expertise and even momentum that the current system has.\u00a0 However, if those aspects are all driving you over a cliff then how valuable are they?\u00a0 Along with this, technology is always changing.\u00a0 The options we had a few years ago are not the same today.\u00a0 There are new solutions and standards available that might bring overwhelming value to an original or from-scratch system.\u00a0 It is easy to stay with the momentum we have, but sometimes all that provides us with is false confidence.<\/p>\n<h2>Final Thought<\/h2>\n<p>The bottom line in considering the pros and cons of these approaches is that your mileage may vary.\u00a0 In order to make these aspects real some intentionality is required.\u00a0 For example, if you want to reduce risk through an incremental approach to change, then each step needs to be examined thoroughly.\u00a0 This examination includes looking for potential side effects and downstream impact.\u00a0 None of these pros or cons are automatic, and the right approach can highlight the pros while reducing the cons.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sooner or later we have to consider how to\u00a0change our systems.\u00a0 This situation can come from growth in business, changes in technology (or requirements), or systems that have aged poorly.\u00a0 When we reach the point of deciding on a move we often have to decide on the incremental vs. all-in approach to achieve our goal.\u00a0 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":431,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[13],"tags":[4,21,28,9,34],"class_list":["post-430","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-consulting-strategies","tag-best-practices","tag-consulting","tag-planning","tag-projects","tag-software-development"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Incremental vs. All-in Change and Enhancement Strategies -<\/title>\n<meta name=\"description\" content=\"There are ways to find the middle ground. However, we usually only have two options in considering incremental vs. all-in as our approach to change. Small or large increments are still very different from a &quot;back to the blackboard&quot; or all-in approach.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Incremental vs. All-in Change and Enhancement Strategies -\" \/>\n<meta property=\"og:description\" content=\"There are ways to find the middle ground. However, we usually only have two options in considering incremental vs. all-in as our approach to change. Small or large increments are still very different from a &quot;back to the blackboard&quot; or all-in approach.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/\" \/>\n<meta property=\"article:published_time\" content=\"2018-05-29T11:00:55+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"512\" \/>\n\t<meta property=\"og:image:height\" content=\"382\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Rob Broadhead\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@rbcposts\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rob Broadhead\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/\"},\"author\":{\"name\":\"Rob Broadhead\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/person\/7a90d1b48e7e23c820769e418263da94\"},\"headline\":\"Incremental vs. All-in Change and Enhancement Strategies\",\"datePublished\":\"2018-05-29T11:00:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/\"},\"wordCount\":1507,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg\",\"keywords\":[\"best practices\",\"consulting\",\"planning\",\"projects\",\"software development\"],\"articleSection\":[\"Consulting Strategies\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/\",\"url\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/\",\"name\":\"Incremental vs. All-in Change and Enhancement Strategies -\",\"isPartOf\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg\",\"datePublished\":\"2018-05-29T11:00:55+00:00\",\"description\":\"There are ways to find the middle ground. However, we usually only have two options in considering incremental vs. all-in as our approach to change. Small or large increments are still very different from a \\\"back to the blackboard\\\" or all-in approach.\",\"breadcrumb\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage\",\"url\":\"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg\",\"contentUrl\":\"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg\",\"width\":512,\"height\":382,\"caption\":\"incremental vs. all-in\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/rb-sns.com\/RB\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Incremental vs. All-in Change and Enhancement Strategies\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#website\",\"url\":\"https:\/\/rb-sns.com\/RB\/blog\/\",\"name\":\"\",\"description\":\"Technology That Serves the Business, Not the Other Way Around\",\"publisher\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/rb-sns.com\/RB\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#organization\",\"name\":\"RB Consulting, Inc.\",\"url\":\"https:\/\/rb-sns.com\/RB\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2016\/12\/RBLogo.png\",\"contentUrl\":\"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2016\/12\/RBLogo.png\",\"width\":256,\"height\":256,\"caption\":\"RB Consulting, Inc.\"},\"image\":{\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/robbroadhead\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/person\/7a90d1b48e7e23c820769e418263da94\",\"name\":\"Rob Broadhead\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/bd120f8660b05d3d93d8889bc23970acf7146d65968ccea2a3f4ff25a38e28f9?s=96&d=mm&r=pg\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/bd120f8660b05d3d93d8889bc23970acf7146d65968ccea2a3f4ff25a38e28f9?s=96&d=mm&r=pg\",\"caption\":\"Rob Broadhead\"},\"description\":\"Rob is a seasoned software developer and technology professional. His background includes over 30 years of development. It includes enterprise systems on a wide variety of system architectures and platforms. His roles have included staff developer, director of development, architect, database administrator, and many points in between. He founded RB Consulting as a software development and implementation consulting company. However, after witnessing a significant number of poorly planned and designed projects, he altered the business focus. The primary focus is on helping customers put together well-designed project plans and navigating the vast sea of technology. This includes building teams\/departments to address IT needs in the future as well as for today. There is also still a software development wing of the company and implementation consulting. Rob received his MBA (with a concentration in e-Business) at the University of Phoenix. He also holds a BS in Computer Science from Rose-Hulman Institute of Technology. He has written and published a semi-biographical book, e-books, and a book on software development careers. He is a podcaster (The Building Better Developers\/Develpreneur podcast) and a regular contributor to Develpreneur, as well as his personal blog on this site.\",\"sameAs\":[\"https:\/\/develpreneur.com\",\"https:\/\/linkedin.com\/robbroadhead\",\"https:\/\/x.com\/rbcposts\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Incremental vs. All-in Change and Enhancement Strategies -","description":"There are ways to find the middle ground. However, we usually only have two options in considering incremental vs. all-in as our approach to change. Small or large increments are still very different from a \"back to the blackboard\" or all-in approach.","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:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/","og_locale":"en_US","og_type":"article","og_title":"Incremental vs. All-in Change and Enhancement Strategies -","og_description":"There are ways to find the middle ground. However, we usually only have two options in considering incremental vs. all-in as our approach to change. Small or large increments are still very different from a \"back to the blackboard\" or all-in approach.","og_url":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/","article_published_time":"2018-05-29T11:00:55+00:00","og_image":[{"width":512,"height":382,"url":"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg","type":"image\/jpeg"}],"author":"Rob Broadhead","twitter_card":"summary_large_image","twitter_creator":"@rbcposts","twitter_misc":{"Written by":"Rob Broadhead","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#article","isPartOf":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/"},"author":{"name":"Rob Broadhead","@id":"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/person\/7a90d1b48e7e23c820769e418263da94"},"headline":"Incremental vs. All-in Change and Enhancement Strategies","datePublished":"2018-05-29T11:00:55+00:00","mainEntityOfPage":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/"},"wordCount":1507,"commentCount":0,"publisher":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/#organization"},"image":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage"},"thumbnailUrl":"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg","keywords":["best practices","consulting","planning","projects","software development"],"articleSection":["Consulting Strategies"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/","url":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/","name":"Incremental vs. All-in Change and Enhancement Strategies -","isPartOf":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage"},"image":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage"},"thumbnailUrl":"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg","datePublished":"2018-05-29T11:00:55+00:00","description":"There are ways to find the middle ground. However, we usually only have two options in considering incremental vs. all-in as our approach to change. Small or large increments are still very different from a \"back to the blackboard\" or all-in approach.","breadcrumb":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#primaryimage","url":"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg","contentUrl":"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2018\/05\/changestrategy.jpg","width":512,"height":382,"caption":"incremental vs. all-in"},{"@type":"BreadcrumbList","@id":"https:\/\/rb-sns.com\/RB\/blog\/incremental-vs-all-in-change-and-enhancement-strategies\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/rb-sns.com\/RB\/blog\/"},{"@type":"ListItem","position":2,"name":"Incremental vs. All-in Change and Enhancement Strategies"}]},{"@type":"WebSite","@id":"https:\/\/rb-sns.com\/RB\/blog\/#website","url":"https:\/\/rb-sns.com\/RB\/blog\/","name":"","description":"Technology That Serves the Business, Not the Other Way Around","publisher":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/rb-sns.com\/RB\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/rb-sns.com\/RB\/blog\/#organization","name":"RB Consulting, Inc.","url":"https:\/\/rb-sns.com\/RB\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2016\/12\/RBLogo.png","contentUrl":"https:\/\/rb-sns.com\/RB\/blog\/wp-content\/uploads\/2016\/12\/RBLogo.png","width":256,"height":256,"caption":"RB Consulting, Inc."},"image":{"@id":"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/in\/robbroadhead"]},{"@type":"Person","@id":"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/person\/7a90d1b48e7e23c820769e418263da94","name":"Rob Broadhead","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/rb-sns.com\/RB\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/bd120f8660b05d3d93d8889bc23970acf7146d65968ccea2a3f4ff25a38e28f9?s=96&d=mm&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/bd120f8660b05d3d93d8889bc23970acf7146d65968ccea2a3f4ff25a38e28f9?s=96&d=mm&r=pg","caption":"Rob Broadhead"},"description":"Rob is a seasoned software developer and technology professional. His background includes over 30 years of development. It includes enterprise systems on a wide variety of system architectures and platforms. His roles have included staff developer, director of development, architect, database administrator, and many points in between. He founded RB Consulting as a software development and implementation consulting company. However, after witnessing a significant number of poorly planned and designed projects, he altered the business focus. The primary focus is on helping customers put together well-designed project plans and navigating the vast sea of technology. This includes building teams\/departments to address IT needs in the future as well as for today. There is also still a software development wing of the company and implementation consulting. Rob received his MBA (with a concentration in e-Business) at the University of Phoenix. He also holds a BS in Computer Science from Rose-Hulman Institute of Technology. He has written and published a semi-biographical book, e-books, and a book on software development careers. He is a podcaster (The Building Better Developers\/Develpreneur podcast) and a regular contributor to Develpreneur, as well as his personal blog on this site.","sameAs":["https:\/\/develpreneur.com","https:\/\/linkedin.com\/robbroadhead","https:\/\/x.com\/rbcposts"]}]}},"_links":{"self":[{"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/posts\/430","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/comments?post=430"}],"version-history":[{"count":3,"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/posts\/430\/revisions"}],"predecessor-version":[{"id":434,"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/posts\/430\/revisions\/434"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/media\/431"}],"wp:attachment":[{"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/media?parent=430"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/categories?post=430"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rb-sns.com\/RB\/blog\/wp-json\/wp\/v2\/tags?post=430"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}