Podcast: Document Engineering, Interview with Robert Glushko
Duration: 15 min.
In this podcast, Dr. Robert Glushko, a professor at UC Berkeley's School of Information, explains the concept of Document Engineering -- the process of developing document models to make information sharing, reuse, or syndication more efficient.
Glushko gives several examples of document engineering, such as creating a calendar event model that allows an event to by shared across numerous calendars. Or a syllabus document model, which allows students to pull specific data from syllabi across the university in unique ways.
The document models Glushko and his students create help people embrace best practices, rather than merely encoding bad habits. Even the founders of Youtube.com learned principles of information organization and retrieval from Berkeley's School of Information.
In this podcast Glushko also talks about the notion of the transaction. He says the user experience isn't based on how easy a website is to use, or how clear certain labels are. What matters most is the transaction -- whether the merchant fulfilled a promise to the customer, and how smooth and efficient the fulfillment was.
Good transactions are enabled by a plethora of document choreography going on in the background. Information designers make the information fit together well and contribute to successful transaction experiences.
For more information on Robert Glushko, document engineering, the the School of Information at Berkeley, see Robert Glushko's home page. You can also read Dr. Glushko's book on Document Engineering, or follow his blog, Doc or Die.
Here's a related post from Robert's blog about his keynote at Doc Train.
I'd Rather Be Writing Newsletter
Get new posts delivered straight to your inbox.
About Tom Johnson
I'm a technical writer based in the California San Francisco Bay area. In this blog, I write about topics related to technical communication — Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, academics, and more. I'm interested in , API documentation, visual communication, information architecture and findability, and more. If you're a technical writer of any kind (progressional, transitioning, student), be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.