Experts typically identify the following top five best practices for essentials of strategic managment:
Imagine the big picture, but start small
This is great advice. If you’re starting from scratch (and never had a strategic data management process in place), you’re entering uncharted territory. It’s always smart to start small—test your ideas and visions on a limited scale so you can learn, build the right skills, and make sure your approach is right before it’s widely deployed. At the same time, it is important not to lose sight of the big picture. It’s too easy to get lost in the little things and deviate from the overall goal. So document the overall goals of the project (what the strategic data management process will look like), identify a small area that can become a pilot test area, and test your approach with this “pilot” test. Also see essentials of strategic managment.
Appoint a project sponsor
As with all enterprise-wide projects, it is important to have a “sponsor” from senior management who will lead the implementation of the data management strategy. His task will be to actively promote and communicate the strategy to the entire organization. This “sponsor” will also provide accountability, shape the data mindset, and help resolve disputes between business units over data use.
Develop a business case
Essentials of strategic managment systems are not without costs. Even if you don’t need special equipment to develop the framework and other details of the concept, you still have to do some work – and this will require resources, that is, the working time of employees.
It is a good idea to develop a business case for such a project. It should contain a description of the project in general terms, a statement of goals and objectives, expected benefits, as well as a timeline with milestones and parameters (indicators) of progress and success achieved. These metrics will help keep the project on track as the project team evaluates progress against predetermined deadlines and milestones. The business case also reminds team members of what the project is for and why it is important for the organization to get it done right and on time.
Choose the right metrics
Measurement is necessary, but “more” does not always mean “better”. Even if the measured indicators are automated, they require time and effort; someone needs to review the results, interpret them, and possibly take corrective action. Too many measurable indicators or using indicators that do not make sense can be counterproductive. Users, operators and workers will quickly realize that metrics are not important and as a result may pay less attention to truly meaningful measurements. As with KPIs (Key Performance Indicators), a handy set (usually six to ten) of useful and meaningful measurable is much better than 50 or 100 parameters that give no idea of how systems actually function and are achieved. Whether the goals set.
Most people have a primary aversion to change, which is based on the fear of the unknown, and the best way to deal with it is information. Be open to those who will be affected by the new processes and procedures, whether or not they are active participants in the process. Explain what you are doing and why. Tell them how it will change their work life (may be small changes) and why collaboration and support for change is important. Involve those who will have the greatest impact on the planning and implementation of new procedures. They have the best understanding of how changes will affect performance, how they can be adjusted to cause less irritation, and how to improve the process to produce better data.