Back to database

Delphine Zurkiya's AI use case

Senior Partner; leader in McKinsey’s North America Life Sciences and Technology Practices and McKinsey’s generative AI initiatives in Life Sciences and Healthcare at McKinsey

Internal knowledge assistant workflow where consultants use Lilli to search McKinsey's knowledge base, synthesize key points, surface relevant documents, and find internal experts.

The problem

What was broken before AI

Consulting research often meant hunting through old decks, reports, interview notes, expert directories, and internal knowledge systems before a team could even frame the right approach. Valuable context existed, but it was scattered across formats and practices, with much of the firm’s knowledge living in PowerPoint. Newer consultants also had to know what to search for, who to ask, and which prior work was most relevant.

What changed

What the use case made possible

Lilli gives consultants a conversational front door to McKinsey’s internal knowledge. According to Business Insider, users can ask a question, have Lilli aggregate key points, identify five to seven relevant internal content pieces, and point them toward appropriate experts. McKinsey says the platform has been widely adopted since its 2023 rollout and reports time savings in searching and synthesizing knowledge.

Why this matters

Why this use case is worth studying

This case shows why enterprise AI gets more useful when it is connected to proprietary context, citations, and people. A generic chatbot can help draft a hypothesis, but a knowledge assistant connected to a firm’s own work can help a team understand precedent: what has been done before, which documents matter, and who inside the organization has real experience. For consulting, that changes the first hour of a problem from blank-page searching into a more informed discussion.

Use this when

When this pattern applies

Use this pattern when your organization has valuable knowledge trapped across decks, reports, wikis, transcripts, and expert networks, and employees waste time rediscovering what others already know.

Exponential Builder analysis

01

Retrieval needs a workflow around it

Search becomes more useful when the answer includes documents to inspect and experts to contact. The assistant should move the user toward evidence and people, not only text.

02

Training is part of the product

McKinsey’s reported “prompt anxiety” is a reminder that adoption depends on helping employees know what a good question looks like. A one-hour enablement session can matter as much as another feature.

03

Institutional memory is an advantage only if people can reach it

Large organizations often have the answer somewhere, but the path is unclear. AI creates leverage when it shortens the distance between a live problem and the organization’s accumulated experience.

Who this is for

Best fit

Consulting, services, and agency teams with large internal knowledge bases

Operators building enterprise search or knowledge-management systems

Founders trying to make company memory usable as the team grows

Product and customer teams that need to connect documents with internal experts

AI leaders looking for a practical, high-adoption internal use case

What to avoid

Mistakes and warnings

Where this pattern can go wrong if you copy it too literally.

Do not treat the synthesis as the final answer; it is a research starting point.

Do not connect AI to messy or over-permissioned repositories without access controls.

Do not let the assistant hide its sources, especially in high-stakes advisory work.

Do not assume employees will know what to ask; McKinsey reported early “prompt anxiety,” and training helped.

Do not mix client-confidential data with general-purpose AI tools unless your legal, security, and contractual setup explicitly allows it.

Watch for old documents that look authoritative but no longer reflect current conditions.

Public workflow preview

The shape of the workflow

A high-level look at how the use case works, with the reusable pattern made clear.

01

Ask the client question

Start with the business problem, sector, geography, or decision the team is trying to understand.

02

Search internal knowledge

Use Lilli to query McKinsey’s internal knowledge repository rather than manually hunting across decks and reports.

03

Synthesize the landscape

Review the summarized key points as an orientation layer, not as final advice.

04

Open the source documents

Inspect the five to seven internal content pieces Lilli surfaces and check whether they actually fit the problem.

05

Find people who know the topic

Use expert suggestions to locate colleagues with relevant experience.

06

Apply consultant judgment

Turn the retrieved context into hypotheses, questions, and analysis that fit the client’s situation.

Copy the pattern

The reusable idea

Pattern in one sentence

Turn the company knowledge base into a guided research assistant that returns a synthesis, source documents, and people to talk to.

Reusable idea

The useful move is to design AI around the moment when a team asks, “Have we seen this before?” Start by connecting AI to your best internal documents, then require it to return source material and likely experts instead of only a polished answer. The output should help a person get oriented faster, not skip the work of checking assumptions.

Steal this workflow

Internal Knowledge Assistant Mini-Spec

Before using the output in a client, board, or leadership setting, open the source documents and verify the claims.

Review rule

Business question:

Industry/function:

Geography or market:

Time horizon:

Source scope: internal only / approved external / both

Sensitivity level:

1

Short synthesis of the answer

2

What we know from prior work

3

What remains uncertain

4

Five to seven source documents to read next

5

Suggested internal experts or document owners

6

Suggested follow-up questions

7

Risks, caveats, or outdated assumptions to check

Suggested prompt

“Search our approved internal knowledge base for prior work related to [specific business question]. Give me a concise synthesis, then list the five to seven most relevant source documents with why each matters. Identify any internal experts or document owners I should contact. Separate confirmed evidence from assumptions, and flag anything that may be outdated or risky to rely on.”

Field notes

Get new AI use cases in your inbox

A short weekly note on how real people are using AI to save time, make money, build tools, and run their lives.

No spam. Just useful AI use cases.

Related use cases

Keep exploring nearby systems.

Browse all