Selection

Overview

What selection asks

• Selection runs at the Allocate stage of a Nutropic engagement, immediately after Map. With each in-scope workflow mapped in cognition mode, specification mode or both, selection assigns each workflow exactly one of the four cognitive patterns and records the reasoning behind the assignment. The discipline rests on three commitments: selection is per workflow rather than per organisation or per tool, it lands on exactly one pattern per workflow, and it produces an explicit reason that travels with the allocation. Those three commitments are what make selection auditable rather than a matter of consultant taste.
• Most workflows resolve cleanly when a small number of diagnostic questions are asked honestly. Where does decision-making responsibility need to sit during the work? How well can the behaviour be specified before it begins? Where does the human need to be while the work runs? What triggers the work in the first place? These four questions draw on the framework's Decisions, Specification, Supervision and Initiation aspects, with Decisions doing the load-bearing diagnostic work. The remaining aspects fall out as consequences. Composite workflows complicate the picture: an outer pattern constrains what inner patterns it can host.
• What good selection produces is not a pattern label alone but a reason that cites the signals and survives the consultant leaving the room. The reasoning is the artefact that allows the allocation to be defended, audited and revised when the work or its operating context shifts. The seams between patterns are where most allocation calls have to be defended. The discipline names its own antipatterns too: pattern-pushing the practice's preferred shape, pattern-shopping across stakeholders for the answer they want, defaulting to Partnership or Utility without reasoning, and pattern-as-technology-choice in which the tool already procured determines the call. Selection's value is precisely that it refuses these shortcuts.