SeSAM

Download the article about SeSAM published in ISTC Communicator.

Watch SeSAM presentations on YouTube

Follow Jonatans blog on dita.xml.org
2012-01-17:
Are you dictating how customers should run their business?

2011-12-28:
Is uncertainty making release management difficult?

2011-11-02:
For whom are you designing?

2011-10-19:
... and those are the reasons to why you should read Jonatan's blog

2011-09-13:
Are personas an effective tool when developing end user assistance?

2011-08-30:
How do you design for findability?

2011-06-21:
Are you creating and managing content nobody reads?

2011-05-24:
How is a topic signaling its content?

2011-04-28:
How do you determine the size of a topic?

2011-04-05:
What is a Meaningful Result Statement (MRS) in SeSAM?

2011-02-28:
What is the purpose of sorting and organizing topics that goes into a map?

2011-01-25:
Do we need a content strategy?

2010-12-19:
How do we identify user tasks?

Join the SeSAM interest group on LinkedIn

Check out the SeSAM presentation from NLDITA 2011

Welcome!

Are you technical communicator struggling with the following questions?

How do I identify which content to include in the manuals I am responsible for? I am involved in a user documentation project or an information analysis audit and need a guide.
How do I organize the manual's contents to make information easy to find? Do I need to create more than one manual?
How do I communicate with SMEs about the input I need to my manuals? How can I gain support and cooperation from SMEs?
I am not an expert on the products I need to document. How do I find out what content the end users need?
How can I keep project stakeholders (product managers) informed? How can I get their approval of my planned content early in the project? How do I avoid having them request major revisions at the final review stage?
There is no agreement or common view in my global content creation team on what content needs to be developed, let alone how it should be organized in manuals or in the CMS. We need to agree on a structured method of planning how content is specified and written, to eliminate inefficiencies.
How do I determine the size of a DITA topic?

Are you a product manager or user documentation manager who needs to:

Improve the organization of user manual/s to make it easier for end users to find content?
Implement a structured way to specify required content in global content creation teams?
Find a way to state requirements for end user documentation?

If your answers are "yes", then SeSAM is what you are looking for. SeSAM is an information architecture and design methodology built on the assumption that users are searching for answers rather than reading manuals methodically.

This site provides an introduction to the SeSAM concept. Navigate to SeSAM overview or In deep to start learning about SeSAM.

Do you need more information?

Are you already familiar with the SeSAM concept as given on this site? Are you trying to evaluate if the concept suits your needs? Or are you ready to start analyzing content according to SeSAM? Navigate to the More info area or Contact area for contact information to Jonatan Lundin which can provide you with the details about SeSAM.