Let's Build A Project: GHOTIES (Day 3)
Table of contents
Introduction
After taking a day off to attend to my Christmas chores, I decided to pick up where I left off with the project. On day two, I managed to highlight the main tasks and form a vague idea of how I wanted them to take shape. Now, on day three, I focused on organizing those tasks into a cohesive sitemap.
The Work
As I said before, when I design, task flows are extremely subject to change—especially when you start mapping. For today’s work, I focused on organizing my task flows into a sitemap. This involved grouping the tasks logically and ensuring user navigation was always top of mind because I wanted my design to be user-centred.
When designing, you need to do everything in your power to make features logical for the user and ensure they progress reasonably. For example, payment features shouldn’t be haphazardly placed in messaging unless it’s done in a meaningful way that doesn’t confuse the user.
It’s not always easy to get it right on the first try—some designers don’t even get it at all. When it comes to design, you have to strike a balance between being innovative and sticking to certain standards. That’s how you make sure your solution doesn’t end up becoming more of a hassle than the problem it’s supposed to solve.
While working on this project, I wanted to create something that felt out of the ordinary but wasn’t unusable, especially when it came to placing orders with writers. I made it compulsory for clients to create a brief first. Once the brief is sent to the writer, only then can the writer send an order confirmation. Payments would be made using on-platform credits after the order is confirmed. This approach seemed the most efficient to allow writer flexibility while making sure both the writer and client are on the same page before the order is finalized.
At the same time, I made a mental note to handle its implementation carefully.
I considered all these factors and more while creating my sitemap. Mapping out the flows helped me see the bigger picture and identify areas where things could be optimized further.
The Proof
