Type, grid, hierarchy
Visual themes and typographic directions; Layout Logic works on grid structure and how the eye actually moves across the canvas.
For professionals — Designers & creative directors
The first idea is always the obvious one.
You know it's the obvious one. The problem is that getting past it takes hours you don't have, and the second idea is usually the first one wearing a different typeface.
The move
Ask what it's like.
Visual Metaphor is the mode most designers end up living in. It refuses to answer the brief literally and instead completes the sentence "this is like ___" — in texture, material, imagery and symbol.
It's the same move a good creative director makes in a review when they stop talking about the layout and ask what the thing feels like. Structurally, it's a lateral jump: you leave the problem's own vocabulary, which is exactly what breaks the obvious-idea loop.
A brief about a bank becomes a conversation about weight, patina and the sound a heavy door makes. That's where a form language comes from.
Working a brief
Concept, not decoration.
01
Seed the tension, not the deliverable
"Poster series" gives you posters. "A heritage brand that needs to stop looking nostalgic" gives you a concept. Seed the problem underneath the artefact.
02
Branch it once, neutrally
Topic Branching — the Graphic Design context's name for the neutral expansion slot — to map what's actually adjacent to the brief before you commit to a direction.
03
Switch to Visual Metaphor and go three deep
Metaphor on metaphor. The first ring is generic; the third is where the material language starts sounding specific enough to design from.
04
Turn constraints into the concept
Constraint Logic treats budget, format, light and site as design drivers — looking for the limit that could generate the idea rather than restrict it.
05
Synthesise two distant branches
The bridge between a material metaphor and a structural constraint is usually the concept you'd have taken a week to arrive at.
06
Keep the map as the rationale
The branch you took, visible next to the ones you rejected, is the clearest presentation of why this and not that you will ever build.
By discipline
Different contexts for different craft.
Form and hand
Ergonomic form and material combinations, with Assembly Logic on manufacturing constraints and part reduction.
Goal against friction
Feature and flow possibilities, plus Devil's Advocate and Success Metrics so a feature idea arrives with its own test.
Program and site
Spatial programs and circulation, Form Metaphor for material language, and the experiential sequence of moving through.
Cohesion across pieces
Silhouettes and materials, with Cohesion Logic naming what ties a collection together — and where it breaks.
Identity that's ownable
Positioning territories, archetype and metaphor, voice and tagline territory — cohering into a distinct identity.
The map is the rationale, not just the output.
Every client presentation includes the question "did you consider…?" A map where the rejected branches are still visible answers it before it's asked — and demonstrates that the chosen direction survived a field of alternatives rather than being the only thing anyone thought of.
Questions
The honest
ones.
Does it generate images?
No. It generates the thinking that comes before an image. Visual Prompts will convert a direction into a detailed, comma-separated prompt ready for an image generator, but Mindflov itself works in concept, metaphor and material language — deliberately, because deciding what to make is the harder half.
Won't leaning on AI flatten my work?
It would if you accepted the output. Mindflov over-generates on purpose so that the design act becomes selection: you pin two things and delete twenty. The map ends up looking like your judgement precisely because you removed most of what appeared on it.
The risk worth naming is different — using it as a shortcut past the discomfort that usually produces good work. It's most useful when you're genuinely stuck, least useful when you're avoiding starting.
I already keep a moodboard. Why this too?
A moodboard collects references you've found. This generates directions you haven't found yet, in language rather than images — which is often the missing step between "these six images feel right" and knowing why, well enough to design from it and defend it.
Which context if I direct across disciplines?
Keep one map per project and switch context as the work moves stage — Brand Architect while the identity is forming, Graphic Design or Industrial Design as it becomes artefact. The map holds everything; the context just changes what the next expansion reaches for.