Evolving a design system
Stakeholders
Toolkit
In the dynamic landscape of digital design, maintaining the foundational elements of a design system is paramount to ensuring consistency, efficiency, and user satisfaction. As the Design Leader at Travix, I embarked on a transformative journey to update our existing Design System, affectionately named Tangram. This case study delves into the intricacies of this endeavour, outlining the rationale, values, and challenges that shaped our path towards revitalising Tangram.

Introduction
Overview
The existing Tangram Design System had languished without active maintenance, impairing its adaptability to the evolving demands of our products. A robust tokenised design system is the bedrock of any successful design strategy, empowering designers to tackle complex UX challenges while fostering consistency across teams. It is the linchpin that unites aesthetics, usability, and brand identity.
The process
Updating a design system can be a complex process that involves multiple steps. Here is the general process that we followed to plan and execute the updating of Tangram:
Create a design system update plan: Develop a plan that outlined the update process and the reasons why we should do this, including the steps involved, roles & responsibilities, and timelines. Identify any potential risks and plan to mitigate them.
Evaluate the current design system: Before updating the design system, we needed to evaluate the current system thoroughly. Identify the strengths and weaknesses of the existing design system, and gather feedback from stakeholders and users (engineers).
Set goals for the updated design system: Define the objectives of the updated design system. Determine what new features, components, and functionalities are needed. Set goals for improved user experience, increased efficiency, and better usability.
Define the scope and timeline of the update: Decided what parts of the design system need updating and prioritised them. Established a timeline for the update, taking into account the availability of resources and the impact on users.
Implement the update: Begin the update process, following the plan we created. Test each component of the updated design system thoroughly with the aid of our new QA resource to ensure that each component works as intended. Iterate as needed based on feedback and potentially some low level user testing.
Communicate the changes: Communicated the updates to stakeholders and users. Provided documentation and training as needed to ensure that users (developers & designers) can easily adapt to the changes.
Continuously improve the design system: Monitor the updated design system to identify any issues that arise, and address them promptly. Continuously collect feedback and analyse data to inform further improvements to the design system.
Design system values
At the heart of our endeavour lay a set of core values that Tangram was designed to embody:
Caring and Considerate: Our design decisions prioritise user well-being and satisfaction.
Empowerment: We provide users with the tools they need to achieve their goals effortlessly.
Craftsmanship: Every design element reflects the meticulous quality that defines our brand.
Frictionless Experience: We minimise user frustration through precise and speedy solutions.
Trustworthiness: We build and maintain trust through every interaction.
User Comfort: Our products are designed to make users feel at home.
This case study sheds light on the process, challenges, and outcomes of our mission to infuse new life into the Tangram Design System, aligning it with our core values and the ever-evolving needs of our digital landscape.
The challenge
As we embarked on the journey to update the Tangram Design System, several formidable challenges loomed large on the horizon. These challenges served as both roadblocks and opportunities to refine our approach and commitment to design excellence:
Legacy Neglect: The existing Tangram Design System had been relegated to the background, with sporadic updates and neglect. This lack of maintenance posed a substantial challenge as we sought to bring it up to date. Balancing the need for radical changes with preserving familiarity for existing users was a delicate task.
Diverse Product Ecosystem: Travix boasts a diverse product portfolio of 5 brands and countless websites, each with its unique requirements and design nuances. Adapting Tangram to cater to this variety while maintaining a coherent design language was a complex puzzle.
User-Centricity: Our commitment to user-centric design demanded that we not only address current needs but also anticipate future ones. Striking a balance between contemporary design trends and timeless usability was a perpetual challenge.
Interdisciplinary Collaboration: The success of Tangram's update depended on the collaboration of cross-functional teams, including designers, developers, and product managers. Ensuring alignment and effective communication across these disciplines was an ongoing endeavour.
Brand Consistency: Tangram was not just a design system but a custodian of our brand identity. Upholding brand consistency while evolving design elements presented a unique challenge.
In this case study, we explore how we tackled these challenges head-on, leveraging our core values as guiding principles to create a renewed Tangram Design System that met the demands of our dynamic digital landscape.
My Role within the Project
As the Design Leader at Travix, my role within the Tangram Design System update project was multifaceted, combining leadership responsibilities within the company with hands-on involvement as an individual contributor to the project. My journey in this capacity began with the recognition that our existing design system required a significant overhaul to meet the evolving needs of our product ecosystem. Below, I outline my roles and contributions to this transformative endeavour:
Initiator and Planner:
Project Formulation: Recognising the need for a design system update, I initiated the project and formulated a comprehensive plan.
Strategic Vision: I outlined the strategic vision for the update, emphasising the importance of aligning Tangram with our core values and the dynamic digital landscape.
Plan Development: I led the development of the update plan, meticulously outlining the steps, reasons, roles, responsibilities, and timelines.
Evaluator and Strategist:
Thorough Evaluation: Prior to embarking on the update, I oversaw a thorough evaluation of the existing design system. This evaluation encompassed identifying strengths, weaknesses, and gathering invaluable feedback from stakeholders and engineering teams.
Goal Setting: I played a pivotal role in setting clear and ambitious objectives for the updated design system. These objectives aimed to enhance the user experience, increase operational efficiency, and elevate usability.
Project Director:
Scope and Timeline Definition: I was instrumental in defining the scope and timeline of the update. This involved prioritising components of the design system for revision and ensuring alignment with resource availability and user impact.
Resource Allocation: I worked closely with various teams to allocate resources efficiently, ensuring that the project stayed on track.
Implementation and Collaboration:
Hands-On Contribution: As an individual contributor to the project, I actively participated in the implementation phase. I worked closely with our new QA resource, to meticulously test and iterate on each component of the updated design system.
Cross-functional Collaboration: I fostered a collaborative environment where designers and developers worked closely together to bring our vision to life. This synergy was crucial in ensuring that the updated design system met the needs of all stakeholders.
Communication and Documentation:
Stakeholder Communication: I took the lead in communicating the changes and updates to stakeholders and users, ensuring transparency and managing expectations effectively.
Documentation and Training: I oversaw the creation of documentation and training materials to facilitate a smooth transition for users adapting to the changes.
Continuous Improvement Advocate:
Ongoing Monitoring: Beyond the initial update, I emphasised the importance of continuous monitoring of the design system. This involved identifying and promptly addressing any issues that arose.
Feedback-driven Enhancements: I championed the collection of user feedback and data analysis to drive ongoing improvements, ensuring that the design system remained agile and responsive to evolving needs.
In summary, my role within the Tangram Design System update project encompassed leadership, strategy, planning, hands-on contributions, and a relentless commitment to collaboration and continuous improvement. The project's success hinged on the convergence of these roles, embodying the ethos that ***effective design and development are most powerful when designers and developers work together harmoniously***.

