🧭 Dojo Compass
Module: Decision-Making, Innovation and Lateral Thinking
Focus Area: Systems Thinking and Performance Improvement
Key Article Point
When entrepreneurs think about the most valuable assets of their companies, they often think about cash, customers, technology, intellectual property, equipment, brands, or the capabilities of their teams.
But there is another asset that many companies possess in significant quantities while systematically failing to capture, protect, organize, or use:
Company knowledge.
Every company—even the smallest SME—is a continuous business learning engine.
Every day, information is generated through:
- Operational successes and failures
- Employee interactions
- Management decisions
- Customer conversations
- Sales wins and losses
- Product development
- Pricing decisions
- Negotiations
- Hiring decisions
- Supplier relationships
- Market changes
- Financial results
- Unexpected problems and the attempts to solve them
Each event generates information.
We can think of this information as the company’s underlying data layer.
If each individual piece of information is represented as a data point:
D = {D₁, D₂, D₃ … Dₓ}
then the company is constantly adding new data points to this set.
But raw data, by itself, is not necessarily knowledge.
Knowledge begins to emerge when the company asks:
- What happened?
- Why did it happen?
- What worked?
- What did not work?
- What should we repeat?
- What should we stop doing?
- Under what circumstances might the same approach produce a different result?
This creates a second layer above the raw information: the knowledge layer.
For example:
An operational problem occurs.
That is data.
The company analyzes the problem and discovers that it was caused by a bottleneck between two departments.
That is knowledge.
The company redesigns the process and records the new approach.
That knowledge can now be reused.
Over time, this process can create one of the most valuable assets an organization possesses: a growing record of what the company has learned about how its own business works.
The problem is that most of this knowledge is never deliberately captured.
It remains inside individual memories, scattered across emails, buried in chat messages, hidden inside presentations, or lost when employees leave.
The result is a strange paradox.
A company may spend years generating experience—but repeatedly behave as if it is starting from zero.
The challenge is therefore not simply to collect more information.
It is to build a system that converts:
Experience → Data → Knowledge → Insight → Action
When this process becomes systematic, company knowledge can become an active competitive asset.
🎯 Key Challenge
How can SMEs capture the knowledge they generate every day and convert it into a practical, searchable, and continuously improving organizational asset?
The problem is larger than simple recordkeeping.
Companies lose knowledge in at least three important ways.
Knowledge Loss #1: Information Is Never Captured
A significant amount of business knowledge exists only in the minds of employees.
Someone learns why a particular customer left.
A salesperson discovers an effective way of overcoming a recurring objection.
An operations manager solves a difficult problem.
A team discovers that a process that appears efficient on paper creates repeated delays in practice.
But unless this knowledge is captured, it remains fragile.
Human memory is imperfect. Over time, details are forgotten, altered, or simplified.
Then, when an employee leaves, their accumulated knowledge may leave with them.
This creates what might be called organizational knowledge leakage.
The company invested time and resources in generating experience, but failed to retain the learning produced by that experience.
Knowledge Loss #2: Information Is Captured but Not Navigable
Other information is recorded—but in a form that makes it extremely difficult to use.
It may exist across:
- Email systems
- Chat platforms
- Shared drives
- Spreadsheets
- Presentations
- CRM systems
- Project management platforms
- Personal folders
- Meeting notes
The company technically possesses the information.
But possessing information is not the same as being able to retrieve it.
Imagine that a company learned an important lesson about entering a particular market three years ago.
The knowledge may exist somewhere.
But if finding it requires searching hundreds of emails, locating former employees, or manually reviewing old documents, the practical value of that knowledge approaches zero.
This is navigation friction.
The greater the friction required to find knowledge, the less likely people are to use it.
Knowledge Loss #3: Knowledge Is Stored but Not Used
Even well-organized information can become passive.
Many document systems are primarily designed for:
- Legal compliance
- Recordkeeping
- File storage
- Version control
These are important functions.
But they do not necessarily create an active knowledge system.
An active knowledge asset should help employees answer questions such as:
Have we encountered this problem before?
What did we learn from the last time we entered a similar market?
Why did this customer segment respond well to one product but poorly to another?
What were the causes of our previous operational failures?
Which practices have consistently produced strong results?
The objective is not simply to create a corporate library.
It is to create an organizational system that helps the company remember, learn, and act more intelligently.
🥋 Dojo Solution
The Dojo approach is to create a Company Knowledge Loop consisting of five stages:
1. Capture
Identify important experiences and record the knowledge generated from them.
2. Convert
Transform raw information into useful lessons, insights, and patterns.
3. Organize
Store knowledge in a structure that makes it easy to navigate.
4. Retrieve
Make relevant knowledge available when decisions or problems arise.
5. Reuse and Improve
Apply previous learning, observe the results, and add the new learning back into the system.
The loop can be represented as:
Experience → Capture → Interpretation → Storage → Retrieval → Action → New Experience
The objective is not to document everything.
That would quickly create an unmanageable amount of information.
The objective is to capture information that has a reasonable possibility of being useful again.
This requires a shift in mindset.
Instead of asking:
“Should we save this document?”
Ask:
“What did we learn here that the company may need to remember?”
🏗️ Putting It into Practice
Step 1. Treat Knowledge as a Company Asset
The first change is conceptual.
Knowledge should be treated with a degree of seriousness similar to other company assets.
Consider a company vehicle.
Most companies know:
- Who owns it
- Where it is located
- Who is authorized to use it
- How it is maintained
Company knowledge, despite potentially being far more valuable, often has none of this structure.
No one is responsible for capturing it.
No one knows where it is.
No process exists to preserve it.
The first principle should therefore be:
Knowledge created through company activity belongs to the organizational learning system, not only to the memory of the individual who experienced it.
This does not mean employees should spend hours documenting every conversation.
It means that the company should recognize that certain experiences generate knowledge worth preserving.
Management should make this part of the organization’s operating culture.
After an important event, the question should become routine:
What did we learn?
Step 2. Identify Knowledge Capture Points
Knowledge capture works best when it is connected to recurring events.
Possible capture points include:
Business Results
After an important positive or negative result, ask:
- What happened?
- Why did it happen?
- What factors contributed?
- Which factors were within our control?
- What can be repeated?
- What should be avoided?
Operational Processes
Capture:
- Bottlenecks
- Inefficiencies
- Process improvements
- Repeated errors
- Successful process innovations
Customer Interactions
Capture patterns relating to:
- Customer needs
- Common objections
- Reasons for customer wins
- Reasons for customer losses
- Upselling opportunities
- Retention and attrition
- Feedback about products and services
Employee and Organizational Interactions
Look for recurring insights regarding:
- Communication
- Decision-making
- Collaboration
- Management structures
- Recruitment
- Employee retention
- Organizational friction
Strategic Decisions
After an important strategic decision, record:
- What decision was made?
- Why was it made?
- What assumptions were involved?
- What happened afterward?
- Which assumptions proved correct or incorrect?
This last category can become particularly valuable.
Over time, the company develops a record of its own decision-making.
It can begin to identify patterns in how it thinks—and where its judgment is strongest or weakest.
Step 3. Create Simple Knowledge Capture Templates
A knowledge system should not create so much administrative work that employees stop using it.
The objective is high-value capture with low friction.
For example, after a significant project, a simple template might contain only five questions:
Project Knowledge Capture
1. What was the objective?
2. What happened?
3. What worked particularly well?
4. What did not work and why?
5. What should we do differently next time?
Similarly, a customer-loss template might ask:
- Who was the customer?
- What was the outcome?
- Why did we lose the customer?
- Is this an isolated event or part of a pattern?
- What should the company change, if anything?
The key is consistency.
A small amount of useful information captured repeatedly can become far more valuable than occasional fifty-page reports.
Step 4. Separate Data from Knowledge
One of the most important distinctions in building a knowledge asset is the difference between storing information and capturing what was learned from information.
For example:
Customer cancelled contract on June 15.
This is data.
A more useful knowledge entry might be:
The customer cancelled after repeated delays in technical support. The underlying issue was not product performance but unclear responsibility between the sales and technical teams. A similar issue has now occurred with three other customers.
This begins to identify:
- A pattern
- A possible cause
- A potential business risk
The company can then link the knowledge entry to supporting data:
- Customer communications
- Support tickets
- Revenue history
- Internal meeting notes
This creates a useful architecture:
Raw Evidence → Interpretation → Lesson → Recommended Action
The knowledge system should ideally preserve the connection between these layers.
Otherwise, the company risks turning opinions into institutional facts without maintaining the evidence necessary to revisit them.
Step 5. Make Knowledge Navigable
A knowledge base that cannot be navigated will eventually become a digital warehouse.
The goal should be to make information easy to find through several possible pathways.
Search
Employees should be able to search for natural-language concepts.
For example:
“Why have customers in Brazil cancelled contracts?”
or:
“What problems have we previously encountered when hiring sales managers?”
Categories
Knowledge can also be organized by:
- Department
- Geography
- Customer
- Product
- Process
- Strategic issue
- Type of lesson
Tags
A knowledge entry may contain multiple tags.
For example:
#CustomerRetention
#Brazil
#Pricing
#TechnicalSupport
Tags can help connect information that would otherwise remain in separate organizational categories.
Links and Relationships
More advanced systems can link related information.
A lesson about customer retention might connect to:
- Customer interview notes
- Product issues
- Pricing decisions
- Employee training
- Previous retention initiatives
This begins to transform a collection of documents into a knowledge network.
Step 6. Choose an Appropriate Knowledge Storage System
There is no single perfect knowledge system.
The appropriate choice depends on the company’s size, budget, technical capabilities, security requirements, and the type of information it needs to manage.
Several broad approaches are available.
1. Shared Cloud Storage
Examples include structured systems built around shared folders and documents.
Advantages:
- Familiar to most employees
- Relatively inexpensive
- Easy to implement
- Good for storing formal documents
Disadvantages:
- Search quality may be limited
- Knowledge can become fragmented
- Folder structures become increasingly difficult to manage
- Relationships between documents are difficult to visualize
This can work well as a basic document repository but may be insufficient as the company’s primary knowledge system.
2. Wiki or Knowledge Base Systems
These systems organize knowledge into linked pages and categories.
They are useful for:
- Procedures
- Internal guidance
- Lessons learned
- Frequently asked questions
- Organizational knowledge
Advantages:
- Relatively easy to navigate
- Information can be structured
- Content can be updated
- Good for collaborative knowledge creation
Disadvantages:
- Requires discipline to maintain
- Information can become outdated
- Search quality depends on the system
- Employees may fail to contribute consistently
This approach can be particularly useful for SMEs that want a relatively simple and centralized knowledge environment.
3. Database-Based Knowledge Systems
A company can create structured knowledge records inside a flexible database.
Each knowledge item can include fields such as:
- Date
- Source
- Department
- Topic
- Lesson
- Related project
- Confidence level
- Recommended action
Advantages:
- Highly structured
- Flexible filtering and categorization
- Can identify patterns
- Useful for repeated knowledge capture processes
Disadvantages:
- Requires initial design
- May feel administrative if poorly implemented
- Complex knowledge may not fit easily into predefined fields
This is particularly useful when a company wants to systematically analyze recurring business experiences.
4. AI-Enhanced Search and Retrieval Systems
Newer systems can use artificial intelligence to search across documents and respond to questions in natural language.
For example, an employee might ask:
“What have we learned from previous attempts to enter new markets?”
The system can retrieve relevant information from across the company’s knowledge base.
Advantages:
- Natural-language search
- Can reduce navigation friction
- Can connect information across multiple sources
- Potentially powerful for large or fragmented knowledge bases
Disadvantages:
- Requires careful data organization and permissions
- Can produce incorrect or incomplete answers
- May create security and confidentiality concerns
- Quality depends heavily on the underlying information
An important principle is:
Artificial intelligence can improve access to knowledge, but it cannot compensate for knowledge that was never captured.
AI should therefore be considered a potential retrieval layer built on top of a well-designed knowledge foundation.
5. Knowledge Graphs and Relationship-Based Systems
A more advanced approach is to represent knowledge through relationships.
For example:
Customer → Product → Market → Problem → Cause → Solution → Result
This can help companies identify patterns that are difficult to discover through ordinary folder structures.
Advantages:
- Can reveal relationships between different information
- Useful for complex organizations
- Supports pattern identification
- Can become increasingly powerful as knowledge grows
Disadvantages:
- More difficult to design
- Requires technical capability
- Can be unnecessarily complex for smaller organizations
- Initial implementation requires significant thought
For many SMEs, this may be a longer-term objective rather than the appropriate starting point.
Step 7. Create a Knowledge Review Process
Knowledge should not simply flow into the system.
It should periodically be reviewed.
For example, management could establish:
Monthly Knowledge Review
Ask:
- What did we learn this month?
- Which lessons are likely to be useful again?
- Are recurring patterns emerging?
- What knowledge should be converted into a formal process or policy?
Quarterly Knowledge Review
Ask:
- What strategic assumptions proved correct?
- What assumptions proved incorrect?
- What recurring problems have we failed to solve?
- What successful practices should be scaled?
This creates a bridge between knowledge storage and decision-making.
The knowledge system stops being an archive and becomes part of the company’s management infrastructure.
Step 8. Turn Knowledge into Action
The final objective is not knowledge for its own sake.
The objective is better action.
A useful knowledge system should help the company:
- Repeat successful practices
- Avoid repeating preventable mistakes
- Train new employees more effectively
- Improve decision-making
- Identify patterns
- Discover new opportunities
- Reduce dependence on individual memory
- Preserve knowledge during employee turnover
The ultimate test is therefore:
Did the company do something better because it remembered something it had previously learned?
If the answer is yes, the knowledge system is beginning to create value.
📌 Key Takeaways
- Every company is a continuous generator of business data and experience.
- Raw information becomes more valuable when it is interpreted and converted into organizational knowledge.
- Much company knowledge is lost because it remains inside individual memories or disappears when employees leave.
- Other knowledge is technically stored but remains inaccessible because it is fragmented across emails, chats, documents, and different software systems.
- High navigation friction dramatically reduces the practical value of knowledge.
- SMEs should treat company knowledge as a strategic asset rather than simply as an administrative record.
- Knowledge capture should be systematic and connected to recurring business events.
- Simple, repeatable templates are generally more effective than demanding long reports.
- Knowledge should preserve the connection between raw evidence, interpretation, lessons, and action.
- The right storage system depends on the company’s needs, complexity, resources, and technical capabilities.
- AI can make company knowledge easier to search and use, but it cannot recover knowledge that was never captured.
- The ultimate objective is to turn accumulated experience into better future decisions.
🌿 Reflection
Every company accumulates experience.
But experience alone does not automatically create organizational learning.
A company can experience the same problem repeatedly without learning from it.
It can lose the same type of customer for the same reason.
It can repeatedly hire the wrong people.
It can enter new markets while forgetting the lessons from previous expansions.
It can allow highly experienced employees to leave—and then discover that much of what they knew left with them.
The difference between experience and learning is capture.
The difference between captured knowledge and a strategic asset is use.
This suggests a simple but powerful progression:
What happened?
becomes:
Why did it happen?
which becomes:
What did we learn?
which finally becomes:
What should we do differently because we learned it?
Over time, these individual lessons can begin to connect.
A problem identified by the sales team may connect to something discovered by operations.
A customer complaint may reveal an issue previously observed in product development.
A failed market entry may contain lessons that make the next expansion significantly more successful.
The company begins to see itself not simply as a collection of people performing activities, but as a system capable of remembering its own experience.
For SMEs, this may be particularly powerful.
Large companies often possess extensive resources, large teams, and institutional infrastructure.
An SME may not have these advantages.
But it can develop something highly valuable: the ability to learn faster.
If an SME can systematically capture what it learns, make that knowledge accessible, and use it to improve future decisions, every important experience can potentially make the organization stronger.
The goal is not to remember everything.
It is to avoid forgetting the things that matter.
A company that learns but does not remember is forced to pay repeatedly for the same lessons. A company that captures, connects, and reuses its knowledge can allow every important experience to continue creating value long after the original event has passed.
⚔️ Dojo Mission
Over the next thirty days, begin building a Minimum Viable Company Knowledge System.
Do not attempt to capture everything.
Start with three knowledge categories that are particularly important to your business.
For example:
- Customer wins and losses
- Operational problems and solutions
- Strategic decisions and their outcomes
For each category, create a simple five-question capture form:
1. What happened?
2. What were the most important contributing factors?
3. What did we learn?
4. What evidence supports that conclusion?
5. What should we repeat, change, avoid, or investigate further?
Then establish a simple storage structure that allows the entries to be searched by topic, date, business area, and relevant tags.
At the end of the thirty days, conduct your first Knowledge Review.
Ask:
What have we learned that would probably have been lost if we had not captured it?
Then ask the more important question:
What will we now do differently because we know it?
That is the moment when company knowledge stops being a collection of information and begins to become an active business asset.
Your company is already generating knowledge every day. The strategic question is whether you will allow that knowledge to disappear—or build a system that allows it to compound.
Leave a Reply