<aside> 💡 I can’t tell you anything you don’t already know. But I’d like to clarify a few things. — JOE FERRARA

</aside>

To review an already built product:

  1. Try using the product, do the things users will do with it.
  2. Note the place where users are likely to get stuck or things that will confuse them.
  3. Sometimes watch other people trying to use the product.
  4. Help the team decide which ones are most important to fix and how best to fix them.
  5. Having a presentation is much better than preparing a “big honking report” detailing the findings, as it allows QnA and team can voice their concerns.

<aside> 💡 Almost always. Even when people know about usability problem, they can’t always fix them completely.

</aside>

<aside> 💡 Usability principle: If something requires a large investment of time — or looks like it will — it’s less likely to be used.

</aside>

<aside> 💡 I’ve always liked the passage in A Study in Scarlet where Dr. Watson is shocked to learn that Sherlock Holmes doesn’t know that the earth travels around the sun. Given the finite capacity of the human brain, Holmes explains, he can’t afford to have useless facts elbowing out the useful ones:

“What the deuce is it to me? You say that we go round the sun. If we went round the moon it would not make a pennyworth of difference to me or to my work.”

</aside>

Usability Attributes: