This document discusses managing change to improve organizational results through better management of people, processes, and technology. It provides examples of recordkeeping failures that caused major issues. A case study outlines how one organization engaged employees and implemented governance to address data quality problems. The document advocates a holistic approach considering people, processes, content and technology, and references resources for digital recordkeeping standards.
4. • Need a combined framework
for understanding and
motivating behaviour change
• Need to change
organisational thinking and
people’s behaviours
• Long run quality, governance
and management processes
need to be built into systems
• Make it easier to do it right
thing than to do it wrong
From Geek to Chic?
5. An example of a more holistic approach: EIM
• Combines BI and ECM
• ECM and BI … only cover part
of the information within an
organization [resulting] in a lack
of available information during
decision making processes,
market analysis or procedure
definition
• EIM [takes] the perspective of
enterprise information strategy,
based on the needs of
information workers
• Wikipedia, accessed 15 April 2010
People Process
Technology Content
6. Why Record Keeping?
• Working in the field for over 20 years
• Help organisations understand their
business environment (internal,
external, competitive and legislative)
• A risk-based methodology to surface
issues and ownership
• A holistic approach to managing record
keeping responsibilities in organisations
– including data and documents
• Some things to share and some to learn
8. Case study redaction policy
• Not many organisations
really want their name
associated with data
quality issues
• Though sometimes they
have no choice
9. Kotter’s model for leading change
Sense of
Urgency
Powerful
Guiding
Coalition
Shared Vision Communicate
Empower
Others
Short Term
Wins
Consolidate Embed
• Based on the factors that
contribute to the failure of
projects
• A sense of urgency driving
a powerful guiding
coalitions united by a
shared vision?
• Or de-prioritised, best
efforts work carried out in
organisational silos?
14. Lessons from the Japanese super scandal
• A recordkeeping system is more than just a
software application
• It is also the policies, procedures, people and business
rules that are used to control and support the application
• Data quality doesn’t exist in a vacuum
15. Key areas for managing risks
Governance and
culture
Records management
and data integrity
Human dimensions
Information
availability and use
Risk areas
17. Information availability and use case study
Patients’ documents
found in Sydney street
– Private documents
dumped, including bank
details, medical records,
wills
– Breach of Aged Care Act
– Breach of privacy
18. Information availability and use case study
• Is there a data protection
program?
• Are there standards for
access and use for
contractors and third
parties, such as the police
or regulators?
• Do all staff know the
requirements for protecting
privacy?
• Have they had adequate
training to protect personal
information?
24. Engaging a data business with its data
• 20 years of operations - and data -
growth
• Business processes hard coded into
the system
• Data regularly over-written
• Fields had contents and meaning
changed
• Always quicker and cheaper to buy
more storage and increase the
processing power of the system than
dispose of redundant data
25. Ensuring records and data integrity
• Lost data:
– Massive exercise in re-validating information
– Risk of losing key clients due to delays
– Loss of ‘face’ as a competent administrator
• Contracts kept in un-locked clerical staff desks
• Major business processes were un-documented
• Business decisions based on ‘gut feel’, not data
• Forecasts were largely guess-work
• Staff kept all the access rights ever granted so
could access and over-write data
26. Information availability and use
• Incomplete data stores
– Members erroneously contacted about other member’s
matters
• Too much inaccessible data
– No way to prove decisions right
– Member queries could mean going through 20 years of data
– Forced to accommodate member assertions
– Open to accusations of unfairness or worse
• System - slow and prone to crashing
– Data arrived late causing missed deadlines
– Staff often either idle or working overtime
– Whole departments had to work late to finalise their business
processes
– Batch processes ran into the next work day
– Simple changes took a long time
28. Governance and culture
• Lack of trustworthy data so
hard to provide management
oversight and control
• Failure to assign responsibility
when something went wrong
• Trouble maintaining
accountability standards and
safeguards when upgrading
technology – no confidence
the system could be upgraded
- or even replaced
33. So, from geek to chic?
• Not quite but many wins – and a few losses
– Some people were very unsure about becoming empowered
– Some blossomed, others were happy to take on a more technical role
– Some left!
• Almost universally people were happy with the increasingly explicit
operating environment
• Various activities and tools were undertaken to consolidate embed
these changes :
– Better pre-validation of data on receipt
– Data checking and validation steps added at field and process level
– Daily ‘huddles’ of key staff to identify emerging issues,
– An online issues tracker to codify and communicate known problems
– Wikis of previously undocumented expertise
– Better on the job training
– Cross functional teams including IT people
• An unresolved challenge: digital preservation and continuity
34. Jeff Rothenberg, senior computer scientist at RAND Corp
Digital information lasts forever, or five
years - whichever comes first