Fixit

iOS • Android • interviewing • facilitation • flowcharts • wireframes • prototypes • testing • stakeholder management
Project overview
The goal of this project was to design an app to help office managers fix their office equipment. There were two parts to the project:
1.Enabling the primary functionality, then collecting/synthesising feedback
2.Reiterating to add new features.
My Contributions
As the only designer, working with a business analyst and a team of app developers, I was solely responsible for planning/discovery, creation of flows, design of wireframes, execution of UI, and provision of a testing plan. 
Phase I: Foundation
As a key part of the project from its inception, I worked closely with the client to establish a process to handle flow, wireframes, review, prototyping, testing and reiterating. Some highlights of the process and how I used the results to steer conversations with the stakeholders:

• Problems to be solved & platforms affected
• Related research / insights if available
• Main goal definition & core hypothesis
• What is the “must know” that informs product direction
• Primary issue of focus & things we cannot control
• What is the desired outcome
• What is / what is not in the MVP scope
• How do we define success for this problem (e.g metrics)

Once I had content for this breakdown, I could continued with ideation phase.
Flow
I took the following to the client for feedback:.

1. The main flow (scanning the barcodes/QR codes of broken equipment and associating them with service requests)
2. Wireframes
Connecting everything
After completing the flow and making some minor tweaks based on initial feedback, I finished the wireframes and then created the interface which would result in the prototype.
I then facilitated a design review with developers to collect further feedback.

Prototype: happy path of adding an issue.

Testing
This testing involved engineers and the office managers who were collaborating with our client. I contributed by providing a plan and a comprehensive list of questions and specific tasks for the interviewer to use while testing the prototype.
We got a few things wrong
We took that feedback and used it to create a couple of new features (i.e. enhancements above and beyond the MVP).
Phase II
Those features were:
1. A chat option
2. The ability to deflect issues

Again, I followed the same approach I’d used in Phase 1 (build a prototype, get feedback, iterate and test). Here’s what we ended up with:
From wrong to right
And again, we tested the new features with engineers, and with the office managers who were collaborating with our client and engineers. They all confirmed that they approved of the solutions I had prototyped.

When asked to think out loud (a) during the ticket-creation process and (b) after completion of the ticket, one participant said this:
Outcome
MVP launch went successful the first business that was used as a test run, and the client was looking forward for scaling it to multiple businesses.
Feedback
G.I - Senior Business Analyst
"Loved working with Alex! Not only did he produce some of the best UX and UI work I've seen, but he's also such a cool person to work with. In stressful situations, he has this ability of lighting up the atmosphere for everyone around."

Want to get in touch?
Drop me a line!

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.