Hire a designer

Explore Durable vs. Adaptable Elements

Durable elements in the design system include the components, attributes, and design tokens that create a sense of stability and familiarity. You can think of these as the foundational pieces that stay consistent, helping users feel comfortable as they move between different products. Meanwhile, adaptable elements bring in the excitement; they offer flexibility and allow for product-specific themes that meet the unique needs of users. This balance is important, it gives designers the freedom to innovate while still staying true to the core identity of the Intuit brand.

Using the right terminology is essential for this framework. Rather than calling these components "fixed," describing them as "durable" emphasizes their capacity to change, much like the layers of a building that can adapt over time. Just as a carefully constructed building can evolve while keeping its fundamental structure intact, IDS can also develop and transform, making sure it stays relevant as user expectations and technology continue to progress.

Recognize the System of Systems Approach

The IDS operates with a 'system of systems' approach, which allows for a balance between autonomy and cohesion within teams. Each product or business unit has the freedom to tailor its design while still aligning with the overarching framework. This structure means that while designers can inject creativity into their specific products, they’re also contributing to a unified branded house that enhances user experience across the board.

The idea is to cultivate a federated ecosystem where shared components can be leveraged across different products, reducing redundancy and promoting efficiency. By fostering this interconnectedness, the IDS not only streamlines the design process but also builds a sense of trust and shared ownership among designers and developers alike.

Manage Variants Across Products and Platforms

Managing variants across products and platforms is another critical facet of the Intuit Design System. With multiple themes, platforms and even light/dark modes to consider, the complexity can quickly escalate. However, the approach taken by IDS ensures that this complexity is manageable. By categorizing components and establishing clear guidelines, the system enables designers to navigate these variants with ease.

Automation plays a pivotal role here. Tools like Style Dictionary help manage design tokens and ensure consistency across various product interfaces. This not only streamlines updates but also helps maintain the integrity of the design as it scales. The goal is to create a seamless experience for users, regardless of which product they’re using or how they interact with it. In a world where users expect fluidity and coherence, this meticulous management of design variants is essential for success.

Embed Designers within Business Units

Embedding designers within business units is like having a translator who understands both the language of design and the specific dialect of each product's needs. These designers act as the bridge, conveying user needs and insights back to the central design system team while also ensuring that the unique aspects of their product's user experience are prioritized. By doing this, they can ensure that each product maintains a level of consistency that fits within the overall design framework, while also allowing for the individuality that users appreciate.

This embedded approach not only empowers designers but also creates a sense of shared ownership. When designers feel connected to the products they work on, it cultivates a deeper commitment to delivering quality experiences. They become champions of the design system, advocating for best practices while also having the flexibility to adapt to specific challenges their product faces.

Establish Leadership and Approval Councils

To keep a unified vision across all products while still embracing the flexibility offered by the federated structure, it's important to establish leadership and approval councils. These councils, which consist of senior design managers and directors, ensure that design decisions are in line with the overall goals of the design system. Their purpose isn’t to act as gatekeepers; instead, they facilitate conversations that foster a shared understanding and alignment among everyone involved.

When new ideas or components are proposed, these councils serve as a platform for collaborative evaluation. They provide a space for feedback and refinement, celebrating successful designs and discussing challenges openly. This structure not only enhances the quality of the final outcomes but also strengthens the relationships between teams, making it easier to navigate complexities that arise during the design process.

Encourage Open Contributions from All Roles

One of the most empowering features of the Intuit Design System is its dedication to encouraging contributions from everyone in the organization. This approach creates an inclusive atmosphere where every opinion counts. Whether you're a designer, developer or project manager, your insights and ideas are appreciated. This open-door policy not only drives innovation but also fosters a sense of community around the design system.

By inviting input from various roles, IDS can tap into a wide array of perspectives, leading to stronger and more user-focused designs. This approach fosters a culture where everyone feels a sense of ownership over the success of the design system. Consequently, the design process becomes more lively and adaptable, evolving alongside user needs and business goals. When everyone is invested in the outcome, it boosts the overall effectiveness of the design system and enriches the experiences it offers.

Break Down Components: Atoms, Molecules and Organisms

Let’s dive a bit deeper into how these components come together. Atoms are the simplest elements of the design system. Think about the basic visual properties like buttons, input fields or even color swatches. They might seem trivial on their own, but when combined, they create something more functional.

Let’s take a closer look at molecules, which are formed by combining atoms to create more intricate UI elements. For example, a search bar is made up of an input field (one atom) and a button (another atom). Moving on to organisms, these are collections of molecules that form distinct sections of a user interface. Imagine a card layout that brings together images, text and buttons, all functioning together smoothly. By organizing components in this manner, the design becomes intuitive and can easily adapt as user needs evolve or new features are introduced.

Create Templates and Pages for Consistency

Once you’ve established your atoms, molecules and organisms, the next step is to create templates and pages that bring everything to life. Templates serve as blueprints for different types of pages organizing the components in a way that ensures a seamless user experience. They help set the standard for layout, spacing and hierarchy, so when users navigate between Intuit products, they feel at home.

