Process

My Design Process Effort

Discovery

The main objective of this phase is to understand the project — how is it improving the user’s life, what value is it adding, what need gap is it solving.

I try to dig in deep, to get answers through research and user surveys.

Ideation & Brainstorm

This is one of my favourite phases in product design. I try to go vast with an array of concepts without really focusing on technical constraints at this point. Each concept comes with it’s set of pros and cons and I along with the respective stakeholders make informed decisions. With a clear understanding of the business and the reason for the product, I also do a competitor analysis to understand what our competition is offering and what how best to carve a niche with our product.

Architecture

Screen Shot 2017-07-10 at 6.26.44 PM.png

Screen Shot 2017-07-10 at 6.22.21 PM.png

Screen Shot 2017-07-10 at 6.21.16 PM.png

Screen Shot 2017-07-10 at 6.48.01 PM.png

This phase is crucial in defining how the whole product ecosystem works. I create information architecture diagrams which communicate the complete solution of what we are trying to achieve with the product. The main objective is find key loopholes in the system and to make sure all stakeholders have a good understanding on what we’re building.

User Journey

Screen Shot 2017-07-10 at 6.35.19 PM.png

Screen Shot 2017-07-10 at 6.36.04 PM.png

Screen Shot 2017-07-10 at 6.39.45 PM.png

Screen Shot 2017-07-10 at 6.37.10 PM.png

Along with the architecture I also create a user journey map, which involves listing down different user segments, user personas and their respective use cases. The primary objective is to discover solutions for each of the use cases. Following which we will have full clarity on the different user segments and their requirements with the product.

Wireframes

Screen Shot 2017-07-10 at 6.42.53 PM.png

Screen Shot 2017-07-10 at 6.50.21 PM.png

Screen Shot 2017-07-10 at 6.51.37 PM.png

Screen Shot 2017-07-10 at 6.47.09 PM.png

Screen Shot 2017-07-10 at 6.45.13 PM.png

This process helps with sketching and laying out all the elements on the screen/page. I sketch out a low fidelity wireframe first with major screens and then create digital high fidelity wireframes which contains all screens and their use cases - the positive, the negative, and very importantly error handling.

Use Case Flows

Screen Shot 2017-07-10 at 6.57.56 PM.png

Screen Shot 2017-07-10 at 6.57.38 PM.png

Screen Shot 2017-07-10 at 6.58.58 PM.png

Screen Shot 2017-07-10 at 6.59.52 PM.png

In complex enterprise products (like Hilti), I created wireframe flows based on each use case. This is because each screen has a multitude of mini flows and interactions which is easier to explain based on flows rather than screens. This greatly decreases the time taken to understand complex flows and get the team on the same page more efficiently.