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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:35:10 UTC

STR.5:4.3 - Make each proposed direction complete enough to challenge

Explain the intended contribution, recipient, reason it is worthwhile, way of providing it and supporting capability. Then name its consequential dependencies, resource demand and exclusions. Separate what is available from what would have to be obtained.

At this level, completeness means that a plausible critic can locate what would make the direction work or fail. It does not mean that every implementation task has been planned. STR.6 constructs sufficiently complete options, and STR.8 examines a missing capability or business-model condition.

Include a credible means of obtaining necessary contributions when the choice depends on it. An existing service, a commission, internal work or a human–AI arrangement may each be relevant. A purchased tool alone is incomplete when the direction also needs expert interpretation, access and incident response.

Keep the direction conditional when its support is unresolved. “Offer an accountable service if a permitted delivery arrangement can cover its full cost at attainable customer terms” is a usable proposal. “We have a platform, therefore we can offer the service” is not the same claim.