If you have heard feedback which goes like this "Looks good to me."

What the feedback feels like: Woo-hoo! My design is working, yay!
What the feedback actually means: It's alright, let's move on.

After a lot of experience failing to ask the right questions, we've found these pointers have helped us elicit better feedback:

• Process of getting feedback should be conducted like a workshop. 
  The facilitation skills really pay-off to help your people get in the mode and get ready for the session ahead of them. 

• Setting the context and problem you are solving for feedback:
  - Let people know what problem you are trying to solve quickly.
  - Also, mention what you have accomplished and your progress.
  - Be direct & specific so that they do not focus on aspects that are not ready.

• Start with options to streamline the process and avoid impatience.
  - Showcase edge-case and use-case thinking by opening up the options.
  - Exhibit pattern-level thinking by showing versions in granular-level screens.

• Collect Feedback the Next Day (If Possible)
  People tend to connect the dots better when there's a break, and they have time to think about the design. I've observed better design feedback shared after a day has passed and followed up on.

• Ask them: what's good, bad, and ugly?
  I've found when we ask for specific feedback, it provides specific answers on what's good, bad, and ugly. This makes it easier for people to distill feedback.

• For the next time you review the same problem, 
  - Show them the before and after. This way, you can provide context and demonstrate the newest possible solution to your stakeholders.

  
  

Good luck and Happy Feedback time!