This is the module where I keep track of how I have developed my skills and knowledge to be able to take part in the development of a product. On this page, you will see CAD drawings, CAD models, concept drawings, CAD sketches, logos, and a PDS.
Contents
Application of Design Processes
> Design Process flowchart
The design process that I have decided to take is Google’s Design Sprint methodology. I have chosen this process due to its simplicity and clarity.
I decided against using other process frameworks like Ulrich and Eppinger’s, as Google’s focused on the development of the product rather than the delivery of the product. This helped me not only focus on development and iteration more, but it helped me to appreciate each step and sub-process.
Below you can see my design process in the form of a flow chart, created using LucidChart. Below each step is a short description, and an example of how I’ve taken this step in the development of the GROWfessor.
You can also click on the image to view it in full screen.
> Identifying Customer Needs
Identifying customer needs is an important process that helps me to narrow down an end product. I used Ulrich and Eppinger’s method of customer data collection which was detailed in their book Sixth Edition: Product Design and Development (2016).
This method of customer data collection was laid out in five steps:
1. Gather raw data from customers.
2. Interpret the raw data in terms of customer needs.
3. Organize the needs into a hierarchy of primary, secondary, and (if necessary) tertiary needs.
4. Establish the relative importance of the needs.
5. Reflect on the results and the process.
I will report below how I took each step.
Gathering Customer’s Raw Data and Interpreting Customer Needs
Customer data was collected through interviews; interviewees ranged from housemates, to close friends. Their names and identities were kept anonymous, but I took note of their age and gender.
The interviews were recorded using my phone and were summarised in the tables below. The interviewees spent some time with the GROWfessor prototype beforehand and had it in front of them during the interview.
Interview 1
Interview 2
After all interviews, the customer statements were summarised, and interpreted into customer needs, using guidelines stated by Ulrich and Eppinger:
- Expressing the need in terms of what the product has to do, not in terms of how it might do it
- Express the need as specifically as the raw data.
- Use positive, not negative, phrasing.
- Express the need as an attribute of the product.
- Avoid the words must and should.
After collecting enough interpreted needs, I will then place them into a hierarchal list.
Hierarchal List of Needs
Below is the interpreted customer needs from both interviews, placed in primary, secondary and tertiary needs. The primary needs are the most general needs, while the secondary and tertiary needs express needs in more detail (Ulrich, K.T. and Eppinger, S.D. (2000) Product design and development. Boston: Irwin/McGraw-Hill.)
Organizing the needs into a hierarchy helps to prioritise the most important needs of the user. This helps me to achieve the desired outcome and meet the user’s expectations.
Establishing Relative Importance
Establishing the relative importance of the user’s needs ensures that the product development process prioritizes the most critical aspects of the product. It involves evaluating each need and determining its significance in meeting the user’s requirements.
To establish the relative importance of the user’s needs, it is essential to consider several factors, such as the user’s goals, expectations, and needs which I have collected and displayed above.
Here you can see how I have used those needs to create an evaluation for each customer’s needs, therefore establishing relative importance.
Customer 1: The primary needs of reliable measurement of water content and monitoring the soil’s condition is the most critical. The secondary needs of a screen to display status information, a modern-looking design with a range of colours, and size choices are also important for the user’s experience. Information on repairs and maintenance is the least important but still necessary.
Customer 2: The primary needs of adequate plant care and a screen to display the status of the soil’s water content are critical. Water damage protection and a range of sizes for different plants are also important. A dynamic and ergonomic shape and an aesthetically pleasing design are secondary but still important, while clarity on the product’s ability to solely care for the plant is the least important.
By establishing the relative importance of the customers’ needs, I can focus on the critical aspects of the product and prioritize its features and functionality. This approach helps to ensure that products meet the user’s requirements and expectations whilst providing a satisfying user experience.
Reflection of Processes
Gathering customer data is a critical step in understanding the user’s needs and requirements. It involves collecting information about the user’s preferences, expectations, and suggested improvements. By gathering customer data, I can gain a deeper understanding of the user’s needs and design a product that meets their requirements.
Interpreting customer information into needs is another critical aspect of creating a successful product. It involves understanding the user’s feedback and translating them into specific product requirements and needs.
The process of organizing the needs into a hierarchy of primary, secondary, and tertiary needs allows for a clear understanding of the user’s requirements. By identifying the most critical needs, I can prioritize where I place my efforts the most within the development of my products. The categorization of needs also allows for a clear understanding of which features could be added later in the development process.
Establishing the relative importance of each need was crucial so that I could evaluate each need’s impact on the product’s functionality, user experience and durability. Therefore, I can know what needs to prioritize in terms of the product’s development.
By taking these steps, I have gathered priceless data to be able to have a clear idea of the type of product that I would like to make, whilst still ensuring that I meet the needs of those who are in demand for my products.
> Mission Statement
Below you can find a mission statement (also called a design brief) which is intended to give clear guidance for the product development organization. (Ulrich, K.T. and Eppinger, S.D. (2000) Product design and development. Boston: Irwin/McGraw-Hill.)
> PDS
I have completed a PDS (product design specification), which is a compilation of statements of what the GROWfessor is intended to do. This PDS can be viewed by clicking the images below and will be updated as the PDS is developed.
You can also click here to view it on Word.
Version 1
Revised Version
In this revised version, I have included ‘Certifications’, as well as edited ‘Dimensions and Size’, which describes the new GROWfessor prototype.
Plausible Design Solutions
> Concept Ideation | Sketching
Below are some freehand pencil concept sketches for the florensics GROWfessor. This was a form of ideation that allowed me to generate ideas, based on the competitor research that I collected. The main things that I wanted to think about, were the form factor, clock face UI, and surface finish.
a timelapse of me drawing the concept sketches.
Below you will see the three pages of concepts that I came up with, as well as my explanation of each page, and my thoughts behind them. You can click each image to view them in full screen.
> Decision Matrix
Below you can find a decision matrix of my two prototypes. The User Requirements (URS) were defined by collected customer needs, and the weighting represents the hierarchy of said needs.
This decision matrix was inspired by Pugh’s method of idea selection, which uses weighting and scoring to evaluate different designs based on URS.
Using Technology and Media to Present Design Ideas
> GROWfessor Prototype #1’s Wiring Diagram
I have successfully designed the rough wiring for the first GROWfessor prototype. It uses an LCD and two LEDs to display the status of the soil using an equation. I can also use a potentiometer to adjust the LCD contrast. This rough wiring was figured out through exploratory design.
This circuit diagram can be viewed on TinkerCAD by clicking here.
My next steps will be to design my own plant pot and figure out a way to consolidate the wiring to save more space.
Known Issues
- Untidy wires cause shorts
- Wires could corrode in wet soil
- Crumbly soil can make it hard for the Arduino to get a reading
> GROWfessor Prototype #1’s Casing
Below is a 3D model of a prototype for the florensics GROWfessor. This was designed on Solidworks 2021 and was made to be 3D printed using ABS. This allows me to test components and see the code working within a physical body for the first time, which I showed in this video here.
The CAD file (.SLDPRT) can be downloaded by clicking the button below.
> GROWfessor Prototype 2’s Casing
Following the collection of customer needs, a second prototype has been conceptualised, designed and sent to print as of the 24th of April.
This prototype has seen a change in its shape, colour and size. The shape has been made less flat, and more rounded around all twelve corners, with a fillet of 20mm. I have chosen the colour black, which is a “quieter” colour, and more minimalistic compared to yellow. As well as this, the main pot area has been made bigger, from a volume of 77 cubed mm to 236 cubed mm.
The model below is the new prototype and can be downloaded below.
> GROWfessor Prototype #2’s Wiring Diagram
Below you can find a wiring diagram for the second GROWfessor prototype. This was made using TinkerCAD.
It uses a sole LCD to display the status of the soil using the same equation as the first prototype. I can also use a potentiometer to adjust the LCD contrast. The schematic for this diagram can be viewed here.
> Website Redesign
This website has undergone a major redesign. I felt as though the previous website’s interface was quite clunky, and the narrow page didn’t give enough space for the content to speak for itself. There were barely any images, videos were left uncaptioned, and pages were quite bare. As well as the monotonous grey background, it didn’t do much for aesthetics either.
In the redesigned website, I took a different approach to presenting my work, dedicating the whole site to florensics. I took the white and light green colour scheme from the logo and applied it to the website, which gave it a cleaner interface. The navigation bar at the top has been condensed, and some pages like Quizlet were removed due to lack of effort and subsistence, and other pages like planning are still under redesign.
I also captioned all new images and all existing videos, giving them all a description. This way, people viewing the site wouldn’t need to watch the whole video, but yet read the description for a quick summary. I also replaced some embedded documents with hyperlinked screenshots and GIFs, which makes it easier for someone to view the documents, compared to a small embedded window in the page, as was done on the previous website.
All in all, I am very happy with the redesign of the website, and its clean and simple aesthetics and detailed approach will be a precedent of the direction that my work and my preparation will take from now on.
Manufacturing Processes
> DFM
Below you can see a flowchart that I used to choose how I will produce my products.
By considering a hierarchy of manufacturing processes (primary shaping, secondary processes, test process), I can select and visualise how I produce an end product.
