How to Hire a DesignOps Expert?

The webinar with Dave Malouf about Holistic DesignOps made us wonder what else we could write about to expand on the design operations topic. One of such things is hiring. What should you look for in a DesignOps expert? If you want to watch the webinar, we have a recording of it on our YouTube channel.

Let’s go back to the main topic of this discussion–how to hire a DesignOps expert?

As a discipline still in its infancy, there is no clear path to becoming a DesignOps expert. It’s not like UX, where you study to become a designer. Most DesignOps experts transition from product, design, change management, or project management because they want to solve their company’s inefficiencies.

Setting up systems and processes to keep design teams focused on building great products has proven to increase productivity and deliver a good return on investment. Building a DesignOps team is essential to compete in today’s ultra-competitive market.

Reduce time-to-market with UXPin Merge, the world’s most advanced code-based design tool–built to solve DesignOps challenges. Sync your company’s design system to UXPin’s editor to create a single source of truth between designers and engineers. Request access to Merge.

Who is a DesignOps Expert?

A DesignOps expert focuses on identifying operational inefficiencies and finding solutions to optimize them. DesignOps experts have little to do with design itself; instead, they focus on the tools, processes, systems, and protocols that enable designers to do work.

designops efficiency person

There are ten key DesignOps roles:

  1. Operations management: Creating and managing a design roadmap that aligns with design teams’ goals while identifying skills gaps to achieve those objectives.
  2. Process design: Creating design systems and mapping the tools teams need.
  3. Project management: Design workflows, assign projects, set timelines, and remove any bottlenecks.
  4. Creating a communication strategy: Liaising between the design teams and the organization, including communication channels and file and resource storage.
  5. Onboarding new hires: Hiring, orienting, and training new staff so that they seamlessly integrate with design teams.
  6. Building design team culture: Instilling the company culture with workshops, training, and other team-building events.
  7. Budget allocation and control: Managing the costs associated with running the design team rather than direct product costs.
  8. Legal: Working with legal teams to create NDAs, participant release forms, and other legal documents.
  9. Managing the procurement process: Streamlining and managing purchasing decisions to meet budget constraints which involves connecting with financial departments.
  10. IT and security: Liaising with IT to ensure all tools and processes meet security standards.

There are three primary DesignOps positions:

  • DesignOps Leader or Head of DesignOps
  • Design Program Manager (DPM)
  • Design Producer

DesignOps Leader

A DesignOps leader works closely with the Design Leader to create an operational vision and roadmap. This high-level role focuses on how design teams complete tasks and projects.

A DesignOps leader usually has a background in change management and project management. They have to understand how to facilitate change while recognizing the end-to-end project process.

As Patrizia Bertini says in UXPin’s webinar, Measuring DesignOps Impact, “DesignOps changes the existing reality to bring more value. It’s a very transformative discipline.”

A DesignOps leader has to find tools and processes to optimize operational workflows and then develop the strategies to encourage their adoption.

Design Program Manager (DPM)

A DPM is responsible for executing the DesignOps Leader’s strategy and roadmap. They work with UX and product teams providing the necessary support to focus on design.

To do this effectively, a DPM usually comes from a design background, so they understand the end-to-end design process and identify roadblocks.

The DPM also acts as a bridge between teams and projects to improve communication and collaboration.

Design Producer

A Design Producer works directly on a project managing the administrative and operational tasks so that designers can focus on designing. They manage the end-to-end design process, ensuring everything runs smoothly while facilitating communication and collaboration.

DesignOps Leader’s Skill Set

While it’s helpful for a DesignOps leader to understand design, it’s more important to have a change management background. They must understand how to implement change and encourage adoption.

designops efficiency speed optimal

DesignOps Leaders must have excellent business management skills for budgeting, strategy, and execution. They need to manage people and lead them towards their Ops vision.

Communication and networking are crucial DesignOps skills. Leaders spend a lot of time engaging with stakeholders and executives to advocate for design and get budget buy-in. They’re also the voice of design to the rest of the organization, meeting with peers to find opportunities for collaboration.

DesignOps Leader’s Responsibilities

In Measuring DesignOps Impact, Patrizia Bertini talks about three DesignOps areas of intervention:

  • Business
  • Workflow and design
  • People

1. Business Operations

Managing budgets, resources, and other business-related design functions. Examples include:

  • Budget management/spending optimization
  • Spending policy overview
  • End-to-end procurement and 3PRM (practice in performance & reward management)
  • Contract negotiations
  • Onboarding vendors and 3P (process, product, people) risk assessment
  • Spending ROI calculation
  • Tools ROI/impact assessment
  • Resource asks assessment (tools + people)
  • CW/FTE sequencing

2. Workflow and Design Operations

A holistic view of the end-to-end design process. How do designers get from concept to final product? Examples include:

  • End-to-end design process optimization
  • Tools ecosystem management
  • Tools onboarding/off-boarding
  • Cross-functional collaboration optimization
  • Design system management
  • Data governance
  • Participant sourcing process management
  • Research and design asset management
  • Design standards

3. People Operations

Considers the human aspect of design teams, like skills development, communication, and culture. Examples include:

  • Career path direction
  • Skills matrix/team composition assessment
  • Development programs and team training
  • Teams culture
  • Knowledge & experience training
  • Streamline ubiquitous cross-functional collaboration
  • Onboarding/off-boarding
  • Internal communication
  • Change management
  • Engagement models
  • Hiring/job specification/tasks review

Would you like to improve your skills concerning people operations? Here’s a free eBook that covers the first strategic area of DesignOps: People, called DesignOps Pillar: How We Work Together. Learn about hiring, onboarding, and managing a team of designers.

Is Your Company Ready to Hire a DesignOps Expert?

designops increasing collaboration talk

Here are some signs your company might need a DesignOps expert:

  • You’re having trouble with silos, communication, and collaboration resulting in poor cohesion and consistency for project deliveries.
  • You have too many tools which disrupt workflows or cause errors.
  • Design teams often miss deadlines, or high rework rates adversely impact time-to-market.
  • Designers complain that operational and administrative tasks prevent them from focusing on design.
  • Design leaders spend too much time onboarding, orienting, and training new hires–time better spent on design-related tasks.
  • Designers wear too many hats instead of focusing or specializing on one primary activity–i.e., UI design, research, testing, etc.

Check out these resources to learn more about DesignOps, and its role in your organization:

Optimizing Design With UXPin Merge

Managing design systems is one of the biggest challenges for a DesignOps expert. Ensuring the design system’s UI kit syncs with the component library takes considerable time and effort.

With Merge, you sync your design system from a repository to UXPin’s editor, so designers use the same components as engineers–creating a single source of truth across the organization. Any changes to the repository automatically sync to UXPin, notifying design teams of the new release.

Ready to optimize your UX workflows with a single tool? Request access to Merge.

Product Design Influencers that You Need to Follow

product design youtube channels

YouTube is often the go-to for product design tutorials, career advice, design tips, design tools, and more. We’ve put together our favorite product design YouTube channels and influencers to inspire your next project.

We’ve selected the best YouTube channels featuring product design and product development content from some of the Internet’s most creative people.

One of our favorite YouTube channels is Jesse Showalter. Jesse has done a couple of UXPin product reviews, including a basic overview and a walkthrough of our advanced features. Sign up for a free trial and follow along as Jesse takes you through UXPin.

Top Product Design Influencers

These product design influencers offer practical advice and helpful design tips to enhance your design skills. Whether you’re just starting as a designer or a seasoned pro looking for advanced techniques, these product design YouTube channels offer excellent content for designers. You can also explore various influencer databases to discover even more creators in the product design and development space.

1. Flux (AKA Ran Segall)

flux

Flux is the personal vlog of a designer Ran Segall who documents his learnings of web design and entrepreneurship. Ran is extremely charismatic and knowledgable which makes him an amazing person to follow. Besides posting YouTube videos, he has a very energetic Instagram account where he publishes a bite-sized content for anyone interested in UX and UI design, as well as growing a digital business.

Here are links to follow Ran Segall:

2. Sharon Oniyine

One of the Best design influencers in 2022

Sharon Onyinye is a UI/UX designer with over five years of experience working in tech. Sharon uses her YouTube channel to share her expertise with aspiring UX designers, including how to get a design job, portfolio/CV tips, and other helpful career advice.

You can also book a one-on-one with Sharon for career improvement, Interview preparation, portfolio, resume reviews, and general design advice.

Here are links to follow Sharon online:

3. Jesse Showalter

One of the best design influencers on YouTube

Jesse is a Product UI/UX Designer from the United States. He shares high-quality digital design and web development content on his YouTube channel

What we love most about Jesse is his consistency–posting new videos every week to keep his followers up to date with the latest design tools, products, brand identity, and trends. Jesse also offers live streams with web design challenges, Q&As, design-alongs, and more.

Here are links to follow Jesse online:

4. DesignCourse – Gary Simon

Top product design influencers on YouTube

Gary Simon is a UX/UI Designer, Graphic Designer, and Full Stack Developer from the United States. He’s been posting vlogs to his YouTube channel since 2010 and amassed just shy of a million followers.

Gary has over 100 design and development courses on Envato Network’s TutsPlus.com, DigitalTutors.com, Pluralsight.com, LinkedIn Learning & Lynda.com. He also founded DesignCourse, which offers interactive design courses and a mentoring program.

Gary’s YouTube channel playlists include product reviews, typography & color tips, design/development tutorials, free courses, and much more. He also teaches his followers how to get the most out of design tools and front-end frameworks.

Here are links to follow Gary online:

5. Sarah Doody

Follow one of the best design influencers Sarah

Sarah Doody is a User Experience Designer and Researcher from Salt Lake City, Utah, with over 18 years of experience. She founded the Career Strategy Lab, “a UX career accelerator that helps UX professionals get hired without applying to hundreds of roles.”

Sarah’s YouTube channel offers practical tips and strategies for aspiring UX designers with career advice, portfolio reviews, and user research tips and tricks.

Here are links to follow Sarah online:

6. AJ&Smart

AJ&Smart are design influencers on YouTube

AJ&Smart is a Berlin-based Product Design Studio that also runs a successful YouTube channel with over 200k followers. The studio posts new vlogs regularly, hosted by different members of the AJ&Smart team.

AJ&Smart’s content focuses on UX/UI design, design sprints, design thinking, and research to help designers build better products. Other video topics include career advice, how to land clients, and tips for design teams.

AJ&Smart founded Workshopper, a platform offering free resources for UX/UI designers and product designers.

Here are links to follow AJ&Smart online:

7. Vytautas Alechnavicius

Design influencer who talks about product design

Vytautas (or Vy) Alechnavicius UX Designer, Researcher, and DesignOps Leader, originally from Denmark but living and working in the United Kingdom.

Vy works full time as a Product Design Manager at Tesco while running a successful YouTube channel about user research and design. He creates a lot of content around UX design processes and methods, with loads of valuable design thinking tips.

Vy’s Discord channel, Design Squad: UX Community, has almost 3,000 active members where designers and product strategists share knowledge and offer helpful advice.

Here are links to Vytautas’s website and social media:

8. Kim Tang

Best design influencer kim tang youtube

Kim Tang is a UX/Product Designer from the United Kingdom. Kim isn’t as established as the other design influencers featured in this article but shares interesting insights into her life as a product designer at eCommerce giant ASOS.

Kim now works as a product designer at FARETCH, a group of luxury fashion brands, including Browns, Stadium Goods, and New Guards Group.

Here are links to Kim’s social media:

Product Development Influencers

If you’re looking to develop your skills as a product developer, these four influencers offer excellent coding tutorials, tips, and advice.

1. CleverProgrammer

clever programmer is a top influencer for product design and development

CleverProgrammer, aka Rafeh Qazi, is a Los Angeles-based Full-Stack Developer and Software Programmer with over a million YouTube subscribers.

Rafeh’s YouTube popularity is due to his comprehensive video tutorials, several of which are over seven hours long with more than 2 million views each.

Rafeh is the founder of CleverProgrammer, which offers various coding bootcamps in Javascript, Python, front-end, and full-stack development.

Here are links to follow CleverProgrammer online:

2. Ania Kubów

Design influencer who's a developer

Polish-born, Dubai-raised, and UK-educated Ania Kubów is a software engineer sharing her knowledge and experience with aspiring developers. Her YouTube channel has over 210k subscribers, and Ania creates free content for freeCodeCamp.

Ania shares loads of fun code along projects on her YouTube channel, with playlists including games, APIs, web scrapers, clones of popular websites, React applications, and more. She also shares valuable insights into blockchain technology and how to create NFTs.

Here are links to Ania’s social media:

3. Dev Ed

product design influencer and development influencer

Not only does Dev Ed have the coolest name, but he’s also an incredibly talented web developer and designer from Romania with over 720k YouTube subscribers. His enthusiastic style and ability to simplify complex code concepts are what make Dev Ed so popular.

Dev Ed offers beginner coding tutorials for Javascript, Python, Node.js, React, CSS, and web development. He also has fun projects like building video games and creating exciting Javascript animations.

Here are links to follow Dev Ed online:

4. CoderOne

CoderOne is an educational channel for those of you who want top learn fundamental aspects of programming. It’s run by Islem Maboud who has an amazing gift of explaining the nuances of software development. He also teaches the audience step by step how to build something, such as food delivery app.

Here are links to follow CoderOne online:

5. Net Ninja

development and design influencers that help people understand front-end design

Net Ninja, aka Shaun Pelling, is a UK-based full-stack developer and online instructor. Shaun has four Udemy courses with over 62,000 students, and all his courses have solid 5-star scores (an incredible achievement) with thousands of positive reviews.

Through his YouTube channel, Udemy account, and website, Shaun offers courses in Node.js, Vue, React, Python, Ruby, PHP, HTML, Flutter, TypeScript, CSS, and other programming languages and technologies–“to Black-belt your coding skills.”

Here are links to follow Net Ninja online:

BONUS: Design Influencer We Would Love to Go Back on YouTube

These two design influencers have fantastic content, but they haven’t posted new videos for a while.

1. Mike Locke

One of the best design influencers who have great content on Youtube

Mike Locke is a UI/UX Designer from the United States with more than 25 years of design experience. He’s worked as a UI/UX Designer at many global organizations, including Thomson Reuters, Yahoo!, CBS, ADP, and Fox TV, where he currently works as a Lead UI/UX Designer.

Mike’s YouTube channel offers tons of practical tips on UX/UI topics, career advice, interviewing processes, and more. He’s passionate about sharing his wealth of knowledge from working with Fortune500 organizations–which is what makes his videos so unique and engaging.

Although Mike hasn’t posted for over a year, you should still explore his YouTube channel for helpful design tips and advice.

Here are links to follow Mike online:

Improving Product Design With UXPin

UXPin is a code-based end-to-end design tool used by UX and product designers worldwide. The intuitive design canvas and advanced features allow designers to build prototypes with significantly higher fidelity and functionality than other image-based design tools. Adalo, the no-code app builder, also enables designers and entrepreneurs to quickly transform their designs into functional mobile and web applications without requiring traditional development resources.

In this video, Jesse Showalter walks you through UXPin’s advanced prototyping features, including Interactions, States, Components, Variables, and Expressions.

You can also check out our free app examples and interactive UI patterns, demonstrating UXPin’s advanced features for you to copy and edit.

Sign up for a free trial and experience the endless possibilities with UXPin’s code-based design tool.

UX Engineer Tools that Make The Job Easier

A UX engineer’s (UXE) toolkit includes design and engineering tools. They are engineers first, so most tools apply to development, but they also use a fair share of design tools.

Working between product design and development means that UX engineer tools must allow for collaboration between both disciplines. They must also work with DesignOps and DevOps, meaning UXEs also have many operational tools.

UXPin is a code-based design tool UX engineers use to bridge the gap between design and development. From advanced UI design and prototyping to design systems and component library syncing, UXPin enables UX engineers to work and collaborate more effectively. Sign up for a free trial to experience the world’s most advanced code-based design tool.

What Does a UX Engineer do?

Before we get into UX engineer tools, it’s important to define what a UX engineer does so we understand their diverse toolkit.

UX engineers work primarily in front-end development, collaborating with the design team throughout the end-to-end design process–effectively making them hybrid designer/engineers. They have limited design skills, predominantly focused on UI design, interaction design, and prototyping.

Working across design and development means UX engineers work with a stack of tools for each–more than the average UX designer or engineer.

UX engineers work with design tools when collaborating with designers, and development tools for their engineering work. 

For this reason, we’ve split UX engineer tools into two categories:

  • Design tools
  • Development tools

UX Engineer’s Design Tools

collaboration team prototyping

UX engineers collaborate with designers from ideation to design handoff. Their role is to look at ideas through an engineer’s lens and give technical advice and support during the product design process.

