Activity
Mon
Wed
Fri
Sun
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
What is this?
Less
More

Owned by Paul

Data Protection Officers

148 members • Free

Supporting Data Protection Officers with practical privacy guidance, compliance tools, and peer support for real-world challenges.

This is a Community for records & information professionals to master global standards, modern practices, and lead digital recordkeeping.

Memberships

FREE AI SEO Mastermind Group

1.9k members • Free

AI Money Lab

54k members • Free

ProLink

127 members • Free

Data Governance Circle

427 members • Free

Business basics for success

59 members • Free

⚡️ Lock in with Adam

1k members • Free

Skool Growth Free Training Hub

5.9k members • Free

AI Automation Society

257.3k members • Free

First Time Founders

411 members • Free

68 contributions to Records Information Management
Managing Records in Legacy Systems
Legacy systems often hold large volumes of high-risk records with limited governance controls and poor visibility. Decisions to migrate, decommission, or maintain these systems are rarely straightforward. Governance should guide decisions about legacy systems — not convenience, cost alone, or organisational inertia. Reflection questions: - Do you have legacy systems holding critical or regulated records? - Is there a clear plan for managing or retiring those systems? Action: List one legacy system and the key records-related risks it presents.
1 like • 30d
@Kate Elphick Absolutely agree. A coordinated approach to Information Governance with subsequent policy and procedure development is needed yet seldom attempted or achieved.
0 likes • 17h
If you had an old system (let's say SAP), and you moved from SAP to a new system. The old SAP would be a legacy system.
Governance without overhead
Information governance is sometimes criticised for adding overhead. In reality, well-designed governance should reduce effort, not increase it. The most effective controls are often invisible — they guide behaviour quietly and consistently. Reflection questions: - Which governance controls feel genuinely helpful? - Which feel unnecessarily complex? Action: Note one control that could be simplified without increasing risk.
3 likes • 27d
@Kate Elphick most people don't devote enough attention to metadata. Done effectively, it is an extremely powerful tool.
1 like • 17h
@Kate Elphick Agreed. Not only is metadata a powerful tool, but it essential in terms of ISO 15489 and most Government electronic records requirements. Without metadata (human or system generated, including audit trails), electronic records lack completeness.
Scenario: Retention vs “Just in Case”
A business unit wants to retain records well beyond the approved retention period “just in case they might be useful later”. There is no legal hold and no documented business justification. What would you do? - Enforce disposal strictly? - Allow an exception? - Ask for justification and document the decision? - Escalate the risk? Explain your reasoning, not just your decision.
1 like • Jan 14
@Lebohang Mokoena Well said. I agree. This also provides clear boundaries and hopefully limits request of this nature in future. If there is a legitimate reason to keep them beyond the current retention period, then the retention period should be changed.
1 like • 22h
@Mbava Muhongo Sadly, most laws and regulations only impose "minimum" legal retention periods. I draw on the Privacy or Data Protection laws to emphasise the "Maximum" period, which is "the length of time required to fulfil the purpose for which the records are gathered and used." Anything kept beyond that period is potentially illegal. This only applies to records contain Personal Information or Special Personal Information.
The emotional load of being the “tidy-up” function
RIM teams are often framed as cleaners of organisational mess. This undervalues strategic contribution and creates frustration. The emotional impact accumulates over time. Naming this matters. Questions 1. Where do you feel this perception most strongly? 2. How do you respond to it? Action - Acknowledge one contribution that went unseen.
Being consulted after the system is live
RIM involvement often arrives post-implementation. By then, constraints are real and options are limited. The role becomes one of mitigation rather than design. Knowing what to push for — and what to let go — is judgement. Questions 1. Where are you most often brought in too late? 2. How do you prioritise interventions? Action - Identify one late-stage fix that had the biggest impact.
0 likes • 2d
@Sibusisiwe Kona Awesome. A great win!
1-10 of 68
Paul Mullon
5
280points to level up
@paul-mullon-3091
Active learner and student of continuous personal development. Always willing to learn, contribute and be taught.

Active 2h ago
Joined Dec 6, 2025