<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Drew Harteveld on Medium]]></title>
        <description><![CDATA[Stories by Drew Harteveld on Medium]]></description>
        <link>https://medium.com/@drewharteveld?source=rss-35f035fa02c3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*k6FrS_-3L-YnDWjbF5egNQ.jpeg</url>
            <title>Stories by Drew Harteveld on Medium</title>
            <link>https://medium.com/@drewharteveld?source=rss-35f035fa02c3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:10:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drewharteveld/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[We Can’t Finish Until We Stop Starting]]></title>
            <link>https://drewharteveld.medium.com/we-cant-finish-until-we-stop-starting-0abaf771f2c7?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0abaf771f2c7</guid>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Fri, 07 Jun 2024 18:44:26 GMT</pubDate>
            <atom:updated>2024-06-07T18:44:26.759Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rFR6qRUGQ_M63wLXwF3Ujw.jpeg" /></figure><h3>Managing the risk of requirements churn during the product development design phase</h3><p>Sometimes these posts come rolling right out of my noggin, and other times I struggle to articulate the point in a compact and understandable format. This post falls into the latter category. To help combat that situation, I’m going to drop the conclusion right up top:</p><h4>In Digital product development, the highest likelihood of change occurs at the beginning of the project lifecycle, during the design phase. We must recognize and expect that, including adequate time and cost into our planning so this eventuality doesn’t derail the project right out of the gate</h4><p>Okay, now that the truth is out there, let’s unpack it to understand why that is and how it should best be managed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWCGxhATFmp4CmC3LsjnXw.jpeg" /></figure><h3>Project Lifecycle and the Cone of Confusion</h3><p>Much has been discussed in this space about the power of standardized process in product development. Whether you utilize a software development lifecycle [SDLC] like my “5 big D’s” or some other approach, having a ready template to help map out new projects is a huge boost.</p><p>For the purposes of this discussion, let’s ignore the specific SDLC and simply represent progress as a single horizontal line with the project’s kickoff at far left, and completion at far right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*cVmS0E6Q1nDHpzRPgEbl3Q.png" /></figure><p>The “Cone of Confusion” is an Agile concept recognizing that we understand the scope, solution strategy, and implications of the project least at its beginning, and most on the day we finish. It is through the act of executing the project that we gain mastery over its subject matter. <em>Inconvenient timing, I know.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tAXQHivGaEBQaLtWLvC1-A.png" /></figure><p>Note that the cone of confusion is at its widest in the very beginning of the project. The further we move through the project, from left to right in the diagram above, the more clearly we understand its subject matter. And the more narrow that theoretical cone becomes.</p><p>Because our level of understanding is at its lowest in the initial phases of the project, that is also the area of greatest risk of change. <strong><em>This makes sense, right?</em></strong> It is during those initial conversations that both customer and execution team are presenting their points of view, exploring feasibility, and riffing off each other to envision the very best product possible.</p><blockquote><em>It is during those initial conversations that both customer and execution team are presenting their points of view, exploring feasibility, and riffing off each other to envision the very best product possible</em></blockquote><p>This is natural, exciting, and how we win in the marketplace.</p><h3>“Concept, Meet Execution”</h3><p>Hooray for all that, but the current techniques for converting cool ideas into working Digital technology require a team of people working in close collaboration across lengthy timelines. What this means in practice is that the scope at some point must be locked to create a stable target for that team to develop against. Estimates around work effort, cost, infrastructure, partner integrations, and other project constraints are all based on this stable scope definition, sometimes referred to as a “baseline”.</p><p>Nothing will cause a Developer to sling their laptop across the room faster than the regular occurrence of, “hey, remember that thing we asked you to start building yesterday? Yeah, we changed our minds and now need you to start building this, instead.” That kind of practice is also a great way to run a project that chews through funding yet makes no progress.</p><p>As established above, the creative churn involved in the design process is pretty much unavoidable due to the cone of confusion, and arguably necessary for the creation of awesome products. And yet, at some point we need to call a halt to all that experimentation in order to establish a baseline stable enough for the team to develop against. <em>Successfully contending with this friction is critical to effectively managing this portion of the product lifecycle.</em></p><h3>Vendor Implications</h3><p>It is not uncommon for there to be at least three distinct entities involved in this phase of the project. There is a <strong>customer</strong>, obviously, who is bringing the vision and signing the checks. Often there is also a <strong>design agency</strong> helping guide the customer in articulating their vision into something actionable and enticing to its target market. Much of the time, <strong>technology solution providers</strong> charged with converting those design concepts into working software are involved in these early phases, as well. Whether these are separate groups in the same enterprise or different companies, the danger remains the same.</p><p>This situation becomes particularly fraught when the deadlines and budget for the project have already been established before all this activity takes place. And turns into a pressure cooker if the players involved are vendors engaged through some form of fixed-price contract arrangement.</p><h3>Managing Design Churn</h3><p>This is a “Knowing is half the battle” situation. Just acknowledging and socializing this risk goes a long way to its very mitigation. If everyone is on the same page about the importance of established deadlines, and savvy/compassionate enough to admit that all groups require adequate time to do quality work, just talking about this risk might be adequate to hold it in check.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jeXu0m77mEnfaPou3_JfRQ.jpeg" /></figure><p>More often, however, especially when working with customers lacking past product development experience, talking just isn’t enough. For those cases, a few potential solution strategies:</p><h4>STRATEGY: Find a ‘Follow Your Nose” Product Model</h4><p>The easiest way to manage the high risk of change early in the program is to find a situation where its implications don’t matter. If budget isn’t a factor, there are no looming deadlines, and we can have access to critical enterprise resources for as long as we need them, most of this risk drains right out the bottom. If we spend seven months generating and absorbing design change early in the program, and that is deemed perfectly acceptable, then let’s keep on rocking.</p><p>While this strategy may seem far-fetched, it was the norm during the infancy of the Digital revolution during the late 90’s and early aughts. Plentiful venture capital and a consumer base rabid for Digital products created an environment wherein many teams were free to follow their noses [and hopefully some critical analytics] to create the best products possible. Those were the days. At least until the bubble burst.</p><h4>STRATEGY: Riff Upstream, Then Stop</h4><p>For those in a more terrestrial scenario of budgets and deadlines, there just isn’t the freedom to follow our noses in hopes of finding the best possible solution. In these cases, we need to carefully plan the program such that we hit the target date, at or below allocated budget, with a product potent enough to fulfill its intended mission.</p><p>Depending upon the organizational structures involved, it may be possible to manage risk by pushing these design activities upstream into their own, compartmentalized phase. All the change risk still exists in this case, but is contained in a controlled environment specifically engineered to absorb it. This may be via some internal Design Lab with a healthy budget and strategic mandates, or via a trusted vendor relationship with a time and materials contract structure. <strong>Regardless, the expectation of this strategy is that there is a defined end to the design process </strong>— all that riffing — beyond which change is contained to an absolute minimum. If the customer can’t play by those rules once we all exit the ‘Design Lab’ part of the lifecycle, this strategy is likely to fail.</p><h4>STRATEGY: Cash Contingency</h4><p>Whether in a manner that is transparent to the customer or less-so, cash is held in reserve to cover the cost for the team to absorb the likely change experienced during this phase. When handled by an external vendor in a transparent manner, cash is locked in escrow until approvals are triggered to make it available. If the customer wants to engage in further exploration, they unlock the cash to fund those activities.</p><p>If client/vendor relationships lack the resiliency for this level of transparency, presented estimates are inflated secretly to allow some contingency to ride along with the raw operational cost. We “pad the estimates” so we don’t lose our shirts when the customer demands more change than had been included in our initial planning. This practice begets strategic problems down the road, but when you’re fighting for your life tactics trump strategy every time. Smart customers build strong vendor relationships to avoid situations just like this.</p><h3>STRATEGY: Predefined Rounds</h3><p>Another oft utilized approach is to press the design process into a predefined number of ‘rounds’. This approach accepts that the creative process is iterative and participants need to walk a journey so they can incubate their concepts along the way. We plan for a standard process that begins with brainstorming &gt;&gt; moves into some kind of prototype development &gt;&gt; presents that prototype back to the customer &gt;&gt; and collects their feedback. <strong>&lt;&lt; Those steps represents one round</strong>, and the feedback generated becomes an input into subsequent serialized rounds.</p><p>As project managers, we can calculate the time/cost of these rounds, and plan for a predefined number to occur during the design phase. This approach gives the customer and team plenty of space to explore different ideas, yet keeps everyone aware of how much more time/cash we have allocated for this activity.</p><blockquote><em>This approach gives the customer and team plenty of space to explore different ideas, yet keeps everyone aware of how much more time/cash we have allocated for this activity</em></blockquote><p>With a really strong customer relationship, we can even afford to allow the customer to cut this process off early if they are confident they have the right answer before we have run through all the rounds included in the plan. An early cutoff has the potential to save cost and time that can be utilized later in the build.</p><p><em>A word of warning, however… </em>Another axiom of project management is known as the “Thousand dollar problem”. This concept states that the same problem can have different costs for remediation depending upon where in the product lifecycle it is discovered:</p><ul><li>If discovered during the design phase, when the team is small and tools are lightweight, it might be solved for <strong>$1</strong> of cost</li><li>That same problem, not discovered until the development process is in full swing with a complete team and established expectations, might cost <strong>$10</strong> to solve</li><li>Not discovered until late in the testing phase or on the cusp of launch, that problem might cost <strong>$100</strong> to fully remediate</li><li>Finally, if that same problem sneaks its way through the entire product development process and is not discovered until the product has been deployed in the marketplace, mitigation might cost <strong>$1,000</strong>, instead</li></ul><p>If anything, I think the sample numbers in this axiom are lowballed. In my own experience, the curve is much steeper and allowing a serious issue to pass all the way to Production could be enough to existentially damage the entire company [SEE ALSO, Tylenol, cyanide, 1982]. But the point of the axiom remains the same.</p><blockquote><em>In my own experience, the curve is much steeper and allowing a serious issue to pass all the way to Production could be enough to existentially damage the entire company</em></blockquote><p>This axiom is generally used to scare project managers into eating all their vegetables, and focusing on due diligence throughout the project run. But it applies to this scenario, as well. <em>Don’t be in such a hurry to capture the savings of chopping a design round or two off the project plan that you leave a problem to fester until later in the process when it will be much more expensive to fix.</em></p><p>Applying the concept of rounds to a design phase doesn’t make the high risk of scope change disappear, but it <strong>does</strong> provide us with some architecture to hold it in place, slice it into chunks, and ensure transparency for all involved.</p><p>As discussed previously, team and stakeholders alike must have a <strong>widely shared understanding that once we complete our journey through whatever design process has been chosen, that design must be fundamentally locked for the rest of the build. </strong>Without this essential locking mechanism, the execution team will be unable to generate solution strategies and efficiently construct the product. Waterfall and Agile methodologies manage the work differently, but this fundamental truth still holds.</p><h3>Final Analysis</h3><p>Technology product development is a risky business, wherein we are building something [relatively] new every time. Even with expertise in the platforms involved, bolting those into a new enterprise is always fraught. The risk of scope change during a project like this is ever-present, and the ‘Thousand Dollar Problem’ axiom tells us that its impact becomes worse as the project moves forward in its lifecycle.</p><p><em>But it is during those heady initial design phases of the project that the likelihood of scope change is highest. </em>Indeed, there is adequate evidence to suggest some amount of this back-and-forth is necessary to create strong products that win in the marketplace. Shared understanding and acknowledgment of this risk is critically important for success. Beyond that, creative and resilient process mechanisms can be utilized to hold that risk at bay so the product lifecycle is able to move forward. <strong>We can’t finish the project until we stop starting it.</strong> Techniques like these help us maximize the utility of the design phase without allowing it to strangle the project before it really even gets underway.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0abaf771f2c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Generative AI and Product Knowledge Accrual]]></title>
            <link>https://drewharteveld.medium.com/generative-ai-and-product-knowledge-accrual-ff9290970b2c?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff9290970b2c</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[generative-ai-use-cases]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Fri, 26 Apr 2024 16:18:51 GMT</pubDate>
            <atom:updated>2024-04-26T16:19:39.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/790/0*VeHhCgbcAQ6OywTT" /><figcaption><em>This image generated, ironically, with Google Gemini</em></figcaption></figure><h4>In the race to integrate Generative AI tools into our product development processes, what do we risk losing?</h4><h3>Poking at AI</h3><p>Like everybody else in the product development space, I have been tentatively poking at the portfolio of publicly-available GenAI tools over the past several months. My perspectives have been, at turns:</p><ul><li>Scoffing at all the vaporware</li><li>Impressed by the insights and data analysis capabilities</li><li>Amused by the silliness of some of the output</li><li>Excited about the potential opportunities for application in our work</li><li>In awe at what seems to be just around the bend</li><li>Concern about the risks to my own employment, and the employment of many of the other humans I know</li><li>Genuine fear about the potential dangers of these tools to our broader culture</li></ul><p><em>Basically, the same gyrations represented in every general interest article and presentation about this technology in the media, today.</em></p><h3>Tentatively Hands-On</h3><p>A prominent client is currently experimenting enthusiastically with the application of these tools against basic business administration tasks. I have been really impressed at not just the breadth of information they can gather, but also the depth of detail they can convey.</p><p>By way of example, we are now using Microsoft Copilot for transcription and analysis of all departmental meetings. The debriefing notes generated by the tool are impressive.</p><p>As a long-time PM, I have generated scores of meeting notes during my career. It is a necessary task, but low-value as the information presented is locked in the context of the meeting instead of the context of the larger project.</p><p>As such, I always end up generating the meeting notes first, and then nearly duplicating that effort as I migrate key details from the meeting into other documentation that represents the holistic project scope. Cutting that initial ‘meeting notes’ step out is a huge benefit for a person like me. And given savvy prompt engineering, I’m betting most of the current GenAI tools could handle the second task effectively, as well.</p><h3>The Value of Specs</h3><p>Which brings me to the core subject of this post: the generation of knowledge. Much of the work we do in product development consists to experimentation, prototyping, and analysis related to the description of an envisioned product [or enhancement] that does not yet exist. For brevity, I’ll just lump all of this under the moniker “specification documentation”, or simply, “specs”.</p><p>The leaders who envision products and fund their development have long understood that the value of specs lies in:</p><ul><li>Describing the envisioned product</li><li>Establishing shared terminology, syntax, and context for these product descriptions</li><li>Representing a model from which specialists can derive a solution strategy for construction</li><li>Serving as a single source of truth when adjudicating whether or not the resulting product has been properly constructed</li></ul><p>Whether you operate in a mostly Waterfall [BRD/FSD/TSD] or Agile [epics/stories] mode, the importance of these specs cannot be overstated. (Note that even when the specs are truly pristine, we will still struggle around their collision with reality while construction is underway. Because product development is really hard. SEE ALSO: <a href="https://drewharteveld.medium.com/adequately-groomed-db9a8f28bb1b?trk=article-ssr-frontend-pulse_little-text-block">https://drewharteveld.medium.com/adequately-groomed-db9a8f28bb1b</a> )</p><h3>The (Other) Value of Specs</h3><p>Like a painting in the pointillist style, from across the room it looks beautiful, logical, and obvious. Those individual blobs of color mix in the atmosphere between the canvas and the viewer to create a clearly understandable and pleasing narrative. Similarly, when described at a high level, most product concepts also seem beautiful and obvious.</p><p>Unfortunately, we can’t reliably build something that has been described at only a high level. To construct successfully, we must describe the envisioned product — via specs — at the most granular level. To extend the pointillism analogy, we must drag the user from across the room until their nose is right on top of the canvas. From this vantage point, the painting is a riot of color devoid of context. That beauty and logic has been replaced with tedious minutiae — and a likely headache.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mIXmViaoXONa7M8dE03MNQ.jpeg" /><figcaption>Image from Robert Shirk at: <a href="http://www.robertshirk.com/blog/pointillism/My_Journey_to_Three_Dimensional_Kinetic_Pointillism.html">http://www.robertshirk.com/blog/pointillism/My_Journey_to_Three_Dimensional_Kinetic_Pointillism.html</a></figcaption></figure><p>This is the hard work of product development, shifting between ‘across the room’, where the product has pleasing context, and ‘nose on the canvas’ where the dirty details must be worked out. All of which must be documented in the specs.</p><blockquote><em>This is the hard work of product development, shifting between ‘across the room’, where the product has pleasing context, and ‘nose on the canvas’ where the dirty details must be worked out. All of which must be documented in the specs</em></blockquote><p>It is through this hard work that the product development team, especially those members tasked with authoring the specs, <strong>gain understanding about the product</strong>. For this special case, I will leapfrog beyond the word “understanding” and utilize the term “grok,” coined from Robert Heinlein’s 1961 novel Stranger in a Strange Land. Per Merriam Webster, to “grok” something is “to understand profoundly and intuitively.”</p><p>This is truly the perfect term, because the knowledge gained by the product development team while engaged in the hard work of crawling through the documentation of specs is certainly ‘profound and intuitive’. The difference between understanding the pointillist painting from across the room and understanding it on a dot-by-dot basis is all the difference in the world.</p><p>Further, this level of expertise becomes pivotal as the product build progresses, with those who have grokked the specs not only providing on-demand reference to that content, but also interpreting incoming questions with the benefit of the full body of context that knowledge provides.</p><p>This is really how the product development process works at the ground level on a daily basis.</p><h3>Grokking for the Future</h3><p>Extending this narrative just one step further, this grokked knowledge pays dividends not only within individual product development builds, but across the entire product lifecycle. Those who grok the product are best positioned to hydrate that knowledge with information about enterprise strategy and the <em>competitive marketplace</em> in order to chart the product’s roadmap into the future [SEE ALSO: Product Managers].</p><p>If we’ve learned anything about enterprise valuation over the past 50 years of market analysis it is that the marketplace value of a company is less about the impact of products and services deployed in the past, and even those being deployed to today, than it is about the impact of the products <em>expected to be</em> deployed in the future. Nobody buys Apple stock today because of the invention of the iPod in 2001, and few are even focused on the current uptake of iPhone 15’s last quarter. Most are are truly interested in what whizbang gizmo Apple will introduce next year, thus further jacking share value beyond what they themselves paid today.</p><p>As we have established, the best positioning to maximize future product impact is to grok every feature included in its current state. You have to understand where your product is today in order to effectively enhance it into tomorrow.</p><h3>What Are We At Risk of Losing?</h3><p>Here is where we wrap the story back to GenAI. We’ve all seen the power of this technology to interpret instructions against the content of of the entire Internet — plus proprietary content that may be provided in a prompt — to generate impressive output. It is no small leap to imagine utilizing these tools to generate specs in support of product development. <em>I’m quite sure that some companies are doing so now to the realization of dramatic efficiency gains.</em></p><p>My concern is that since no human is putting in the sweat equity to generate those specs, no human is earning the level of grokked knowledge that can only come through that activity. This means, potentially, that they are generating lightning fast specs today, but not building the underlying knowledge base to effectively enhance their products tomorrow. These tools might allow us to advance very quickly, but how long until we don’t understand our products adequately to know where to take them in the future?</p><blockquote><em>My concern is that since no human is putting in the sweat equity to generate those specs, no human is earning the level of grokked knowledge that can only come through that activity</em></blockquote><h3>Doomsday Scenario</h3><p>One potential answer is — I guess — “we don’t need to know”. AI knows. It did the work, it has that grokked knowledge [plus all the information on the whole Internet], so AI will tell us where best to go in the future.</p><p>And this is the implication that most scares me. Once we surrender the strategic parts of the product development process to the AI, we open ourselves to all sorts of prejudices baked into that black box that we cannot discern. By its very nature, the output of AI can’t be pragmatically validated by existing quality assurance techniques. How are you going to parallel longhand a logic cascade that takes into account all the information on the planet? <strong>Can’t do it.</strong> Once we cede this function to AI our ability to recognize intrinsically unacceptable output, and control it, will begin to erode. Perhaps swiftly.</p><h3>Practical Concerns for Product Development</h3><p>That’s a whole lot of doom and gloom, and well beyond the scope of risk to be found in the kinds of digital product development most of us engage in on a regular basis. And I’m no ontologist — so not the right guy to make these arguments.</p><p>For many years I have been aware of the obvious value provided by specifications, <em>as well as the quieter yet deeper knowledge created through their generation</em>. It’s not the kind of thing we talk about often with our clients, as they start to worry that we are treating their critical product development build as more of a science project than a commercial endeavor. But at the level of the team, we deeply understand the importance of the knowledge created, as well as the pivotal role played in the project by those who have grokked it.</p><p>A quick, final vignette: I was recently having breakfast with a colleague who runs the PMO for a mid-size technology provider. One of their PMs had recently asked to engage in some more strategic work. In close proximity, this leader receiving a request to generate a go-to-market plan for a product with an impending launch. Attempting to tie demand to the supply, my contact provided the PM with relevant inputs and asked her to take a crack at drafting the plan.</p><p>A scant two hours later, the PM delivered a passable marketing plan that smelled distinctly of GenAI. My contact thanked the PM and dropped the report into the garbage. The point of that exercise wasn’t the plan itself, but the knowledge to be gained by the PM through the act of its generation. And the PMO lead needed a PM with that knowledge fully grokked in order to successfully execute the plan in reality. The application of GenAI in this case completely missed the point.</p><h3>Walking the Path</h3><p>My concern is that in a world wherein no human is forced to do the hard work of research, analysis, and description to generate product development specs, no human will be grokking the knowledge about those products that comes only from walking that path.</p><p>I certainly don’t want to stand in the way of progress in the adoption of these powerful tools into our workflows. Nor do I want to miss out on the speed and efficiency to be gained by their embrace. But I also don’t want us to lose that skillset without careful consideration about the larger implications, today and into the future.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/generative-ai-product-knowledge-accrual-drew-harteveld-itnmf"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff9290970b2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Platform vs. Program Expertise?]]></title>
            <link>https://drewharteveld.medium.com/platform-vs-program-expertise-6786e0773595?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6786e0773595</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[digital-operations]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Wed, 28 Feb 2024 21:16:47 GMT</pubDate>
            <atom:updated>2024-02-28T23:47:53.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z2Mlr85KpOCuCfNH" /></figure><h4>In sourcing operational leadership for enterprise platform integrations, focus on program expertise over platform familiarity</h4><p>This one is for the Customers — those who are on the buying/accountability side of large, complex, programs. We’re talking about programs that involve the installation of mission-critical operational platforms into enterprise operations. These are platforms like general ledgers, ERPs, personalization engines, data warehouses/lakes/visualization tools, portfolio planning tools, asset management systems, and HR/Ops platforms.</p><p>Among the many, many important decisions to be made in instantiating those programs is how to handle their executive-level management. In bootstrapping programs of this magnitude, sometimes amid all the other details of platform selection, system integration partner interviews, investment forecasting, and integrated planning, the critical element of program management architecture gets lost. It seems such a small thing — simply an administrative shadow of all the really important work to be done — its easy to lose adequate control of along the way.</p><p>Here’s how that usually goes:</p><ol><li>Customer needs a large platform integrated into their highly complex operational environment</li><li>A platform is chosen</li><li>The platform vendor has its own professional services team, or a list of partners to provide system integration</li><li>A System Integrator (SI) is chosen</li><li>In its SOW, the SI includes a line item for “Program Management”</li><li>The customer is thrilled, thinking, “I don’t have any people to do this, anyway,” and, “They’ve got to be good at this since they do it all the time…”</li></ol><p>Sometimes, this scenario works okay. Most of the time, less so. There are two key problems with this approach:</p><p>FIRST, <strong>Program management should be a function of the customer.</strong> They are the ones receiving the assets of the build, and thus ultimately responsible for the quality of deliverables. This is not a function that should be outsourced — particularly not to the vendor doing the work.</p><p>SECOND, <strong>Expertise with the chosen platform and expertise running complex programs are not the same thing.</strong> While it is theoretically possible that the SI has a resource who adequately wields both, experience suggests that those resources are as rare as rainbow-colored ponies.</p><p>Each of these problems/opportunities is addressed in the sections below.</p><h3>Program Management as a Customer Function</h3><p>The largest and most dynamic enterprises may have their own team of on-staff program managers with the expertise and gravitas necessary to run large, complex, mission-critical initiatives. For everyone else, these initiatives only roll around every few years and it just doesn’t make sense to warehouse this talent.</p><p>Due to this reality, when the head of that professional services team at the vendor, or managing partner at the SI, offers to cover the program management function on their own team, most customers jump at the opportunity. Ultimately though, this strategy falls short.</p><p>Due to the scope and criticality of responsibilities shouldered by this program manager, as well as the need to leverage trusted relationships when challenges arise, it is best for this role to be played by a resource inside the customer org. Because a large portion of this job consists of coordinating and policing the everyday activities of the program, it can seem a fishy proposition for that SI-supplied program manager to be effectively policing a group of colleagues with whom they share a margin imperative outside of the program.</p><blockquote><em>Due to the scope and criticality of responsibilities shouldered by this program manager, as well as the need to leverage trusted relationships when challenges arise, it is best for this role to be played by a resource inside the customer org</em></blockquote><p>As with so much in this business, customer comfort when things are going well can feel very different than when the program gets hung-up in challenging terrain. At the time of SOW execution the System Integrator’s A-team is in the room and everyone is all smiles. A few months later, when the idiosyncrasies of the scope become apparent and the customer is comparing an obscene burn rate against a conference room full of twenty-something consultants, relations can become less cordial.</p><p>In that moment the customer needs its own program professional, fully-embedded with the team, with trusted expertise and clear loyalties, to plot a course through the thicket.</p><p><strong>Having strong program management expertise on the vendor side is always a benefit.</strong> In the best case scenario, that is matched by a customer-side counterpart through whom a senior-to-senior planning dynamic can be established.</p><h3>Program vs. Platform Expertise</h3><p><em>Allow me to clearly state up front that this is a choice we really shouldn’t have to make. </em>Logically speaking, we should be able to find resources who are equally strong in their expertise with the chosen platform as they are with the discipline of program management for large and complex integrations. My own experience from the field, however, suggests these folks are few and far between.</p><p>For the most prevalent platforms, like Oracle Financials, I have worked with some leaders from the very largest System Integrators that wielded necessary strength in both disciplines. But those ninjas are the exception rather than the rule. And once you wade outside of the very most popular platforms, and/or the largest and most expensive System Integrators, the population plummets.</p><p>Perhaps it is a simple function of personality… Maybe the psychological nature of those who yearn for deep platform expertise is incongruous with the flexibility, sensitivity, and process focus that engender strong programs. I’m personally too close to this debate to be able to describe the WHY with much clarity. All I know is that in the real marketplace these people are not as widely available as we would like or expect.</p><h4>“The Tech Works Just Fine”</h4><p>Further, the challenges that knock us down in these programs are rarely rooted in the tech, itself. <em>Generally speaking, the platforms being chosen for mission-critical business functions at large enterprises are well vetted across many years of real-life performance across a broad portfolio of customers. </em>Unless you sign up to beta test a brand new AI-based ERP, you should feel confident that the tech will work as expected.</p><p>The most challenging terrain the program must traverse is that soft tissue zone BETWEEN the platform and the operational organization into which it must be integrated. For success in this region, you need a program manager with the expertise to successfully:</p><ul><li>Establish ground rules, put on the striped shirt, and help officiate the game of everyday program activity</li><li>Manage the dynamic breadth and depth of program scope</li><li>Establish and support strong information exchange between the business SMEs and the technologists charged with translating their needs into platform configurations/customizations</li><li>Maintain program transparency to stakeholders and enterprise leaders, alike</li><li>Manage the customer-side political landscape in order to escalate issues and find resolutions</li><li>Establish ‘single source of truth’ assets to unify the team and contextualize its work</li><li>Establish and enforce clear jurisdictional boundaries across program resources/groups</li><li>Maximize collaboration with partner groups, both inside and outside of the specific customer’s org [incl. PMO, Audit, Corporate Finance, Corporate IT]</li><li>Create balance and accountability across multiple vendor partners, often whom are competitors in the larger marketplace</li><li>Deploy carrot and stick as necessary to keep the whole assembly moving in the right direction at a reasonable pace</li></ul><p><strong>That being the case, if forced to choose between platform expertise and program prowess, you’d rather have the latter.</strong></p><p>That’s not to say you don’t need technical expertise in your build. Of course you do! But in the vast majority of cases that is already supplied through the platform vendor, and/or their professional services team, and/or the technical resources on the SI team. We already have solid coverage around technical expertise. What we need is a senior-level program resource with the competency, sensitivity, and clout to orchestrate integration of that tech into the very human operational architecture of the customer organization.</p><h3>Hop In, Let’s Go</h3><p>Conventional wisdom suggests that the resource you need to lead your complex platform integration would be the resource with the most expertise in the platform. My own experience suggests otherwise.</p><blockquote><em>Conventional wisdom suggests that the resource you need to lead your complex platform integration would be the resource with the most expertise in the platform</em></blockquote><p>Of course we need platform expertise, and that comes through the platform vendor and whatever strategy they market to ensure what they sell gets successfully installed. But that only represents the first few steps on an arduous integration journey.</p><p>To maximize your chances at a successful arrival, you need a program manager with expertise in the dynamics of large programs across complex enterprises. And you’d really like that resource to <strong>not</strong> work for your chosen System Integrator. If the SI has that function on offer, great. But you need your own heavy to stand toe-to-toe and ensure your interests, as the customer, remain front-and-center.</p><p>If you don’t carry resources with that level of program management expertise on your team, then engage an independent to play this role from your side. While they will have to hustle to climb the learning curve of your enterprise and establish trust with your leaders, at least you’ll know they have the planning competency to effectively lead your program, and their loyalties sit squarely with you.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/platform-vs-program-expertise-drew-harteveld-7bpef"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6786e0773595" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Capacity Planning on the Cheap]]></title>
            <link>https://drewharteveld.medium.com/capacity-planning-on-the-cheap-5b90ff4d69ed?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b90ff4d69ed</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[operations-management]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Thu, 15 Feb 2024 19:41:52 GMT</pubDate>
            <atom:updated>2024-02-15T19:41:52.508Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*dE-dP8_c9oR5KV1Cd6k9BQ.jpeg" /><figcaption>“I think we can fit another one in. No?”</figcaption></figure><h3>Master operational capacity to scale your product development throughput</h3><p>My business supports a diverse portfolio of clients from the Tech, Media, Manufacturing, and Pharmaceutical industries. The operational realities across these industries can differ substantially based on maturity, regulatory burden, and culture. Invariably, however, <em>every product development org I walk into shares at least one challenge in common: </em><strong><em>Capacity Planning at the Executive Roadmap level.</em></strong></p><h3>Executive Roadmap Capacity Planning</h3><p>Before we dive into the HOW on this solution strategy, let’s get together on the WHAT. When I say “Executive Roadmap Capacity Planning” I’m talking about planning that occurs below the level of enterprise strategy, but above the detailed execution through which the products actually come to life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qhePMJHMvxOfxGJFuo6Tvw.png" /></figure><p>This is a critical juncture, at which planning turns the corner from <strong>aspirational</strong> to <strong>practical</strong>. Or at least it should. In my experience the conveyance of the Executive Roadmap down to the organization tasked with its execution is rarely endowed with adequate practical capacity analysis. The result is a C-suite constantly disappointed with the output of their product development team, and team members forever crushed by impossible expectations from the C-suite.</p><blockquote><em>The result is a C-suite constantly disappointed with the output of their product development team, and team members forever crushed by impossible expectations from the C-suite</em></blockquote><p>What follows is a basic methodology I have customized to help fill this gap.</p><p><em>IMPORTANT NOTE: Offerings from Planisware, Oracle, and other enterprise vendors are specifically engineered to address these needs — plus many others — at scale. If you have access to those tools, consider yourself lucky and get cracking.</em></p><p><em>However, for those of us who do not have those tools available, </em><strong><em>or who choose not to integrate planning data to the depth those systems demand in order to answer these questions</em></strong><em>, alternatives do exist.</em></p><p><em>For this example, I will be using Microsoft Project. This tool has been chosen for its powerful Resource Leveling functionality, and because it is easy to bastardize to get this job done. If you hold a PMP certification and recall the “forward pass” and “backward pass” math from your trusty PMBOK, you know Microsoft didn’t invent these concepts. They did, however, package them in a way that easily and inexpensively meets our needs for for this exercise.</em></p><p><em>I recognize that MSProject isn’t considered ‘modern’ in an Agile world. If you have walked away from this tool for that reason alone, you are missing out on a ton of powerful functionality. I’ve been running Agile projects since 2007 and freely pull from the Waterfall toolbox all the time to help my teams get where they need to go. You be you.</em></p><h3>Critical Questions to Answer</h3><p>This Capacity Planning regime creates a medium-high level model intended to answer the following questions in a transparent and visual manner:</p><ol><li>What is the <strong>list of products</strong>, provided in stack-ranked prioritized order, the enterprise aspires to construct?</li><li>Who are the <strong>teams involved</strong> in construction of those products, including coarse volumes of capacity?</li><li>What is the <strong>expected duration</strong> for each product build?</li><li>What is the breadth and depth of <strong>resource engagement</strong> expected to be necessary to complete each product? How far can I stretch my workforce across this project portfolio?</li><li>Based on a comparison between available resource capacity, resource requirements of each product, and the interplay of all products in the portfolio against each other, <strong>when can the execution of each product build be expected to occur?</strong></li></ol><h3>Solution Components</h3><p>The Capacity Planning regime described here requires five critical components:</p><ol><li>A <strong>backlog of desired products</strong>, provided in stack-rank, prioritized order</li><li>Granularity-appropriate, high-level inputs about the <strong>capacity of each team</strong> to complete simultaneous work</li><li>A <strong>Capacity Planning model</strong>, in this case utilizing MSProject, through which this information can be brought together for review, analysis and experimentation</li><li>A <strong>team of leaders</strong> empowered with the knowledge and authority to speak definitively about expected duration and resource engagement to complete each product</li><li>A <strong>regularly recurring cadence</strong> through which the Capacity Planning team gathers to review/update the existing model, a well as providing necessary inputs to absorb new incoming demand into that model</li></ol><h3>Bootstrapping Capacity Planning</h3><p>This section describes the basic steps in my own Capacity Planning solution. It assumes a cold start with no prior information available. Once the team has moved through this cold start, maintenance of these materials becomes much more streamlined.</p><p><em>As a medium-high level model, this Capacity Planning regime does not track activity at the granularity of individual resources, tasks or tickets.</em> Instead, each product build is represented by a single summary row on the Gantt chart, displaying target Start Date, Duration, and End Date</p><h4>STEP 1: Defining Teams</h4><p>A logical first step is to define all teams involved in construction of any/every product in the backlog.</p><p>Once the teams have been defined, high-level capacity must be provided for each. There are several ways in which capacity can be represented. Past experience with this model suggests that the most flexible is as a raw count of resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*irkhowCaABaISon5dJQw8g.png" /></figure><p><em>Note in the screenshot above, in red, the rough designation for the number of resources available on each team. This is critical for the calculations to come.</em></p><p>This approach, and the target granularity of this model, does not account for the differing strengths, skillsets, or specific expertise of those human resources. In order to create and maintain a model that operates at the desired level of detail, and provides information actionable to its chosen audience, this information is considered below this model’s operating granularity. We’re not thinking at the level of individual resources here, we’re focused on the capacity of teams.</p><h4>STEP 2: Stack-Rank Prioritized Backlog</h4><p>As discussed above, this model demands that prioritization be represented via a single stack-ranked list of desired products. Stack-ranking looks like an easy exercise until you’re the guy charged with juggling all those competing needs to get it done. While generating that list may be difficult, it is essential in support of this planning model. As a bonus, it also represents excellent business hygiene</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LouLW5uXZD2blT0VID9HeA.png" /></figure><h4>STEP 3: Product Durations, Dependencies, and Effort Estimates</h4><p>Arguably the most critical part of the process, the Capacity Planning team must, <em>based upon whatever information is available</em>, provide a high-level estimate of total duration for the product build. This is also a good time to model the dependency relationships between the products, themselves, as well as any internal or external constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PEVgIERR-ujYpB9-pRwB_Q.png" /></figure><p>Once this has been provided, the Capacity Planning group must generate high-level estimates for the engagement of resources across teams throughout the life of that build. For example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*03Wbg2p_n16IsqF6qeEGGA.png" /></figure><p><em>Note in the screenshot above, in red, the rough allocation of resources from across teams to this product build. This is critical for the calculations to come.</em></p><h4>STEP 4: Resource Leveling</h4><p>The magic happens when MSProject runs the arithmetic to compare resource demand, identified for each product, against available resource capacity. Based on this analysis, MSProject <strong>automatically repositions projects across time based on availability of necessary resources.</strong></p><p><em>What this means in practice is that, based upon current prioritization, that product you had hoped for at end-April may not actually be available until the last week in May. </em>The benefit of this approach, as coarse as it may be, is that it allows leadership to understand and contend with these scheduling constraints right away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q1rZj43r5pQTgEUKGEWRqQ.png" /></figure><p><em>Note the red arrows in the screenshot above, representing specific product builds that are pushed out from original timeslots based on the resource leveling arithmetic</em></p><p><strong>THIS IS THE PAYOFF. That resource leveled Gantt listing each initiative on the roadmap, calibrated to represent reasonable start and end dates based on team capacity, is the intelligence all of this effort begets.</strong></p><p>Congratulations. Now the hard work begins.</p><h3>“Let’s Make A Deal…”</h3><p>When this Capacity Planning analysis spits out a narrative that is unacceptable to leadership, we have a few switches to throw in hopes of finding a more favorable outcome.</p><h4>Reprioritize Products in the Backlog</h4><p>The Capacity Planning model is configured to apportion resourcing against the products in the backlog in a top-to-bottom fashion. That means products at the top of the list will gobble-up the resources they need, leaving fewer available for those products lower on the list. When that scenario occurs, the model automatically delays start of each product build until all necessary resources are available.</p><p>The easiest way to adjust the model to create an earlier start date for a product that has been bumped by the resource leveling arithmetic is to move that product higher in the backlog. Of course, the stack-ranked prioritization methodology demands that for one product to move up in the list, another must move down. There can be only one product at position #1, one at position #2, one at position #3…</p><p>This practice represents not only a requirement of the Capacity Planning regime, but strong business planning hygiene. The fact that it can be so damned difficult to get a leadership team to coalesce around a single prioritized order isn’t a defect of this process, its a feature. Better the leaders thrashing through this labyrinth of competing needs than leaving the line resources to try to figure it out on their own.</p><blockquote><em>The fact that it can be so damned difficult to get a leadership team to coalesce around a single prioritized model isn’t a defect of this process, its a feature</em></blockquote><h4>Adjust Scope of Individual Products</h4><p>The duration values associated with the products in the model are based on the perceived size and complexity of each. In order to shorten the duration of a specific product build, it may be possible to adjust the size, number, or complexity of the features therein.</p><p>Thus, a product build that had been previously scoped to include twelve features and estimated at 8 weeks duration may be feasible at 4 weeks duration if only half of those features are included.</p><p>A useful technique is to break a larger effort into sub-products, each represented at its own position on the backlog and its own bar on the Gantt chart. Each of these sub-Products can be scheduled based upon the deadlines of its internal features, allowing space for other products to be addressed in between.</p><h4>Examine Dependencies and Constraints</h4><p>Resource availability is not the only factor in determining when product executions will occur. Two others are dependencies and constraints, both of which can be internal or external in nature.</p><p><strong>Dependencies: </strong>There may be a relationship between two products in the backlog through which Product A must be completed before Product B can be initiated. There may also be scenarios wherein multiple product builds must begin at the same time, meaning none can initiate until all are ready.</p><p><strong>Constraints: </strong>Constraints represent schedule impacts that are not dependent in nature. For example, there may be a moratorium against work on a platform due to a critical update, or as a risk mitigation over a holiday break. A platform or technical tool may become unavailable as of a certain date due to a contractual limitation. A product may be targeted for release to coincide with some event in the physical world, such as a trade show.</p><p>Examining, analyzing, and adjusting dependencies and constraints can be a useful way to tweak the model in order to gain more positive outcomes.</p><h4>Engage more Resourcing</h4><p>In _some_ cases, it may be possible to increase team velocity by engaging additional resources. Based upon the granularity of representation of different teams within the Resource Sheet, the model can provide useful insight into which teams are experiencing the greatest contention within any time period. Armed with that information, it may be possible to increase resourcing in a strategic fashion in order to gain the most speed-per dollar.</p><p>CAVEAT EMPTOR — as we all know, the engagement of resourcing, either FTE or consultant, is not a seamless process. Searching for, engaging, and training new resources comes with its own opportunity costs, none of which are particularly well represented in this project-focused model.</p><p>Given adequate lead time and the right circumstances, however, this model can help the enterprise to recognize resource bandwidth shortfalls with adequate lead time to address them in a calm, diligent fashion.</p><h4>Truth First, Truth Always</h4><p>It goes without saying that where all these mitigation strategies are concerned, <strong>alignment with truth</strong> is critical. The model only remains useful as long as its attributes are true representations of the feasibility, behavior, and engagement of resources in the real world.</p><p>It is easy — and dangerous — to twist the model into a narrative that is pleasing to leadership yet infeasible in reality.</p><h3>Limitations of the Model</h3><p>There is much to love about the Capacity Planning model presented here, but it isn’t perfect. A few known limitations are presented below. Most of these are not unique to the specific modeling strategy being presented here, and are a byproduct of many modeling regimes.</p><h4>Coarse (for speed and flexibility)</h4><p>In order to remain lightweight, flexible, and easily understood, this model exists at a relatively coarse level of detail. More granular detail is possible, but makes the model more clunky and difficult to interpret. The level of granularity described herein represents a ‘sweet spot’ between accuracy of detail and ease of use. When you apply this model in your own shop, you’ll find the sweet spot that meets your own needs.</p><h4>All the Resources All the Time</h4><p>One example of the limitation of this coarseness is in the allocation of resourcing to the individual products in the model: <strong>all resources are represented as involved in the product build during its entire lifecycle</strong>. This model provides no notion of resources rolling on/off a product build across time.</p><p>From an Agile perspective this may be considered a benefit instead of a drawback, as Agile espouses engagement of the complete multidisciplinary team throughout the entire product build lifecycle. However, not every enterprise operates that way. When resourcing gets tight, this limitation can have outsized importance.</p><p>As above, you can further complexify the model to meet this need. But you do so at the cost of speed, flexibility, and ‘at a glance’ interpretation. For me, this ‘all resources all the time’ structure works just fine for the Executive Roadmap level, and any associated discrepancies can be managed via the more detailed planning processes lower on the hierarchy.</p><h4>Garbage In/ Garbage Out</h4><p>Any model is only as good as its inputs. In order to maximize the value of the Capacity Planning regime described here, all involved stakeholders must be enthusiastically engaged and willing to provide best-possible estimates around duration and resource allocation based on limited information.</p><p>Leaders who are unwilling or intellectually unable to provide these services will erode the efficacy of the analysis. The utility and speed of the model break down when leaders fall into the “I don’t know enough to provide those initial estimates” trap. Providing services like these is simply the right and responsibility of modern technology leadership. We’re not etching anything in stone, here. We’re trying to gain directional guidance.</p><h4>Shatter Under Pressure</h4><p>This regime represents a three-dimensional model of an actual scenario with hundreds of variables. That doesn’t make the model useless, it just means we need to understand the level at which it operates most effectively.</p><p>Playing the “What about this detail? What about that detail?” game with this model will cause it to quickly shatter. The model is intended to provide a limited representation of reality, not encompass all of reality’s variables. A clear understanding of this model’s target granularity and the role it is intended to play in enterprise planning is critical for its effective implementation.</p><p><em>In return for that investment, we gain mastery over our Executive Roadmap and ensure that all downstream activity is informed by a well-calibrated understanding of actual team bandwidth.</em></p><h4>Manual Engagement</h4><p>Engagement of the Capacity Planning regime as described here really requires a ‘czar’ resource who owns the MSProject files, quarterbacks collaboration, and manages socialization of associated planning/change across the enterprise. This model can’t run on autopilot. It requires thoughtful and creative engagement by busy leaders in order to remain accurate and useful over time.</p><h3>The Fast &amp; The Flexible</h3><p><strong>Why bother with all this effort?</strong> To ensure that, from the moment we depart the aspirational brainstorming portion of the planning process, our expectations are calibrated to match our means. Why waste valuable leadership energy pining for a rate of delivery that is infeasible in our current situation? Instead, let’s challenge our leaders to make the difficult prioritization decisions necessary for the team to to focus on the products with the greatest benefit to our enterprise.</p><blockquote><em>Why waste valuable leadership energy pining for a rate of delivery that is infeasible in our current situation?</em></blockquote><p><em>We already have strong tools and processes for planning at the portfolio and sprint levels. But if we don’t force leadership to calibrate its expectations at the level of its Executive Roadmap, we’re already putting our people in the pressure cooker by the time those parts of the planning hierarchy roll around.</em></p><p>This methodology does not purport to solve all planning problems or provide automated traceability from the strategic level down to tickets and resources. If that is what you need, go buy Planisware.</p><p>Instead, this homespun approach is focused is on being cheap and fast to implement, while providing a flexible mechanism to model different scenarios so leadership can find the best path.</p><p>Whether you utilize my own hacked-together solution presented here or some spreadsheet, post-it note, and abacus-based monstrosity of your own design isn’t the point. The point is to put some capacity-aware mechanism in place way up at the top of the planning hierarchy where leadership assumptions and expectations are born.</p><p>It may seem counterintuitive that the best way to scale your team is by establishing a quantitatively-derived ceiling for the amount of work the team can metabolize. <strong>But that is the truth</strong>. If you want to hold on to the best resources and provide them with the breathing room they need to build with quality and creativity, throttling the demand from leadership to match actual team bandwidth is essential.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/capacity-planning-cheap-drew-harteveld-ghb1e"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b90ff4d69ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Planning at the Inception]]></title>
            <link>https://drewharteveld.medium.com/planning-at-the-inception-7963e4bd0d12?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7963e4bd0d12</guid>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[operations]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Mon, 05 Feb 2024 22:38:06 GMT</pubDate>
            <atom:updated>2024-02-06T11:47:13.708Z</atom:updated>
            <content:encoded><![CDATA[<h4>Start your program off on the right foot, then run like hell</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LcdvmjVTPV_Ij0vH" /><figcaption>Copyright Warner Brothers Pictures</figcaption></figure><p>Let’s take a few minutes to think about planning at the very inception of a new program. We’re not talking about after the kickoff or once all resources have been engaged. We’re talking about during those initial hours when a business reality has forced senior leaders to contend with the fact that a large effort may be necessary to plug a hole in the current situation, and they are trying to sketch the outlines of that effort.</p><p>Often this scenario looks like just a handful of those leaders in front of a whiteboard, likely after-hours, perhaps with a half-eaten pizza on the table. With any luck, there’s also a bottle of scotch that one of them learned to keep in a bottom drawer for situations just like this one. Diligence during this initial brainstorming session will plant seeds that may define the success or failure of the program months down the line.</p><p><em>DISCLAIMER: In both this space and my business as a whole I try not to be overly prescriptive. I have learned from experience that the best operational solutions are organic and built-for-purpose. Just because I’m not familiar with your ways of working doesn’t make them wrong. I show up to learn first and teach second.</em></p><blockquote><em>I show up to learn first and teach second</em></blockquote><p><strong>However, in this critical phase of program inception, there really is a RIGHT WAY to move the conversation forward</strong>. For my own shorthand, I utilize the progression: WHAT &gt;&gt; HOW &gt;&gt; WHO &gt;&gt; WHEN .</p><p>The order here is just as important as the underlying concepts. I’ll describe each below, and then we can talk about interplay.</p><h3>1. The WHAT</h3><p>Without question, in 98% of cases the only right place to start is by defining the target state for the product or service being created. Beware the trap of contextual framework in defining this scope. Something you consider to be an obvious inclusion might be nonexistent in another person’s context. For this reason, be as specific as you can at this high level. If you want the Content Browse feature to be driven by a carefully maintained taxonomy, add that to the list. This isn’t a formal specification, but we definitely want to clearly include the critical attributes of each part of the envisioned scope.</p><h3>2. The HOW</h3><p>Now that the WHAT of the scope has been clearly defined, at a high level, we are in a position to sketch out the HOW. What talent, equipment, technology, knowledge, licenses, and partnerships will work together in order to realize that WHAT? What rules of engagement will be established to keep this effort on the rails and moving forward? If there are multiple approaches available, how will we choose and how should that adjudication activity be included in our planning process? The WHAT is theoretical. The HOW begins to crank that theory down into the practical realm.</p><h3>3. The WHO</h3><p>The next step is to determine what roles, resources, and specific expertise will be required to make that HOW a reality. Begin to sketch the interplay between different individuals or groups that will be required to bring this idea to life. Try your best not to jump ahead into the scheduling idiosyncrasies of different resources, equipment, or environmental factors. For the moment, keep staffing high-level and theoretical, “Three concurrent teams under a program governance structure, plus UX and Infra shared service engagement throughout…” That’s the level of detail we’re looking for at this juncture.</p><h3>4. The WHEN</h3><p>Only now that you have clearly defined the WHAT, HOW, and WHO, are you in a position to begin blocking out a high-level schedule. There are a bunch of constraints to consider during this part of the thought process:</p><ul><li>Business Cycle</li><li>Availability of internal/external resources</li><li>Impacts of this effort on other initiatives underway in parallel</li><li>Outputs from initiatives necessary as inputs to this effort</li><li>Availability of specialized equipment</li><li>Environmental factors [EX/ we can’t pour the foundation during the monsoon…]</li><li>Aspirational target delivery date</li></ul><p>It may take a few tries, but these will eventually snap-together into some kind of cohesive puzzle that shows your HOW rolling out across time.</p><h3>Attribute Interplay</h3><p>As soon as these four attributes have been defined, the negotiations begin:</p><blockquote>“The deadline won’t allow us to address all the scope desired. We’ll need to cut our WHAT down to just these essential elements…”</blockquote><blockquote>“While we have this HOW and WHO engaged, there are a few items of technical debt that it makes sense for us to knock off as part of the WHAT…”</blockquote><blockquote>“Dr. Taylor has critical expertise in this area, but is not available until next year. Since we can’t wait that long we will have to utilize a less-expert WHO and add another 8 weeks to the WHEN to allow for some learning along the way…”</blockquote><blockquote>“We all agree that this WHAT is important, but in light of other high-priority initiatives there won’t be an open lane of WHEN for this program until Q2 of next year…”</blockquote><p>This massaging of the previously-defined attributes represents the best path to success in this exercise. As with all intellectual collaboration, compassion, tact, and an open mind are critical to effective dialogue.</p><blockquote><em>As with all intellectual collaboration, compassion, tact, and an open mind are critical to effective dialogue</em></blockquote><p><strong>Please don’t make the mistake of pouncing into negotiations before the basic WHAT, HOW, WHO, and WHEN attributes have been initially defined and documented</strong>. The human brain isn’t so hot at this ‘breadth first, then depth’ approach. We tend to get in a lather and dive right down the rabbit hole.</p><p>In order to make the most of this exercise, we need to coach each other to peel the onion one layer at a time. The concepts defined and shared during that initial round, before the negotiations begin, become the objects we all move around the map while the negotiation is underway.</p><h3>What About Budget?</h3><p>Even the richest of enterprises still operate within some kind of financial guardrails. There is no question that cost is a critical constraint to all program planning. However, in the scenario postulated here, a small group of senior leaders huddled after-hours to try to work through an intractable business problem, we really don’t want to get into the details of dollars and cents. At this juncture, we want to focus on what is theoretically possible with the assets available, not be limited by what is financially feasible. Nobody ever invented the future by starting with accounting (no offense, <a href="https://www.linkedin.com/in/thomas-bliss-71360114/">Tom Bliss</a>).</p><blockquote><em>Nobody ever invented the future by starting with accounting</em></blockquote><p>We may be forced to run a secondary round of negotiation once we introduce cost into the picture. Better that than to be limited right out of the gate by budgetary realities. To quote the great Kenny Rogers, “There’ll be time enough for counting, when the dealing’s done.”</p><h3>Start Off On The Right Foot, Then Run Like Hell</h3><p>I’ve been in that postulated room, with the pizza and the scotch, many times throughout my career. It’s exciting and daunting, and in my experience the enterprise rarely finds itself there willingly. More often, business realities conspire to force our hand in sketching out a solution to a problem that can no longer be ignored or cost-effectively held at bay.</p><p>During those initial moments of inception, <strong>envisioning the future program attributes in the right order helps mitigate the risk of missing crucial details</strong>. Due to the operational mechanics and hierarchical structures of modern enterprises, oversights generated during this early planning might lie dormant for weeks or months. By the time we recognize these errors it may be too late to fix them without large impact to the program, its budget, or the enterprise as a whole.</p><p>We avoid these oversights by taking a breath, envisioning program inception in the right order, getting it all on the whiteboard so our syntax is in synch, and negotiating in good faith toward a feasible solution.</p><p>At the end of this inception process, we’re still only at the very start of the program. But handling this part with good diligence provides the firmest possible foundation upon which to build everything that comes after.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/planning-inception-drew-harteveld-nom8e/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7963e4bd0d12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Postcards from the Brink]]></title>
            <link>https://drewharteveld.medium.com/postcards-from-the-brink-131d9aab32ec?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/131d9aab32ec</guid>
            <category><![CDATA[digital-strategy]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[martech]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Fri, 26 Jan 2024 18:08:47 GMT</pubDate>
            <atom:updated>2024-01-26T18:08:47.058Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sO6pLKm3sdV99G5fN_fRrg.jpeg" /></figure><h4>Clutching a program from the jaws of disaster and living to tell the tale</h4><p>During the past year I had the pleasure of collaborating with a large team on a global MarTech initiative at a major life sciences firm. When my team walked in the door, the program was on the brink of collapse. As I write this, we are in the final third of our timeline with our program humming efficiently. It’s amazing what a little bit of process optimization and governance can do.</p><p>None of what my team implemented was groundbreaking. We’ve all seen and done these things before. But recognizing the needs and generating fit-for-purpose solutions seems to have been the missing piece in an otherwise complete puzzle. To be clear: the ground-level team was rocking before we arrived, and are still rocking today. But sometimes rocking at the ground level, alone, just isn’t enough to keep a program on the rails.</p><blockquote><em>Sometimes rocking at the ground level, alone, just isn’t enough to keep a program on the rails</em></blockquote><p>Below, a few high-level themes related to the issues we discovered, the solutions we put in place, and the impacts those had on the larger effort.</p><h3>“Lead with Compassion and Humility”</h3><p>Stealing this quote from a favorite colleague, <a href="https://www.linkedin.com/in/bobby-pennington/">Bobby Pennington</a>. While it might sound hokey, it is truly the root of successful collaboration.</p><p>We are all humans, deserving of the most basic compassion and respect when we come to work each day. While we may work in different departments, or for different firms, and be focused on different parts of the larger process, we are all engaged within the service of the program.</p><p>Some enterprises have organically developed a culture of differentiation and blame. Leveling the playing field, clearly defining jurisdictional boundaries, holding everyone accountable, and enforcing a low-tolerance policy toward bad behavior in this area are critical to program success. We need clearly defined rules of engagement around how we work together, and must all play by those rules. If we can’t meet that most basic standard of behavior, we’re dead on arrival.</p><h3>Lift &amp; Shift Strategy</h3><p>The program in question involved the migration of a large volume of content data from one system to another. Having been through similar endeavors before, leadership realized that the winning strategy is to <em>limit change to an absolute minimum through this process and get to the target platform as quickly as possible</em>.</p><p>There can be an inclination, especially for those new to this kind of migration, that, “Hey the hood is open and the tools are out, so wouldn’t it be most efficient to make all the other adjustments we need while we have this move underway?” This is a recipe for disaster. Every individual change, even the small ones, increases risk exponentially.</p><blockquote><em>“Hey the hood is open and the tools are out, so wouldn’t it be most efficient to make all the other adjustments we need while we have this move underway?”</em></blockquote><p>Our program is lucky enough to have this ‘Lift &amp; Shift’ approach mandated, defined, and enforced from its very inception. Without the streamlining this approach engenders, we would still be wallowing in the first phase of the project, wondering why progress was so difficult to attain.</p><h3>Effective Leadership Engagement</h3><p>Speaking of our Lift &amp; Shift strategy, it is enforced with compassion and teeth by an action-biased Steering Committee focused on removing roadblocks and creating program alignment.</p><p>The members of this SteerCo have the authority to make binding decisions on the program, and the wisdom to understand the importance of <strong>clear alignment in supporting those decisions</strong>. Convincing leaders to put the needs of the greater enterprise ahead of their own agendas is a major win in any business context. In the case of our program, it became among the most potent forces driving our success.</p><h3>Shared Source of Truth</h3><p>Among the most concrete and actionable changes we made in this program was to create a self-service list of milestones for the many stakeholders following along with our progress. These milestones represent the fusion of our own planning/progress, as well as constraints from the business, external partners, and some regulatory authorities that play a role in this enterprise.</p><p>Information that had been cloistered by bureaucracy in the past was suddenly clear and freely available for our stakeholders. <em>They might not be thrilled with the dates we publish</em>, but at least they experience the control that comes from knowing where to find those dates, and track their progress along the way.</p><blockquote><em>Information that had been cloistered by bureaucracy in the past was suddenly clear and freely available for our stakeholders</em></blockquote><p>In the event that one of those stakeholders requires more detail than that provided by these self-service materials, we do an on-demand deep dive to address their specific questions. When we do, those published milestones become a valuable shared point of departure for the conversation.</p><p>Maintaining synchronization across these materials requires a fair amount of effort from program leadership, but the payoff for our customers — and thereby the health of the program itself — is well worth that lift.</p><h3>Jurisdictions &amp; Responsibilities</h3><p>Roles, responsibilities, and jurisdictions must be clearly defined. This is useful in all of business, but particularly critical where large programs are concerned.</p><p>When I arrived on the program, the customer had a poor habit of keeping responsibilities vague and then placing blame on a vendor — <em>the party least able to defend itself </em>— when expectations were not met. Identifying and agreeing to curb this behavior demanded some uncomfortable conversations.</p><p>Ultimately, the customer recognized that responsibility must be logically and equitably distributed across the larger team, those assignments must be clearly documented, and everyone must be held accountable to complete their own tasks.</p><p><em>This seems totally obvious in the light of day</em>, but we all know how destructive culture and social norms can spread throughout a company if better behavior is not positively modeled and continually enforced by senior leadership. Que everyone’s favorite Drucker quote about culture eating strategy for breakfast…</p><p>Addressing those issues through clear definition of jurisdictions and responsibilities within the context of our program was a critical win.</p><h3>Collaboration with Partner Orgs</h3><p>The enterprise in this scenario is complex, global, and operates in a highly regulated industry. As such, our program is deeply dependent upon other groups to realize our own mission. To make matters worse, most daily operations at the company occur within existing organizational silos, while our effort uniquely required operation _across_ those silos.</p><p>Not recognizing the potency of these dynamics, we blundered around a little bit in the beginning, stymied by a lack of traction at every turn. During a timely reset, we politely reintroduced ourselves to these partner orgs, explained our mission, and worked to understand their own agendas. Discovering opportunities for our own mission to support and enhance those agendas has been useful to secure buy-in and associated collaboration.</p><blockquote><em>Discovering opportunities for our own mission to support and enhance those agendas has been useful to secure buy-in and associated collaboration</em></blockquote><p>We have also been lucky enough to find key resources within each partner group with the knowledge, authority, and willingness to become strong collaborative partners to our program.</p><p>All this complexity requires a fair amount of bobbing and weaving in our own planning to get us from point A to point B — complexity my team is happy to absorb if the alternative is spinning our wheels in place.</p><h3>“We Succeed or Fail, Together”</h3><p>I was introduced to the “We succeed or fail, together” concept during my embrace of Agile in the early aughts. I have delivered this message to many, many stakeholders and colleagues over the years, and once even needed longtime mentor and infamous digital troublemaker <a href="https://www.linkedin.com/in/scottjlevine/">Scott Levine</a> to deliver it to me during a particularly contentious integration program.</p><p>Like the ‘compassion and humility’ quote addressed at the top of this piece, this concept is existential to any program. As described by a leader from our primary vendor, “In bringing you on board as their own program manager, [customer] suddenly had more skin in the game.” That may sound crazy since the customer was always footing the bill, and desperately needed the program’s success to support its larger strategic goals. <strong>But he’s right.</strong></p><p>Bringing OpsGov into the middle of this program was an act of defiance against the turnkey expectation of the original agreement. It represented the customer standing up and taking active responsibility for daily operations of their program. In doing so, they gave up whatever catharsic or political cover might be gained from pointing blame at a vendor for lack of success. With that bargain, they netted enhanced collaboration, transparency, and control.</p><blockquote><em>With that bargain, they netted enhanced collaboration, transparency, and control</em></blockquote><h4>Paved With Good Intentions</h4><p>I don’t mean to suggest that my team or these learnings represent the golden ticket to success with every complex program. Every enterprise is unique, and as program management professionals it is our job to enter into new situations with ears open and head on a swivel. Challenges must be understood first and addressed second, or we risk wasting precious time and treasure solving for problems that don’t actually exist.</p><p>My experience has been, however, that issues and mitigations like those described here represent a melody that gets played often when humans come together in large, complex, for-profit enterprises to address structural needs. So next time you are walking into a difficult and broken situation, hum this melody as you explore its dark corners. I’m betting you will find at least some of these recommendations applicable as you put your own solution strategies in place.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/postcards-from-brink-drew-harteveld-lffwe"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=131d9aab32ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stamping Out Camrys]]></title>
            <link>https://drewharteveld.medium.com/stamping-out-camrys-20f3717e345a?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/20f3717e345a</guid>
            <category><![CDATA[research-and-development]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[program-management]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Wed, 26 Apr 2023 18:43:25 GMT</pubDate>
            <atom:updated>2023-04-26T18:43:25.454Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*723jcYKUQdyNE77DQbUOGw.jpeg" /><figcaption>Photo from: 50 Shades of Beige: A Visual History of the Toyota Camry; Car &amp; Driver</figcaption></figure><h3>Creating an equivalency of expectation in the nature and output of Product Development with Production leads to frustration and disappointment</h3><h3>Dangerous Equivalency</h3><p>My work as an independent consultant provides rich opportunities to interface with senior-level business leaders, particularly in the technology and operations realms. This is a privilege, and always educational. Because my own focus is on product development, and that of the business leaders normally is not, there is a specific conversation I find myself having on a regular basis. It starts with the business leader saying something like:</p><blockquote><em>“Hey, when I buy a Camry, what I expect to get is a Camry. Not a lot of discussion about the Camry costing more than originally quoted, or ‘could you live without the air conditioning for the first few weeks you have it on the road?’”</em></blockquote><p>This statement alludes to painful experiences by the leader with Product Development projects in the past, including overruns and the need to de-scope features along the way.</p><p>This is a valid perspective, particularly coming from a C-level leader. <em>Unfortunately, it signifies a fundamental misunderstanding of the differences between Product Development and Production.</em> If we can’t unwind this misunderstanding, every Product Development project will be at risk of the kinds of frustration and disappointment articulated by the leader in the statement above.</p><h3>Dueling Analogies</h3><p>To embrace the analogy, Toyota has invested decades learning absolutely everything there is to know about building Camrys. Their profitability on the Camry line is measured in millimeters of weld margin and seconds of assembly line throughput. Production is a game played by vigorously limiting the number of variables and exerting maximum control over those that remain. At its root, Production clearly understands and has deep experience with every facet of the process to convert raw materials into a finished product. Toyota has been manufacturing Camrys since 1983. They have the process completely wired at this point. <strong>That is the essence of Production.</strong></p><p>Product Development represents a very different scenario. While we might be leveraging tools, platforms, processes, and target markets with which we have familiarity, the whole point of Product Development is to assemble, integrate, and customize these in a new context to derive a new outcome. “Yes, we have done this before. But we’ve never done it here, with your platform ecosystem, organizational structure, data portfolio, and political environment. And those attributes represent a whole lot of variability.’” From this perspective, it is clear just how different Product development and Production truly are.</p><blockquote><em>“Yes, we have done this before. But we’ve never done it here, with your platform ecosystem, organizational structure, data portfolio, and political environment. And those attributes represent a whole lot of variability.”</em></blockquote><p>Extending the Toyota analogy, a more apt comparison for Product Development than the Camry assembly line would be the Toyota Racing Development [TRD] research &amp; development program. While specifics of Toyota’s TRD investment are not shared publicly, the capsule history found here: <a href="https://www.autotrader.com/oversteer/what-is-trd">https://www.autotrader.com/oversteer/what-is-trd</a> provides some context for the breadth, depth, and longevity of the program. Similarly, this press release [ <a href="https://pressroom.toyota.com/toyota-earns-most-rd-patents-among-automakers-in-intellectual-property-owners-association-rankings-for-8th-consecutive-year/">https://pressroom.toyota.com/toyota-earns-most-rd-patents-among-automakers-in-intellectual-property-owners-association-rankings-for-8th-consecutive-year/</a> ] related to patent awards includes the quote, <em>“Toyota invests over $1 million in emerging technology globally and has invested over $1 billion in R&amp;D related to automated vehicles and robotics since 2017.”</em> All of this demonstrates that Toyota, my business leader’s example of efficiency at the top of this post, is not only expert in Production but also invests heavily in Product Development.</p><h3>Learn Today to Earn Tomorrow</h3><p>Product Development and Production are different games, with different rules and different goals. Creating comparisons between the two is unhelpful, and can be the source of unrealistic expectations. Product Development is inherently risky [SEE ALSO: <a href="https://drewharteveld.medium.com/first-lets-not-fail-19756f4bcd58">https://drewharteveld.medium.com/first-lets-not-fail-19756f4bcd58</a> ] and requires a wide margin for learning-based change along the way. <strong>This doesn’t mean the Wild West. </strong>Those experienced in Product Development, regardless of industry, know how to execute these projects in a manner that is organized, controlled and transparent. But what it does mean is that if you are a business leader who expects your Product Development projects to roll forward like Camrys rolling off an assembly line you are in for a load of disappointment.</p><blockquote><em>This doesn’t mean the Wild West. Those experienced in Product Development, regardless of industry, know how to conduct these projects in a manner that is controlled and transparent.</em></blockquote><p>There’s an old saying in Product Development that we <strong>‘learn today to earn tomorrow’</strong>. This can be interpreted in two ways. First, it would be prudent to not think of your Product Development initiatives as strictly profitable in the near term. There are simply too many unknowns to accurately estimate the cost to reach the target vision, as well as profit that can be harvested once the product is in place. This is why so many smart companies employ an iterative approach to product development — investing in multiple, small-scale initiatives to prove the many facets of a concept before going all-in on productionalization. The other interpretation of the quote is that if you choose NOT to learn today, you will be challenged to earn revenue tomorrow. Our industries, target users, and the larger marketplace are always in motion. While product development may demand inconveniently wide margins for learning and change along the way, few enterprises can afford to opt out of the pursuit completely while still retaining market share and relevancy.</p><h3>Play the Game</h3><p>Given that equation, it makes sense for business leaders to clearly understand the opportunities and challenges of engaging in Product Development, investing in the people, processes, and tools necessary to do it well. Conflating Production with Product Development, and expecting a similar performance profile from each, is a recipe for frustration and disappointment. Scrub this mindset from your leadership team, recognize Product Development for the bargain it represents, and gain expertise in executing these projects effectively to propel your enterprise forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20f3717e345a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“First, let’s not fail.”]]></title>
            <link>https://drewharteveld.medium.com/first-lets-not-fail-19756f4bcd58?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/19756f4bcd58</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Mon, 10 Apr 2023 22:55:58 GMT</pubDate>
            <atom:updated>2023-04-10T22:59:10.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/257/1*6Uf5W1rUvZPtAG_5DhPsPQ.jpeg" /><figcaption>…and things were going so well</figcaption></figure><h4>Embracing a risk management posture that secures the fate of the project from inception through closure</h4><h3>Putting Risk In Its Place</h3><p>We all get into this business because we love to build things. Building is fun, it often makes the world a slightly better place, and occasionally we even get paid to do it. But there is one pivotal piece of business to address before grabbing the tools and starting to hammer out software — our risk management posture.</p><p>Technology product development is risky business. While we may have developed expertise in the platforms, coding languages, and data structures utilized in our industry, most projects find us in a situation where we are bringing that knowledge together with a large number of variables for the first time in history.</p><blockquote>“Haven’t you ever done this before?”</blockquote><blockquote>“Of course we have, but we’ve never done it HERE, with your platform ecosystem, business structure, political environment, and goals.”</blockquote><p>There is plenty that can go wrong in our work, which is why it is so critical to <em>limit that list to only those variables that absolutely cannot be controlled</em>. We’ll have our hands full with the risk that is organic to the product development business — we can’t afford to be distracted of any disasters of our own making.</p><p>For that reason, the risk management posture we bring to our own projects at OperationalGovernance is <strong>“Defense, first”</strong>. While it might feel heroic to rush into the burning building of customer business problems without adequate diligence, doing so rarely leads to the best possible outcome. Instead, we employ a methodical, carefully considered, highly transparent process in order to identify, mitigate, and manage as much risk as possible from Project Kickoff through Administrative Closure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yHLEDJfeKatrCy9j-cmPfw.png" /></figure><h3>Understanding the Components of Risk</h3><p>From the very outset, we must recognize that some risk is <strong>unknown</strong>. It’s either going to hit us or it isn’t, and if it doesn’t we will be blissfully unaware it was even lurking in the shadows. <em>We win where unknown risk is concerned by keeping this category as small as possible.</em> We realize that by doing the homework, understanding the larger contexts within which our project exists, and remaining sensitive to changes in the environment that may signal something unexpected in our midst. To quote the incomparable VV Brown, “Baby, there’s a shark in the water.”</p><blockquote><em>While it might feel heroic to rush in to the burning building of customer business problems without adequate diligence, doing so rarely leads to the best possible outcome.</em></blockquote><p>On the Known side of the diagram, we see all of the risks of which we have the potential to be aware. Note that some known risks are simply deemed <strong>acceptable</strong>. Due to their low likelihood, small expected impact, or the cost of mitigation being too high for us to afford, we document these risks, cross our hearts, and let ’em ride.</p><p>Of those risks deemed to be <strong>unacceptable</strong>, some may be <strong>mitigatable</strong> while others may not. History is full of great projects that never came to fruition because the known risk was so potent, and our ability to reliably mitigate so feeble, that even their most dedicated evangelists simply shook their heads and walked away.</p><p>The place we can have the greatest impact on the risk management of our projects is through the definition, description, and execution of <strong>mitigations</strong>. Depending upon the cost to put these mitigations in place, we may be able to insulate ourselves completely from the danger if/when those risks manifest. More often, our mitigations strike a balance that protects us from the most egregious damage possible within the limits of available time, cost, and other constraints. In those cases, some <strong>residual</strong> risk seeps through our mitigating filter and drops to the bottom line. That’s the risk you’ll need the intestinal fortitude to plow through on the path to project completion.</p><p>I once flew halfway across the country with an encrypted hard drive in my carry-on as a mitigation to the internet going down at just the moment my banking client was transferring millions of records for an important acquisition. The likelihood of the risk coming to fruition was low, but if it had the impact to our project would have been huge. The cost of a round-trip ticket from NYC to Dallas was reasonable, so I spent a day at 30,000 ft on a ‘just in case’ mission. In that situation, the internet did not go down and the data in my backpack turned out to be redundant. My reward for the exercise was free peanuts and peace of mind. <strong>I’ll take it.</strong></p><p>Tracing multiple lines through this diagram is an interesting intellectual exercise that provides a visceral understanding of just how much total risk there will be in any project we undertake. Coming face-to-face with that risk doesn’t mean we should run from those opportunities. It does, however, demonstrate how incredibly important it is that we strike a defensive posture on the project from its very first moments — and hold that diligence through administrative closure.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/first-lets-fail-drew-harteveld"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19756f4bcd58" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enterprise Platform Integration; An Iterative Approach]]></title>
            <link>https://drewharteveld.medium.com/enterprise-platform-integration-an-iterative-approach-52aad552135a?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/52aad552135a</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[enterprise-platform]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Wed, 05 May 2021 16:25:07 GMT</pubDate>
            <atom:updated>2021-05-05T22:55:46.245Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*vMAaaQuGo9sedYJptcPA-A.jpeg" /><figcaption>Image courtesy Google</figcaption></figure><h4>Harness the tools of Iterative product development to drive your enterprise platform integrations with speed, transparency and control over risk</h4><p>With a lilt in her voice, one of the strongest technology leaders I’ve ever worked with recently said, “I love the Agile for new product development, but I’m still not convinced where platform integration is concerned…”</p><p>It’s an understandable position, and addresses issues I have wrestled with in my own practice for many years. After all, with an enterprise platform integration:</p><ul><li>We know where we’re starting, and</li><li>We know where we expect to end up</li></ul><p>The shortest distance between two points will always be a straight line, and that looks a whole lot like a Waterfall project.</p><h3>Don’t Believe the Hype</h3><p>As a dedicated Agilist, my refutation of the model above isn’t around the “straight line” part, but rather the assertion that we “know where we expect to end up”.</p><p>YES, we may intellectually understand, in broad strokes, the scope and target end-state of the initiative. But the devil lies in the details, and the penetrating truth is that broad strokes don’t cut it when millions of dollars and professional reputations are on the line. Below the level of broad strokes are thousands of choices and challenges that must be metabolized during this journey. Very few of these are clearly identified or adequately understood at the beginning of the effort, when Waterfall would have us execute and lock our planning.</p><p>We need a mechanism to decompose those broad strokes into details granular enough to build and test. And that’s where an iterative methodology really shines.</p><p>The benefits of an iterative approach have been described in rich detail elsewhere, but just as a quick review of some top-contenders:</p><ul><li><strong>Risk/Value Balance: </strong>Agility is all about keeping cycle times fast, queues short, and holding time at a minimum. All of these strategies compress the distance between cash invested in the build and value delivered to the marketplace (internal or external). In a world as chaotic as ours, holding back delivery simply for the sake of a grand, “ta-dah!” moment is insane. Think of this in the context of manufacturing: would any manufacturer build all of its products, store them in a warehouse, and only ship them into the consumer pipeline when every last one was completed? Of course not! One warehouse fire and the entire investment would be up in smoke. Manufacturers build, ship, and earn on a rolling basis to mitigate risk and fund the machine.</li><li><strong>Better Business Control: </strong>Iterative methodologies all revolve tightly around direct, day-to-day engagement of product-focused stakeholders in the build. Not only does this keep the business in the driver’s seat, but also ensures that stakeholders understand the context and nuance of challenges along the way. No more limitations to visibility based on the lens established by the service provider.</li><li><strong>Real-World Feedback:</strong> We’re not as smart as we think we are. <em>Yes, even you. </em>It turns out that much of the functionality that we invest the enterprise’s precious capital to build is barely ever utilized by real users. The best way to combat this risk is to put the tools into the hands of real users as early and often as possible so that we can learn from their feedback and behavior. What they find useful, we extend. What they ignore, we abandon. This approach demands a willingness to deploy features in an unpolished state, and the relationships to do so without driving the user community bananas. In exchange, our product roadmap shifts from theoretical to practical with a bullet.</li></ul><blockquote>Okay, so we all agree that applying an iterative approach to enterprise platform integration is worth the trouble. Let’s talk about one strategy for making that happen.</blockquote><h3>Acme Custom Widget</h3><p>I will create a brief narrative so that we can run through an iterative approach to enterprise platform integration, together.</p><p><em>Acme Custom Widget manufactures and installs custom widget solutions to a global customer base</em></p><p><em>Cheaper widget options are available, but Acme differentiates with quality, range of configurations, expert installation, and managed services</em></p><p><em>Acme currently runs its operations on a portfolio of platforms that have grown organically over time. They are looking for a more holistic solution</em></p><p><em>Acme has found a vendor/platform/set of platforms [doesn’t matter for this narrative] that they believe will close current operational gaps and position them for success in the coming years</em></p><p>Acme operations involve the following basic Business Functions:</p><ul><li><strong>Commercial: </strong>Sales pipeline and relationship management</li><li><strong>Estimating: </strong>works closely with sales, and acts as a bridge to Operations and Finance</li><li><strong>Resourcing: </strong>Specialty widget manufacturing and installation is tricky business. Among its differentiators is the portfolio of experts that Acme can bring to custom widget installations across the globe</li><li><strong>Operations: </strong>Deal execution from post-close through delivery</li><li><strong>Change in Scope: </strong>Many specialty widget deals require adjustments along the way based on requirement maturation, market conditions, and ground truth. The Change in Scope business function manages these in-stream adjustments from the Commercial, Operations, and Financial perspectives</li><li><strong>Financial:</strong> Corporate finance, cost tracking, AP/AR, etc.</li></ul><h3>NOT our Strategy</h3><p>Replacing the current portfolio of tools in place at Acme with a new suite of tightly integrated platforms is a massive job. Based on the breadth and importance of integrations across these platforms, the initial idea might be to make ALL of the changes, test them together, and then launch to users.</p><p>Fortunately, five decades of IT experience have convinced us that while that may <em>seem the most logical approach</em>, it is not the approach most likely to succeed.</p><blockquote>Fortunately, five decades of IT experience have convinced us that while that may <em>seem the most logical approach</em>, it is not the approach most likely to succeed</blockquote><p>Entire books have been written about why the monolithic approach to enterprise platform integration no longer works, and a complete examination is beyond the scope of this post. Suffice it to say that this endeavor is simply too large (too many stakeholders, too many integrated business processes, too many different tools and platforms, too many use cases, too many competing priorities) to be effectively metabolized in one shot.</p><p>Rather than a monolithic approach, ours will be iterative.</p><h3>An Iterative Approach</h3><p>Leveraging an iterative approach to enterprise platform integration, at Acme Speciality Widget or anywhere else, requires us to make fundamental decisions about how the total scope will be parsed into a serialized set of components to be addressed in priority order.</p><p>Leveraging some syntax created in a previous post (<a href="https://drewharteveld.medium.com/avoiding-the-quiet-disaster-6078a7608411">https://drewharteveld.medium.com/avoiding-the-quiet-disaster-6078a7608411</a>), we will organize the work according to <strong>Business Functions</strong>.</p><p>As the name suggests, Business Functions describe elements of the business, not technology tools or platforms. Organizing the scope in this manner helps ensure understanding by and continued relevance to the stakeholders so dependent upon this program’s success.</p><p>The logical map below helps us visualize Acme’s Business Functions, as well as key points of intersection:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7b5qilOeSWLK05DY" /></figure><h3>Iterative Delivery Across the Map</h3><p>In a nutshell, our approach will be to carve off individual Business Functions from the larger map and deliver them one at a time. This, as the only alternative to delivering in a monolithic fashion.</p><p>Based on our planning at Acme, this is how we expect to organize and deliver the total scope:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EzQcdV5UzCtwjg0i" /></figure><h4>Business Function Integrations (and Embracing Difficult Decisions)</h4><p>Having a shared master plan is good, but let’s not get ahead of ourselves… Carrying forward our Acme narrative, based upon a robust analysis of job complexity, readiness, and platform foundations, it has been decided that the first Business Function to be tackled will be <strong>Resourcing</strong>.</p><p>What this really means is that the team will invest the first Flight of the program [more on Flights, below] focused on meeting the needs of the <strong>Resourcing</strong> Business Function. The expectation is that:</p><ul><li>Scope of this Business Function will be broken down into individual Functional Attributes</li><li>Functional attributes will be constructed in a strictly prioritized fashion</li><li>Only as many Functional Attributes as can be metabolized by the team during this Flight can be included</li><li>At the end of the Flight, all Functionality Attributes will be deployed to Production</li><li>Real users will begin utilizing these Functionality Attributes in their everyday work</li><li>Unless other specific accommodations have been planned, this portfolio of Functionality Elements will represent the sum total of scope included in the Resourcing Business Function for this program</li><li>After the program is complete and all business functions have been addressed, the enterprise is welcome to make additional passes to add ever-more richness to the solution</li></ul><p>This is Acme’s shot at tackling <strong>Resourcing</strong> at this juncture, and the team will plow forward as aggressively as it can. It is likely that the team will not be able to address <em>every envisioned/defined element</em> of Resourcing during the Flight, which is why prioritization of those elements is so incredibly important. Also, to the greatest extent possible, each Functionality Element must be constructed such that it can stand on its own, in case some of its closely related brothers and sisters don’t make the cut. Understanding the contours of what _<em>absolutely</em>_ must be included for Resourcing to stand as a Business Function on its own — at least initially — is the nature of Minimum Viable Product strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1Y1_D80Si1aZTVE2" /></figure><p>Don’t fool yourself, these are excruciating decisions and the business of product development demands that we make them every single day.</p><h4>Iterative Exhaust</h4><p>Note the squiggly lines at each edge of the Resourcing solution in the diagram above. These represent the borders where the N<em>ew solution the team is putting in place rubs up against the Legacy solution that is already there</em>. These squigglies represent the need to integrate the New into the Legacy, at least temporarily. Eventually, the *entire* solution will be covered by new components. Until that time, we must ensure that the New and the Legacy can work together, in Production, seamlessly. We refer to these New-to-Legacy integrations, collectively, as “Iterative Exhaust”, an unavoidable byproduct of our iterative approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/0*j0M3jmnmuActq573" /></figure><p>Those who know more about arithmetic than about product development might look at the Iterative Exhaust and label it ‘waste’. After all, these involve code that is not intended to be utilized for the long term… As soon as the Business Function next door receives its own new treatment, these points of integration will have to be refactored or removed. “Wouldn’t it be more efficient,” they ask, “to just do the whole job and launch once at the end in order to avoid the cost of these disposable elements?” It’s a fair question, and the answer is “<strong>NO.</strong>”</p><p>Seventy years of dodgy IT initiative results have proven that the ‘build it all and then launch at the end’ approach is fraught with risk. Our choice is to embrace an iterative approach, instead, in order to help mitigate that risk. Iterative Exhaust is an unavoidable byproduct of that decision.</p><p>The ‘waste’ actually only exists on paper, anyway. My own involvement in twenty-five years of enterprise initiatives has taught me that while the physical manifestation of our work is software, the assets that lay just inches below that surface are all about <em>knowledge</em>. From a very real perspective, the product of the enterprise’s investment in the program is knowledge, of which working software is just an actionable byproduct. Our program isn’t a research project with somebody else’s money, but that doesn’t preclude us from understanding and maximizing the role that accrued knowledge plays in its outcomes.</p><p>From this point of view, the work involved, <em>and knowledge accrued</em>, in addressing Iterative Exhaust is anything but waste. Indeed, the more we learn about the borders of the New and the Legacy now, the better prepared we will be to expand the New into fresh territory during subsequent Flights.</p><blockquote>From a very real perspective, the product of the enterprise’s investment in the program is knowledge, of which working software is just an actionable byproduct</blockquote><p>IMPORTANT — While the goal of the integration program is to improve operations, the Iterative Exhaust should not include these aspirations. These are temporary bridges we are building between old and new. Their target in terms of convenience, robustness, and scalability should be limited to <em>“not materially worse than the user experience running in Production, today.”</em> It’s easy to get so swept-up in creating an improved solution that we lose sight of the actual yardstick against which progress will be measured by our users. We need a different yardstick for Iterative Exhaust than the one we use for the new functionality that represents our core mission.</p><p>Do not underestimate the capacity of those users to accept and support a temporarily less-than-optimal solution if they know it is in service of more fundamental improvement down the road. Especially if they feel included in the thought process along the way.</p><h4>Flights to Production</h4><p>As explained above, each Business Function is addressed, all the way to Production, within the context of its own Flight. So what’s a Flight?</p><p>A Flight is an organized set of Sprints, complete with its own expectations around planning and delivery. For the purposes of our Acme Custom Widgets example, each Flight has a duration of twelve weeks. Assuming sprints of 10 business days, that makes 6 Sprints per Flight. The diagram below helps illustrate each Flight’s internal structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0ZT6VzhCDpzexEdu" /></figure><p>The point of the Flight structure is to galvanize attention of the entire team around a limited body of scope during a designated block of time. Once the Business Function to be addressed during the Flight has been chosen, all other scope in the program is pushed out of view. We can’t solve all the Business Functions at once, so those that aren’t <strong>Resourcing</strong> will need to wait. We’ll wire ’em up when the time comes.</p><blockquote>The point of the Flight structure is to galvanize attention of the entire team around a limited body of scope during a designated block of time</blockquote><p>There are three key components to each Flight —</p><p><strong>New Functionality Sprints:</strong></p><p>Assuming a SCRUM methodology, as utilized at Acme, the team has 4 Sprints, or about 8 weeks, to tackle all of the Functional Attributes to be included in the Flight. Four sprints is not a long time, so, as explained above, prioritization and componentized construction will be critical.</p><p>As with all SCRUM, testing of the software must be managed within the bounds of each Sprint. Functionality Attributes that do not pass testing get tossed back into the Backlog for future reprioritization.</p><p>One unique element of this approach is that the team does not deploy code all the way to Production at the end of each Sprint. Doing so is a laudable aspiration of Agile, and the absolute best way to maximize value to the enterprise. But within the structure being described in this post, our operational goals are best met by temporarily delaying deployment until the end of the Flight</p><p><strong>Hardening and Deployment Sprint:</strong></p><p>The Hardening and Deployment Sprint does not involve any new functionality. During this Sprint, any few outstanding bugs are addressed, and all of the code is retested in an integrated fashion. Further, the team prepares the code for deployment to Production and plans any associated cutover activities. Any Functionality Attributes that are not able to successfully pass testing are stripped from the scope and tossed back into the Backlog. These will not be included in this Business Function for the foreseeable future.</p><p>At the end of the Hardening Sprint, all Functionality Attributes are deployed to Production.</p><p><strong>Hypercare and Prep Sprint:</strong></p><p>The two weeks following deployment of the Business Function are referred to as a Hypercare and Prep Sprint. It is imperative that no new functionality be constructed during this time. Instead the focus is on:</p><ul><li>Keeping the team on the balls of its feet to support any bugs or issues discovered in Production</li><li>Providing training and other support to the real-life users employing the solution in their real-life jobs</li><li>Engaging in high-level planning for the next upcoming Flight</li></ul><p>If your enterprise is operating in a Scaled Agile framework, the Flights as described above look a whole lot like SAFe’s “Program Increments”. That is by design. The point here is that this cadence is valuable and accessible even if your company hasn’t jumped into the deep end of the Scaled Agile pool.</p><h4>Production or Bust</h4><p>As described above, the team needs to think of this Flight as their single shot at addressing <strong>Resourcing</strong> during this program. That’ll require brutal prioritization and a coding architecture that leaves accessible ‘hooks’ for currently unknown integrations down the road.</p><p>Unless leadership is willing to rebaseline the entire program, what we can’t do is <em>“just tack-on a few extra sprints of Resourcing to get all the goodies.”</em> Even if leadership IS willing to rebaseline, this is rarely the best course of action. It is always better to plow forward across the larger scope, working toward a total-breadth solution. We can always charter a second phase program, after this one is complete, to lay-in more functionality under one or more Business Functions. And if there isn’t time/money to do that, all the more reason for us to keep our build lean and focus on delivering <em>some</em> functionality across the entire breadth of the solution.</p><p>One more quick reminder that the development team needs to utilize a set of best practices around code and branching such that any single Functionality Attribute that cannot pass testing can be stripped away without the entire solution falling apart. <strong>Because at the end of the Flight we are going to Production.</strong></p><h4>Rinse &amp; Repeat</h4><p>Once the Business Function/ Flight/ Sprinting rhythm is in place, the program takes on a life of its own. Subsequent Business Functions are snapped-together like Legos into an ever-extending row from the beginning of the program to its carefully managed end. As each new Business Function is addressed:</p><ul><li>Any Iterative Exhaust that was previously put in place is identified and refactored into the new solution</li><li>New Iterative Exhaust is created at the borders of this Business Function in order to allow it to play in Production with all elements still in Legacy mode</li></ul><p>Product development teams are quick to learn architectures that largely mitigate any churn caused by Iterative Exhaust.</p><p>The diagrams below illustrate the succession of Flights through which Acme’s entire map of Business Functions is addressed across its enterprise platform integration program:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uCnpsAKPoKXpf7Lh" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1uziTxM2CVFYWmDq" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FBQ08rtecormzUpH" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9sYu_156qiK04BUa" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qxYcicWEChOhXB6S" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yteM4koylG4GCQDK" /></figure><h3>One Team, One Dream</h3><p>All of this operational architecture is worthless if senior leadership can’t make the mental shift that lies at the root of all Agility:</p><ul><li>“This is the team I have chosen to assemble, and I provide it with the authority to responsibly steer the program as well as my continued faith in its intention to do so”</li><li>“I have my own agents acting as full members of this team, as responsible for success, failure, and working through challenges as every other member”</li><li>“This team will work as hard as it can, every single day, and keep the strategy of the program and enterprise as the core of every decision and action”</li><li>“I understand that I cannot have everything, thus recognize the pivotal responsibility of my embedded agents to prioritize the work in order that the most important components can be completed, first”</li><li>“I know that the best way for us to get from the start to the finish of this foot race is to focus on momentum and not get bogged-down in functional minutiae along the way. We can always come back for another pass, later, if warranted”</li></ul><p><strong>If senior leadership can’t make that mental leap — and many leaders cannot — all the operational architecture in the world isn’t going to solve the problem. Forget an iterative approach. Forget a waterfall approach. Stick with running your business on index cards and good luck scaling your enterprise.</strong></p><h3>Agile Evolution</h3><p>It is true that iterative methodologies were germinated in the world of new product development. The primacy of the Big Tech early adopters in today’s marketplace proves Agile’s potency in that scenario. Do not underestimate the utility of these concepts in an enterprise platform integration context, as well, however.</p><p>Given a lightweight architecture for defining and organizing scope, basic shared commitments about prioritization and momentum, and an acceptance that any puzzle needs to be assembled one piece at a time, we can leverage an iterative approach to de-risk and maximize our enterprise platform integrations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52aad552135a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resolving Conflict]]></title>
            <link>https://drewharteveld.medium.com/resolving-conflict-33173251a54?source=rss-35f035fa02c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/33173251a54</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Drew Harteveld]]></dc:creator>
            <pubDate>Mon, 05 Apr 2021 16:17:31 GMT</pubDate>
            <atom:updated>2021-04-05T16:18:43.845Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJGDTPQhUvGNAEslG1dDAA.jpeg" /><figcaption>Image courtesy of Flickr</figcaption></figure><h4>Conflict is a constant companion in the world of product development. Adopt an architecture that converts this liability into an asset to strengthen your team and the products it delivers to market</h4><p>Product development is tricky stuff. We are in the business of creating something from nothing, embedded within complex, global, collaborative enterprises. Conflict is endemic to that process. Indeed, there are those who believe that conflict is a critical attribute to the creation of great products. <strong>Count me among them.</strong></p><p>Conflict pushes us to maximize performance</p><p>Conflict keeps our focus on the needs of our customers</p><p>Conflict forces us to examine multiple options, cut away the fat, and secure high ground</p><p>Conflict helps leadership to understand where we are, what is challenging our progress, and how they can best engage to create alignment</p><p>Conflict sharpens team cohesion</p><blockquote>Conflict sharpens team cohesion</blockquote><p>But conflict can also be corrosive. When not addressed in a swift and egalitarian fashion, it can fester to become a source of increasing drag on enterprise progress. Because humans are tribal creatures, conflict that begins between two individuals or groups in one subject area can spread to areas having nothing to do with that original concern. When conflict becomes endemic in this way, it blossoms into feud.</p><p>We need a forward-focused structure in place to address conflict in our programs before it does too much damage. Left unchecked, it has the potential to eat us alive.</p><h3>Resolution Attributes</h3><p>I utilize a high-level structure to organize my teams strategically around conflict resolution. This seems awfully formal when typed out in blog form, but my experience has been that it can be established up-front and utilized in a manner that feels second nature in no time.</p><p>There are three key attributes to successful conflict resolution: <strong>Embracing the Conflict</strong>, <strong>Opening Lines of Communication</strong>, and <strong>Establishing a Decision-Making Hierarchy</strong>. Let’s take a look at each, along with a few activation examples.</p><h4>ATTRIBUTE: Embracing the Conflict</h4><p>There are plenty of legitimate reasons for conflict to exist within our complex enterprises:</p><ul><li>Multiple jurisdictions with different areas of focus</li><li>Separate business units, each with its own revenue streams</li><li>The ever-present fight for control of meager product development resources</li><li>The natural responsibilities of those groups tasked with de-risking the enterprise, such as Audit, Procurement, Legal, and InfoSec, as opposed to those tasked with enterprise expansion, like Sales, BizDev, and R&amp;D</li></ul><p>Perpendicular agendas are architected into many organizations because there’s just no other way to create a company that can simultaneously cover its many needs. In those cases, conflict isn’t caused by resources being angry or mean — they are simply doing their jobs. Conflict is a natural occurrence in these environments, and we must create structure to manage it with a minimum of angst and blowback.</p><p>The first, most important attribute to this structure is admitting those conflicts exist and dragging them into the sunshine for examination. We can’t fix what we can’t understand. Do the research and have the conversations necessary to clearly and completely define each conflict that is causing significant drag. Sometimes, shining this bright light reveals that there’s way more bark there than bite, and the resolution process can be that much easier to execute.</p><blockquote>We can’t fix what we can’t understand</blockquote><p>Two different work experiences of mine present opportunities for comparison. In one, the leader of our org was a well-known personality with a powerful core of enthusiastic followers. There was also a sizable faction of our target demographic, however, that our research had revealed to harbor passionately negative emotions about our brand. Unfortunately, there was an informal understanding that we weren’t to talk about that negative research when the leader was in the room. That was <em>conflict we were not free to embrace,</em> a state that created all sorts of wasted time, effort, and circuitous communication. Every company has liabilities, and these need to integrated into strategy in a logical fashion. A different CEO at a different company — also a celebrity — presented a counterpoint. That leader seemed always on the prowl for festering conflict, loving nothing more than to tug it from the shadows and get it addressed. This made for some uncomfortable meetings, but created a clarity and consistency that allowed the team to move at high velocity. Two different orgs operating at different scales, but interesting to compare, nonetheless.</p><h4>ATTRIBUTE: Opening the Lines of Communication</h4><p>If you have followed the instructions above and dragged your conflict into the sunshine, you better have a structure in place to hash it out among the relevant parties. Some of this is cultural, as different industries/enterprises have different default strategies for working through conflict. Having spent a considerable portion of my career on Wall Street, I’m no stranger to the executive shouting match. Other orgs work better with formal written briefs and gap analysis. Choose the communications medium that is the best fit for your own culture. I’m not here to judge — as long as you have a structure in place that allows all participants to feel safe in articulating and justifying their positions, you can find your way to resolution.</p><blockquote>As long as you have a communications structure in place that allows all participants to feel safe in articulating and justifying their positions, you can find your way to resolution</blockquote><p>Establish clear and stable rules of engagement for communicating about conflict:</p><ul><li>When will we talk through the disagreement?</li><li>Who will be included in that conversation?</li><li>what supporting assets will be brought into the analysis?</li><li>What guardrails will be put in place to keep the conversation efficient and under control?</li></ul><p>Many conflicts involve sensitive topics related to people, assets, and financials. Create a structure wherein these details can be exposed, examined, and addressed in a way that respects and maintains appropriate sensitivity</p><p>Leadership needs to decide if it is more interested in supporting its favorites: people, clients, products, markets, etc., or finding its way to the truth. If the communication rules of engagement apply to different individuals in different ways at different times — they break down in a hurry.</p><h4>ATTRIBUTE: Establishing a Decision-Making Hierarchy</h4><p>Getting those conflicts into the sunshine and creating an effective communications structure to clearly understand them from all angles will get us to resolution about 80% of the time. When we drain the angst out the bottom of most issues, the best course of action is usually clear to everyone.</p><blockquote>When we drain the angst out the bottom of most issues, the best course of action is usually clear to everyone</blockquote><p>Occasionally, however, our analysis around a conflict will lead to impasse. Everybody makes a good argument, but a single choice is required. Who is going to make that call?</p><p>Enterprise leadership must put in place a clear hierarchy of decision-making authority. Different enterprises have different aesthetics: some are comfortable pushing authority deeply down to those closest to the action. Others are more confident centralizing authority across a smaller set of leaders with formalized jurisdiction. Regardless of the aesthetic, there needs to be some kind of ladder that teams can climb in search of a leader with adequate authority to provide clear and binding resolution. And there must be mechanisms in place that allow for those escalations to be managed efficiently. Finally, that decision-maker must understand their role in the process and have the courage to provide a definitive and adequately detailed choice.</p><p>I once worked under an otherwise terrific CEO who chose to deploy her authority sparingly — leaving her direct reports to “fight it out” to determine whose solution would come out on top. <em>Good strategy for identifying ruthless EVPs, bad strategy for elevating the best ideas.</em> As a leader, it is your right and responsibility to make the tough calls based on imperfect information. <strong>Do your job.</strong></p><p>As soon as a challenge has been successfully adjudicated, decisions need to be memorialized in program documentation. Not only will this protect the team from plodding over the same rocky terrain more than once [it happens all the time on long-term programs], it’ll also begin building an archive of past decisions to serve as a reference for future conflict. If we can see that the Program Sponsor made a certain decision the last three times this kind of issue swung around, we can be reasonably sure of how she will rule if this one hits her desk, as well.</p><h3>Thrust, Parry, Slash, Parry, Thrust</h3><p>Conflict is a constant companion in the world of product development. Complex enterprises, a chaotic marketplace, and the need to move at speed set us at tactical odds with one another occasionally, even while we may be strategically aligned. Creating a solid architecture for conflict resolution is a critical component to your larger operational governance [SEE ALSO: <a href="https://drewharteveld.medium.com/operational-governance-5eebd570ff68">https://drewharteveld.medium.com/operational-governance-5eebd570ff68</a> ]</p><p><strong>Create that solid architecture by:</strong></p><ul><li>Embracing the Conflict</li><li>Opening Lines of Communication</li><li>Establishing a Decision-Making Hierarchy</li></ul><p>Executed properly, the liability of conflict can be converted into an asset that strengthens your team and the products it delivers to the marketplace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33173251a54" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>