These need to be prominent
and explained in plain language. Any type of inner-circle nomenclature, buzzword-laden
prose, or technobabble will make as much headway with a management team as a pillow
through concrete. Simple words, clear messages.
The timeline
Define the length of the redesign process, from start to finish. It??™s important to spell this
out in as much detail as possible, taking into account the team??™s current workload, learning
curves for new technology, testing phases, and whatever else is pertinent. There are
two key rules in laying out the project timeline:
OVERVIEW
13
1
Indicate major landmarks for the process: Don??™t package the redesign as one lump
project; break the timeline into manageable chunks approvers can understand and
measure against. Make sure each milestone can be proven with a tangible product,
like a wireframe, a functional comp, or a fully operational beta.
Be honest about the time: Never over-promise and under-deliver; if the project will
take six to eight weeks, tell the decision-makers it will take ten, and then surprise
them by delivering after only seven.
The cost
The preceding page of advice can be largely ignored, since this is the page every person is
going to flip to right away without reading anything else.
Pages:
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85