- Useful technology and frameworks for a scalable design system
- How to create a design systems process from scratch
- How to collaborate with developers in a design system
This document discusses the use of design systems and collaboration between designers and developers. It includes quotes and links about topics like Gantt charts, limiting design options through standards like the 8-point grid, using JSON configuration files to separate design from code, and RACI responsibility matrices to clarify roles. The overall message is that design and development work best as collaborative, multi-disciplinary partnerships.
The document discusses the goals and learnings from a design system mission to enable teams to create straightforward user experiences. It notes that the tension between product and design system goals is healthy. Key learnings include looking at existing products, synthesizing information to move forward, focusing on experiences rather than just components, and building the design system like a product. The document also outlines different models for how a design system can be built and aligned with product roadmaps.
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
Balancing UX Consistency and Developer Productivity in a Design Systemuxpin
You'll learn:
How to structure, govern, and maintain a design system
How to improve design consistency, productivity, and quality with React
How to avoid design debt in short-term and long-term projects
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.
Initiating and Sustaining Design Systems for the Enterpriseuxpin
1. The document discusses athenahealth's efforts to establish an enterprise design system called Forge to improve design quality, velocity, and consistency across their 200+ product teams.
2. It outlines the challenges of the current state including design debt and wasted time recreating common interfaces.
3. The goals of Forge include focusing designer time on higher-value work, establishing design standards and guidelines, and enabling greater code and design reuse across teams.
How to create new processes to sustain a design system
How to evolve the way companies build and ship products
How to decide on a governance model for design systems
Design Spikes for the Dual-Track Agile Processuxpin
You'll learn:
How to fit design spikes into a Scrum framework
How to address user stories without neglecting UX strategy
How to solve design problems before they become development issues
This document discusses the use of design systems and collaboration between designers and developers. It includes quotes and links about topics like Gantt charts, limiting design options through standards like the 8-point grid, using JSON configuration files to separate design from code, and RACI responsibility matrices to clarify roles. The overall message is that design and development work best as collaborative, multi-disciplinary partnerships.
The document discusses the goals and learnings from a design system mission to enable teams to create straightforward user experiences. It notes that the tension between product and design system goals is healthy. Key learnings include looking at existing products, synthesizing information to move forward, focusing on experiences rather than just components, and building the design system like a product. The document also outlines different models for how a design system can be built and aligned with product roadmaps.
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
Balancing UX Consistency and Developer Productivity in a Design Systemuxpin
You'll learn:
How to structure, govern, and maintain a design system
How to improve design consistency, productivity, and quality with React
How to avoid design debt in short-term and long-term projects
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.
Initiating and Sustaining Design Systems for the Enterpriseuxpin
1. The document discusses athenahealth's efforts to establish an enterprise design system called Forge to improve design quality, velocity, and consistency across their 200+ product teams.
2. It outlines the challenges of the current state including design debt and wasted time recreating common interfaces.
3. The goals of Forge include focusing designer time on higher-value work, establishing design standards and guidelines, and enabling greater code and design reuse across teams.
How to create new processes to sustain a design system
How to evolve the way companies build and ship products
How to decide on a governance model for design systems
Design Spikes for the Dual-Track Agile Processuxpin
You'll learn:
How to fit design spikes into a Scrum framework
How to address user stories without neglecting UX strategy
How to solve design problems before they become development issues
UXPin: State of the Union Product Keynote by Marcin Trederuxpin
How UXPin unifies design with code in design systems
Recent design system features in UXPin alongside roadmap
Predictions for the future of design tools.
What do you get when user experience drives the agile process? Dual-Track Agile, where the features of the product are discovered alongside the development of the product itself. This session will explain what dual-track agile is, the benefits of dual-track agile, the role of UX, and what to expect. It will focus on the discovery cycle, the role of validated hypotheses and assumptions and how UX uniquely contributes to this invaluable process.
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.
UX, DX, DSX: Developers and Data Scientists as UsersUXDXConf
More and more companies nowadays are investing heavily in building infrastructure for developers and data scientists. But often, building infrastructure products are treated as pure engineering practices and differentiated from feature products.
I would like to share my experience leading a team at BuzzFeed in building user-centric infrastructure products for our developers and data scientists, and how I integrate and adapt traditional PM techniques for technical products.
Building software for our peers is a double-edged sword. On one hand, our users are technologists themselves and have immense appreciation for well-designed infrastructure and tools. On the other hand, it is very tempting for us as developers to make assumptions about those folks with whom we work closely. When building tools for data scientists, it is especially crucial to keep in mind that they have their own distinct workflows and needs.
The document discusses building scalable design systems. It notes that design teams are growing, problems are more complex, and teams are distributed. Maintaining design debt can fracture the user experience. A design system, defined as a reusable set of components governed by standards, can help by providing consistency, communication, efficiency, maintainability, and scalability. The document outlines components of a design system and benefits. It shows examples from companies and tools for design systems. It discusses approaches to starting a design system like inventorying existing design, structuring the system, and standardizing. It also notes design systems require ongoing extension and maintenance.
Presented at UX Scotland in Edinburgh on 6/8/2016. Many of us are thrust into an Agile Development world. How do we do our best UX in a process designed by developers? Where do we belong and how do we work within a Scrum team?
The document discusses challenges faced by design teams and proposes adopting engineering best practices to improve collaboration, engagement, and productivity. It identifies six challenges design teams often face: designers focusing on individual craft; designing in a vacuum; low perceived productivity when files are shared; lack of open communication; lack of transparency in others' work; and constant hustle with no reflection. To address these, the document recommends practices like partner designing, peer reviews, source file control, regular design standups, show-and-tell sessions, and design retrospectives. The outcomes of implementing these practices on one team included improved collaboration, engagement, and productivity as well as a visibly better culture and morale.
Get hands-on advice for rapid Agile prototyping in a product team.
You'll learn:
- How to determine the right depth and breadth for MVP prototypes.
- How to prioritize use cases for prototyping.
- How to elicit the right stakeholder and user feedback.
- How to correctly annotate prototypes for dev and QA.
Slides Ari Tiktin recently used in his discussion w/ mentees of The Product Mentor.
The Product Mentor is a program designed to pair Product Mentors and Mentees from around the World, across all industries, from start-up to enterprise, guided by the fundamental goals…Better Decisions. Better Products. Better Product People.
Throughout the program, each mentor leads a conversation in an area of their expertise that is live streamed and available to both mentee and the broader product community.
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.
How large companies can be as fast and agile as the successful startups? And what is MVP and Dual-track Agile, anyway? We are to discuss a real case of implementation of some methods of Lean Startup and Customer Development in Kaspersky Lab.
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
Iterate quickly with a prototype you can testNicole Capuana
A hands-on workshop where you will pair up and sketch a design for a mobile app. You will turn those sketches into a clickable prototype and draft a usability test. Don’t worry, you don’t have to be a designer to do this. If you can draw a square, circle, line, and a triangle, you’ll do fine.
We’ll review prototype tools, how to structure a test, and why this approach can help you validate, experiment and learn fast.
Most businesses fail within the first year or two. How do you improve your odds of success? We’ll review the magic in learning loops, how to understand your users and customer development, and what you need in team dynamics to drive your startup forward and point you in a more successful direction.
By Nick Barendt & Nicole Capuana
This document summarizes a presentation by Matteo Cavucci and Emanuela Damiani on design and product development. They discuss how the web has changed since 2007 and the need for more modular and flexible approaches. Traditional linear product development processes are no longer effective. Instead, companies should adopt agile and design thinking approaches, focus on user research and experimentation, and view design as a continuous and collaborative process rather than something that ends at launch. Designers and organizations need new tools and structures like "DesignOps" to support experimentation, automation, and continuous learning and improvement.
The document discusses how UX practitioners can adopt an agile mindset and work within agile frameworks. It outlines key agile concepts and compares traditional vs. agile development lifecycles. It also provides an example project timeline to illustrate how UX and development tasks are interleaved. The presentation emphasizes that agile is about people over process and advocates evolving design documents alongside software development through iterative conversations.
Contributing to Drupal: It's Not as Hard as it LooksKarl Kaufmann
This document provides an introduction to contributing to Drupal with no programming experience. It outlines the basic tools needed like Git and Drupal core, how to get started with novice issues and documentation work, resources for help like core mentoring hours, and ways to get involved through local meetups or starting your own events. The goal is to show that contributing is accessible and can deepen your Drupal knowledge and skills while helping clients and the community.
You'll learn:
- How to run the right research on tight timelines
- How to plan research while still designing
- How object-oriented UX can improve the Agile process
Building Sustainable Software: An Introduction to Software EngineeringMuhammad Shehata
Introduction to software engineering and project management methodologies like Waterfall and Agile. In addition to discussing some practices and tools like Version Control Systems, CI/CD, Code reviews and testing strategies.
UXPin: State of the Union Product Keynote by Marcin Trederuxpin
How UXPin unifies design with code in design systems
Recent design system features in UXPin alongside roadmap
Predictions for the future of design tools.
What do you get when user experience drives the agile process? Dual-Track Agile, where the features of the product are discovered alongside the development of the product itself. This session will explain what dual-track agile is, the benefits of dual-track agile, the role of UX, and what to expect. It will focus on the discovery cycle, the role of validated hypotheses and assumptions and how UX uniquely contributes to this invaluable process.
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.
UX, DX, DSX: Developers and Data Scientists as UsersUXDXConf
More and more companies nowadays are investing heavily in building infrastructure for developers and data scientists. But often, building infrastructure products are treated as pure engineering practices and differentiated from feature products.
I would like to share my experience leading a team at BuzzFeed in building user-centric infrastructure products for our developers and data scientists, and how I integrate and adapt traditional PM techniques for technical products.
Building software for our peers is a double-edged sword. On one hand, our users are technologists themselves and have immense appreciation for well-designed infrastructure and tools. On the other hand, it is very tempting for us as developers to make assumptions about those folks with whom we work closely. When building tools for data scientists, it is especially crucial to keep in mind that they have their own distinct workflows and needs.
The document discusses building scalable design systems. It notes that design teams are growing, problems are more complex, and teams are distributed. Maintaining design debt can fracture the user experience. A design system, defined as a reusable set of components governed by standards, can help by providing consistency, communication, efficiency, maintainability, and scalability. The document outlines components of a design system and benefits. It shows examples from companies and tools for design systems. It discusses approaches to starting a design system like inventorying existing design, structuring the system, and standardizing. It also notes design systems require ongoing extension and maintenance.
Presented at UX Scotland in Edinburgh on 6/8/2016. Many of us are thrust into an Agile Development world. How do we do our best UX in a process designed by developers? Where do we belong and how do we work within a Scrum team?
The document discusses challenges faced by design teams and proposes adopting engineering best practices to improve collaboration, engagement, and productivity. It identifies six challenges design teams often face: designers focusing on individual craft; designing in a vacuum; low perceived productivity when files are shared; lack of open communication; lack of transparency in others' work; and constant hustle with no reflection. To address these, the document recommends practices like partner designing, peer reviews, source file control, regular design standups, show-and-tell sessions, and design retrospectives. The outcomes of implementing these practices on one team included improved collaboration, engagement, and productivity as well as a visibly better culture and morale.
Get hands-on advice for rapid Agile prototyping in a product team.
You'll learn:
- How to determine the right depth and breadth for MVP prototypes.
- How to prioritize use cases for prototyping.
- How to elicit the right stakeholder and user feedback.
- How to correctly annotate prototypes for dev and QA.
Slides Ari Tiktin recently used in his discussion w/ mentees of The Product Mentor.
The Product Mentor is a program designed to pair Product Mentors and Mentees from around the World, across all industries, from start-up to enterprise, guided by the fundamental goals…Better Decisions. Better Products. Better Product People.
Throughout the program, each mentor leads a conversation in an area of their expertise that is live streamed and available to both mentee and the broader product community.
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.
How large companies can be as fast and agile as the successful startups? And what is MVP and Dual-track Agile, anyway? We are to discuss a real case of implementation of some methods of Lean Startup and Customer Development in Kaspersky Lab.
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
Iterate quickly with a prototype you can testNicole Capuana
A hands-on workshop where you will pair up and sketch a design for a mobile app. You will turn those sketches into a clickable prototype and draft a usability test. Don’t worry, you don’t have to be a designer to do this. If you can draw a square, circle, line, and a triangle, you’ll do fine.
We’ll review prototype tools, how to structure a test, and why this approach can help you validate, experiment and learn fast.
Most businesses fail within the first year or two. How do you improve your odds of success? We’ll review the magic in learning loops, how to understand your users and customer development, and what you need in team dynamics to drive your startup forward and point you in a more successful direction.
By Nick Barendt & Nicole Capuana
This document summarizes a presentation by Matteo Cavucci and Emanuela Damiani on design and product development. They discuss how the web has changed since 2007 and the need for more modular and flexible approaches. Traditional linear product development processes are no longer effective. Instead, companies should adopt agile and design thinking approaches, focus on user research and experimentation, and view design as a continuous and collaborative process rather than something that ends at launch. Designers and organizations need new tools and structures like "DesignOps" to support experimentation, automation, and continuous learning and improvement.
The document discusses how UX practitioners can adopt an agile mindset and work within agile frameworks. It outlines key agile concepts and compares traditional vs. agile development lifecycles. It also provides an example project timeline to illustrate how UX and development tasks are interleaved. The presentation emphasizes that agile is about people over process and advocates evolving design documents alongside software development through iterative conversations.
Contributing to Drupal: It's Not as Hard as it LooksKarl Kaufmann
This document provides an introduction to contributing to Drupal with no programming experience. It outlines the basic tools needed like Git and Drupal core, how to get started with novice issues and documentation work, resources for help like core mentoring hours, and ways to get involved through local meetups or starting your own events. The goal is to show that contributing is accessible and can deepen your Drupal knowledge and skills while helping clients and the community.
You'll learn:
- How to run the right research on tight timelines
- How to plan research while still designing
- How object-oriented UX can improve the Agile process
Building Sustainable Software: An Introduction to Software EngineeringMuhammad Shehata
Introduction to software engineering and project management methodologies like Waterfall and Agile. In addition to discussing some practices and tools like Version Control Systems, CI/CD, Code reviews and testing strategies.
Developer Productivity Engineering with GradleAll Things Open
Presented by: Justin Reock & Sterling Greene
Presented at the All Things Open 2021
Raleigh, NC, USA
Raleigh Convention Center
Abstract: In 2007, Hans Dockter invented the Gradle Build Tool because he felt that developers deserved less friction in their toolchain. The prevailing build technologies of the time were adequate but inefficient, not taking advantage of possible acceleration technologies and, with some exceptions, very limited in their language and framework support. Gradle is now one of the most widely used build tools available, downloaded about 25 million times a month as of September of 2021. It’s the default build tool in Android Studio, and is trusted by millions of developers to create their artifacts quickly and cleanly.
The principles that originally guided the Gradle build tool towards its current popularity have continued into an emerging practice known as Developer Productivity Engineering or DPE. DPE is a new software development practice that uses acceleration technologies to speed up the software build and test process and data analytics to optimize the impact of acceleration technologies and make troubleshooting more efficient. Leading technology companies are using this practice today to accelerate feedback cycles by over 90% in some cases, improving the developer experience and increasing team velocity.
Join Sterling Greene, Lead Software Engineer for the Gradle Build Tool, and Justin Reock, Field CTO of Gradle Enterprise, to learn why DPE is swiftly becoming the most important movement in software development since the introduction of DevOps.
Attendees will walk away from this presentation with a better understanding of:
● The importance of fast feedback cycles and how to achieve them using build and test acceleration technologies
● Using build and test data to make troubleshooting and problem root cause determination more efficient.
● The importance of leveraging failure analytics to improve toolchain reliability, including managing avoidable failures like flaky tests.
● How to continuously improve performance and guard against regressions through trend and metric observability.
● The Cost of Inaction (CoI) by not investing in developer productivity across your local build environments and CI/CD pipelines in terms of engineering cost, TTM and software quality.
● How to elevate the strategic priority of DPE in your organization.
Metodologías agiles de desarrollo de softwareJuan Gomez
This document discusses agile software development methodologies. It begins by defining what agile development is not, such as cowboy coding or not following a process. It then explains several common agile methodologies like Scrum, XP, FDD, and Kanban. For each methodology it outlines key practices and processes. The document aims to dispel myths around agile development and explain how agile methodologies can be implemented effectively in projects while still adhering to good practices and standards like CMMI.
When setting up a new project we have some tips and tricks to help you do this in the best way possible, incl. infrastructure, database, standard attributes, logging, code alignment, and service center.
Managing a team and project are quite synonymous. Especially, teams require effective distribution of responsibility / roles. Once that is setup, a proper process guides people to make progress. All this fits into a product lifecycle, which is essential to develop the right product, in the right way, and deliver it at the right time.
Don’t Let Process Hold You Back: Best Practices for Cross-Functional Collabor...Tasktop
Creating great software takes many skilled people. There’s business requirements to fulfill, technical requirements to consider, development, testing, packaging, and the release.
While having a single cohesive process is crucial to helping all these teams work together, they’re often working in disparate systems with their own processes and workflows. What’s more, these teams are often spread across different departments, buildings and even time zones.
How can you ensure your teams stay in sync and create better processes that allow individual teams to move fast and be agile, while maintaining effective cross-team collaboration? In this webinar with GitLab, we discuss how establishing a ‘single source of truth’ is critical to functional collaboration, and cover the best practices for:
- Building processes that yield better results
- Keeping cross-functional teams in sync
- Integrating tools for better workflows
- Tips for remote teams
One of the main hindrances to teams being able to respond rapidly to new features are technical problems resulting from bad coding practices, also known as technical debt. Melissa and Brett will cover Agile tools and practices that help development teams write better code and increase maintainability. Topics that will be covered include:
Pair programming
Automated Unit Testing
Refactoring
Test-Driven Development
Agile Architecture
Software development myths that block your careerPiotr Horzycki
During 15 years of my software development career, I was a victim of numerous myths and fads of the IT industry. "We must have Scrum", "Rewrite everything", Hype-Driven Development, 100% test coverage - just to name a few. You'll learn where do these myths come from, why they're wrong and what are the real-world, battle-tested alternatives. You can skyrocket your career just by focusing on the right things!
In Agile development, architects still play an important role by setting constraints and principles to provide guidance and boundaries for development teams. While Agile values working software over documentation, architects can document architecture decisions and provide guidance through code examples. On Agile teams, the architect acts as an owner who facilitates architectural decisions, explores new technologies, and evolves the architecture over time based on learnings. The architect also helps align development across teams when needed.
Product Development Planning by Creative Engineering Design LeadProduct School
This document discusses product development planning from Creative Engineering Design Lead. It provides an overview of product development processes and considerations, including common steps like empathizing, defining, ideating, prototyping, and testing. It discusses breadboarding prototypes, design for manufacturing, costs, and planning projects. Project planning involves determining phases, tasks, costs, and timelines. Common phases include concept development, design, engineering, prototyping, refinement, manufacturing release, and support.
The document discusses DevOps and provides an overview of key concepts:
- It defines DevOps as breaking down silos between development and operations through culture, process, and technology integration.
- The pillars of DevOps are discussed as integration, collaboration, and communication.
- Application Lifecycle Management (ALM) and tools like Jira, Confluence, and Bamboo are presented for managing the full software development lifecycle.
- Continuous Integration (CI), Continuous Deployment (CD), and infrastructure automation are key DevOps technologies covered.
XP is an agile software development methodology based on values of communication, simplicity, feedback, courage, and respect. It emphasizes coding, testing, listening, and designing activities. Core practices include pair programming, test-driven development, small releases, refactoring, and collective code ownership. Testing is done through automated unit tests written by developers and acceptance tests defined by customers.
MongoDB World 2018: How an Idea Becomes a MongoDB FeatureMongoDB
The document describes the software development lifecycle used by the MongoDB Database Engineering Team. It involves carefully scoping projects, designing features, implementing code, testing, and getting acceptance from product management. Key aspects include establishing consensus during scoping, addressing downstream impacts, writing comprehensive tests, and continuously improving processes over time.
The document discusses various software development methodologies including Agile, Scrum, XP, Kanban, Lean, Crystal, DSDM, FDD, V-Model, Incremental Model, Evolutionary Prototyping, Cowboy Coding, and Personal Software Process. It describes how each methodology works, the roles involved, advantages and disadvantages. For example, it states that Agile is responsive to market changes, Scrum uses sprints, planning meetings and burndown charts, and Cowboy Coding lacks structure but allows for experimentation.
Similar to Scaling Products With Design Systems (20)
Creating and maintaining a design system for 130 teams - Bethany Sonefelduxpin
The document summarizes the evolution of Carbon Design System, IBM's design system created to provide consistency across 130+ teams. It started in 2014 with a small team and focused on developing core components. Over time, the team grew Carbon to include design kits, templates, add-ons and other resources. They also open sourced the system and maintained it through documentation, contributions and bug fixes. The talk highlights lessons like starting small, anticipating future needs, and dedicating time to maintenance as the system and its user base expands.
The document discusses creating experience principles for user experience (UX) systems. It provides examples of Spotify's experience principles and defines what makes good principles. Experience principles outline a product or service's core values and ensure its purpose is expressed through design. Good principles are specific, actionable, impressionable, have a point of view, and are living. The document also discusses design language systems, which define unified experiences through interaction patterns, components and style guides. It provides tips for developing experience principles and design language systems.
How Atlassian builds and manages their design system across their product suite
How the Design System team empowers users by iterating with research and testing
How design and engineering cooperate to be efficient and productive
Accessibility in Design Systems by Allison Shawuxpin
You'll learn:
The benefits of accessibility in a design system
How to create and incorporate accessibility standards
How to improve accessibility across your product suite
Consistency vs. Flexibility in Design Systems: A GE Case Study by Ken Skistimasuxpin
A case study from the Predix Design System at GE on how balance consistency and flexibility in a large scale design system.
You'll learn:
Where design systems should be consistent or flexible
How GE Digital handles consistency vs. flexibility in the Predix design system
How to adapt tools and technology to balance both.
Developing UX ROI in Enterprise Land: An ADP Case Studyuxpin
You'll learn:
How to develop a quantitative framework for measuring UX ROI
How to use UX ROI as a strategic alignment tool with CX and other internal customer teams
Best practices and lessons learned
Three's a Party: How Trifectas Help Product, Engineering, and Design Work Tog...uxpin
You'll learn:
How to change your collaboration model for PM, engineering, and design as teams grow
How to define responsibilities, cadence, and activities across every layer of a product organization
How Shopify tackles multi-disciplinary collaboration across product teams
Automating Design Processes for Teams: An IDEO Case Studyuxpin
You'll learn:
How IDEO used bots to help automate user research
How you can use automation to improve team efficiency
The future of automation in design
Calculating the ROI of UX with Standard Financial Modelsuxpin
You'll learn:
- How to create a UX ROI model with decision trees and expected values
- How to forecast the effect of UX on sales
- How to use SUS and NPS to measure the effect of UX
From 6 to 126 in 4 Years: The Story Behind Atlassian Designuxpin
You'll learn:
- How to lead design teams through periods of rapid growth
- How to change design processes, build design culture, and scale teams over time
- How to engage engineering and product teams to create a customer-focused organization
Building a UX Process at Salesforce that Promotes Focus and Creativityuxpin
You'll learn:
- How Salesforce designed a large-scale UX process across teams
- Why certain design activities were chosen over others
- How to preserve design quality at scale
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
- How to design across devices with an ecosystem approach
- How to design consistent, complementary, and continuous experiences
- How to deliver the right experience at the right time on the right device
Participatory Design: Bringing Users Into Your UX Processuxpin
Participatory design tactics practiced by frog design
Collaborative activities for finding user needs, generating, and evaluating design ideas
How to select and deploy participatory design activities within an Agile team
You'll learn:
How Bloomberg implemented Agile UX across offices
How to execute staggered sprints with designers and developers
How to employ a “Community of Practice” methodology to improve product consistency
Collaborative Product Discovery at Fjord: A Case Studyuxpin
You'll learn:
How to adapt user research and strategy methods for Agile timelines
How to turn research insights into a cohesive product strategy
Useful activities for “just enough research”
You'll learn:
- How to transition through through inspiration, ideation, and implementation with a global team
- How to turn “statements of intent” into prioritized user stories.
- How to increase team velocity without sacrificing usability
Practical eLearning Makeovers for EveryoneBianca Woods
Welcome to Practical eLearning Makeovers for Everyone. In this presentation, we’ll take a look at a bunch of easy-to-use visual design tips and tricks. And we’ll do this by using them to spruce up some eLearning screens that are in dire need of a new look.
Explore the essential graphic design tools and software that can elevate your creative projects. Discover industry favorites and innovative solutions for stunning design results.
International Upcycling Research Network advisory board meeting 4Kyungeun Sung
Slides used for the International Upcycling Research Network advisory board 4 (last one). The project is based at De Montfort University in Leicester, UK, and funded by the Arts and Humanities Research Council.
21. ● Ensure consistency and eliminate confusion
● Formalized and unified components
● Full pages can be easily deconstructed into component blocks
Forge 7