Where I struggle most is in dealing with people who understand the theory of software design, but have never really been involved in software projects. They either don’t understand workflows or they’re not conceptual or something. That’s still a challenge I need to overcome.

Workflows must be mandated in transactional UI design (not so much in informational UIs). If a UI designer can’t do them they should be shot!

In my business we have been promoting detailed user interface workflows for years now.

They serve the following purposes:
- Absolutely no question of what users want - They can even replace scenarios and personas if you like.
- Completely clear communication to designers and developers on exactly how the interface fits together.
- Unquestionability (is that a word) for my clients that this UI design stuff is really really complex.

The thing I often hear is ‘oh, we are just reskinning our application for another (customer) audience. The functionality is the same so the UI is easy.’ That is so untrue for transactional apps and workflows demonstrate the value of detailed interaction design.

One of my partner companies only asks for workflows as a deliverable now. They are smart and the government sites they do use similar patterns, but with different workflows. The workflow gives them the insight they need about customer interaction and any more work by my HCI consultants IN THEIR CONTEXT is a waste.

Thanks