Most enterprises aren't fully exploiting real-time streaming data that flows from IoT devices and mobile, web, and enterprise apps. Streaming analytics is essential for real-time insights and bringing real-time context to apps. Don't dismiss streaming analytics as a form of "traditional analytics" use for postmortem analysis. Far from it — streaming analytics analyzes data right now, when it can be analyzed and put to good use to make applications of all kinds (including IoT) contextual and smarter. Forrester defines streaming analytics as:
Software that can filter, aggregate, enrich, and analyze a high throughput of data from multiple, disparate live data sources and in any data format to identify simple and complex patterns to provide applications with context to detect opportune situations, automate immediate actions, and dynamically adapt.
Forrester Wave™: Big Data Streaming Analytics, Q1 2016
To help enterprises understand what commercial and open source options are available, Rowan Curran and I evaluated 15 streaming analytics vendors using Forrester's Wave methodology. Forrester clients can read the full report to understand the market category and see the detailed criteria, scores, and ranking of the vendors. Here is a summary of the 15 vendors solutions we evaluated listed in alphabetical order:
Clients tell us they are resistant to SaaS because of SaaS vendors’ unwillingness to offer unlimited liability. Sound familiar? It’s time to stop holding SaaS vendors to a higher standard than the alternative. Consider this: In-house systems do not offer unlimited liability. Very few non-SaaS vendors offer unlimited liability.
Say what? You did get unlimited liability? If your vendor does offer unlimited liability, beware. Small vendors are all too happy to sign up for things in the contracts. But, it’s hard to get them to pay up in the event of a serious incident. More likely, you’ll end up spending a lot of time in court and find there’s no money for them to pay out. Be cautious when you see this because it rarely will do you much good and it may be a sign that the vendor is taking on deals that are unsustainable in other ways, too – which makes them a vendor viability concern.
What should you do? Instead of honing in on the legal language of liability, ask for some reasonable yet meaningful liability (such as 2 years’ worth of fees) and focus the rest of your energy on due diligence and pushing for transparency. Check out the vendor’s processes, policies, and third-party certifications. Approach this more as a risk assessment than a contract negotiation, working closely with your security and risk team (or partners). Also, look for signs of transparency. Leading SaaS vendors put out a lot of information about security, performance, and other key metrics. They foster a culture of openness and transparency.
Finally, keep in mind that a SaaS vendor will die off if they have a poor track record. That pressure generally keeps them more focused on delivering great service than a legal contract does.
This tends to be a contentious topic, and I’d love to hear perspectives and experiences.
BuzzFeed's supposed to be the media company that holds the answer to the media business's future in a post-banner world. While the media world is dying, BuzzFeed's been hiring, growing to new markets, winning new investment on high valuations and projecting hockey stick sales growth.
But worrying signals that BuzzFeed was struggling were confirmed in an article by Financial Times, which cited a miss on 2015's revenue target and a halving of 2016's target. To this, BuzzFeed's chairman said "There's nothing cratering in the industry. It's better than ever." Meanwhile, he offered no evidence to the contrary, reminding this analyst of:
Counter to Lerer's assurances and in line with FT's findings, there are some pretty good reasons BuzzFeed may be missing its numbers. I'll present them in true BuzzFeed listicle style (all gifs credited to giphy.com). Here goes:
1) BuzzFeed's tried to position itself and its expected revenue as a software play, but it's just....not.
The challenges of how to manage, ingest, store, analyze, and act upon data in the IoT are beginning to bear down on enterprises. The honeymoon talk of ‘billions and billions of devices’ is over and it’s time to get down to the dirt of how to generate value from all these connected devices. Streaming analytics platforms, already architected to handle IoT data as it streams into the data center, are being extended to deploy out to gateway devices (such as wireless access points) and even out to edge devices (such as manufacturing equipment) to extend the intelligence out to where data is generated and actions occur.
Forrester clients can read the full details of our analysis here and start the process of turning slow processes and weekly analytical batches into the immediate insights needed to support today’s dynamic business environment.
After a conversation with my colleague Lori Wizdo the other day about buyer journey mapping, she followed up by sharing the following cartoon – which I thought was perfect:
Perfect because it captured both our perspectives on the topic: Lori’s that buyer journeys are by their very nature hypothetical; and mine that you can never anticipate every buyer’s possible path to purchase.
This is not to say that buyer journey mapping is a futile exercise – or that the way to deal with its limitations is to ensure that your customers stay on the paths you’ve laid out for them, as appealing (and humorously absurd) as that reaction may be for all marketers.
As Lori pointed out in a recent blog post, you need to understand your buyer’s typical path to purchase to build an effective omnichannel marketing strategy that successfully engages with buyers at the right time with the right content through the right channel.
But be realistic in your goals and recognize that you will never be able to anticipate every possible buyer journey. When large companies with a wide range of solutions are documenting dozens, if not hundreds, of discrete paths to purchase, it’s too easy to get lost in the process and proceed well past the point of diminishing returns.
Facebook held its annual developer conference in San Francisco this week. Analysts at Forrester collectively fielded a lot of questions from the media, but most of them focused on bots and the Messenger platform. Here are my top takeaways from the event:
It's still early days for developer tools: Facebook approached F8 with a humble, honest tone and message about the state of its applications, platforms and tools for developers. Facebook didn't over promise. Every executive on the main stage to the breakouts in the "Hacker X" and "Hacker Y" pavilions offered an honest portrayal of where Facebook is today. Where is it? Facebook holds a very strong position in terms of total minutes of use and monthly active users across its various apps and platforms (e.g., Facebook, Whatsapp, Instagram, Facebook Messenger, Oculus, etc.), but they are just beginning to offer tools to developers. Developers of mobile apps want to borrow mobile moments on Facebook's apps/platforms because they don't own enough mobile moments themselves. Facebook is just in the earliest of stages of giving tools to these developers to help them borrow mobile moments effectively.
A regular inquiry request we get from clients is “Which approach should we use to build our mobile apps?” There are a lot of arguments made for either side of the web vs. native approaches and some compelling arguments as well for using cross-platform tools to deliver apps. Because it’s such a common discussion, we crafted a report that addresses this topic quite well in Native, Web, and Cross-platform Mobile Apps All Have Their Place.
Ultimately, from the report, “it’s not a question of either/or; it’s which approach best fits the app in question.” The app’s specific features and capabilities drive one aspect of the approach you’ll select; any flowchart you’ve seen on this topic deals with that directly. However, you’ll also have to consider other organizational and technical aspects as well. So, if you’re looking for an absolute answer to the question posed, it’s: “It depends!”
So, what about cross-platform tools? Cross platform tools muddy this conversation a bit as platforms generally deliver native apps or web apps and many can deliver both. The selection of a cross-platform tool is driven by the same questions you’d ask about a native or web app: what are you trying to accomplish with the app coupled with specific questions about what capabilities and benefits the platform provides in key areas you’ll be exercising.
Today, Microsoft's Terry Myerson announced the new strategy for Windows in the classroom. Windows 10 -- which is now Windows-as-a-service, with periodic updates delivered from the cloud -- will see a big feature update this summer with the Windows Anniversary Update, announced a few weeks ago at the BUILD developer conference. Now we're learning about the education-specific features that will take on Chromebooks.
It's no secret that Google's Chromebooks have taken the education market by storm; they now constitute more than half of shipments of new devices sold to U.S. schools. Some schools are even re-imaging old Windows PCs into Chromebooks. As a result, both Apple and Microsoft have seen their positions in the educational market slide south over the past four years.
Why does this matter? Well, for the obvious device sales implications, of course. But it's part of a longer-term customer relationship issue, too: If young people grow up not knowing Windows, will they ever care about the platform? Tomorrow's Windows customers could be shaped in today's classroom... or tomorrow's Chromebook customers could be.
For schools, Windows Anniversary Update will address key issues in education:
Our new report, "How To Spur Collaboration Across Your Customer Experience Ecosystem," grapples with the enablement question from a technology standpoint. Why focus on technology? The people who constitute a CX ecosystems are never entirely colocated, yet they must share and discuss business artifacts (e.g., marketing collateral, contracts, designs) in order to make decisions that affect customers' experience. This problem requires a technical solution.
If you’re unfamiliar with it, F8 is a two-day event focused on developers, a crucial part of Facebook’s ecosystem. I was fortunate enough to attend, and though I have many takeaways, which I'll discuss in upcoming posts, the one that surprises me most is Mark Zuckerberg himself.
Zuckerberg’s rousing introductory keynote set the foundation for the two-day event. He kicked things off with an ambitious 10-year road map.
Let’s be honest: The most we see from companies today is a three-year road map or, for the adventurous, a five-year road map. Yes, Zuckerberg caught our attention once he took the stage; however, when the 10-year road map slide appeared, a new type of energy filled the venue. As a result, I couldn’t help but take a holistic look at his approach and name it “Zuckerberg 101.” For F8, this approach consisted of a foundational message, expectation setting, and an appeal to the audience. Take note marketers because this approach is one we can all use to foster connections with our audiences. It also helps us understand Facebook’s long-term strategy, along with its near- and long-term investments. Zuckerberg 101 consists of:
A foundational message. F8 2016's message is that Facebook’s mission of connecting everyone is everything. The 10-year road map echoes this vision with key milestones that aim to provide everyone with the power to share. All subsequent presentations reflected this theme throughout the event, creating a consistent message. Key takeaway: If you're trying to change the world (or anything else), make sure everyone knows why you’re in it to win it.