A simple guide to the design process: kick-start your next project in 2026

Creating products, services, or experiences that people genuinely want is harder than it looks. Even strong ideas can miss the mark when teams skip research, overlook user needs, or move too quickly from concept to execution.

The design process helps teams reduce that risk. It gives you a structured way to define the problem, research your audience, explore solutions, test ideas, and improve the final product before launch.

In this guide, we’ll walk through the seven steps of the design process, explain how the process differs across industries, and share practical ways to keep users at the center of each decision. We’ll also show how monday.com’s AI Work Platform can help teams manage research, ideas, feedback, approvals, and launch work in one connected workspace.

Get started with monday.com

Key takeaways

• The design process helps teams move from problem definition to research, ideation, prototyping, testing, and launch
• A strong design process keeps user needs at the center instead of relying only on internal assumptions
• Research, prototyping, and testing help teams reduce risk before investing heavily in a new product, service, or experience
• Design processes vary by industry, but most rely on clear requirements, feedback loops, iteration, and cross-functional collaboration
• monday.com’s AI Work Platform helps teams manage design workflows with boards, dashboards, automations, integrations, workdocs, and AI-powered capabilities

What is the design process?

The design process is a framework that helps you break down large projects into smaller, easier-to-handle stages.

It’s prominent in engineering, architecture, and manufacturing because it helps companies deliver finished solutions that customers want and need.

At a glance, it looks something like this:

(Image Source)

To do this well, teams gather feedback from potential users or customers at multiple stages, including before they create a prototype or invest significant time and money into a project.

What are the seven steps in the design process?

The number of steps technically depends on the industry and overall method, but we like 7.

When divided into 7 steps, the design process ranges from identifying the problem the design or product will solve to research, planning, prototyping, and more.

In sequential order, they are…

1. Identifying the problem
2. Researching it in-depth
3. Ideating possible solutions
4. Evaluating and selecting a promising solution
5. Creating a prototype
6. Testing and troubleshooting
7. Making improvements to and releasing the final product

Let’s take a closer look at these steps and how you can put the design process into practice for your own projects.

1. Identify the problem you want to solve

Whether you found a pattern in negative customer feedback or you have some R&D budget left to spend, the approach stays the same.

You and your project or product team need to figure out:

• What problem do you want to solve?
• Who has this problem?
• Can the solution help everyone equally?
• What are the requirements for this project?
• What are our limitations — budget and other constraints?
• What is our ultimate goal?

Even if you think you have a good idea, focus on the requirements and your limitations. A lot of new projects fail before they even start.

Poor requirements gathering, weak upfront planning, and unclear vision are common reasons projects struggle before they ever reach execution.

(Image source)

Don’t neglect the upfront legwork.

2. Research the problem in-depth

At this stage, you’ll figure out the market state, whether any competing products exist or are on their way, and what user needs competitors neglect.

Again, a few simple questions can help you get to the bottom of things.

• Do current solutions exist that try to solve the problem?
• Are these failing to meet customer needs in any way?
• Do these solutions offer niche-specific versions?
• How much are customers spending on similar products?
• Can you use existing technologies, open-source or otherwise, to solve the problem?

If you’re trying to solve problems for an existing product or service, starting from scratch isn’t always best. You may find that developing an integration or partnering with another company is the best solution.

Don’t enter an established market without a clear differentiator. If your solution is slower, harder to use, or less valuable than what already exists, customers will have little reason to switch.

3. Ideate possible solutions

Finally, it’s time to get down to business and start solving the problem.

Start by using “how might we” questions to create a list of ideas. You can also add more detail if you want.

• How might we achieve X?
• What is the scope and timeframe for developing the solution?

You can brainstorm together, or ask each person to write down ideas separately before meeting to compare, combine, and refine them. Starting individually can help reduce groupthink and give quieter team members more room to contribute.

But a list of 50+ unsorted ideas isn’t a good starting point for in-depth evaluation. So you should identify the ones with the most potential, and shortlist 10 or so creative ideas to explore further.

At this stage, there are 2 potential traps that any project team must avoid. Some companies stick to “realistic” ideas, often aiming too low in the process.

