Services emerge when a process is constrained within defined boundaries. We use language to define the boundaries of our Services. Not just any language, but carefully chosen taxonomies, forged and hardened like machine tools.
Typically a service, or “Value Stream”, is a component of a larger system, modeled as a series of steps, a boundary delimited fragment, where each step is a key waypoint on the road toward some definite objective.
A Service Specification is how we express the plan, a means to codify the creation of value for the business.
Successful implementation of a strategy depends on being able to communicate not just the goal, but the plan.
Drying out ambiguity of intent is essential. If we had a method to describe the plan in a consistent way that was sufficiently clear to allow a team with appropriate competencies to execute against it, we could think of it in terms of Strategy as Code.
Douglas Hawkins — "Survey ribbon on a tree trunk"
Markus Spiske — "Hacker binary attack code — Canon 5d Mark III and analog Leica APO Macro 100mm lens"
Siarhei Plashchynski — "Post Box"
Gan Khoon Lay — "Agile stick figures"