|By Emily Burns||
|November 30, 2012 02:00 PM EST||
Efficiency may be the most commonly used term in enterprise software marketing - that or "ensure." And not without reason - efficiency is one of the key value propositions of most enterprise software, from collaboration tools, to productivity tools, to integration tools and beyond. At a certain point though, the gains to be achieved from efficiency become smaller and smaller and of lesser and lesser business significance.
This is resulting in a shift in focus from efficiency to effectiveness. At times, these goals are twin, but in many cases, they are not - the most effective allocation of resources may not be the most efficient - at least in the short-term. Managing an organization with an eye toward effectiveness can be a challenge, because business metrics are often tied to processes and other types of "discrete" pieces of work, and how quickly/efficiently they are completed. As a result, when an organization makes the shift to managing for effectiveness rather than efficiency, the metrics used to evaluate success typically have to be "leveled-up," that is, taken up to the level that really matters to the business. An example of this leveling up occurred several years back when customer service organizations changed their focus from shortening call times to increasing the rate of first call resolution. Resolving a customer issue on the first call may result in increasing the length of the call, but over the long term it is a more effective approach, because it may result in a shorter overall expenditure of the Customer Service Representatives' aggregated time, and will certainly result in more satisfied customers.
Operationalizing this "leveling-up" is not an easy task. Most of the greatest challenges associated with doing so relate to data. First, organizations must have an idea that their current efficiency-based metrics are not serving them well. The only way to know that your current practices are ill-serving you is to capture data to make that point. In the CSR example above, that means being able to find out that a customer has called multiple times. But the way that calls are typically handled, a case is created for each one, meaning that the data doesn't tell a story of a customer calling multiple times and taking the time of many different CSRs; instead, the data tells of ten individual calls, each of which lasted three minutes. The complexity of the problem is actually greater than this, because what happens more often than not in such cases is that a customer will try to resolve the problem by contacting the organization through multiple different channels - phone, Web, email, chat. Because the data is so often fragmented, organizations will typically find out about such broken practices through a series of irate letters and phone calls, or in the worst case scenario, in a drop-off in customers. Whatever the means of notification, at some point it becomes clear to the organization that they not only have a problem of misaligned incentives, but also a data problem. They then turn to the data to understand what has been going on in their organization and how to manage more effectively.
The story likely can be pieced together from the data, but the organization must still make sure they are asking the right questions - if "number of cold calls made" is not the right metric, what is? Once the right questions have been identified, then it's time to turn to the data. Because in most organizations the data to be captured was not set up with these higher-level goals in mind, getting the right answer from the data requires some work. The data across these various systems must be integrated and federated - all of the necessary data must be extracted from the various systems inside and out of the organization and loosely coupled so that the data is telling the whole story. It also requires cleansing the data and rationalizing it such that data about the same thing being captured in different systems is in sync.
It may be that even after having all of the data rationalized and accessible, the crucial data needed to manage the business more effectively is not currently being captured. This is a relatively small problem, with practically everything digitized and virtualized, there is very likely a way to capture the data an organization seeks. A common scenario is that the data is being captured, but in an off-premise cloud-based application or in a partner's application or it may be that the data is embedded in the activities carried out on social networks. In all of these cases, new technology makes the data accessible and manageable. As a result, so, too, are the answers to the real business questions of how to manage the business more effectively.
Data integration tools make it possible to integrate and federate data from cloud-based applications with on-premise systems, to incorporated data from third parties. The ability to use Hadoop MapReduce to take in and manage unprecedented volumes of data from social networks and other non-traditional sources makes it possible to truly have, manage and analyze all of your data. New social MDM technology means that you can tap into the data embedded in social interactions on social networks and use this to create an even more fully fleshed-out golden record for your customers.
In truth, it is the gains we have made in efficiency, in finding ever-more efficient ways to access, store and analyze data that make this turn towards effectiveness possible. Without being able to do all of the above in a time- and cost-efficient manner, it is not possible to use the data to manage more effectively.
In many ways, this is what the hype about Big Data is all about. The unarticulated and implicit excitement about Big Data is really about being able to take advantage of the data in which we are all awash and use it to manage our organizations more effectively than ever before. Managing for effectiveness looks different in every industry. In retail, managing for effectiveness is understanding customers - catering to them when, where, how and with what they want. In pharma, managing for effectiveness is limiting physician wash out, getting more clinical trial data more quickly, and being able to complete or pull the plug on trials faster based on the results of that data. In every industry, managing for effectiveness means using the power of data to make the best business decisions possible, getting a true return on data.
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
May. 4, 2016 07:00 AM EDT Reads: 1,039
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
May. 4, 2016 06:00 AM EDT Reads: 1,247
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
May. 4, 2016 06:00 AM EDT Reads: 946
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
May. 4, 2016 03:45 AM EDT Reads: 2,033
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
May. 4, 2016 02:00 AM EDT Reads: 664
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
May. 4, 2016 01:00 AM EDT Reads: 579
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
May. 4, 2016 01:00 AM EDT Reads: 1,097
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
May. 4, 2016 12:45 AM EDT Reads: 390
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
May. 3, 2016 08:45 PM EDT Reads: 2,211
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
May. 3, 2016 08:45 PM EDT Reads: 1,001
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
May. 3, 2016 08:15 PM EDT Reads: 1,577
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
May. 3, 2016 07:30 PM EDT Reads: 1,928
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
May. 3, 2016 05:45 PM EDT Reads: 1,637
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
May. 3, 2016 04:45 PM EDT Reads: 1,140
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
May. 3, 2016 04:45 PM EDT Reads: 936
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
May. 3, 2016 03:30 PM EDT Reads: 409
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.
May. 3, 2016 12:15 PM EDT Reads: 1,604
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
May. 3, 2016 12:00 PM EDT Reads: 1,384
With DevOps becoming more well-known and established practice in nearly every industry that delivers software, it is important to continually reassess its efficacy. This week’s top 10 includes a discussion on how the quick uptake of DevOps adoption in the enterprise has posed some serious challenges. Additionally, organizations who have taken the DevOps plunge must find ways to find, hire and keep their DevOps talent in order to keep the machine running smoothly.
May. 3, 2016 06:30 AM EDT Reads: 1,504
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
May. 3, 2016 03:00 AM EDT Reads: 1,454