So, why did we do this?
Updating a design system can bring several benefits to the business, engineers, designers, and end users. Here are some reasons why updating our design system was important, along with the associated benefits for each stakeholder group:
Business benefits
Consistency: A robust design system ensures consistent branding and user experience across all products and platforms, which strengthens brand identity and recognition.
Efficiency: Developers and designers can work more efficiently by reusing established design patterns, components, and guidelines, reducing redundant efforts and development time.
Scalability: An updated design system provides a foundation for scaling products and services quickly, enabling the business to respond faster to market demands and stay ahead of the competition.
Reduced Costs: With a centralised design system, we can avoid duplicating design and development work, leading to cost savings in the long run.
Engineering benefits
Productivity: Developers can leverage a comprehensive design system to streamline their workflow and focus on writing efficient code, resulting in faster development cycles.
Consistency and Maintenance: Using standardised design patterns and components ensures consistency and reduces the effort required to maintain and update the codebase.
Collaboration: A well-documented design system facilitates collaboration between designers and developers, promoting effective communication and alignment throughout the development process.
Designer benefits
Design Consistency: An updated design system provides a shared language and visual consistency, allowing designers to create cohesive user experiences across different products and platforms.
Faster Iteration: Designers can iterate more quickly by leveraging existing components and guidelines, accelerating the design process and reducing time-to-market.
Focus on Innovation: With a solid design system foundation, designers can spend more time on creative problem-solving, exploring innovative solutions that enhance the user experience.
End user benefits
Improved Usability: A consistent and intuitive design system makes it easier for users to learn and navigate through different products and services, enhancing their overall usability and satisfaction.
Familiarity: When users encounter consistent design patterns across various products and platforms, they can quickly understand and interact with new features or interfaces, leading to a more seamless experience.
Accessibility: An updated design system can prioritise accessibility standards, making products and services more inclusive and ensuring that all users can access and interact with them effectively.
When taking these benefits into consideration I started to qualify and quantify elements in order to help us create the success measurements for the project. Also, breaking the benefits down into the stakeholder groups and setting the KPI’s enabled me to gain a smooth buy in from the C-Suite to proceed with this project.

