🎟 Ever wanted to create your own font? Sign up to our live & interactive workshop with Dribbble’s co-founder Dan Cederholm on December 15 🎟
Trending designs to inspire you
Work designers are riffing on
Interviews, tutorials, and more
Prompt to flex your design skills
Find your dream design job
An exclusive list for contract work
Get new leads in your inbox every day
Introduce yourself to new clients with Pitch
A marketplace of digital assets…
Icons, Illustrations, Patterns, Textures…
Display, Script, Sans Serif, Serif…
Mock Ups, Social Media, Presentations…
Characters, Objects, Textures…
WordPress, Shopify, Bootstrap, HTML5…
Procreate, Affinity, Photoshop, InDesign…
Earn money doing what you love
Find, contact, and hire designers
The #1 job board for creatives
Board for freelance & contract work
I've posted a few of these before, but this iterative system-level work is one of my favorite parts of a product design process.
Products are (complex) systems, and it's helpful to map everything at out a high level before anything gets fully 'designed', prototyped or built. This kind of artifact is a hybrid of traditional sitemaps, flowcharts, and wireframes. The benefit is that you can start to make UI-level decisions & establish consistent patterns quickly, while maintaining a relational understanding of how everything fits together. This kind of artifact is also easy shareable and understood by designers, engineers and managers (and for most clients with the right walk-through).
From here, it's easy to break down screens into user stories (or vice versa), plan / prioritize sprints in tools like Trello, and jump into high-fidelity wires and prototypes.
Information can be beautiful too, and wish I saw more of this kind of stuff on Dribbble.