Concepts (UX) Workflow steps

Those who work in UX, UI design are usually very structured so they jump on to a good workflow like a snake on a baby iguana.
How do we add structure to the concept workflow? This one for me is pretty clear.

  • Concept backlog
  • In progress
  • Review
  • Done

A question comes as to what happens in the review step. You have a few options. Add steps for Amends and Final review or when it’s reviewed and requires more work or amends then it is simply moved back to the backlog. I prefer this as it’s clean.
Another question is when and how do the developers review it?! Now some would shy away from getting the developers to check here. For many reasons I’d include them

  1. They’ll feel part of the team
  2. They have the best knowledge of what’s possible on a platform
  3. The will think about things you’ve not considered
  4. There will be less to talk about when they estimate the work later

Do we add a step? You don’t have to but I personally feel it’s very powerful and it follows the same rules that if a story needs more work then it goes to backlog. If the developer needs to investigate something then it stays in Tech review until she has done her investigation.

Advertisement

chris_stanley_watch


issue_as_a_concept
So our final design workflow looks like this

  • Concept backlog
  • In progress
  • Review
  • Tech review
  • Done

Now on to the Design workflow

Leave a Reply

Your email address will not be published. Required fields are marked *