So, what did we do?
Our journey began by scrutinising the foundational elements that constitute Tangram.
In order to create and solidify the project goals I created SMART (Specific, Measurable, Achievable, Relevant and Time-bound) goals for each of these areas.
Colours: The palette that paints our digital canvas.
Specific: Update the colour palette in the design system to create a more modern and cohesive look across all devices.
Measurable: Review and update at least 80% of the existing colours within the next 2 months to ensure they align with the new design guidelines.
Achievable: Develop a comprehensive colour system that includes primary and secondary colour palettes, as well as guidelines for colour usage, contrast ratios, and accessibility compliance.
Relevant: Conduct user testing and gather feedback to ensure that the updated colour palette enhances the overall user experience and reflects the company's brand identity.
Time-bound: Complete the full rollout of updated colour palette in the design system within the next 3 months, with regular checkpoints and milestones to ensure progress is on track.
Typography: The voice that speaks through our content.
Specific: Update the typography in the design system to create a more cohesive and modern look across all devices.
Measurable: Review and update at least 75% of the existing typography styles within the next 3 months to ensure they align with the new design guidelines.
Achievable: Create a comprehensive typography guide that includes detailed instructions on font families, weights, sizes, spacing, and hierarchy to ensure consistency across all applications.
Relevant: Conduct user testing and gather feedback to ensure that the updated typography is legible, easy to read, and enhances the overall user experience.
Time-bound: Complete the full rollout of updated typography in the design system within the next 6 months, with regular checkpoints and milestones to ensure progress is on track.
Iconography: The visual cues that guide user interactions.
Specific: Update the iconography in the design system to create a more consistent and modern look across all devices.
Measurable: Review and update at least 90% of the existing icons within the next 3 months to ensure they align with the new design guidelines.
Achievable: Develop a new set of customisable icon components that can be easily adapted to different product categories, allowing for greater flexibility and efficiency in the design process.
Relevant: Conduct user research and gather feedback to ensure that the updated icons effectively communicate key messages and enhance the overall user experience.
Time-bound: Complete the full rollout of updated iconography in the design system within the next 6 months, with regular checkpoints and milestones to ensure progress is on track.
Form controls: The building blocks of user input.
Specific: Update the form controls in the design system to create a more user-friendly and aligned experience across all pages and devices. To include inline error handling.
Measurable: Review and update at least 90% of the existing form controls within the next 2 months to ensure they align with the new design guidelines.
Achievable: Develop a comprehensive set of customised form control components that can be easily adapted to Tangram, allowing for greater flexibility and efficiency in the design process.
Relevant: Conduct user testing and gather feedback to ensure that the updated form controls effectively handle information, error states, enhance usability, and improve user engagement.
Time-bound: Complete the full rollout of updated form controls in the design system within the next 3 months, with regular checkpoints and milestones to ensure progress is on track.
Illustrations: The narrative visuals that enhance user engagement.
Specific: Update all illustrations in the design system to reflect the company's brand identity, with a focus on incorporating more vibrant colours and a modern, minimalist design style.
Measurable: Review and update at least 50% of the illustrations in the design system within the next 6 months to ensure that they are consistent with the brand guidelines.
Achievable: Work with the marketing designer to develop a new set of customisable illustration components that can be easily adapted to different product categories, allowing for greater flexibility and efficiency in the design process.
Relevant: Conduct user research and gather feedback to ensure that the updated illustrations resonate with target audiences and effectively communicate key messages.
Time-bound: Complete the full rollout of updated illustrations in the design system by the end of the year, with regular checkpoints and milestones to ensure progress is on track.
Interactions: The choreography of user experiences.
Specific: Update the interactions in the design system to create a more intuitive and seamless user experience across all platforms and devices.
Measurable: Review and update at least 80% of the existing interactions within the next 3 months to ensure they align with the new design guidelines.
Achievable: Align all interaction patterns with common animation and transitions that can be easily adapted to different components and elements within Origami, allowing for unified interaction experience.
Relevant: Conduct user testing and gather feedback to ensure that the updated interactions effectively communicate key messages, enhance usability, and improve user engagement.
Time-bound: Complete the full rollout of updated interactions in the design system within the next 6 months, with regular checkpoints and milestones to ensure progress is on track.
Accessibility: The commitment to inclusivity.
Specific: Improve the accessibility of the design system to ensure that it meets or exceeds accessibility standards, including WCAG 2.1 AA.
Measurable: Conduct an accessibility audit of the design system to identify areas that need improvement and develop a plan to address at least 90% of the identified issues within the next 6 months.
Achievable: Develop a comprehensive accessibility guide that includes guidelines for colour contrast, typography, navigation, forms, and interactive elements to ensure that all users can access and use the design system.
Relevant: Conduct user testing and gather feedback from users with disabilities to ensure that the updated design system is inclusive and meets their needs.
Time-bound: Complete the full rollout of the updated design system that meets accessibility standards within the next 12 months, with regular checkpoints and milestones to ensure progress is on track.
…and what are the potential obstacles?
Even in the planning stages I became aware that there were several potential obstacles that could arise as we went through the process of the project. I think it’s worth covering them here in this case study as it may be a helpful heads-up for some folks:
Resistance from stakeholders: Stakeholders may resist changes to the design system because they are comfortable with the current system and fear that the new system will be more difficult to use.
Lack of clarity around design system goals: If the goals and objectives of the design system update are not clearly defined, it can be difficult to gain buy-in from stakeholders and/or C-Suite and ensure that the project stays on track.
Resource constraints: Updating a design system can require a significant amount of time, money, and resources. If these resources are not available, it may be difficult to complete the project successfully.
Compatibility issues: If the updated design system is not compatible with existing software, tools, or systems, it can cause disruption and delays.
Inadequate testing: Insufficient testing of the updated design system can lead to bugs, errors, and usability issues that may undermine the effectiveness of the system.
Lack of user feedback: If user feedback is not taken into account during the design system update, it may not meet the needs of the users and may be less effective than the previous system.
Resistance to change: People may resist changes to the design system simply because they prefer the way things were done in the past. This can be difficult to overcome, especially if the changes are significant.
Design efficiency: Potential reduction in productivity for non design system projects... while the design investigation phase is ongoing, if resources are an issue.
To overcome these obstacles, I found it was important to have a clear plan, communicate the benefits of the new system to stakeholders, involve users in the design process, and allocate sufficient resources for implementation (design & development) and testing.

