Transformation capacity in 2026: plan according to available teams rather than cumulative ambitions

The subject “Transformational capacity” must lead to proof, not just to deployment: the expected effect must be measurable and reversible.
Frame the “scarce skills” point, control the “business load” point, then decide with an explicit reference measure.

1. Key figures

These benchmarks limit the decision to planning by real capacity; they don't take it for you. A published value describes a precise perimeter, a date and sometimes a population different from yours. Read it as a constraint to be tested, not as the promise of an automatic effect. This benchmark does not decide.

When an arbitrage is disputed, the date of the source is checked: for this topic, the first source leads to the following operational reading: “The purchase price is not enough to compare two technological options. » The second reference in the table must also be compared to your perimeter and a local measurement. This distinction between external reference and local measurement protects the analysis against easy extrapolations.

2. Read the sources without overinterpretation

As long as doubt remains, a responsible function is named: a source is useful when a reader simultaneously understands what it asserts, the scope it covers, and the limit of extrapolation. The five benchmarks below are therefore reread as decision markers, never as causal promises.

For the “planning by real capacity” scope, external data can only be used to decide if its scope, date, unit and limit are explained. The review should separate what the source establishes, what the team infers, and what a local test still needs to demonstrate.

Concretely, the proof sheet preserves the organism, the title, the URL, the date of consultation, the population, the unit, the method and the reservation of interpretation. It then indicates the decision that the benchmark informs and the local observation capable of contradicting this benchmark. In this file, attach this register to “rare skills” and entrust its review to “General Management”. Data without a documentary owner ages silently; data with a revision condition remains controllable and can be cited without losing its context.

2.1. Benchmark 1

The source GOV.UK — Choose the right tools and technology locates the terminal “4 obligations” in the field “public digital services, transposable principles”. It provides an external reference to the diagnosis; it does not replace either a local reference measurement or the analysis of exceptions. The context requires the proof.

2.2. Bench 2

The “2 phases before engagement” milestone, published by GOV.UK — Commercial off-the-shelf products, falls under the “purchase of digital products and services” scope. It helps to formulate a testable hypothesis, without transforming an external value into an automatic objective. The answer depends on the cycle.

2.3. Bench 3

GOV.UK — Working with contractors documents “5 evidence”. The exact range is shown in the previous table; keep it when comparing this data to your own operations, populations and periods. Exceptions reveal maturity.

2.4. Benchmark 4

GOV.UK — Digital, Data and Technology Playbook provides the indication “3 output assets” here. This information informs a choice; it does not, by itself, demonstrate that the same effect will appear in your context. The risk is concrete.

2.5. Bench 5

The GOV.UK reference — What each role does publishes “5 key roles”. Before making a decision, check the date, the population covered and the possibility of replicating the measure locally. The threshold remains explicit.

3. Reusable citation sheet

When a dependency changes, measurement uncertainty remains visible: a robust citation must be able to be repeated without losing its author, its date, its scope or its limit. The sheet below isolates these elements and links them to a specific decision; it prevents a correct figure from becoming misleading after extraction from its context.

4. Introduction: framework the primary risk

Teams see “scarce skills”, then “job load”, but they do not always connect these signals to the chosen measure. The “dependencies” point becomes a local setting and “work in progress limits” becomes a late check.

Concrete risk takes the following form: a schedule that affects the same people several times. This problem cannot be corrected either by an activated option or by an additional dashboard; it requires a perimeter, a person responsible and contradictory proof.

Our position is therefore clear: the system only has value if the announced effect is observable. The comparison must relate to the situation before the change, then to the same segments after the test. The average can deceive.

5. Actors and responsibilities

This distribution avoids confusing execution and responsibility. The first operational responsibility falls to the “General Management” function; the “Professionals” function provides separate control. The decision is only defensible if each actor knows what it measures, what it authorizes and what it takes back when the accepted limit is crossed. The perimeter is authentic.

6. Definition: planning by real capacity

In this guide, the scope “planning by real capacity” combines the points “rare skills”, “business load”, “dependencies” and “limits of work in progress”. The objective is to obtain a portfolio compatible with the skills and the load of change; the decision is based on critical load and throughput of completed results.

