32. Design research in parallel
📣 Real-user report — shared publicly by a Muse user, not independently verified.
The job: A designer hands Muse the pre-design research: it finds landing pages in a niche, spots patterns across them, and organizes the references — while he keeps working.
I'm about to design [a landing page for a dev-tools SaaS]. Research landing pages in this space: find [12] strong examples, identify the recurring patterns (hero structure, social proof placement, CTA copy, pricing presentation), and organize the useful references into a swipe file grouped by pattern. Deliver it as [a Notion page / markdown doc] I can use as context when I start designing.
What Muse will do:
- Define the niche and the number of examples you want
- Ask Muse to find strong landing pages in that space
- Have it extract recurring patterns across them
- Get the references organized into a swipe file grouped by pattern
- Use the swipe file as context for design direction, visuals, and build
Why it works: research is the most parallelizable part of design — Muse browses and organizes while you stay in flow. The swipe file becomes reusable context for every downstream step (direction, visuals, motion, build).
Common failures:
- Muse can only research what's publicly browsable — gated or login-walled galleries won't work
- Pattern-spotting is taste-adjacent; review the swipe file before treating it as direction
Reported by @DesignByMoein on X · Sep 2026
Loading comments…