Instant Publish vs Approval Publish - Which one do you use and why?

[chapmak]

Do you have Knowledge Managers review and then approve articles to be published to ensure they are well written, conform to your standards, etc. or do you let articles be instant published?       Has anyone had to switch from instant publish to having to review / publish due to quality issues?      Do you get decent quality with instant publishing or is it one of those, you have instant publish and let it ride due to lack of staff to review then publish articles.

[Rene Dugas]

Instant when the KBbase is for a closed, private or tight audience.
Approval when the audience is wide or user / customer facing

René

[Aerin]

When they brought me in to start a knowledge management process, the first thing I did was switch from instant publish. We don't have dedicated writers, the SMEs are expected to create content. But they mostly weren't comfortable or skilled with writing. I didn't want to establish a culture where poor writing was acceptable - that defeats the purpose. We created two workflows, so to begin, all content from new teams is reviewed by the team and then knowledge manager. Once they demonstrate an established level of competency, then they are allowed to publish with only a review by another team member.

[Rum]

We don't use Instant Publish in our organization. However, we have multiple KM Managers (like myself for main knowledge base, one KM Manager for Service Desk team (for Self-Service knowledge base, which also a team manager, and one KM Manager and supervisors for the IT Operations Data Center team). These two teams have the most KB articles which was the reason we have KM Managers for the teams. I won't be able to review and approve all KB articles for all IT teams.