During the first week I wanted to connect with the product through the stakeholders: representatives from the marketing, sales, development and support teams.
I set up individual interviews around their schedules and then prioritized in a workshop the order in which we’ll tackle the issues of the next version.
I’m so sorry I haven’t captured more screenshots of the previous version: back then it was the live version and it felt like it would be years until it would be retired and I was so invested in the present that I didn’t considered that I would plan to bore anybody later in a case study.
Course correction
The design process usually follows roughly 4 steps: discover, define, design and then test to iron out the kinks. While it may be healthy, real life situations might push a designer (read sinner) to ease on the bulldog like grip on the process and adapt the methods and knowledge to meet the monsters encountered.
After the interviews it was clear to me that this was a long overdue effort, sprinkled with bits of frustration and the team needed a structure to deliver and visible results, quicker rather than later.
We agreed that we would handle in the first month the main 3 priorities we set, use wireframes as main deliverables and then come up with a style guide that would inform the development as we continue with the rest of the application.
Weekly design sprints before they were a thing
Meeting every Thursday allowed us to make sure we’re on the same page, while email and Skype managed to cover day to day communication.
Each week was a cycle that followed these steps:
- gather data about the next section/page that needs care and prioritize main items to adjust
- manual sketch initial ideas to clear the mental slate
- do research to look for how others deal with similar problems
- build an interactive proposal that covers the adjustments making sure you develop a simple and coherent visual and interaction language
- present it in the weekly meeting and receive feedback
- discuss the finer points of the issues you encountered or foresee when it comes to technical implementation and use
- suggest alternatives and plan for adjustments
A weekly loop that made sure we deliver consistently and feed the pre-planned development efforts in a timely manner.
Tools & magic
I used UXPin to hold all the necessary assets: research results, mindmaps, research results, wireframes and final design assets. It allowed for transparent collaboration and a decent manner to manage the handover to the development team.
Later on I turned to Frontify to hold the specifications for the style guide. Back then it was a magic, brand and atomic design oriented tool.
Are we there yet?
The initial estimate for the duration of the redesign project (made solely by the client) was two months. Before the end of the first month it became clear that at least 4 months would be necessary to accomplish our goals and make sure that a new functionality, the agenda, would be properly integrated.
Since summer holidays bumped into the project’s roadmap journey lasted for a total of 7 months, for the last 3 collaboration was done remotely, from Iasi.