Improving information management is a priority for most organisations I work with, in both the public and private sectors. The pressure comes from several directions at once: making business processes more efficient, meeting compliance obligations, and delivering new services on top of systems that were never designed for them.

In practice, “information management” has often meant deploying technology — content or document management systems, data warehousing, portal applications. That rarely works on its own. There are usually many systems to integrate, a wide range of business needs to satisfy, and organisational and cultural issues that technology cannot resolve.

Information management is much more than technology. It is equally about the processes and working practices behind how information gets created and used — and about the information itself: its structure, its metadata, and its quality.

The goal of an information management system is to capture, manage, preserve, store, secure and deliver the right information to the right people at the right time — from a trustworthy source, as accurately and quickly as possible, at a reasonable cost. Done well, it treats information as a corporate asset, valued and managed like any other investment.

For my full background and project history, see my personal professional profile.

What good information management gets you

  • Knowing where your information is — on desktops, on servers, anywhere on the network, at any time
  • Control over the growth of unstructured information, which expands far faster than most organisations plan for
  • Lower cost of managing that unstructured information
  • Staff spending less time hunting for key information or restoring lost data
  • More collaboration — if people can find information, they can share it
  • Policy support for information management procedures and practices
  • Fewer costly episodes of missing files, at every level from the executive team down
  • Reduced litigation exposure, particularly where retention policies are weak
  • Better regulatory and audit compliance, at lower cost
  • Identification and protection of the records needed to recover after a disaster
  • Quicker response to customers’ information needs
  • Better decisions, supported by data quality and data governance rather than instinct
  • Support for business processes and operations, for decision making at every level, and for competitive strategy

Information management covers five things

  • People
  • Process
  • Technology
  • Content
  • Culture and organisation

All five have to be addressed. Projects that treat this as a technology exercise are the ones that fail.

The problems I usually find

  • A large number of disparate information management systems
  • Little integration or coordination between them
  • Legacy systems needing upgrade or replacement
  • Systems in direct competition with each other
  • No clear strategic direction for the technology environment as a whole
  • Patchy adoption by staff of the systems that already exist
  • Poor information quality: inconsistency, duplication, out-of-date records
  • Little recognition or support from senior management
  • Limited resources to deploy, manage or improve systems
  • No organisation-wide definitions for information types and values — no shared taxonomy
  • A wide range of competing business needs
  • Lack of clarity about broader organisational strategy
  • Difficulty changing established working practices
  • Internal politics limiting what can be coordinated across the organisation

That list is daunting, but it is also normal. There are practical ways to deliver within these constraints, and that is most of what the job consists of.

How I run an IMS programme

Step 1 — Set up the design and implementation team

  • Establish clear goals, tasks and schedules, and a way of communicating with the planning group
  • Inventory the team’s skills and bring in other expertise where it is missing
  • Inventory the existing systems that will need to be linked
  • Identify who will actually use the system

Step 2 — Survey the stakeholders

  • For each group of users, identify their primary responsibilities
  • Document the existing databases, maps and records, and the formats they are held in
  • Identify the gaps in the data
  • Separate data collection, data management and analytical functions
  • Identify the obstacles to building the system, and the options for getting past them
  • Identify possible sources of funding and staff support
  • Identify current or planned projects that could affect implementation

Step 3 — Prioritise the data needed

  • Rank data needs against what the organisation is actually trying to do
  • Set a schedule for developing or acquiring it

Step 4 — Integrate existing data and develop what is missing

  • Formalise data transfer standards and QA/QC protocols
  • Agree a plan for transferring, relating, integrating and updating data
  • Evaluate the data sources for quality and compatibility
  • Choose the key relational fields and decide how they will be linked
  • Decide how often each database is updated
  • Set criteria for integrating and relating data, based on those findings
  • Put up options against those criteria, with the strengths, weaknesses and cost of each
  • Agree which option is both preferred and fundable

Step 5 — Evaluate hardware and software

  • Identify existing plans for reconfiguring hardware and software that could affect the design
  • Determine the priority and sequence of the applications involved
  • Establish what existing hardware and software can be carried forward
  • Check compatibility between operating systems and platforms
  • Establish the real requirements for exchanging and accessing data, including network capacity
  • Set criteria for the hardware, software and network configuration
  • Put up options against those criteria, with strengths, weaknesses and cost
  • Agree which option is preferred and fundable

Step 6 — Evaluate organisational design, staffing and support

  • Set out information management responsibilities against the chosen technical model
  • Identify staffing needs — hiring, reassignment, training
  • Outline staffing options with their strengths, weaknesses and cost
  • Agree which option is preferred and fundable

Step 7 — Build a short- and long-range implementation plan

  • From steps 2 to 6, develop a multi-phase five-year plan covering staffing and training, hardware, software, application development, data development and conversion, and network and communications
  • Attach realistic funding to each component — a plan without it is a wish list

For my full background and project history, see my personal professional profile, or get in touch.