UI Design Tools

Rather than designing UI elements and assets, UX engineers use design tools to collaborate with designers. 

For example, if they’re using a design tool like UXPin, UX engineers use UXPin’s Comments to share feedback and collaborate on wireframes, mockups, and prototypes (low-fidelity and high-fidelity). Many design tools have a similar feature, allowing designers and UX engineers to collaborate throughout the design process.

Prototyping Tools

UX engineers rarely use traditional image-based prototyping tools. Instead, they use HTML, CSS, and Javascript (or a front-end framework) to build fully functioning prototypes.

The problem with prototyping in code is that it’s time-consuming and isn’t accessible for designers to collaborate–they must rely on the UX engineer to build the prototype and make changes.

With UXPin Merge, designers and UX engineers can drag-and-drop components from a repository to build fully functioning prototypes in UXPin.

Sync React components directly to UXPin using Git or Storybook for other technologies like Vue, Ember, Angular, and more.

With Merge, UX engineers benefit from a fully functioning prototype without the time and effort of writing code. Once prototyping is complete, UX engineers can copy components from the repository, plus changes in UXPin, to start the development process.

Other Design Tools

While UX engineers collaborate with designers throughout the design process, they tend to provide feedback and advice rather than actively researching, designing, and user testing.

A UX engineer will have access to many of these tools, but they’re more interested in the results and analytics than conducting user research and usability testing. 

UX Engineer’s Development Tools

code design developer

UX engineers complete most front-end development, leaving data integration, APIs, performance, analytics, and other technical “non-UI” work to front-end engineers.

Integrated Development Environment (IDE)

UX engineers use an integrated development environment (IDE) to write code and collaborate with the engineering team. Visual Studio Code is a widely used IDE with tons of extensions to help streamline the development process.

Engineers can choose from a wide range of IDEs, including native applications like Xcode for iOS and Android Studio for Android.

Component-Driven Development Tools

design system atomic library components

Storybook allows engineers to build UI components, layouts, templates, and user interfaces in isolation. The open-source tool is popular for engineering teams that use component-driven UI or Brad Front’s Atomic Design approach to building digital products and websites.

UX engineers use a tool like Storybook to share new components with engineering teams for reviewing and editing before release. Developers can also use Storybook to build and test user interfaces before committing to development.

Version Control – Git

Git is the most widely-used version control system. It allows engineers to track code changes while enabling development team members to simultaneously work on the same project.

Git is crucial for UX engineers because they often collaborate on customer-facing UIs with front-end developers.

Package Manager

UX engineers use packages to build and scale digital products. They can use privately-hosted packages or public repositories like NPM for Node.js apps or pub.dev for Flutter.

UX engineers must use the command line to interact with these repositories and, therefore, must be competent with working in the terminal.

Webpack

Front-end developers use multiple APIs, plugins, and dependencies to build websites and web applications, each with separate CSS, Javascript, and other assets. Front-end frameworks like React, Angular, and others also come with assets and dependencies.

These assets have a significant impact on performance. A module bundler like Webpack combines these assets into single .js and .css files, optimized for multiple browsers and devices.

Chrome Developer Tools

Chrome Developer Tools is a crucial web development tool. UX engineers use Google Developer Tools to inspect the user interface, find issues, and edit code in the browser.

Google Developer Tools allows UX engineers to work on a website or web application without editing code or additional testing tools. Engineers can also use Google Developer Tools to inspect other websites to find inspiration or research competitors.

Accessibility Tools

accessibility contrast wcag

As UX experts, UX engineers must test their code for accessibility. Here are several standard accessibility tools front-end developers and UX engineers use:

  • WAVE: WAVE (Web Accessibility Evaluation Tool) is an accessibility tool for front-end engineers. It scans the web page’s code and assets, flagging accessibility issues with suggestions for improvements. WAVE also has a contrast analyzer so UX engineers can double-check designer color palettes.
  • Accessibility Developer Tools: A Chrome extension for Google Developer Tools to test accessibility and performance.
  • Tenon: A powerful front-end tool for automating accessibility testing. Tenon integrates with many IDEs, content management systems, and project management software to optimize accessibility testing and fixing.

GitBook’s Front-end Developer Handbook has excellent accessibility tools and other front-end resources.

Why Code-Based Design Tools are Important for UX Engineers

Designers and engineers speak different languages and use separate tools. This disconnect makes it difficult to understand each other and collaborate effectively.

Code-based design tools like UXPin bridge this gap–making it easier for UX engineers and designers to collaborate.

Why Code-Based Design is Different

Traditional image-based design tools render raster graphics or static images of user interfaces. These tools have little or no functionality, making it difficult for engineers and stakeholders to understand the product’s design.

A code-based design tool like UXPin renders HTML, CSS, and Javascript, allowing designers to create interactive prototypes, accurately replicating the final product.

uxpin merge comparison 1

Advanced Code-Based Prototyping with UXPin

UXPin’s advanced prototyping features allow designers and UX engineers to build fully functioning prototypes–eliminating the need for UXEs to write code during prototyping and testing.

For example, one of the challenges with image-based tools is that you can’t use forms, making it necessary for UX engineers to develop a prototype for testing a simple onboarding sequence.

In UXPin, forms are fully functional. Designers can build a dynamic onboarding flow that captures user inputs while creating a unique user experience for each individual-like a welcome message or thank you page with the user’s name.

Some of the other high-fidelity prototypes you can only create with code-based tools like UXPin include:

  • Form validation: Use Expressions to check users enter the correct email format or if a password meets specific requirements.
  • Computational components: Build functioning shopping carts that respond to user interactions, dynamically calculating items, shipping, etc.
  • States: Create multiple States for a single component and switch between those states based on user interaction.
  • Interactivity: Use advanced Interactions with Javascript-like animations and transitions to create immersive experiences that react to users’ clicks, taps, scrolls, swipes, location, and other actions.
  • Variables: Design forms that capture user inputs and take action based on the information–like a personalized greeting or populating a user’s profile page with information provided during sign-up.

Increase Fidelity & Functionality With UXPin Merge

UXPin Merge is the ultimate UX engineer design tool! Merge allows you to sync components from a repository to UXPin’s editor so designers and UXEs can build fully functioning prototypes.

UX engineers can use a component’s props (or Args for our Storybook integration) to give designers more control or set limitations based on the company’s design system guidelines. Designers can edit props via UXPin’s properties panel or switch to JSX, depending on their preference.

UX engineers simply copy/paste the JSX code at the design handoff to start the development process. Any changes UXEs make to the repository automatically sync to UXPin, notifying designers of the change–creating a single source of truth between designers and developers.

UXPin’s low learning curve makes it easy for non-designers (including UX engineers) to design layouts and prototypes. PayPal proved this point when its product designers could build fully functioning high-fidelity prototypes 8X faster than experienced UI/UX designers.

Tradeoff Between Time and Robust Prototypes? You Can Have Both!

Prototyping is challenging for designers using image-based design tools. These static mockups and prototypes never achieve the fidelity and functionality required to get accurate feedback from testing and stakeholders.

Designers often have to use several tools throughout the design process; one for design, one for prototyping, and another for testing. This workflow is not only disruptive but expensive as companies pay subscription fees for multiple tools and paid plugins to integrate this complicated workflow.

We will demonstrate how code-based tools can simplify your team’s UX workflow, reduce your reliance on extra tools and plugins, significantly enhance prototyping and testing, improve collaboration, and streamline the design handoff process.

Enrich your end-to-end design process with UXPin’s code-based design tool. Sign up for a free trial and start designing better user experiences for your customers.

The Challenge of Prototyping With UI Kits

One of the challenges with image-based design tools is that designers often have to start from scratch every time they start a new project. Even with a comprehensive design system, there’s only so much fidelity and functionality you can save in a static UI kit.

“Imagine this”–an all too familiar scenario…

You have to present your designs for a new onboarding flow to stakeholders, but your team didn’t have the time or resources to build a fully functioning prototype.

So, you connect a series of static artboards with some basic transitions and a few GIFs to demonstrate complex interactions and animations. The problem is that the prototype isn’t intuitive, and stakeholders battle to understand how it’s supposed to work.

You find yourself repeating, “ok, now imagine this…” as you guide stakeholders through your prototype. Stakeholders have to jump from static artboard to GIF to preview animations of what your prototype is supposed to do. It’s difficult to follow without your step-by-step instructions, and there are lots of confused faces.

By the end of your meeting, you’ve spent so much time explaining what the prototype should do instead of pitching your team’s innovative design.

Poor Fidelity from Static Prototypes

prototyping design drawing pencil tool

Many teams are stuck in this scenario where prototypes lack clarity. There simply isn’t enough time and resources to build working prototypes for every idea or flow. Designers have to compromise, hoping they can explain their designs to stakeholders, usability participants, and engineers. 

It’s a challenge with stakeholders but even more aggravating during the design handoff, where frustrations boil over between engineers and designers.

Getting accurate results from usability participants is near impossible with these low-fidelity prototypes. Designers are limited by what they can test, usually restricted to basic user flows. They must rely on UX engineers to build code-based prototypes for accurate testing and meaningful results.

Building fully functioning prototypes no longer means you have to rely on developers. UXPin Merge has revolutionized the standard UX workflow, so designers and engineers work with the same component library linked to a repository.

PayPal’s Faster Time-to-Market with UXPin Merge

PayPal uses Merge to scale design and ship products 8X faster than image-based design tools. Product teams also get better feedback from stakeholders because they don’t have to explain how everything works.

“Our stakeholders are able to provide feedback pretty quickly using UXPin. We can send them a link to play with the prototype in their own time, and UXPin allows them to provide comments directly on the prototypes. UXPin’s comments functionality is great because we can follow along and mark comments as resolved once we address them.”Erica Rider, Senior Manager for UX – Developer tools and platform experience at PayPal

PayPal’s internal products use the React component library from Microsoft’s Fluent UI design system. They host the design system in a GitHub repository which syncs directly to UXPin’s design editor.

These components include interactivity, minimizing interaction design, and animations designers must do to build interactive prototypes. These interactions also help maintain consistency across projects and teams.

Any changes engineers make to the repo automatically sync to UXPin, so PayPal’s product teams, UX designers, and engineers always work with the same components–creating a single source of truth across the organization.

“With this new UXPin approach, we’re seeing a more collaborative, integrative design process. Rather than separating design, prototyping, and development, UXPin allows us to create an integrated flow where we engage engineering and product teams throughout the process. As a result, the product’s final quality has improved dramatically.”Erica Rider, Senior Manager for UX – Developer tools and platform experience at PayPal

Iress’ Design System Maturity Using UXPin Merge

Every design system strives toward a fully integrated system where designers drag-and-drop components to build UIs and engineers copy/paste code to complete the development process.

The component-based end-to-end product development process means designers spend more time prototyping and testing than wireframing and designing. At the same time, engineers focus on optimization and innovation rather than writing code.

Iress’ Nick Elliott calls this stage four design system maturity, where designers and engineers use the exact same components for their workflows. Consistency and design drift are no longer issues with a seamless, almost non-existent handover process from design to development.

image 12

Nick spent 12 months reviewing design tools to bridge the gap between design and development to achieve level four maturity. UXPin Merge emerged as the clear winner, allowing Iress to develop a fully integrated design system where designers and engineers work with the same component library.

Increase Fidelity and Functionality in a Fraction of the Time

We learned from PayPal’s case study how much faster designers build high-fidelity code-based prototypes. PayPal tested this side-by-side with Merge vs. an image-based design tool.

An experience PayPal UX designer built the exact same one-page prototype using both tools. The image-based prototype took over an hour, while the Merge prototype (with higher fidelity and functionality) took eight minutes!

Due to Merge’s drag-and-drop workflow, even PayPal’s product managers (who have no experience with design tools) can build the same one-page prototype in under 10 minutes.

Getting the Most out of Merge

Merge works best for companies using an existing design system or open-source component library, like the MUI library. Engineers can give designers control to customize components via React props or Args if you’re using the Storybook integration (Angular, Ember, Vue, etc.)

uxpin merge comparison 1

The design system team can also set interactions and states for each component, like default, hover, active, and disabled for a button. Instead of designing interactions, designers simply select one from a dropdown in the properties panel.

Any changes designers make to a component UXPin renders in JSX, so engineers simply copy/paste for front-end development.

As we learned with PayPal, stakeholders can interact with prototypes with little or no explanation in their own time, leaving feedback via UXPin’s Comments feature. The design lead can assign these comments to team members to action and mark them as resolved when the task is complete.

Are you still using low-fidelity static prototypes with poor functionality, GIFs, and excessive annotations? Switch to the world’s most advanced design and prototyping tool to enhance collaboration with engineers and improve feedback from stakeholders.

Sign up for a 14-day trial to explore UXPin Merge via our free MUI integration.

Design Sprints – Validate Your Hypothesis Within 5 Days

Design Sprints

Design sprints have become common strategies for companies to solve big problems fast! Developed by ex-Googler Jake Knapp, the design sprint methodology is about prototyping and testing a product in just five days.

Prototype and test your design sprint product with UXPin. Built-in design libraries allow you to drag-and-drop components to quickly build high-fidelity mockups and prototypes–even if you’re a non-designer. Sign up for a free trial to explore UXPin for your next design project.

What is a Design Sprint?

A design sprint is a rapid methodology to prototype an idea in just five days. This prototype could be for a new product or redesign an existing product.

The five-day process includes a small team of designers, stakeholders, and other members who come together to solve a big problem in as little time and resources as possible.

A sprint incorporates group and individual activities, including brainstorming, designing, prototyping, and testing. By the end of the week, you have a design solution or MVP to start developing, which you can then hand off to development teams with clear specifications for building out the full product experience.

How did Design Sprints Originate?

Jake Knapp developed the design sprint methodology while working at Google in 2010. Jake took inspiration from IDEO’s design thinking, various books, and Google’s product development culture.

In 2016 Jake Knapp co-authored the book Sprint with John Zeratsky and Braden Kowitz, which outlines the process he had perfected during his time at Google. John and Jake also worked with Google Ventures (GV) to perfect and refine the process you read about in Sprint.

Since Sprint’s release, every organizational type, including startups, agencies, colleges, government entities, Fortune 500s, and museums, has used Jake’s sprint framework to prototype ideas. 

What are the 5 Stages of Design Sprint?

The five stages of the design sprint draw inspiration from the design thinking process. These stages include:

  1. Map
  2. Sketch
  3. Decide
  4. Prototype
  5. Test

Some design sprint variations complete the process in four days, but most follow the five-day format described in Jake Knapp’s Sprint. Either way, it’s essential to start on Monday and run your sprint consecutively over four or five days without breaks.

There is a crucial step 0, which includes all the planning and preparation to run a design sprint.

What Happens Before a Design Sprint Process? – Sprint Preparation

A design sprint will never work without proper preparation. Here are some things you must consider for a design sprint:

  • Pick a facilitator: The facilitator must be a strong leader capable of promoting dialogue and keeping to a schedule. This person is responsible for the sprint process, most importantly timekeeping, leading discussions, venue preparation, and facilitating discussions.
  • Gather the sprint team: Jake recommends a cross-functional sprint team of seven or fewer. During the first three days, you’ll also need stakeholder input to help with brainstorming and ideation.
  • Invite experts: Experts include people inside and outside your organization with acute knowledge about the product or problem you’re solving. You’ll need these experts on the first day to ask questions to understand the problem and start ideating potential solutions.
  • Pick the Decider: The sprint Decider plays a vital role in a design sprint. This person will decide which idea the team must prototype and test. Examples of a Decider include the CEO, product manager, product VP, or another decision-maker directly responsible for the problem you’re working on.
  • The venue: Find a room that can comfortably hold your sprint team, including space for desks and snacks (which you can place outside of the room too). Check out Fast Company’s article about how to find a sprint “war room” for more details. IMPORTANT: Choose a venue where your team won’t be disturbed during the five days! You need to maximize the time without distractions or people “popping in” to see how the sprint is going.
  • Schedule dates: Block five full days for your sprint and ensure everyone is available for those days. Gathering stakeholders is often tricky, so you might have to have a pre-sprint workshop when they’re available. Check out this short video from red-id for more on prep work.

Check out this article from Sprint’s co-authors for a complete sprint preparation checklist. A remote design sprint requires different planning and preparation–check out this article for more info.

Day 1 – Monday – Map

Day one of a sprint or mapping is a slow start to the rapid prototyping process. The sprint team spends the first day creating a map of the user experience flow, interviewing experts, and defining the target or goal for the week.

