So, You Want to Be a Designer
By: Dr Mehmet Yildiz
Tags: Entrepreneurship, Design Thinking, Design, Leadership, Innovation

Design, Leadership, Design Thinking, Innovation, Technology

So, You Want to Be a Designer

I share prerequisites in the simplest possible way

Image by Sambeet D from Pixabay

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, etc. The more granular the categorization, the easier to understand and solve the problem.

To solve a problem and design a solution, I provide 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. We need to have a mental picture of the 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.

Designing requires a methodical approach. Design methods can be voluminous; therefore, I provide 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 the 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 we document all details, it is time to 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. After the integration, we have the first iteration of the minimum viable product (MVP). It refers to the bare minimum effort to create minimum functional requirements.

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 model 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. Many industries use agile methods. We can design products and services in our 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.

Advance level courses are specializing in the design of specific domains, disciplines, and industries. Design activities, approaches, and methods can be different based on the field, the subject, and the industry.

Design Thinking is a commonly used process for product and service development which is articulated in the attached story.