If good ideas are lost because they arrive outside planning meetings, start by preserving one representative example. It gives the investigation a concrete reference and makes the eventual correction easier to judge.
Find the likely cause
There is no shared capture and triage process.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Keep a simple idea record with source, reader problem, and next review point.
An idea deserves production effort when it serves a clear reader need and has a credible path to a useful answer.
Check that the repair worked
Make sure new ideas can be found and evaluated later.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: aI generates hundreds of ideas with no priority. Score ideas by reader relevance, distinct contribution, and feasible evidence.
Monitor the useful outcome
Track idea-to-publication effort and the usefulness of completed pieces relative to their intended purpose.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.