ILLUSTRATIVE SOLUTION SCOPE
Internal knowledge software
Help people find useful answers in a defined body of business knowledge, with the sources available for review.
Define the knowledge boundary
Choose the documents, owners and users before designing search. A small approved collection is easier to assess than an unrestricted drive. Establish how outdated documents are replaced and what happens when two sources disagree.
Design for the user
Build around the actual task: finding a policy, locating a procedure or answering a recurring product question. Show relevant source excerpts and links. Make it easy to report a missing or incorrect answer, and provide an explicit “not enough information” path.
Permissions are part of the product
A search result should not expose material a user cannot access. Agree authentication, document permissions and access checks at ingestion and retrieval. Do not use a demonstration dataset to infer that production permissions are solved.
Deliverables to agree
User journeys, focused web application, approved document ingestion, source display, permission checks, evaluation cases, deployment documentation and agreed source-code handover. Maintenance of the document collection belongs in the operating scope.
Evaluate before extending
Create questions that cover common tasks, ambiguous requests and answers absent from the sources. Review retrieval relevance, source support and refusal behavior. A retrieval-based application may fit better than fine-tuning when the problem is access to changing information.
Questions for your project brief
- Which documents are approved for use?
- Who maintains and updates them?
- What access groups must be respected?
- What would an unacceptable answer look like?
START A CONVERSATION
Turn a business problem
into a clear project.
Bring a task, a bottleneck, or a product idea. The first step is a clear scope.