Strategic advice to leverage new technologies
Technology is at the heart of nearly every enterprise, enabling new business models and strategies, and serving as the catalyst to industry convergence. Leveraging the right technology can improve business outcomes, providing intelligence and insights that help you make more informed and accurate decisions. From finding patterns in data through data science, to curating relevant insights with data analytics, to the predictive abilities and innumerable applications of AI, to solving challenging business problems with ML, NLP, and knowledge graphs, technology has brought decision-making to a more intelligent level. Keep pace with the technology trends, opportunities, applications, and real-world use cases that will move your organization closer to its transformation and business goals.
Insight
I was talking recently with a colleague who is involved in a business performance management initiative. The subject quickly turned to one of the most important challenges associated with such an effort: identifying key performance indicators (KPIs). This Advisor summarizes what we discussed.
Basically, there are a number of techniques useful for identifying KPIs for business performance management efforts. But the reality is that, more than likely, organizations are going to have to utilize multiple techniques.
I was talking recently with a colleague who is involved in a business performance management initiative. The subject quickly turned to one of the most important challenges associated with such an effort: identifying key performance indicators (KPIs). This Advisor summarizes what we discussed.
Basically, there are a number of techniques useful for identifying KPIs for business performance management efforts. But the reality is that, more than likely, organizations are going to have to utilize multiple techniques.
In this, the last installment of my three-part series on LoTech -- HiFi (for parts one and two, see "Part 1: The Evolution of Story Cards and User Stories," 23 March 2006, and "Part 2: The Cost of Tracking Tools," 11 May 2006), we will look at ways to take metrics beyond "how fast" or "how much."
A friend of mine recently returned from a software development conference where he picked up an introductory copy of a business rules management system (BRMS) development tool. I asked him what he planned to do with it, and he said he had no plans, really, because he "didn't want to learn some new development language." Basically, he said he couldn't see writing rules to create applications he could more easily develop just by writing code.
Although everyone's known that it's been in the works for some time now, Microsoft last week finally revealed its plans for its upcoming on-demand CRM offering: "Microsoft Dynamics CRM Live."
One important fact to keep in mind when considering Microsoft's planned entry into the CRM software as a service (SaaS) market, is that it will not become generally available until sometime in mid-2007 for North America, with other locales to follow.
Given the increasing use of mobile technology in many corporations, how can we weave that technology into a future IT department architecture that will prove resilient over the years to come while still addressing the immediacy of making a difference to the bottom line today?
In April 2006, Cutter Consortium conducted a survey that asked 106 end-user organizations about their use of open source business intelligence (BI) tools. The goal was to determine the degree to which companies are using or planning to use open source BI tools. In particular, the survey was designed to identify the issues and trends encountered in these efforts and to provide statistics useful for benchmarking and measuring your own organization's use of open source BI tools.
I always enjoy the annual Cutter Summit conference. At this wonderful event, I have a chance to talk to a lot of old friends and Cutter clients and, most important, I always meet and learn from people who I haven't heard from before. This year was no exception: there were great talks about wikis, open source, and technology roadmapping planning. However, there was also something I find distressing: there was still an inordinate amount of discussion about code and coding.