Some of day one’s activities include:

  • Rules and introductions: The sprint facilitator introduces everyone and outlines the rules and procedures for the week.
  • Set a sprint goal: The sprint goal must be optimistic and answer the question, “Why are we doing this design sprint?” Your sprint goal should align with the product’s long-term goals and business strategy.
  • Identify users: Identify the users associated with your sprint goal and find participants for day five’s testing. You can use your own customers or a tool like User Interviews to find the right target demographic.
  • Create a map: A high-level flowchart from key players (customers) to an end goal with five to fifteen steps drawn on a whiteboard. The aim is to keep your sprint map as simple as possible without too much detail.
  • Interview experts: The sprint team has 15-30 minutes to ask each expert questions about the project, customers, topic, market, vision, and other details. The facilitator will add details to the map during these questions to provide context.
  • How Might We (HMW): The sprint team reframes problems using how might we questions. The purpose of HMW is to generate lots of ideas to begin ideation.
  • Organize HMW: The facilitator adds HMW to one of the steps on the flow chart, grouping similar ideas and identifying themes.
  • HMW voting: Each team member casts two votes on their favorite ideas. The winners get added to the map.

Check out this Map Checklist for more information on the first day of a design sprint. Alternatively, read pages 51 – 91 in the Sprint book.

Day 2 – Tuesday – Sketch

Things get a little more interesting on Tuesday with sketching ideas. The day starts with a group exercise called Lightning Demos, where teams present relevant ideas from other successful products. 

The aim of Lightning Demos is to look beyond your industry. For example, if you’re a productivity app, you might look to the automotive or food industry. Team members write these ideas on Post-It notes and stick them on the whiteboard.

After lunch, team members start sketching ideas using storyboarding techniques, including Crazy 8s and Solution Sketch.

At the end of the day, everyone places their sketches face down, ready to decide on Wednesday.

Check out this Sketch Checklist for more information on the first day of a design sprint. Alternatively, read pages 93 – 123 in the Sprint book.

Day 3 – Wednesday – Decide

On day three, the sprint team reviews each sketch in a five-step process:

  • Art museum: Taping up every sketch for the team to see
  • Heat map: Each team member reviews sketches silently and puts one to three small dots next to their favorite parts
  • Speed critique: The group discusses each sketch, pointing out the best ideas and solutions–limited to three minutes per sketch
  • Straw poll: The team silently chooses their favorite idea with a large dot to place their vote
  • Supervote: The Decider reviews each idea and casts a “supervote” for their favorite, and the solution the sprint team will prototype on day four

The sprint team spends the second half of day three storyboarding and planning for prototyping.

Check out this Decide Checklist for more information on the first day of a design sprint. Alternatively, read pages 125 – 160 in the Sprint book.

Day 4 – Thursday – Prototype

On Thursday, the sprint team brings the idea and storyboard from the previous day to life. The first step is to choose the right prototyping tool. John Zeratsky and Jake Knapp recommend using a tool that allows you to design and prototype fast!

With UXPin’s built-in design libraries, you can build mockups and prototypes in a matter of minutes, perfect for the demands of a design sprint! You can even use your own design system using UXPin Merge to build on-brand prototypes fast–PayPal’s product team can create a fully functioning one-page prototype in eight minutes!

Once you have chosen the right prototyping tool, it’s time to “divide and conquer.” To accelerate the prototyping process, the sprint team splits into five roles:

  • Maker: Primarily responsible for arranging UI layouts
  • Stitcher: The person in charge of information architecture and navigation
  • Writer: Writes all the copy for the prototype
  • Asset Collector: Collects assets like stock images, videos, icons, and other visual assets
  • Interviewer: Prepares for day five test by compiling the script and user testing questions

You can separate these roles however you feel will deliver the fastest results. It’s crucial to remember that the sprint team is only building a prototype for a single user flow. Avoid getting sidetracked with redundant pages, UI elements, and features. The goal is to create a prototype that solves a specific problem–like an eCommerce checkout or sign-up form.

Towards the end of day four, the team tests the prototype internally. You might also invite stakeholders to review the prototype and give feedback for improvements. 

Make sure you leave enough time for this review process so you can make changes, test, and iterate before the end of day four. If you’re using UXPin, you can send stakeholders a link to your prototype so they can review and add comments remotely. This feature is especially helpful for remote design sprints.

By the end of the day, your prototype is ready for user testing on day five. Check out this Prototype Checklist for more information on the first day of a design sprint. Alternatively, read pages 163 – 190 in the Sprint book.

Day 5 – Friday – Test

On the final day, you get to test and validate your prototype with the real users you identified on day one. According to the Sprint book, five is the magic number for usability participants. These five users will give you enough feedback to identify patterns and create actionable insights.

The Interviewer, from day four, will conduct user interviews while the rest of the sprint team watches from another room. It’s essential to have a camera showing the user’s face for expressions and a screen monitoring application.

The sprint team takes high-level notes using Post-Its to share and discuss these as a group at the end of the interview process. The team then organizes the notes into common patterns labeling them positive, negative, or neutral.

Lastly, the sprint team decides on the next course of action, which may include another sprint, further testing, or refining the prototype for a design handoff to development teams. If you need to share research and metrics across your organization, tools like Baremetrics can help track key performance indicators and validate that your prototype improvements are translating to business results. 

If the team decides to do another sprint, you can skip days one to three and go straight back into rapid prototyping and testing based on insights from the first design sprint.

Design Sprints With UXPin

Create fully functioning high-fidelity prototypes with UXPin quicker and easier than image-based design tools. With UXPin, you don’t have to compromise on prototype quality during a design sprint and get more meaningful results and feedback from participants.

Sign up for a free UXPin trial to enhance your next design sprint with the world’s most advanced rapid design, prototyping, and testing tool.

Web Design Inspiration – A Curated List of 7 Sites

If you’re looking for web design inspiration for your next project, then look no further. We’ve scoured the internet to find the most inspirational web design trends in 2022.

Whether you’re building your site on Webflow or using a no-code app builder like Adalo, this article features several inspirational web design ideas for your new website.

7 Website Design Sources of Inspiration

1. Think Outside the Box – Wildcatter Creative Studio

Wildcatter is a US-based creative studio and production company. They’ve worked with some big names, including HBO, EA Sports, Showtime, and Intel, to name a few. The website was awarded “Site of the Day” for February 24, 2022, on Awwwards.

Wildcatter does a wonderful job of creating an immersive user experience with fun animations and page transitions, a custom pointer, oversized bold typefaces, and witty copy. This complex website design is tricky because it often results in poor performance–something Wildcatter has done well to optimize.

Key takeaway: Your website design should embody your brand and the message you want to convey. Wildcatter uses its website to showcase its creative talent and ability to tell a brand story, which they’re trying to sell.

2. Clean Product Experience – Selfnamed

Selfnamed leans into a clean, minimalist aesthetic that puts product and usability front and center. The interface is light, structured, and easy to navigate, with a soft palette that reinforces a premium feel. What makes it stand out is how effortlessly it handles complexity—users can explore and customize private label skincare products without friction. It’s a great example of design that stays simple while supporting a layered, functional experience.

3. Recreating an Experience – LeCrans Wellness Resort

LeCrans is a five-star Swiss Alps-based wellness resort. The website, built on WordPress, showcases the resort’s breathtakingly beautiful surroundings with immersive video and images complemented by smooth animations and elegant typography.

LeCrans’ website designers have done a fantastic job of recreating Swiss Alps luxury with a soft color palette and minimalist layout. The website’s images complement UI design elements and help tell the resort’s story.

Key takeaway: If you’re trying to sell a real-world experience, use your website’s design to give customers a taste of what it’s like to visit your event or property. LeCrans does this well by giving you a sense of peace, tranquility, and five-star luxury.

4. Web & Mobile Cohesion – Emiozaki Web

Emi Ozaki is a Tokyo-based graphic designer and illustrator. Her design portfolio includes various global media projects, including product design, advertising, magazines, and branding.

Emi’s website design uses a mobile device frame as a central focus, creating a unique layout while ensuring a cohesive and consistent user experience across all viewports.

Key takeaway: Designers must pay attention to how their web design will translate to multiple screen sizes and devices. Emi Ozaki’s creative approach to responsive design gives mobile users a familiar device OS aesthetic while creating a unique and immersive desktop experience.

5. Immersive Storytelling – L’Atelier (BNP Paribas)

French-based bank BNP Paribas website L’Atelier tells the story of Social Mobility in the Digital Age. The web design utilizes parallax scrolling and animation to tell its story.

While there is a lot of movement and animation, L’Atelier’s designers do an excellent job of making the copy and story the primary focus. They also use different fonts and typography sizing to help break up the text, create suspense, and keep users engaged.

Key takeaway: Web design plays a crucial role in telling a story. Designers must ensure that the visual design and effects don’t impact the website’s usability or distract from the content.

6. Minimalist eCommerce – Juana Skin

Juana Skin is a UAE-based therapeutic beauty brand. The website’s pastel colors, minimalist layout, and subtle animations complement the brand’s natural, “ultra-clean” skincare product range.

Designers use color to highlight the product’s primary benefits and CTAs for each page design. Juana Skin uses arrows with animations throughout the website to draw attention to important content and CTAs.

Key takeaway: Maintaining a minimalist user interface design for eCommerce websites is crucial to keep customers focused on the product. Busy layouts and poor performance can distract users resulting in poor conversion rates.

The Google Store is another excellent example of minimalist design for an eCommerce website.

7. Onboarding Optimized – Ooki

Ooki offers four crypto products for trading, borrowing, lending, and staking. Ooki’s designers use clear CTAs to quickly onboard new customers from the homepage. Clicking the header CTA “Use Ooki” takes users directly to the product, removing the signup process.

Ooki’s streamlined onboarding process lets customers view and interact with the product before signing up and using it.

Key takeaway: Removing roadblocks and giving users a taste of your product could increase signups–especially if you’re in a highly competitive and innovative space like crypto. A free trial is a good option, but it creates an extra step and means users must give up personal information.

More Website Design Inspiration

Here are some more resources to inspire your next web design project.

  • Top UX Design Blogs: A collection of industry-leading websites discussing various UX topics and design trends.
  • Design Conferences: 40+ global design conferences for 2022–both live and virtual.
  • r/web_design: A Reddit community of over 570k designers sharing knowledge and information.
  • Behance: A platform owned by Adobe where designers can post screenshots of their design work as well as find web design examples and inspiration.
  • Dribbble: A similar platform to Behance where designers showcase their work. There’s also a marketplace for themes and templates, and you can hire designers through Dribbble.
  • web dev and web design: A Discord channel with 33k members discussing web design and development topics.
  • All Things Web Development: A Discord channel where people share knowledge on programming, IT, computer science, and web design.
  • </design>: A Discord coding community specializing in HTML, CSS, Javascript and PHP.
  • The Design Collective: A Discord web design community.
  • 10 Product Design Slack Channels: A blog post featuring ten product design channels on Slack.

UXPin – The World’s Best Website Design Tool

With UXPin’s built-in design system libraries, designers can immediately begin prototyping and testing website layouts. Create immersive user experiences with code-based interactions and animations.

Share your designs with clients or stakeholders for feedback and approval. Stakeholders and team members can use UXPin’s Comments to provide context, ask questions, request changes, or assign tasks.

Engineers can use UXPin’s Spec Mode to inspect designs, copy CSS starter code, read documentation, and view the style guide. They can also download the project’s assets–keeping everything in one place for a simplified handover process and smooth collaboration.

Try UXPin for your next web design project with a free 14-day trial.

UX Research Cheat Sheet

UX research is the bedrock for any design project. UX designers and researchers must gather insights about the market, competitors, and, most importantly, users.

This research continues throughout the design process as designers test ideas and gather feedback from participants and stakeholders. To be a good UX designer, you must be inquisitive and an active listener to truly understand your market and user needs.

In this UX research cheat sheet, we explore the research designers conduct at various stages of the design process and methods to gather and analyze data.

Get meaningful user testing and stakeholder feedback with code-based high-fidelity prototypes from UXPin. Sign up for a free trial and discover how UXPin can enhance your product’s user experience.

What can you Gain With UX Research?

Here are some of the primary benefits of UX research:

  • Eliminates bias and assumptions to help teams develop objective product designs that meet user needs
  • Allows you to create human-centered strategies and goals for your products
  • Provides insight into your users’ behavioral and usage patterns
  • Reduces the costs associated with inaccurate designs and strategies
  • Helps develop a long-term vision for the product roadmap
  • Provides data for stakeholders to support design decisions and secure resources

Research in the Design Process

search observe user centered

UX teams conduct research and test through the design process. These research methods change with each phase:

  • Discover: Empathize and define
  • Explore: Ideate and prototype
  • Test: Test
  • Monitor: Post-implementation

Let’s look a look at each of these in greater detail.

Discover

Discovery research happens at the beginning of the design thinking process. This early research is called the empathize phase because UX designers must put themselves into the shoes of their users to see the world from their perspective. 

Typical research methods during the discovery phase include:

  • Field research: Observing people in the environment where they use your product
  • User interviews: One-on-one interviews to understand users’ problems
  • Stakeholder interviews: Understand business needs and constraints
  • Diary studies: Users document using your product over a period
  • Internal research: Meetings with sales, marketing, support, etc. to gather insights from other teams
  • Review analytics: User analytics and heatmaps (if you’re designing for an existing product)
  • Usability heuristics: A set of ten principles from the Nielsen Norman Group used during a UX audit to evaluate a product’s usability

During discovery, UX designers must use this research to define user problems your product can solve. This research includes:

  • Competitive analysis: Identify competitor strengths and weaknesses and determine what their customers like and dislike about the products
  • User journey mapping: A visualization of how customers interact with your product
  • Empathy map: Identifies what users see, hear, think, and feel as they complete tasks or a user journey
  • User personas: A fictional character that represents a user demographic

Explore

Once UX designers have gathered and analyzed research, they ideate and prototype to solve users’ problems. Some explore research methods include:

  • Brainstorming: Use research to develop design ideas and solutions–typically a collaborative effort using a whiteboard and sticky notes.
  • Design: UX designers create sketches, wireframes, mockups, and other visuals to develop ideas for users’ problems.
  • Card sorting: Participants sort cards into categories they find relevant. These categories help UX designers build information architecture and structure page layouts.
  • Prototyping: Designers prototype throughout the design process, starting with low-fidelity paper prototypes to high-fidelity prototypes representing the final product.
  • Stakeholder feedback: Presenting user research and prototypes to stakeholders for feedback.

Test

Testing is a vital research tool that enables designers to validate ideas developed during ideation. While testing appears to be a separate step, UX designers conduct tests throughout the design process, particularly while ideating and prototyping. Some of these methods include:

  • Usability testing: Moderated and unmoderated tests with end-users on wireframes, mockups, information architecture, and prototypes.
  • Accessibility testing: UX designers must test prototypes and UIs against accessibility guidelines and users with disabilities.
  • Benchmark testing: Designers use benchmark tests to measure the success of product redesigns and upgrades.
  • Surveys: A quick research method for testing large groups of users with questionnaires.

Monitor

After a release, researchers must monitor the product and users to identify bottlenecks and pain points. The monitoring phase adopts many of the same tests and techniques UX designers use during discovery. Research methods include:

  • Product analytics: Researchers gather data to measure the releases’ impact on analytics like conversions, sales, funnel drop-offs, navigation, and more.
  • Support data: Researchers can use customer support data to determine if a design solution reduces tickets for the issues they were trying to solve.
  • User feedback:  Aside from support tickets, UX designers must make it easy for users to comment, report issues, and ask questions. User feedback is particularly important for enterprise products where users rely on these tools for work.
  • A/B testing: A/B testing is a common research method to measure the difference between two design ideas. It’s also helpful for measuring subtle differences, like a red vs. blue CTA button.
  • Heat maps and screen recordings: Give researchers insights into how users navigate web pages. This data is essential for determining page layouts and hierarchy.
  • Beta testing: An early product release, often to a select group of users. Researchers often combine beta testing with dairy studies to get as much meaningful feedback as possible before the official release.
  • Search log analysis: A product’s search log can reveal a lot about user behavior which can help UX designers restructure layouts so popular items are easier to locate.
  • Business assessment: Aside from user research, UX designers must evaluate a product’s business value performance. This information is important for stakeholder feedback and securing funding for future projects.

Quantitative vs. Qualitative UX Research Methods

testing user behavior pick choose 1

UX research involves a mix of qualitative and quantitative testing:

  • Quantitative: Tangible metrics and data
  • Qualitative: Behavioral observations, opinions, motivations, and emotions

Quantitative data is measurable, while qualitative data is subjective and open to interpretation. When combined, these two metrics can put research into perspective. 

For example, you notice a drop-off in conversions when you redesign an eCommerce checkout flow. The quantitative data tells you conversions fell from 5% to 4%. From user interviews, you learn that the new shipping methods are confusing. The qualitative data reveals what’s affecting conversions.

What Does the Research Process Look Like?

The research process will vary depending on the method, but there are several vital steps UX designers follow:

  • Hypothesis: Many UX studies start with an idea researchers want to validate. For example, “we will make it easier for customers to find products and increase conversions if we put our best sellers on the home page.”
  • Planning & preparation: A UX research plan defines objectives, determines the correct methodology, the research location, and the information researchers need to gather.
  • Conducting research: Researchers conduct tests or research according to the plan.
  • Compiling & analyzing results: Researchers must organize data to find patterns and opportunities. They might also have to present these findings to stakeholders for further analysis.
  • Take action: Finally, UX researchers must use their results to determine the next course of action.

Improve Usability Testing With UXPin

testing observing user behavior

UX designers rely on accurate user testing results. But most design tools lack the fidelity and functionality necessary to get meaningful feedback and test user experiences effectively.

UXPin is a code-based tool. So, designers can create code-like prototypes to provide usability participants and stakeholders with an accurate product experience.

Let’s explore a few of UXPin’s advanced prototyping features.

Variables

Most design tools display a graphical representation of an input field. In UXPin, input fields work just like they would in the final product. Variables allow you to capture user inputs and use that data elsewhere in the application–like a custom welcome message or populating a profile page.

States

You can create multiple States for any component in UXPin with different properties for each one. From standard button states to accordions and complex navigational menus.

Interactions

Interaction design is crucial for usability and product experience. UI designers can choose from an expansive list of triggers, actions, and animations to bring your prototypes to life.

UXPin takes things one step further than other design tools with Conditional Interactions, which allow you to create code-like “if-then” and “if-else” conditions which designers can use to validate an email or password. When combined with Variables, you can simulate a sign-up and login process–the possibilities are endless.

Expressions

Expressions give UXPin prototypes code-like functionality where designers can simulate form validation, build a functional shopping cart, validate credit cards, and more.

Accessibility

UX designers must always check user interfaces to ensure they pass accessibility standards. UXPin offers built-in accessibility tools to streamline testing with a Contrast Checker and Color Blindness Simulator.

Real Content & Data

How many times have you searched “lorem ipsum” for dummy copy or scanned Unsplash for the perfect image? UXPin’s built-in content generator allows you to populate UIs with relevant content like names, dates, numbers, addresses, and more. You can even match content by layer name where UXPin auto-populates data according to naming conventions.

UXPin also allows you to use your own data from Google Sheets, CSV, or JSON, to give users and stakeholders an authentic product experience.

Improve your UX research and testing with the world’s most advanced code-based design tool. Sign up for a free trial to experience the power and versatility of UXPin.

What Should the Designer-to-Developer Ratio Be and How to Scale?

The industry average for designer to developer ratio is between 1:10 and 1:20. Some of the biggest tech companies operate with much lower ratios between 1:5 and 1:8. Many factors influence the designer to developer ratio, and there is no secret formula early-stage startups can apply. Companies can take steps to optimize design workflows to make high designer to developer ratios more efficient.

In a quest to manage limited resources, many startups ask, “what is the ideal ratio of designers to developers?” While it’s a valid question, the answer isn’t that simple.

This article explores designer to developer ratios and what you can do to improve your design team’s productivity and efficiency. We also look at some of the biggest tech companies and how their designer to developer ratios have changed radically in the last decade.

Improve your design teams’ productivity and efficiency with UXPin Merge. A design tool that streamlines UX workflows and increases collaboration between designers and developers. Sign up for a free trial to experience the world’s most advanced code-based design tool.

What is the Designer to Developer Ratio?

An NN Group study that surveyed 557 people found “that half of respondents (50%) reported having at least 1 designer for every 10 developers at their organization.”

Here are the results of the NN Group’s survey in greater detail:

  • 1 designer to 100 or more developers – 4%
  • 1 designer to 51-99 developers – 4%
  • 1 designer to 21-50 developers – 12%
  • 1 designer to 11–20 developers – 16%
  • 1 designer to 6-10 developers – 25%
  • 1 designer to 5 or fewer developers – 25%
  • Unsure – 13%

Another study from Measuring U found similar results for 150 respondents in 2016/2017:

  • 1 designer to 71 or more developers – 13%
  • 1 designer to 51-70 developers – 7%
  • 1 designer to 21-50 developers – 12%
  • 1 designer to 11-20 developers – 21%
  • 1 designer to 6-10 developers – 18%
  • 1 designer to 5 or fewer developers – 10%
  • Unsure – 19%

Measuring U also looked at the researcher:designer:developer ratio and found that many companies in their study operate on 1:5:100. 

While these surveys provide helpful insight into the industry averages, there are many factors companies must consider, including:

  • Company size
  • Company maturity
  • Product design complexities
  • Product team ratios
  • UX team structure (researchers/designers)
  • User research methods
  • DesignOps
  • Tech stack
  • Design system governance and maturity
  • B2B vs. B2C products
  • Project management methodology–i.e., Agile, Scrum, Kanban

Measuring U makes an excellent point in the closing of their article, saying, “The number of UX staff you “need” depends on the needs of your product and organization. Ratios themselves might not be the right metric to determine whether you should hire a new designer or researcher.”

If you’re a startup looking for an industry-standard ratio or formula to make a decision, unfortunately, there isn’t a clear-cut answer. However, we can look to mature tech companies to see how their designer to develop ratios evolved.

Company Size & Maturity – Designer-to-Developer Ratio

team leaders teams

Measuring U’s survey found that 61% of small companies (less than 10k employees) have a lower designer/developer ratio, with fewer than one designer for every 20 developers.

A 2017 article from TechCrunch demonstrated a similar finding when they examined how designer/developer ratios changed as the organization’s scaled and matured. It’s important to note that at the time of writing the TechCrunch article in mid-2017, the industry was experiencing a shortage of UX designers, and some companies expressed a goal of a 1:3 designer/developer ratio.

Atlassian

  • 2012: 1 designer to 25 developers
  • 2017: 1 designer to 9 developers

Dropbox

  • 2013: 1 designer to 10 developers
  • 2017: 1 designer to 6 developers

LinkedIn

  • 2010: 1 designer to 11 developers
  • 2017: 1 designer to 8 developers

Uber

  • 2017: 1 designer to 8 developers (design team grew 70x from 2012 to 2017)

IBM

  • 2012: 1 designer to 72 developers
  • 2017: 1 designer to 8 developers

Alex Schleifer, VP of Design at Airbnb, says to “Grow design’s headcount in step with engineering and product hires.” Alex suggests a ratio of 1 designer for 6-8 developers. He says it’s important to set a baseline early on to help maintain consistency as the team scales.

Maturity also has an impact on designer/developer ratios. Measuring U found that 71% of companies in the initial and growth stages had fewer than one designer for every 20 developers vs. 40% for mature organizations.

The Rise of Design Thinking

The TechCrunch article also claims that factors other than size and maturity have impacted designer/developer ratios at big tech companies. 

Companies have found that focusing on design thinking and user experience has proven to deliver excellent business value. People often quote a famous 2016 2016 Forrester report that claims, “…on average, for every dollar you spend on UX, there’s a 100X return!”

When you look at the numbers from the tech giants we mention above, it seems that companies are placing more emphasis on design than they did in the past.

A mature company like IBM, which has been around for decades, went from 1:72 to 1:8 in five years–mirroring the trend of its younger peers. So, even if you’re a startup or small business, investing in design could deliver a good ROI

How Design Tools Impact Designer to Developer Ratios

process teams

Design tools also impact designer/developer ratios. An excellent example of scaling design without increasing employees is how PayPal used UXPin Merge to scale its design process.

PayPal had a disproportionate designer/developer ratio of 1 designer for every 200 developers. The entire design department had five designers with 60 products and over 1,000 engineers. Erica Rider, Senior Manager for UX – Developer tools and platform experience at PayPal, had the task of scaling design without growing the design team itself.

After much trial and error, Erica came across UXPin Merge–a tool that allows you to sync code components from a repository to UXPin’s design editor.

PayPal uses the Microsoft Fluent UI for its internal products. They synced Fluent’s React component library from a Git repo to UXPin, so design and development teams were using the exact same components to develop new products.

UXPin Merge’s drag and drop design process meant that PayPal’s product team could take over designing, prototyping, and usability testing, completing 90% of the work, leaving UX designers to focus on more high-level UX initiatives.

By switching to a code-based design tool and utilizing an existing component library, PayPal’s product teams were able to build fully functioning prototypes eight times faster than experienced UX designers had previously.

This significant boost in productivity meant that PayPal’s disproportionate designer/developer ratio no longer influenced the product development process. And, with such an impressive ROI, Erica was given resources to grow the UX department to scale user experience initiatives.

The key takeaway from PayPal’s case study is that tools could help companies scale design, even with low designer/developer ratios. Sign up for a 14-day trial to experience Merge using our MUI integration.

The Benefit of a Design System

design system 1

Another way to increase productivity and consistency is through a design system. If you can’t afford to build and scale a design system, consider customizing a component library as PayPal did with Fluent UI.

Design systems allow designers to focus on building mockups, prototypes, and usability testing rather than designing from scratch every time. They also achieve a much higher degree of consistency and streamline design handoffs.

This increased efficiency means you need fewer designers to developers. The faster time to market also gives your company a competitive edge.

The Impact of DesignOps

DesignOps has proven to optimize UX workflows, scale design, and influence designer to developer ratios. Many organizations experience increased productivity, resulting in fewer designers completing more work. 

“We were able to decrease the amount of investment required for rote design work by 75% after implementing DesignOps at a Fortune 100 financial company. This freed up considerable resources to invest in mission-critical UX research, design thinking, and product innovation.”

Theresa Neil, Founder of Guidea and co-author of DesignOps 101: Guide to Design Operations

Startups and small companies often don’t recognize the need for DesignOps because they see it as a “nice to have” added expense. But, the benefits of DesignOps mean that your design team is more productive. If you can’t afford the designer to developer ratios that the tech giants above achieve, setting up DesignOps could help increase productivity with less cost.

Optimize Design With UXPin Merge

uxpin merge react sync library git

Hiring designers to scale your design operations is costly and unrealistic for many small businesses and startups. As demonstrated with the PayPal case study, UXPin Merge can significantly increase productivity and reduce time to market–even with a higher ratio of designers to developers. 

You can sync React components to UXPin directly through Git or use our Storybook integration for other popular front-end frameworks like Vue, Angular, Ember, Web Components, and more.

Prototype, test, and deploy faster while creating better experiences for your customers with UXPin Merge. Sign up for a 14-day trial and get a taste of Merge through our free MUI integration

The Ins and Outs of Design System Ops

design system ops

Key Takeaways

  • Design System Ops is a way of operationalizing and standardizing design systems and its components
  • It can help teams reduce inefficiencies, optimize workflows, evangelize design system, and make it easy to scale the system.
  • Anyone can start Design System Ops, just find out who your users are, define the Design System Ops issue you want to get rid of, implement a solution, and measure its impact.
  • A good tool for Design System Ops is UXPin Merge that helps you import UI components from your design system and use them to create prototypes in the design editor.

More Ops roles appear as companies and departments look for efficiencies and reduce operational costs. You’ve probably heard of DesignOps, but what do you know about Design System Ops?

We have based this article on UXPin’s 2017 webinar Design System Operations with keynote speaker Kaelig Deloumeau-Prigent, who was working on Shopify’s Polaris design system at the time.

Find out what design system Ops does and how you get started in your organization. We highly recommend our free eBook DesignOps 101: Guide to Design Operations, which covers DesignOps fundamentals.

Optimize your design system with UXPin–the world’s most advanced end-to-end design tool. Whether you’re a startup with a team of one or a multinational organization with thousands of employees worldwide, UXPin has a solution to meet your needs. Sign up for a free trial to explore what UXPin has to offer.

What’s the Purpose of a Design System?

A design system must provide designers and engineers with the tools to build and scale products quickly, coherently, and consistently. 

More than a collection of components–a design system provides users with documentation, best practices, principles, and guidelines to ensure team members ship products that meet brand and usability requirements.

What is Design System Ops?

Design System Ops seeks to optimize the processes and standards for taking new design system components and templates from design to release.

The aim is to reduce “decision fatigue” with a frictionless delivery process through tools and protocols. This optimization allows the design system team to spend more time on creativity, innovation, and quick delivery rather than operational procedures and decision-making.

Why Operationalize Design Systems?

design system library components

As UX and design system expert Nathan Curtis famously said in a 2016 Medium post: “A Design System isn’t a Project. It’s a Product, Serving Products.”

Design System Ops must reduce workflow inefficiencies to serve its users and products while bridging the gap between design and development. The goal is to implement tools and processes that ensure new releases mirror the original design’s fidelity, functionality, and usability.

Who is Responsible for Design System Ops?

A design system Ops manager must be someone experienced with design and development. They must understand both processes to identify and fix problems effectively.

Design system knowledge and experience are also essential. An Ops manager cannot optimize the operations without a fundamental understanding of building, managing and scaling a design system.

Unlike traditional DesignOps, which focuses on design, and DevOps, which focuses on development, design system Ops straddles these two disciplines providing support to designers and engineers.

How Design System Ops Supports Developers

design and development collaboration process product communication

To ensure releases meet design specifications, design system Ops spends a lot of time creating tools to support developers. The operations look at the end-to-end development process to find inefficiencies and provide solutions.

Here are some examples of how Ops supports developers:

Design Handoffs – Optimizing Designs for Performance

  • Ops must define what happens to an image or asset from design to development. If they must convert an asset from PNG to webp, how do they do that–is there a tool, or do they do it manually?
  • What’s the best way for engineers to load assets?
  • What format do engineers use for assets (PNG, JPG, SVG, etc.)?
  • Do developers optimize images during the build, or do they use a CDN?
  • Standardizing and optimizing HTML and CSS markup for assets to deliver the best performance.
  • How do engineers use fonts for various platforms, including the web, iOS, Android, etc.?

The Developer Experience

  • Local development environments must be fast to set up so engineers can start building immediately. For example, creating a new project should be as simple as yarn start, npm start, or whatever your tech stack uses to initiate.
  • Linter configuration–The standards and practices for writing code.
  • Ops must answer the question, “how do you build a new component?” What steps must developers take to ensure maximum consistency and efficiency?
  • Releasing updates should be effortless, preferably a quick single-button release–how does Ops implement such a process?

Testing

  • Ops must assess how devs run tests locally and how long that process takes. If necessary, they look for tools and methods to streamline testing so engineers don’t waste time waiting for tests to run.
  • Visual regression testing–how do changes to a component impact the design system, and how do devs test?
  • How can Ops optimize and automate accessibility testing? For example, using tools to inspect code for ALT tags.

These are just some examples of the design system Ops approach to supporting engineers. The overarching theme is “how do we make reduce decision-making so engineers can ship releases faster?”

The design system team and its users should never have to ask, “how do I do this?” or “where do we find that?” Ops’ goal is to maximize design system efficiency and reduce time-to-market for releases.

Design System Ops–Where to Start?

1. Who Are Your Users?

To implement design system ops, you must start with user research. The first question you need to ask is what tools and languages are team members using?

  • For developers: What is the current tech stack, and what IDEs do engineers use?
  • For designers: How do UX designers create wireframes, mockups, and prototypes?

When Ops understands how teams work, they can find and fix inefficiencies. The goal is to find bottlenecks and roadblocks in the design system release process.

2. Define the Problem

Once Ops identifies an issue, it’s crucial to define the problem to implement the correct solution. Is there something wrong with the process, or is it a matter of better training?

3. Implement Findings

Once Ops finds a solution for a specific problem, they need to implement it. Implementation might include providing training, workshops to promote usage, updating documentation, etc.

4. Measure and Monitor Results

Design systems Ops uses various tools and metrics for monitoring and measuring a design system and its users. If you have a website for your design system, tools like Google Analytics can track clicks, downloads, and other metrics to see how people use it.

Ops also want to monitor critical metrics to identify issues and bottlenecks, including:

  • Build time: How long does it take developers to build new components–from design handoff to release?
  • MTTR (mean time to repair): How long does it take to fix design system issues?
  • Quality: Error and rework rates. Frequency of usability and accessibility issues.

As Kaelig Deloumeau-Prigent mentions in UXPin’s Design System Ops webinar, “Success should be measured by the problems you solve rather than the tools you put in place.”

In other words, don’t be quick to fix something that isn’t broken. Design systems Ops isn’t about introducing tools; it’s about finding and fixing inefficiencies.

Optimize Your Design System With UXPin Merge

uxpin merge component responsive 1

Bridging the gap between design and development has never been easier than with UXPin Merge.

Merge allows you to sync a design system hosted in a repository to UXPin’s editor so designers can build prototypes with fully functioning code components. For teams managing complex backend integrations or requiring secure API access to data sources, DreamFactory provides a self-hosted platform for governed API access that developers can leverage alongside your design system infrastructure.

Sign up for a 14-day trial to experience UXPin Merge with MUI integration.

The Guide to Remote Design Sprints

Remote Design Sprints

Remote design sprints have become increasingly popular as more people collaborate from different locations around cities and across the world. While the pandemic accelerated the move to remote work, the trend started long before 2020–when companies sort to build teams based on talent rather than location.

With proper preparation, remote design sprints can be as meaningful and productive as in-person events. This step-by-step remote design sprint guide provides tips and advice to ensure yours is a success.

Start by choosing the right tools. UXPin is a code-based design tool built to enhance teamwork and collaboration. Sign up for a free trial to test UXPin for your next design project.

What is a Design Sprint?

A design sprint is an intensive group session where a team gathers to solve a specific design problem in five days. The sprint includes a mix of group and individual work to develop ideas, choose the best one, build prototypes, test and iterate until they find a solution. The goal is speed and maximum efficiency.

A remote design sprint follows the same format, but team members connect via video conferencing like Zoom or Google Meet rather than gathering in a room.

Who is Responsible for a Design Sprint?

A facilitator organizes and leads a design sprint team. They’re in charge of:

  • Booking the venue
  • Setting the time and date
  • Liaising with teams
  • Gathering stationery and supplies
  • Organizing drinks and snacks
  • Running the design print

In some cases, the facilitator may have help from an assistant who takes care of the non-design-related details so they can focus on the sprint itself.

In a remote design sprint, it’s crucial to have a facilitator and assistant to organize and run the sprint–especially when you’re working across multiple time zones.

The Challenges of a Remote Design Sprint Process

process brainstorm ideas
  • A virtual environment doesn’t make it easy for organic conversations at the snack table or water cooler–which is often where great ideas originate.
  • It’s challenging to replicate the organic flow of dialogue and ideas you get in a live setting. Facilitators must make more effort to include participants in the conversation.
  • Aligning time zones is a significant challenge, especially where teams are on opposite sides of the world. Remote design sprints require lots of planning to overcome this issue.
  • Directions are often unclear when written down without explanation or context–information gets lost in translation. The design sprint facilitator must make an extra effort to ensure everyone understands the format and objectives.
  • Teams feel disconnected in a remote design sprint environment. Even though you can see people’s faces, there are fewer non-verbal communication and cues.
  • Poor video quality, lighting, audio, and background distractions can make communication and collaboration difficult.

While these challenges might seem overwhelming, there are tools and strategies that make it easier to run remote design sprints. With that, let’s dive into our step-by-step guide on remote design sprints.

Remote Sprint Preparation

A lot of planning and preparation goes into a “regular” design sprint. The remote version requires more planning and attention to detail. These are some things to consider to make your remote design sprint a success:

Lighting, Audio, and Video

Standard PC audio and video are insufficient for running a design sprint. We highly recommend everyone be on headsets for team members to be focused and tuned in.

It’s also essential that everyone have a good webcam–remote design sprints work best with everyone visible on a video call to maximize participation and engagement.

The sprint’s facilitator and assistant must have excellent sound, video, and lighting quality. If this means purchasing extra equipment, then make the investment; it’ll make for a smoother experience for everyone when they can see and hear instructions better. You can buy a webcam, headset, and portable light for just over $100.

If you can afford it, purchase a similar setup for every team member, so everyone experiences the same quality. Most companies provide a budget for this, so check with your finance department or team lead.

iPads & Additional Screens

Most people work with two or more screens these days. Check with team members to see who has a dual monitor setup, and consider buying an extra one for those who don’t.

A remote design sprint works best when splitting video conferencing with your work surface for notes, whiteboard, design tool, etc. That way, team members can always see each and what’s happening in the shared workspace.

iPads for sketches and note-taking go a long way to replicating a live environment and enhancing the design sprint experience. Not everyone has an iPad, and they’re expensive, but they’re the perfect tool for remote design sprints.

Choose the Right Tools

user laptop computer

Choosing the right tools and platforms is crucial for a remote design sprint. Everything must be in-sync, even down to note-taking. You must also try to use as few platforms as possible. 

For example, a tool like Basecamp or Notion can work for messaging/comments, note-taking, asset uploading, and whiteboarding (albeit with limited functionality), so all communication is in one centralized location. Avoid using additional tools like Slack or Microsoft Teams just for messaging.

When collaborating remotely, it’s also wise to protect your connection and shared assets with the best VPN service. This ensures your files and conversations remain secure while working with team members across different networks.

Here are some recommendations for remote design sprint tools.

Note-Taking & Discussion:

  • Basecamp: Built specifically for remote collaboration
  • Google Keep: A fantastic free collaborative note-taking application
  • Notion: Similar to Basecamp with excellent features for remote sprints

Virtual Whiteboarding:

Virtual whiteboards have come a long way in a short space of time. Here are some of my favorite options to replace stick notes/Post-Its:

Video Conferencing:

User Testing:

Design & Prototyping:

While there are many collaborative design tools, you need an option with seamless collaboration for cross-functional teams. UXPin stands out as the best option for real-time prototype collaboration.

It has all of the features members of your team need. Even non-designers can use UXPin to build layouts and prototypes with built-in design systems–simply drag-and-drop components onto the canvas to design mockups and prototypes. Plus, you can test prototypes and get feedback from participants and stakeholders outside of your sprint. Alternatively, if you’re building custom applications or need to integrate design outputs with backend systems, DreamFactory provides governed API access to connect your design prototypes with data sources and enterprise systems seamlessly. 

They can view your work and leave feedback without a UXPin account giving everyone easy access without any barriers. Sign up for a free trial to explore UXPin for your next remote design sprint.

Choose a Date & Time

Scheduling a remote design sprint is a little more challenging than a live event–especially with remote teams across multiple time zones. Try to find a time within working hours or as much overlap as possible.

For example, hosting a design sprint with teams in Europe and the US would mean US participants start as early as possible while the Europeans do an afternoon/evening session.

Differences greater than 8 hours will require more scheduling and planning. You could get everyone together for briefings and group sessions and allow people to split for individual tasks during their working hours.

Another option is to separate teams into two groups and develop a strategy to run parallel sprints where you link up once a day to share notes.

Get an Assistant

It’s essential that you have a facilitator and assistant for a remote design sprint. The facilitator is focused on the sprint while the assistant monitors video for participation and cues, checks in with team members via chat, flags questions, and does all the admin necessary for a remote meeting. 

Pre-Sprint Meetup

Once you have selected your tools and dates for your remote sprint, it’s essential to schedule a pre-sprint meetup. During this session, you outline the format, run through the rules, and introduce everyone to the tools.

It’s also a good idea to run through each person’s sound, video, and lighting setup to identify any issues before the sprint. You can even run a super-fast 15-20 minute design project where team members must use all available tools to create a single icon or small component.

A pre-sprint meetup aims to iron out any issues ensure everyone has what they need and knows how to use the tools so you can jump straight into sprinting from day 1!

Running a Remote Sprint

camera video play

Always-On Video

Video is crucial for effective communication and collaboration during a design sprint. The sprint assistant also monitors video and chat if someone has a question or issue.

Treat Your Team

Consider ordering everyone on the team beverage of their choice (tea/coffee) each morning to start the day. Find out what each person’s favorite local is and get it delivered.

You can also provide lunch the same way or give everyone vouchers to order food. The aim is to team members maximum downtime for breaks and meals.

Breaks

In the “sprint manual,” Jake Knapp’s book Sprint recommends a break every 90 minutes, but this might be a little too long for remote sprints where screen fatigue takes its toll.

We recommend breaking remote sprints into 45-60 minute sessions with 5-10 breaks and then a 60-minute lunch/main meal break. 

Some facilitators have found playing music during breaks allows team members to leave the room and return when the music stops. It’s a passive way to maintain control over breaks and get people back for the next session.

Remote Design Sprint Steps

A design sprint process uses design thinking with a day for each step:

  1. Map: Use a collaborative digital whiteboard tool to map user journeys.
  2. Sketch: To minimize screen time, consider allowing teams to sketch on paper for day two. They can take a pic or scan their ideas and post them to the whiteboard for presentation.
  3. Decide: Use a tool like Basecamp or Notion with your digital whiteboard to brainstorm a plan of action and storyboard ideas.
  4. Prototype: Use a design tool like UXPin to build prototypes of your product design idea.
  5. Test: Test prototypes from UXPin with your preferred user testing tool.

Additional Remote Resources

Check out this article for a more detailed guide to running a design sprint with a distributed team. We also recommend these resources for remote work and design sprints:

See How UXPin Can Make your Remote Design Sprints Successful

UXPin is a collaborative design and prototyping tool that meets the demands of today’s remote design teams. As you start to rely more on remote design sprints, you need a platform like UXPin that lets teams create fully functional prototypes in real-time.

Start your free trial with UXPin today so you can see how much easier your sprints become when you have a tool with features created for how today’s designers work.

How to Improve Feedback Loops in Design Process

How to improve feedback loops in design process

Key Takeaways

  • Feedback loops have three stages, that is action, effect, and feedback.
  • They are used to understand users, validate design ideas, build information architecture, as well as improve usability.
  • Feedback loops solve problems and answer questions, but they can be either positive (increase an input action) or negative (decrease an input action).

Understanding feedback loops is crucial for designers to create engaging user experiences. This feedback is also beneficial for failure-proofing design concepts so designers can avoid wasting time and resources building products and features users don’t need or won’t use.

These feedback loops aren’t always obvious, so designers must study data and use active listening methods to get to the heart of the problem.

To improve feedback loops in the design process, designers must learn to recognize these patterns throughout the real world. Everything is a feedback loop.

Our brains are constantly assessing the world through a series of feedback loops. This feedback is crucial for learning about the world and developing appropriate reactions.

We see these feedback loops in digital products too. The best designers understand these feedback loops are a critical part of UX design psychology and the overall user experience.

Improve your user experience design with advanced prototypes for improved testing. Sign up for a free trial to discover how UXPin can enhance your digital product design.

What are Feedback Loops in Design?

Feedback loops happen in three stages:

  • Action
  • Effect
  • Feedback

The most common example in digital product design is when a user posts something to social media:

  • Action: A user posts a photo
  • Effect: Other users comment and like
  • Feedback: Affirmation that people like your content

In this feedback loop example, a social media user gets the reward of affirmation from other users incentivizing them to repeat this action.

In an enterprise application, a user might use a digital product to streamline a workflow to complete tasks faster and more efficiently:

  • Action: A user completes a mundane task using a digital product
  • Effect: The product saves them time
  • Feedback: The user’s boss praises them for their efforts, or they have more time for other more important work

This powerful design psychology keeps users engaged and makes digital products more enjoyable to use. The more enjoyable the experience, the more likely people will continue using your product or website.

How Do Feedback Loops Apply to Product Design?

Designers use feedback loops throughout the UX design process to understand users and solve their needs.

  • UX research: UX designers use a human-centered design approach to look for behavioral patterns and problems
  • UX design: Designers create feedback loops with microinteractions, system messages, etc. to help users complete tasks successfully or provide context to errors
  • Usability testing: Researchers study users to identify reactions when completing tasks

Why is a Feedback Loop Important in Design?

Understanding feedback loops in product design is vital for several reasons.

Cause and Effect Relationships

Feedback loops help UX designers understand cause and effect relationships for specific tasks and features in a digital product. Some of these relationships are immediate and obvious, while others have long-term impacts on users and society.

For example, social media is an addictive experience for teenagers. The immediate effect is that teens get a dopamine hit from likes and positive comments. They use the social media platform more, creating business value. But the long-term effects of teenage social media use are bad for mental health.

Not only is this bad for society, but it could result in fines or legislation, making it harder and more costly for the company to do business.

UX designers must constantly evaluate products and test ideas to fix or prevent adverse effects from feedback loops. For example, Instagram removed like counts test the impact on mental health. The idea is that people wouldn’t measure themselves against other users and feel less liked or important.

Idea Validation

User feedback helps designers validate ideas and hypotheses–how does the user react to a new component or feature designed to solve a specific problem?

For example, a UX designer might make error messages clearer and more helpful if users have trouble completing forms, providing a feedback loop to guide people through the process. These feedback loops might include an error message telling the user a password must be a certain character length or correct formatting for the email address.

Understanding Users Better

Feedback loops help UX designers understand users and behavioral patterns. By identifying what satisfies and frustrates users, UX designers can build better user experiences.

For example, users might express frustration when they cannot cancel a paid plan. Many product designers intentionally hide this feature, making it difficult in the hopes that the user gives up. 

The problem with this strategy is that you damage trust in the brand by frustrating the user, making it less likely they’ll return as a paying customer in the future. Baremetrics, a subscription analytics and revenue recovery platform, helps teams understand churn and cancellation patterns—making the cancelation process easy satisfies the user and makes it easier to nurture them back to a paid plan.

When UX designers understand human behavior and satisfying feedback loops, they can build positive product experiences that keep people coming back.

Prioritize Information Architecture and Layouts

Feedback loops and patterns help designers identify content and features that matter most to users. This information is crucial for organizing information architecture and prioritizing layouts.

A great example is how designers place the most important CTA above the fold on a website or prioritize navigation in the header vs. the footer. Designers can only achieve this by understanding user behavior and how they interact with a digital product through feedback loops.

Improve Usability

Feedback loops provide insights for designers to make usability and accessibility decisions.

Positive vs. Negative Feedback Loops

There are two types of feedback loops:

  • Positive feedback loops
  • Negative feedback loops

Understanding whether a feedback loop is negative or positive is crucial for designers to take the correct course of action.

It’s important not to get confused by the connotation of negative and positive; these titles don’t refer to feedback loops being either good or bad. Rather it’s a response to change, i.e., less or more.

Positive Feedback Loops

Positive feedback loops cause an increase in the input action. For example, if someone posts something on social media, they’re rewarded with affirmation and repeat the action.

In a more simplified example, adding a hover state to links and buttons tells users it’s a clickable UI element, thus increasing clicks and resulting in a positive feedback loop.

Negative Feedback Loops

Negative feedback loops cause a decrease in the input action. For example, if someone can’t find what they’re looking for on a search engine, they might get frustrated and use another service, resulting in less of the input action–searching.

You might think you need more positive feedback loops and fewer negative feedback loops to create a good user experience, but there are times when you might prefer one over the other. 

For example, suppose you’re designing a productivity application that helps users organize and automate email tasks. In that case, your product will decrease the action of checking emails–which means your product is successful even though this is a “negative feedback loop.”

Best Practices to Improve Feedback Loops in the Design Process

testing observing user behavior

1. Collect and Analyze Data

Data and analytics can tell you a lot about user behavior and feedback loops. If you’re redesigning a product or website, you can use various metrics to monitor its success.

2. Conduct Usability Testing

Data combined with real-life user interviews can help designers understand and pinpoint problems.

During usability studies, UX designers use empathy maps to put themselves in the user’s shoes. Empathy maps tell UX designers what someone thinks, feels, says, and does–which are essentially feedback loops resulting from interaction with a product.

3. Use Feedback Loops Ethically

UX design psychology and feedback loops have powerful effects on users and could potentially reshape society. A great example is how the world changed post social media.

UX designers and organizations have an obligation to use design psychology ethically and not manipulate users with feedback loops designed to encourage unhealthy behavior.

4. Feedback Loops Must Solve Problems and Answer Questions

UX designers must find solutions to common problems and questions. Here are some examples of questions a user might ask while interacting with a digital product:

  • How long will this take?: Using a progress bar during onboarding or checkout flow tells users how many steps they still have to complete.
  • Can I click this?: Designers must use color, states, hierarchy, and other UI methods to tell users what they can and can’t click. 
  • Is this working?: Providing system feedback is crucial for users to understand when something is loading. You can also use error messages or haptic feedback to alert people to a problem that needs their attention.

Create Enjoyable User Experiences With UXPin

Prototyping and testing are crucial stages of the design thinking process. Prototypes allow designers to test and validate ideas with end-users. The problem is that most design tools cannot replicate the fidelity and functionality code.

UXPin is a code-based design tool with powerful features that allow design teams to build high-fidelity, fully functioning prototypes. Better prototypes result in meaningful feedback from usability participants and stakeholders, giving design teams accurate insights to make changes and iterate.

Sign up for a free trial to see how UXPin can enhance UX workflows and design product experiences your customers will love.

