Session archive · CMS/DITA North America 2018
When the product changes, the content operation changes with it.
The announced 2018 Denver session focused on DITA infrastructure for changing content needs. Guidewire’s Neeraj Bhatia and Bluestream’s Nenad Furtula would discuss tools, processes, and a culture of change.
Themes described in the 2018 session abstract
The 2018 DITA infrastructure session
Archive · Published 6 March 2018. Event invitations and roles reflect the original publication period; the event has passed.
At the CMS/DITA North America conference on April 24 in Denver, Colorado—Nenad Furtula VP of Sales and Marketing at Bluestream is pleased to be co-presenting a talk with Neeraj Bhatia, the Director of Technical Publications at Guidewire Software.
Be sure to join them for their exciting presentation, “Thriving in an Environment of Change,”
The enterprise software landscape is changing—from monolithic on-premise products to cloud-based micro-services, from one-size-fits-all products to custom solutions for different markets and customer segments, from annual releases to weekly updates, and from closed to open, integrated systems.
What imperatives do these changes introduce for our content, toolset, architecture, and delivery options? How do technical communication teams adapt and respond to this rapidly changing landscape, and to continuously evolving user expectations?
Join Guidewire Software and Bluestream Solutions as they share their experience of introducing new tools, new processes, and a culture of change in a growing organization.
Learn how an organization and a CCMS vendor collaborated to implement new DITA infrastructure to support evolving content needs and user expectations: CMS/DITA North America 2018
The announced speakers
Neeraj Bhatia is the Director of Technical Publications at Guidewire Software. He worked in Advertising for four years before moving to technical writing 19 years ago. He has written and managed documentation for highly technical software products, and has built and led global teams at Veritas Software and Symantec Corporation. At Guidewire Software, he leads a distributed team working on a mix of on-premise and cloud products, and is driving several changes, including the transition to DITA.
Nenad Furtula is partner and a VP of Sales and Marketing at Bluestream Database Software. Nenad has been working with XML and bringing XML related products to market for over 15 years. Currently his primary professional interest lies in building and socializing a DITA-enabled component content management system called XDocs. Nenad holds a BBA from Capillano University and MSc (Computer Science) from Dalhousie University.
Editorial context · October 2026
The session as announced
The abstract linked changing products to content decisions. As release cycles and delivery models changed, teams also needed to consider users’ evolving expectations. Therefore, the DITA infrastructure discussion extended beyond the choice of tools. The speaker biographies reflect roles at the time.
Translate a product change into a content decision
| Change to investigate | Content decision to make |
|---|---|
| More frequent updates | For example, define the smallest content unit the team can review and release safely. |
| Different customer configurations | Decide how the team will identify which guidance applies to each supported context. |
| Distributed contributors | Instead of assuming everyone shares the same working context, make ownership and the review handoff explicit. |
| More delivery destinations | Identify the common source controls. Then decide which checks the team must repeat for each output. |
Start with one release boundary
Start with one product area to keep the change initiative manageable. First, follow a single update from engineering information to customer-facing content. Note where people wait and which facts they enter more than once. Next, check how the team confirms that the documentation matches the product. Finally, use that evidence to choose the next improvement: the process, the content model, or the tool configuration.
Archive source: Thriving in an Environment of Change, 6 March 2018.