Response from: Zubair    (04/27/06 9:13am)

Yes, i feel that quick-fix stop-gap solutions are appropriate; but for projects where a very specific mindset about the implementaion has developed. Successfully implementing new functionality is not possible without gaining the confidence of end users and the quick fix even if not as per best practices, does help gain build confidence. It's akin to the famous cliche....'to be able to change the system, you have to first become a part of the system.'

Response from: Eric Kimberling    (04/27/06 9:20pm)

As you already know from my referenced blog entry, there are different schools of thought on this. I think it is a very healthy discussion and disagreement that we have.

The good news is that we are both concerned with the same common goal: to increase user acceptance, job effectiveness, and efficiency. That's a huge first step that many companies overlook, so I think it's ok that we approach the solution from different perspectives.

Eric
Panorama Consulting Group LLC
www.panorama-consulting.com

Response from: Rajiv Renganathan    (05/02/06 7:16pm)

I think "quick-fix" will always exist simply because they are "quick" and gets the work going.

I think it about successfully managing the change wherein the "quick fix" does undergo relook.