I recently had a client ask about MDM measurement for their customer master. In many cases, the discussions I have about measurement is how to show that MDM has "solved world hunger" for the organization. In fact, a lot of the research and content out there focused on just that. Great to create a business case for investment. Not so good in helping with the daily management of master data and data governance. This client question is more practical, touching upon:
what about the data do you measure?
how do you calculate?
how frequently do you report and show trends?
how do you link the calculation to something the business understands?
I just came back from a Product Information Management (PIM) event this week had had a lot of discussions about how to evaluate vendors and their solutions. I also get a lot of inquiries on vendor selection and while a lot of the questions center around the functionality itself, how to evaluate is also a key point of discussion. What peaked my interest on this subject is that IT and the Business have very different objectives in selecting a solution for MDM, PIM, and data quality. In fact, it can often get contentious when IT and the Business don't agree on the best solution.
General steps to purchase a solution seem pretty consistent: create a short list based on the Forrester Wave and research, conduct an RFI, narrow down to 2-3 vendors for an RFP, make a decision. But, the devil seems to be in the details.
Is a proof of concept required?
How do you make a decision when vendors solutions appear the same? Are they really the same?
How do you put pricing into context? Is lowest really better?
What is required to know before engaging with vendors to identify fit and differentiation?
When does meeting business objectives win out over fit in IT skills and platform consistency?
Data management is becoming critical as organizations seek to better understand and target their customers, drive out inefficiency, and satisfy government regulations. Despite this, the maturity of data management practices at companies in China is generally poor.
I had an enlightening conversation with my colleague, senior analyst Michele Goetz, who covers all aspects of data management. She told me that in North America and Europe, data management maturity varies widely from company to company; only about 5% have mature practices and a robust data management infrastructure. Most organizations are still struggling to be agile and lack measurement, even if they already have data management platforms in place. Very few of them align adequately with their specific business or information strategy and organizational structure.
If we look at data management maturity in China, I suspect the results are even worse: that fewer than 1% of the companies are mature in terms of integrated strategy, agile execution and continuous performance measurement. Specifically:
The practice of data management is still in the early stages. Data management is not only about simply deploying technology like data warehousing or related middleware, but also means putting in place the strategy and architectural practice, including contextual services and metadata pattern modeling, to align with business focus. The current focus of Chinese enterprises for data management is mostly around data warehousing, master data management, and basic support for both end-to-end business processes and composite applications for top management decision-making. It’s still far from leveraging the valuable data in business processes and business analytics.
The number one reason I hear from IT organizations for why they want to embark on MDM is for consolidation or integration of systems. Then, the first question I get, how do they get buy-in from the business to pay for it?
My first reaction is to cringe because the implication is that MDM is a data integration tool and the value is the matching capabilities. While matching is a significant capability, MDM is not about creating a golden record or a single source of truth.
My next reaction is that IT missed the point that the business wants data to support a system of engagement. The value of MDM is to be able to model and render a domain to fit a system of engagement. Until you understand and align to that, your MDM effort will not support the business and you won’t get the funding. If you somehow do get the funding, you won’t be able to appropriately select the MDM tool that is right for the business need, thus wasting time, money, and resources.
Here is why I am not a fan of the “single source of truth” mantra. A person is not one-dimensional; they can be a parent, a friend, or a colleague, and each has different motivations and requirements depending on the environment. A product is as much about the physical aspect as it is about the pricing, message, and sales channel it is sold through. Or, it is also faceted by the fact that it is put together from various products and parts from partners. In no way is a master entity unique or has a consistency depending on what is important about the entity in a given situation. What MDM provides are definitions and instructions on the right data to use in the right engagement. Context is a key value of MDM.
As the new analyst on the block at Forrester, the first question everyone is asking is, “What research do you have planned?” Just to show that I’m up for the task, rather than keeping it simple with a thoughtful report on data quality best practices or a maturity assessment on data management, I thought I’d go for broke and dive into the master data management (MDM) landscape. Some might call me crazy, but this is more than just the adrenaline rush that comes from doing such a project. In over 20 inquiries with clients in the past month, questions show increased sophistication in how managing master data can strategically contribute to the business.
What do I mean by this?
Number 1: Clients want to know how to bring together transitional data (structured) and content (semi-structured and unstructured) to understand the customer experience, improve customer engagement, and maximize the value of the customer. Understanding customer touch points across social media, e-commerce, customer service, and content consumption provides a single customer view that lets you customize your interactions and be highly relevant to your customer. MDM is at the heart of bringing this view together.
Number 2: Clients have begun to analyze big data within side projects as a way to identify opportunities for the business. This intelligence has reached the point that clients are now exploring how to distribute and operationalize these insights throughout the organization. MDM is the point that will align discoveries within the governance of master data for context and use.
Watching the Mobile Device Management market is a bit like watching a sneeze. My colleagues Christian Kane and Benjamin Gray are tracking nearly 75 vendors in the space, many of them just a few years old. We've also seen a fresh round of acquisitions as established endpoint management vendors look to shore up their flanks and freshen their portfolios.
Differentiation amongst vendors is hard to come by, as is long-term enterprise MDM experience. And that's what makes LANDesk's acquisition of Wavelink interesting. Mobile Device Management in an industrial or field setting is more than just enforcing passcode restrictions, enabling remote wipe in case of loss, or rolling out software. Companies like Wal-Mart and FedEx have significant portions of their businesses that depend on handheld devices for package delivery, inventory and point of sale. MDM in these settings involves a range of capabilities from diagnosing connectivity and printing issues over the air, to interfacing modern mobile apps to mainframe-based warehouse inventory systems.
Perhaps the best way to describe what Wavelink does is "Industrial MDM". They boast 15,000 customers in 85 countries, and have been in the business for several years. The flagship product is called Avalanche and its historical strengths have been in Windows Mobile environments. They added iOS and Android a couple of years ago and are about to release their 2nd generation release of the same.
Why it makes sense for LANDesk:
Competitive: It gives LANDesk the opportunity to own the IP for MDM technology and positions them differently than other MDM solutions on the market given Wavelink's industrial focus.
I have recently published a report on enterprise mobility in India. Improving mobility infrastructure, including networks and devices, and business and workforce demand are fueling the growth of mobility within organizations. Mobility is being used not only to connect with customers, but also to connect with suppliers, partners, and employees. A few key takeaways from the report are that:
Interest in advanced mobile-enabled applications is increasing. There is a great impetus among enterprises in India to move beyond only mobile-enabling basic applications such as email, IM, contacts, and calendar. Twenty percent of enterprises plan to mobile-enable advanced applications like location-based services in the coming 12 to 24 months, while 37% of enterprises want to mobile-enable customer relationship management.
Mobility is among the top enterprise priorities for 2012 and investment is set to rise. For business decision-makers at enterprises and SMBs in India, provisioning mobility is one of the top three priorities in 2012. As a result, investment in all aspects of mobility — such as mobile devices, applications, middleware, and services — will increase.
The workforce wants employers to support mobility at work. The consumerization of smart mobility devices like smartphones and tablets is beginning to have an impact on the enterprise front. More than 60% of employees want to use smartphones at work.
I don’t blame you. And here’s why: The scope of mobile management is confusing and expansive, including things like mobile device management (MDM), persona separation technology, enterprise application stores, application management and a slew of other tools. Some vendors focus purely on one mobile management category, like device management, while plenty of others tackle two or three different enterprise challenges. At the same time, this market is evolving so fast that any assessment of the technologies and their vendors is out of date within 2-3 months.
But before I explain why Symantec’s acquisition is so important, let me give some more context. Mobile management has three main components which I&O professionals are thinking about, the device, the apps, and the data. Today, most first firms follow a very similar path: devices first – get an MDM solution to provide some control over the environment, set a mobile policy for employees, and start trying to figure out what to do about applications and data. Realistically, MDM only solves your challenge around device control – probably the least important of the three. That’s the path that many vendors are following today. As the MDM market becomes more commoditized, most vendors are turning their engineers towards data protection and sharing tools and application management technology. Had a conversation about Dropbox or Box.net lately? That’s a conversation about both apps and the data.
Today, Tibco Software — best known for its SOA integration, complex event processing, and business process management suite — announced its acquisition of Nimbus Partners, a privately held business process analysis vendor based in the United Kingdom. Nimbus Partners is smaller and less well known than the other more mature and full-featured BPA solutions, such as those from ARIS, Provision, and Mega. Nimbus, which employs more than 100 people, sold process discovery and authoring tools along with its homegrown methodology for quickly capturing and managing detailed information on business processes. Nimbus’ features and ease of use appealed mostly to process architects, process analysts, and business stakeholders that wanted an environment more robust than Microsoft Visio but not as technical — or requiring as much training — as other BPA environments.
Google sent shock waves through the mobile world this morning as it announced a planned acquisition of Motorola Mobility for $12.5 billion in cash. The initial commentary has largely focused around Motorola’s patent portfolio, how this will affect the other Android manufacturers, and what Google will do with the rest of Moto’s hardware business which my colleague John McCarthy summed up nicely in his blog post.
So what kind of an impact does this have on infrastructure and operations (I&O) professionals? For the most part, not much of one. I&O professionals are working to make their organizations platform-agnostic by deploying mobile device management (MDM) solutions. For them, Android is only one in an increasingly crowded space of platforms including iOS, Blackberry, and Windows 7 Mobile.
Still, there is one interesting implication in this deal that I&O pros should take note of — Google gets 3LM. Back in February Motorola Mobility acquired 3LM, a startup including former Google employees who worked on Android, which specializes in enterprise security and management software. Rumors had already been flying that some of the 3LM functionality like storage encryption and anti-malware would be included in the next version of Android (Ice Cream Sandwich). With 3LM now a part of Google, firms might finally management and security capabilities I&O and security pros have been asking for in Android.