Upon request from my readers following me on various platforms, in this article, I aim to provide a brief and high-level overview of the design process for absolute beginners and aspiring designers.
I specifically use simple language and refrain from using jargon and technical terms to make it easy to understand for people from a non-design background.
The design process starts with a problem in front of us.
Designers solve problems systematically and methodically.
To solve a problem, first, we need to understand the problem.
To understand the problem, we need to ask several questions.
Asking questions can help us analyze the problem in detail.
We can ask both closed and open-ended questions.
We can analyze the problem until it makes sense to us.
If the problem does not make sense to use, we cannot produce a solution.
We also need to understand the type of problem.
For example, we can categorize the problem as scientific, technological, practical, business, educational, personal, financial, art, etc.
The more granular the categorization, the easier the problem can be to understand and to solve.
To solve a problem and design a solution, I provide some practical steps.
Solution design has two main aspects: creative and procedural.
The creative aspects of the design process require vision. Designers must have a mental image of the end product or service. We also need to have a strategy. It means we need to have a mental picture of how to reach a solution at a high level.
Designing doesn’t necessarily mean inventing.
Designing is to connect several components coherently to create a functional product or service. Therefore, integration skills are essential for designers. Integration refers to logically, physically, and functionally combining, contrasting, and linking objects.
The procedural aspect of designing mandates a methodical approach. I simplify this approach for you. Some methodical approaches can be voluminous so this is a 30 thousand feet view.
Understanding the requirements of the solution is critical.
To understand the requirements, we can ask questions to the owner and users of the solution. For example: What will the user of this object do with it? How, when, and where will they be using it? How often will they be using it? The more questions we ask the better we can understand and confirm the requirements.
Asking questions also can help us to understand the use cases of the solution.
Validating requirements and use cases are the most critical parts of designing a solution.
We need to be detailed and precise for each requirement and use case. Otherwise, our solution cannot meet the desired quality.
Once the requirements and use cases are validated and detailed, we can create a simple diagram of our solution context. The context diagram shows key components (parts) and essential relationships between the components.
The next stage is to create a model for the solution.
A model can be the smallest scale of the final product.
We can develop the model on a paper or a computer screen.
There may be multiple models in complex designs, but in this article, we only focus on simple design model.
Once we have a model, we can document the details of each part and related elements of these parts. Depending on the type of product or service that we are designing, we can describe the attributes and features accordingly. Attributes can be color, size, dimensions, type of materials, etc. Features can be the functions of the product. For example, the object can do x, y, z function.
Once all details are documented, we can start the integration activities. During the process, we can connect and combine items based on the requirements.
Some items may require linking, some contrasting, and some can have various other relationships.
Once the integration activity is done, we have the first iteration of the minimum viable product (MVP). It refers to the bare minimum effort to create minimum functional requirements. You may have heard the term MVP in business environments. Entrepreneurs love this term. Opposite of MVP in the corporate world is gold plating.
The next stage is to test the product. The first test can be a proof of concept. We can perform a proof of concept based on the requirements and use cases of the product.
The test can provide us with the necessary feedback. We can determine whether the product is ready to implement as the first version.
If the tests are successful, we can proceed to the implementation phase and go to the next iteration of the product to further improve it for the next version.
If the tests fail, we examine the solution and look for the faults such as logical errors. After making necessary adjustments and amendments, we test again. This frequent testing approach for the minimum viable product is called agile approach.
By applying an agile approach, our designs can be more economical, faster, and higher quality. Agile methods are commonly used in many industries. You can design products and services in your field by using an agile approach.
The design process can be very comprehensive and involved, especially for complex, first of a kind, and bespoke solutions.
There are advance level courses specializing in the design of specific domains, disciplines, and industries.
Design activities, approaches, and methods can be different based on the domain, discipline, and the industry.
I hope this very simplified approach to the design process can provide useful insights to the beginners and aspiring designers.
Thank you for reading my perspectives.
You may also check my other technical and technology-related stories published on News Break.
Get updates delivered to you daily. Free and customizable.
Welcome to NewsBreak, an open platform where diverse perspectives converge. Most of our content comes from established publications and journalists, as well as from our extensive network of tens of thousands of creators who contribute to our platform. We empower individuals to share insightful viewpoints through short posts and comments. It’s essential to note our commitment to transparency: our Terms of Use acknowledge that our services may not always be error-free, and our Community Standards emphasize our discretion in enforcing policies. We strive to foster a dynamic environment for free expression and robust discourse through safety guardrails of human and AI moderation. Join us in shaping the news narrative together.
Image by 
Most Popular
Comments / 0