STR.13 - Choose and Maintain Strategy Methods

Type: Method pattern Status: —

STR.13:1 - Problem frame

Use this when a strategic practitioner must choose, retain, adapt or retire a way of doing strategic work, or when later users cannot recover which method variant fits their situation and what supports that judgement.

A team may run a large scenario workshop for a choice already settled by an established constraint. Another may use a single forecast where materially different futures reverse the preferred direction. A third has useful experience in old documents but cannot tell which assumptions, participants or permissions made it applicable. The problem is not necessarily a missing technique. It may be the choice of technique, its explanation, available support or the loss of the reasons for using it.

Strategy is the wider practice. This pattern governs the strategic-method repertoire: usable ways of framing, generating, comparing, committing and reconsidering under particular conditions. A Method is a reusable way of doing; its description, a template, a tool and one performance are different things.

Distinguish that repertoire from the subject’s way of obtaining its contribution. Finding how SensorCo could explain inspection errors is an STR.6 option-construction question; deciding whether the team’s search routine can discover credible ways is a question here. If even the worthwhile contribution is unsettled, STR.5 supplies that earlier entry. Improving the strategy practitioner’s Method does not itself obtain the customer’s diagnostic result.

The practical gain is a supported present choice and enough retained reasoning for a later practitioner to reuse or reject it intelligently. Keeping the present method can be the complete result.

Do not use this pattern merely because the annual planning date arrived or a new technique is fashionable. Use the direct pattern for an ordinary strategic decision when the current method already suffices. Use STR.15 for an actual cultural-continuation question, and the direct learning or organization-change Method when capability, assignment or access is the missing result.

STR.13:2 - Problem

Method selection often substitutes familiarity, novelty, conformance or one favourable outcome for practical worth. A method can be coherent and usable yet demand more effort or capability than the receiving decision warrants. Another can appear expensive while preventing a consequential error that a lighter alternative misses.

Maintenance compounds the problem. Every edited template becomes a new method, while a real change in entry or stop rules disappears into a document revision. Evidence from one team is silently attached to another variant or generalized to all strategy work.

A useful repertoire must therefore preserve both situated comparison and semantic identity. It must help someone decide what to do next, not merely catalogue names.

STR.13:3 - Forces

STR.13:4 - Solution

Start from the strategic decision the method must help, compare feasible alternatives at the strength of the available evidence, and maintain only the distinctions needed for later choice. ME.14 supplies the situated worth comparison; ME.15 supplies variant, provenance and reuse maintenance. Reuse adequate results from those patterns instead of repeating their work.

STR.13:4.1 - Name the receiving problem and the needed first result

State the strategic question, decision holder, horizon, uncertainty, stakes, available capability and support, current constraints and the last useful decision time. Name the first result that would help: a bounded frame, discriminating futures, comparable whole options, a sufficient cost comparison or a supported decision to stop.

Ask what is actually failing. The team may not know how to construct alternatives, may misunderstand an instruction, or may lack access to a qualified cost estimate. These require different contributions. A better method description cannot itself provide customer permission or shared capacity.

Recover the present method’s operations, entry and stop rules, and the evidence for its current use. An ordinary existing account can suffice. Do not begin by commissioning a new method architecture or strategy platform.

STR.13:4.2 - Compare serious current alternatives

Include the current method, a feasible lighter or stronger alternative, a situation-specific branch and stopping the proposed method change where those can affect the choice. A support or capability change can be a serious rival to replacing the method.

For each alternative compare:

• the strategic result it can support and its material blind spots;
• the uncertainty and comparison basis it can represent responsibly;
• time, cognitive effort, coordination, tools and maintenance;
• required capability, access, assignments and authority;
• affected people, exposure, displaced work and reversibility;
• evidence strength, applicability limits and the remaining gap.

Keep observed performance, estimates and structural reasoning distinct. A completed workshop is not evidence that a better strategic decision followed. An adequate comparison may rely on credible estimates and constraints without pretending to have causal evidence.

Use ME.14 to return a situated keep, revise, replace, branch or stop, or a retained set with its unresolved limitation. A supported current course can coexist with an unresolved stronger claim. Further testing is selected only when its attainable decision contribution warrants the whole burden under C.11.DUA.

STR.13:4.3 - Change the right thing

Identify whether the proposed change alters reusable operations, dependencies, entry or stop rules, or only their description, representation or support. A clearer sentence is not automatically a new Method; a reordered decision rule can be a real semantic change even if its description needs only one sentence.

For a proposed variant, preserve the earlier way or source account, what is retained and changed, why it was changed and the intended situations. State which evidence for the earlier way still applies and what remains unsupported for the changed one. A traceable entry can preserve the proposal as a candidate and complete the present maintenance task.

