Congratulations for being the chosen one ! The business likes your
solution and we are also fine with the technology, functionality and customer
references. Now that we have an agreement on the price lets quickly get
legalities and other formalities out of the way. The process for PO creation
and other paper work will take another couple of weeks. The question is how
quickly can you allot resources to our project ? I do not believe that we need
3 months to get the solution off the ground into a pilot or for that matter
go-live.
Any objections to aggressive timeline expectations from the customer are
brushed aside citing urgency in business need and the dynamic business
environment. Software vendors sheepishly accept the modified forceful project
plan which assumes turnaround of all documentation from users with no delay or
for that matter existence of clean data. Idealistic as it may appear both sides
approach the project with enthusiasm that is outward for the vendor who is
happy to get the business. D-day arrives and the project kicks off with much
fanfare.
This situation has occurred a lot more often than gets visibility; time
to market expectations from commercial-off-the-shelf software implementations
(leaving aside ERP type solutions) are getting shorter. Most of them offer
standard process automation or functionality that is typical across companies. Thus
with basic configuration and some integration the anticipation is that the
solution will be up and running in no time. Reality however bites every time
with outcomes that do not live up to such expectations exposing the fallacy in
the approach.
Analyzing scores of such projects undertaken by many of my peers the
discovery was not very surprising. The facts were largely consistent and
created a picture which when played back to the CIOs made them cringe and
accept it. There were reasons and there were reasons; they were not the usual
that have been published by various groups who track challenged projects. In
almost all cases these failed to achieve timelines as well as deliver the
functionality expected and the CIO ended up with the short end of the stick.
To begin with the evaluation of available options extended to eternity
with high business expectations wanting to select the perfect solution. Comparing
apples with pineapples creates a situation where the end result morphs from
being a custard apple to a jackfruit. Moving from one demo to another scope
expands to encompass all exception conditions. Sanity prevails after some time
with CIO or business CXO intervention to bring back expectations closer to
reality. Elapsed time through evaluation now puts pressure to achieve results
in impractical timelines.
What started as a city street drive has now converted into a formula one
race ! We need to finish the journey in the fastest possible time; get your
experts, put more people on the job, why does hardware delivery take so much
time, put it on the cloud. Configurations cannot take that long, it should be
possible to reuse expertise from other customer projects. We are not that
different but we are different; what we meant is not what you have understood,
you don’t know our business and we don’t have time to educate you.
Time keeps ticking with business participants unable to adhere to
unworkable timelines resulting in missed milestones and angst on all sides.
Reviews soon become infrequent with everyone wanting to just finish the project
with redoubled effort. The cascading effect leaves everyone frustrated and
wondering why they accepted the stretched targets or ever got into the project
in the first place. The formula one race with no equipment, trained drivers and
crew suddenly is back to being what it should have been, a street car race.
Accepting reality brings everyone back to what they should have done to
begin with; plan with real assumptions, acknowledge dependencies and the need
to follow a workable model with good project management practices. It is good
to take time to find the right solution which needs to be given due time for
deployment too. I believe that CIOs need to continuously educate business users
not to apply consumer principles to enterprise software deployments. They need
to push back even at the cost of being unpopular or appearing unaligned.
Sometimes they should also be ready to go to a formula one race !
No comments:
Post a Comment