To ensure we are able to understand, capture, and track the value of the work we do we have enlisted several tools to communicate value and align efforts with value. Three specific tools we use intended to keep us value-focused and aligned are the Lean Canvas, the Goal-Oriented Roadmap, and User Stories. Each of these tools, used properly, allow aligned value to emerge throughout the product development process and in turn improve our overall performance.

To capitalize on the benefit these tools are designed to deliver, we need to use them appropriately. To maximize alignment our value proposition should be captured in the three tools based on “Objectives and Key Results” (OKRs), think KPIs on steroids.

Lean Canvas: Many organizations, at the early stage of project/product development, create a Lean Canvas (or Business Model Canvas). The Lean Canvas first and foremost should capture the Why, identifying the problem to be solved. Our default process may be to skip this overarching question and dive directly into our solution. Failing to understand the problem first significantly reduces our potential value proposition. Proper use of the Lean Canvas should capture the Why / Value proposition in three areas:

Problem Description

Business Value

Goals/Metrics

The value captured is not meant to be a bulleted list. It should be an aspirational qualitative statement that guides and aligns all future efforts. Likewise Goals & Metrics should provide specific quantitative success criteria of the value to be delivered. Use OKRs to target bold goals and measurement of value.

Goal Oriented Roadmap: Throughout our Agile project lifecycle we plan and execute against a Goal-Oriented Roadmap. The “Goal” (Why/Value) drives the roadmap. The Goal should describe the benefits and value alignment for all work to be executed within the timebox. Applying OKRs to the Goal in the Agile Goal-Oriented Roadmap affords shorter cycles and rapid adjustment to change while reducing risk and promoting innovation. Again this is not a bulleted list, but a clear, aligned, and aspirational directive.

User Stories: The work of our Agile teams is driven by User Stories provided, usually, by the Product Owner. Good User Stories are value-based and results-focused, not technical and task driven. Completing tasks without delivering value is not success. When writing User Stories, a Hypothesis-Driven approach —We believe if we do (__X__), we will meet objective (__y__), which can be measured by (__z__) — will create Value-based User Stories, driving delivery of value not just completion of tasks.

The chain of completing Value-based User Stories to deliver features that support our roadmap goals, allow us to successfully deliver innovative products that solve our customers problems as defined by our Lean Canvas. Following this framework provides a definition of value that can be tracked and quantified from project inception to completion.

About OKRs: Objectives and Key Results are used to align and track objectives and outcomes. The main goal of OKRs is to connect organizations, teams, and individuals to generate movement in the same direction with measurable results. There is a wealth of information available on the web addressing OKR’s. I would recommend starting here with the OKR Guide.