016 - How to Run A Design Critique (feat. Ben Peck)

016 Ben Peck.jpg

Design critiques are a great way for a designer to get feedback from his/her design team. However, depending on the way they are facilitated or the manner of which a designer asks for feedback, sometimes they don't always turn out so great.

Knowing the value of feedback from design peers, how can we as design teams create a critique process that doesn't lead to negative, out of context or unproductive advice that can hurt designs or even bruise a designer's pride in the process?

Patrick and Andy met with Ben Peck to discuss the challenges that deign teams face when participating in regular design critiques and how we can make them more productive and helpful for all involved. 


  • How to build a proper critique process that will work for your team.
  • What sort of critique guidelines can help designers to give/receive productive feedback.  
  • How to streamline rapid feedback during the critique and record the information given to the presenter for later review.

And much more...



Ben Peck is a Product Design Director at Jane coming from over a decade of design experience working with software companies that have partnered with brands such as Nike, The North Face, Oakley, Under Armour, and Sonos. Ben is focused on designing Jane’s software and products to significantly impact the user experience needs of our consumers and sellers.

Ben is also the cofounder of the Front Conference, a product design and management conference held in Utah which is on it 4rd year, as well as the Director of Product Hive with over 3,000+ product designers and product managers.



Did you know that we rebooted Lunch UX? Our first event is scheduled for June 29th. Patrick will be kicking it off the with a workshop where you can learn how to properly add friction to your designs. 

 If you haven't signed up yet, it's okay, it's not too late to redeem yourself. RSVP here.

015 - How to Front, a special conference episode featuring Andy and Patrick

015 how to front.jpg

Andy and Patrick went to Front! They spent 2 days conferencing it up in local SLC, learning how to build better product from awesome designers, researchers, leaders and product managers. Now, it's time they shared what they learned.

For this very special episode, Andy and Patrick sit down with each other to go over notes and imperssions gleaned from the 14 talks, random encounters and overall adventures had at front. 





  • Designing for accessibility and diversity and avoiding bias in design teams
  • Understanding users habits 
  • Using intuition to make design decisions
  • Allowing teams to make mistakes and shipping imperfect products
  • Unity over conformity with design systems and alignment

And much, much more...

Speakers discussed:

Benjamin Evans | Design lead - Airbnb

Aryel Cianflone | UX researcher - LinkedIn

Vickie Tan | Product designer - Headspace

Tim Van Damme | Principle designer - Abstract

Adrienne Gajownik | Principle designer - Pendo

Brian Crofts | CPO - Pendo

Cameron Moll | Speaker, Author and Design manager - Facebook

P.S. We are rebooting LunchUX - join us!

014 - How to Avoid Designing Only the Happy Path with Andrew Ditto

Andrew Ditto 014.jpg

Designers solve problems, it's what we do. However, when it comes to solving problems through experience design, we sometimes tend to only focus the "happy path" - the journey our users will take when they successfully complete a design solution.

But what about the "not so happy path"? What happens when an error occurs, or a certain user cannot interpret the design correctly? Many of us designers can admit that we have shipped designs that have only accounted for the solution and not the potential problems it can cause our users along the way. 

Andy and Patrick sat down with Andrew Ditto, a Quality Assurance Engineer at Canopy, to learn about how designers can get better at creating design solutions that also account for the "not so happy path".


  • What techniques quality assurance engineers employ to uncover bugs or potential user experience flaws in the design. 
  • How quality assurance engineers gain the empathy necessary to understand how users will break a design and how can designers tap into that knowledge.
  • How designers can learn to be more humble and parter with quality assurance to design "happy path" solutions while also accounting for the potential, "not so happy path" scenarios their users may encounter.



Andrew Ditto is a Quality Assurance Engineer at Canopy and a mad scientist who thinks Fahrenheit is BS and who the hell used Pascal anyway?