Vigilante content is all the content created (and often distributed) by people who are not tasked with creating content. It’s the content that someone thinks up and then writes. And then publishes or emails or prints to hand out at a conference. In essence, it is unauthorized content. Vigilante content
We can no longer afford the costs of traditional, document-based content management in the pharmaceutical industry. We need pharma companies to prioritize content reuse and automation rather than manual, error-prone legacy processes. We do not need pharma companies wasting time creating redundant content. It is a waste of resources to
In January 2022, I received my Year in Review video from WW (formerly Weight Watchers). The video showed me some fun stats about my participation in the program in 2021. 191 days of tracking a meal in the WW app 114 non-starchy vegetables recorded 364 days of activity 4,714,339 steps
In The Unique Challenges of Pharma Content, we discuss challenges faced by pharmaceutical companies in the creation and management of content. Here is a short list: Takes too long to create, approve, and deliver content Cannot leverage or reuse content across documents and organizational silos Cannot manage the high volume
For centuries, humans have shared information through documents. We’ve used digital files, printed paper, illuminated manuscripts, parchment scrolls, and clay tablets. Regardless of form factor, a document has traditionally been created as a single monolithic entity, authored in the same format in which it was intended to be consumed. When
A question came up recently in a conversation about structured authoring and a migration into a component content management system: “If we’re not going to reuse this content, and it is always entirely unique, do we still need to chunk it into components?” The short answer is … it depends.
Buy this Book to learn exactly what it takes to deliver personalized experiences at scale.
Get exclusive access to Val’s thoughts and hand-picked content with our newsletter.
“*” indicates required fields