Of course, it will break
your heart to change what in all likelihood will have become your ???baby??? by now.
In addition, of course, there is a higher cost associated with changes at this point,
since you will need to update not only the modeling language but also the generators
and existing models. However, this heartache and cost are nothing compared to the
heartache you will cause modelers if you do not make the changes, and the cost to
the business in terms of lost productivity.
All too often at this stage we have seen people make mistakes that proved fatal to
the whole introduction of DSM. Most often these mistakes are some kind of shortcut
or ducking out in terms of time, resources, or responsibility. In a way, this is perfectly
natural: de?¬?ning the DSM solution was a challenging learning process, but in a fairly
safe environment. The only people involved on a day-to-day basis were the team
themselves, and the activity was largely technical. Now a new group of normal users
are going to see and use what the team has built. This will certainly result in criticism,
constructive or otherwise.
This is also the ?¬?rst phase where there is the start of the organizational changes that
DSM entails, and many technical people are uninterested in doing the people-related
work to make changes like that run smoothly.
Pages:
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652