|
Needs analysis is almost automatically part
of any large-scale organization-wide change in operational
procedures, especially so for big, multi-division organizations.
In this context, needs analysis is a cross-check that what
is being proposed is, in fact, applicable and appropriate.
In mid-sized and smaller organizations, needs analysis is
frequently overlooked or by-passed as unnecessary or simply
ignored because the scale of the operation doesn't seem to
call for it. In the context of mid-sized and smaller organizations,
needs analysis is a primary means of putting "new eyes" on
the situation, an important step in making sure that what
is being proposed is applicable and appropriate.
Failing to do some level of needs analysis is a significant
part of why so many productivity improvement projects do
not live up to expectations or deliver the promised results.
So, we strongly recommend that some form of analysis be part
of every project, even if it is just a check-list that has
been compiled with input from every department that will
be impacted by the project.
We recommend a formal needs analysis process because that
tends to get everyone's attention
focused, at least for a few minutes, on what went on before,
what needs to be done, what constitutes success and a dozen
or more similar questions. It doesn't need to be lengthy
if everyone has already devoted time and thought to the situation,
but experience shows that it does need to happen if you want
to get the return on your investment you expect and deserve.
The degree of detail needed is a
function of the size and complexity of the project and,
to some extent, the organization. We don't over-use or abuse
this technique but we do urge our clients, if they are serious
about results, not to overlook needs analysis. |
