In a well-run critique, we explicitly separate out the discussion of “What are we trying to do with this design?” from the discussion of “Does this rendition accomplish it?” By separating out these two pieces, we avoid digging into the designer’s work just because they unaware of a critical requirement or need.
It doesn’t matter if you’re a designer, an HR pro, whatever. Go read this post by Jared Spool on a better design critique process right now. It’s awesome.
Hat tip to Rian van der Merwe.
🔥 Hot off the press! I just launched a new pocket guide. Learn about ES6 arrow functions,
const, function hoisting, and more.