Method is the system of conventions, specifications, skills, and policies that governs how an endeavor conducts itself.

Secondary intension

Something is method when it has all of:

  1. Codification: it is documented — as specifications, policies, skills, or other explicit artifacts. Uncodified habit is not method (it may become method through codification).
  2. Coherence: its parts relate to each other as a system, not as an ad-hoc collection of rules
  3. Prescriptiveness: it says how things should be done, not merely how they are done
  4. Revisability: it can be changed when it no longer serves the endeavor’s objectives

Distinguished from

  • Practice: the actual doing. Method is the score; practice is the performance. Method without practice is shelfware. Practice without method is improvisation.

  • Methodology: a methodology is a particular named approach to work (e.g., Scrum, Shape Up). Method may draw on multiple methodologies. Method is what this endeavor actually uses; methodology is what someone else designed.

  • Doctrine: in military usage, doctrine is the body of principles guiding action. Doctrine and method are close — but doctrine emphasizes principles and authority, while method emphasizes system and practice-orientation.

  • Specification: a specification defines a single convention (e.g., semiotic-versioning defines how versioning works). Method is the collection of all such specifications as a coherent system.

  • Policy: a policy is a single standing commitment (e.g., “reason constructively”). Method includes all policies plus the specifications, skills, and conventions that implement them.

In the semiotic framework

Method is the stable fragment of the agential semioverse — the configuration of norms, tools, and conventions that has achieved closure (the j operator). When method works and is practiced, it is invisible. When method fails to close under new conditions, closure pressure generates revision.

In this repository

The semiotic-* specification family constitutes the emsemioverse’s method:

  • semiotic-markdown — how files carry meaning
  • semiotic-specification — how conventions are documented
  • semiotic-versioning — how artifacts are versioned
  • semiotic-changelog — how changes are tracked
  • semiotic-project-management — how work is planned and tracked
  • semiotic-endeavor — how these cohere as a system