Others may aim too high, focusing only on the most ambitious or innovative idea without considering feasibility.

Luckily, there’s a helpful design thinking process that can help teams get the best of both worlds and routinely select the best ideas. It’s called the four categories method, where you group the strongest ideas into four categories.

(Image Source)

• The most rational ideas are the easiest to implement and most closely aligned with existing processes
• The most delightful ideas have the greatest potential to impress or support customers
• The darling idea is each group member’s favorite idea
• The long shot is a challenging idea with strong upside if it works

Everyone on your project team should choose one or two ideas for each category. Depending on the group size, voting by colored post-its or holding an online survey may be necessary.

By using surveys and forms, you can easily distribute your questions and collect as many participants and data points as possible.

By the end of this process, you should have four to eight good ideas to take to the next stage.

4. Evaluate and select a promising solution

Okay, so you have your shortlist of ideas. Now, it’s time to put them to the test.

• Does it fit the necessary time frame?
• Can you complete it within budget restraints?
• Does it truly align with your target customer’s needs?
• Is the product in itself a differentiator for your company?

Even if you can’t meet in person, don’t just let one person decide. Distributed or remote teams can use a Kanban board to prioritize and select ideas.

Depending on the company’s size, you may have an approval committee or a senior executive who gives the go-ahead for large projects.

You could have them give a quick yes-or-no on the initial shortlist before exploring the viability of each option over a few days.

If you end up with multiple viable options, hold a vote on which to proceed with first. Splitting up your team’s focus too much won’t lead to good results.

5. Create your prototype

Spend as little time as possible validating your idea with a prototype, without rushing the process.

Remember that this isn’t what you’re bringing to market. It doesn’t need all the bells and whistles and a complete branding kit.

• For physical products, use cheap materials and reusable segments.
• Rely on lo-fi prototypes like storyboards or partially developed products, where you manually fulfill the process.

Don’t underestimate the value of lo-fi prototypes. Even a simple manual version of an idea can help teams validate whether users actually want the experience before investing in a full build.

6. Test and troubleshoot

AI-powered tools can also help teams summarize testing notes, group common feedback themes, and surface repeated usability issues, making it easier to decide what to improve next.

If you only have a lo-fi prototype to work with, don’t worry. As long as you deliver the experience your customer expects, you can get meaningful feedback.

For example, if your product is an AI-powered curator for cheap airline tickets based on someone’s bucket list, you can start with a landing page and have someone manually curate tickets using search engines.

After the user tests, make sure you interview your customers and ask them relevant questions.

• Did the prototype solve your problem?
• Was there anything unexpected about the experience?
• Did you struggle to complete any tasks?
• What was your first impression of the prototype?

You should also test some users without direct instructions from staff to see how intuitive it is.

If you’re developing something to replace an existing digital product or feature, you should set up an A/B test.

monday.com’s A/B testing template can help with that…

Get started with monday.com

An A/B test splits your users or traffic into two audiences. The first continues to see the old design or product, while the second sees the new one. Based on their behavior and a few predetermined metrics, such as adoption, conversion, time on page, etc., you gain valuable insights and feedback from a much wider audience before making your final decision.

7. Make improvements to and release the final product

If your prototype was a huge hit, all that’s left now is to touch up your product and release it to the public.

But first, your team needs to answer the following questions.

• Did users report issues completing any specific tasks with your products?
• Did they immediately understand how to use it?

If there were significant issues, go back to the prototyping stage. If there weren’t, make adjustments for the smaller issues and move straight to release.

Is there a difference in the design process in different industries?

While the term “design process” refers to a similar approach across the board, the number of steps and most important considerations vary from industry to industry.

Let’s break those differences down…

Engineering design process

The engineering design process emphasizes early-stage research and robust prototyping and testing before tackling the final product.

Prototyping can often mean running virtual tests using design and modeling software based on the materials, building standards, and requirements.

But that doesn’t make the process any easier. You need to consider the elements and find the right materials to match physical requirements with the desired design. You must also factor in a complex supply chain when evaluating project scope, costs, and viability.

