What problem are we solving? Every profession exists to solve a problem. Disciplines that evolve over time, understand the problem they solve, and the relationship to how they do their work. The disciplines that fail to evolve are the ones that become focused on tools of their craft as it was at some point in time - rather than the problem they solve.
A good approach, "what problem are we trying to solve?" It forms a solid basis for continually improving business processes and identifying something that has evolved into an ineffective solution.
But who is the 'we' trying to solve the problem? RM professionals solve the problems we see (capture, reliability, disposal) with EDRMS/ECM's that make sense to us.
Where we have devolved RM responsibilities to the subject matter expert they are going to find their own solution to the problem (search, access). It may be the same problem for multiple SMEs but they are going to have their own solution that makes sense for them (Google drive, shared drive, desktop) - I see this is as the reason for much of our sprawl. As an RM professional I'd love the SMEs to bring me their problems and let me help them find the solution that works for them - and for me.
But do they know where to find me and do they trust that I can and will help?
- I think the tool "five whys" is really helpful for figuring out what the actual problem we are solving is. We use tools to solve problems. When we keep using the tool and forget the problem, we lose our connection to value and our organisations stop valuing us.
- Trust is built one promise at a time, and one story at a time. If people don't know you can solve a problem, they can't ask. When they know and they ask, following through and helping them in a way that they find helpful builds trust. It's a virtuous cycle - help people, and they (or the people who know you helped) will ask for more help. Hopefully along the way you get budget to help more.
A good approach, "what problem are we trying to solve?" It forms a solid basis for continually improving business processes and identifying something that has evolved into an ineffective solution.
But who is the 'we' trying to solve the problem? RM professionals solve the problems we see (capture, reliability, disposal) with EDRMS/ECM's that make sense to us.
Where we have devolved RM responsibilities to the subject matter expert they are going to find their own solution to the problem (search, access). It may be the same problem for multiple SMEs but they are going to have their own solution that makes sense for them (Google drive, shared drive, desktop) - I see this is as the reason for much of our sprawl. As an RM professional I'd love the SMEs to bring me their problems and let me help them find the solution that works for them - and for me.
But do they know where to find me and do they trust that I can and will help?
Hi Karen, great questions!
My personal opinions -
- I think the tool "five whys" is really helpful for figuring out what the actual problem we are solving is. We use tools to solve problems. When we keep using the tool and forget the problem, we lose our connection to value and our organisations stop valuing us.
- Trust is built one promise at a time, and one story at a time. If people don't know you can solve a problem, they can't ask. When they know and they ask, following through and helping them in a way that they find helpful builds trust. It's a virtuous cycle - help people, and they (or the people who know you helped) will ask for more help. Hopefully along the way you get budget to help more.