Process from the eyes of a designer

If design was just about brainstorming solutions and tinkering with prototypes then work would feel a lot simpler. *wink* The reality is that there are plenty of other tasks that a designer should be involved in.

As the value of user-centered design becomes more realized, the more designers (and companies) will have to face the fact that creating products and services goes beyond sitting and making things.

A beautiful design process is probably interpreted by each designer in a different way and may also vary based on the type of product or team setting.  If your team is already focused on creating designs from a user-centered approach some of the points shared here shouldn't be too surprising.

Key elements include getting the right skill sets and knowledge experts involved. This method can't be performed alone; it requires getting other moving parts, aside from the designer, to play their role and seek a similar vision--stakeholders, clients, engineering teams, etc.

Here a small, comprehensive list of what and when things might take place to allow for a collaborative and impactful design process when designing a product or a service.

How do your stakeholders perceive the design process? Engineers? It is important to have all players aligned.

Project Introduction

  • Identify the motivation (the "why") behind project or feature
  • Identify the persons who should be involved (skills + knowledge)
  • Identify the best means of user outreach
  • Set an initial deadline
  • Identify the definition of success

Research

  • Paint a picture of the Now with observations, measurements, journey map, task flow, etc.
  • Figure out the drive behind why things are done as they are
  • Identify what can be improved based on pain points, wants, and needs
  • Be aware of "sunny day" and "rainy day" scenarios
  • Compare stakeholder versus user needs
  • Paint a picture of the Future ideal experience with clear requirements
  • Never be afraid to question the original goals of the project if the research reveals that the solution/direction is not right

Design

  • Draw out task flows
  • Sketch and/or wireframe various solutions
  • Exchange perspectives with other designers to feel certain about the direction
  • Test low-to-high fidelity prototypes
  • Record findings and what to improve for next round
  • Refine visuals and package deliverables for engineers

Keep Others Involved

  • Always stay in close contact with stakeholders, clients, and/or product managers
  • Explain the "why" behind your design decisions, tying it to the user's experience
  • Have engineers set eyes on mid- to high-level fidelity designs to plan ahead and get questions answered as early as possible
  • Get engineers in-tune with research findings and user's experience

Development and Deployment

  • Prioritize stories based on user and stakeholder needs
  • Provide support or do additional testing if any new complexities or missing parts are brought to light
  • Track data and behavior using analytics to measure success or use as leverage to dictate future improvements
  • Observe and analyze the new Now from the old Now