Spending adequate time in the problem space is essential. I crave truly understanding the problem we’re trying to solve, why we’re solving it and how it will deliver measurable value. It’s also important for me to understand the existing processes and pain-points to make sure we’re not about to repeat any past mistakes.

Whether this is achieved as a team with a whiteboard and sticky notes, alone in my FigJam or even sketching out loose concepts in my sketchbook, keeping things ‘messy’ at the start allows space for more ideas to flourish before committing to a path forward.

After we’ve all aligned on a solution or two worth exploring, I start designing. Pencil and paper, flowcharts, wireframes, screens and prototypes, there’s a lot of creating and undoing until a cohesive vision is achieved.

(aka. cHaOs MoDe)

Any job is dangerous when done in isolation and that’s especially true when designing software for someone else to use regularly. It’s important to work fast to get something out the door and then use feedback from real users to make improvements in real time.