A Strategy Must Be Built Using an Iterative and Incremental Method

Collin Rusk
3 min readJul 16, 2021

An organization needs explicit strategies, but they cannot simply conceive of them, implement them, and deploy them. Those schemes might be incomplete or insufficient, once deployed. An institution cannot anticipate every shortcoming, prior to construction or launch. Those imperfections can only be mitigated over multiple stages. Each launch provides new information, regarding the approach necessary for a strategy’s goals. A business must use a methodology employing iteration and incrementalism to build a strategy to meets its objectives.

A method’s purpose can have implied aspirations. That aim might only be achievable, if other targets are met. Those prerequisites are not always knowable to organization, prior to construction and deployment. An approach can have emergent qualities. For example, an institution might learn its game plan requires on-the-fly adjustment. A scheme for a draft board cannot stay static, since the list must adjust to what other teams do. What tweaks are needed and the circumstances that demand them are not always known, until they are encountered. Blue prints tend to have unanticipated attributes.

Characteristics are not a plan’s only unexpected aspect. A method’s problems are just as difficult to define upfront, as its purpose and its tactics are. Certain issues are not apparent to a company, until a process is built and used. For example, a team might discover that the order in its draft broad is tricky. That arrangement can have unexpected edge cases, leading to issues that are difficult to address. Sequencing is a multivariable dilemma. Any decision about any one element has built in assumptions, which can lead to difficulties, in the right circumstances. A draft board contains unforeseen issues, which can be tough to solve.

That unanticipated aspect is not handled efficiently, using single-pass development. That methodology tends to proceed slowly, when handling unexpected elements. Those components require iteration to handle them economically. Without cycles, they emerge eventually. When they do, an organization’s actionable window is frequently closed. Most institutions do not have infinite time to create, build, and deploy a strategy. For example, a team can wait months or years to complete a single version of its process for creating a draft board. When that iteration is complete, that group discovers it is flawed, leading to a need for another variation. With each instance taking such a long time, the company cannot see the benefits of its work. To see those advantages, it needs an approach faster than a single-pass one. An iterative technique is more efficient. Cyclical methods allow for adjustment based on new information. Modifications can be made by a business to a version, since each one does not have to be a completed product. That organization can use a feedback loop to handle unexpected elements. The process’s iterations allow an institution to manage unanticipated components more efficiently than it otherwise would.

A cyclical methodology might be comparatively economical, but it has difficulties of its own. The technique’s efficiency depends on the size of its cycle. A loop is more cost-effective to a company, when it is paired with incrementalism. For example, a business could build its draft boar to near completion, or it could build a tiny portion of it. Small increments allow an organization to get feedback faster. That new information allows it to adjust its list more quickly than it could with larger steps. Big chunks can require rework, if new insights invalidate previous assumptions. A tinier piece makes less impactful predeterminations, reducing the upper bound on the size of the effort an institution must redo. Those revisions create inefficiencies. A company needs incrementalism to decrease them, making cycles efficient.

Iterations allow a business to handle unanticipated elements, including problems. Those aspects and issues are managed more economically by cyclical methods than by single-pass ones. Yet, iterative approaches are only made cost-effective to an organization, if they are paired with incrementalism. An institution can build and deploy a strategy that meets its objectives, if it employs those techniques. How to use those methods specifically is described in future articles.

Follow ExperTech Insights on Twitter and subscribe to its Substack newsletter.

This article originally appeared in the Strategy Construction Journal hosted by ExperTech Insights.

--

--

Collin Rusk

Software Architect with a specialty in enterprise systems and founder of ExperTech Insights (https://expertechinsights.com)