Conference archive · LavaCon 2017
Bring a content problem worth talking about.
Bluestream’s LavaCon 2017 notice invited colleagues and customers to discuss their content challenges and highlighted the conference’s focus on business problems, customer success, and professional community.
The 2017 announcement
Archive · Published 30 August 2017. Event invitations and roles reflect the original publication period; the event has passed.
Bluestream looks forward to meeting up with old colleagues and customers and to making new acquaintances as well. We would love to talk to you at LavaCon. Please come by our table in the Exhibit Hall and tell us about your content challenges!
The LavaCon mission is, “To help organizations decrease costs and increase revenue by solving content-related business problems, to give content professionals the skills they need to better enable customer success, to create a community in which content professionals can collaborate and advance the field as a whole.”
You can learn more about LavaCon on the website LavaCon.org.
Editorial context · October 2026
The invitation at the heart of the notice
This brief announcement was an invitation to a conversation at Bluestream’s exhibit table. The LavaCon mission statement connected content-related business problems with customer success and professional community.
Make the conversation specific
Describe the bottleneck
Bring one example of work that takes too long, repeats unnecessarily, or leaves ownership unclear. Explain what happens before and after the problem.
Bring a real sample
Use a representative topic, publication, or review request. A concrete artifact makes it easier to discuss structure, reuse, release, and delivery without relying on broad claims.
Define a useful next step
End with one question to test, one process to map, or one sample to examine. Record what evidence would make the next conversation more productive.
Connect the content issue to its consequence
A duplicated procedure matters because someone must maintain each copy and check that they still agree. An unclear approval step matters because an author cannot tell whether the publication is ready. Describe the consequence in your own workflow before asking whether a new tool will help. That gives the discussion a practical boundary and keeps an attractive feature from becoming the answer to an undefined problem.
A reusable conversation brief
Write four short lines before a conference discussion: the content you produce, the people who depend on it, the handoff that causes trouble, and the result you need to improve. Add any constraint that a proposed solution must respect. A short brief helps a new contact understand the problem before moving to possible solutions.
Archive source: LavaCon Lineup, 30 August 2017.