Design Debt: issue template

[AlicjaSuska]

Description

• Define the problem and explain why it is important to solve it. Feel free to attach screenshots and point to external resources.

Type of Design Debt

• Operational - slows down the design and development teams’ work. It can be defined as the absence of the underlying structure and processes
• UX - inconsistent experiences throughout the product that negatively impacts the learnability and integrity of the flow
• Visual - focused on inconsistent graphical aspects of the interface like shapes, colors, etc.

Size

•  S :  small straightforward modifications to existing functionality, no research required.
• M : medium-sized projects that usually involve 1–2 teams (or more teams in very small capacity) that may require simple research; they leverage an existing functionality or flow.
• L:  large initiatives that require cross-team collaboration and research; major changes in flow or functionality are needed.
• XL:  extra large cross-team cross-functional strategic projects that require major architectural changes, broad ideation, and complex research. Potentially a redesign of the whole product or its major areas.

Product area(s)

• List which product areas (or products) are affected by Design Debt.

Dependencies

• List which teams need to be engaged in fixing this Design Debt and what are the dependencies between them.

Impact

• impact-effort matrix:
  • quadrant I: high-impact - high-effort
  • quadrant II: high-impact - low-effort
  • quadrant III: low-impact - low-effort
  • quadrant IV: low-impact - high-effort
• customer impact matrix

Urgency

• Low :  no impact on the current roadmap. The issue can be tackled at a convenient time;
• Medium :  moderated impact on the planned work. Consider taking care of the issue in the nearest future or together with associated development;
• High :  work on the roadmap is highly affected. Fix the issue as soon as possible. Not resolving the problem may negatively impact planned work or cause exponentially accumulating Design Debt.

---

Proposed solution (optional)

• Describe how you would like to solve the problem.

Processes

• List what activities (research, design exploration, RFC document, workshop, etc.) are needed to find the solution to this problem.

Timeline (optional)

• Set the timeline for design to make this issue engineering-ready.