Menu

Supplementary Canvas

Short Tip: Artifacts that can help with specific analyzes, if necessary for the solution.

What is it?

These are supplementary Canvas to be optionally used according to the solution’s characteristics; they allow approaching the detailing of risks.

Why use it?

The Canvas can be used as a tool for detailing aspects of the initiative that are not captured in other Canvas, namely:

  • Risks: relevant for products that are generally innovative or face significant obstacles to their execution.

How to use it?

The Initiative Leader conducts the process, together with the Development Team and other relevant stakeholders.

When approaching risk, the following steps should be taken:

  • Print and discuss with the team the Assumptions and Constraints Canvas relating to product development. Consider that:
    • Assumptions are hypotheses assumed by the team, even if externally defined – e.g., the product can be made of any material;
    • Constraints are restrictions to product development – e.g., the product should be ready in 6 months.
  • Print and discuss with the team the SWOT Canvas. Consider that:
    • Strengths are the product’s positive aspects, usually under your control (internal environment);
    • Weaknesses are the product’s negative aspects, usually under your control (internal environment);
    • Opportunities are those aspects that can have a positive impact on the product in the future, usually beyond your control (external environment);
    • Threats are those aspects that can have a negative impact on the product in the future, usually beyond your control (external environment).
  • Print the Risks Canvas and bring to it the main Assumptions, Constraints, Strengths, Weaknesses, Opportunities or Threats considered by the team as Potential Risks to be addressed.
    • For each potential risk item, make an impact and probability assessment, write it on the top of the card and place it on the Canvas;
    • Once all cards are finished, consider actions to be taken for each threat or opportunity, and then write down the action and its owner. Write any necessary details on the back. 
  • For each action related to a threat or opportunity requiring an effort by the Development Team, include that action as an item in the Product Backlog.

Templates