Iterating the canvas areas
When to iterate the content in an Information Product Canvas area
The content in the Information Product Canvas is designed to evolve as you move through the Information Value Stream, but not every area requires the same level of iteration at the same time. Some areas naturally lend themselves to early iteration during the discovery and prioritisation steps, while others are better refined during the design or build steps as deeper understanding emerges.
Knowing when to iterate each area of the canvas is key to keeping it accurate and aligned with both stakeholder needs and technical realities. Iterating too early can lead to unnecessary effort and waste, while iterating too late can result in misaligned expectations.
When to iterate an Information Product Canvas Area
T-Shirt Sizing
A T-Shirt Size is often assigned shortly after the Workshop, once there’s enough information for the data team to make a high-level guesstimate to assist with prioritisation and roadmap planning. During backlog refinement or design, the data team revisits and refines the guesstimate based on deeper technical insights, ensuring the timeline and scope remain realistic.
Vision Statement / Outcomes
If the Information Product isn’t being prioritised, it’s often a sign the Vision Statement and Outcome need improvement, they should clearly convey its value and benefits. Refining them can better align the Information Product with organisational goals, highlight its business value, and strengthen the case for prioritisation.
Business Questions
During the Workshop, the key Business Questions stakeholders need answered are captured. During the design step, the data team engages with stakeholders to clarify details, address feasibility, and ensure the questions continue to align with business needs and available data.
Core Business Events
Core Business Events are captured at a high level during the Workshop, identifying the processes that generate the required data. During the design step, the data team begins investigating existing data structures and systems, aligning the canvas with previously documented Core Business Events. They iterate the canvas as they identify more precise data flows.
Will / Won’t
Initially, during the discovery and prioritisation steps, this area captures basic scope boundaries based on stakeholder expectations. During the design and build steps, the data team dives deeper into technical viability and feasibility, iterating this area in collaboration with stakeholders to adjust scope based on time constraints, data availability, or technical limitations. This ongoing collaboration and negotiation ensures that expectations are clear and that any trade-offs are mutually agreed upon.