I am stuck on a design critique that stays specific. I need to critique hierarchy, spacing, flow, and content without falling back to taste, but my current attempt is getting vague and too big. What would you check first?
I needed a usable answer on a design critique that stays specific
This started as a messy question about a design critique that stays specific. The follow-up made the answer practical.
First, shrink the decision. Do not solve the whole subject at once.
- Name the user decision first.
- Check the keyboard path.
- Remove one competing action.
Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.
The smaller decision was the missing piece. I was asking for the whole system at once.
4 comments
Sign in to join the conversation.