A model replacement can look local until its representation reaches every retrieval path.
Better benchmark scores may conflict with migration risk, serving cost, and the evidence required for trust.
Who you’d be doing this for
“I can accept a planned change, but not a surprise drop in what people can find.”
Birke Seyoum · Enterprise Knowledge Platform Owner
Accountable for reliable internal search across business-critical systems during a platform transition.
What is at stake
The provider retires on a fixed date, and re-embedding every tenant cannot be undone cheaply. You have to weigh better recall against cost, and prove that results still respect permissions.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- provider deadline vs. verification depth
- benchmark relevance vs. permission-safe behavior
- migration certainty vs. model flexibility
- cost predictability vs. retrieval quality
Why Glean
At Glean, this often matters because retrieval quality and access-aware behavior must remain dependable through platform changes.
Written with these in mind
Not your kind of problem? 6 more at Glean, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.