One Drupal platform, multiple government products

This session is for project managers, product managers, content strategists and other technologists interested in taking product-centric approach to government digital services.

In early 2019 #Drupal was introduced into a robust product ecosystem, in which dozens of product teams design and deliver Veteran-centered digital tools and services, with outcome-oriented approaches.

Drupal’s role was modest at first, as the new home for content powering a couple dozen pages about health care benefits for #Veterans.

Since then, CMS has expanded to house ten distinct products, each with their own editor base, outcome orientation, Veteran-centered design, and unique governance needs. CMS-supported products range from homepage, to the marketing-oriented Campaign Landing Pages, to content about the VHA health system, the largest health care delivery system in the United States. And there are more products on the way.

In this session, we’ll describe some successes and failures we’ve had in taking this product-centric approach to building with Drupal in a broader product ecosystem at the VA’s Office of the CTO - Digital Experience. We’ll dig into:

* Managing the tension between “Core” platform features vs product specificity, in the content model and in the rest of the application
* #Enterprise governance tools and processes
* What we’ve learned about optimal (and dysfunctional!) team structures and relationships
* Approaches to customer service (help desk, training, and product documentation)
* How we’ve made make Drupal “self-aware” of its product orientation, with a layer that helps teams to leverage a product orientation throughout the application.

Attendees can expect to learn more about what to do–and what not to do–when taking a product-oriented approach to building with Drupal.

🎤 Presenter(s): Kevin Walsh, Rachel Kauff

Drupal is a registered trademark of Dries Buytaert.