Process – Cliff Herndon

01. Define the Problem / User Needs

With every project, listening and understanding the nature of the challenge is the first step in finding a viable solution. This entails effectively engaging with the end-user and comprehending their industry needs or unique circumstances. Who is the user, what are their assumptions, what are their needs, how do they use the existing products currently, what is their online interaction with the UI elements, what devices do they use, and what do they expect to accomplish during their user experience?

Hightlights :

• Meet with Shareholders
• Clearly Define Issues
• Interview Users
• Observe Interactions
• Define Requirements
• Create User Personas

02. Collect Info & Analyze Ideas

After gathering vital information from shareholders and obtaining a clear understanding of the challenges that need to be addressed, my goal is to learn as much as possible about the competitive landscape to explore potential solutions. I study a variety of sources from around the digital landscape to generate new concepts and UI solutions. With enough information, I can start sketching ideas, defining task flows, creating wireframes and low-fidelity prototypes.

Hightlights :

• Brainstorm Ideas
• Market Research
• Analyze Competitive Landscape
• Define Task Flows
• Sketch Rough Ideas
• Create Wireframes
• Generate Prototypes

03. Determine Design Language

Exploring potential concepts and ideas, defining the user flows, and going through the ideation and validation phase of wire framing, I begin by building a catalogue of all the reusable components that will be used within the product. This includes images, patterns, colors, text styles, icons, and even grid systems. Creating an inventory of UI components reveal inconsistencies in the design language and pave the way for a high-fidelity design system.

Hightlights :

• Design Essential Screens
• Design UI Elements
• Create Prototypes
• Create Style Guide

04. Communicate, Collaborate

More than aesthetics and problem-solving, I feel the most important part of the design process is communication and collaboration. It’s vital to maintain a collaborative approach throughout the life of the project and frequently touch base with shareholders, architects, engineers and users to refine the team’s design-language while maintaining the original objective. I make it a point to maintain continuous communication with the team by presenting wireframe sketches, mood boards, iterations and low-fidelity prototypes for feedback and design validation.

Hightlights :

• Frequent Check-ins with Product Owners and Engineers
• Stakeholder Reviews
• User Demonstrations
• Early Feedback

05. Hand-Off, Support and Monitor

Once prototypes are finalized and approved by key shareholders, the “hand-off” occurs and my support and monitoring progress during the development phase with engineers. If well planned, the design hand off starts in the early stages of the product design process. It’s my responsibility to support engineers and provide any last-minute modifications, assets or details. From development to completion, I’ll make sure the engineers are clear on design deliverables, interactions and overall flow.

Hightlights :

• Hand-Off to Engineers
• Product Demonstrations
• Collab to Provide Clarity
• Support and Monitor

06. Test, Revise, Repeat

Before signing off and launching the digital product into production, testing and designing should be an ongoing, iterative process. Did our team accomplish what we set out to do and solve for all user experience concerns? Testing and revisions should be an ongoing process, to gather client feedback we use analytic tools such as heatmaps and A/B testing to measure the success of our decisions. Through the data and findings, we can iterate and make adjustments accordingly. The goal is to carryout user research whenever you can to design with the people, not just for them.

Hightlights :

• User Testing
• User Interviews
• Data Collection
• Design Iterations