On this scope, the scope remains explained: the definition is therefore operational: it names the components, the desired effect, the indicator and the limit. A reader can quote it without having to reconstruct the meaning from the rest of the page. The compromise appears clearly.

7. Why the subject becomes structuring

During the review, the residual risk is accepted: the sources converge on three limits: 4 obligations, 2 phases before commitment and 5 proofs. They do not describe a universal average; they specify thresholds, obligations or operating conditions. In the present case, the third source leads to the following operational reading: “Transfer capacity counts as much as delivery capacity. »

This reading transforms the figures into decision questions: what perimeter do they cover, what uncertainty remains and who can act when the measurement goes beyond the accepted threshold? When planning by real capacity, this responsibility conditions the desired effect. The decision can be reviewed.

8. Compare four levels of engagement

Concerning planning by real capacity, the comparison does not indicate a universal winner. It makes visible the cost of an absent proof, an overly simple driver or a premature extension. The right level depends on the criticality of the flow, the quality of “business load” and the concrete possibility of resuming “work in progress limits”. The measurement precedes arbitrage.

9. Recommended methodology: seven verifiable steps

Applied to planning by real capacity, the following method is part of good public and operational practice. It is not presented as a proprietary method of Logiks: its value comes from the order of controls and the possibility, for a third party, to verify each deliverable.

9.1. Formulating the decision

Expected action: describe the expected result and relate it to “rare skills”. Start on a perimeter where the team can still get back. The expected proof relates to the decision actually made and the value which justifies it; record it in a note cadrage which names the decision, the limit and the person responsible.

9.2. Measuring the starting point

After going into production, the observed field remains stable: the work consists first of observing the decision indicator before any modification. Do not retain an ideal demonstration or an overall average: observe the initial situation and its variations between segments. The useful deliverable is an initial measurement dated and broken down by useful segment.

9.3. Trace Critical Path

At this stage, it is necessary to link “business load” to the data, teams and dependencies concerned. Involve the person who handles the exceptions, then compare the result to the exceptions encountered by the teams operating the system. You must be able to give a map of exceptions, dependencies and owners to a decision-maker absent from the project.

9.4. Laying down safeguards

Here, the action consists of framing “dependencies” with limits, rights and a recovery procedure. Run the check on a normal case and a degraded case, keeping the limits, action rights and rollback possibility as criteria. The concrete output takes the form of a control matrix that makes cost and reversibility visible.

9.5. Test the difficult case

This step transforms intention into control: experiencing “work in progress limits” in a representative scenario, then in a degraded scenario. Measure what actually changes in nominal behavior, induced failure, and recovery quality, including human recoveries. Document everything in an account of the nominal scenario, failure and human recovery.

9.6. Build evidence

In the presence of a third party, the incident is subject to review: to move forward without hiding the deferred cost, you must compare results, errors, interventions and full cost at the starting point. Compare before and after on the discrepancy between the initial promise and the recorded facts, then have a file of logs, discrepancies and decisions readable by a third party reread by an actor who did not design the test.

9.7. Decide and Review

Because the context evolves, human recovery is tested: expected action: assign the review and follow the measurement according to an explicit cadence. Start on a perimeter where the team can still get back. The expected evidence relates to the threshold that triggers a correction, an extension or a halt; record it in a review rule with correction and stopping thresholds.

10. Logik tips: proof, mastery and reversibility

Our priority is the following risk: a schedule that affects the same people several times. Start where this fragility already produces an expectation, a loss, or a contested decision; the prestigious perimeter can wait.

Faced with a gap, the hypotheses remain rereadable: keep the reference measurement at the level where a team can act. A quarterly average does not replace an observation by course, by cohort or by type of exception; the marker must remain actionable.

Treat “rare skills” as a documented decision. A manager, a hypothesis, a limit and a review date are better than an adjustment whose origin no one knows.

Experience "dependencies" with "work in progress limits", then with a degraded recovery. The test should reveal operation and operating cost, not just confirm that the demonstration holds up.

Only extend the system if the observed facts support the desired effect and if “business load” remains controllable by a person outside the project.

In this file, the recommendations express a judgment of sequence: make the risk observable, test the hypothesis relating to “dependencies”, then commit the resources. Sophistication comes after the demonstration of the announced effect; it does not replace it. The roles are distinct.

11. Decision grid

