Inspect the example
Start with the owned sample so you can learn the critique method without uploading your design.
IroGuide docs
Learn the critique method, then make a better first decision.
A practical documentation hub for new users, beginners, students, creators, and advanced learners who want a practical evidence-to-action method before personalized review becomes available.
Free example
Start with a clean loop.
Every useful critique begins with a visible decision, a relevant goal, and one prioritized action.
Find the evidence
Name the exact visual decision you can see before deciding whether it helps or hurts the goal.
Understand why
Connect the observation to hierarchy, readability, audience, purpose, or another relevant principle.
Act on the first fix
Start with the highest-impact recommendation before polishing secondary details.
Learning paths
Use IroGuide differently as your skill grows.
Understand what to submit
- Pick one design problem
- Write a short brief
- Review the top issue first
Build critique habits
- Compare hierarchy and spacing
- Track repeated comments
- Save before and after versions
Pressure-test decisions
- Use stricter context
- Ask follow-up questions
- Convert critique into a design rationale
Core concepts
What IroGuide is optimizing for.
IroGuide is built to explain design decisions, not replace them. The best results come from strong context.
Context controls the answer
A portfolio cover, ad creative, app screen, and event poster should not be judged with the same criteria.
Scores are directional
Use score changes to spot movement, but rely on the written priorities when choosing what to fix next.
Private by default
Saved reviews stay in your signed-in workspace unless you intentionally share or publish a critique.
Audience matters
Stronger prompts describe who must understand, trust, click, buy, attend, or remember the design.
Advanced practice
Turn critique into a repeatable design system habit.
Advanced learners get more value when they ask narrower questions, document reasoning, and compare changes against the same objective.
- Submit one design direction at a time so feedback stays specific.
- Name the constraint that matters most, such as conversion, readability, premium tone, or brand recall.
- Use follow-up chat to clarify tradeoffs instead of asking for a full second review immediately.
- Treat every recommendation as a design hypothesis, then validate it against the audience and format.
Reference