DEFINE THE BUSINESS GOALS
Your ECM initiative must begin with the identification of clearly defined measurable goals. These goals must emerge from cross‐functional planning groups. Too many efforts begin with a list of requirements for the ECM Solution, but these requirements cannot be defined accurately at such an early stage. The goals themselves will typically number between five and 10, and require agreement from all business units before you begin
constructing shortlists of vendors. This will help you avoid lengthier discussions at an inappropriate stage of the ECM effort. The goals should be strategic in nature, reflecting your objectives over two or three years. The overall business goals should succinctly and quantitatively summarize the essence of the required ECM solution, and they should be linked to the overall strategy of your organization. They should also be clearly phrased so that the benefits are clearly understood and actively supported by the executive sponsors and stakeholders. These objectives will form the basis for all requirements of the ECM project and will be the tool that allows irrelevant features to be quickly identified. The benefits of this approach include:
- Faster short listing of suitable vendors.
- Reduced expenditure in the selection phase.
- Increased clarity about the solution components necessary for the appropriate solution.
- Greater project transparency and more support from high‐level sponsors as a result.
- Easier building of business case for the initiative.
- Accurate listing of requirements.
APPLY AN ECM MATURITY MODEL
The adoption of maturity models is inhibited by the perception that they are abstract and theoretical, with little connection to the real world. Yet the appropriate maturity model can provide the basis for practical decisions, cost savings and the mitigation of many risks. A maturity model is a tabular representation of solution areas such as Capture, Workflow, Search and Retrieval, Web Content, or Records Management, together with a rating of how “mature” or developed that solution area can be. A simple thick client capture technology would have a low rating, while a sophisticated, thin client capture technology would score higher. The model can therefore be used to assess the level of maturity a future ECM Solution should have. It also assists in the articulation of a strategic vision and permits insight into the complexities of reaching that vision. A complete and realistic evaluation of all aspects of your current environment is necessary to assess the maturity level of your current system. Without this initial assessment you will be unable to determine what future levels of maturity are achievable, or how much effort is required to exact the corresponding changes. Such analyses also help to simplify buying decisions, and clarify whether the products on which your existing solution is based require upgrading or replacement. Benefits from applying maturity model analysis include:
- The creation of a succinct, easily communicable summary of status of the ECM Solution to executive sponsorship and stakeholders.
- The difficulty and cost of moving an ECM Solution to the desired level can easily be underestimated. A maturity model helps expose these difficulties and costs, and provides valuable input to the design of another indispensable tool — the road map.
BUILD A ROAD MAP TO PROMOTE LONG-TERM SUCCESS
A road map is a high‐level representation of the planned changes against the chosen timeline for those changes. Road maps are commonly represented as Gant charts, with the overall effort typically divided into overlapping phases. Each phase represents the changes required to raise the maturity of the ECM Solution to a higher level on the maturity model. The complexity of the required change will determine whether multiple steps for a particular solution area are taken in any one phase. (A phase typically ranges from three to six months.) This approach helps mitigate the risks associated with lengthier endeavors, such as attrition of key staff and budget reallocation away from the project.
Use a road map‐based approach to:
- Ensure that the order in which you deploy the ECM Solution components matches the priorities of your overall business strategy.
- Help organization leaders avoid deploying short-sighted point solutions and silos. Easy win can be considered, but not at the expense of higher‐order goals.
- Permit a more thorough assessment of vendors and filter out those that can’t support your vision of your solution.
- Allow a careful assessment of how long it will take for your ECM Solution to provide business value.
IDENTIFY AND FOLLOW THE RELEVANT INDUSTRY BEST PRACTICES
Choose a Solution‐Deployment Methodology: ECM programs which diligently apply a project management office (PMO) and solution‐deployment methodology have a significantly higher chance of succeeding. The methodology will provide focus, optimize time to value and help reduce potential risks. Discuss the most appropriate methodology with your vendor. The methodology that your organization primarily endorses may
not provide the full benefits. An intelligent mix of your existing practices and those extolled by the vendor for its products is usually optimal. Choose the Right Team: The right mix of staff will ensure that the right strategy and designs are established, that costs for core‐development phases are reduced and that on‐the‐job training for in‐house staff is provided. Apply a Form of Requirements Tracing: Requirements tracing is a method by which the requirements of the individual phases are aligned with the goals identified and selected for that phase. This provides focus and helps ensure the exclusion of costly and unnecessary features. It can also prevent, or reduce, scope creep. Collaborate With Your Vendor: Involve your main vendor in the selection of the appropriate products and the design of the ECM solution architecture. Some of these changes are likely to involve third‐party products and will require a firm statement of compatibility from your main vendor.
SELECTING A SYSTEMS INTEGRATOR
When implementing an ECM Solution you should set your sights on a full‐service Enterprise Content Management integrator that provides infrastructure and services that streamline information processes. The vendor should help your organization leverage your information assets through document imaging, distributed capture, workflow and integration with existing business software systems. A true ECM vendor will have a comprehensive approach, including analysis, training and support; will advance efficiencies, security, compliance and competition through your entire organization. Teaming with Experience: Your organization should work with a vendor that can bring several years of ECM experience to the table. This results in well‐defined, long‐term goals that are enlightened and effective. Let the Problem Drive the Solution: Work with a Vendor that does not come to you with a specific idea of what product you need, but instead concentrate on specifically defining business challenges that you face. This process leads to business solutions that integrate with your standing technology investment and result in real returns for your organization. The vendor’s services should provide an independent and objective approach. Many vendors use a one size fits all philosophy. Find a vendor that is flexible and has proven methodologies to help you define a truly suitable solution. Best Practices: In each industry there are recognized best practices and leading tools that are used by organizations based on their size and demographics. Seek a vendor that has a breadth of experience to draw upon, so that you can leverage their best practices and apply them.
PITFALLS TO AVOID IN ECM PROJECTS
- Primary causes of excessive deliberation and consequent budget overruns in ECM projects include:
- Disagreements while building a business case for the required investment.
- Poor selection criteria leading to difficulties in selecting a vendor.
- Difficulties in recognizing products to match the solution components.
- Business users rushing to install ECM products to gain short‐term benefits.
- Underestimation of the importance of change management.
- Inconsistencies between the requirements cited and those which govern the deployed solution.
Shon D. Mueller
Senior Account Manager