So, how did we do it?
For projects of this scale there are many processes that you can wrap around them to ensure a positive outcome but when it came to the process of how we were actually going to tackle the work then I wanted to keep it as simple as possible.
After reviewing many other case studies and reference sources of how different companies implemented new Design Systems, I settled on the 4 step iterative process below.
Design: In this first phase, we wanted to gather a clear understanding of the problem we were trying to solve. The solutions included the overarching principles and guidelines that governed our design system's updates. We wanted to define our target audience, understand their needs, and identify any pain points that our design system can solve.
Investigate: The investigation phase was all about our engineers understanding the technical requirements and implications of the proposed update. What work would be needed to update a foundational piece and how that would affect specific components.
Implement: In the implementation phase, we started to bring our design updates to life. This involved the engineers to create or amend elements within the codebase and for designers to create or amend the design components within Figma. Both designers and engineers also created the relevant documentations for the updates.
Release: Finally, we wanted to release our updated design system to users. This involved heavy collaboration with engineers and QA to integrate the design system into Storybook and conduct thorough quality assurance testing to ensure that the design system is effective, usable and bug free. We also wanted to monitor user feedback and make any necessary updates based on user needs and behaviour.
As mentioned, this process is an iterative one, meaning that we repeated each phase several times as we tackled each foundation and refined our design system based on user feedback and testing. By following this process, we were able to create a design system that is both effective and efficient, meeting both user needs and business goals.
While breaking each of these process phases down into more granular actions I was able to define some milestones, which in turn can act as a to-do tick sheet.
…and how did we measure success?
After working out the benefits to each user group (business, engineering, designers and users) it was logical to look for success metrics in the areas that I had marked as benefits, to see if we had any baselines to work off and attach some SIMple goals to.
On top of the KPI’s, the main measurements I set were:
USER FEEDBACK/SATISFACTION
Collect feedback from users to determine whether they find the new design system easy to use and whether it meets their needs. Conduct user surveys to get a comprehensive understanding of user satisfaction and aim for 85% satisfaction rate by the end of Cycle 4 2023.
EFFICIENCY METRIC
Measure the efficiency of the new design system for Designers and Developers by comparing the time it takes to complete tasks using the new system versus the old system. A by product of this will be fewer design iterations, and improved design quality, leading to fewer design-related issues and cost saving through time spent. The target of reducing time on task is 10%, we should see this impact by the end of Cycle 3 2023.
ADOPTION RATE
Track the adoption rate of the new design system to see how many users are actively using it, we will aim for an 80%+ adoption rate by the end of 2023. This can help determine whether the new system is meeting the needs of the users and if it is better than the old system.
CONSISTENCY
Evaluate the consistency of the new design system by reviewing the consistency of design elements such as colour, typography, and layout. Ensure that the new system is more consistent than the old system and that it aligns with the brand's overall visual identity. Through QA and sign off from Marketing by the end of C4 2023.
MAINTENANCE & SCALABILITY
Successfully setup internal processes that enable us to align and evolve the design system across multiple teams. Clearly identify component pipelines and integrate with development processes to be monitored and discussed in a quarterly meeting with engineers, to start in Cycle 4 2023.

