Adding Additional Context
avoid assumptions and fills in knowledge gaps, when and where it makes sense
During the Pattern Storming Canvas Workshop, additional context often emerges that the data team will find useful. The challenge is capturing this information in a way that enhances understanding without overcomplicating the canvas or introducing unnecessary waste by adding too much detail too early.
As seen in the example canvases from the previous chapter, data teams vary significantly in how they capture this additional context. The Information Product Canvas is intentionally flexible, allowing context to be added wherever it fits best. If a piece of information naturally fits in a specific area, include it there.
However, some context, such as diagrams or detailed explanations, may not fit neatly within the canvas. In these cases, a different approach is needed to ensure the information remains accessible and useful.
One example is the wireframing pattern described on the next page. Some data teams draw wireframes on the back of a physical canvas, others use a separate sheet of paper, while some sketch on a whiteboard, take a photo, and store it alongside the digital canvas. The best approach depends on the type of context being captured, how it will be stored, and, most importantly, how it will be used in the subsequent steps of the Information Value Stream.
The Information Product Canvas thrives on simplicity and focus, but not every piece of data work fits neatly into its visual format. Adding additional context helps data teams avoid assumptions and fill in knowledge gaps. The key is to capture just enough context at the right time, removing ambiguity without overwhelming the canvas or introducing unnecessary complexity too early.
Data teams often gather extra context to support the successful design, build, and delivery of an Information Product. This context helps ensure clarity, improves alignment with stakeholder needs, and reduces ambiguity during development.
Some examples of additional context data teams commonly capture include:
Detailed Descriptions of Core Business Events
Expanded information on key business processes that generate the data used in the Information Product.Information Product User Journeys
Visual maps or narratives outlining how users interact with the Information Product to achieve specific outcomes.Wireframes of the expected Delivery Output
Low-fidelity visual mock-ups that illustrate the layout and structure of dashboards, reports, or other output formats.Business Glossaries
Clear definitions of business terms and concepts to ensure consistency across teams and stakeholders.Persona Templates
Detailed profiles of typical data users, outlining their needs when using the Information Product.Press Releases for Data Platform Features
Pre-prepared communication materials that explains new data platform capabilities in a stakeholder-friendly format.Return on Investment (ROI) Calculations
Analyses comparing the expected benefits of the Information Product to its development and operational costs.Strategic Alignment Mapping
Visuals or narratives that show how the Information Product supports the organisation’s broader strategic goals.Business Rule Definitions
Specifications of logic and conditions applied to the data, such as the calculation methods.KPI Definitions
Clear explanations of key performance indicators used in the Information Product, including how each metric is calculated.Data Sources
Information about where data originates and any dependencies involved.Assumptions and Risks
Documented potential risks, dependencies, or assumptions that could impact timelines, scope or delivery success.
Additional context can be captured in different places depending on the format of the canvas and the type of information being captured:
Annotating the Canvas Areas
Capture extra details directly within a relevant canvas area, where suitable, such as the Core Business Events or Will/Won’t areas.
Back of the Paper Canvas
If using a physical paper canvas, data teams can write additional context on the back to expand key areas without cluttering the front.
Digital Collaboration Tools
Using digital tools like Miro, Confluence, Notion, or Google Docs allows data teams to capture supplementary information while keeping the canvas streamlined.
Documentation as Code
For technical details, markdown files and Git repositories provide visibility, traceability, and version control for this additional context.