Let's Break All The Data Rules!

Michele Goetz

When I think about data, I can't help but think about hockey. As a passionate hockey mom, it's hard to separate my conversations about data all week with clients from the practices and games I sit through, screaming encouragement to my son and his team (sometimes to the embarrassment of my husband!). So when I recently saw a documentary on the building of the Russian hockey team that our miracle US hockey team beat at the 1980 Olympics, the story of Anatoli Tarsov stuck with me. 

Before the 1960s, Russia didn't have a hockey team. Then the Communist party determined that it was critical that Russia build one — and compete on the world stage. They selected Anatoli Tarsov to build the team and coach. He couldn't see films on hockey. He couldn't watch teams play. There was no reference on how to play the game. And yet, he built a world-class hockey club that not only beat the great Nordic teams but went on to crush the Canadian teams that were the standard for hockey excellence.

This is a lesson for us all when it comes to data. Do we stick with our standards and recipes from Inmon and Kimball? Do we follow check-box assessments from CMMI, DM-BOK, or TOGAF's information architecture framework? Do we rely on governance compliance to police our data?

Or do we break the rules and create our own that are based on outcomes and results? This might be the scarier path. This might be the riskier path. But do you want data to be where your business needs it, or do you want to predefine, constrain, and bias the insight?

Read more

Beyond Big Data's Vs: Fast Data Is More Than Data Velocity

Michele Goetz

When you hear the term fast data the first thought is probably the velocity of the data.  Not unusual in the realm of big data where velocity is one of the V's everyone talked about.  However, fast data encompasses more than a data characteristic, it is about how quickly you can get and use insight.  

Working with Noel Yuhanna on an upcoming report on how to develop your data management roadmap, we found speed was a continuous theme to achieve. Clients consistently call out speed as what holds them back.  How they interpret what speed means is the crux of the issue.

Technology management thinks about how quickly data is provisioned.  The solution is a faster engine - in-memory grids like SAP HANA become the tool of choice.  This is the wrong way to think about it.  Simply serving up data with faster integration and a high performance platform is what we have always done - better box, better integration software, better data warehouse.  Why use the same solution that in a year or two runs against the same wall? 

The other side of the equation is that sending data out faster ignores what business stakeholders and analytics teams want.  Speed to the business encompasses self-service data acquisition, faster deployment of data services, and faster changes.  The reason, they need to act on the data and insights.    

The right strategy is to create a vision that orients toward business outcomes.  Today's reality is that we live in a world where it is no longer about first to market, we have to be about first to value.  First to value with our customers, and first to value with our business capabilities.  The speed at which insights are gained and ultimately how they are put to use is your data management strategy.  

Read more

How Will The Data Economy Impact Enterprise Architects?

Gene Leganza
No self-respecting EA professional would enter into planning discussions with business or tech management execs without a solid grasp of the technologies available to the enterprise, right? But what about the data available to the enterprise? Given the shift towards data-driven decision-making and the clear advantages from advanced analytics capabilities, architecture professionals should be coming to the planning table with not only an understanding of enterprise data, but a working knowledge of the available third-party data that could have significant impact on your approach to customer engagement or your B2B partner strategy.
 
 
Data discussions can't be simply about internal information flow, master data, and business glossaries any more. Enterprise architects, business architects, and information architects working with business execs on tech-enabled strategies need to bring third-party data know-how to their brainstorming and planning discussions. As the data economy is still in its relatively early stages and, more to the point, as organizational responsibilities for sourcing, managing, and governing third-party data are still in their formative states, it behooves architects to take the lead in understanding the data economy in some detail. By doing so, architects can help their organizations find innovative approaches to data and analytics that have direct business impact by improving the customer experience, making your partner ecosystem more effective, or finding new revenue from data-driven products.
 
Read more

The Kiss of Death for Data Strategy

Michele Goetz

The number one question I get from clients regarding their data strategy and data governance is, “How do I create a business case?” 

This question is the kiss of death and here is why.

You created an IT strategy that has placed emphasis on helping to optimize IT data management efforts, lower total cost of ownership and reduce cost, and focused on technical requirements to develop the platform.  There may be a nod toward helping the business by highlighting the improvement in data quality, consistency, and management of access and security in broad vague terms.  The data strategy ended up looking more like an IT plan to execute data management. 

This leaves the business asking, “So what? What is in it for me?”

Rethink your approach and think like the business:

·      Change your data strategy to a business strategy.  Recognize the strategy, objectives, and capabilities the business is looking for related to key initiatives.  Your strategy should create a vision for how data will make these business needs a reality.

·      Stop searching for the business case.  The business case should already exist based on project requests at a line of business and executive level. Use the input to identify a strategy and solution that supports these requests.

·      Avoid “shiny object syndrome”.  As you keep up with emerging technology and trends, keep these new solutions and tools in context.  There are more data integration, database, data governance, and storage options than ever before and one size does not fit all.  Leverage your research to identify the right technology for business capabilities.

Read more