A recipe for collaborative product ownership: Finding solutions to business problems that are feasible *and* sustainable.
—
How do you translate an OKR back to a hypothesis that can be challenged by the various roles within a team? How do you ensure that the communication around initiatives is not hindered by conflicting terminology or by misinterpretation? In what ways can you involve business stakeholders in finding solutions that will help them understand the technical constraints that a team has to take into account? And how do you prevent tech teams building the wrong thing the right way?
**Imagine**:
– a way to **visualize and clarify** to the relationships between OKRs, hypothesis and the underlying technical constraints within the technical real-estate;
– having a **common language** to talk about problems in context, removing ambiguity and confusion in the process;
– and finally a way to **collaboratively** dive into the nitty gritty detail of the current landscape and the proposed solution;
In this session Marijn Huizendveld will take you through the process of leveraging your existing OKRs to clarify what needs to be done to all stakeholders and members of a team.
**Expect:**
– To learn what constitutes a good Objective, Key Result, and Health Metric;
– To see how OKRs can be visualized in a Wardley Map;
– To capture heuristics that are helpful when mapping OKRs with a team
