Library / Strategy Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:30:10 UTC

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.