For large-scale construction projects, the modern supply chain is exceedingly complicated. It involves renting equipment, using a mix of complete segments plus raw materials like gravel, and tons of sub-contractors.

(Image Source)

So it makes sense that you’d want to have everything lined up before you go ahead with a design.

Manufacturing or physical product design process

If you’re trying to develop a brand new solution to a complex problem with a lot of varying and hard-to-quantify factors, digital prototyping and testing may not be enough.

The prototyping process can take a long time, and will often send you straight back to the drawing board.

For example, the lack of manual green chile pickers in New Mexico led agricultural researchers to develop a harvesting machine. Early prototypes ripped out the entire plant or left many of the chiles behind, making the solution impractical for real-world use.

(Image Source)

Only after decades of prototypes did they figure out that the solution wasn’t in developing a better machine but a more robust, well-rooted plant that could better resist the more hard-handed harvesters. New seeds were the answer, not hardware.

If it is a consumer product, you also have to comply with FDA regulations and undergo testing before launching it. That leads to drawn-out research, prototyping, and testing phases.

Of course, not all products are physical.

Read our interview with Parchment for more insight into the digital product design process. 

Graphic or UX design process

A UX or graphic design process can be much leaner. There’s no physical product, supply chain, or limited regulations involved.

A designer also starts with user research and identifying problems. But they can quickly develop partially functional prototypes and get real users to test them.

The effort required to get actionable data is also much lower, and you can typically access it in real time. That shortens the distance between steps in the cycle, so some agencies include user testing as part of their idea development process.

The best way to manage a design project is to put your customers front and center.

The importance of user-centric thinking throughout the design process

You won’t get a perfect understanding of your target customers during the initial stages of research.

That’s why it’s essential to keep going back to and maintain an ongoing relationship with potential customers.

(Image Source)

For example, in software or game development, beta testing is the perfect example of this. You can get feedback from users and even the broader marketplace in real time.

If everyone hates the beta test, you may need to go back to the drawing board and ask those beta users what they want instead.

If they think it’s alright, but it “misses something,” then you need to refine and retest your prototype until they’re satisfied.

Keep customer feedback at the center of design decisions

Most companies understand the value of customer empathy in theory, but internal decision-making can still become disconnected from what users actually need.

(Image Source)

Strong design teams make sure customer insights influence decisions at every level, from early research to final approval.

It’s OK to trust the instinct and experience of senior creative staff for some things. But they shouldn’t be able to veto design decisions unilaterally when user research indicates otherwise.

Five stages of the user-centered design process

Another way to think of the design process is to condense it into five distinct phases, which some like to call the user-centered design process.

• Empathize: Gain a deeper understanding of users and their needs through research, observation, and direct engagement
• Define: Synthesize findings from the empathize stage and clearly articulate the core user problem
• Ideate: Generate a wide range of possible solutions and explore different ways to solve the defined problem
• Prototype: Create scaled-down or low-cost versions of the solution to test and gather feedback
• Test: Assess prototypes with real users, then refine the solution based on what you learn

Five common design process mistakes to avoid

Mistake 1: not understanding users’ needs

The most common pitfall creative teams face is jumping straight to solutions without fully understanding their users’ needs. It’s crucial to gain real insights into your target users’ needs and challenges before creating or updating your product.

The research stage involves immersive research, user feedback, and direct engagement with users. Bypassing this step can result in products or services that fail to address real human-centric issues and fall flat in the market.

Mistake 2: focusing too much on business goals

Many teams make the mistake of defining problems purely from a business perspective, such as increasing market share or driving revenue. While these goals are important, they should not overshadow the need for human-centered design. The focus should be on solving users’ problems, which indirectly supports achieving business objectives.

For instance, instead of framing the problem as “we need to increase sales,” a more effective approach would be to ask, “How can we enhance user experiences to encourage more purchases?”

Mistake 3: limiting creative idea generation

During the ideation phase, some teams limit their creative process to only “feasible” or “realistic” ideas. This constraint can limit creativity and cause teams to miss stronger solutions.

