Rule-to-Route
A run starts when the organization decides who should get what, and how quickly. The processes here write the routing rules, implement them in the systems that deliver work, set and publish the response clock, watch what actually happens against it, and change the rules when the answer is consistently wrong. The stream owns the rule and the measurement rather than the conversation: whether an inquiry was any good is the judgment of whoever received it. Every rule here is readable by the people it routes to, because a routing rule nobody can see is indistinguishable from an accident.
vs/rev/rule-to-route v1The processes
The processes in this stream
Fix a Misroute
Starts withsomebody says work reached the wrong person
Ends whenthe work is with its owner and the rule carries the case
Activities inside
- Take in the Report of a Misroute
- Confirm It Went to the Wrong Person
- Hold the Clock Where It Is
15 activities · 53 blanks to fill · 2 human gates
Watch the Response Clock
Starts withthe reporting period closes
Ends whenthe promise and the result are published side by side
Activities inside
- Take in the Promise and the Window
- Name What Each Clock Covers
- Read Where the Times Come From
16 activities · 48 blanks to fill · 2 human gates
Write a Routing Rule
Starts withsomebody asks who should get this work
Ends whenthe rule is live, published and holding
Activities inside
- Take in the Routing Question
- Read How Work Is Routed Now
- Name Who Should Get What
17 activities · 61 blanks to fill · 1 human gate