28. cure:
before you begin,
ensure consensus on
the “win” and set
priorites
29. symptom:
never enough time
for good development,
user testing or quality
assurance
30. question
do great plans promise
great products?
31. you can not treat software
development like a
construction project
32. The Broken Analogy
“A bridge is the sum of its
parts. The pieces of metal
and welds and everything
else all add up to a single,
static bridge. A software
system is the behavior
created by the dynamic
interaction of its parts”
EffectiveUI
The art of building great experiences in software
33. Things you would never
have to deal with while
constructing a bridge:
34. Can we move the bridge 17
feet to the left?
It’s only 17 feet, so that’s
not a big deal, right?
35. We aren’t very happy with
how the bridge looks so far.
Can you propose a change
in the kind of materials
you’re using to make it
more attractive?
36. Remember when you asked us
whether the bridge would ever
need to support vehicle traffic
and not just pedestrian traffic,
and we weren’t sure, so we just
settled on the cheaper
pedestrian version? Well, we
were wrong. What can you do to
make this work for our needs?
37. We’ve hired an offshore
company to start building from
the other side of the valley so we
can cut the construction time in
half. They’re making some
improvements on your design,
so please coordinate with them
to make sure everything comes
together ahead of schedule.
52. 1. Using the term RIA
2. Putting channel before product
3. Skinning
4. Avoiding conflict
5. Developers aren’t involved in design
6. Not defining success
7. Waterfall
8. Requirements ahead of outcomes
9. Ego
10. Choosing the wrong platform