Requesting Design Updates

We strive to ensure that Tecton is a themeable and flexible design system. Each component or pattern is put through a rigorous cycle of design, user testing, and development. As such, we strongly recommend that designs and products use the components as designed and developed to ensure consistency and synergy with the Q2 Ecosystem.

This guide is a streamlined process for requesting visual changes to ensure that the Tecton Design System remains consistent, scalable, and responsive to team needs. This guide outlines the steps for external teams to request visual changes through the lead designer.

1. Understand the Purpose of the Design System

Before submitting a request, ensure that you understand the goals and principles of the Tecton design system. The system is built to maintain consistency, accessibility, and usability across all platforms.

Key Principles:

• Uniformity: Ensure all designs follow the established guidelines.
• Accessibility: Support inclusive user experiences.
• Scalability: Allow for growth and evolution of the system.
• Themeability: Reflecting the brand or product of our customers.

2. Define the Need for the Change

Clarify why the visual change is necessary by addressing the following:

• Purpose: What is the problem this change will solve?
• Impact: How will this change benefit the user experience or the design system?
• Scope: Will this change affect other components or systems?

Document these points to provide context for your request. Engage your designer and work to figure out where the visual differences are coming from.

3. Review Existing Documentation

Check the design system's documentation to confirm:

• Whether the requested visual element already exists.
• If some similar components or patterns could be adapted.
• Whether the proposed change aligns with the design principles.

4. Submit a Detailed Request

Prepare a clear and comprehensive request to the lead designer. Include the following:

A. Request Summary

• Title: A concise title summarizing the request.
• Description: A brief explanation of the change.

B. Supporting Details

• Use Case: Describe the specific situation where the change is needed.
• Mockups or References: Provide visual examples, sketches, or references.
• Dependencies: Note any components or systems that rely on the proposed change.
• Accessibility Considerations: Address how the change meets accessibility standards.

C. Priority and Deadline

• Indicate the urgency of the request and any critical deadlines.

5. Communicate with the Lead Designer

Submit your request through the designated communication channels (e.g., email, project management tool, or design review meeting). Ensure the lead designer(Currently Spencer Tullos) has all the necessary information to evaluate your proposal.

6. Participate in the Review Process

Be available to:

• Clarify any details.
• Provide additional examples.
• Collaborate on refining the proposal.

The lead designer will assess the request based on design principles, system scalability, and user impact.

7. Receive Feedback and Updates

The lead designer will provide feedback or approve the change. If approved, they will coordinate implementation with the design system development team. If declined, constructive reasons and alternative solutions will be shared.

8. Post-Implementation Review

Once the change is implemented:

• Verify its effectiveness in the intended context.
• Share feedback on its integration with the design system.

By following this guide, external teams can contribute effectively to the evolution of the design system while maintaining its core integrity. Please contact Spencer Tullos, the lead designer on Tecton.