A design system is a framework of practices that bring designers and products together. It is a platform to identify, and document what to share, whether a visual style, design patterns, front-end UI components, and practices like accessibility, research, content strategy.
The role of design with enterprise organizations is expanding, spreading across product teams and influencing decision-making at higher and higher levels. This scale, paired with the array of devices, browsers, screen sizes, locales, and environments, makes it increasingly challenging to align designers and developers to deliver cohesive user experiences.
In this talk, I’ll discuss the lessons learned, the challenges faced, and best practices for creating and maintaining an effective interface design system.
A design system can vastly improve your team's productivity, but most of all, it leads to better products! The challenge lies in creating a mature system and leading its adoption across the company successfully. Let's talk about how we learned to meet the needs of different designers and developers on different products, on different tech stacks, on different platforms. Attendees will go home with tips they can use to improve design systems of any stage.
The Design System is an essential part of today's UX world which provides agility and performance in the longer term. Atomic Design is a part of Design System for designers and developers to build the parts of a complete design.
Building a Design System: A Practitioner's Case Studyuxpin
- How to build a design system from scratch
- How to audit your product for design consistency
- How to structure and communicate a design system to an Agile team
Evolving your Design System: People, Product, and Processuxpin
You'll learn:
How to create and maintain a design system over several years
How people, process, and product change alongside a design system
Lessons learned from growing the Linkedin design system
Drew has spent the better part of the last two years leading the charge on launching and managing the global design system at AIG. Learn some of the battle-tested tips, tricks, and methods gained during the process including how to:
- Manage contribution and intake
- Manage “snowflake” vs system components
- Support multiple brands with a single system
- Track and measure the ROI of your system
- Perpetuate buy-in
Bio
Drew Burdick is a multi-faceted design leader with over a decade of experience. He founded and led a creative agency, led top accounts at Red Ventures, and most recently helped to transform product design at AIG by leading a team to establish their global design system. He is now a leader with the Experience Design practice at Slalom, helping to drive client engagements in the Charlotte market.
In this talk we’ll uncover our journey in creating a Design System for Skyscanner and share our learnings on how we sold it to the business by proving its worth. We’ll talk through some of the design and tech considerations we’ve made and share the tools and techniques which have helped us along the way.
A design system can vastly improve your team's productivity, but most of all, it leads to better products! The challenge lies in creating a mature system and leading its adoption across the company successfully. Let's talk about how we learned to meet the needs of different designers and developers on different products, on different tech stacks, on different platforms. Attendees will go home with tips they can use to improve design systems of any stage.
The Design System is an essential part of today's UX world which provides agility and performance in the longer term. Atomic Design is a part of Design System for designers and developers to build the parts of a complete design.
Building a Design System: A Practitioner's Case Studyuxpin
- How to build a design system from scratch
- How to audit your product for design consistency
- How to structure and communicate a design system to an Agile team
Evolving your Design System: People, Product, and Processuxpin
You'll learn:
How to create and maintain a design system over several years
How people, process, and product change alongside a design system
Lessons learned from growing the Linkedin design system
Drew has spent the better part of the last two years leading the charge on launching and managing the global design system at AIG. Learn some of the battle-tested tips, tricks, and methods gained during the process including how to:
- Manage contribution and intake
- Manage “snowflake” vs system components
- Support multiple brands with a single system
- Track and measure the ROI of your system
- Perpetuate buy-in
Bio
Drew Burdick is a multi-faceted design leader with over a decade of experience. He founded and led a creative agency, led top accounts at Red Ventures, and most recently helped to transform product design at AIG by leading a team to establish their global design system. He is now a leader with the Experience Design practice at Slalom, helping to drive client engagements in the Charlotte market.
In this talk we’ll uncover our journey in creating a Design System for Skyscanner and share our learnings on how we sold it to the business by proving its worth. We’ll talk through some of the design and tech considerations we’ve made and share the tools and techniques which have helped us along the way.
UI design becomes increasingly important for products and services. Influencing their users' expierence. UX itself determines the value of digital offerings and is their key differentiator. But "historically grown" incoherent interfaces deteriorate value and brand of products and services.
This talk is about design systems, that help to avoid (or overcome) design dept and to enable scaling UX across platforms, products and devices. Modularity and standardisation of repeatedly used aspects helps speeding up processes and increasing business value. Design systems help making user experience tangible to teams and brand values actionable.
The SlideShare presentation consists of the summary of the Design System 101 Workshop, as presented by UX Gorilla with Mayank Dhawan.
Link of the event: https://bit.ly/2RwN4RF
The workshop took place on December 01, 2018 at 91springboard, Jhandewalan Extension, New Delhi.
This event was for designers, developers or members of the product team to help them with a clear understanding and give them useful ideas to make better decisions, help their teams to save time so that they can do things they would enjoy.
Design systems: accounting for quality and scalabilityuxpin
You'll learn:
How Forumone builds and implements design systems for their clients
How to plan, create, sell, and implement a design system
How to use common design tools to build a design system developers will use
Design system presentation - How to sell it internallyEugene Kardash
Design System is a systematic approach to creating and maintaining consistent user interfaces, which coherently communicate the brand values and empower user experience.
This presentation's goal is to give an overview of the current state of design maturity at the company (here, at Herbalife Nutrition), to justify the necessity of having it, and to get buy-ins from decision makers.
Slides for a few events i was lucky to give a talk this year. From my experiences of building a design system for the product team. Figma and storybook js are introduced.
Let's talk about Design Systems and how they could help you build better products in terms of efficiency, consistency, UX, code quality and accessibility.
Summary:
1. About me
2. Why have one?
3. Design system (fundamentals)
4. How to build a design system (process)
5. Cost and value
6. Inspiration
7. Q&A
Design Systems First: Everyday Practices for a Scaleable Design Processuxpin
You'll learn:
- How to create, adopt, and maintain your first design system
- How to practice a “design systems first” process of product development
- How to build and govern a design systems operations team
Creating and Scaling an Enterprise Design Systemuxpin
You'll learn:
- How to create a unified design language for a complex organization.
- How to use the most efficient processes and tools for maintaining the design system.
- How to scale code and interaction patterns across platforms and products.
Trying to build a design system for your project? But still, don't know how to? Then this post gonna teach you how to create the design system for the project!
------------------
Follow me on Instagram to learn more about design
https://www.instagram.com/fazurrehman/
------------------
Understand Design System
A Design System is the single source of truth, which groups all the elements that will allow the teams to design and develop a product even there is lots of benefits to having a design system, but you need to find the right people or company who really need design system or you think you really can solve their business problems by design system!
I will continue the design system in the 2nd post and tell you better understanding and road-map how to build a design system. ⠀
Interested to work with me, let's start working together!
fazurrehman@gmail.com
During this Morgenbooster, we will dive into the understanding of digital design systems, and why they have become increasingly popular.
What are they? How do they work? What will you gain from building one? And last, but not least we will take you through a couple of tangible experiences and journeys of building such a system.
Throughout the talk we will be sharing experiences from both a design and development perspective.
And hopefully we will all have the feeling of getting one step closer to a design system, which meets all the requirements in modern digital design. A system where all services, assets and communications are designed from one central place to evoke both emotions in a coherent brand experience and support the functional necessities of today’s dynamic business strategies.
In today's video, I showed & discussed one of the most anticipated topics! "Design System". Here I talked in detail about the concepts and applications.
The Outcome 2021 Conference
Summary of the talk:
- Intro to design systems and what a design system is made of
- How design systems help businesses to become more efficient
- Process of starting out a design system
- Measuring success and maintenance
Taken from Future of Web Design (#FOWD), London 2015 Conference. http://futureofwebdesign.com/london-2015
Reports are in from Twitter, Medium, and the like; we can’t make full comps, use Photoshop, or even utter the phrase 'visual design' anymore. What’s a designer to do? Has our role evaporated? Fear not! Dan Mall will help redefine the tasks of the modern day designer in light of the multi -device world that snuck up on us.
Building compelling business cases for Design SystemsLaura Van Doore
This talk was originally presented at Web Directions Summit 2018 in sunny Sydney.
Design Systems have reached peak popularity. It’s no secret that the topic of Design Systems have been an outrageously popular topic over the past few years. Every design team has either built one, is building one, or wants to build one. But it’s not designers who we have to convince when it comes to investing in the build of a design system. Especially if we aren’t lucky enough to be in an organisation where design has a ‘seat at the table’. How can we sell the benefits of a design system with more focus on appealing to upper management, who may not see the same benefits we do?
This talk is aimed primarily at designers, but may also interest product managers, front end developers & other roles core to a product team. It will be of most benefit to those who are either looking to introduce a design system into their organisation, or to bolster their case to increase the business investment in an existing design system. The aim of the session is to equip the audience with the right tools & mindset to effectively sell a design system project to higher levels of business function within their organisation.
Implementing a Design System in a Small Team by SnapTravelProduct School
This session will provide a blueprint for how a team of 2 Designers and 3 Frontend engineers can work together, in a lean way, to build and implement a design system within 6 months while still working on other important company initiatives/features.
UI design becomes increasingly important for products and services. Influencing their users' expierence. UX itself determines the value of digital offerings and is their key differentiator. But "historically grown" incoherent interfaces deteriorate value and brand of products and services.
This talk is about design systems, that help to avoid (or overcome) design dept and to enable scaling UX across platforms, products and devices. Modularity and standardisation of repeatedly used aspects helps speeding up processes and increasing business value. Design systems help making user experience tangible to teams and brand values actionable.
The SlideShare presentation consists of the summary of the Design System 101 Workshop, as presented by UX Gorilla with Mayank Dhawan.
Link of the event: https://bit.ly/2RwN4RF
The workshop took place on December 01, 2018 at 91springboard, Jhandewalan Extension, New Delhi.
This event was for designers, developers or members of the product team to help them with a clear understanding and give them useful ideas to make better decisions, help their teams to save time so that they can do things they would enjoy.
Design systems: accounting for quality and scalabilityuxpin
You'll learn:
How Forumone builds and implements design systems for their clients
How to plan, create, sell, and implement a design system
How to use common design tools to build a design system developers will use
Design system presentation - How to sell it internallyEugene Kardash
Design System is a systematic approach to creating and maintaining consistent user interfaces, which coherently communicate the brand values and empower user experience.
This presentation's goal is to give an overview of the current state of design maturity at the company (here, at Herbalife Nutrition), to justify the necessity of having it, and to get buy-ins from decision makers.
Slides for a few events i was lucky to give a talk this year. From my experiences of building a design system for the product team. Figma and storybook js are introduced.
Let's talk about Design Systems and how they could help you build better products in terms of efficiency, consistency, UX, code quality and accessibility.
Summary:
1. About me
2. Why have one?
3. Design system (fundamentals)
4. How to build a design system (process)
5. Cost and value
6. Inspiration
7. Q&A
Design Systems First: Everyday Practices for a Scaleable Design Processuxpin
You'll learn:
- How to create, adopt, and maintain your first design system
- How to practice a “design systems first” process of product development
- How to build and govern a design systems operations team
Creating and Scaling an Enterprise Design Systemuxpin
You'll learn:
- How to create a unified design language for a complex organization.
- How to use the most efficient processes and tools for maintaining the design system.
- How to scale code and interaction patterns across platforms and products.
Trying to build a design system for your project? But still, don't know how to? Then this post gonna teach you how to create the design system for the project!
------------------
Follow me on Instagram to learn more about design
https://www.instagram.com/fazurrehman/
------------------
Understand Design System
A Design System is the single source of truth, which groups all the elements that will allow the teams to design and develop a product even there is lots of benefits to having a design system, but you need to find the right people or company who really need design system or you think you really can solve their business problems by design system!
I will continue the design system in the 2nd post and tell you better understanding and road-map how to build a design system. ⠀
Interested to work with me, let's start working together!
fazurrehman@gmail.com
During this Morgenbooster, we will dive into the understanding of digital design systems, and why they have become increasingly popular.
What are they? How do they work? What will you gain from building one? And last, but not least we will take you through a couple of tangible experiences and journeys of building such a system.
Throughout the talk we will be sharing experiences from both a design and development perspective.
And hopefully we will all have the feeling of getting one step closer to a design system, which meets all the requirements in modern digital design. A system where all services, assets and communications are designed from one central place to evoke both emotions in a coherent brand experience and support the functional necessities of today’s dynamic business strategies.
In today's video, I showed & discussed one of the most anticipated topics! "Design System". Here I talked in detail about the concepts and applications.
The Outcome 2021 Conference
Summary of the talk:
- Intro to design systems and what a design system is made of
- How design systems help businesses to become more efficient
- Process of starting out a design system
- Measuring success and maintenance
Taken from Future of Web Design (#FOWD), London 2015 Conference. http://futureofwebdesign.com/london-2015
Reports are in from Twitter, Medium, and the like; we can’t make full comps, use Photoshop, or even utter the phrase 'visual design' anymore. What’s a designer to do? Has our role evaporated? Fear not! Dan Mall will help redefine the tasks of the modern day designer in light of the multi -device world that snuck up on us.
Building compelling business cases for Design SystemsLaura Van Doore
This talk was originally presented at Web Directions Summit 2018 in sunny Sydney.
Design Systems have reached peak popularity. It’s no secret that the topic of Design Systems have been an outrageously popular topic over the past few years. Every design team has either built one, is building one, or wants to build one. But it’s not designers who we have to convince when it comes to investing in the build of a design system. Especially if we aren’t lucky enough to be in an organisation where design has a ‘seat at the table’. How can we sell the benefits of a design system with more focus on appealing to upper management, who may not see the same benefits we do?
This talk is aimed primarily at designers, but may also interest product managers, front end developers & other roles core to a product team. It will be of most benefit to those who are either looking to introduce a design system into their organisation, or to bolster their case to increase the business investment in an existing design system. The aim of the session is to equip the audience with the right tools & mindset to effectively sell a design system project to higher levels of business function within their organisation.
Implementing a Design System in a Small Team by SnapTravelProduct School
This session will provide a blueprint for how a team of 2 Designers and 3 Frontend engineers can work together, in a lean way, to build and implement a design system within 6 months while still working on other important company initiatives/features.
Zeeto Tech Exchange: Design for Scalability - UXZeetoSlides
Zeeto is a technology platform that makes online properties and mobile apps money by asking their visitors smart questions and using their answers to display high-value ads.
The Zeeto Tech Exchange is a leading San Diego tech community group that meets on a monthly basis to discuss, debate and network. "Design for Scalabality" was presented in February 2017.
Making security software is hard. Making lots of security products is harder. Making lots of security products with a great and consistent user experience is, well, nigh on impossible. But it can be done. In this presentation you will find out exactly how to deliver not just the best security technology to your customers, but also a pretty darn good user experience to boot. And even more importantly, how you, as a designer, can personally contribute to making it even better!
As a PO, product designer, or PM, you've probably already thought about the possible benefits of building a design system for your organisation. And surely as all teams, like us, you kept asking yourself:
How do we start it?
But here are some guidelines to help you clarify how to start a DS.
Analyze the way Software Projects are developed among Distributed teams highlighting the various hurdles, a typical Distributed team may face, including the solutions and the most appropriate tools to help overcome those challenges
Analyzed the way Software Projects are developed among Distributed teams, and highlighted the various hurdles, a typical Distributed team may face, including the solutions and the most appropriate tools to help overcome those challenges, and explained how these tools help solve those problems.
Model-driven and low-code development for event-based systems | Bobby Calderw...HostedbyConfluent
It's a dream as old as business computing: the ability to create a graphical model and then to deploy it as a working information system. Many attempts to realize this dream have come and gone with varying degrees of success, from visual programming languages like Visual Basic and Scratch, to business workflow systems like BPMN and its proprietary commercial variants, to engineering-focused systems like UML.
But let's face it: most low-code and model-based application development tools fall far short of the needs of modern software development teams. At best, they're useful for rapidly testing ideas and creating prototypes. At worst, they're used by "citizen coders" to cynically circumvent good engineering practices, with IT operations left holding the bag of operating, securing, and scaling black-box applications that cut against modern DevSecOps practices.
Event-driven application architecture, enabled by infrastructure like Kafka and its ecosystem, has the potential to dramatically advance toward the age-old, model-driven and low-code dream. But what would an event-centric and developer-friendly low-code look like?
This talk will outline strategies for low-code and model-driven development based on Event Modeling. We'll explore how event-driven application architecture provides a simple yet robust framework for generating DevSecOps-friendly code for the UI, for the web services layer, and for event-processing.
This is take two of the presentation, some things added, some removed, but still the regurgitation is best..
The purpose is to raise your awareness of software architecture in light of modern day agile development. Disciplines to incorporate and reconsider
Design Systems have reached peak popularity. It seems that every design team has either built one, is building one, or wants to build one. With the release of the incredible Nested Symbols feature followed by Sketch Libraries just a few months ago, Sketch has emerged as an essential part of the Design System workflow.
In this talk we will be covering:
• Best of breed Design Systems out in the wild
• Demo of the Design System from FathomHQ
• Exploring essential Sketch plugins & tools for a seamless workflow
• Handy hacks for getting your Design System project rolling
• Roll out strategies for Design Systems
About Laura
Laura is a Senior Product Designer at Fathom, a B2B SaaS product in the fintech domain. Over the last nine years, she has worked her way through design and UX roles in a variety of environments, from small agencies to corporate giants. Her experience includes creating digital solutions for travel, government, SaaS, health, fintech, real estate and ecommerce. Laura has a natural curiosity for solving 'people problems’, which makes her a passionate advocate for unravelling complexity, measuring UX, and crafting design systems.
If you're thinking about migrating from TFS on-premises to VSTS, it's not necessarily a simple decision as to how to get there. During this briefing we discussed some of the considerations that lead you to the right migration path, gotchas that we have encountered, and how we can help you get to VSTS quickly and effectively.
Microservices at Scale: How to Reduce Overhead and Increase Developer Product...DevOps.com
As a cloud native application grows in size—more microservices, more dependencies, more teams—there’s a corresponding increase in…
Complexity: Over time, the application becomes a lot harder for a single developer to reason about and contribute to. Staying on top of READMEs and managing cross-team communication is practically a full-time job.
Scaling challenges: The reality of building, deploying, and testing a 100+ service distributed application means developers are going to spend a lot of time sitting around waiting.
But it doesn’t have to end up this way, and there are concrete steps that DevOps engineers can take to keep their developers moving quickly even as an application grows. In this webinar, we’ll show you how to use open source products to:
Make it easy for your developers to code and run on-demand tests against a production-like environment—without having to constantly deal with the complexity that comes with a large application
Codify the relationship between all your services and tests, making your system self-documented and easy to understand
Keep your integration tests running fast so that devs can more easily write and debug their tests and get the quick feedback loops they need
Facilitate remote, in-cluster development and give every developer their own isolated namespace—and never again ask a developer to deploy the application on their laptop
First users: Heuristics for designer/developer collaborationJonathan Abbett
From the University of Illinois Web Conference 2013.
Ask a web designer who his “first users” are, and he’ll probably name early adopters, stakeholders, or usability testers. Designers rarely consider their actual first users: the web developers they work with to build their designs. Over the last year, I’ve performed an informal user research project where the “users” were software development teams of all shapes and sizes. Drawing on these discussions and my background as a former web developer, I’ve created a set of friendly heuristics (in the tradition of Jakob Nielsen and Louis Rosenfeld) that designers can use to make their design materials far more useful for developers. I’ll show how these heuristics will encourage holistic solutions rather than piecemeal design work, surface critical implementation issues sooner, and establish a stronger basis for designer/developer collaboration.
SEF 2014 - Responsive Design in SharePoint 2013Marc D Anderson
Presented with Christian Ståhl
Everyone is talking about responsive design. But are you really ready to bring SharePoint to mobile and tablets? While you may have an idea of what your site will look like when finished, there are many basic concepts and pitfalls that aren’t always outlined in the “How To’s”.
In this session, we will go through foundational steps to planning a responsive SharePoint site including how to handle a hybrid content scenario that uses publishing and team sites. You will learn what tools and templates can make your life easier during design, build and testing. If you are excited about the capability of bringing SharePoint to any device but not sure where to start, check out this session to get the foundational understanding of the concept, best practices and examples to get you started.
XP teams try to keep systems fully integrated at all times, and shorten the feedback cycle to minutes and hours instead of weeks or months. The sooner you know, the sooner you can adapt.
Watch our record for the webinar "Continuous Integration" to explore how Azure DevOps helps us in achieving continuous feedback using continuous integration.
Similar to Design Systems: Enterprise UX Evolution (20)
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
11. “But I build applications, not
Legos…”
I KNOW WHAT YOU’RE THINKING
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22. • Need to look and behave similarly
• Implement similar UI components
• Duplicate low-level functionality
• Must be white-labeled or themed
• Are built on different tech stacks
• Suffer from visual regression bugs
A Design System will provide value if your products…
D O I N E E D A D E S I G N S Y S T E M ?
23. • Provide a single source of truth for building UIs
• Save time and money
• Increase consistency
• Decrease maintenance
• UX teams focus on the experience; dev teams on
implementation
• Improve user experience through well-defined
and learned behaviors
BENEFITS OF A
DESIGN SYSTEM
32. WHY NOT?
• Those are rapid prototyping tools, not
design systems
• Their components do not consider your
unique context
• Not detailed enough
• You take power away from your
developers
• You are beholden to their timeline and
community
B O O T S T R A P O R F O U N D AT I O N
34. Pattern Library
UI Components, Page Templates, Reference Files
(.psd, .ai, .sketch)
Code
Coding Standards, Supported Browsers and Devices, Versioning,
Pattern Implementation
Brand Identity
Fonts, Colors, Meaning, Visual Language,
White Labeling Logo/marketing related
Editorial Guidelines
Voice and Tone, Word List, Capitalization and
Punctuation
Foundations and Principles
Guiding Design Principles, Accessibility
Targets, Animations, Scaling, Grids
35. “A Design System isn't a project. It
is a product, serving products.”
A design system is not simply a style guide. It is a living thing whose value is realized only
when products successfully implement the patterns of the system.
Nathan Curtis
Design System Evangelist
37. • Check up to 25 components you feel are most important to include
in the first version of the design system.
• Cross out at least two sections you think are unnecessary or
unimportant for your applications.
• Add a star by up to five components that you should expect to
spend extra effort getting right.
Participants:
Identify components
with a checklist
1A simple checklist can quickly identify which
components are essential to an organization.
38. The cut-up gives visibility on how you are doing
things today, and the level of complexity a
component needs to accommodate.
2Cut-up components
from various interfaces
• Organize and print out screenshots from the existing site and/or
applications
• Create categorized sections (forms/buttons/navigation/etc.) based
on the component checklist
• Participants cut up each page into components, separating
components into their assigned category
• This exercise generates momentum, brings clarity, and trims fat
39.
40. Before you start designing components,
you need to establish a base.
• Establish low-level design principles
• Start with color, typography, iconography, units of
measure, grids, spacing
• Align on what you are going to name each component
3Lay a solid foundation
for your components
41. Rebuild each of your UI components, one
at a time, from the ground up.
• Identify the smallest pieces and build from there
• Define which pieces inform others
• Write down reasons why you made certain
design decisions
4Design components
from scratch
42. For a design system to thrive and survive,
it needs a sufficient level of management
and organization.
• Create the order for when you are going to tackle each
component
• Schedule weekly reviews with stakeholders and
developers
• Establish long-term governance
5Work closely with
your team
44. Your Software’s Context
You cannot simply design whatever you want. Take into account all
of the software you have today when designing, and frequently
refer back to the results of the component cut up for reference.
Your Users
Who are you designing for? Are your users bank tellers, auto
mechanics, grandparents? How are they accessing your software?
For how many hours a day? Remember that designers and devs are
also users of the design system.
45. • Modern vs. legacy web browsers
• Native/web hybrid
• Native desktop app for Mac/Windows
• Native mobile app for iOS/Android
Which devices/environments do you need
to support?
Device Support
• Mobile
• Tablet
• Desktop
• Large Screens
• 4K/Retina
• Watch
What are your responsive breakpoints?
How does that affect our component design?
Responsive
46. • Create flexible systems that consider the
experiences of people with disabilities from
the start
• Maintain reasonable contrast ratio between
text and background colors
• 4:5:1 for small text
• 3:1 for large text
• Use online tools
• wave.webaim.org
• colorsafe.co
• hexnaw.com
Do you need Section 508 and WCAG 2.0
compliance?
Accessibility
• Make your CSS highly configurable
• Select smart defaults by making the contrast
between colors as high as possible
• Leverage color algorithms in your CSS
preprocessor for dummy-proof color schemes
• Consider providing a Light UI or Dark UI for
different environments
Does your experience need to be easily
themed or rebranded?
White-Label
47. • Nothing – the component exists but hasn’t started
• Loading – waiting for the component to render
• None – the component has initialized, but it’s empty
• One – you have some data
• Some – the ideal state for this component
• Too Many – Too many results/characters/etc.
• Incorrect/Correct – success/error
• Done – correct input has been received
Designing for all states
• Active/Hover/Focus – elements that can be interacted with
50. A Design System is not an application framework and
should not be coupled to one.
Build self-contained components
• Create a prescriptive application template
• Build on or for one particular framework
DO NOT
• Focus on building long-lasting vanilla HTML/CSS/JS
• Keep your components “dumb”
• Consider all your systems
DO
Enable faster and more consistent developmentYOUR GOAL:
51. Provide useful assets and comprehensive documentation
of how and when to use each component in the system.
Deliver obvious value
Enable faster and more consistent developmentYOUR GOAL:
• Define required HTML structure
• Include production-ready CSS and JS
• Be semantic and accessible
• Make components configurable
• Ensure consistency
60. Central
Repository
ROLL IT OUT
Ensure adoption by making your Design System
easy to consume and update.
Publish multiple ways Make it collaborative
Update frequently Ensure reliability
61. A design system can be a large
investment of time and money,
but it pays clear dividends.
SELLING DESIGN SYSTEMS
62. http://www.usability.gov/what-and-why/benefits-of-ucd.html
*Benefits of User Centered Design
$1,652,400 annual savings or 21.25%time saved
Assumptions are in back up slides.
(x hrs)*($4050.00)*(48 weeks) = annual savings
100 devs
each save 2 hrs
per week
=
$388,800
annual savings*
100 devs
each save 30 min
per week
=
$97,200
annual savings*
100 devs
each save 5 hrs
per week
=
$972,000
annual savings*
100 devs
each save 1 hr
per week
=
$194,400
annual savings*
Time saved
when art direction
isn’t needed
Time saved
from rework
Time saved
when components
are compatible
Time saved
when assets
are available
63. adapted from an article written by Josh Clark at Big Medium
BEFORE AFTER
64. • Less, more productive meetings
• More alignment and collaboration
• More formalized processes
• Change in company culture to working
smarter, not harder
• Confidence that design will be
implemented correctly the first time
• Teams are less overwhelmed and not in
perpetual fire fighting mode
• Teams that are already stretched to
capacity will increase speed and quality
Dev
UX
Design
Brand
Strategy &
Insights
Digital
Marketing
Analytics
Design
System
DIGITAL TEAMS
DAY TO DAY IMPACT
65. Dev
UX
Design
Brand
Strategy &
Insights
Digital
Marketing
Analytics
Design
System
• Provide a single source of truth for
building UIs
• Save time and money
• Increase consistency
• Decrease maintenance
• UX teams focus on the experience, dev
teams on implementation
• Improve user experience through well-
defined and learned behaviors
DIGITAL TEAMS
BUSINESS IMPACT