Another pattern I have seen data teams use to extend the Pattern Storming Canvas Workshop is creating an initial wireframe of the final Information Product as part of the workshop.
Wireframing is the pattern of creating a simple visual blueprint that maps out the core structure, layout, and flow of an Information Product, without the distraction of design details like colour, typography, or styling.
In an in-person workshop, sketch the wireframe on a whiteboard and capture a photo of it. In a virtual workshop, use tools like Miro or Google Slides. The wireframe is then stored alongside the completed canvas templates to provide additional context.
The wireframe is usually created after completing the canvas and then used to validate the shared understanding of the desired Information Product. This helps ensure that both stakeholders and the data team are aligned on expectations.
New data requirements may emerge during the wireframing process that weren’t identified when completing the canvas. For example, adding a dropdown filter to the dashboard might reveal the need for a Core Business Concept not previously discussed. A stakeholder may request a “Channel” dropdown, leading to a conversation about products being sold through multiple channels, something that hadn’t been identified initially.
A wireframe is a rough sketch, a visual diagram that acts as a shared language between you and the stakeholders to ensure alignment on the Information Product’s requirements. Avoid diving into detailed design at this stage, that will come later in your Information Value Stream steps.
Wireframing bridges the gap between abstract data requirements and tangible Information Product user experiences. It enables faster feedback, promotes shared understanding, and fosters better alignment between data teams and stakeholders.