Microsoft Dynamics CRM

Implementing a CRM or ERP or other enterprise system at a company – of any size – is an immense challenge and investment of manpower and money.

But without an investment in organizational commitment and the right mindset, the project could be doomed from the beginning, resulting in over-runs and low adoption of the new technology. And while project over-runs are the immediate pain, lack of adoption prevents you from capturing all the value of the new enterprise system for years to come.

But it doesn’t have to be this way. This week, Kyle looks at the Kotter 8-Step Process for Leading Change as a framework for realizing the value of your enterprise software investment.

Data is the lifeblood of your enterprise software systems and operations. Without good data, made accessible at the right time to the right people, considerable friction is imposed upon a business. So it’s imperative that, when upgrading or re-implementing your enterprise software, the data enters your new system in the best shape possible. The process of data conversion involves taking existing, legacy data from the older system (or collection of spreadsheets) and organizing and uploading it into the new system. This week, Datix Business Analyst, Ryan Mosby discusses the keys to a successful data conversion – and most of them aren’t technical.

Over the past couple of weeks, I have discussed why business process modeling should not be >skipped or undertaken without a consulting partner despite some common misconceptions.

We’ve worked with clients who believe that they can take on the complex task of business process modeling on their own. While it’s certainly possible for any firm to produce a deliverable that documents its own processes, companies also tend to have certain blind spots that can lead to incomplete or myopic results. And, the results likely won’t map to the enterprise software, leaving key functionality and efficiency untapped. Here are key misconceptions that lead to a risky DIY approach.