In a recent workshop with Jeff Eaton of Lullabot, he was sharing his thoughts on "Modeling rich narrative content" and how structured content creates better experiences for readers, gives more (of the right kind of) control to authors, and helps content extend its reach. These concepts have their roots in the content strategy conversations about "Create once, publish everywhere", Nimble content, and Adaptive content.
During the section of the workshop on content modeling, Jeff was walking through the steps of "breaking down re-usable components, and figuring out how to work with them." The first step totally surprised me. He said that for each content component we're designing we need to ask: What's its job?.
Now, I realize that asking this kind of question should be obvious to a content strategist like you or me since we're constantly asking "why?" and trying to understand the purpose of each piece of content. So why was I so surprised and excited by this?
Jobs are simple and familiar
The language that Jeff Eaton used that really clicked: job. It's simple and it captures so much of what I'm often struggling to explain to people. Anyone can relate to a job and how to describe it. That's the beauty of it.
Ask Wikipedia what a job is and you get this:
A person's job is their role in society.
If you take this snippet and apply it to content modeling you might get something like this:
A content component's job is its role on the website.
This simple idea can be easily incorporated into your modeling activities. To describe a content component's job, start with this simple MadLib.
The job of a __________ is to __________.
The first blank is the content component and the second blank is the job description.
Example: the job of a staff bio
Applying the MadLib format, from above, to a Habanero staff bio, you get something like this:
The job of a ...staff bio... is to ...promote a staff member's expertise and personality to (potential) clients.
You could stop there and have defined a clear purpose for this content component on the website. You could then use this "job description" throughout a design project, during training, during an audit, etc. to have conversations about the value and intent of the staff bio component.
Depending on your needs, you could take it a step further and describe the jobs of the smaller components of a staff bio, as well.
|Content component||Job description|
|let people know which of our 3 offices this employee works in|
|Photo||help (potential) clients recognize our employees so they can "put a face to a name" or "put a name to a face"|
|Bio blurb||share each person's work and education story – peppered with some individual character|
|Quote||to have some fun and get to know this person more|
|Contact info||make it easy to reach this person|
|Recent insights||further demonstrate this person's expertise and interests|
Ask better questions
Thinking about the job of each content component encourages you to ask and answer different questions because each content component on a website plays a different role and has a different job description.
When planning content components, you'll ask:
- How would I describe the job of this content component?
- How does this content component's job relate to our web strategy?
- Does our website and our business actually need this job to be done?
When crafting content or reviewing content on your website, you'll ask:
- Which content components should I use on this page to achieve my messaging goals?
- Is this content component doing its job well? How could it improve?
Benefits of describing jobs
Fine. But why should I go to all of the trouble of describing jobs for each content component when I've already got so much to do?
The immediate benefits of understanding the job of each content component are that it:
- generates better conversations during the design process,
- creates a shared understanding around content functions, and
- helps authors make thoughtful and informed decisions when it comes to crafting new content.
Every piece of content on your website has a job to do. The idea of a job is simple and familiar so adding "content jobs" to your language will be well-received and readily understood by others. Job descriptions follow a simple format and help you ask better questions of the content you create and review. With job descriptions as your frame of reference, you and your team will be positions to have better conversations and to make informed content decisions.
Oh, and content that doesn't have a clear job should either get one or get out. ;)