Thinking that process is a silver bullet that can fix everything is sort of like early economic theories that presumed that accurate predictions of markets can be made without incorporating human behavior. You need to factor in the people and the business culture using the process. Many, if not most software businesses are conducted in a waterfall way even though the product they are making may be built using an agile process. The power of agile as well as the meaning of the word implies flexibility, which is why switching an IT department to an agile process alone doesn’t make for a successful software product. For the business to optimize it’s success it needs to listen to the feedback and adapt it’s products, goals and sometimes even budgets.
Presentation By Christina Persson & Joan Vermette.
As a designer, have you ever felt frustrated by having to break the creative process up into tiny task boxes that block the way to good design?
Have you ever felt frustrated by a lack of structure, leading to endless rework, crossed communication lines, and plain old wasted time?
There’s too much process in some cultures, and not enough in others. And we declare that we hate process or we love process, as though that were an immutable quality of our souls.
But what do designers need?
The true beauty of any great digital product lies in the intersection between these various aspects. Without people understanding the big picture of how a modern web project works, from top to bottom, there is bound to be failure at these all-important integration points.
“Hiring a designer to create wireframes is like hiring a carpenter to swing a hammer. We all know that the hammer-swinging is not what matters: it’s the table, the cabinet, the deck. Clients don’t hire us to wield hammers, but to create fine furniture. It’s not the process they need or the tools, but the end result.”