As a manager, we are constantly faced with the same dilemmas, we must decide quickly and take advantage of an opportunity. But a small inner voice reminds us that we need to analyze the file in more depth.
All of these analyzes can really help make better decisions, but "too much analysis and that's paralysis ...." says the adage, right? How can we cope?
I always propose the method of small steps. Gone are the days when the production of a big 80-page report to present a file analysis was necessary. But in most cases, one- or two-page files are not enough. A structured method always helps.
Here is the one I propose to you:
1. Frame: Properly frame the problem and express it clearly on paper
2. Validate: Identify all stakeholders or stakeholders in the file and validate the need expressed in the first point. Be careful not to lose sight of the real need, and fall into the "accessory needs".
3. Analyze: Assign the analysis task to someone who will have time to surround themselves with the right people. The key to a good analysis lies in the right analyst with the right contributors.
4. Limit: Inform the analyst from the outset of the time and budget constraints of the said file. Ask clear questions, but do not do the analysis for him.
5. Deliver: Do not over formalize the report, but determine a minimum to produce, for example a comparative table, a list of reasons "for and against", a SWOT analysis, supplier quotes, a precise number of scenarios (2 or 3 max for example). Clearly determining your document expectations will save you a lot of money.
6. Delegate: Trust your analyst; if he feels constantly watched or his work is systematically put aside for the benefit of your own analysis, he will never be able to do it.
7. Act: Respect your own constraints. If you have set a 7-day timeline, make a decision immediately after the submission of the analysis report.
This very simple method allows all managers to make faster decisions, but especially better decisions. I think it helps to find the right balance between "too much analysis" and "too little analysis".
Christian Boulet, your IT Director on request