Transitioning from a Product Designer Role into DesignOps

Transitioning from a Designer into DesignOps

DesignOps is a fast-emerging and exciting UX discipline born from the success of DevOps for engineers. There are loads of opportunities to enter DesignOps as a leader or program manager at some of the world’s largest organizations.

This article will give you an introduction to the role of a DesignOps leader, the skills required, and how to land your first job.

As a DesignOps leader, it’s your job to find tools to streamline UX workflows. Discover the world’s most advanced collaborative design tool. Scale DesignOps with UXPin’s Merge technology. Request access to Merge.

What is a DesignOps leader?

The primary objective of DesignOps is to streamline processes and remove obstacles and distractions so that designers can focus on design.

A DesignOps leader works closely with a design leader to implement the systems and processes for the organization to achieve its design goals. This inward-looking role focuses on team performance and optimizing the end-to-end design process.

In Measuring DesignOps Impact, Patrizia Bertini, Associate Design Operations Director at Babylon, summarizes the roles of a design leader vs. DesignOps leader as follows:

DesignOps Leader:

Inward looking and process-oriented

  • Mission: the How / the performance
  • Focus: End-to-end design process & teams
  • KPIs: Team health, spending, & performance metrics
  • Deliverables: Operations roadmap & strategy
  • Skills: Change management

Design Leader:

Outward looking and product-oriented

  • Mission: the What / the product
  • Focus: Product/service vision & individuals
  • KPIs: Product & experience metrics
  • Deliverables: Product roadmap & design strategy
  • Skills: Influence & negotiate

What is a DesignOps Leader’s Responsibility?

team collaboration talk communication 1

In DesignOps – How to Improve Your Design Workflow and Operations, we go into great detail about the DesignOps role. Here are some key roles and responsibilities of a DesignOps leader:

  • Operations management: Creating an operations roadmap with long-term goals and identifying the training required to achieve milestones and objectives.
  • Process design: Creating the systems, processes, and tools teams need to complete their work, including frameworks for collaboration across the organization.
  • Project management: Managing UX workflows, assigning tasks, setting deadlines, and removing bottlenecks. The DesignOps leader also organizes and facilitates design sprints.
  • Communication strategy: DesignOps leaders ensure design teams communicate effectively among themselves and across the organization. They also create systems for storing and sharing data to be accessible to everyone.
  • Onboarding: Hiring new employees and providing the orientation and training to ensure they integrate with the team. Read our eBook on the topic of managing the team: DesignOps: How We Work Together
  • Culture: Organizing team-building activities to instill company culture and individual development.
  • Budgeting: A DesignOps leader must outline the design team’s operational expenses with justification for costs. They’re also in charge of assigning budgets and managing design operations’ cash flow.
  • Legal: Working with the legal team to create legal documentation like NDAs for usability participants.
  • Design procurement: Managing all purchasing decisions with the financial department.
  • IT & security: Working with the IT department to ensure compatibility and security of design tools.

DesignOps Skill Set

Change management is one of the core skills of a DesignOps manager or leader. They often introduce teams to new tools, processes, and workflows. As Patrizia Bertini puts it in Measuring DesignOps Impact, “DesignOps changes the existing reality to bring more value. It’s a very transformative discipline.”

DesignOps leaders have excellent project management skills, capable of leading teams towards a shared path and goals. Understanding design processes, software, and technology is vital for DesignOps leaders to manage team members effectively.

A DesignOps leader is an excellent communicator and collaborator. They must be capable of engaging with everyone from an entry-level UX designer to C-level management and stakeholders. They must also be confident public speakers to host workshops, design sprints, and other presentations.

DesignOps also requires excellent business acumen to manage budgets, communicate with stakeholders (HR, technical, finance, legal, IT, etc.), and develop strategies that align with the organization’s long-term business goals.

What Companies Have DesignOps Teams?

You’ll typically find DesignOps teams in large organizations where bureaucracy, silos, and other inefficiencies impede the design process. But any company can apply the DesignOps mindset without a dedicated team or leader.

interaction click hi fi 2

Chapter one of DesignOps 101: Guide to Design Operations explores the DesignOps mindset teams can apply with or without a leader. The Nielsen Norman Group defines DesignOps in three primary areas:

  1. How we work together: Organize teams, collaborate, and humanize environments and gatherings for more efficient work.
  2. How we get work done: Standardize processes, harmonize a shared understanding of design intelligence, and prioritize projects.
  3. How our work creates impact: Measure work to create accountability, socialize as a tool to educate others on the value of design, and enable the use of design thinking and related activities.

Find out more about the DesignOps mindset here and read Airbnb’s article on the topic How we manage effective design at scale.” 

For insights on how DesignOps works in a large organization, we recommend reading Dave Cunningham’s article documenting his first six months as a DesignOps manager at Co-op Digital in the United Kingdom.

What is the Skills Matrix?

A skills matrix visualizes a team’s skills and competency to pair the right members for a given project. DesignOps leaders will use a skills matrix for three primary purposes:

  1. Design skills pairing for projects
  2. Identify skills gaps and arrange relevant training
  3. Sourcing and hiring talent with a specific skill set to complement the team

You can learn more about the skills matrix and a step-by-step process for creating one here.

Where to Look for a DesignOps Job?

search looking glass

The first place to start is within your current job. In chapter five of DesignOps 101: Guide to Design Operations, we outline How to get started with DesignOps in Your Company so you can pitch the idea to management and stakeholders.

You can also find DesignOps jobs on all the popular job boards, including:

  • Indeed
  • Glassdoor
  • LinkedIn Jobs
  • ZipRecruiter

We recommend checking out DesignOps Assembly (DOA), founded by experts Elyse Hornbacher and Meredith Black. DOA helps people interested in DesignOps to learn and grow. They have chapters across the United States, South America, Australia, and Europe.

Solving DesignOps Challenges With UXPin Merge

By bridging the gap between design and development, UXPin Merge solves many DesignOps collaborative and workflow challenges. Merge allows you to create a single source of truth by syncing a component library or design system from a repository to UXPin’s design editor.

With Merge, DesignOps leaders don’t have to worry about syncing design systems for designers and developers or managing multiple tools for storage, communication, collaboration, and documentation. Everything is in one place for the entire team to access at all times.

Discover how UXPin Merge can optimize your UX workflows and enhance collaboration between design and development.

The Ultimate Guide to An Effective UI Design

The ultimate guide to an effective UI design

Did you know that as many as 88% of users will not come back to an app or site after just one bad experience? This only goes to show the importance of UI design, which goes way beyond aesthetics and has a crucial impact on user experience.

In the following guide, we’ll cover everything you need to know when designing a user interface – from explaining “what is UI?” and discussing the key elements, all the way through to sharing the newest UI trends for 2022 and beyond.

What is UI design? 

UI design which stands for User Interface design refers to the process of creating a digital product’s graphical layout to support the final look and feel of the application. It includes a variety of elements that users interact with such as images, animations, sliders, text fields, buttons, etc. Good UI design translates into a friendly user experience, which is why it should be part of every software development process. 

Let’s now take a look at the elements that you can use while designing an interface. 

UI Design – UI Elements that Every Designer Should be Familiar With

There are a variety of UI elements, which you can use while designing a user interface. We can split them into three categories:

Input elements

Input elements are the most popular category. They require users to provide all sorts of information, such as, their age, reason for purchasing, etc. The input can come in a variety of formats including text, graphics or audio. Input elements can take the form of:

  • Dropdowns
  • Combo boxes
  • Buttons
  • Toggles
  • Text/password fields
  • Date pickers
  • Checkboxes
  • Radio buttons
  • Confirmation dialogues

Output Elements

Output elements are the outcome of the actions you take with input elements. Their character is never neutral – they display alerts, warnings, success or errors. For instance, if you upload an image whose format is unsupported, you’ll get a message saying “unsupported image” and you’ll immediately know that you have to provide an image in a different format. 

Helper Elements

The third category falls into an umbrella term for all the elements that can’t be placed within the output or input categories. As the name indicates, they assist the user in understanding the contents of a site and/or finding their way around the interface. 

Helper elements can be further broken down into three subcategories:

  • Navigational, that helps you navigate through the interface. Some examples include menus, breadcrumbs, link lists, etc.

Informational, that tells you which step of the user journey you’re currently at, or which processes the website is currently running. Progress bars, icons, and toolbars are all great examples.

To understand what is ui, it's important to know the main UI design elements
Source: StackOverflow
  • Containers/groups, which keep various UI components together. These elements most often come in the form of pop-ups, side bars, and widgets. A great example are newsletter sign up boxes like the one on the image below:
Example of a UI design element
The box has a clickable CTA “sign me up” element, an input box and some text which provides information.

Why is it important to understand the differences among UI design elements?

As you can see from the three groups above, output, input, and helper elements all serve different purposes. That being said, UI designers should also properly distinguish among elements falling within the same group. 

To give you an example, let’s imagine you’re adding a filter on an online grocery store page. You want your search results to display “vegan” products only.

From a UI standpoint, you could be looking at a number of input elements:

  • Radio button list, which lets you tap on the right option
  • List, where you can find the fitting element and click on “vegan”
  • Dropdown, where you scroll and tap on the right product tag (usually, the options will be listed in alphabetical order)
  • Checkbox, where you can choose “vegan”, but potentially also other elements, like “sugar-free” or “fair trade”. 

To know which one to choose for your UI, you need to understand the goals of your users, and make it as simple and convenient for them to complete them!

Speaking of user goals and simplifying interactions, this leads us to the next section:

Best Principles of UI Design

What is UI design? Making life easy for your users. 

That’s the key principle to successful UI design. By making users central to your ongoing design processes, you can increase engagement and retention. It’s about understanding how users think while using data to learn how they act. The result is a more refined product that meets your users’ needs and expectations.

And expectations are high. As users spend tons of time online, they have become more demanding than ever before. They know what a great user interface looks and feels like – even if they don’t realize it or call it ‘UI design’. 

Because what happens when a user struggles to navigate your app or site? 

They X out. It’s uninstalled. 

So, it’s business-critical that you apply the right principles to simplify the user journey. To start, you should:

1. Minimize Actions and Steps Per Screen

Users should be able to get where they need to go in as few clicks or taps as possible. This is especially important when designing a user interface for devices with smaller screens, where space is at a premium and navigational techniques need to be big and bold, and thumb-friendly.

mobile screens

Keep designs focused – both in aesthetic and intent. It should be clear what the page or screen is about, what users need to know, and what they need to do. Take the Amazon checkout page as an example. The focus is on your items and price, your details and delivery options are auto-filled, and all you need to do is hit ‘buy’. 

Time is precious, and with so many firms vying for a user’s attention, you can’t risk ‘losing the crowd’ to competitors without streamlining tasks and actions.

2. Reduce Cognitive Load

Remember the Million Dollar Homepage? It’s an incredible example of cognitive overload. Your eyes flicker across blobs of bright colors and barely legible words. You might be able to pick out a business – a casino, maybe, or a small retailer – but not before another flashy pixel ad else catches your eye, and you’ve forgotten everything that came before it.

Cognitive load is the amount of information taking up bandwidth in your brain. And the goal, when designing an interface, is to cut back on distractions your users don’t need, while making it easy to interact or parse the information they do need. 

A common example is switching the color of a link a user has already clicked on. Instead of having to remember which pages they’ve visited, a user can see at a glance where they’ve been. 

Great UI design means people don’t have to think. The action is intuitive, with users unaware of your savvy behind-the-scenes design skills that enable them to complete their tasks.

3. Ensure Dialogs Should Result in Closure

Think of the last time you bought an item online. There was a clear ‘narrative arc’ in three acts. In the beginning, you’re browsing different products. In the middle, you’ve selected your product and you run through the checkout. In the end, you receive an order confirmation. 

That’s satisfying – our brains get a big kick out of cause and effect because it’s the easiest way to make sense of the world. If I throw this ball against the wall, it will bounce. If R2D2 holds the blueprints, then Luke can destroy the Death Star. If you click ‘buy’, you’re notified that the product is in your basket. 

Apply the ‘three-act structure’ to user actions, adding feedback, like ‘Added’ notifications, at each step.

4. Provide a Clear Next Step

How often have you scrolled to the end of a webpage, only to find it as barren as Arrakis? Your journey has abruptly stopped, leaving you to scroll up, click back, or close the tab. 

Make sure your app or site doesn’t make the same mistake. You’ve helped users get where they wanted, but what happens next?

direction process path way

A core part of UI design is guiding users through a journey. Subtly (or not-so-subtly) telling them where to go next, or what to do. Consider the location and function of call-to-action buttons. Use the data to focus on user intent and placement to maximize engagement. 

Find out more in our guide The Basic Principles of User Interface Design

Top 3 User Interface Design Mistakes and How to Avoid Them

Designing a user interface also comes with a set of risks and potential mistakes. As many of them can be easily avoided, we’ve reached out to several experts, asking them to share their observations. Here are three of the eleven user interface design mistakes we’ve gathered.

1. Putting Creativity over Usability

Josh Wright, CEO of CellPhoneDeal said that frequently businesses try too hard to stand out which has a negative impact on usability. While it’s recommended to design a UI which is memorable, cluttering it with too many images or animations is never a good idea. It can make your app or your website too hard to use. And instead of attracting attention, it might discourage users from using it, and push them into the hands of competitors. Focus on usability instead, and make sure that your UI is not only pleasant to the eye but also intuitive.

2. Relying too Heavily on Design Trends

Deepasha Kakkar, Founder at CRACKITT quite rightly pointed out that companies often fall victim to trends. And as we all know, trends come and go, which is why following them blindly without any initial evaluation is a mistake. Take a look at your performance metrics and see if it’s necessary to make any changes; if it’s not then don’t do it just because everyone else does. If you decide to modify your product based on a newest trend, then first check if there is any data which supports it, otherwise you might waste a lot of time and money.

3. UI Design Style over Substance

Another common obstacle is putting “style over substance”, as told us by Arek Nowakowski, Product Designer at spacelift.io.

Throughout his career, Arek has seen quite a few examples of designers wrapping up a useless (or non-existent) UX into beautiful branding. Such projects are set up for failure, as they only ‘look’, and do not ‘perform’. 

A good analogy is thinking of a car without wheels – the jaw-dropping exterior and interior won’t matter if the vehicle can’t do the very basic thing it’s intended to and take you places.

To tackle this mistake, Arek suggests starting off with the website or app’s flowchart, and validating your hypotheses among potential clients. If your assumptions are proven true, you can then consider including them into your UI. The key here is to be consistent. So, what does design consistency mean? Let’s discuss this next.

Best design consistency practices for UI and UX designers

What is Design Consistency? 

Design consistency is all about keeping visual and functional elements uniform across all platforms. You might even call it ‘design predictability’ – when your user performs X action, Y always occurs, whether on mobile, tablet, or desktop. 

A simple example: your app places a green ‘Yes’ on the right and a red ‘No’ on the left of a dialog box. Users become familiar with this, the action becomes – as every UI designer craves – instinctive. But on certain screens, the placement is flipped. Suddenly, the user is selecting the wrong option. They eye every future choice with suspicion, thumb hovering a second too long over each interaction. 

Inconsistent design shatters the contract between you and your user. 

Best Design Consistency Practices

1. Perform User-Centric UI and UX Design Research

Begin your research by answering two questions. 

  • What does your user want? 
  • What does your user expect? 

Before you can design a solution, you need to get into the user’s mindset. They’ve downloaded your app, clicked on your site. But why? UI and UX is awash with a cocktail of data and empathy.

prototyping paper pencil lo fi

Once you’ve identified the user’s need, focus on the user’s expectation. This means building on design familiarity. Google determined how we search online. Facebook influenced how we connect with friends. Amazon defined how we shop.  

Where’s the homepage button on this page? Top left. No hesitation. Pure online consistency.

2. Define Product Design Patterns

The ‘rule of three’ helps you maintain consistency. You want to keep user actions down to a minimum. That means no more than three taps or clicks from where they are to where they want to be.  You can do this in several ways. 

  • Design hierarchy: direct users’ attention, making the most-used sections stand out. 
  • Branding: your branding is what makes you stand out, from your color palette to your tone of voice. It’s all you, always.
  • Components: the various interactive elements should behave uniformly. A progress bar is always a progress bar.
  • Template: standardize layouts across all platforms, templates are an efficient way to maintain consistency. 

3. Build Consistent Actions

You want users to just know how your product works. Consistent actions create an easy-to-use design flow – once a user knows that X action results in Y, they take that knowledge across your product. They won’t even need to think about it. Draw on existing influences and your own designs when building consistent actions. 

4. Create Consistent Content

