Design Systems
Joe and the team ride again.
Resideo
Role
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Objective
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Context
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Outcome
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Role
Design Director
Objective
Co-create the first design language put into place across all of IBM’s product portfolio.
Context
Two other Design Principals and I wrote the guide in question. We directed the application of the guide in various contexts.
Outcome
Over 100 products adhered to this design guide, With an initial focus on Color, Typography, and Iconography there was a lot of freedom given to designers.
Intapp
Role
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Objective
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Context
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Outcome
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Role
Design Director.
Objective
Consume the IBM Design Language and leverage it to create a Watson-Specific design language with both Dark and Light modes.
Context
As the use of the IBM Design Language was taking place there was the need to evolve its use within the context of Watson products.
Outcome
A distinct look and feel set Watson apart from its counterparts in other areas of IBM. There was a more refined approach to foreground, middle ground, and background spaces within applications.
Zeroed In
Role
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Objective
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Context
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Outcome
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Role
Design Director.
Objective
Provide guidance along with the Guide, ‘A guide to the guide,’ so to speak.
Context
The act of publishing components wasn’t going to suffice. The organization had over 50 designers, in multiple countries, and was growing. Context needed to be provided.
Outcome
Consistent application of IBM Watson Design Language across all products. This included Layout, Visualizations, Iconography, Color, Buttons, and Animation. Clarity was provided on rules and what was intentionally left to each product team of designers to own.
Cloud Data Services
Role
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Objective
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Context
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Outcome
content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here, content goes here
Role
Design Director.
Objective
Consume the IBM Design Language and leverage it to create a Cloud Data Services-specific dialect. Unify a mix of net-new and legacy product.
Context
Cloud Data products and services needed a differentiated look and feel when compared to other portfolios. Before the guide was created they were not cohesive in look and feel.
Outcome
Over two dozen products and services adhere to this design language. Since not everything in the portfolio had the benefit of having an assigned designer the guide’s website was written with a high degree of instruction.