customize

You are here

Dries Buytaert: The evolution of Acquia's product strategy

Error message

  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.
  • You must enable the PECL memcached or memcache extension to use memcache.inc.

Four months ago, I shared that Acquia was on the verge of a shift equivalent to the decision to launch Acquia Fields and Drupal Gardens in 2008. As we entered Acquia's second decade, we outlined a goal to move from content management to data-driven customer journeys. Today, Acquia announced two new products that support this mission: Acquia Journey and Acquia Digital Asset Manager (DAM).

Last year on my blog, I shared a video that demonstrated what is possible with cross-channel user experiences and Drupal. We showed a sample supermarket chain called Gourmet Market. Gourmet Market wants its customers to not only shop online using its website, but to also use Amazon Echo or push notifications to do business with them. The Gourmet Market prototype showed an omnichannel customer experience that is both online and offline, in store and at home, and across multiple digital touchpoints. The Gourmet Market demo video was real, but required manual development and lacked easy customization. Today, the launch of Acquia Journey and Acquia DAM makes building these kind of customer experiences a lot easier. It marks an important milestone in Acquia's history, as it will accelerate our transition from content management to data-driven customer journeys.

A continuous journey across multiple digital touch points and devices

Introducing Acquia Journey

I've written a great deal about the Big Reverse of the Web, which describes the transition from "pull-based" delivery of the web, meaning we visit websites, to a "push-based" delivery, meaning the web comes to us. The Big Reverse forces a major re-architecture of the web to bring the right information, to the right person, at the right time, in the right context.

The Big Reserve also ushers in the shift from B2C to B2One, where organizations develop a one-to-one relationship with their customers, and contextual and personalized interactions are the norm. In the future, every organization will have to rethink how it interacts with customers.

Successfully delivering a B2One experience requires an understanding of your user's journey and matching the right information or service to the user's context. This alone is no easy feat, and many marketers and other digital experience builders often get frustrated with the challenge of rebuilding customer experiences. For example, although organizations can create brilliant campaigns and high-value content, it's difficult to effectively disseminate marketing efforts across multiple channels. When channels, data and marketing software act in different silos, it's nearly impossible to build a seamless customer experience. The inability to connect customer profiles and journey maps with various marketing tools can result in unsatisfied customers, failed conversion rates, and unrealized growth.

An animation showing Acquia's journey building solution

Acquia Journey delivers on this challenge by enabling marketers to build data-driven customer journeys. It allows marketers to easily map, assemble, orchestrate and manage customer experiences like the one we showed in our Gourmet Market prototype.

It's somewhat difficult to explain Acquia Journey in words — probably similar to trying to explain what a content management system does to someone who has never used one before. Acquia Journey provides a single interface to define and evaluate customer journeys across multiple interaction points. It combines a flowchart-style journey mapping tool with unified customer profiles and an automated decision engine. Rules-based triggers and logic select and deliver the best-next action for engaging customers.

One of the strengths of Acquia Journey is that it integrates many different technologies, from marketing and advertising technologies to CRM tools and commerce platforms. This makes it possible to quickly assemble powerful and complex customer journeys.

Implementing getBestNextExperience() creates both customer and business value

Acquia Journey will simplify how organizations deliver the "best next experience" for the customer. Providing users with the experience they not only want, but expect will increase conversion rates, grow brand awareness, and accelerate revenue. The ability for organizations to build more relevant user experiences not only aligns with our customers' needs but will enable them to make the biggest impact possible for their customers.

Acquia's evolving product offering also puts control of user data and experience back in the hands of the organization, instead of walled gardens. This is a step toward uniting the Open Web.

Introducing Acquia Digital Asset Manager (DAM)

Digital asset management systems have been around for a long time, and were originally hosted through on-premise servers. Today, most organizations have abandoned on-premise or do-it-yourself DAM solutions. After listening to our customers, it became clear that large organizations are seeking a digital asset management solution that centralizes control of creative assets for the entire company.

Many organizations lack a single-source of truth when it comes to managing digital assets. This challenge has been amplified as the number of assets has rapidly increased in a world with more devices, more channels, more campaigns, and more personalized and contextualized experiences. Acquia DAM provides a centralized repository for managing all rich media assets, including photos, videos, PDFs, and other corporate documents. Creative and marketing teams can upload and manage files in Acquia DAM, which can then be shared across the organization. Graphic designers, marketers and web managers all have a hand in translating creative concepts into experiences for their customers. With Acquia DAM, every team can rely on one dedicated application to gather requirements, share drafts, consolidate feedback and collect approvals for high-value marketing assets.

On top of Drupal's asset and media management capabilities, Acquia DAM provides various specialized functionality, such as automatic transcoding of assets upon download, image and video mark-up during approval workflows, and automated tagging for images using machine learning and image recognition.

A screenshot of Acquia's Digital Asset Management solution
By using a drag-and-drop interface on Acquia DAM, employees can easily publish approved assets in addition to searching the repository for what they need.

Acquia DAM seamlessly integrates with both Drupal 7 and Drupal 8 (using Drupal's "media entities"). In addition to Drupal, Acquia DAM is built to integrate with the entirety of the Acquia Platform. This includes Acquia Lift and Acquia Journey, which means that any asset managed in the Acquia DAM repository can be utilized to create personalized experiences across multiple Drupal sites. Additionally, through a REST API, Acquia DAM can also be integrated with other marketing technologies. For example, Acquia DAM supports designers with a plug in to Adobe Creative Cloud, which integrates with Photoshop, InDesign and Illustrator.

Acquia's roadmap to data-driven customer journeys

Some of the most important market trends in digital for 2017

Throughout Acquia's first decade, we've been primarily focused on providing our customers with the tools and services necessary to scale and succeed with content management. We've been very successful with helping our customers scale and manage Drupal and cloud solutions. Drupal will remain a critical component to our customer's success, and we will continue to honor our history as committed supporters of open source, in addition to investing in Drupal's future.

However, many of our customers need more than content management to be digital winners. The ability to orchestrate customer experiences using content, user data, decisioning systems, analytics and more will be essential to an organization's success in the future. Acquia Journey and Acquia DAM will remove the complexity from how organizations build modern digital experiences and customer journeys. We believe that expanding our platform will be good not only for Acquia, but for our partners, the Drupal community, and our customers.

Acquia's product strategy for 2017 and beyond

Source: 
https://dri.es/the-evolution-of-acquia-product-strategy