01
Start with the job, not the art
We're not picking the prettiest mark — we're picking the one that best does a job. Quick reminder of that job: signal credible, international, institutional to a healthcare CEO; hold up next to the Chamber, Vanderbilt, and Global Health Connector; work everywhere from a favicon to a banner. Everything below is easier if we keep measuring against that.
02
Try "this works for ___ because"
Taste is hard to act on; fit is easy. Instead of "I like #3," something like "#3 works for reaching executives because it feels established" gives us a reason we can weigh. And "#5 might be a problem on a name badge because the frame gets busy" is gold — it's a real, fixable observation.
03
Bring the problem; let the designer bring the fix
The most useful notes point at a problem, not a solution. "The G closes up when it's small" helps more than "make the G rounder" — it tells the designer what to solve and leaves them room to solve it well. If a note doesn't tie back to the job, it's probably a preference (which is fine to name, just good to label).
04
Reactions welcome, votes not needed
This isn't a tally. One sharp observation about how a mark will behave in the real world is worth more than five thumbs-ups. Rob owns the final call — the group's job is to surface what he can't see alone, so honest reactions help most.
05
Three separate decisions
It's easy to blur these, so let's keep them apart: the concept/mark (does the idea serve the program?), the typeface (legible? right tone?), and color — which we're deliberately leaving out today. That's why everything's in grayscale; don't let a gray render talk you out of a mark.
06
It's fine to set options down
Four of these five won't get used, and that's the point of showing five. Setting a mark aside isn't a knock on it — it just wasn't the right tool for this particular job. No need to defend one out of politeness.