Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I do web design for a few years now and as I want to make step further and think my designs using flow charts.

What do you recommend? What books? What software to use to actually create the flow charts ?

I need an introduction and some recomendations.

Thx.

share|improve this question

closed as not constructive by JohnGB, Matt Obee, greenforest, Charles Wesley, André Mar 25 '13 at 16:49

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
I understand the question, but we don't allow questions that amount to recommendations as they amount to a discussion and not a specific UX question with an answer. –  JohnGB Mar 25 '13 at 14:11
    
Right now it's a very wide question. Maybe you can ask more specific once you started to dive deeper into the topic. Think of the audience for your flow charts - why did you want to do it in the first place and who's going to look at them? Long ago I used Jesse James Garrets Visual vocabulary: jjg.net/ia/visvocab. –  greenforest Mar 25 '13 at 15:10

1 Answer 1

Good that you are looking into this! I did ux design for years, before working with an experienced information architect, who created user workflows that I was simply envious of!

The way I learned was reading up on UML (Unified Modeling Language), which is used by programmers and business systems analysts - just a smidge differently from the way designers use it. They often use it to model programming and logic flows, ux designers use it to model user flows.

Any UML books you pick up will be helpful in forming the framework you will use to communicate with developers, BUT you'll need to do a mental translation to adapt their rigour to a user workflow.

For instance, I always supply a KEY to translate the shapes I use in a flow. Typically the key consists of, at minimum: user action, system response. You can be flexible in the language you choose for shapes and forming the flow, but you should be as consistent as possible across flows so that your audience can gain fluency in reading your design flows.

Tool of choice for workflows (note: PC user here): MS Visio (this program was designed for flows! also can make beauteous wireframes, but bit of a learning curve). Alternative for Mac users is typically Omnigraffle.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.