When later users need to distinguish an identified FPF U.Method from a candidate proposal, use ME.15’s independent admission step under A.3.1. Here admission means establishing a reusable way of doing, the kinds of participants it is for, its applicability and preconditions, intended result or preserved condition, and limits or stops. Establish that basis for the changed way itself or retain its candidate status. ME.14 answers the separate practical question of whether using or changing the way is worthwhile for this strategic decision.

For a non-variant change, name the actual object, the affected claim or edition and the needed maintenance action. Repair an ambiguous instruction where the ambiguity occurs and inspect its affected uses.

Obtain the relevant Method Engineering result when the open question is how to construct the method, whether its operations are coherent or whether it fits the intended conditions. Keep that answer distinct from section 4.2’s comparison of its practical worth.

STR.13:4.4 - Preserve a repertoire that supports the next use

For each retained entry, make the problem, first useful result, method or candidate status, situation conditions, serious alternative and retention reason easy to recover. Keep the evidence and its limits attached to the exact semantics, performers, support and window they concern.

Where derivation matters, ME.15 preserves the relationship between variants and the separate descriptions and support editions. Where a downstream use needs an explicit set result, use G.5’s applicable selection or declaration contribution. A declaration of an already selected set does not repeat the choice, admit its members or commission their use.

An existing working note, example, searchable discussion or method description may preserve all that is needed. Create a new card, diagram or archive only when it improves an actual retrieval or reuse problem enough to warrant maintenance.

Make retirement precise. Removing an entry from current offered choices need not erase its history or an adequate use elsewhere. State the conditions under which it should be reconsidered, not a universal expiry date.

STR.13:4.5 - Refresh affected uses and close the present method decision

When a source, alternative, capability, support condition or evidence claim changes, identify which current repertoire use depends on it. Use G.11 for the currentness or scoped-refresh question and A.10.1 when discovering several affected actual source uses is necessary. Neither produces a new strategic-method worth judgement by itself.

Retain independently adequate entries. A source update can finish with a repaired reference when meaning and applicability are unchanged. A failed transfer or changed constraint can require a new situated comparison or a narrower applicability claim.

Return what is kept, changed, branched or stopped, why, for which receiving work and under which limits. A qualified repertoire entry or a justified keep can close without another trial. If the method is adequate but is not transmitted, enacted or recognized, pass that distinct question to STR.15 rather than claiming that the worth comparison established cultural adoption.

STR.13:5 - Archetypal Grounding

These are constructed teaching cases. Estimated burdens illustrate decisions, not measured comparative effectiveness.

STR.13:5.1 - SensorCo selects the analysis its current choice needs

SensorCo is considering device-only activity and service directions over twelve months. Several plausible futures can reverse the preferred commitment. Its team can use a qualified three-future comparison from STR.4 and STR.9, including whole service costs, permissions and the viable device rival. A single expected sales figure would conceal the decision’s material uncertainty.

The method question changes if an authoritative restriction establishes that the service commitment under consideration is unavailable throughout the entire decision window. Suppose the restriction is sufficient for that eligibility conclusion and no feasible service alternative changes the present choice. Repeating the full scenario exercise cannot make that excluded commitment available.

The team then uses the established constraint and direct comparison to support the present device-only decision. It preserves the prior scenario reasoning for its qualified uses and possible later conditions. It does not infer that scenarios are generally worthless or that the company should never consider another service direction.

A useful repertoire can retain the following distinctions without inventing a universal ranking:

The four-day preparation already authorized in the connected case remains a bounded allocation. A method preference does not enlarge it. If preparing a stronger comparison would exceed that allocation, the team must compare a smaller sufficient result, a different obtaining arrangement or a separate authorized decision.

STR.13:5.2 - A wording repair and a candidate branch

A strategy note says “approve the portfolio” where the established method already distinguishes retained alternatives from jointly authorized work. Readers repeatedly mistake a shortlist for allocation. The maintainer rewrites the instruction to name the actual result and checks the affected examples. This is a description repair, not a new method variant.

Separately, the team’s present routine begins every direction inquiry with a full scenario workshop. It proposes a reusable change: test decisive eligibility constraints first, while retaining scenario work when it can still distinguish feasible choices. That changes an entry or ordering rule. It is a candidate branch whose preserved and changed semantics, intended situations and limits should be explicit.

The word change supplies no evidence for the new branch’s effectiveness. A later local use can supply an occurrence with its conditions; it does not by itself establish transfer to a different team, decision or authority arrangement.

