The Graphic Design Process, Step by Step

The graphic design process is a loop, not a straight line from brief to finished file, and every time I have watched a team run it like a straight line the rework has shown up late and cost real money. It alternates divergent thinking (opening up, exploring many possibilities) with convergent thinking (narrowing to a single decision), and that alternation is the whole engine. I run Moonb, a creative studio, and nearly every version of the process I have taught or handed to a client sits on two named frameworks, so I name them before anything else.

The Double Diamond, formalized by the UK Design Council, splits the work into four phases across two diamonds: Discover, Define, Develop, Deliver. You open up, then narrow, then open up again, then narrow a second time. I keep this shape on the whiteboard for kickoffs because the two diamonds do most of the explaining for me.

Its user-centered cousin, Design Thinking from the Stanford d.school (Empathize, Define, Ideate, Prototype, Test), runs on the same underlying beat. Different labels, same rhythm of diverge then converge. On a real project those frameworks become practical stages, and I have watched one mistake sink almost every stage there is: committing to an answer before the divergent thinking has actually happened.

The frameworks line up against the stages like this, along with the specific way I watch each one break.

Stage	Double Diamond	Design Thinking	Mode	Where I watch it break
1. Brief	Sets up Discover	Empathize	Framing	Dictating the answer
2. Research	Discover	Empathize	Divergent	Skipping it to save a week
3. Ideation	Discover to Define	Ideate	Divergent	Editing ideas too early
4. Concepts	Define	Ideate to Prototype	Convergent	Jumping brief to one execution
5. Execution	Develop	Prototype	Convergent	Building without a system
6. Feedback	Develop	Test	Diverge then converge	Unstructured notes, too many cooks
7. Handoff	Deliver	Deliver	Convergent	Treating it as “send the files”

Stage 1: The brief (direction, not the answer)

A brief sets the direction and never the execution. On scoping calls I repeat one line until it sticks: a brief that dictates the exact answer is a failed brief. A strong one covers roughly seven things: the project summary and objectives, the target audience, the key message and brand guidelines, the deliverables and formats, the timeline and available spend, the success metrics, and the approval workflow. I write it jargon-free and leave the designer real room to explore, because a brief that spells out the solution has already made the design decisions, usually worse ones.

Stage 2: Research and discovery (before any software opens)

This is the Discover diamond, and it happens before a single pixel exists. It covers the audience, the brand’s current assets, a competitor and market visual audit, and above all the real problem worth solving. The job is to sharpen or reframe that problem so nothing downstream is built on a guess. When a project of mine has blown up in the final week, I can almost always trace it back to research we rushed or skipped, which is why I now refuse to let a team open Figma until this part is done.

Stage 3: Ideation (diverge, quantity over quality)

Now you open up, and the point is volume of raw ideas with judgment switched off, kept in quick disposable formats:

• Moodboards: deliberately ambiguous visual collections that chase a feel rather than a finished layout.
• Thumbnail sketches: fast, tiny, low-fidelity, testing composition and hierarchy rather than polish.
• Word and visual association maps.

I set a target here, something that sounds excessive like forty thumbnails, because the first ten ideas are almost always the obvious ones anyone would have reached anyway.

Stage 4: Concepts (converge to two or three directions)

This is the convergent phase most amateur processes skip by leaping straight from brief to a single execution. You rank and combine the pile, then narrow it to two or three distinct directions, each a different valid reading of the same brief. I present every concept with a rationale (why it answers the brief) rather than as a menu of interchangeable options, because the moment a client picks on taste alone, the conversation stops being about the work.

Stage 5: Execution and development

The chosen concept now gets built at full fidelity in the production tool, whether that is Figma, Illustrator, InDesign, or Photoshop. Every element is a decision: the typographic system, the color palette, the grid, the hierarchy and spacing, the imagery. Building with components and reusable styles here is what keeps a multi-asset project consistent and editable three months later, and I have inherited enough un-systemized files to know how expensive the alternative gets.

Stage 6: Feedback and iteration (structure it or drown in it)

Feedback is only worth anything if it is structured. I consolidate it into a single set of comments, tie each note back to the brief’s objectives, keep it specific (“this does not feel premium” tells the designer nothing), and route it all through one decision-maker. Two to three revision rounds is the accepted industry standard. Unmanaged feedback is the main engine of scope creep, so I agree a scope lock up front (what a round does and does not include) to protect the timeline. Iteration is where financial risk actually leaves the project, which is exactly why a real process treats revision as a core stage rather than a formality.

Stage 7: Delivery and handoff (a technical discipline)

Handoff is where the specs have to be exactly right, and getting them wrong is how good work arrives broken. Lock these down:

• Print: CMYK color, at least 300 DPI, at least 3mm (0.125in) of bleed, critical elements held a few millimetres inside the trim line, delivered as a press-ready PDF (PDF/X-1a), the format printers accept everywhere.
• Digital: RGB, exported as PNG, SVG, or JPEG at the resolutions each placement needs.

A professional handoff also ships organized, clearly-named files alongside the editable source and a short style guide, so the work keeps working after the designer walks away. I have been handed “final” files with no source and layers named “Layer 47 copy final FINAL,” and rebuilding from that costs more than the original design did.

Why the discipline pays off

This is not bureaucracy. McKinsey’s “Business Value of Design” study tracked 300 companies over five years and found the top design performers grew revenue and shareholder returns far faster than their peers. A disciplined process that alternates divergence with convergence, and de-risks the work through structured iteration, is what produces that gap. The classic mistake at every stage is the one I opened with: skipping the divergent thinking and committing too early.

At Moonb the design work runs through this exact process, with a senior Creative Director holding the line from brief to handoff as part of an embedded team. If you are weighing up who to hand a project to, I would put process ahead of portfolio gloss, because a strong portfolio can be one lucky first draft and a real process cannot. See how Moonb works.