Findings are not improvements. Twelve logged usability issues, a benchmark that dropped four points, a review full of red flags — none of it has changed anything for a single user yet.
Turning findings into changes takes three unglamorous steps. Rank them by how badly they hurt and how many people they hit; effort decides the order within a band, not whether a severe problem gets fixed at all. Decide what you are changing and what you are knowingly leaving alone, and write that second list down, or you will argue it again every month. Then put the revised design back in front of people.
Most of that deciding happens with other people in the room. A badly run hour goes on a button label and never reaches the twelve issues.
Critiques & Reviews
A critique is not an approval meeting and not a taste contest. It exists because two weeks with a design makes you blind to it. Invite four or five people who are not — someone who knows the users, someone who has to build it.
Open with the problem and the constraints, then say what you want feedback on — "the order of these three steps", not "thoughts?". An open floor produces opinions about corner radii.
Feedback comes as an observation plus a reason: nothing earlier uses the word "workspace", so a first-time user will not know what it means. An alternative counts too, if it arrives with the problem it solves. "I don't like it" is the one thing nobody can act on.
The designer takes the notes and makes the call. A critique that ends in a vote has no author left.