How to prevent failure: project education
According to Standish Group, top causes of failed IT project are these:
- lack of end-user engagement,
- unclear specification,
- changes in scope,
- lack of management support,
- lack of planning,
- unrealistic and unclear goals.
I haven’t seen too many failed Microsoft Dynamics NAV implementation projects, but those that I did see fail, have failed precisely for a selection of these reasons.
Take a closer look at the list above. Doesn’t it seem that the blame lays mostly on the customer? But is it really customer’s fault?
There is a fantastic website that I haven’t been aware of yet: 
Implementation is like marriage. For better or worse, you choose a piece of software, take it under your roof and commit to it for a long term, so help you God.
There are three kinds of people: those who watch things happen, those who make things happen, and those who wonder what happened.
Somehow I’ve missed it earlier, but a wealth of information for developers, architects and technical consultants specializing in Microsoft Dynamics NAV is now available on MSDN in the 
Someone has tweeted about my blog yesterday. Was that you?
To customize or not to customize, that is the question. When you see a complex business process far from the standard ERP system, a knee-jerk reaction is to reach for customization tools and do the development.
Last week I participated in a discussion about budgets and whether you should ask your potential customers their budget. It made me think: how often do customers reveal their project budgets before the consultants bid?
When I started blogging just short of two years ago, there weren’t too many NAV blogs. I don’t bother to go do the count, but I figure there was no more than ten of them. Then it exploded: today, there are about forty.