Operating Concept

Value Increments

The smallest piece of an initiative that produces a measurable business outcome on its own. The unit that lets a portfolio plan in months instead of years and reclaim the outcome value most organizations leave on the table.

The Problem Value Increments Solve

Most organizations fund strategic work in boulders.

A multi-year initiative gets approved. Eight months in, no business outcome has landed. The phase-gate review finds the work is on schedule and on budget, so funding continues. At month fourteen, a market shift makes half the original case obsolete, but the initiative is two-thirds complete and politically expensive to stop. At month twenty, the system finally ships. By then the business case has been updated to match what was actually delivered.

This is not a delivery problem. The teams executed. The problem is on the strategic side, in how the work was sized, funded, and governed before any team touched it.

Boulder-sized initiatives quietly impose three costs.

They forfeit outcome value the organization could have captured earlier. A twelve-month initiative bundling three measurable outcomes, each worth a hundred thousand dollars per month in operational expense reduction, looks identical on the funding slide to the same three outcomes delivered as three separate increments. The funding-slide view is wrong. If the first outcome could ship in month three as a stand-alone increment, the organization captures nine months of that outcome’s value, nine hundred thousand dollars in this case, assuming the outcome value stabilizes shortly after release. The capital was already committed. The outcome window is what was lost.

They delay decision-making until the cost of changing direction is prohibitive. A boulder produces no measurable outcome until it lands. Until then, the only honest answer to “is this working?” is “we’ll know when we ship.” By the time the answer is in, the budget is mostly spent and the political cost of stopping is higher than the cost of continuing on a known-bad path.

They consolidate accumulated debt at the portfolio level. When investment decisions get made on activity and schedule rather than outcome, delivery teams compensate for upstream funding decisions they cannot change. They cut quality to hit dates, take on technical and process debt, and paper over dependencies that should have been resolved upstream. The portfolio’s investment discipline is what shapes what teams can actually deliver. When the upstream side runs on year-shaped bets, the downstream side runs on heroics and debt.

A value increment is the unit that addresses all three.

What a Value Increment Is

A value increment has four properties.

It produces a measurable business outcome. Not an activity completion. Not a milestone. An outcome the business already cares about: revenue protected, operational expense reduced, customer cycle time cut, a new capability accessible in production. The outcome is concrete enough to count.

It is the smallest piece that produces that outcome on its own. If you can slice it smaller and still have an outcome the business recognizes, you should. If you cannot, you have found the increment.

It is owned by a single accountable group. The increment is a unit of investment, not a coordination challenge. If shipping it requires capacity from four teams across four products, that is a property the portfolio has to plan for, not a problem the increment owner can solve.

It has explicit acceptance criteria tied to the measurable outcome. Specific, testable, unambiguous. Format is secondary. The requirement is testability. If the increment ships without measurably moving the named outcome, the increment did not land, regardless of what was technically delivered.

The duration of an increment is not fixed. Some take six weeks. Some take six months when the work cannot be sliced smaller and still produce something the business can use. The slicing discipline is to find the smallest unit that still produces an outcome, not to fit every increment into a uniform time box.

Three Types of Value Increment

The category matters because each type carries a different acceptance pattern, a different review cadence, and a different relationship to the rest of the portfolio.

Customer-facing value increment. The business outcome lands with an external customer. New capability accessible in production, conversion rate moved, customer-perceived cycle time reduced, a churn pattern interrupted. Acceptance criteria reference customer-observable behavior or business-metric movement. Review cadence is tied to when the outcome becomes measurable in the customer surface.

Technical value increment. The business outcome is internal but measurable. An automated regression suite that cuts release verification cycle time from two weeks to two days, freeing engineering capacity per release. A platform consolidation that drops infrastructure cost by a named amount. A data-pipeline replacement that enables three downstream initiatives that were previously blocked. The criterion is the same. The outcome is measurable and the business recognizes it. The audience is internal.

Innovation increment. The work tests a hypothesis. Will a unified operational core actually reduce per-acquisition integration cost the way the business case claims? Will the new technology stack support the throughput we are assuming? Acceptance criteria reference what the hypothesis claimed and what the experiment will measure. The outcome is the evidence, not the rollout. A successful innovation increment may produce a clear “no, do not pursue this further,” and that outcome is as valuable as a “yes, scale this.”

All three types live in the same portfolio backlog. The portfolio carries a mix. Most multi-year initiatives carry a hypothesis worth testing as an innovation increment before the larger investment commits.

The Requirements Hierarchy

Value increments sit inside a four-level hierarchy that connects strategic outcomes to executable work.

