After completing my wireframes and prototype, it was time to move onto the next step: testing my design.


Thankfully, the usability test went really well — there weren’t any major issues, which I was thrilled about! However, during the session, my friend (who was my test user) asked why there was a Start Task button on the home page when the same feature already existed inside the app.

At first, I tried to explain my reasoning, but as I talked it through, I realised it wasn’t actually as efficient as I had thought. Essentially, the user would be going through the same process twice, just from different places — which made it feel a bit unnecessary.

home.png


Iterations Based on These Findings

After reflecting on the feedback, I decided to remove the Start Task button from the home page.

Honestly, I think it was the right decision — I had been a little unsure about that feature from the start.

Taking it out hasn’t affected the overall flow or functionality of the app, and I actually think it’s made the design simpler, cleaner, and more focused. Fewer repeated options means less chance for users to feel confused about where to begin, which definitely improves usability.

home copy.png


<aside> 👩🏻‍🦱

Reflecting on the Usability Testing Process

Running the usability test was a really interesting experience. Even though I had some practice with usability testing during class, doing it for my own project felt completely different. I tried to follow the research and best practices I’d looked into, but because I was testing with a friend, it was hard to stay completely professional — it would’ve felt unnatural to act too formal. That said, I don't think it impacted the results. I made sure not to give any hints, and I let her explore the app and figure things out on her own. I’m really happy with the feedback I got — especially because she falls right into Poco’s target audience. It was reassuring to hear she liked the app overall, and I’m genuinely glad that she pointed out something I had already been questioning myself. In a way, this experience taught me something important: if I'm doubting a feature, there’s probably a good reason for it. Sometimes, trusting my instinct — especially if something doesn’t feel 100% right — can save time and make the design stronger in the long run.

</aside>