Avoiding a failed CRM project - Top Tips

Gartner Group reports over 70% of IT projects fail to meet expectations and that is mostly due to poor Project Management. 

If you are ever faced with a Gantt chart or a task list referred to as a CRM project plan, then there is an extremely high likelihood of failure. While the schedule is essential, it is only one of seven critical elements of a robust CRM Project Plan.

At the outset, the goal of the project must be crystal-clear to everyone on board. Setting up tangible project goals and objectives is necessary to get all team members on the same page. Knowing exactly what you need to do and having a clear vision of the deliverables, will inform budgeting, resource management, and more intricate details throughout the project lifecycle. This will also help you begin to figure out which tasks or phases of the project are most critical and need to be prioritised.

Effective communication is key for all project managers and small business owners. Maintaining clear and consistent communication with project stakeholders, team members, vendors, and clients is crucial to keeping everyone informed about the project's progress. This not only helps to identify any issues early on in the project lifecycle but also prevents them from escalating into larger problems in the future. To streamline communication, consider using collaboration tools like Slack to organise and manage your communications efficiently. By keeping everyone on the same page, you can ensure smoother project execution and successful outcomes.

Managing major projects involves balancing budgets, engaging stakeholders, meeting deadlines, and navigating various challenges. A centralised project plan serves as your roadmap, offering updates on progress and capturing key insights post-completion.

Project Plans must include:

1. Execution Charter

An executive summary of what is to be achieved. Detailing timeline, outcomes and who is involved in the project.

The Project Management Execution Project Charter is a short, preliminary document that provides authority for the Project Work to begin and establishes the authority of the Project Manager. A Project Charter document describes a project to create a shared understanding of its goals, objectives and resource requirements before the project is scoped out in detail.

2. Stakeholder Identification

Project Stakeholders are “Individuals and organisations who are actively involved in the project, or whose interests may be positively or negatively affected as a result of project execution or successful project completion" as defined by the Project Management Institute.

Not all Stakeholders are equal so it's important to do Stakeholder Analysis so you can  prioritise your Stakeholders. There are 2 primary types of project stakeholders - internal and external stakeholders;

Internal stakeholders: These stakeholders originate from within the organisation. Internal stakeholders encompass individuals or groups within the company, including team members, managers, executives, and other relevant parties.

External stakeholders: These stakeholders  are individuals or groups external to the organisation. This encompasses customers, users, suppliers, and investors who may have a vested interest in or be impacted by the project's execution or successful completion.

The types of stakeholders in project management you will see are;

• Project manager and team

• Functional Line Managers

• Team members and daily users

• Resource managers

• Executives/Senior management

• Company owners

• Investors

Stakeholder Communication

Stakeholders my change over the course of the project so it's important to have Contact Details of Executives, managers, users, and influencers involved in or affected by the project to keep them updated with the status of the project items that matter most to them. Various factors play a significant role in shaping stakeholder communication.

• The type of communication: Does the stakeholder prefer to receive information proactively, or does he prefer to seek out information himself? A differentiation can be made between push and pull communication methods.
• The frequency of communication: Does the stakeholder prefer real-time updates, or would they rather receive a weekly update or a monthly summary?
  
• The means of communication: Does the stakeholder prefer a personal conversation or a phone call for updates, or is an email with a status update sufficient? Perhaps they prefer receiving reports in a group video meeting?
  
  

3. Scope of the Project

Including Requirements Definition and Specification and Exclusions

Requirements Definition

Requirements definitions detail both WHAT the project will enable and exactly HOW the functionality, system and support will deliver the WHAT. They provide a clear framework for all stakeholders to strive towards, even when not all stakeholders have a precise vision of the finer details.   The definition should also include Testing Requirements and scripts to prove the requirements have been met in accordance with the agreed business process. 

In such instances, delving deep into project requirements becomes crucial to unveil all layers and gather comprehensive information before kicking off the project.

Project Specification

Project spec is a comprehensive document outlining the objectives, functionality, and ultimate purpose of a business plan implementation. It includes details on the software to be utilised, performance expectations from a user perspective, all within a concise format of just a few pages.

This document serves as a vital tool to guide developers on precisely what needs to be accomplished. Collaboration is key in its development, involving input from managers to developers across the board.

Project Specifications are essential for any project, especially a tech project,  whether it be a website, or a business application. They provide a detailed roadmap for project development, outlining all necessary components for successful project completion.

Define the project’s exclusions

When managing scope, it's crucial to define not only what you will do but also what you won't.  Setting clear boundaries is key in staying focused on the project at hand.

4. Delivery Approach

A detailed explanation of how the project will be delivered, including methodology, standards and Quality Assurance processes.

Your delivery approach maybe customer led or maybe it's focus is to minimise risk, once you have established your approach you need to communicate the methodology to be used in the project. There are many types of project delivery methods for professional services, including:

The Project Management institute has a comprehensive blog article to help best Decide on the Project Delivery Approach.

5. Schedule

Detailed task lists with associated timeframes and resources

When mapping out your tasks, it is crucial to establish realistic timelines. While this may be simpler with smaller, seasoned teams, it can pose a greater challenge with larger, newer teams. Setting achievable timelines helps prevent overcommitting to clients and underestimating the time and effort needed to deliver all project components.

Moreover, this approach enables better expectation management and more effective communication with stakeholders. It is always wiser to err on the side of caution by overestimating and under-committing rather than risking client dissatisfaction, which could deter future collaborations. Maintain transparent and efficient communication with your team and stakeholders to ensure everyone is on the same page regarding timelines and to prevent any client disappointment.

6. RAID analysis and log

Including fully documented risks, assumptions and dependencies

While there is some overlap between RAID Log and Risk Register documents, the difference is that a RAID log is more comprehensive than a risk register. In addition to documenting risks, a RAID log also includes assumptions or actions, an issues log, and dependencies or decisions.

7. Project Management log

Log of all tasks and assigned responsibilities

The project log serves as a centralised repository for the project team, allowing them to monitor any changes made throughout the project lifecycle. It acts as a valuable tool for documenting past project details, capturing any revisions made in your absence, or any crucial information that may have been overlooked.

This comprehensive document meticulously tracks all project events, not only logging critical decisions but also offering insights into the individuals involved and the reasoning behind those decisions.

Other factors for the business to consider

When analysing proposals for CRM implementation and adoption here is a proven rule of thumb:

-25% of a project cost is project management and related activities

-25% to system and user acceptance test and associated documentation,

-25% to requirements definition documentation, sign off and design,

-25% to implementation

Neglecting to invest enough in project management, such as solely relying on a task list, can steer the project towards becoming part of the alarming 70% of projects that fail.

Related Content

• McKinseys 7S Model to implement Full Cycle Sales
• Project Integration Management
• Waterfall Project Management Software
• Agile Project Management Software

Why not join us at SpokeSpeak?  - a Sales and HubSpot Sales Hub focussed community that's open to HubSpot enthusiasts, experts and newbies as well as those of you who are simply Hub-curious 🤔 

Check out the next episode at SpokeSpeak.com