My two cents
Here is one structure that I like to use to synthesise learnings made from user tests in a way that pushes the team to stay focused and practical:
Validated: things we had as the hypothesis that worked well during the testing. These are things we don't need to discuss further or change. If needed, you can further divide this into "validated and important" versus "validated but less important than what we thought"
To work on: things we need to adapt or decide on. These elements are validated as enough different people mentioned the same idea. If needed, you can further divide this into "To discuss and decide" for things where you could keep things as is and "To change or clarify in prototype" for things that you already know need to be changed.
Inspirations: things that are not validated but are nevertheless inspiring. These are elements that you can review and draw inspiration from.
Below you can see in a video a real-world case where I used this structure: