Creating simple user experiences is complicated.

Customer Focus Cartoon

Designing user experiences to be simple and intuitive isn’t easy. The tendency is to push all the hard stuff onto the back-end folks, but we’ve worked with enough engineering teams to know that the easier we make it for them, the better the experience is going to be for the user.

Learn
Our process begins by gaining a clear understanding of the product or service being built, the user type(s), the industry or category it functions within, the expected (and not-so-expected) use cases, any third-party or other dependencies, existing paradigms, etc.

Listen
Gaining this level of understanding can only happen by listening.

Listening to the product manager, what are the deadlines, where are the roadblocks, who are the stakeholders, what do we need to deliver first?

Listening to your customers, understanding their pain points, how will this tool fit in with their day, what 10% of the tool will they use the most, what solutions are they using now, and why?

Listening to your engineering teams, learning how they work, how they want our code, and how we can best serve them.

By working hard to understand the requirements of all the stakeholders, we’ve found that projects run more smoothly, there’s less iterations, UAT has a lot less surprises, and products get delivered on-time and on-budget

Headset Labs Whiteboard
Please don't erase!

What you can expect

Questions. Lot’s of questions. We’ll sketch out front-end flow diagrams and prepare empathy maps that describe the user’s issues, needs, feelings, and more. (We’ve found empathy maps to be indispensable, especially in the world of chatbots and conversational commerce scripting).

Empathy Map Example
Empathy Map Example

From there we’ll build out use cases into flow diagrams to see where the corner cases are, get a count of how many screens we need to create, how many we can re-purpose as the build gets rolling, etc.

Once we have clear use cases, prioritized functions, and required approvals, we start the design. Depending on the product or service, we’ll create a fair amount of alternatives so there’s no stones left unturned. We build interactive mock-ups so everyone can see exactly how everything flows and behaves before any code is written. We’ll test those mock-ups with users (if possible) and make iterations accordingly – while all this is going on we’ll be in close contact with product managers and engineering teams, so everyone’s on the same page

Front end flow example
Front-end flow example

From designing to testing to iterating to coding.

  • We can handle any portion of your project from any point need us to (we get a lot of “can you fix this UI?” work)
  • Typically we deliver full .css and all other required files¬†
  • If it works better for you, we can design the entire user experience, deliver pixel-perfect wireframes, specifications and .PSD files so your team can generate .css internally
  • If you need it, we can design, prototype and build the entire product from front-end to back-end
  • All work is performed here in the United States
  • We work in Agile or waterfall depending on what you need
  • We’re Invision groupies, love Slack, tolerate Jira, and use GitHub (or any other version control tool you like)
  • We can handle UAT and incorporate the resulting front-end feedback into the product
  • We’re a bit obsessive. Born out of the world of graphic design, QA is in our blood. Nothing leaves us until it’s carefully checked, tested and checked again

Contact us today; we’d love to hear what you have going on.