Right context, wrong assumption: what Morgan Stanley learned about prompting at scale
August 29, 2026 · 5 min · Free, with full transcript
Morgan Stanley's deployment of an AI assistant for its financial advisors exposed a problem most teams overlook: feeding the model more information does not produce better answers. The real discipline is selecting which context matters, and why that distinction changes how you build prompts entirely.
Listen to the podcast
4 min
Read the full transcript
Welcome to the Leaders' Insights podcast.
Today's episode, right context, wrong assumption, what Morgan Stanley learned about prompting
at scale.
Morgan Stanley gave its financial advisors an AI assistant, stuffed it with the firm's
entire research library, and discovered something that should embarrass half the industry.
More context made the answers worse.
Explain that.
The counterintuitive part everyone skips.
Morgan Stanley wired their assistant to something like 100,000 internal research documents through
OpenAI's models.
And the early lesson wasn't, we need more data.
It was, we're drowning the model.
When you dump everything into the prompt, the prompt being the instructions and background
you hand the model before it answers, it starts treating irrelevant paragraphs as if
they matter.
But that's the whole pitch, isn't it?
Feed it your knowledge base and it gets smarter.
You're telling me the pitch is wrong?
The pitch is lazy.
There's a well-documented failure mode researchers call, lost in the middle.
Models pay attention to the start and end of a long context window and quietly ignore
what's buried in the middle.
So if the one document that answers the advisor's question is on page 40 of 60,
the model may skim right past it.
More pages doesn't mean more accuracy.
It means more noise competing for the model's attention.
So the fix is retrieval, right?
Only pull the relevant documents.
That's not new.
Retrieval is the tool.
That's RAG, Retrieval Augmented Generation, where you search your documents first and
only feed the model the top matches.
But Morgan Stanley's real insight was upstream of that.
Retrieval only helps if you've decided what relevant actually means for that user in that
moment.
An advisor asking about a client's retirement allocation doesn't need last
week's oil market commentary, even if the words overlap.
The discipline isn't fetching context.
It's ruthlessly deciding what to leave out.
Give me a concrete example of that going wrong.
Picture an advisor asks, what's our house view on municipal bonds for
a high net worth client in California?
A naive system retrieves 20 documents mentioning municipal bonds,
including a technical piece on bond mechanics,
a dated 2023 tax note, and a national overview.
The model blends them and produces something generic and slightly stale.
The right system knows the query has three constraints.
The security type, the client tier, the state tax situation, and
pulls only the current California specific guidance.
Same model, completely different answer.
This sounds like a lot of manual curation.
Doesn't that defeat the point of automation?
It shifts where the human effort goes.
You're not answering questions manually.
You're building the selection logic once.
Morgan Stanley put real work into evaluation,
having actual advisors grade responses before rollout.
That grading is what tells you your retrieval is pulling garbage.
Most teams skip it, ship the demo, and
wonder why adoption dies in month two.
Let's be honest about the numbers though.
Morgan Stanley says advisors love it.
That's the firm talking about its own product.
How much do we trust that?
Right to be skeptical.
Vendor and first party numbers on AI adoption are almost always polished.
What I trust more is the behavioral signal.
They reported the assistant getting used across the vast majority of their
advisor teams, and they kept investing in it rather than quietly shelving it.
That's more telling than any satisfaction percentage.
Firms kill tools that don't work.
This one survived, which suggests the context selection discipline
actually moved the needle.
So for someone building this at a much smaller scale,
a lawyer, a small consultancy, what's the transferable lesson?
Stop thinking, how do I give the model everything I know?
Start thinking, what are the three or
four facts that actually determine the answer to this specific question?
Structure your retrieval around those, not around keyword overlap.
And test it against real questions from real users,
not the tidy examples you invented.
Give me the one thing to do Monday morning.
Take your last ten prompts, and for each,
delete half the context you fed the model, the least specific half.
Run them again.
If the answers hold or improve, that context was never helping.
It was diluting.
You'll learn more about what your model actually needs in 20 minutes than in
a month of adding documents.
That's a wrap.
Fresh AI briefings drop daily at MBA-training.com.
Read and go deeper
- The article behind this episode: Right context, wrong assumption: what Morgan Stanley learned about prompting at scale
- The free AI track
- Watch on YouTube · the full playlist