🖊️My Design Process
How my mind worked throughout this project
When first reflecting on my design process, I used the double diamond method as my main inspiration. The main difference is Cool Tasks started as a project, so there was no time to gain insight and research into the problem of current task management apps. I have some notes on what I went through that I'll discuss in more detail later on:
I started with vast ideas at the very beginning, thanks to a mind mapping activity.
I honed in on the MVP
I changed up some basic layouts and designs throughout my iterative process
I landed on my final prototype
This type of funnel system made me think of a turnip on its side:
But more specifically, here is a general design of what my design process looks like (which does look a bit like a turnip):
I had to zero in on a certain feel and features before starting my prototype. After, I went on different paths for iterations and what I wanted to do with the feedback I received throughout the process. Finally, I chose one specific design to present as my final prototype.
Our class started the project off with a Mind Mapping group activity (shown below). It helped all of us understand what we first think of with a task management app, and also give us a new perspective by working and talking with our peers to see if there were any similarities or differences.
With this and other mind mappings, the class decided on what the MVP should be:
Add tasks that contain a title, due date, and level of priority
Categorize tasks by class
Check off/complete tasks when you’re done with them
Some functionality to notify you of certain tasks
With the MVP in mind, I began making a paper wireframe of what I first expected my app to look like.
I really wanted to hone in on the MVP, and thought of adding the search bar and ability to create categories as the only extra features on my first wireframe. The first wireframe did have everything that was expected for an MVP, along with the added features. The main conflict however, was the general layout of my app.
Starting from the first round of group feedback we had done in class for our wireframes, I kept a master document of feedback given to my app:
The main problem was that my home page with the list of classes and a specific class page felt too similar, and there wasn’t anything different about them, resulting in confusion on whether or not you had changed to a different screen.
Following through on the feedback and other changes I felt like I needed to make, I went to work on the next step - creating a user flow with a brand new paper wireframe for each screen. There were major design changes for almost everything, as well as the addition of an edit classes screen.
After gathering feedback from the User Flow, I finally got started in Figma for creating a clickable prototype. Through this time, we used our class time to understand how to get insightful feedback from others, and actually get feedback for our apps. I asked my friends and someone from the IDM floor about my prototype throughout its many iterations.
Finally finishing my iterative process, I landed on my final prototype to showcase my class in my presentation:
Looking Ahead
As the project came to a close and I began creating my presentation for class, I started to think up what I would want to do if this project had higher stakes. For example, if this had been the prompt for a final project, what could I add/change if given more time?
Save previous iterations rather than write over them
Play around with Figma and understand more of its features
Ask better questions to receive specific feedback on certain functionalities
Add a new feature to view tasks through a calendar, and merge multiple accounts' calendars
Create more wireframes before deciding to move on to clickable prototypes
Get more feedback!
Last updated