Considering UX Services for your software? Sign up for our series ✉️

The UX Process: A Practical Explanation

July 30, 2024
Ceara Crawshaw

Knowing that the goal of UX is designing with humans in mind and that the expected results are more usable and more pleasant products and services – the remaining gap to fill is how to get there. While specifics differ from one designer or one organization to another, UX methods tend to follow similar broad strokes. The design process uncovers many opportunities for businesses, whether that’s cost reduction or seizing new opportunities (we created an article to help calculate the ROI of UX research and design, if you’re curious to find out more).

 The UX design process

Phase 1: Discovery

An important first phase in any project, design or otherwise. In UX, discovery involves doing as much initial research as possible to understand what we’re looking at. Understanding the context of a problem is key to understanding the problem itself and its potential solutions. The intensity of the discovery phase corresponds to the scope of the project and nature of the business. Often on smaller teams, discovery can be expedited or spread more naturally throughout the design process.

Here’s a few research activities UX designers often perform during this phase:

Context mapping 

This is a term we made up at Pencil & Paper - it’s an expedited onboarding process where we facilitate contextual understanding of the tech, business, data and user context.

Main benefit: gain a holistic understanding of the project, create collaborative relationships and access necessary documentation and artifacts for study.

P&P’s own unique onboarding process involves context mapping, a strategy designed to expedite the knowledge transfer of complex enterprise platforms, data structures and user bases.

User interviews

This process happens throughout the process but often kicks off in the beginning. This is a key part of the iteration cycle, where user input informs direction. Interviewing can be a very efficient method to derive huge insights. In B2B SaaS products, we often focus our interviewing a lot on mapping existing workflows, workarounds and painpoints. 

Main benefit: this insider perspective unlocks new understanding, smashes assumptions and gives users the opportunity to pipe in their thoughts.  

This is a user journey we mapped after a series of interviews with doctors for a medtech project we did. Not the sections on the bottom - this not only maps “what is” but naturally brings up “what could be” - this kind of output from research. 

Stakeholder interviews

Put simply, stakeholder interviews are just having a conversation with key people involved in making the project a reality. In organizations where information is scattered or it’s important for specific people to be involved, stakeholder interviews become more and more important in order to secure alignment. At P&P, we focus on deriving subject matter from specific subject matter experts (SMEs) during our context mapping process, so we treat stakeholder interviews as a different thing.

Main benefit: these interviews help us get more information about the challenge at hand and understand what it takes to make the project successful.

Contextual research

This is one of the most fun and fascinating methods of research out there. In short, it’s observing people in their natural habitat to understand how they do things.

Main benefit: looking at how people do things in their natural environment can help us identify things that users are not aware of because it’s so normal for them. You can observe things that people would never describe to you. 

A lot of times, the equivalent of this comes with screen sharing their workflow in software, but every once and a while it’s hyper-relevant to test irl. Example situations where this is important: a science lab, a manufacturing factory floor, a retail environment etc. 

Market research 

Examining direct or indirect competitors and the industry at large to suss out competitive design advantages. This can be a little difficult for B2B SaaS products, as many require meetings with sales people for a demo of the product.

Main benefit: finding weaknesses of competitors can give us ideas for new concepts. We can also find places where we don’t need to reinvent the wheel.

Surveys & Quantitative Analysis

Taking in information at scale can be very useful for analyzing and determining where to focus the UX effort. 

Main benefit: this can help support places to dig into deeper with design and research efforts. Analyzing these numbers often can populate well-informed and interesting research questions.

Phase 2: Definition

This is where UX designers think about what they’ve seen or heard during the discovery phase and begin putting things together into insights that will inform what they design. This is where the ambiguity between phases begins. There are parts of each of these phases that overlap with one another. 

Mapping & Diagramming 

As part of the context mapping process, we take in a lot of information. At this point we draw out the logic and groom rough notes to convey our understanding of the logic of the software at hand. We might draw flowcharts, user flows etc to begin. However, as we start the design phase and begin imagining the future, we’ll use the same types of diagrams, just in the future-facing context.

Main benefit: creates alignment of the team and a shared understanding of the “as is” scenario.

This example outlines a fun task flow we created which shows the movement of a user through a path.

User personas 

These are narratives that are created to describe users of the software you’re working on - the exact format isn’t important, just that it illustrates interesting and relevant information to the team.

Main benefit: this can create understanding and challenge incorrect assumptions about users and can get the team focusing on specific personas in the software. It’s a step towards more user-centricity for many teams.

This example shows a senior analyst working on a clinical report product.

