January 26th, 2010 was a black day for the enterprise software business.Late yesterday, Oracle launched a lawsuit against independent support provider (ISP) Rimini Street, alleging 'massive theft' of its intellectual property. Industry analysts had been expecting something like this - Oracle is already suing Rimini Street's predecessor TomorrowNow and was clearly worried that a competitive market would force it to cut the price of its hugely profitable maintenance offering.
One of the great things we can do with our Consumer Technographics data is compare user behavior and technology adoption in different international markets. Our recently published report The Global eCommerce Adoption Cycle uses data from four continents to provide a snapshot of eCommerce around the globe.
With its acquisition of BPM-software leader Savvion, Progress Software has taken a step closer to providing a full line of enterprise middleware. Progress has operated as a supermarket of middleware brands addressing mostly specialized needs, but now is creating broader enterprise application platforms out of its separate middleware brands [Figure 1.].
Many of my clients have asked, "How should I use Twitter for customer service?" There are many applications that are adding Twitter as part of the contact center apps. But today I'd like to talk about the basics of using Twitter. I spoke with Anne Wood, the Head of Knowledge Management at Carphone Warehouse to learn about how they entered into Twitterland.
I’ve met many CIOs, all with their own unique challenges and approaches to overcome them. But despite their differences, all CIOs ask me the same question: “what is the next big technology trend that I should look out for?”
It’s a tough question — not because there is a shortage of emerging tech trends out there. The tough part is whittling down all of trends to the really big ones — I mean the ones that could really change the way we do business. So all through 2009, my answer was: 1) consumerization of IT (what we at Forrester refer to as Groundswell), 2) lean IT, and 3) cloud computing. For those interested, you can still view the Three Tech Movements CIOs Should Know webinar I did with colleagues Ted Schadler and John Rymer late last year.
Last week Dr. Dobb's published an article I penned in December on "What Developers Think". I won't rehash the thrust of that piece here other than to reaffirm the growing trend of technology populism in development shops - where tech-savvy workers make their own decisions about what technologies to use.
Slowly but surely, with lots of criticism and skepticism, the business intelligence (BI) software-as-a-service (SaaS) market is gaining ground. It's a road full of peril — at least two BI SaaS startups have failed this year — but what software market segment has not seen its share of failures? Although I do not see a stampede to replace traditional BI applications with SaaS alternatives in the near future, BI SaaS does have a few legitimate use cases even today, such as complementary BI, in coexistence with traditional BI, BI workspaces, and BI for small and some midsize businesses.
In our latest BI SaaS research report we recommend the following structured approach to see if BI SaaS is right for you and if you are ready for BI SaaS:
Map your BI requirements and IT culture to one of five BI SaaS use cases
Evaluate and consider scenarios where BI SaaS may be a right or wrong fit for you
Select the BI SaaS vendor that fits your business, technical, and operational requirements, including your tolerance for risk
First we identified 5 following BI SaaS use cases.
Coexistence case: on-premises BI complemented with SaaS BI in enterprises
SaaS-centric case in enterprises: main BI application in enterprises committed to SaaS
SaaS-centric case in midmarket: main BI application in midsized businesses
Elasticity case: BI for companies with strong variations in activity from season to season
Power user flexibility case: BI workspaces are often considered necessary by power analysts
One of the key themes I saw popping up in 2009 was the need for market researchers to communicate insights instead of information (or even worse: data). I've been at a number of events where this was discussed and I followed multiple discussions in market research groups like for example Next Generation Market Research (NGMR) on LinkedIn. Personally I added to this discussion by publishing a report called The Marketing Of Market Research - Successful Communication Builds Influence.
The general consensus is that market researchers should stay away from elaborating on the research methodology and presenting research results with many data heavy slides and graphics. Instead, they should act more like consultants: produce a presentation that reads like an executive summary (maximum 20 slides or so) and starts with the recommendations. The presentation should show the key insights gained from the project, cover how these results tie back to business objectives, include alternative scenarios and advice on possible next steps.
However, another consensus from the conversations is that not all market researchers are equally well equipped to deliver such a presentation, where they're asked to translate data into insights, come up with action items, and tell a story. Most participants in the discussions agreed with the statement that the majority of market researchers still feels most comfortable when they present research outcomes (aka numbers).
NetApp is an industry-leading provider of storage and data management solutions. It has a presence in more than 100 countries-- thousands of customers and a network of more than 2,200 partners-- and a culture of innovation, technology leadership, and customer success. The company was seeking to build higher brand awareness and deeper engagement with employees, customers, and partners and decided to deploy both customer and employee communities.