UNV-06: Invisible Stakeholders

You will see who is missing from the room when an implementation is specified, and how to find them before go-live.

What do you want to understand next?

• What is Vektor, why does it exist and what does it do?
• Does the quantitative methodology stand up?
• What are the risks, limitations and controls?
• What changes operationally if Vektor is adopted?

Where this document fits

• The Unvarnished series · The invisible stakeholders
  If you want more context first: UNV-05: The Change Request Trap — The change request trap
  If you want to go further: UNV-07: The Hammer, the Tool, and the Methodology — A tool, not a methodology

Evaluation Guide · Ask the Puppy · Browse everything

The document itself