Methodology

Content Development Methodology

A methodology is a collection of principles, practices, tools, and
techniques used to achieve a specific end. Content solutions result
from consistently applying a repeatable content development
methodology to effectively manage the content lifecycle.

The content development methodology
described here consists of a group of
sequential but interrelated tasks, each of
which requires multiple steps to execute.

The same methodology is used to create
any content solution. The steps required
within each task may vary depending on
the context within which the methodology
is being applied.

Generally, the execution of tasks is more
complex when the methodology is used
within larger, more complex organizations.

Capture
Concept

The concept for a content solution may come from
virtually anywhere. It may come, for example, from a
single individual who recognizes a need, or by way of the
collaboration of several people intent on solving a
problem, or from organization leadership.

The creation of a content solution begins with capturing
the concept so it may be assessed as viable and if it
provides a solution to a problem. The way a concept is
captured may be more or less formal. What is important
is that it be captured in a way that allows it to be
properly evaluated to determine if there is value in
developing the concept as a content solution.

Key Points

Concept generation

Single individual
Brainstorming (2 or more people)
Team collaboration
Leadership

Concept capture (i.e.)

"Back of the napkin"
Mind map
Formal description
White paper

Validate
Concept

A captured concept for a content solution needs to be
assessed to determine if it can be practically developed
and if it will fill a need. Includes identification and analysis
of potential/appropriate audiences.

Validation determines if the concept will be developed as
a product. The decision, based on both captured facts
and assumptions, addresses the use of necessary
resources to create a solution.

Key Points

Assessment

Is it practical?
Will it fill a need or solve a problem?

Validation is agreement to go forward

Validation logic needs to be documented

Plan
Project

Any development effort needs to be managed as a
project. The project plan provides an listing of the tasks
required to complete the project and a time line for
completion. The plan provides the discipline needed to
get the project done, but is not overdeveloped.

The value of a project plan is twofold: it keeps
development on track toward completion, and it provides
a historical record on which to base future development
projects. Also, for complex projects, it allows for the
allocation of resources.

Key Points

Project plan

Listing of project tasks in sequence
Time line for completion (estimated)
Only as complex as necessary

Value of a project plan

Monitors progress to completion
Historical record for future estimates
Allows for allocation of resources

Conduct
Research

Research may be conducted initially as the concept is
developed, and through the Design Product task. It may
continue into Develop Product task as required.

Research includes reviewing available relevant
documentation and best practices, conducting subject
matter expert (SME) interviews, observing actual
practices, and drawing on other sources.

Key Points

Supports quality solution development

Accurate
Complete

Research includes

Relevant literature & documentation
Best practices
SME interviews
Observation of actual practices

Design
Solution

Content solution design relies on research and the need
to create a solution that meets requirements with a bias
toward simplicity and minimalist principles.

Solutions are designed to deliver just the right
information to the right audience.

Solution designs are expressed in work products like
story boards, wire frames, mock-ups, or templates and
are subject to reviews with SMEs.

Key Points

Design basis

Solution specification
Audience analysis
Research

Design principles

Simplicity
Minimalism
"Just right" information

Develop
Solution

Content solution development is the execution of the
solution design as a finished product. Appropriate tools
are used to create a product that meets specifications.

May include the development and evaluation of an
content solution prototype, a one-off but complete
version of the fully executed product design. A prototype
is tested by a representative sample of the intended
audience. Feedback may prompt revisions.

Key Points

Execution of design

Content details developed
Illustrations added
Assembled as a finished solution
May represent a prototype for testing

Review
Solution

The content solution is reviewed by a limited number of
appropriate subject matter experts. This is an iterative
process in which the developer provides revisions based
on the reviews. No set number of review cycles is
established as the team works together to produce the
desired product.

Key Points

Review of solution

Identified SMEs provide review
Developer responds with revisions
Cycle is repeated to SMEs' satisfaction
Review cycles kept within reason

Approve
Solution

Content solutioin approval signifies acceptance by the
customer or an authorized representative. Approval
denotes satisfaction with the product and, where
appropriate, indicates an intent to compensate the
developer according to existing agreements.

Approval provides consent for publication, duplication,
and distribution.

Key Points

Approval of solution

Acceptance of the solution
Indicates intent to compensate
Consent to publish and distribute

Note that the methodology described here
is comprehensive and may not be
appropriate in all cases. Any portion of the
methodology may be waived by mutual
agreement.

Publish
Solution

To "publish" may have a predefined meaning, depending
on the context. Within organizations, certain conditions
may have to be met to consider something "published."
Or, an organization may have no definition of publishing
at all. In some cases, to publish a product simply means
to make it available, for sale or otherwise.

Within the context of this methodology, Publish Solution
means to meet all predefined conditions of the owner of
the publication prior to distribution. This may include
obtaining a copyright, providing notifications, storing
publication files in specified locations, or other details.

The owner of the published solution creates a definition
of "publish" within the proper context.

In some cases, the owner of the solution may choose to
work with a traditional publishing house.

Key Points

Publish solution

Meet all conditions required by owner's
definition of publishing
File all necessary legal documents,
such as applications for copyright
Arrange for solution duplication, as
appropriate
Store solution files in required locations
and update indexes and tables of
contents
Determine other requirements for
distribution (part of solution
specification)
Provide all necessary notifications

Distribute
Solution

Content solution distribution is as dependent on context
as is publishing, and is usually part of that process. In
short, it means making the product available to the
intended audience.

Distribution should be defined and planned as part of the
solution specification and within the context of the
defined publishing process.

Key Points

Distribute solution

Make the solution available to the
intended audience
Observe the requirements of the
defined publishing process

Blog

The Business of Knowledge & Communication