awork

UX, SaaS

Summary

awork is a work management tool, that enables teams to plan their projects, assign team ressources and track their time - all at one place. compared to other apps, the focus of awork is to make project management as fun as possible, by keeping the UX as clean and easy as possible combined with a modern and playful design. as a customer base they are targeting creative teams, and my focus was the user-centric development of new features and the optimization of existing flows and designs.

‍

What I've done

1. Strategic Discovery: define customer needs & pain points

2. User Research: Conduct user interviews, derive learnings & implement these into concept

3. Optimize current onboarding flow: via testing and iterative concepting

4. Concepts for team planner, subscription process, referral flow etc.

5. Support + lead sprint development teams

‍

Conducting user research

Creating customer centric concepts, needs constant user feedback. At awork I had a lot of freedom to conduct user research e.g. before a big new feature was launched (Called "Team planner"), which included some more complex flows including ressource allocation within a team based on their current workload. Therefore I did user interviews via video calls, letting the users explore the team planner first on their own and then asking them to plan some tasks and to assign some projects to team members. I did that with an interview framework I had set up using Figjam (Step 1) where i could quickly take notes. After the interviews I clustered the feedback and analyzed the challenges users had, while using the planner (Step 2).

‍

Step 1: Gather insights via user testings - collection in Figjam

Step 2: After clustering, I marked down the most common challenges within the app

‍

I presented the feedback to the product development team and let derived ideas concerning smaller UX improvements, as well as bigger conceptual changes that had to be done. By voting for the most important ones (Step 4), I could quickly create ideas, that were directly implemented before the launch (Step 5).

‍

Step 3: Summary of learnings - what did users like/ dislike

‍

Step 4: Derive ideas (small UX improvements & new concept ideas) + vote with team

‍

Step 4: Develop concepts & impactful improvements, starting with the low hanging fruits

‍

Learning

This all happened within 8-9 days and shall show that fast adaption is always possible. Normally I do a nice insight presentation for clients, showing learnings, doing some benchmarking and deriving the concepts. But if time is limited - all you need is a Figjam (or any other form of whiteboard collaboration tool) - take a 1.5 hours working session with the team - to come to really fast and nice results! Although I personally love them - no fancy presentation needed!

‍

Deriving concepts collaboratively

What i really liked was communicating and working together a lot in Figma! Asking for feedback, comment and brainstorm together worked out nicely. Here others in the team commented on concepts I did.

‍