Initiatives sit at the top. An initiative supports one of the organization’s four to six enterprise strategic outcomes. Initiatives carry intent. They do not carry a frozen specification. The work the initiative will produce is identified, refined, and re-identified over time as value increments emerge.

Value increments sit below initiatives and are the execution unit of the strategic portfolio side. They are intent-based and outcome-focused. They are created and managed on the portfolio side. Each increment names a description, a set of measurable outcomes, and testable acceptance criteria for each outcome. The discovery process for an increment starts at the description and the outcomes, then refines the acceptance criteria until each outcome has a concrete, testable check attached. Specific, unambiguous, verifiable. Testability is the framework requirement; format is a secondary choice. Scenario-based formats (Given / When / Then) tend to work well, but any testable convention satisfies the requirement.

Features sit below increments and straddle the line between the strategic portfolio side and the tactical delivery side. A feature is an intent-based specification of a piece of work that supports an increment’s acceptance criteria. Depending on the organization, features may be created and managed primarily on the portfolio side (where they decompose increments into supporting work that can be sequenced for delivery), on the delivery side (where teams shape them against current capacity and constraints), or in collaboration across both sides. The placement is organizational context, not framework prescription. What is invariant: every measurable outcome has at least one feature supporting it, and every feature traces back to at least one measurable outcome. If a candidate feature cannot be tied to an outcome, the feature does not get built. The connective tissue is enforced at intake, not discovered at review.

Stories sit below features and are the execution unit of the tactical delivery side. Stories carry their own testable acceptance criteria. Every feature decomposes into stories that, together, satisfy the feature’s acceptance criteria.

The hierarchy is one specification per increment, in the language of business outcome rather than the language of activity. The increment is a strategic investment unit, not a requirements artifact.

Just-in-Time Discovery

A portfolio backlog can hold dozens or hundreds of identified value increments. Almost all of them are placeholders. Discovery is invested only in the increments the organization plans to start in the next one to two quarters.

The top of the portfolio backlog gets full discovery treatment: description refined, outcomes named, acceptance criteria written. The rest stays as placeholders until the planning horizon brings them forward.

The payoff is not just effort saved. It is decisions deferred until the information to make them is available. An increment refined eighteen months before it will be worked is refined against assumptions that will be wrong by the time the work starts. Refining it just before the work begins means refining it against the conditions the work will actually meet.

Quarterly Planning at the Portfolio Altitude

A portfolio backlog populated with value increments unlocks a planning rhythm most organizations do not currently have.

Quarterly planning becomes a real decision event. The body running the event has a candidate set of increments from the portfolio backlog, refined enough to commit to. It has a view of current capacity, including the capacity already committed to in-flight increments crossing into the next quarter. It has a view of cross-team and cross-product dependencies attached to each candidate increment.

Carryover work is accounted for first, against measured capacity. Available capacity is loaded to roughly eighty percent, reserving headroom for estimation imprecision and the unplanned work every quarter produces. New increments are pulled from the candidate pool against what remains. Cross-product increments that need teams not available are deferred. Higher-priority increments that need capacity another increment is currently consuming force explicit reallocation calls.

Many organizations already run quarterly events under names like quarterly business reviews or phase-gate reviews. Those events do not produce the same effect. They review a small number of large boulders and ask whether to continue funding them. Continue is the default answer. The events that matter are the ones that can pull a new increment in, push another out, and adjust the portfolio against current conditions. The unit being managed at the event has to be small enough for those moves to be available. The value increment is that unit.

A Worked Example

Big Bank acquired a regional bank several years back, integrated the customer-facing front end, and ran the back-office systems as a wholly-owned subsidiary on the regional bank’s original platforms. The acquisition synergies the original deal modeled never fully materialized. The platform separation kept duplicate functions, duplicate vendor contracts, and duplicate operational staff in place. A senior leadership change finally forced the call: fold the subsidiary’s back-office systems into Big Bank’s platforms and dissolve the entity into the main organization.

The first roadmap put the work on an eighteen-month schedule, broken into three phases with a phase-zero foundation in front. Phase zero stood up the joint integration team, provisioned environments, and established the data-migration tooling. Phase one absorbed the deposit and lending systems. Phase two absorbed wealth management. Phase three absorbed the supporting analytics, compliance, and reporting stacks. Each phase had sub-streams, and across the top of the chart ran a row of vertical milestone lines indicating where business value was supposed to land.

The phases were not phases. Look closer and each phase was a work stream that ran most of the eighteen months in parallel with the others. The milestones above them did not align to phase boundaries. The first milestone, the one the board cared most about, required slices of work from phases one, two, and three combined. The phase-shaped funding case was producing a misshaped delivery plan, and the people running the work knew it but had no unit of work small enough to act on.

