A strong Company Brain should first answer the questions that appear in daily operations again and again. This is not theoretical knowledge management. It is about pricing approvals, complaints, handovers, responsibilities, customer exceptions, and accounting documents. When these answers are reliable and easy to find, work becomes faster, calmer, and less dependent on individual people.
Why should a Company Brain start with real operational questions?
Many knowledge projects start too big. A system is introduced. A wiki is created. A folder structure is debated. Someone becomes responsible. Then something familiar happens: employees still search old emails, ask the same colleagues, or keep their own private notes.
The reason is rarely a lack of willingness. The reason is often that the new system does not answer the questions people actually have during work.
A Company Brain should therefore not begin with a perfect taxonomy. It should begin with the 20 questions that affect revenue, speed, quality, and customer trust every week. Who may approve prices? What information do we need for a quote? What happens when there is a complaint? Which customers have special agreements? Which documents does accounting need? Who decides when the standard process does not fit?
That may sound basic. It is not.
If one employee cannot answer these questions quickly, work slows down. If ten employees answer them differently, errors appear. If only one person knows the answer, the company becomes dependent on that person.
Atlassian reports that 56 percent of workers often find that the only way to get the information they need is to ask someone or schedule a meeting. This pattern is expensive in mid-sized companies: knowledge exists, but it is not available where the decision is being made.
Which 20 questions should a Company Brain answer first?
The following list is deliberately practical. It applies to many mid-sized businesses, including technical service providers, construction-related companies, IT service firms, facility services, field service organizations, property-related services, and B2B operations. The wording should later be adapted to the industry. The core remains the same: a Company Brain must first protect daily work.
Who is allowed to approve prices?
This question looks small, but it affects margin, commitment, and speed. A Company Brain should clearly show who may approve discounts, special conditions, package prices, project rates, or deviations from standard pricing. The important part is not only the name. It is also the logic: up to what amount, for which customer group, and with which justification?
What information do we need for a quote?
Quotes often fail not because of calculation, but because of missing input. A good Company Brain does not only list required fields. It explains which information really matters: scope, location, deadline, photos, technical details, contact person, special requests, contractual basis, existing documents, and desired delivery or execution date.
Which quote template is current?
In many companies, several templates circulate at the same time. An old version on a shared drive. A newer version attached to an email. A modified version on one employee’s desktop. The Company Brain must clearly answer which template is valid, who maintains it, and when it was last reviewed.
Which customers have special agreements?
Special agreements are risky when only individual employees know them. A Company Brain should show which customers have different prices, response times, invoice routes, contact rules, documentation duties, or service levels. The reason for the exception matters as much as the exception itself.
What do we do when there is a complaint?
Complaints require clarity. Who receives the complaint? Who evaluates it? Who communicates with the customer? Which deadlines apply? When is escalation required? Which goodwill rules exist? A Company Brain should explain the process clearly enough that a new employee does not promise something out of uncertainty.
How does the handover from sales to execution work?
Many mistakes happen between promise and delivery. Sales has spoken to the customer, but execution receives only a PDF or a short note. A Company Brain should define which information must be handed over: scope, exclusions, dates, risks, customer preferences, photos, contact people, pricing logic, and open points.
Which documents does accounting need?
Accounting is often involved too late. Then purchase orders, proof of performance, customer numbers, cost centers, contract data, or payment terms are missing. A Company Brain should explain which documents must be complete for each type of transaction before invoicing begins.
Who is responsible for which decision?
Org charts help only to a point. Daily operations need real decision paths. Who may stop a delivery? Who decides on goodwill? Who prioritizes urgent cases? Who approves deviations from the standard process? A Company Brain must link responsibilities to specific situations.
Which information may be communicated to customers?
Communication is critical in service, complaints, and delays. Employees need guardrails: What may be promised? Which wording is approved? When is internal approval required? Which information is internal and should not be shared externally?
Which standard replies do we use frequently?
Many companies write the same emails again and again. That costs time and creates inconsistent communication. A Company Brain should contain approved standard replies for quote receipt, scheduling, complaints, missing information, delays, maintenance, payment questions, and follow-ups.
Which mistakes must not happen again?
Every company has paid for mistakes. It becomes expensive when the lesson is not reusable. A Company Brain should capture recurring failures: wrong calculations, unclear ownership, missing documents, technical assumptions, communication errors, or problematic supplier decisions.
Which projects or cases are similar to the current one?
This is one of the strongest use cases for a Company Brain. Employees should be able to find similar quotes, complaints, tickets, projects, or customer cases. Not by remembering a file name, but by searching for similar situations.
Which deadlines apply to this case?
Deadlines are often scattered across contracts, quotes, emails, laws, internal processes, and customer agreements. A Company Brain should show deadlines for quote submission, response, execution, complaints, documentation, invoicing, and escalation.
Which systems must be updated?
One transaction often touches several systems: CRM, ERP, ticketing, accounting, project management, file storage, and customer portals. The Company Brain should explain which information belongs in which system and which system is the leading source.
Which documents must be archived?
Not everything has to be stored forever. But some documents are critical: quotes, order confirmations, approvals, proof of performance, photos, acceptance records, invoices, complaint histories, and contract changes. The Company Brain should show where each document belongs and why it matters.
What do we do when information is missing?
Missing information is normal. The question is whether employees know how to handle it. Can a quote still be created? Should the customer be asked for more details? Who approves assumptions? Which risks must be documented?
Who can help with technical or specialist questions?
A Company Brain does not replace experts. But it makes expertise visible. Employees should know who can help with which topic. This prevents the same people from being interrupted constantly and helps new employees find the right contact faster.
Which services do we not offer?
This question is often underestimated. Clear non-services protect against wrong expectations, bad projects, and unprofitable commitments. A Company Brain should state which services are deliberately excluded and how customers should be informed professionally.
Which quality check is required before closing a case?
Before a transaction or case is closed, the required checks should be clear: completeness, documentation, photos, signatures, approvals, invoice data, customer satisfaction, and open risks. A Company Brain should present these checks as error prevention, not bureaucracy.
What is the next sensible step?
This is the most important question. A Company Brain should not only return information. It should create orientation. When an employee describes a case, they should understand which rule applies, which template fits, who decides, which documents are missing, and what should happen next.
Which questions belong to which knowledge area?
A Company Brain becomes easier to manage when questions are grouped by operational knowledge areas. The following table provides a simple starting structure.
| Knowledge area | Typical questions | Why it matters | Risk without a clear answer |
|---|---|---|---|
| Sales and quotes | Prices, required data, templates, approvals | Protects margin and speeds up quoting | Wrong commitments, rework, margin loss |
| Customers and contracts | Special agreements, contacts, deadlines | Prevents inconsistent customer handling | Escalations, contract errors, lost trust |
| Execution and service | Handover, quality, similar cases, responsibilities | Makes operational work more predictable | Delays, duplicate work, quality issues |
| Complaints and escalation | Process, communication, goodwill, approvals | Reduces uncertainty in difficult moments | Wrong promises, customer frustration, costs |
| Accounting and records | Documents, archiving, invoice data | Supports clean billing | Missing invoices, follow-ups, payment delays |
Why are these questions more important than a large knowledge base?
Because companies do not fail because they lack pages. They struggle because they lack answers at the moment of decision.
A large knowledge base can look impressive. It can contain many documents. It can be well structured. Still, it does not help much if employees cannot answer a simple operational question quickly.
Gartner describes modern customer service knowledge management systems as platforms that replace traditional knowledge bases, manage content, and power conversational AI, chatbots, and AI agents. The business problems are practical: inconsistent service levels, difficulty finding needed information, and the manual burden of keeping content updated and complete.
The same logic applies beyond customer service. It applies across mid-sized operations.
A Company Brain should therefore not be designed as an archive. It should be designed as a working instrument.
Which numbers show the practical need?
Knowledge is often invisible in daily operations. The cost becomes visible when employees search, ask, wait, duplicate work, or make decisions based on incomplete information.
Atlassian states that 56 percent of workers often need to ask someone or schedule a meeting to get information. It also reports that teams using the Atlassian platform spend 50 percent less time searching for information.
Asana’s Anatomy of Work Global Index 2023 reports that knowledge workers estimate they could save 4.9 hours per week through improved processes.
IBM cites IDC data stating that knowledge workers spend about 2.5 hours per day, or roughly 30 percent of the workday, searching for information. This older figure is still widely used as a reference point for the persistent problem of fragmented enterprise information.
These figures should not be copied mechanically into every company case. But they point in the same direction: when answers are not findable, work becomes expensive.
How should a company capture the first 20 questions?
The best starting point is a workshop based on real cases. Not abstract. Not “Which knowledge categories do we need?” but: “Which questions cost us time this week?”
Sales, execution, service, accounting, and leadership should review three to five real transactions together. A quote. A complaint. A handover. An invoice. A special customer. This quickly shows which answers are missing.
Those gaps become the first knowledge objects. Each object should be short and reliable: question, answer, validity, owner, source, last review date, and related cases.
It sounds simple. That is why it works.
How does a Company Brain stay current?
Freshness does not come from good intentions. It comes from ownership and integration into workflows.
When a pricing rule changes, the Company Brain must be updated. When a customer receives a special agreement, it must appear there. When a complaint creates a new lesson, it must be captured. When a template is replaced, the old version must be clearly superseded.
APQC provides specific questions to capture critical role-related knowledge from employees and recommends using them especially with experts, senior employees, and people at risk of leaving. This shows that critical knowledge must be captured deliberately, not by accident.
A Company Brain is therefore not a one-time project. It is an operating standard.
Sources for the statistics used
- Atlassian: “Stop losing time searching for the information you need”
https://www.atlassian.com/blog/strategy/information-management - Atlassian: “State of Teams 2024”
https://www.atlassian.com/blog/state-of-teams-2024 - Asana / HRTechCube: “Asana Anatomy of Work Global Index 2023”
https://hrtechcube.com/asana-anatomy-of-work-global-index-2023/ - IBM Support with IDC reference: “Cognitive University for Watson Systems SmartSeller”
https://www.ibm.com/support/pages/cognitive-university-watson-systems-smartseller
Further reading
- APQC: “Questions to Capture Critical Knowledge from Employees”
https://www.apqc.org/resource-library/resource-listing/questions-capture-critical-knowledge-employees - APQC: “Knowledge Management FAQ”
https://www.apqc.org/resource-library/resource-listing/knowledge-management-faq - Gartner: “Market Guide for Customer Service Knowledge Management Systems”
https://www.gartner.com/en/documents/5491795
FAQ
What is a Company Brain?
A Company Brain is a structured company memory. It does not only store documents. It connects knowledge with customers, processes, decisions, responsibilities, and real questions from daily work. The goal is to help employees find reliable answers faster and reduce operational dependence on individual knowledge holders.
Why should a Company Brain start with questions?
Questions reveal where uncertainty actually exists inside the company. A pure document repository can store many files and still miss daily work. When a Company Brain starts with real operational questions, it creates faster value: fewer repeated questions, faster decisions, clearer handovers, and better onboarding.
Which departments should be involved first?
The best starting departments are usually sales, execution, service, accounting, and leadership. These areas have many handovers and frequent friction points: missing quote data, unclear approvals, customer exceptions, complaints, and billing issues. These interfaces usually provide the most valuable first questions for a Company Brain.
How many questions should a Company Brain answer at the beginning?
Twenty well-selected questions are often enough for a strong start. The number is less important than operational relevance. The first questions should focus on areas where employees frequently ask for help, errors occur, customers wait, or decisions depend on individual people. The system can then grow step by step.
How is a Company Brain different from a wiki?
A wiki usually contains pages and instructions. A Company Brain is more question- and context-oriented. It connects answers with owners, sources, approvals, customers, cases, and related decisions. This makes knowledge usable in a specific work situation rather than merely stored somewhere.
Who maintains the answers in a Company Brain?
Every answer needs a subject-matter owner. Pricing rules should belong to sales or leadership, not IT. Complaint processes should belong to service or quality management. The technical platform can be centrally managed, but the accuracy of operational knowledge must remain with the responsible business function.
How can outdated or wrong answers be avoided?
Answers need sources, review dates, and owners. Critical content should be reviewed regularly, especially prices, customer agreements, templates, and compliance-relevant processes. It should also be visible whether an answer is approved, outdated, or only informational. Without governance, a Company Brain quickly loses trust.
What role does AI play in these 20 questions?
AI can help employees find the right answer faster, identify similar cases, and summarize existing documents. However, the underlying sources must be approved, current, and properly owned. AI does not automatically fix a weak knowledge system, but it can make a good system much more usable.
All articles about company brain
