Hypothesis map (Manangement Category)

I finally got my hands on reading Alexander Byndyu’s book about strategic planning. In general, this is Alexander’s second book, the previous one was called “Antifragility in IT” and I have already talked about it before. toldAnd then Alexander and I. recorded The "Code of Leadership" podcast series, where this book was disassembled. In the new book, Alexander talks about his method of mapping hypotheses, which develops the ideas of the method of impact mapping by Goiko Adzic. By the way, Goiko has a book called "Impact mapping," which I'm talking about. told earlier. In fact, Aleksand creatively expands this approach and proposes the following structure of the method, which he reveals in the first part of the book The Structure of the Hypothesis Map.

1. Purpose: By what criteria at the end of the work will we realize that we have achieved success
2. The subject is the one whose life we want to change with the help of a hypothesis so that the change leads us to the goal.
3. A hypothesis is a formalized idea by which we are going to change the behavior of a subject.
4. The task is a list of activities with the help of which we will test whether our hypotheses are correct. The main point of the change between impact mapping and hypotheses mapping is that the main focus of the map is to capture through hypotheses the answer to the question of why we think certain tasks will lead us to the goal. The hypothesis is formulated in the form

If <action 1> and <action2> ..., then < consequence>, because "idea">

In the second part of “The Subtlety of Mapping Hypotheses”, the author talks in more detail about the fact that goals should be set according to SMART, subjects should be described clearly and not amorphously “all consumers”, hypotheses should be correct in form, they should have meaning, tasks should not hang in the air and often they are combined in chains for implementation. In the third part of “Stages of work with the map of the hypothetical”, the author tells how to create it and when to stop, and then shares the approach to validating the map, which allows you to understand, not whether we did the crap. In the fourth part, the author describes the advantages of the approach, which include:

1. Sensible approach to decision
2. Strategy in the form of schemes as an accessible way of communication
3. Ability to vary implementation
4. Competitive advantage due to a clear and flexible strategy
5. Filter for projects without an idea (high-pitched)
6. Transfer of knowledge within the company
7. Switching the Mindset from “project costs” to “investment in strategy implementation”

In general, I liked Sasha Byndyu’s second book better. It is evident that he is writing in a focused way about the tool he used very often to work with strategy. In my opinion, this tool can be quite effective. More about the map of hypotheses can be read on the website cardhypothesis.

#Software #SoftwareDevelopment #Management #Processes #Strategy #Leadership #ProductManagement