Ask DN: What's your design process?

almost 8 years ago from , Director of Product Design @AccessLoyalty - Founder @MadeUsable & MOKRs

What steps do you take in your design process?

I have seen various kinds, each different based on the designer and the project.

Do you start with sketches? Work with a Product Manager or Analyst to get requirements? Wireframes? Straight to html? Prototypes? Where does user feedback fit in?

1 comment

  • , almost 8 years ago

    Most projects of mine start with:

    requirements/ideation : more often than not, I have worked with a Product Manager who has given me requirements, or rather we worked together on requirements. Those meetings would frequently generate new ideas.

    sketches/whiteboard : Not all PMs or BAs are visual thinkers. Designers are for the most part. :o) I've found that sketching helps them see what I have envisioned in my head. It also gives me a jump on realizing the overall design.

    requirements validation : When possible, I try to validate the solution(s) that we've come up with to users and/or stakeholders.

    wireframes or hi-fidelity designs or html : I tend to use wireframes when working on something completely new. If I am working within an existing app that I have produced designs for in the past, I will do hi-fi designs. There have also been times where it has been best to go straight to html for the design.

    more validation : It is always good to have those you are designing for in the loop. Once pixels have been laid (or html coded) I show where we are at to users and/or stakeholders, making sure we are on track and that things make sense.

    prototyping : Once I have created screens, putting them together in a prototype to get the flow tuned in is next. For years I have used InVisionApp for this. (http://www.invisionapp.com) It is by far the easiest way to create prototypes for desktop and mobile. I can create clickable prototypes of wireframes or hi-fi designs. If I am creating html, there is a bit more interactivity that can be achieved.

    even more validation : now that prototypes have been created, it is easy to elicit feedback via user testing and/or demoing to stakeholders.

    working with development : throughout the process I'm sure to include the developer that I know is working on the project in what I am producing. Make sure he/she doesn't think that I am creating the need for magic during development.

    development and continued care : After iterating on the design and arriving at the solution, the PM/BA and myself sit with the dev team that is involved in the production of the project and walk though it all making sure they understand the requirements and flow. As they are developing, I keep tabs on the progress of the project, assuring that the final project is in line with what was designed and validated.

    Sure these steps move around depending on the project, but it is more or less what I follow.

    1 point