UNV-04: Plan Last

You will understand why the plan is written before the workflow is understood, what real discovery is, and what artefact should come first.

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 · Plan last
  If you want more context first: UNV-03: Complexity as Cover — The consultant layer
  If you want to go further: UNV-05: The Change Request Trap — The change request trap

Evaluation Guide · Ask the Puppy · Browse everything

The document itself