STR.13:5.3 - Retrieve the reason, not just the old answer

A practitioner retrieves a five-year-old device/service comparison. It contains a useful explanation of why incident support and data rights mattered. Its numerical estimates and permissions concern the earlier situation.

The practitioner retains the explanation and obtains the current conditions needed for the new choice. An accessible note pointing to the relevant reasoning can solve the memory problem. Rebuilding an archive or repeating the old recommendation is unnecessary.

STR.13:6 - Bias-Annotation

Method specialists may overvalue analytical sophistication; incumbent teams may overvalue familiarity. Compare each against the same receiving result and credible full burden, including the best use of displaced effort.

A polished description can also hide weak transfer evidence. Preserve candidate status, contextual limits and the distinction between a method’s plausibility, actual use and established contribution.

STR.13:7 - Conformance Checklist

• The method question names a receiving strategic decision and useful first result.
• Current feasible alternatives include a sufficient incumbent or simpler course.
• Result, uncertainty, burden, capability, support, authority and reversibility inform comparison.
• Observations, estimates, contribution and causal claims retain their different reach.
• A semantic variant is separated from description, support and local Work changes.
• Retained reasoning supports actual later choice without automatic new record machinery.
• Candidate status and evidence remain bound to their exact subject and conditions.
• Refresh reaches affected uses without treating all entries as invalid.
• A justified keep, bounded repertoire result or stop can complete the question.

STR.13:8 - Common Anti-Patterns and How to Avoid Them

Annual method replacement. A date or trend substitutes for a receiving problem. Retain an adequate method until a material choice warrants comparison.

More analysis is always better. A workshop continues after a sufficient constraint settles the decision. Compare attainable decision benefit with its full burden.

New template, new Method. A wording or layout revision creates false variants. Recover changed reusable semantics before naming a branch.

Local success becomes a universal rule. One favourable occurrence erases performer, support and situation limits. Preserve what the evidence actually reaches.

Memory without a usable reason. An archive retains answers but not their conditions. Make the relevant rationale and current-use limits recoverable.

STR.13:9 - Consequences

Practitioners can select methods by the strategic result they need and explain why a lighter, stronger or different branch is worthwhile. Useful experience survives without every document revision multiplying the repertoire.

The result may reveal that the real missing contribution is support, capability or permission. It also leaves broad effectiveness claims unresolved when the present evidence supports only a bounded choice.

STR.13:10 - Rationale

Strategic methods operate under different uncertainty, stakes, capabilities and authority. A situated repertoire preserves useful plurality without treating every method as equally suitable or searching for a universal winner.

Maintaining meaning and evidence separately from visible artifacts lets descriptions improve while genuine semantic changes receive the attention they need. Preserved reasoning supports later choice; a catalogue alone does not.

STR.13:11 - SoTA-Echoing

How should a strategic method earn its place? Adopt ME.14’s situated comparison of domain contribution, whole burden and current alternatives, rather than equating fit, popularity or task completion with worth. Sections 4.1–4.2 make continuation and a lighter sufficient method serious rivals. The contrast between a single forecast and uncertainty-sensitive judgement draws on Lempert and colleagues’ 2024 analysis and Rapp, Olbrich and Packard’s treatment of judgement under uncertainty. These inform the comparison question; they do not prove a universal strategy-method ranking.

What should a repertoire preserve? Adopt ME.15’s semantic-variant and evidence distinctions. The pattern also addresses how reasons, alternatives and criticism can be lost between people and tools. Sections 4.3–4.5 and cases 5.2–5.3 favour a retrievable qualified reason over automatic new variants or a larger archive. The repertoire retains several Methods and lets practitioners revise them as their uses change. Reopen the repertoire decision when a changed alternative, semantic rule, capability, source or supported use changes the situated comparison.

STR.13:12 - Relations

• STR.1–STR.12 and STR.14 supply receiving strategic questions and actual method-use experience; this pattern does not repeat their domain decisions. STR.5 develops an unsettled contribution and direction; STR.6 searches for and constructs the subject’s obtaining ways. This pattern instead chooses or improves the Methods used to perform that strategic work.
• ME.14 supplies situated practical worth; ME.15 maintains variants, candidate lineages, provenance and reuse.
• G.5 supplies an applicable selection or declaration result when a downstream set use requires it.
• G.11 governs currentness and scoped refresh; A.10 and A.10.1 govern source reliance and affected-use discovery where needed.
• C.11.DUA governs a proposed further evidence demand by its attainable contribution and whole burden.
• STR.15 governs actual cultural continuation; direct organization-change and human-capability Methods supply their separate needed results.

STR.13:End