It’s not news that the digitally empowered customer is changing our world. What is news is 1) the pace needed to catch up to an extremely dynamic and impatient customer and 2) the magnitude of real change needed to meet the challenges (and opportunities) of a customer-led market.
The magnitude and pace of change driven by customers, competitors, and innovation can be dizzying:
As loyalty structures erode, customers are conditioned to rapidly adopt and abandon services.
The battle of trying to apply traditional waterfall software development life-cycle (SDLC) methodology and project management to BI has already been fought — and largely lost. These approaches and best practices, which apply to most other enterprise applications, work well in some cases, as with very well-defined and stable BI capabilities like tax or regulatory reporting. Mission-critical, enterprise-grade BI apps can also have a reasonably long shelf life of a year or more. But these best practices do not work for the majority (anecdotally, about three-quarters) of BI initiatives, where requirements change much faster than these traditional approaches can support; by the time a traditional BI application development team rolls out what it thought was a well-designed BI application, it's too late. As a result, BI pros need to move beyond earlier-generation BI support organizations to:
Focus on business outcomes, not just technologies. Earlier-generation BI programs lacked an "outcomes first" mentality. Those programs employed bottom-up approaches that focused on the project management and technology first, leaving clients without the proper outcomes that they needed to manage the business; in other words, they created an insights-to-action gap. BI pros should use a top-down approach that defines key performance indicators, metrics, and measures that support the business' goals and objectives. They must resist the temptation to address technology and data needs before the business requirements.
The end of a quarter forces me to reflect on what I learned in regards to my coverage area: measurement and attribution. From customer insights (CI) pros and marketers, I saw an increased interest in advancing their measurement approaches. On the attribution front, there is an appetite to learn about specific methodologies, use cases, ongoing attribution management strategies, and attribution applications to marketing/media buys. On the vendor side, I saw more advancement in tools, approaches, and offline and mobile data integration. I predict attribution — and general consumer and marketing measurement — will continue to be a hot topic for marketers and CI professionals well into 2014. Specifically, I expect to see more attribution adoption and usage of attribution to measure customer purchase paths and to learn more about customer behaviors and motivations.
In the meantime, let me recap the Q3 2013 measurement takeaways:
Let's face it, IT often suffers from a bad reputation. And in many cases it's well deserved. Over the years many IT leaders attempted to change IT's reputation by empowering other departments to dictate what IT should be doing — and in the process they became order-takers. And the portfolio of projects from well-meaning business leaders mushroomed. To cope with the overwhelming demand, IT established rigorous process around governance, forming committees with the power to determine what IT works on. And almost inevitably, many of these committees are bogged down by politics — meaning IT is not always working on the right things — and at the same time slowing down the whole pace of change. No wonder then that many people across the business spectrum view their own IT group as a slow, unresponsive impediment to getting things done.
But CIOs the world over are actively engaged with their leadership teams in changing IT's reputation. The goal for these CIOs is to shift IT from order-taker to business-partner, helping shape future business strategy and using technology to increase the value their organization brings to the end customers of the business.
This transition is not easy. Nor is it guaranteed to work. Sometimes an IT organization's employees are simply unwilling or unable to embrace the change. Sometimes the reputation of IT is so sullied that nothing short of a cold-reboot will work (organizations going down this route will start by outsourcing all of IT, then they gradually hire back key skills needed to derive more effective business outcomes).
Market conditions are changing quickly; firms need to make the best possible business decisions at the right time and base them on timely, accurate, and relevant information from business intelligence (BI) solutions. The repercussions of not handling BI change well are especially painful and may include lost revenue, lower staff morale and productivity, continued proliferation of shadow IT BI applications, and unwanted employee departures. Ineffective change management often lies in the process of preparing the people affected by change rather than in planning the technology implementation. Firms that fail to prepare employees for enterprise BI change early enough or well enough will be left behind. They need to implement a multifaceted series of activities ranging from management communication about why change is needed to in-depth, role-appropriate employee training.
Why change management is so critical? Most strategic business events, like mergers, are high-risk initiatives involving major changes over two or more years; others, such as restructuring, must be implemented in six months. In the case of BI, some changes might need to happen within a few weeks or even days. All changes will lead to either achieving or failing to achieve a business result. There are seven major categories of business and organizational change:
Business process changes
New technology implementations
Changes to business process outsourcing or IT sourcing
The data shows that 70% of corporate change efforts either totally fail, have lukewarm results, or the change never becomes an integral part of the company culture. As I talk to clients about their change efforts, what’s worked and what hasn’t, some clear patterns emerge.
Change is not an event — it’s a process. You make plans for the executive to announce the change to employees. The executive talks about why it’s important for the company to make the change, what the change will look like, and the assistance the company will provide employees during this transformation process. The executive responds to employee questions and recommends that employees discuss any additional questions with their managers. A thoughtful speech, well delivered with empathy around challenges of change . . . it’s good, but it’s not enough. The executives have been thinking about and planning this transformation for weeks or months and know it well. The employees are hearing about the change for the first time, in this hour-long, all-hands company presentation. Anxiety, shock, and fear are typical reactions. Rather than this one-time announcement, make sure executives explain that today’s meeting is the first of many that will be held periodically using different media (web, in-person, email, social network, etc.) to provide updates and answer questions. Remember, half the audience may have heard nothing beyond the statement that major change is going to happen. Fear set in and they began to think about how this change will affect them.
Chris and I recently published a report describing how to build risk and compliance principles into your company’s corporate culture. As we worked to finalize, edit, and publish the report, a flurry of new corporate scandals emerged, all related to this topic.
Here are just a few of them:
Wal-Mart executives accused of trying to hush up bribery cases in Mexico (article here).
A whistleblower accuses Infosys of engaging in a systematic practice of visa fraud (article here).
A former Goldman Sachs employee writes an op-ed for the New York Times blasting the company’s ethics (article here).
JP Morgan suffers a $2 billion trading loss due to “poorly monitored” trades (article here).
Think of a medieval fortress: It was originally used for a small army, it has walls nine meters thick, and it’s surrounded by buildings hundreds of years old. Upon entering, you are confronted with the concept of eternity.
This fortress is located in the smallest state on earth — though it is also perhaps the best-known state in the world. The business housed within the fortress is what many might classify as a SME but with with complexity of a large enterprise, holy but busy, centralized but truly global — its work spans hundreds of countries with hundreds of currencies and hundreds of languages — and it serves very special and demanding clients.
Have a clue yet of where we are?
Zoom on Italy, then zoom on Rome, then zoom on Vatican City, and you can’t miss the round tower (Torrione Sisto V) where the Vatican Bank, or Istituto per le Opere di Religione (IOR ), is located. You won’t be allowed in if you are not a client, an employee, or part of a religious congregation. Change comes hard to institutions this steeped in tradition. To give you a clue, IOR’s previous managing director spent his entire career at IOR — 60 years — and retired at the age of 80. We all know it’s the soft and cultural aspects of transformation that are the hardest part for any organization.
Nevertheless, IOR has been going through a major change since 2008, working to replace its legacy IT system with a modern BT one. The new BT system brings more flexibility for the business, richer business functionality, and greater integration and development capabilities. Enabling fast change is the key driver for IOR’s IT transformation program from IT into BT.