Define Compelling Use Cases

Stan Garfield
The seventh step in the 12 Steps to KM Success is to define compelling use cases with clear advantages over existing alternatives. Don’t talk about driving adoption or rolling out tools. Instead, talk about the clear advantages of using them over existing alternatives.
For example, you can use COLLABORATION as an acronym that includes 13 use cases that are more specific than just asking people to collaborate.
- Communicate: Inform the organization about your activities. plans, and progress; interact with colleagues; solicit input, feedback, advice; or relax, refresh, relieve tension, and laugh
- Obtain: Gain assistance from others, find out what others are doing, retrieve information, or receive answers to questions
- Locate: Find subject matter experts, documents, credentials, references, sites, official methods, lessons learned, proven practices, or other needed resources
- Learn: Become educated on a topic, deepen expertise, or keep current on the latest news
- Assist: Respond to a request; respond to a client request for information. proposal, or support; submit a proposal; deliver a product, project, service, or client engagement; or provide expertise
- Build: Develop and deliver a presentation or webinar; write a document, or build and deliver a product or service
- Offer: Answer questions; provide points of view, proven practices, lessons learned, examples, or official methods; get staffed on a project or client engagement; lead an effort; or praise, recognize, and thank colleagues
- Resolve: Identify issues, solve problems, or fix something that is broken
- Ask: Ask questions, request advice, or submit a query or request
- Transfer: Transfer knowledge; share links, insights, lessons learned, tips, tricks, or techniques; or contribute reusable content
- Innovate: Develop new and better ways of serving clients; solicit ideas; manage the innovation process; improve existing products, services, processes, and tools; or invent new products, services, processes, and tools
- Onboard: Orient new hires or team members, get oriented as a new hire or team member, or orient new clients
- Network: Connect to others with similar interests, work together as part of a team, or connect multiple organizations to deliver services together
Another acronym, SAFARIS, can be used to remember seven key uses for communities and Enterprise Social Networks. Each of these is more effective and efficient that alternative approaches, and that is the strength of offering use cases.
- Share a link. “Here is a link to the recording of the most recent Lucidea webinar.”
- Ask a question. “Has anyone encountered this problem before, and if so, how was it solved?”
- Find a resource. “I’m looking for a specialist in artificial intelligence to help in a project.”
- Answer a post. “Here are links to three relevant documents in the knowledge repository.”
- Recognize a colleague. “Thanks to Janet Johnson for helping me solve a difficult problem.”
- Inform about your activities. “I am working on updating the enterprise taxonomy, so suggested changes are welcome.”
- Suggest an idea. “I think we should add a button next to each document in the repository to click on if it was useful.”

Stan Garfield
Please read Stan’s additional blog posts offering advice and insights drawn from many years as a KM practitioner. And learn about Lucidea’s Inmagic Presto, with KM capabilities to support successful knowledge management programs.
Similar Posts
The KM Mentor, Part 3: Advice for an IT Professional at a Culinary Institute
KM expert Stan Garfield provides advice for a culinary institute IT staff member on how to develop training materials, prioritize KM initiatives, and support chef-instructors and students.
The KM Mentor, Part 2: Advice for a Music Festival Librarian
KM expert Stan Garfield advises a new music festival librarian on how to build a sustainable library and knowledge management program in one year.
The KM Mentor, Part 1: Advice for an Architecture Firm Librarian
How can a solo librarian at an architecture firm address knowledge gaps? Stan Garfield shares practical advice for developing an effective KM strategy.
The KM Cure, Part 3: Knowledge Rot
Stan Garfield explores how knowledge rot—outdated, inaccurate, conflicting, redundant, or missing information—causes costly errors and poor decisions without active curation.




Leave a Comment
Comments are reviewed and must adhere to our comments policy.
0 Comments