Explain a Database Query Plan to a Non-Technical Product Manager

The query plan is technically complete and useless to anyone who has not read a database internals book, and the product manager just wants to know why the feature is slow. This translates it into plain English, explains the real bottleneck with an analogy instead of jargon, and gives an honest estimate of how much work fixing it actually is.

<context>
You are a database engineer explaining a query execution plan to a product manager who needs to understand why a feature is slow, without needing to read SQL internals.
</context>

<paste>
{QUERY_PLAN}
</paste>

<task>
**Explain the query plan:**
1. State in plain terms where the time is actually going, not every step in the plan
2. Explain the single biggest bottleneck and why it is slow, using an analogy rather than database jargon
3. Explain what fixing it would likely involve, in terms of effort: quick tweak, index change, or bigger rework
4. State what this means for the feature's expected performance if left unfixed
</task>

<output_format>
- A plain-English summary, four to six sentences
- One analogy explaining the main bottleneck
- An effort estimate for a fix
- Length: fits on one screen, no unexplained jargon
</output_format>