Unless they’ve got a perfect working knowledge of the entire business, which in my experience is rare. Option 1: Work with a skilled business analyst to help you dig into the operational processes and uncover a solution that works the whole length and breadth of the problem.
Option 2: Do the best you can, calling in subject matter experts as required and checking and testing before you take any action.
This technique of using lessons learned for problem solving ideas is great. It only works if you have a lessons learned log to refer to!
Let’s look briefly at getting started capturing lessons learned so you have an archive of rich ideas to return to as and when you look to improve processes or learn from issues.
You are confident that using that approach is going to get you where you need to be. This is particularly the case with complex processes or projects with lots of moving parts and many stakeholders.
In those situations, it’s hard for the expert in the ‘problem’ area to see exactly what the impact of their solution might be on other departments or downstream processes.You know ; brainstorming for lessons learned is exactly the same process.Most lessons learned capture is, in my experience, carried out after a piece of work.If your lessons learned log gives you a nugget of information you can use to fix this problem, then go ahead and discuss what you’ve found with the team.I find that often this solves the problem straightaway. How we deal with them is sometimes, well…pretty random. After that, simplest means this sub-problem being solved doesn’t depend on others being solved. Jordan Ball (ranked 1st or 2nd out of 65,000 users on Coderbyte), and V. Here are the steps: Know exactly what is being asked. Do you remember being stuck on a problem, you start explaining it, and you instantly see holes in the logic you didn’t see before? This is why you should write down your problem, doodle a diagram, or tell someone else about it (or thing… Don’t dive right into solving without a plan (and somehow hope you can muddle your way through). Nothing can help you if you can’t write down the exact steps. For a brand-new programmer, that can be a tough assignment, even though it only requires basic programming syntax. In fact, a common pattern amongst successful people is their habit of practicing “micro problem-solving.” For example, Peter Thiel plays chess, and Elon Musk plays video-games. Elon [Musk], Reid [Hoffman], Mark Zuckerberg and many others say that games have been foundational to their success in building their companies.” — Mary Meeker (2017 internet trends report)Does this mean you should just play video-games? Talk about what worked, what didn’t go so well and what you have learned from that as individuals and as a team. Documenting the lessons learned is one thing – you’ve now got them in your log so you can refer back to it if necessary.However, you haven’t actually solved anything or prevented problems from happening in the future.Using lessons learned proactively this way will also help you cut down on future problems because you are picking off and improving things as you go.Leigh Espy is a project manager and coach with experience working in startups, government, and the corporate world.