Visioning-Development-Planning is the engine to speed up the development of systems. It connects people to the work, creating collaboration in trust in a learning environment. In a short introduction the method was proposed rather abstract https://www.linkedin.com/pulse/combining-systems-thinking-design-patrik-marien.
With one visual anchor, people can manage each other and themselves in an agile way. It allows to take a quick project start with little information and resources available, and keep rolling. Participants can quickly anticipate from the early start and see how they contribute to the success of a project.
Visioning-Development-Planning will not conflict with installed structures, methods and tools. The visual anchor connects people to your methods and tools as a personalized framework, giving visibility to ‘what to use when’.
The method makes things understandable by visualizing situations as systems and models with properties, to organize continuous development in a smooth flow and cut the crap. Visual thinking allows to create with an open mind during conversations, and close with a written understanding in ‘only necessary’ documentation.
Creating systems with vision and strategy, understanding each other.
Visioning-Development-Planning is about ‘discovering awareness of need‘ and creating a path to get that need.
The ‘What you want’ with the ‘how to get’ is visualized as a system view (the current and the future) to find elements and relationships with properties, simply by asking questions as what- who- when- where- why- how- how much.
Each created system is part of a bigger system and so related to adjacent systems. Draw the different levels chunking up and down.
What’s under the hood.
Visioning-Development-Planning is about fast progress and fun at work. Some concepts makes this clear.
Translation:
Every system creation and evolution cycle knows three events (fragments) [.] + [?] + [!] , each with a clear purpose [=] .
It is not a serial process. There is no preferred order which event comes up first.
Rhythm:
Events can start as much as can be handled, according to run a whole system translation cycle in a short cycle time.
The preference is to start with visioning (path to innovate) or modelling (path to create).
Play:
Set the game you want to play: such as a sequence of [.] [?] [!] with a clear view to what you want to achieve [=] and how to do that [resources, tools and method]
Learn of this game, review and adjust the tools and method anchored to each fragment [.][!][?][=]
The fragments explained:
“make your point”
It is: a moment for using imagination without using knowledge, free from all judgment.
What you do is: visualizing what is in the head(s).
How: it is creating, a fast hand drawing picture with pen and paper.
Why: to capture individual and collaborative thinking.
Examples: a representation of a concept of your vision, a representation of each conversation/ communication, a representation of an observation.
“understand”
It is: a moment for using knowledge, exploring unknowns.
What you do is: visualizing as a system, how things look like- what things do- what processes are going on.
How: based on the hand drawn model, find knowns and unknowns in the system. Look from different viewpoints, through more knowledge lenses.
Why: to stimulate curiosity and research. Bring in expertise, professionalism and experience.
Examples: a representation of a concept of a system- product- service with its properties, a representation of the impact of each conversation/ communication, a representation of a process.
“build up”
It is: a moment for making things work, materializing, crafting and testing.
What you do is: creating tangible evidence, a model with properties.
How: fast prototyping and sampling to the final model in use. Acting in a possible reality.
Why: to learn by testing.
Examples: paper prototypes, 3D prototypes, Virtual Reality prototype, test set up, pre-production samples.
“decide by purpose”
It is: a moment for reasoning. It is the purpose that turns one to next fragment and next cycle.
What you do is: creating purpose and building trust in collaboration with people.
How: reviewing and reflecting of whatever comes up, a team should ask “why we do this for, to achieve what”- “what can we do with what have now”.
Why: to be aware of purpose, avoid mistakes, appreciation outcome and learn.
Examples: short question & answer moment, give & take discussion, organized reviews, reflecting sessions, planning session, prioritizing, documenting.
Lessons learned.
Visioning-Development-Planning assists leaders and teams to create great products and many of many people who could work so will remember the value and the feel of been appreciated for their work.
(Must read more about: visioning, visual thinking, visual communication)