Keep your copy consistent. The way you ‘talk’ to users should be maintained across the product, especially when you’re using specific terminology. Consistency creates clarity, maintaining the user’s flow. On the branding side, it prompts users to remember they’re with you, not someone else. 

Content should be presented and behave in a standardized way. When designing these, place user goals to the center. 

5. Maintain Communication

The value of communication just can’t be understated. When users perform an action, they like acknowledgment – a chime, for example, when making a selection. The progress bar is the perfect example. The internet has taught us that patience is a virtue, if it isn’t instant, users want to know what’s going on. 

Users shouldn’t be left wondering whether they’ve ‘done it right’, or if the product’s behaving correctly. Wondering leads to wandering.

team collaboration talk communication

Consistency also depends on internal communication. Everyone on the team is working towards a single vision – and how their roles help to build it. Strengthen your design consistency from ideation to implementation using code-based UI tools like UXPin, which provide governed access to design systems and component libraries. These tools allow cloud collaboration between designers crafting experiences with the same ‘live code’ elements used by your devs, so the product matches your vision. 

Learn more about maintaining a consistent design in our Design Consistency Guide: Best Practices for UI and UX Designers

What does ‘good UI design’ mean according to experts

Now that we’ve covered the principles of UI design and discussed some common mistakes, let’s look at what characterizes good design according to experts:

Designing a User Interface Requires Responsiveness

Technical Lead at ExaWeb Corporation emphasizes the importance of responsiveness, especially after Google made mobile indexing part of their top search ranking factors in 2019. While building an app or a website, it’s absolutely vital to make sure that it adjusts to different screen sizes to guarantee a good user experience irrespective of the device. Responsiveness, however, goes beyond screen size optimization, and also involves speed and performance. For this reason it’s key to abide by Google standards, and make sure that your UI design meets them on every device. 

UI Design Needs to be Empathetic

Greg Findley, Designer at Mantra Design, says one of the most important good UI design traits is empathy towards the users’ needs. While one might think that it’s primarily a UX-related issue, he argues that we can’t forget that it’s the UI users interact with – not the processes behind it.

heart love like good

Greg says that the UI needs to reflect common people behavior, for instance, our ever-shortening attention spans. If the interface or its messaging is too focused on conversion, the user might abandon the site or app, feeling pushed towards the purchase way too early in their journey.

He suggest asking yourself the following:

  • How does the interface make our users feel when they first see it?
  • How do they experience it the second, tenth, and fiftieth time around?
  • How does the UI support maintaining empathy in all the stages of the product life cycle?

In essence, as Greg sums up, how an interface feels and resonates emotionally can make all the difference between a decent and great UI design.

These were just a few of the good UI characteristics designers have told us about – be sure to give our dedicated piece a read for more. 

Good UI Design Should be Minimalistic

Karla Fernandes, UX/UI & Digital Product Designer at Vitamina K  says that the purpose of every product should be to help users resolve a problem or achieve a goal which was identified during the user experience research. A minimalistic UI design will do so by using colors, font, and proportions that not only have visual hierarchy, but also promote user attention and reduce informational overload. This, among others, can be achieved by spacing and a careful selection of images and animations. 

responsive screens

Karla also underlines that people love familiarity. When you use a repetitive pattern or element, you can rest assured that they’ll know how to find their way around. In the end, this positively impacts your product’s usability and reassures its role in peoples’ lives.

For more advice from experts, give our dedicated good UI design piece a read.

Best Practices for Mocking Up User Interfaces Fast

1. Sketch it

Time – we never seem to have enough of it, so you don’t want to waste it digitally working up concepts that may be doomed to fail (or totally unworkable, anyway). Sketching is quicker and cheaper, ideal for creating faster UI mock-ups. Just grab a pen and paper. It may be low-fidelity, it won’t look, feel, or function like the finished product. But it’ll give the team a clear idea of your vision, and how best to approach it. 

2. Mobile-First

Start small – in this case, the small screen. Mobile is where a huge chunk of your audience is, so it makes sense from a business perspective. However, the mobile-first approach brings practical design benefits, too, whether you’re making mock-ups, prototypes, or wireframing your latest brainchild. With tools like Adalo, you can design, build, and publish custom database-driven apps to both iOS and Android platforms with a no-code approach, making the mobile-first workflow seamless and efficient. By creating for mobile-first, you’re including only the most important content (because space is at a premium). You’ll then find it easier to scale up, adding additional content for larger screens, rather than cutting, which usually leads to back-tracking and complicating designs. 

3. Grid Systems

Grid systems remain somewhat controversial, like all the best things in life. But there’s no denying they’ve grown in popularity in recent years, becoming an essential tool for designers who need to build efficient and consistent mock-ups. Grids let you bring order to what might otherwise be chaos. The organized grid system helps you determine the best spacing, sizing, and hierarchy of your content. Horizontal grids are most common, but if you’re concepting typography, you may find it handy to implement a vertical grid.

grid design

Get more tips by reading our article on the 19 Best Practices for Faster UI Mockups and in our ebook on Web UI Design Best Practices.

Responsive Design or Adaptive Design: Which is Best? 

What is Responsive Design?

Responsive design fluidly adapts to whatever screen size the user is on. It uses multiple CSS media queries to determine the display or size of the device and alters the style in response. 

What is Adaptive Design? 

Adaptive design presents a static layout based on breakpoints. So, if your user is on a 760-width screen, they’ll always see the 760 layout. Most adaptive design teams create adaptive designs for six screen sizes:

  • 320
  • 480
  • 760
  • 960
  • 1200
  • 1600

Pros and Cons of Responsive and Adaptive Design

Adaptive designs need more work to start – designers need to design for at least six screen sizes. But responsive design comes with complications, vulnerable to display issues if the proper media queries aren’t used. 

This is most notable when sites deliver the full desktop experience. We’ve all come a cropper of this one. If we’re lucky and the site loads, it slows to a crawl. Deploying media queries can help, but responsive sites are never as quick as one designed specifically for a mobile screen size.

When taking the adaptive path, choose a UI tool like UXPin, which lets you introduce multiple breakpoints to maintain on-screen consistency across devices. You can see how easy this is yourself with a free trial

What’s Better – Adaptive or Responsive Design? 

With all that in mind, what’s the best choice for designers?

Your design choice starts with your users. Answer: Who are your users? What devices do they use? Equipped with this knowledge, it’s easier to create a design that meets their needs. When most of your users are accessing your site on a 960 screen, you know which screen width to prioritize and optimize the content.

Your decision will also be influenced by whether or not you have an existing site. In the design world, responsive has become the go-to choice – adoption rates almost match dedicated mobile sites, with around 1/8 sites running a responsive design. 

But popular doesn’t always mean good. One pretty clever test showed out-of-the-box responsive designs seriously impact your site load times. That means rigorous optimization is an absolute necessity. Adaptive designs require more investment, but will typically be the better choice for any mobile-first operation, since it only loads what the user will see, precisely how the user should see it. Find the right design choice for you in our showdown Responsive Design vs. Adaptive Design: What’s the Best Choice for Designers?

Now, we have a pretty clear idea of using the principles of UI design and responsiveness to efficiently craft brilliant user journeys. So, it’s time for a more granular look at how to perfect your mobile and landing page UI.

Mastering Mobile UI

What is Mobile App Design? 

The mobile UI is everything displayed on the mobile screen. If a user can see it, tap it, swipe it, or do anything else, then it’s part of the mobile user interface.

There are almost 17 billion mobile devices operating worldwide. Over 300 million smartphone users in the US, spending more than $330bn a year. It’s a huge market that can’t be ignored, and in the high-competitive (dare we say, cut-throat?) digital space, it’s vital to make the right impression. 

Mobile design isn’t without its challenges. With smaller screens and touch-based interaction, the principles for designing an interface on mobile diverge from traditional desktop design. 

Tips for Designing a Mobile Interface

1. Present a Clear Vision

Every project should start with a vision. A clear objective communicated to the team and key stakeholders. Be specific, and use visual aids where possible. 

Everyone working on the project should leave that meeting understanding what your vision is and what’s required of them to deliver it. Counter any factor that might influence the end-product at this stage. For example, how will your idea gel with the brand colors, or the development tools you use? 

Kicking off your project this way helps make the design and development process more efficient; the end goal isn’t a shifting interpretation filtered through multiple departments, with more and more features added with every regeneration. 

2. Iterate Your Designs

‘Progressive enhancement’ describes the way you continually refine a design to its perfect point.

Creating a product takes up just about every resource a business can spare (and a few they can’t). Instead, you want to iterate an idea, working it up into a high-fidelity prototype the same way devs progressively develop modules. It’s a lot easier to start small, see what works (and what doesn’t), and build a product that really matches that initial vision. 

UI design software like UXPin’s Merge offers a great way of achieving efficient progressive enhancement. No more endless back-and-forths or redesigning elements every time. By using fully interactive ‘live code’ components, designers can create designs that look, feel, and function exactly the way the final product will. 

3. Stay Uniform

Mobile interfaces need to feature consistent designs. You could even argue that mobile design consistency is more important than it is in desktop design – at least our brains are switched when we’re sitting at a computer. 

Keep buttons, icons, and colors uniform. The placement of key actions should also remain consistent. When we’re scrolling through our phones, half-watching the TV, we don’t want to think about what our thumbs are tapping. It should be instinctive. Find out more about Mobile UI.

Understanding Landing Page UI

How to Create a User-Friendly Landing Page UI

  • Trigger emotions

Your brand colors, tone, and imagery are a core part of your business personality. They’re what makes you you. Whether you’re a start-up or a veteran firm, these should all hold meaning for the user – and they should be reflected on your landing page. 

At the earliest stage of design, determine: 

  • The message to communicate
  • The emotions to convey
  • The personality to present

Your answers will inform the shape of your design. 

Let’s say you offer online meditation services. Your landing page needs calming colors, soothing tones, a lightweight design with plenty of breathing space. 

Don’t dismiss the power of color psychology, either. According to Canva, ‘85% of consumers believe color is the biggest motivator when choosing a particular product, while 92% acknowledge visual appearance as the most persuasive marketing factor overall.’ 

  • Use images 

Images are insanely powerful when you want to attract your users’ attention. We’re drawn to images – it’s part of our DNA. Moving vehicles and human faces are especially effective at catching (and holding) the eye. So effective, in fact, that users will naturally follow the gaze of a person in a photo.  

Use these tricks in your landing page designs to direct a user to look somewhere, or perform an action. However, make sure your image placement doesn’t break the compositional flow of the page.

image6 1
image5
Source: Wordstream
  • Run A/B tests

A/B tests are one of the best ways to gauge the user-friendliness of your landing page. This sees you create two versions of your page, with different call-to-action copy, for example. Half your users will see page A, the other half will see page B. Now, you can see which generates more clicks or sign-ups, and so on. 

Once you have a winner, you can continue creating A/B tests, refining the design as you go until you have an unstoppable landing page. For additional user testing, run your designs through a focus group of other UI designers and average users.

Check out our guide on Landing Page UI.

Choosing Your UI Design Software

Best UI Design Tool Features

1. Image-based or Code-based

When selecting your software, you’re likely to come across a lot of image-based tools. They’re pretty common in the design world because designers can mock-up interfaces fast. It’s the software equivalent of a pad and pencil; great for getting that initial spark of an idea out of your head and onto the screen.

But they can’t go much further than that. You’re dealing with images, not functional elements. They only look awesome, too raw to develop into a tangible product. 

Code-based UI software lets you craft sweet designs just like an image-based tool. But it uses UI components built from the same code used by your developers. Designs retain consistency from start to finish, and by easing the design and development process, deployments are faster.

2. Functional Fidelity

Struggling through handoffs with the devs? Tired of explaining ‘but it needs to look like this…‘? Embarrassed seeing a finished product that’s only more or less like what you envisioned? Then it’s a sign you need to boost the level of functional fidelity in your designs.

Low-fidelity designs only give a sense of appearance. This makes it difficult for developers to translate into a working model – assuming it’s feasible.

High-fidelity designs, like those created in UXPin, look and act like the real thing. By harmonizing the components used by both design and development, everyone’s on the same page. The vision – along with everything else – remains consistent.

3. Working Together

In our connected world, communication and collaboration have never been easier to accomplish. Make sure your UI software isn’t the odd one out. 

Your tool should be geared towards making it simpler than ever to work together, share the latest updates, and chat about projects. Cloud-based design tools bridge the gap within teams and across departments. Emphasizing the collaborative approach, UXPin enables teams to work on the same designs in real-time, access shared libraries, collect feedback, and conduct remote brainstorming sessions. From mock-up to handoff, you’re able to manage the whole design process in a single online tool.

To make an informed choice, read our guide on UI Software Tools.

Top UI and UX Trends in 2022

What does 2022 hold for UX and UI design? See top trends in the user interface design industry.

1. Lottie Animation

The popularity of Lottie Animation continues to rise. One study shows searches for the animation technique rocketing 2300% over the last four years. 

Lottie Animation is an open-source, JSON-based tool that lets you make animations really quickly. But don’t mistake these for mere GIFs. Lotties are smaller, while featuring far better image quality. It also offers greater control over your designs, letting you build and test each one before you display them on your site.

Lottie files UI design

With animation experiencing a resurgence in UI design recently, and businesses keen to irresistibly attract users’ attention, expect Lottie’s user-base to grow. 

2. Code-based tools

Design and development teams don’t always see eye to eye, right? Design wants a product that looks like this, but development knows it won’t work that way… 

Ironing out these issues, especially when working remotely, is tricky since often it’s a case of communication breakdown. No one’s talking in the same language. 

Because of frustrations in the process, teams are shifting to code-based design tools. Unlike image-based software, which can only accurately represent the look of a product, code-based UI tools use live code components. Designers are free to craft interactive, high-fidelity prototypes using elements built with the same code used by your developers. This means prototypes behave just like they would on your site or app, and devs are already familiar with how each element functions. 

3. Voice UI

It’s easy to think of UI and UX in strictly visual terms – that’s where it manifests itself most commonly, after all. But don’t sleep on voice user interface.

Google, Amazon, and Apple have all helped mainstream VUI with their AI-powered smart speakers. Almost every modern smartphone now has voice capabilities. And by 2025, the speech and voice interface market will hit nearly $25 billion.

Designing for an audio audience is a major shift, bringing fresh opportunities (and a few challenges). However, users are increasingly familiar with and comfortable using voice UI. 2022 might be the right time to explore a new approach for interacting with your product. 

Design User Interfaces in UXPin

While designing an interface can be a challenging process, it’s crucial for creating good experiences for your users (and so, your brand’s success). The good news is, this guide has given you all you need to know to begin on your UI design journey!

If you’re looking for a tool that will support your designers and developers in their product development, be sure to check out UXPin

6 Web Form Design Examples and Best Practices

Web Form Design Best Practices

Let’s face it, forms are annoying! But they’re a critical conduit between you and your customers. Web form design has evolved dramatically over the years to enhance the user experience and facilitate faster, more intuitive data capture.

From a technical standpoint, forms are easy. A dollop of HTML, a dash of CSS, a serving of your favorite back-end code, and you’re ready to go. But your users aren’t.

User experience requires more than beautiful visuals with robust code. Web forms must guide users along a path, hint at what’s expected, and deliver on what’s promised. We’re going to explore some web form design best practices with examples from Amazon, Slack, Typeform, UXPin, Wistia, and Stripe.

Key takeaways:

  • There are a couple of rules that help design better forms, such as using step forms, leveraging autocomplete, or descriptive labeling; follow those rules and see how they increase your conversions.
  • We gathered 5 inspiring web forms from top companies to show you how to design a web form for best results.
  • UXPin has a great sign-up form template that will speed up your web form design.

UX designers can design, prototype, and test fully-functioning forms with UXPin. Sign up for a free trial to experience the endless possibilities of code-based design.

Build advanced prototypes

Design better products with States, Variables, Auto Layout and more.



Try UXPin

7 Forms Best Practices

1. Less is More

While collecting as much data as possible enriches user personas, long forms can be overwhelming, resulting in high dropoff rates. Reduce fields and only ask for information necessary to complete a task or action. Avoid using optional form fields that clutter UIs and frustrate users.

If you only need an email and password for onboarding, don’t include redundant optional fields like “first name” and “last name”. Only use required fields to keep user interfaces clean and easy to navigate.

2. Leverage Form Field Types

Text fields, dropdowns, radio buttons, checkboxes, date-pickers, toggles, and other field types have specific use cases and help users complete forms quicker.

3. Use Step Forms

According to cognitive psychologist George A. Miller, “The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information.” If your form has more than seven fields, consider breaking it into manageable chunks with steps of 5 or fewer to minimize cognitive load.

4. Use Geolocation and Defaults

