FeedBack Application is a concept I’ve worked on sparked from my own problems and frustrations as a freelance graphic designer.
I applied the design thinking process and through the course of diverging and converging, I developed an application which offers something different to what’s currently available on the market.
I’m often faced with a lot of day-to-day tasks such as invoicing clients, chasing clients for design feedback, managing client expectations and following up on unpaid invoices! To ensure I wasn’t the only designer facing these frustrations I interviewed 5 graphic designers and asked them what they found most frustrating when working with clients. Here are the responses I received:
After reviewing the interview results, I decided to focus on helping designers find a way to ensure they receive feedback from clients on time during the concept stage so they can stick to the project timeline.
I chose to interview 5 graphics designers. Here are the insights I gained after card sorting:
Adobe Acrobat is a software program which creates PDF and other file types. Users share PDFs for viewing, reviewing, signing, and tracks activity too.
Google’s cloud-based platforms Docs, Sheets and Slides allow users to collaborate and edit in real-time as well as leave comments.
Although, Adobe Acrobat and Google allow for collaboration and feedback from all parties involved they all happen inside their own native entities. They also serve a wider target audience and may not necessarily be suitable for creatives.
Who is affected by this problem?
A freelance designer
She works in a co-working space
She constantly checks her email for client feedback
Chasing clients for feedback
Consolidating feedback to give to his designers, so they can design
Equipped with the knowledge gained from the research I had conducted and having developed the personas Sara and David, I then began ideating. Knowing my users all use email to communicate with their clients it was obvious to focus on creating an online application solution.
I identified features the user would need:
Identifying the MVP to take to prototype is essential as I wanted to quickly test and learn from the results. I prioritised features based on users primary needs and features that would give them a surprise and delight with using the product.
Hey there, this is the default text for a new paragraph. Feel free to edit this paragraph by clicking on the yellow edit icon. After you are done just click on the yellow checkmark button on the top right. Have Fun!