top of page
The Problem:
Digital privacy is important for everyone, but not everyone makes it a priority due to a high barrier to entry when it comes to cleaning up your digital footprint because everyones data is everywhere. I co-designed Reclaim: a web app that scans your inbox, tells you what companies have your information, what information they have, if you’ve been in a data breach, and what to do about it.
Learnings
Designing Reclaim taught me so many invaluable lessons. I saw all the nuances that happen when designing start to finish, and how quickly things can get complicated.
I learned how important collaboration is between PM, Design, and Dev, and what an efficient agile team looks like.
I was reminded of the importance of storytelling, and tying all design work back to the original user problem we’re trying to solve.
If I Could Do it Again...
No project is perfect. Hence the dumpster fire Slack-reaction, always used in good taste.
If I had to do the project over again, I would take a mobile-first approach, improving responsive design.
I would push for more communication with our marketing team to improve launch efforts and consistency with their landing page and branding decisions.
I would attend developers stand-ups and work more agile from the start, making sure I was working closely with their spikes to translate to final designs and reduce friction in my process.
I would socialize my data from research efforts more, making user research an expectation from stakeholders.
I would document my process better, and use artifact templates to capture solutions.
I would be more intentional about building our design system at the same time, making sure elements used in this product were built to work across multiple platforms.
What I Learned About End To End Product Design
End to end product design isn’t as straightforward as it may seem. There are so many different moving parts, and you may have multiple sections of the product at different points in the design process at any given time. This is where keeping lists, good communication, and having a plan that everyone agrees on is so important.
What I Learned About Agile Development
Agile can vary between each team. It’s important to have tools that an agile team can customize to work for them. Communication is key. No team player should be afraid to share roadblocks, feedback, or ideas, and it’s important to keep that line of communication open. As I designer, I recognize that good ideas can come from anywhere, and Everyone on the team is a SME in something helpful.
What I Learned About My Design Process
My process is lean, fueled by data, and crafted for success. I’m collaborative, ready to get everyone together from kickoff to handoff.
I’m focused on the problem to solve and JTBD, and understand that though my process, it’s my job to get the team to rally around that problem, and the solutions will come.
bottom of page