When it comes to pages, they showcase how these templates come together in real-world scenarios. Each page should have a clear purpose and fulfill specific user goals, whether it’s allowing a user to complete a transaction or access important information. By maintaining this level of consistency across all products, users will find it easier to interact with different Intuit offerings, leading to a more satisfying overall experience.

Build a Unified Naming Council for Design Tokens

One of the foundational steps in effective design token management is establishing a unified naming council. This council's primary goal is to standardize the names of design tokens across different teams and platforms, creating a shared language that everyone can understand. Imagine how confusing it could be if different teams referred to the same color or font by various names. A naming council helps eliminate that confusion, fostering clearer communication and collaboration.

This council is composed of representatives from various design and development teams, ensuring that the naming conventions reflect the needs and perspectives of all stakeholders. By engaging a diverse group, the council can create names that are intuitive and meaningful, making it easier for anyone to pick up and use the design tokens without having to search through documentation or guess what things might mean. The end goal is to build a cohesive design language that resonates across all levels of the organization.

Automate Variant Management and Updates

As the design landscape evolves, so do the requirements for design tokens. Automation plays a pivotal role in managing these variants efficiently. Instead of manually updating tokens across multiple products whenever a change is needed, automated systems can handle these updates seamlessly. This not only speeds up the process but also minimizes the risk of human error.

Using tools like Style Dictionary can be incredibly beneficial in this regard. These tools allow teams to define their tokens in a structured way, making it easier to generate and manage variants based on themes, platforms or even user preferences like light and dark modes. Automation ensures that when a change is made, be it a new color or an adjusted spacing, everyone is on the same page without needing to comb through each product individually to implement the changes. This level of efficiency not only saves time but also helps maintain the integrity of the design system, ensuring that the user experience remains consistent across all touchpoints.

Embed Engineers in Product Teams

Embedding engineers in product teams creates a dynamic environment where collaboration flourishes. It's like having a translator in the room who speaks both design and code. Designers can quickly bounce ideas off their engineering counterparts, leading to faster iterations and fewer miscommunications. For instance, if a designer is experimenting with a new interaction pattern, having an engineer on hand can help determine if that idea is viable or if adjustments need to be made. This immediate feedback loop is invaluable and helps to maintain momentum throughout the development cycle.

This approach also fosters a sense of shared ownership among team members. When engineers are invested in the design process, they’re more likely to support design choices and come up with creative solutions. This collective commitment not only improves the quality of the final product but also strengthens team culture, making everyone feel empowered to share their ideas.

Use Shared Tools and Documentation for Consistency

Consistency really matters in any design system and utilizing shared tools and documentation is key to achieving that. At Intuit, teams make use of common platforms for their design and development tasks, which helps keep everyone aligned. Whether they're working with a design system like the Intuit QuickBooks Design System or using collaborative tools like UXPin, having a centralized hub for resources makes it easy for teams to find the most current information.

Quality documentation is another piece of the puzzle. When designers and developers document their processes, decisions and guidelines, it creates a valuable resource that can be referenced later. This is particularly helpful when onboarding new team members or when teams need to revisit previous projects. By using standardized documentation practices, Intuit fosters a culture of transparency and accountability, allowing everyone to contribute effectively to the design system while ensuring that no one is left guessing about design choices or coding standards.

In essence, enhancing collaboration between designers and developers is about creating an environment where communication flows freely, ideas are exchanged openly and everyone works toward a common goal. By embedding engineers in product teams and utilizing shared tools and consistent documentation, Intuit ensures that their design system evolves seamlessly, benefiting both the creators and the end-users.

Track Component Adoption and Usage Metrics

Keeping tabs on component adoption is all about understanding how design elements are integrated into real-world applications. Metrics like how often a component is used across projects can reveal a lot. For instance, if a particular button style or navigation element isn’t being adopted widely, it may signal that it needs redesigning or that additional training is required for teams to use it effectively.

The Intuit Design System team often looks at usage statistics not only to measure success but also to foster a culture of accountability among designers and developers. When everyone is aware of how their contributions fit into the bigger picture, it creates a sense of ownership and motivation. Plus, these metrics can be showcased to stakeholders to demonstrate the tangible benefits of the design system, making a case for continued investment in its evolution.

Prepare for Future Interfaces Beyond UI

As technology rapidly evolves, the Intuit Design System must also prepare for interfaces that go beyond traditional user interface elements. Emerging platforms such as voice interfaces, augmented reality, and even virtual reality experiences are becoming increasingly important. These new frontiers require a fresh perspective on design principles and a willingness to experiment with different interaction methods.

To stay ahead of the curve, the design team is engaging in research and creating prototypes for future interfaces. This hands-on method allows them to understand how users might interact with these new environments, which helps them incorporate those insights into the design system. This way, they ensure that Intuit products not only meet current user needs but are also prepared to adapt and succeed in a quickly changing tech environment. Their aim is to build a design system that embodies the flexibility and creativity of the products it supports, enhancing user experiences across all platforms.