Signal-to-System
A run starts when the revenue organization needs something its tools cannot do, or when a tool it has stops earning its place. The processes here work out what is actually needed, evaluate what exists, run the security and procurement review, integrate the choice with the systems on either side of it, administer it once it is in, and retire whatever it replaced. Nothing here decides how the work is done, only what it is done inside. A tool bought without a process to run in it is the failure this stream exists to prevent, which is why every run names the process it serves.
vs/rev/signal-to-system v1The processes
The processes in this stream
Administer a Tool
Starts witha tool goes live under an owner
Ends whenthe tool is held, and its place is decided again
Activities inside
- Take On the Tool
- Set the Roles and the Permissions
- Open and Close Accounts
15 activities · 48 blanks to fill · 3 human gates
Choose a Tool
Starts witha need the current tools cannot meet is raised
Ends whenthe tool is chosen, reviewed and recorded against a process
Activities inside
- Take in the Need
- Name the Process It Serves
- Check the Stack for It
18 activities · 48 blanks to fill · 3 human gates
Integrate a Tool
Starts witha chosen tool is handed over to be wired in
Ends whenthe tool is wired in and what flows where is written down
Activities inside
- Take in the Chosen Tool
- Name the Systems Either Side
- Agree What Flows Where
16 activities · 45 blanks to fill · 2 human gates
Retire a Tool
Starts witha decision to retire a tool is recorded
Ends whenthe tool is off, the data is kept and the process runs elsewhere
Activities inside
- Take in the Decision to Retire
- Find What Depends on It
- Name Where the Process Goes
15 activities · 47 blanks to fill · 2 human gates