Scope and problem definition

Zeroing in on the precise problem to solve is key to making sure you spend your UX dollars wisely, and get the best ROI possible. This is where we formulate a problem statement based on the information at hand. 

Main benefit: this focuses the team not on “what can be built” but “what users need us to build” which is a focus that many companies need. This is hyper-relevant especially now that we grapple with design user-centred AI features. 

Phase 3: Design

This is the stage most people get excited about; when ideas begin to materialize and it starts to feel like there may actually be a light at the end of the tunnel. An important principle in UX design is testing and validating ideas. Checking in with your users at multiple points throughout the design phase helps confirm that you’ve made sound design decisions and highlights how you can improve and refine your design over many iterations.

Wireframing 

Creating wireframes or “low fidelity” sketches of screens and interaction flows is key to the design process, this is a super fast and cheap way to start aligning around your ideas and exploring possibilities.

Main benefit: cheap and collaborative method to explore ideas, which not only designers can do.

Prototyping

This is where the interface is able to be interacted with. Prototyping is making our static wireframes come to life through clickable prototyping (in Figma and other design products), or with code. 

Main benefit: you can test out ideas in more depth and “feel” the flow and interactivity. 

Usability Testing

Using either prototypes or live code, you can run through tasks and flows with users and observe their perceptions, roadblocks and usability issues (points of confusion).

Main benefit: introduces real feedback which informs direction as well as “quick fixes”.

Phase 4: development implementing collaboratively with developers

Though we involve developers throughout the entire design process, this is when we work together to make the thing come alive!

UX documentation

This is the visual specs, interaction behaviour and system logic that applies to the design work, it’s packaging up the deliverables for software developers to build. Other users of documentation might be the product team, technical writers, quality assurance analysts and potentially back-end devs and data people. 

Main benefit: clarity of information, ease of collaboration and reduction of “mis-implementations” of designs. 

These are a few UX documentation examples from UX Documentation Guide which illustrates the breadth and depth your UX documentation should take.

Wrap up

Once the entire user experience process has been completed, you often loop back to assess a feature or flow over time and determine if more UX love, innovation or general richness needs to be added. This process is happening in shorter bursts and longer cycles depending on the scope of problem you’re trying to solve and how much design exploration they require. There’s a big difference between developing a whole new paradigm of data analysis and fixing a bad user management screen for example. 

If you’re itching for your team to come to appreciate the design process and how designers think, consider taking our Intro to UX Masterclass!

Great data-rich UX minus the mess

Our secret methodology for features that hinge on data.

Amazing design for data-rich features relies on:
Clarifying the problem space

  • Unveiling the mystery of the data
  • Establishing great collaborations that will lead to better data quality
  • Creating realistic designs that fully consider the data structure, limitations and capacities
  • Solidifying rationale through a process of understanding

Our Data Mapping Workshop is a tried and tested approach to understanding the data deeply, so you can design better (and look like a total pro in the process).

Data Mapping Workshop

$499 USD
Learn More

Download our Table UX Audit Checklist

Do a mini UX audit on your table views & find your trouble spots with this free guide.

Available in a printable version (pdf).

Please fill in the form below and it will be in your inbox shortly after.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
letters

Want to dig deeper on flow diagrams?

Be the first to know about our upcoming release!

If you found this intro content useful and find yourself needing to express yourself more efficiently on your software team, this training is for you. Our new flowchart training includes real-life enterprise stories and examples for using flowcharts for UX. You’ll get tips on how to make your diagramming efforts successful, how to derive info for the flow charts, and how to get others to use and participate in the diagramming process.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Contact Us

Intro to UX for Teams

A fun, high-impact injection that levels up your entire team and gets UX alignment without all the fluff. We cover everything from the basics of UX to real-life, enterprise examples that you might just sound a little familiar.

For up to 20 team members
7 Videos
55 min
$1000 USD

Explore our UX/UI Services

Curious about the possibility of working with the P&P crew on your enterprise software project? Check out our services.

Our services

Join our newsletter

Bringing enterprise-grade UX resources into the world to help you think better and have more interesting conversations with your crew!

Newsletter sign up

Data Tables Checklist

This free checklist lets you double check your data tables for their UX quality and assess various aspects which make or break the data table experience for your users.

PDF
Free

Explore our UX/UI Services

Curious about the possibility of working with the P&P crew on your enterprise software project? Check out our services.

Our services

Join our newsletter

Bringing enterprise-grade UX resources into the world to help you think better and have more interesting conversations with your crew!

Newsletter sign up