- You get your website designed.
- It's BLAH.
So, you go back, think of ways to improve it, get your ideas to the designer, and weeks later you still get BLAH.
How do complex stuff get done for happy clients?
Software developers call the approach agile development:
- They release client projects early and often.
- Every release can stand on its own (e.g., Version 0.001, Version 0.002, Version 0.003, etc.)
That way, you correct mistakes early and often without having to go back and redo chunks of the project -- saving freakish:
You also ensure that the project improves incrementally, according to the client's satisfaction, and every release is a step closer to completion.
Instead of waiting months for a client to see X, the client sees the project quickly (weeks/days) to lend feeback and guide direction as early as possible.
The Cognitive Biases
Peeps tend to get into habits thinking Client X WANTS THISSSSS, based on conversational information that doesn't paint a perfect picture of what they really want in their heads.
- So the project contractor builds it according to what s/he thinks the client wants.
- The client pictures something else.
- So, then: "DANG OKAY YOU THINK YOU KNOW BETtER THAN ME SO ILL JUST DO WHAT YOU WANT."
The contractor then surrenders leadership on the project to the client, and lets the client lead the rest of the way -- resulting in SUCK STUFF.
Suckiness all around.
Releasing stuff to clients early lets you correct mistakes before they result in catastrophes.
You + Blind Guy
Imagine you're travelling across the country and you don't know the directions. There's a blind guy in the car who knows the directions but HE CANT SEE OH NOES.
So what do you do yo maximize your chances of getting across the country safely and efficiently?
You consult with him early and often to make sure you're going the right direction before you head in a totally catastrophic direction.
Posted on February 03
Next tip »