People Inheriting a System
- Customer
- Someone taking over a system already running
- Context
- Nobody remembers why it was set up this way
The Jobs of someone accountable for choices they did not make and nobody recorded.
5 Jobs
- 01When I inherit a system, I want to understand it, so I am not running something whose shape I cannot explain.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 02When I take on a system, I want to know what it costs, so I am not paying for what nobody uses.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 03When what I inherited is old, I want to decide rightly between repairing and replacing, so I am neither pouring money into what will go nor discarding what still works.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 04When the old system must last two more years, I want to keep it running, so it is not firefighting every week.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 05When I have just inherited a large system full of problems, I want to know where to begin, so six months are not spent on what matters least.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
The four perspectives are for Pro Members
The Job statements in this Set are open to everyone. Pains, Desired Outcomes, Existing Solutions and Opportunity Gaps live inside the community, for Pro Members.
See Pro Member