The grid does not automatically produce arbitrage on real capacity planning. On the other hand, it forces teams to show their assumptions about “rare skills”, their thresholds and their responsibilities; a disagreement is then explicit and can be resolved. These mistakes are costly.

12. Frequent errors

12.1. Consolidate activation and result

Activating “rare skills” does not prove that the expected effect is achieved. This error shifts the debate towards the tool while the decision concerns an observable change.

12.2. Optimize the first available indicator

At the next milestone, the result keeps the same meaning: a convenient proxy can improve while the decisive measure deteriorates. Link each signal to a decision and a guardrail.

12.3. Ignore exceptions

Between two reviews, the comparison maintains a previous state: the nominal path often hides the fragility described above. Test a borderline case, a failure and how the team regains control.

12.4. Leave an addiction without an owner

When “business load” is everyone’s responsibility, no one decides on the incident or the cost. Assign the decision before deployment.

12.5. Present risk as a formality

Documenting “dependencies” without correcting the system produces facade compliance. The record must show a check performed and its result.

12.6. Extend without exit rule

If “work in progress limits” does not allow a decision to be made, the pilot continues by inertia. Set continuation, correction and termination thresholds in advance.

13. Action Plan 30 / 60 / 90 days

13.1. Days 1 to 30: establishing the starting point

• describe the decision, the scope and the person responsible for it;
• record the initial value of the indicator before any modification;
• inventory dependencies and their exceptions;
• write the main risk and its detection condition.

Without a designated owner, the signal is broken down by segment: the first phase serves to make the disagreement visible. At thirty days, management must know the baseline measurement, the missing data and the specific case on which progress will be judged.

13.2. Days 31 to 60: testing the critical path

• implement primary control over a representative flow;
• test the recovery in a normal then degraded situation;
• record errors, human interventions, delays and costs;
• compare the observations to the initial scenario.

Outside of the nominal scenario, the changes are versioned: this pilot does not only seek to demonstrate that the technology works. It must establish whether the system advances the selected indicator without shifting a disproportionate burden towards the operation, users or a supplier.

13.3. Days 61 to 90: decide and organize the continuation

• consolidate the evidence and have its limitations reread;
• assign each recurring control to a named function;
• confirm the next review date and discharge procedure;
• extend only if the facts support the effect initially announced.

Depending on the hypothesis retained, the budgetary limit is noted: at ninety days, the initial hypothesis must be demonstrated or refuted. Three decisions remain legitimate: extend, correct or stop the perimeter; continuing without a threshold does not constitute a fourth option.

14. FAQ

14.1. How to define planning by real capacity?

This is a decision framework applied to planning by real capacity. The approach links “rare skills” to “dependencies” and “work in progress limits” controls, with a reference measurement, managers and an exit rule.

14.2. What to start with?

Once the baseline is established, the decision to stop remains possible: start with a real decision, a reference measurement and an already observed manifestation of the main risk. The tool comes after this cadrage.

14.3. What budget should be retained?

During the audit, the fallback procedure is accessible: add preparation, integration, operation, control, training, incidents and exit. Compare this full cost to the expected value, not just the license or campaign price.

14.4. How long should the test last?

The test must cover a complete measurement cycle and at least one exception related to “dependencies”. Its duration derives from this observation, not from an arbitrary standard.

14.5. When to scale?

Scale up when progress remains stable, “work in progress limits” are controlled, and responsibilities, costs and exit conditions are documented.

15. Conclusion

With incomplete data, external dependence is documented: the decision is solid when a common measure links technical, business and financial choices. The number of options activated is less important than the ability to explain discrepancies, deal with exceptions and reverse a choice that has become costly.

The pivot is simple: the “planning by real capacity” project must no longer be a project to be delivered, but a capacity to govern to produce the announced effect. Control remains human.

16. Main sources

• GOV.UK — Choose the right tools and technology — consulted on 11 July 2026 — public digital services, transposable principles.
• GOV.UK — Commercial off-the-shelf products — updated on July 4 2025 — purchasing digital products and services.
• GOV.UK — Working with contractors — accessed 11 July 2026 — digital services teams.
• GOV.UK — Digital, Data and Technology Playbook — accessed on 11 July 2026 — digital purchases and contracts.
• GOV.UK — What each role does — accessed on 11 July 2026 — digital product and services teams.