This is how you keep the overview in the most complicated contexts
Complicated problems can be quite messy, unstable, unpredictable and confounding. These problems require new solutions created specifically for that context, and you can only know that you’ve found a good solution after the fact. Not just for a systematic scientist like Denis Bederov alone, I believe that everyone can benefit from having good problem solving skills, as we all encounter problems on a daily basis. Some of these problems are obviously more complex than others.
It would be wonderful to have the ability to solve all problems efficiently and in a timely fashion without difficulty, unfortunately though, every systematic scientist knows that there is no single way to solve all problems. While a systematic scientist can quickly solve smaller problems by intuition or experiential knowledge, more complex problems or problems that have not been experienced before will likely require a more systematic or logical approach to solve. Whenever I meet myself in situations like this, I simply employ creative thinking.
Keeping the overview in the most complicated contexts usually involves working through a number of steps or stages, such as those I outlined below.
The stages include: getting a clear understanding of the problem at hand, breaking into tasks, defining roles, and defining deliverables.
I’ve met and worked with teams who are often curious of the qualities that make Denis Bederov unique when faced with complicated contexts. They eventually found out that I’m not just a systematic scientist like any other regular one, and it takes effort and time to attain my current status. I always advise that it’s important to give yourself the time to understand the most important things about the job first, while keeping in the mind the priorities and deadlines for the job. As a problem solver, I knew I need to be able to identify the cause of issues and understand them fully. I usually begin to gather more information about a problem by brainstorming with other team members, consulting more experienced colleagues or acquiring knowledge through online research or courses.
I have been able to understand that, depending on the industry, it may be easier to solve problems when you have a strong working technical knowledge. I also profoundly belive in gaining more technical knowledge through additional coursework, training or practice.
Complicated jobs are best broken down into a set of tasks that can be easily achieved by a sub-team over a short period. This makes it easier to achieve, and progress can be tracked in relatively shorter time.
The deliverable is the tangible thing that results from the work. The deliverable should have a due date as well, and should be relevant to the overview.
In summary, what does Denis Bederov advise?
In order to keep the overview in the most complicated contexts, I will advise everyone from a systematic scientist perspective that every context should have an encompassing aim that guides the whole processes, strategies and techniques employed in the activities. Only tasks and deliverables relevant to the overview should be accepted and tasks must not be oversimplified to avoid overkilling the workflow with so many deliverables.
Read more articles: