Prototype graph signals for unresolved expertise searches
Relationship data often looks valuable before teams know which decision it should improve.
Signals that appear intuitive can compete with the need for a measurable and understandable retrieval outcome.
“I can find plenty of docs. I still can’t tell who actually knows this system today.”
Gabriela Machado · Enterprise Architecture Lead
Coordinates cross-functional technology initiatives and repeatedly needs to identify who owns active systems and decisions.
What pulls against what
- intuitive graph value vs. measurable user outcome
- signal richness vs. relationship freshness
- prototype freedom vs. serving realism
- document retrieval vs. ownership discovery
What is at stake
Several relationship signals look promising, but pursuing the wrong one could create elaborate retrieval without a meaningful user outcome
Why Glean
At Glean, this can matter because enterprise knowledge is shaped by relationships as well as by files.
Written for
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.