Process to people: How content governance can power content teams

Content Strategy Seattle
Content Strategy Seattle
Public group


920 5th Ave Suite 1400 · Seattle, WA

How to find us

Address: 920 5th Ave #1400. When you enter the building, go up the stairs or escalators to the next floor and go up to floor 14.

Location image of event venue


Can't make it to Confab? We're thrilled to be able to offer a sneak preview of what will no doubt be a popular presentation by Blaine Kyllo. Blaine is joining us from beautiful Vancouver, BC, and we're delighted to be able to share this presentation with our Meetup group.

Content processes make sure that everyone involved with content, from stakeholders to subject matter experts to content creators, have a shared understanding of the work being done.

After facilitating workshops with numerous companies from different sectors, Blaine has discovered their ideal content processes are all similar – at least at a high level.

In this presentation, Blaine shares the suite of content process models for each phase of the content life cycle that can be used – immediately – by anyone, in any company, in any industry.

• How content processes can be created
• Why content processes are useful
• Specific content processes that have been developed for a variety of industry sectors
• A common suite of content processes that can be used by any content team, in any organization, to streamline operations

Speaker Bio

Blaine is a senior content strategist at Content Strategy Inc, where he focuses on enterprise content governance. His clients have included BC Hydro, Investors Group, and Pearson. He’s also structured content teams for other contexts and has become a master at streamlining complex content processes.

Before content strategy, Blaine worked as managing editor for a leading independent book publisher, as well as with a national telecommunications company, and a non-profit initiative.

He’s also an audio and print journalist.

Check out his recent article on the GatherContent blog: