Data Strategy Steps: Communicate, Communicate, Communicate


We have made it to the end of the week to the last step in executing your data strategy. Now by no means do I think that this process is as easy as 4 steps. The boots on the ground effort that will be required to put this into motion can take months. I am trying to provide some verticals of work so that you can stay organized and focused. The pillars that I have been reviewing over the last few days will provide you with the structure you will need to be successful at developing and executing your data strategy.

I have also spent the last few weeks wrapping everything around one common cord. Communication. Nothing will work if the team is not on board, from the highest level right down to the mail room. The ONLY way to engage them all is to make sure that they all understand the goals, reasons, and how we all plan to get there. Now let’s figure out how to do that.

What do you need to consider when documenting your data strategy?

  • Be clear and concise. The data strategy should be easy to understand for everyone who needs to read it. Avoid using technical jargon or acronyms.  This includes business terms that may be specific to certain departments.  To avoid this, you may need to define these processes or terms as you document the data strategy.  
  • Be specific. The data strategy should be specific enough to guide decision-making, but not so specific that it becomes outdated quickly.  Maybe you do not specifically call out a software package but instead outline the processes or principals that a software package can implement.  
  • Be flexible. The data strategy should be flexible enough to adapt to changes in the business environment.  This strategy is a long-term plan.  Software comes and goes; business objectives change sometimes overnight.  Our data strategy needs to provide the guide rails to get to the goal.

So, what tools do we pull out of the toolbox to help us communicate the plan? Two of the most important will be a roadmap for the overall strategy and a data governance plan.  How do I describe these tools?

  • Data strategy roadmap: A data strategy roadmap is a visual representation of the data strategy. It can be used to communicate the high-level goals of the data strategy and the steps that will be taken to achieve those goals.  This WILL include a timeline and yes that is very important.  We all must be held accountable for the resources we are about to use, and this roadmap will do that.  Here we can visually display our progress and in turn the value that the plan has generated. 
  • Data governance plan: A data governance plan is a document that outlines the rules and procedures for managing data within an organization. It helps to ensure that data is accurate, secure, and compliant with regulations.  This tool will be used more with the business stakeholders because it will be used to communicate the safety of the data. It is also a perfect way to engage them to verify that the decisions that have been made are correct. 

In addition to these tools, it is also important to communicate the data strategy to the business through regular meetings. These meetings should be held with both C-level executives and business stakeholders.

C-level meetings should be high-level and focus on the overall goals of the data strategy. These meetings should be very visual and demonstrate the ROI of the data strategy. The executives need to see how this process is progressing the organization to its objectives.

Business stakeholder meetings should be more detailed and focus on the specific needs of the business. These meetings should be used to get feedback from business stakeholders and to ensure that the data strategy is meeting their needs. This meeting can highlight wins, but it needs to focus on near misses or failures too. Part of being flexible is knowing when to flex and communicating to the business stakeholders is a very important part of that.

By communicating the data strategy through a variety of tools and meetings, you can ensure that it is understood by everyone who needs to know about it. This will help to ensure that the data strategy is successful in achieving its goals.

Here are some additional tips for documenting and communicating your data strategy:

  • Use plain language that is easy to understand. Avoid using technical jargon or acronyms.
  • Use visuals to help explain the data strategy. This could include charts, graphs, or diagrams.
  • Tailor the communication to the audience. C-level executives will need a different level of detail than business stakeholders.
  • Get feedback from the audience. This will help you to ensure that the communication is clear and effective.
  • Keep the communication updated as the data strategy evolves.
  • Have regular touch points.  How often you meet with both groups can and should very.  Communicating with the stakeholders should happen more frequently, but both groups should be meet with routinely.  

Communication will make or break your data strategy.  It does not matter how good a job you do if no one understands what you are doing or how it impacts business objectives you will fail.  Keep the lines of communication open as you move forward with your data strategy.  This is one of the keys you will need to unlock success. 


Comments

Post a Comment

Popular posts from this blog

Data Strategy: Guiding Principles

Image
  It has been a long time since my last post, and a lot of things have changed.  I have a new job, I have moved to the other side of the state, and I even have a new dog.  But one thing that has stayed with me is my focus on data and how much potential it has.  All of this change has also solidified my understanding of why a data strategy is critical to any success in the data world.  Without a strategy, your effort will be as useless as trying to strike the wind.  You have to be able to aim your blows if you intend to hit anything.  In our case, we want to "hit" that business objective, the one thing that the business must have to progress to the next phase in its development.   The thing I have come to understand is that when the term "Data Strategy" is used, most people in management jump right to the end and focus on things like cost or "vendor lock-in".  Some people in management focus so much on what they perceive the outcome will ...
Read more

Data Principles: The Power of Naming Standards

Image
In my last blog, I highlighted five data principles that I have used in the past to create a solid data strategy.  The idea behind a principle is that it is flexible to adjust to changing needs but rigid enough to maintain order.   A good example of this is the golden rule, "do unto others as you would have them do to you".  When you apply this principle, you are free to do whatever you want, as long as it is something you want done to yourself.  It is a very flexible principle that can have serious consequences if broken.   One crucial principle that forms a solid foundation for your data initiatives is  naming standards . It might seem like a simple concept, but consistent naming conventions throughout your data environment can significantly impact efficiency, governance, and understanding for everyone involved.  With the right naming standards, looking into the data environment as a DBA, developer, or user, there will be no question about ...
Read more

Data Governance: Building good bones

Image
The next step in our data governance journey will be setting up the data governance framework. In some ways this is just like the frame that your home is built around. In a home the frame lays out the exterior and interior walls, provides a place for electrical and network wiring, a place for insulation, and more importantly exterior and interior wall coverings like brick and sheetrock. The data governance framework works in the same way. By using principles and guidelines it provides structure around your data so that you can implement things like data cleansing rules, roles around data, and the tools that you allow the business to use. The end goal is to make sure that your data is being used in a consistent and compliant way so that everyone using it gets the same answers. You can see why this is a task that is easier said than done. Your data governance framework should include the following components: Data governance roles and responsibilities : This section should de...
Read more