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

Memberships

Records Information Management

133 members • Free

19 contributions to Records Information Management
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.
0 likes • 17h
I will acknowledge a quiet win – for example, how I streamlined metadata tags in our Records Management System, cutting search times by 30%. I will share that in a team email, stating that the metadata cleanup resulted in smoother audits and faster searches, highlighting it as a significant achievement. I will continue to frame these wins to shift the perception, emphasizing the strategic value of Records Information Management's work in supporting business objectives and reducing risk.
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.
1 like • 2d
One late-stage fix with big impact – pushed for metadata retrofits in a live system to fix searchability. It improved user adoption and reduced lost documents complaints by like 70% . Had to negotiate scope but totally worth it.
Retention decisions that won’t age perfectly
Retention decisions are made in context — regulatory, organisational, and technological. That context changes. Experienced RIM professionals accept that some decisions will look imperfect later. What matters is defensible reasoning at the time. Questions 1. How do you review past retention decisions? 2. What makes one defensible for you? Action - Revisit one decision and note its original assumptions.
1 like • 2d
keeping project documents for 5 years. Assumptions - Regulations required 5-year retention for audit purposes. - Storage costs were a concern, so keeping docs for "just" 5 years seemed efficient. - Project documents were mainly for reference; no major ongoing legal/biz need expected post-5 years.
When consistency conflicts with practicality
Consistency is a core RIM value, but rigid consistency can obstruct work. Exceptions emerge quietly. Managing them without collapsing the system is subtle work. This balance defines mature programmes. Questions 1. Where have exceptions become normalised? 2. How do you prevent drift? Action - Track one exception and how often it occurs.
1 like • 2d
Saving documents to personal drives instead of shared drives Over a week, this happened 7 times. Reasons might be Faster to save locally Didn't know where to put it in the shared drive Working offline
Explaining disposal without sounding careless
Disposal decisions can trigger anxiety. Many colleagues equate deletion with loss or risk. RIM professionals must explain disposal as governance, not neglect. Language matters here. Questions 1. Where do disposal conversations stall? 2. What framing works best? Action - Rewrite a disposal explanation in plain language.
2 likes • 2d
I think it is clearing out unnecessary documents to reduce clutter and risks, keeping only what's needed for business or compliance. It is about managing information properly, not getting rid of stuff carelessly .
1-10 of 19
Sibusisiwe Kona
3
42points to level up
@sibusisiwe-kona-3021
Recent information science graduate eager to apply skills in a supportive role. Passionate about making difference in people's lives.

Active 17h ago
Joined Jan 20, 2026