The reframe ran horizontally and vertically. Horizontal: take each phase and identify the smallest discrete units of work it actually contains. Vertical: for each business outcome the program promised, circle the work across phases that has to come together for that outcome to land. The first business outcome required roughly thirty percent of phase one, twenty percent of phase two, and ten percent of phase three. That cross-phase slice is one value increment. Three to four months of work. It owns the first material outcome. The phase view does not name it.

Innovation increments lived alongside the value increments. The original plan assumed Big Bank’s platforms could handle every workflow the regional bank’s systems currently supported. For many workflows that was true. For others it was a hypothesis. The unconfirmed ones became explicit innovation increments: build a proof against the parent platform, test it against representative regional-bank traffic, decide go or no-go before committing the larger absorption capacity. A handful failed the test. That failure redirected investment toward building new functionality on Big Bank’s platform before the dependent absorption could proceed. The phase plan would have surfaced those gaps in execution. The increment view surfaced them while the alternative still had room to maneuver.

The team shape followed the unit of work. Where the phase plan implied splitting people seventy-five percent on the absorption work and twenty-five percent on their current responsibilities, the increment plan pulled them into discrete value-delivery teams aligned to the cross-phase slice they owned. The split-allocation pattern, well-known to fail, was no longer the default.

The phase view did not disappear. Board-level reporting still rolled up to it. The phases described how work was sequenced. The value increments described how the business measured progress. The two views coexisted, and the program continued to report against the phase plan to the executive audience that had funded it on those terms.

Big Bank had resisted moving its broader portfolio onto an increment-based operating model several times before. The cost of the change felt larger than the cost of staying with project-shaped funding. The subsidiary absorption became, in effect, a self-contained pilot of the operating model. The pilot was itself an innovation increment at the altitude above any single program, a hypothesis that running portfolio investment as increments would unlock faster outcome realization and tighter dependency management. The hypothesis cleared. The model is now spreading to the rest of Big Bank’s portfolio, on the strength of evidence rather than argument.

The phases describe how work was sequenced. The value increments describe how the business will measure progress.

What Value Increments Are Not

Not project chunks. A project sliced into smaller projects is still project-shaped: defined scope, defined deliverables, success measured by completion against scope. A value increment is outcome-shaped: success measured by whether the named business outcome moved. Two projects of the same shape and effort can produce different value increments depending on which one is anchored to a measurable outcome and which is anchored to a deliverables list.

Not features renamed. Features sit one level below value increments in the hierarchy. A feature is a piece of execution that supports an increment’s acceptance criteria. Treating features and increments as synonyms collapses the hierarchy and loses the connection between work and business outcome.

Not a substitute for strategy. Value increments operate inside an initiative that traces to a strategic outcome. The increment does not set the strategic direction. It is the unit that lets the strategic direction be executed in steps small enough to govern, fund, and adjust.

Not just a delivery technique. The slicing happens at the strategic side, where investment decisions are made. The work the slicing produces flows downstream to delivery teams, who execute against the acceptance criteria like any other work. The new discipline is upstream.

What Value Increments Are For

Value increments are the execution unit of the strategic portfolio side. They let a portfolio plan, fund, and govern strategic work in quarter-sized steps instead of year-sized boulders.

Paired with the Value Acceleration Process at the executive altitude, the value increment is the unit of work the engine acts on. The improvement backlog is populated with increments, not initiatives. The cost of being wrong is one increment cycle, not one fiscal year.

Paired with Latency Load, value increments are the lever that compresses the latency between strategic intent and measurable business outcome. The smaller the increment, the less Latency Load the work accumulates between funding decision and outcome realization. Outcome value the boulder model forfeits, the increment model recaptures.

Paired with the Three Barriers diagnostic, value increments are the operating unit that lets an organization act on Alignment Drift and Choked Flow at the portfolio altitude. Without an increment-sized unit, the portfolio cannot rebalance against drift or unblock flow without restructuring entire initiatives. With the increment as the unit, portfolio adjustment becomes a routine quarterly move, not an extraordinary intervention.

The framework names what is broken and the engine moves the organization through it. The value increment is the unit the engine works on at the strategic altitude.

The Value Acceleration Process. The engine that acts on the value increment at the executive altitude.

Latency Load. The operational cost the value increment compresses between funding commitment and outcome realization.

The Three Barriers. The diagnostic frame the increment helps act on at the portfolio altitude.

Requirements hierarchy. Initiative → Value Increment → Feature → Story. Value increments are the execution unit of the strategic portfolio side. Features straddle the line. Stories are the execution unit of the tactical delivery side. Every measurable outcome traces to at least one feature; every feature traces back to at least one measurable outcome.