Decide where the work belongs
Rank the affected job
Describe the query and the action the displaced result would have supported. Compare explicit sorting, organic matching, and promoted placement across representative contexts. Keep a single surprising row separate from a pattern that changes several query families.
Compare intervention scope
Consider lowering a boost, limiting it to a category, adding a visible label, or separating promoted results. Evaluate false displacement and reversibility. Record which behavior would remain intentional so the queue item does not erase the business requirement.
Choose a queue move
Set owner, experiment boundary, and revisit signal. Make clear whether the next step is evidence collection, a limited ranking test, or copy review. Preserve the before-state and query set so the change can be evaluated without memory of the dispute.
What to carry forward
Prioritize the smallest intervention that protects the affected search job while preserving a stated business constraint. The decision is ready when scope, risk, and revisit evidence are explicit. If the result order reflects an intentional tradeoff, queue explanation or grouping work rather than labeling relevance defective.
Technical background: Elastic documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow