Key takeaways<\/h2>\n\n- The design process helps teams move from problem definition to research, ideation, prototyping, testing, and launch<\/li>\n
- A strong design process keeps user needs at the center instead of relying only on internal assumptions<\/li>\n
- Research, prototyping, and testing help teams reduce risk before investing heavily in a new product, service, or experience<\/li>\n
- Design processes vary by industry, but most rely on clear requirements, feedback loops, iteration, and cross-functional collaboration<\/li>\n
- monday.com\u2019s AI Work Platform helps teams manage design workflows with boards, dashboards, automations, integrations, workdocs, and AI-powered capabilities<\/li>\n<\/ul>\n
What is the design process?<\/h2>\nThe design process is a framework that helps you break down large projects into smaller, easier-to-handle stages.<\/p><\/blockquote>\n
It\u2019s prominent in engineering, architecture, and manufacturing because it helps companies deliver finished solutions that customers want and need.<\/p>\n
At a glance, it looks something like this:<\/strong><\/p>\n![\"Design](\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/02\/Design-process-diagram.png\" "\\"Design")
<\/p>\n
(Image Source<\/a>)<\/p>\nTo do this well, teams gather feedback from potential<\/a>\u00a0users or customers at multiple stages, including before they create a prototype or invest significant time and money into a project.<\/p>\nWhat are the seven steps in the design process?<\/h2>\n
The number of steps technically depends on the industry and overall method, but we like 7.<\/p>\n
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.<\/p>\n
In sequential order, they are…<\/strong><\/p>\n\n- Identifying the problem<\/li>\n
- Researching it in-depth<\/a><\/li>\n
- Ideating possible solutions<\/li>\n
- Evaluating and selecting a promising solution<\/li>\n
- Creating a prototype<\/li>\n
- Testing and troubleshooting<\/li>\n
- Making improvements to and releasing the final product<\/li>\n<\/ol>\n
Let\u2019s take a closer look at these steps and how you can put the design process into practice for your own projects.<\/p>\n
1. Identify the problem you want to solve<\/h3>\n
Whether you found a pattern in negative customer feedback or you have some R&D budget left to spend, the approach stays the same.<\/p>\n
You and your project or product team need to figure out:<\/strong><\/p>\n\n- What problem do you want to solve?<\/li>\n
- Who has this problem?<\/li>\n
- Can the solution help everyone equally?<\/li>\n
- What are the requirements for this project?<\/li>\n
- What are our limitations \u2014 budget and other constraints?<\/li>\n
- What is our ultimate goal?<\/li>\n<\/ul>\n
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.<\/p>\n
Poor requirements gathering, weak upfront planning, and unclear vision are common reasons projects struggle before they ever reach execution.<\/p>\n
![\"Project](\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/02\/Project-failure-causes.jpg\" "\\"Project")
<\/p>\n
(Image source<\/a>)<\/p>\nDon\u2019t neglect the upfront legwork.<\/p>\n
2. Research the problem in-depth<\/h3>\n
At this stage, you\u2019ll figure out the market state, whether any competing products exist or are on their way, and what user needs competitors neglect.<\/p>\n
Again, a few simple questions can help you get to the bottom of things.<\/p>\n
\n- Do current solutions exist that try to solve the problem?<\/li>\n
- Are these failing to meet customer needs in any way?<\/li>\n
- Do these solutions offer niche-specific versions?<\/li>\n
- How much are customers spending on similar products?<\/li>\n
- Can you use existing technologies, open-source or otherwise, to solve the problem?<\/li>\n<\/ul>\n
If you\u2019re trying to solve problems for an existing product or service, starting from scratch isn\u2019t always best. You may find that developing an integration or partnering with another company is the best solution.<\/p>\n
Don\u2019t 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.<\/p><\/blockquote>\n
3. Ideate possible solutions<\/h3>\n
Finally, it\u2019s time to get down to business and start solving the problem.<\/p>\n
Start by using \u201chow might we\u201d questions to create a list<\/a> of ideas. You can also add more detail if you want.<\/p>\n\n- How might we achieve X?<\/li>\n
- What is the scope and timeframe for developing the solution?<\/li>\n<\/ul>\n
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.<\/p>\nBut a list of 50+ unsorted ideas isn\u2019t 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.<\/span><\/a>\nAt this stage, there are 2 potential traps that any project team must avoid. Some companies stick to \u201crealistic\u201d ideas, often aiming too low in the process.<\/p>\n
Others may aim too high, focusing only on the most ambitious or innovative idea without considering feasibility.<\/p>\n
Luckily, there\u2019s a helpful design thinking process that can help teams get the best of both worlds and routinely select the best ideas. It\u2019s called the four categories method, where you group the strongest ideas into four categories.<\/p>\n
![\"Four](\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/02\/Four-categories-method.png\" "\\"Four")
<\/p>\n
(Image Source<\/a>)<\/p>\n\n- The most rational ideas are the easiest to implement and most closely aligned with existing processes<\/li>\n
- The most delightful ideas have the greatest potential to impress or support customers<\/li>\n
- The darling idea is each group member\u2019s favorite idea<\/li>\n
- The long shot is a challenging idea with strong upside if it works<\/li>\n<\/ul>\n
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.<\/p>\n
By using surveys and forms<\/b><\/span><\/a>, you can easily distribute your questions and collect as many participants and data points as possible.<\/p>\nBy the end of this process, you should have four to eight good ideas to take to the next stage.<\/p>\n
4. Evaluate and select a promising solution<\/h3>\n
Okay, so you have your shortlist of ideas. Now, it\u2019s time to put them to the test.<\/p>\n
\n- Does it fit the necessary time frame?<\/li>\n
- Can you complete it within budget restraints?<\/li>\n
- Does it truly align with your target customer\u2019s needs?<\/li>\n
- Is the product in itself a differentiator for your company?<\/li>\n<\/ul>\n
Even if you can\u2019t meet in person, don\u2019t just let one person decide. Distributed or remote teams can use a Kanban board<\/a> to prioritize and select ideas.<\/p>\n![\"Kanban](\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/02\/Kanban-idea-board.png\" "\\"Kanban")
<\/p>\n
Depending on the company’s size, you may have an approval committee or a senior executive who gives the go-ahead for large projects.<\/p>\n
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.<\/p>\n
If you end up with multiple viable options, hold a vote on which to proceed with first. Splitting up your team\u2019s focus too much won\u2019t lead to good results.<\/p>\n
5. Create your prototype<\/h3>\n
Spend as little time as possible validating your idea with a prototype, without rushing the process.<\/p>\n
Remember that this isn\u2019t what you\u2019re bringing to market. It doesn\u2019t need all the bells and whistles and a complete branding kit.<\/p>\n
\n- For physical products, use cheap materials and reusable segments.<\/li>\n
- Rely on lo-fi prototypes like storyboards or partially developed products, where you manually fulfill the process.<\/li>\n<\/ul>\n
Don\u2019t 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.<\/p>\n
6. Test and troubleshoot<\/h3>\n
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.<\/p>\n
If you only have a lo-fi prototype to work with, don\u2019t worry. As long as you deliver the experience your customer expects, you can get meaningful feedback.<\/p>\n
For example, if your product is an AI-powered curator for cheap airline tickets based on someone\u2019s bucket list, you can start with a landing page and have someone manually curate tickets using search engines.<\/p>\n
After the user tests, make sure you interview your customers and ask them relevant questions.<\/p>\n
\n- Did the prototype solve your problem?<\/li>\n
- Was there anything unexpected about the experience?<\/li>\n
- Did you struggle to complete any tasks?<\/li>\n
- What was your first impression of the prototype?<\/li>\n<\/ul>\n
You should also test some users without direct instructions from staff to see how intuitive it is.<\/p>\n
If you\u2019re developing something to replace an existing digital product or feature, you should set up an A\/B test.<\/p>\n
monday.com’s <\/strong>A\/B testing template<\/strong><\/a> can help with that…<\/strong><\/p>\nGet started with monday.com<\/a>\n![\"AB](\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/02\/AB-testing-template.png\" "\\"AB")
<\/p>\n
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.<\/p>\n
7. Make improvements to and release the final product<\/h3>\n
If your prototype was a huge hit, all that\u2019s left now is to touch up your product and release it to the public.<\/p>\n
But first, your team needs to answer the following questions.<\/p>\n
\n- Did users report issues completing any specific tasks with your products?<\/li>\n
- Did they immediately understand how to use it?<\/li>\n<\/ul>\n
If there were significant issues, go back to the prototyping stage. If there weren\u2019t, make adjustments for the smaller issues and move straight to release.<\/p>\n
What is the design process?<\/h2>\nThe design process is a framework that helps you break down large projects into smaller, easier-to-handle stages.<\/p><\/blockquote>\n
It\u2019s prominent in engineering, architecture, and manufacturing because it helps companies deliver finished solutions that customers want and need.<\/p>\n
At a glance, it looks something like this:<\/strong><\/p>\n<\/p>\n
(Image Source<\/a>)<\/p>\nTo do this well, teams gather feedback from potential<\/a>\u00a0users or customers at multiple stages, including before they create a prototype or invest significant time and money into a project.<\/p>\nWhat are the seven steps in the design process?<\/h2>\n
The number of steps technically depends on the industry and overall method, but we like 7.<\/p>\n
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.<\/p>\n
In sequential order, they are…<\/strong><\/p>\n\n- Identifying the problem<\/li>\n
- Researching it in-depth<\/a><\/li>\n
- Ideating possible solutions<\/li>\n
- Evaluating and selecting a promising solution<\/li>\n
- Creating a prototype<\/li>\n
- Testing and troubleshooting<\/li>\n
- Making improvements to and releasing the final product<\/li>\n<\/ol>\n
Let\u2019s take a closer look at these steps and how you can put the design process into practice for your own projects.<\/p>\n
1. Identify the problem you want to solve<\/h3>\n
Whether you found a pattern in negative customer feedback or you have some R&D budget left to spend, the approach stays the same.<\/p>\n
You and your project or product team need to figure out:<\/strong><\/p>\n\n- What problem do you want to solve?<\/li>\n
- Who has this problem?<\/li>\n
- Can the solution help everyone equally?<\/li>\n
- What are the requirements for this project?<\/li>\n
- What are our limitations \u2014 budget and other constraints?<\/li>\n
- What is our ultimate goal?<\/li>\n<\/ul>\n
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.<\/p>\n
Poor requirements gathering, weak upfront planning, and unclear vision are common reasons projects struggle before they ever reach execution.<\/p>\n
<\/p>\n
(Image source<\/a>)<\/p>\nDon\u2019t neglect the upfront legwork.<\/p>\n
2. Research the problem in-depth<\/h3>\n
At this stage, you\u2019ll figure out the market state, whether any competing products exist or are on their way, and what user needs competitors neglect.<\/p>\n
Again, a few simple questions can help you get to the bottom of things.<\/p>\n
\n- Do current solutions exist that try to solve the problem?<\/li>\n
- Are these failing to meet customer needs in any way?<\/li>\n
- Do these solutions offer niche-specific versions?<\/li>\n
- How much are customers spending on similar products?<\/li>\n
- Can you use existing technologies, open-source or otherwise, to solve the problem?<\/li>\n<\/ul>\n
If you\u2019re trying to solve problems for an existing product or service, starting from scratch isn\u2019t always best. You may find that developing an integration or partnering with another company is the best solution.<\/p>\n
Don\u2019t 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.<\/p><\/blockquote>\n
3. Ideate possible solutions<\/h3>\n
Finally, it\u2019s time to get down to business and start solving the problem.<\/p>\n
Start by using \u201chow might we\u201d questions to create a list<\/a> of ideas. You can also add more detail if you want.<\/p>\n\n- How might we achieve X?<\/li>\n
- What is the scope and timeframe for developing the solution?<\/li>\n<\/ul>\n
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.<\/p>\nBut a list of 50+ unsorted ideas isn\u2019t 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.<\/span><\/a>\nAt this stage, there are 2 potential traps that any project team must avoid. Some companies stick to \u201crealistic\u201d ideas, often aiming too low in the process.<\/p>\n
Others may aim too high, focusing only on the most ambitious or innovative idea without considering feasibility.<\/p>\n
Luckily, there\u2019s a helpful design thinking process that can help teams get the best of both worlds and routinely select the best ideas. It\u2019s called the four categories method, where you group the strongest ideas into four categories.<\/p>\n
<\/p>\n
(Image Source<\/a>)<\/p>\n\n- The most rational ideas are the easiest to implement and most closely aligned with existing processes<\/li>\n
- The most delightful ideas have the greatest potential to impress or support customers<\/li>\n
- The darling idea is each group member\u2019s favorite idea<\/li>\n
- The long shot is a challenging idea with strong upside if it works<\/li>\n<\/ul>\n
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.<\/p>\n
By using surveys and forms<\/b><\/span><\/a>, you can easily distribute your questions and collect as many participants and data points as possible.<\/p>\nBy the end of this process, you should have four to eight good ideas to take to the next stage.<\/p>\n
4. Evaluate and select a promising solution<\/h3>\n
Okay, so you have your shortlist of ideas. Now, it\u2019s time to put them to the test.<\/p>\n
\n- Does it fit the necessary time frame?<\/li>\n
- Can you complete it within budget restraints?<\/li>\n
- Does it truly align with your target customer\u2019s needs?<\/li>\n
- Is the product in itself a differentiator for your company?<\/li>\n<\/ul>\n
Even if you can\u2019t meet in person, don\u2019t just let one person decide. Distributed or remote teams can use a Kanban board<\/a> to prioritize and select ideas.<\/p>\n<\/p>\n
Depending on the company’s size, you may have an approval committee or a senior executive who gives the go-ahead for large projects.<\/p>\n
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.<\/p>\n
If you end up with multiple viable options, hold a vote on which to proceed with first. Splitting up your team\u2019s focus too much won\u2019t lead to good results.<\/p>\n
5. Create your prototype<\/h3>\n
Spend as little time as possible validating your idea with a prototype, without rushing the process.<\/p>\n
Remember that this isn\u2019t what you\u2019re bringing to market. It doesn\u2019t need all the bells and whistles and a complete branding kit.<\/p>\n
\n- For physical products, use cheap materials and reusable segments.<\/li>\n
- Rely on lo-fi prototypes like storyboards or partially developed products, where you manually fulfill the process.<\/li>\n<\/ul>\n
Don\u2019t 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.<\/p>\n
6. Test and troubleshoot<\/h3>\n
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.<\/p>\n
If you only have a lo-fi prototype to work with, don\u2019t worry. As long as you deliver the experience your customer expects, you can get meaningful feedback.<\/p>\n
For example, if your product is an AI-powered curator for cheap airline tickets based on someone\u2019s bucket list, you can start with a landing page and have someone manually curate tickets using search engines.<\/p>\n
After the user tests, make sure you interview your customers and ask them relevant questions.<\/p>\n
\n- Did the prototype solve your problem?<\/li>\n
- Was there anything unexpected about the experience?<\/li>\n
- Did you struggle to complete any tasks?<\/li>\n
- What was your first impression of the prototype?<\/li>\n<\/ul>\n
You should also test some users without direct instructions from staff to see how intuitive it is.<\/p>\n
If you\u2019re developing something to replace an existing digital product or feature, you should set up an A\/B test.<\/p>\n
monday.com’s <\/strong>A\/B testing template<\/strong><\/a> can help with that…<\/strong><\/p>\nGet started with monday.com<\/a>\n<\/p>\n
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.<\/p>\n
7. Make improvements to and release the final product<\/h3>\n
If your prototype was a huge hit, all that\u2019s left now is to touch up your product and release it to the public.<\/p>\n
But first, your team needs to answer the following questions.<\/p>\n
\n- Did users report issues completing any specific tasks with your products?<\/li>\n
- Did they immediately understand how to use it?<\/li>\n<\/ul>\n
If there were significant issues, go back to the prototyping stage. If there weren\u2019t, make adjustments for the smaller issues and move straight to release.<\/p>\n
The design process is a framework that helps you break down large projects into smaller, easier-to-handle stages.<\/p><\/blockquote>\n
It\u2019s prominent in engineering, architecture, and manufacturing because it helps companies deliver finished solutions that customers want and need.<\/p>\n
At a glance, it looks something like this:<\/strong><\/p>\n (Image Source<\/a>)<\/p>\n To do this well, teams gather feedback from potential<\/a>\u00a0users or customers at multiple stages, including before they create a prototype or invest significant time and money into a project.<\/p>\n The number of steps technically depends on the industry and overall method, but we like 7.<\/p>\n 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.<\/p>\n In sequential order, they are…<\/strong><\/p>\n Let\u2019s take a closer look at these steps and how you can put the design process into practice for your own projects.<\/p>\n Whether you found a pattern in negative customer feedback or you have some R&D budget left to spend, the approach stays the same.<\/p>\n You and your project or product team need to figure out:<\/strong><\/p>\n 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.<\/p>\n Poor requirements gathering, weak upfront planning, and unclear vision are common reasons projects struggle before they ever reach execution.<\/p>\n (Image source<\/a>)<\/p>\n Don\u2019t neglect the upfront legwork.<\/p>\n At this stage, you\u2019ll figure out the market state, whether any competing products exist or are on their way, and what user needs competitors neglect.<\/p>\n Again, a few simple questions can help you get to the bottom of things.<\/p>\n If you\u2019re trying to solve problems for an existing product or service, starting from scratch isn\u2019t always best. You may find that developing an integration or partnering with another company is the best solution.<\/p>\n Don\u2019t 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.<\/p><\/blockquote>\n Finally, it\u2019s time to get down to business and start solving the problem.<\/p>\n Start by using \u201chow might we\u201d questions to create a list<\/a> of ideas. You can also add more detail if you want.<\/p>\n 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.<\/p>\nBut a list of 50+ unsorted ideas isn\u2019t 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.<\/span><\/a>\n At this stage, there are 2 potential traps that any project team must avoid. Some companies stick to \u201crealistic\u201d ideas, often aiming too low in the process.<\/p>\n Others may aim too high, focusing only on the most ambitious or innovative idea without considering feasibility.<\/p>\n Luckily, there\u2019s a helpful design thinking process that can help teams get the best of both worlds and routinely select the best ideas. It\u2019s called the four categories method, where you group the strongest ideas into four categories.<\/p>\n (Image Source<\/a>)<\/p>\n 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.<\/p>\n By using surveys and forms<\/b><\/span><\/a>, you can easily distribute your questions and collect as many participants and data points as possible.<\/p>\n By the end of this process, you should have four to eight good ideas to take to the next stage.<\/p>\n Okay, so you have your shortlist of ideas. Now, it\u2019s time to put them to the test.<\/p>\n Even if you can\u2019t meet in person, don\u2019t just let one person decide. Distributed or remote teams can use a Kanban board<\/a> to prioritize and select ideas.<\/p>\n Depending on the company’s size, you may have an approval committee or a senior executive who gives the go-ahead for large projects.<\/p>\n 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.<\/p>\n If you end up with multiple viable options, hold a vote on which to proceed with first. Splitting up your team\u2019s focus too much won\u2019t lead to good results.<\/p>\n Spend as little time as possible validating your idea with a prototype, without rushing the process.<\/p>\n Remember that this isn\u2019t what you\u2019re bringing to market. It doesn\u2019t need all the bells and whistles and a complete branding kit.<\/p>\n Don\u2019t 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.<\/p>\n 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.<\/p>\n If you only have a lo-fi prototype to work with, don\u2019t worry. As long as you deliver the experience your customer expects, you can get meaningful feedback.<\/p>\n For example, if your product is an AI-powered curator for cheap airline tickets based on someone\u2019s bucket list, you can start with a landing page and have someone manually curate tickets using search engines.<\/p>\n After the user tests, make sure you interview your customers and ask them relevant questions.<\/p>\n You should also test some users without direct instructions from staff to see how intuitive it is.<\/p>\n If you\u2019re developing something to replace an existing digital product or feature, you should set up an A\/B test.<\/p>\n monday.com’s <\/strong>A\/B testing template<\/strong><\/a> can help with that…<\/strong><\/p>\nGet started with monday.com<\/a>\n 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.<\/p>\n If your prototype was a huge hit, all that\u2019s left now is to touch up your product and release it to the public.<\/p>\n But first, your team needs to answer the following questions.<\/p>\n If there were significant issues, go back to the prototyping stage. If there weren\u2019t, make adjustments for the smaller issues and move straight to release.<\/p>\n<\/p>\nWhat are the seven steps in the design process?<\/h2>\n
\n
1. Identify the problem you want to solve<\/h3>\n
\n
<\/p>\n2. Research the problem in-depth<\/h3>\n
\n
3. Ideate possible solutions<\/h3>\n
\n
<\/p>\n\n
4. Evaluate and select a promising solution<\/h3>\n
\n
<\/p>\n5. Create your prototype<\/h3>\n
\n
6. Test and troubleshoot<\/h3>\n
\n
<\/p>\n7. Make improvements to and release the final product<\/h3>\n
\n