So, who made it happen?
When creating or updating a design system, it's important to involve a range of stakeholders to ensure the system meets the needs of all users and aligns with the overall goals of the organisation. Some key stakeholders that I involved in this project and the reasoning why I chose those folks were:
DESIGNERS
Designers are essential stakeholders in any design system project. We can help identify design patterns that need to be updated or added, provide feedback on the design tokens and components, and ensure that the system aligns with the design principles and standards of the organisation.DEVELOPERS
Developers play a critical role in implementing the design system within the organisation's codebase. They can help identify technical requirements and constraints, provide feedback on the usability and accessibility of the design system, and ensure that the system can be easily integrated with existing Origami elements and pages.PRODUCT OWNERS/MANAGERS
Product owners are responsible for ensuring that the design system aligns with the overall product strategy and user needs. They can help prioritise features and components, provide feedback on the usability and functionality of the system, and ensure that the system meets the needs of all users.MARKETING, COMMUNICATIONS AND E-COMM TEAMS
Marketing teams are responsible for ensuring that the design system aligns with the organisation's brand and messaging. They can help identify brand guidelines and ensure that the system is consistent with the overall visual identity of the organisation. As well, with the Comms & e-comm teams involvement will ensure the correct direction for Tone Of Voice (TOV) and business goals are not impacted negatively.QA TESTERS
A quality assurance (QA) tester will play a very important role in the project by ensuring that the system is thoroughly tested for functionality, usability, and accessibility. They can help identify and report any bugs or issues with the system, provide feedback on the user experience, and ensure that the system meets the organisation's quality standards.
Overall, by involving this diverse group of stakeholders in the project helped us ensure that the system meets the needs of all users, aligns with the overall goals of the organisation, and is implemented effectively within the organisation's codebase.
…and who are we reaching and why?
The target audience for a design system update can vary depending on the purpose of the update. However in our case, the primary audience for the project would be the designers, developers, and other stakeholders who are responsible for creating and implementing the design system. This includes Product designers, front-end developers, product owners, and other members of the design and development team.
However, the secondary audience for a design system update would be the end-users of our products that the design system supports. The purpose of the design system is to ensure a consistent and cohesive user experience, so it's important to consider the needs and preferences of our end-users when updating the design system. This includes conducting user research and gathering feedback to ensure that the updated design system effectively meets their needs and enhances their overall experience.
Ultimately, a design system update should be targeted towards both the internal design and development team as well as the end-users, with the goal of improving the efficiency, consistency, and usability of our products.

So, when was it done?
To make a project at this scale tangible a lot of moving pieces have to come together in order to ensure success. Planning and creating a roadmap for this project provided several benefits. Here are some reasons why we created a roadmap and used a Gantt chart to show its different stages:
Provides a clear overview of the project: A roadmap can help us to understand the overall goals of the project, the timeline for completing it, and the different stages that need to be completed. This helps to ensure that everyone is on the same page and working towards the same objectives.
Helps to identify dependencies: By breaking the project down into different stages and creating a Gantt chart to show the timeline for each stage, we can identify any dependencies that exist between stages. This can help us to plan the project more effectively and avoid delays.
Allows for better resource allocation: When we have a clear understanding of the different stages of the project and the timeline for completing them, we can allocate resources more effectively. This can help to ensure that we have the right people and tools in place at each stage of the project.
Enables better communication: By having a roadmap visualised, we can communicate our plans and progress to stakeholders and team members. This promotes transparency and helps to keep everyone informed and invested in the project.
Helps to manage risk: It also helped us to identify potential risks and develop contingency plans to mitigate them. This inevitably helped us avoid delays or unexpected problems during the project.
Here is the Gantt chart for the detailed breakdown of the project timeline and action items below... but as all live projects it evolved, mutated and matured as business priorities changed and resource levels fluctuated.