Instead, ideation sessions should encourage a wide range of innovative ideas, including those that may initially seem far-fetched. Techniques like brainstorming and design sprints are valuable for generating diverse design ideas.

Pro tip: create a multidisciplinary team to bring various perspectives to the table, pushing boundaries and challenging assumptions. By integrating diverse viewpoints and fostering a culture of open idea sharing, teams can explore a broader solution space, leading to more creative and effective designs.

Mistake 4: skipping or rushing prototyping

Prototyping is a critical stage in the design process model that should not be skipped or rushed. Creating prototypes allows teams to test and iterate on their design solutions, uncovering potential issues before full-scale development. Skipping this step can result in unvalidated assumptions and costly mistakes down the line.

Effective prototyping involves building low-fidelity versions of the product and conducting initial testing with users. This process provides deeper insights into how real users interact with the design, revealing areas that need improvement. Agile teams should invest sufficient time in this stage to refine their solutions and ensure they effectively meet users’ needs.

Mistake 5: ignoring the need for iteration

Treating the design thinking process as a linear sequence of steps is another common mistake. In reality, design thinking is an iterative problem-solving methodology in which each stage informs the previous one. Ignoring this iterative nature can lead to missed opportunities for refinement and improvement.

For example, findings from the test stage may highlight new insights that require revisiting the empathy or definition phases. Agile teams should embrace this cyclical approach, enabling continuous improvement and adaptation. Iterative and observational testing throughout the design cycle is essential for developing a deeper understanding of users and creating truly impactful, human-centered design solutions.

How monday.com’s AI Work Platform supports the design process

monday.com’s AI Work Platform helps teams manage the design process from research and ideation to prototyping, testing, approvals, and launch.

With templates, boards, dashboards, automations, integrations, workdocs, and AI-powered capabilities, teams can build a repeatable design workflow that fits how they work.

Standardize your design workflow with templates, boards, and deliverables

The first step is to outline the overall workflow in different stages and standardize the process with deliverables, boards, and events.

For example, a brief stage can be initiated by identifying a problem and then instructing everyone to note their ideas before the idea review meeting.

With a clear process, teams can follow the same design principles, track deliverables, and keep each stage of the workflow visible.

Bring customer insights from other departments into the design process

Cross-functional collaboration across departments is essential for creating products that your customers love.

Design work often depends on insights from customer support, sales, marketing, product, and operations. Bringing that information into a single workspace helps teams make better decisions without having to chase context across disconnected tools.

Teams can connect monday.com with tools like Zendesk to bring customer support insights into design and product workflows.

And that’s only scratching the surface of what you can do with a single integration.

Keep customer insights visible throughout development

Of course, it’s not enough to just get access to data. You also need to make sure your teams do something with it.

Before starting on a new product, you can include crucial customer insights at the top of every board the product team will use.

That way, everyone involved can make decisions with the customer context in view.

Monitor design progress and feedback with dashboards

With connected boards and integrations, teams can use monday.com dashboards to monitor design progress, feedback, workloads, and launch readiness. Custom widgets can help teams track research findings, prototype status, testing feedback, approval progress, and related data from connected tools.

Use AI-powered capabilities to summarize and organize feedback

Design teams often collect feedback from interviews, surveys, support tickets, usability tests, and stakeholder reviews. AI-powered capabilities in monday.com can help summarize updates, group feedback themes, draft project updates, and surface items that may need attention.

Tools like monday sidekick, monday agents, monday vibe, AI columns, and the AI workflow builder can help teams move from scattered input to clearer next steps while keeping people in control of final design decisions.

Build a design process your team can repeat and improve

Creating something new is easier when the work follows a clear process. The design process helps teams break complex projects into stages, keep user needs visible, and improve ideas before they reach the market.

With monday.com’s AI Work Platform, teams can manage each stage of the process in one workspace, from early research and ideation to testing, approvals, and launch.

Use monday.com’s design workflow template to start building a repeatable process your team can improve over time.

Get started

The content in this article is provided for informational purposes only and, to the best of monday.com’s knowledge, the information provided in this article is accurate and up-to-date at the time of publication. That said, monday.com encourages readers to verify all information directly.