Do you have these "anxieties" about implementing a CMS?

• "Changing our current way of doing things seems tough. It's a hassle to learn new rules and how to use new tools."

• "What happens to the massive amount of 'past manual assets' we've created so far?"

• "I'm afraid that even if we implement it, no one will use it properly, and it will end up being a 'waste of treasure'."

These are the "realities" you should know before implementation, and they are also part of the "changes" necessary to transition to a better process.

Introduction: Understanding Change and Turning It into an Opportunity for Growth

CMS implementation is "operational reform." To gain the benefits a CMS offers, the team on the ground needs to "adapt" to new processes. (If you want to know more about the specific benefits of CMS implementation, please see our other column, "5 Benefits a CMS Brings to Manual Production.")
Link to "5 Benefits a CMS Brings to Manual Production"

In this article, we specifically explain the "5 Changes" you need to adapt to in order to secure those benefits.

A CMS is not a "magic system," but a "powerful engine" that maximizes team productivity. While effort is required to get used to new ways of working, it is also an opportunity for growth for both your team and yourself.

CMS Implementation Is Operational Reform! 5 Changes Field Staff Must Face

Change 1: Fundamental Shift in Writing Style

What should you do?

You must shift to "Topic-Based Writing." (A method of writing information as complete units of topics/items.)

Specifically?

A CMS is premised on "reuse." Therefore, each component (topic) must be "self-contained" so that its meaning is clear on its own. For example, expressions that rely on other contexts, such as "as mentioned above" or "in this chapter," can no longer be used.

Why is it necessary?

Removing context dependency prevents inconsistencies when reusing content in other manuals. As a result, you create logical manuals that are "understandable no matter where you start reading."

Change 2: Selecting an Authoring Environment (Content Creation Tool) and Transitioning to "XML"

What should you do?

You need to get used to handling content in "XML" format.

Specifically?

XML is a format that defines the "role" of information—like "This is a title" or "This is a warning text"—rather than its appearance (design). A CMS stores and manages information in a database with these "roles" clearly defined. For example, with SCHEMA ST4, which we handle, you can work in familiar tools like Word or Browser, and the system automatically converts and stores your work as XML. This minimizes the burden of learning new tools.
Link to ST4 Page

Why is it necessary?

Crucially, XML, which gives information a "role," serves as the fuel that powers the CMS engine's automatic processing.

Change 3: How to Deal with Past Assets (Existing Data)

What should you do?

You need to "componentize (turn into topics)" existing data and, in some cases, "rewrite" the content.

Specifically?

Simply pouring past Word or DTP data into a CMS won't work well. You need to divide and organize existing text so that it becomes "a chunk of information (topic) that explains one theme and is complete on its own." For example, you divide content according to role definitions (types): "How to Turn on Power" becomes a Procedure (Task), "What is the Safety Function" becomes a Concept, and "Specifications List" becomes a Reference.

Why is it necessary?

A CMS cannot treat huge files (entire books) as "reusable components." Only by properly dividing, defining, and storing them can the CMS recognize each piece of information and assemble it freely when needed. Also, this transition work is not just for CMS implementation; it should be an "excellent opportunity to organize and inventory the company's intellectual assets."

Change 4: Transition from "Individual Discretion" to "Team Rules"

What should you do?

Compliance with standardized rules and workflows decided by the team becomes mandatory.

Specifically?

Since designs are defined by templates, layout adjustments at individual discretion are no longer needed. Furthermore, you can use CMS features like "permissions management" and "approval flows" (e.g., Create -> Review -> Publish) to clearly divide staff roles.

Why is it necessary?

Enforcing rules on the system side physically eliminates "quality variations among staff." This prevents the risk of reliance on individuals and enables safe, efficient operation for the entire team.

Change 5: New Task of Continuous Maintenance of Shared Assets

What should you do?

You need to continuously maintain shared assets such as "templates," "glossaries," and "shared topics."

Specifically?

For example, you maintain shared assets in their latest state by regularly updating standard text blocks (components) like "Safety Precautions" in response to regulatory changes.

Why is it necessary?

In a CMS, a single component is reused across multiple manuals, so neglecting maintenance spreads outdated information far and wide. This activity is vital to ensure "information accuracy," a key benefit of a CMS.

FAQ: "Technical Questions" to Resolve Before Implementation

Here are some frequently asked questions and their answers.

Q1. How is it different from traditional DTP software?
A1. The biggest difference is that while DTP software is "document creation software" that handles text and design together, a CMS is an "information management database" that manages them completely separately. If DTP software is "a single lump of clay sculpture," a CMS treats data like text and diagrams as "blocks," assembling them freely as needed. This enables the same information (content) to be automatically output in different designs (templates), such as for print or web.

Q2. Can I use it without XML knowledge?
A2. No specialized XML knowledge is needed for basic writing tasks. While general CMSs use XML editors that require learning protocols like tagging, the system assists you, so you don't write code directly. Furthermore, SCHEMA ST4 has a feature that allows you to use Word or Browser directly as editing tools, so writers can work without being conscious of XML at all. Of course, you can also use a dedicated XML editor for more rigorous structured writing.

Q3. How do you manage illustrations, diagrams, and screenshots, not just text?
A3. Illustrations are centrally managed as "components" just like text. This means updating one master illustration automatically reflects the change in all related manuals, preventing replacement omissions. Management of multilingual versions (e.g., Japanese/English) is also possible. Image files that differ by language are managed by attaching attributes (metadata) regarding the language.

Q4. Can you manage product versions and specification differences?
A4. This is a CCMS specialty. (In SCHEMA ST4, we call this "Variant Management.") This mechanism manages "components" like text and illustrations by attaching attributes (metadata) such as "For Version 1.1," "For European Market," or "For English." For example, when outputting, if you specify "V1.1, European Market, English," the system automatically selects the correct text and images matching those attributes and generates the manual for that specific market.

Summary

We have explained the backstage of a CCMS, which creates and manages information in "topic (component)" units. "Structuring" may seem difficult at first glance, but implementing these rules establishes a system where anyone can create high-quality manuals.

With "SCHEMA ST4" provided by us, you can realize this structured writing with intuitive operation.
Link to ST4 Page

If you want to know more, please feel free to contact us.
contact us

Related articles：

Common Challenges in Manual Creation and the First Step to Solving Them: "CMS Basics"

No More Burnout! 5 Benefits a CMS Brings to Manual Production