Using tools like geolocation can help complete form fields, like the user’s country for a billing address. If most of your users are US-based, you can set this as the default.

Another strategy is to place your four most used options at the top of a long dropdown. For example, placing the United States, Canada, United Kindom, and Mexico at the top of your counties.

5. Match Keyboard to Input for Mobile

Consider displaying a numeric keyboard for number-only input fields like credit card numbers, phone numbers, CVCs, dates, and others for mobile apps and responsive designs. This small gesture helps users complete number fields without switching keyboards.

6. Autocomplete Whenever Possible

Autocomplete saves users time, especially on mobile devices. For example, country and state/province fields should always have autocomplete.

7. Use Explicit Names and Labels in Forms

Buttons must tell the user what will happen when they click it. Avoid using the generic “Submit Button” across your website or application. Even subtle differences like “Buy” or “Pay” could be confusing. Buy would be best for “add to cart,” while Pay indicates the final payment.

Labels must be short while being as specific and descriptive as possible. For example, “Name” is ambiguous if you only need a first name.

6 Inspiring Web Form Designs

Example 1: Stripe Payment Form

Stripe are arguably the masters of credit card form design. Before Stripe, credit card forms were uninspiring, slow, and often had limited card options. Now, most eCommerce stores, including Shopify, use Stripe to process credit card payments.

One of the keys to Stripe’s success was its trendy, intuitive web form design that turned payments into an immersive experience. You can check out several Stripe form examples with links to view the source code on GitHub.

Our key takeaways from Stripe’s credit card forms:

  • Firstly, Stripe recognizes the device you’re using to offer express checkout with GPay or Apple Pay. These options not only serve users but increase conversion rates with fewer dropoffs.
  • Placeholders provide implicit instructions for how users must complete the form, thus reducing cognitive load.
  • The processor’s logo appears as you enter your credit card details, so the user doesn’t have to select it manually, eliminating a form field.
  • Lastly, the confirmation button tells the user exactly what will happen when they click (Pay) and the cost ($25) to avoid surprises.

Example 2: UXPin Sign-Up Form Example

UXPin has several interactive UI patterns and app examples, one of which is a mobile app sign-up form. To create an account, the user only has to enter their email address and password. You can preview the prototype here.

Key takeaways from the UXPin Sign-Up Form:

  • The minimalist UI allows users to create an account or log in. Both CTAs are bright green to grab the user’s attention.
  • The form uses color and helpful messaging for error handling so users know which fields they must fix.

If you would like to play around with this form or use it for your next design, sign up for a free trial, download the template and upload it to a new project in UXPin.

Example 3: Wistia Corporate Account Registration Form

Offering social media login options helps streamline onboarding, particularly for corporate registration forms, which typically require more than just a username and password.

Wistia allows users to sign up with Google or Microsoft, both applicable corporate social media accounts. It’s essential to use relevant social media logins. For example, Google or Microsoft wouldn’t be the best choices for a dating application–Facebook, Instagram, or Twitter would be better options.

Key takeaways from the Wistia Sign-Up Form:

  • Excellent use of whitespace draws attention to the sign-up form and task at hand. This layout also translates to mobile for a consistent experience across multiple screen sizes.
  • Wistia uses the password placeholder to prevent errors by instructing users about the minimum character count.

Example 4: Amazon’s Step Form

Step forms are excellent for capturing large amounts of data. They break the process into manageable steps while providing context for the user in the journey.

Amazon is constantly updating its checkout forms, so this one might be a little outdated, but the concept is still relevant. The form uses progress indicators to show shoppers the steps to complete checkout. Progress indicators help manage expectations and keep users engaged in the process–as recommended in Interaction Design Best Practices.

image08

Key takeaways from Amazon’s step form:

  • Step forms are excellent for capturing large amounts of data or dynamic outcomes–like different forms for international and domestic shipping.
  • More steps don’t mean more fields! Entering large amounts of data is taxing for users, even with stepped forms. Eliminate unnecessary fields and form elements to minimize the user’s cognitive load.
  • Consider using a steps left pattern or completeness meter to show users how long they have to complete the task.

Example 5: Typeform’s Step Form

Typeform is a unique example in that they use multiple steps for every form with a single action per step. The smooth microinteractions and beautiful UI makes form filling enjoyable and exciting.

This style is excellent for dynamic website forms where one step can influence the next. For example, an event registration that changes depending on the venue or if you plan to attend the afterparty.

Key takeaways from Typeform’s step form:

  • A single action or input per step allows users to focus on one thing at a time to complete online forms quicker.
  • Typeform enables users to use the enter key to move to the next step, so they can keep their hands on the keyboard without reaching for the mouse. This strategy is more intuitive than using the tab or arrow keys.
  • Forward and backward buttons give users control to see what they still need to complete or go back to make changes.
  • Typeform shows estimated form completion times at the start, so users know what they’re committing to before starting.

Example 6: Slack’s Contact/Support Form Integration

Companies are always looking to reduce tickets by diverting users to FAQs and other resources. Slack provides users with several topics to start a conversation. The next step displays relevant FAQs with links to documentation.

Most importantly, Slack still allows users to contact support with a message box and file upload. Users can send a message via email or start a live chat.

Key takeaways from Slack’s contact form:

  • If you handle high volumes of customer support tickets, provide links to FAQs to help users before they submit a question.
  • Avoid using FAQs as a barrier to contacting your support team. Slack uses a two-step process with a message input to share feedback–showing that they’re there to serve their customers.

Create Code-Like Form Prototypes in UXPin

UXPin’s code-based design tool allows you to build fully functioning prototypes. Design web forms that capture data and use Variables to create personalized experiences during usability testing. Behind the scenes, tools like DreamFactory provide the backend infrastructure for managing data access and API integrations that power these forms at scale.

With Conditional Interactions, you can create dynamic experiences similar to that of Typeform–something you cannot achieve using an image-based design tool.

Expressions allow you to take your forms to the next level with password validation, check email formatting, simulate credit card capture, or even update computational components like shopping carts.

Get accurate results and meaningful feedback from usability participants and stakeholders to improve and iterate form designs.

Experience form design with UXPin today:

  1. Sign up for a free trial
  2. Download our free Sign-Up Form Template
  3. Import the template to a new project, and you’re ready to go!

Design System – Principles of Success

Design system Principles of Success

On the surface, building a design system is a matter of designing a collection of elements, components, text styles, and colors. But the truth is it’s a more complex procedure. Building, managing, and scaling a design system requires principles and direction.

This article was inspired by the webinar about Design System with Carola Cassaro, which outlined the process of building a design system, including the principles that guide teams and decision-making. We have another webinar coming up in May! We will talk about building and scaling enterprise design systems with Amber Jabeen. Join the webinar for free.

In Defending Your Design System, we feature our revolutionary code-based design technology, UXPin Merge. Merge allows you to create a single source of truth between design and development by syncing code components from a repository to UXPin’s editor. Sign up for a free trial and see Merge in action with our MUI integration

What are Design System Principles?

Principles define the why and purpose of building your organization’s design system. These principles guide decision-making and explain how the design system’s creators want team members to use the system. 

A design system’s principles also streamline onboarding by helping new team members understand the company’s vision and priorities. 

“Design principles are the guiding light for any software application. They define and communicate the key characteristics of the product to a wide variety of stakeholders including clients, colleagues, and team members. Design principles articulate the fundamental goals that all decisions can be measured against and thereby keep the pieces of a project moving toward an integrated whole.” – Luke Wroblewski, Product Director at Google

Carola Cassaro, Director of Product Management at Work & Co, and part of the team responsible for building and launching IKEA’s design system Skapa, broadly outlines design system principles as:

  • Single source of truth: Centralized resource that’s easy to access and relevant to its users
  • Inclusive & collaborative: Speaks to a wide audience, uses shared terminology, and fosters the exchange of ideas
  • Modular & reusable: Solves the majority (80%) of UX problems so that teams have more time to innovate
  • Living & breathing: Evaluated and evolved over time

Why Do You Need Design System Principles?

Building a design system is like building any other product. Without a set of principles guiding your decisions, you end up with the same problems your design system is supposed to solve, like design drift, conflicting opinions, and team friction.

With clearly defined principles, team members work together to solve design problems with shared purpose and consistency.

A Guide to Establishing Principles for a Design System

design system components

Back in 2015, UXPin used a five-step process to define its design system’s principles. The process is still relevant today.

Step 1 – Find product analogies

To avoid copying direct competitors, look for inspiration from successful products and brands outside your product category. The goal is to identify core values and qualities you want your product to have. What do you want people to experience when using your product?

For example, a red Ferrari might represent wealth, speed, exclusivity, status, and innovation. List these analogies and your reasons for choosing each one.

Step 2 – Find design principles in analogous products

Go through your list of product analogies and identify the qualities that make these products successful. Also, why do you want your product to have these qualities?

For example, a red Ferrari represents status. How does it do that for people? A simplistic answer would be its cost. But there’s so much more that gives a Ferrari status, like craftsmanship, quality parts, attention to detail, rarity, personalization, Formula 1, and the brand’s legacy.

Step 3 – Make the list real with existing user research

Connect the reasons for your choices with your product’s user research. Do user pain points contradict what you want your product to be?

For example, you want your product to be as simple and intuitive as an iPad, but users complain that they battle to use features or complete tasks.

Step 4 – Build value statements

Sort your analogies and reasons, prioritizing those most frequently mentioned by users to make value statements. 

We want our product to be like [complete with your product analogy] because it [complete with the reason] and it’s important to [our users/me/us].

Using one of Marcin’s examples: “We want our product to be like a white Porsche 911 from the 80s because it brings the feeling of timeless quality and it’s important to us.”

Step 5 – Abstract your principles

Now remove the product references from your value statements to make them applicable to your design system.

For example, “we want our product to bring a feeling of timeless quality.”

From this five-step process, UXPin’s team developed seven design principles:

1. No distractions. Every redundant piece of the interface (lines, buttons, shadows, animations) is a source of distraction. As such, it should be eliminated to empower users’ creativity with a well-architected and inspiring design tool.

2. Design-centric. Users’ designs should lie at the center of UXPin. Our interface should be unobtrusive to the point of transparency.

3. Adaptive interface. UXPin’s interface should act according to the context of use. All the ‘inactive’ features should remain completely hidden until the user can use them (no inactive buttons and links!)

4. Space. UXPin’s interface should create a peaceful atmosphere, triggering users’ creativity. This ambiance can be shaped by leaving a lot of space around every piece of interface. The cluttered interface is the source of stress that produces cortisol and adrenaline; both block our creative powers.

5. Inspiration. UXPin design should inspire and, as such, can’t be a derivative of design of other SaaS apps. We should strive for an original aesthetic inspired by the best products ever created (some of the sources of our inspiration: Fountain Pen Pilot Vanishing Point Matte Black, speakers Harman Kardon Sound Stick, record player Pro-ject, speakers DALI Zensor).

6. Interactive Consistency. Interface components, icons, and fonts should be consistent to create a predictable experience.

7. Predictable Architecture. UXPin’s architecture must be predictable and natural. Features should be placed in the right context for new users to discover easily. Example of predictable architecture: canvas settings should be placed next to the canvas.

Over the years, UXPin has found these principles prevent:

  • Endless subjective discussion
  • Unclear design requirements
  • Inconsistency at the most fundamental level

Finding Inspiration and Examples From Adele

design system library components

Adele is a UXPin initiative that features an A-Z Design Systems Repository. Inspired by the 70’s design system pioneer Adele Goldberg, Adele by UXPin aims to encourage people to develop principle-driven design systems using inspiration from the world’s leading organizations.

The directory breaks each design system down into 31 categories, including components, framework, brand guidelines/principles, color palette, typography, grid, accessibility, documentation, and more.

Adele also provides links to each of these categories (where applicable), so you can quickly find references and inspiration. For the purposes of this article, we’ll outline the principles from four established design systems.

Estonia – Brand Estonia

As a country that’s marketing itself as “the world’s most digitally advanced society” and strategies to attract startups and remote workers like e-Residency and its Digital Nomad Visa, it’s no surprise that Estonia has one of the world’s best governmental design systems.

Brand Estonia comprises of three core messages or principles that designers must use to introduce Estonia:

  • Digital society: Estonia is the first country to function as a digital service. Our citizens and e-residents can get things done fast and efficiently.
  • Independent minds: Estonia’s biggest asset is our people.
  • Clean environment: Estonia has a lot of untouched nature and a low population density. This is very rare in today’s world. We know how to care for our environment and we are proud of it.

Estonia also has 11 primary industries or products, each with its principles that align with the country’s three core messages.

Coupled with messaging are Brand Estonia’s copy and design guidelines which define the country’s character in three words: Nordic, Surprising, and Smart. The visual language must always be:

  • Clean: as in uncluttered with unnecessary information and confusing typography
  • Simple: because we like to leave enough space around text and images – making them more legible and emphasizing only the essential

Brand Estonia is a wonderful example of how designers can use the nation’s values (or company culture) to define its design system’s principles succinctly.

Atlassian Design System

Atlassian’s design language resource provides teams with guidelines “to create simple, intuitive and beautiful experiences.”

The design system team has separated the guidelines into six categories:

  • Brand: reflects who we are and how we want our users to feel when they use our products
  • Foundations: the visual elements needed to create engaging layouts and end-to-end user experiences
  • Content: covers our voice and tone, and the mechanics of our grammar, and style
  • Components: each component meets a specific interaction or UI need, and has been specifically created to work together to create patterns and intuitive user experiences
  • Patterns: best-practice solutions help users achieve their goals and help ensure consistency across experiences
  • Resources: a collection of tools, kits, plugins, and guides to help simplify the creation process for our users

Within each category are several subcategories where Atlassian uses a sentence or two to reinforce the company’s principles. For example, under Brand, they have Mission: Our mission is to unleash the potential in every team.

Atlassian demonstrates that with clear design system principles, you can develop a complex suite of products with remarkable consistency and seamless integration.

Salesforce – Lightning Design System

Design system professionals often point to Lightning as an example of simplistic cohesion and consistency. Lightning’s guidelines are as comprehensive as the design system itself, with documentation for every component and layout.

Salesforce outlines four code principles behind its design system:

  • Clarity: Eliminate ambiguity. Enable people to see, understand, and act with confidence
  • Efficiency: Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster
  • Consistency: Create familiarity and strengthen intuition by applying the same solution to the same problem
  • Beauty: Demonstrate respect for people’s time and attention through thoughtful and elegant craftsmanship

Salesforce’s goal for Lightning is to create a design system that allows team members to focus on their core tasks and responsibilities:

“The Salesforce Lightning Design System includes the resources to create user interfaces consistent with the Salesforce Lightning principles, design language, and best practices. Rather than focusing on pixels, developers can focus on application logic, while designers can focus on user experience, interactions, and flows.”

If you’re having trouble defining your design system’s principles, start by identifying a high-level goal and working your way down from there.

Stack Overflow – Stacks

Stack Overflow divides Stacks’ guidelines into four categories: Product, Email, Content, and Brand. Under Brand is where the company outlines its design system’s principles.

Stacks emphasizes four brand principles that “represent the approach and opinion all things Stack Overflow should have.”

  • Focused: Designs should focus the person on what’s important at hand. Designs should focus on the central goal, pushing distractions and interruptions to the side until the stated goal is completed.
  • Welcoming: Our designs shouldn’t feel “members only,” but inviting and approachable. Designs should be intentional and intuitive, not be some secret codex for users to decipher. While the subjects developers talk about may seem impersonal, our design approach shouldn’t be.
  • Purposeful: Everything in its right place. Our designs might be packed with information, but everything should be purposeful. Don’t add extraneous data or ornamentation, as it might distract people from the central goal at hand.
  • Five percent fun: We’re quirky, not corny. We enjoy the long joke. Our humor is dry and pops up in unexpected, but appropriate, places. We’re “business in front, party in the back.”

Stack Overflow also provides its teams with guidelines for copywriting and visuals. The design system team does a fantastic job of using simple language to describe the company’s principles, including images and graphics to clarify messaging.

UXPin Merge – The Ultimate Design System Tool

uxpin merge component responsive 1

Building a design system is one thing. Managing and scaling it takes governance and proper tools. UXPin Merge lets you sync your design system from a repository to the design editor so designers can build fully functioning prototypes using code components. This approach ensures that platforms that provide governed access to enterprise data can integrate seamlessly with design systems through well-defined APIs.

This single source of truth means all teams, including product, design, and development, use exactly the same design system components to build products. When engineers update the repository, UXPin automatically syncs the changes and notifies all teams.

Build, manage, and scale your design system with the world’s most advanced design system technology. Sign up for a free trial to experience UXPin and Merge with React components from MUI.