So, what were the outcomes?
As of writing this case study (August 2023), our awesome design team had taken 4 foundational pieces (Form controls, Typography, Iconography and Colour palette) and put them through the ‘Design Assessment’ phase which was essentially a review and audit process to research the current situation, external best practice guidelines, internal usage data and competitor analysis. This in turn gave them enough input to produce the proposed solutions - the Design Improvement phase on the Gantt.
All of the research and the solutions were organised into a beautiful Figma file and then presented with key stakeholders in a Story Mapping session. I’ll not go to deep on what a Story Mapping session is but its essentially lots of technical discussions around implementation, known unknowns and technical restraints to give the developers a better understanding of what, why and how they will implement the changes into the code base.
…here comes the curve ball!
It was decided to implement the new Colour Palette with their associated Tokens first as this was one of the quick easy wins, considering other business priority projects that the engineers were undergoing it was an amicable compromise.
At this point the other project pieces are progressing as planned. However, I’m sure the roadmap will be adjusted as we go through our main Product Cycle Planning & Roadmap sessions and if there are other business priorities which impact development resources then we will adjust our plan and expectations.
Personally I’m OK with adjustments like this as I understand that prioritising a design system project over product initiatives that have business cases and predicted ROI with limited resources, is pretty much impossible within an e-comm company.
I’m sure there are many information sources and case studies out there that actually attached a predicted ROI on a Design System project, which would make it more attractive to prioritise and more digestible for the Product Leadership… happy hunting!
Also because this is an on-going project I can not give any outcomes that are attached to the success measurements. However, if we use the granular steps within the outlined implementation process as KPIs, then approximately 70% have been met for the 4 foundational pieces that are ongoing.

Conclusion
Transforming Tangram for the Future
The journey to revitalise the Tangram Design System has been an exciting and transformative endeavour. At the core of this undertaking were the principles of adaptability, consistency, and user-centricity, all woven into the very fabric of Tangram. This case study has illuminated the path we traveled, revealing the intricacies of our process, the challenges we faced, and the achievements that are still unfolding.
The Power of Collaboration and Leadership
One of the key takeaways from this project is the paramount importance of effective collaboration between designers and developers. As the Design Leader at Travix, my role was not just about steering the ship but also about diving into the intricacies of the project. I recognised the need for change, formulated a comprehensive plan, set ambitious goals, and paved the way for our vision of Tangram to align seamlessly with our core values and the dynamic digital landscape. Collaboration was not just a catchphrase; it was the very essence of our success.
Addressing Challenges Head-On
Our journey was not without challenges, but every challenge served as an opportunity to refine our approach and commitment to design excellence. We faced legacy neglect, navigated a diverse product ecosystem, and ensured a user-centric focus. We championed interdisciplinary collaboration and maintained brand consistency. These challenges, while formidable, were instrumental in sculpting a renewed Tangram Design System that met the demands of our ever-evolving products and digital landscape.
A Roadmap to Success
To ensure that this project remained on course and yielded positive results, we created a roadmap that provided a clear overview of the project, identified dependencies, allocated resources effectively, facilitated better communication, and enabled risk management. This roadmap was a living document that evolved as business priorities shifted, ensuring that we remained agile and responsive to changing circumstances.
Evaluating Success
While we are still in the midst of this transformation, the initial steps have borne fruit. A significant portion of our foundational pieces have passed through the design assessment and improvement phases, and the colour palette has been successfully updated. As for the other foundational pieces, progress is well underway. The success measurements and KPIs embedded within our process will serve as guiding stars, allowing us to measure our achievements against the granular steps outlined in the project plan.
In conclusion, the update of the Tangram Design System is an ongoing journey. It embodies the spirit of collaboration, adaptability, and the relentless pursuit of design excellence. As we forge ahead, we remain dedicated to aligning our design system with the core values that guide us and the evolving needs of our digital landscape. We look forward to the continuous evolution and improvement of Tangram, solidifying its place as the bedrock of our design strategy and the catalyst for exceptional user experiences.
Our journey is far from over, but it's a testament to the power of design leadership, collaboration, and a shared vision for a better, more user-centric digital future. Together, we shape the evolution of Tangram and with it, the user experiences of tomorrow.
Thank you for taking the time to read this massive case study, I hope you found it informative and if you have any feedback then please reach out!


