Start with an agreed outcome

A busy team can produce many files without moving closer to a decision. Begin each project with a short brief: the audience, the problem, the deliverables, the deadline and the person who can approve the work. Add examples of what success would look like, such as a readable product page or a consistent set of campaign images.

Keep the brief in one place and date important changes. If the objective changes, acknowledge the effect on scope or timing. This makes a revised direction visible instead of leaving team members to reconcile different conversations.

Give every task an owner

For each deliverable, identify who creates it, who reviews it and who makes the final decision. These can be the same person in a small team. What matters is that responsibility is clear. A shared board with “Brief”, “In progress”, “Review” and “Approved” can be enough to begin.

Break work into outcomes that can be checked. “Prepare three approved product crops” is easier to review than “work on content”. Attach the latest file and the relevant brief to the task. Limit simultaneous work when too many open tasks are delaying completion.

Make feedback usable

Review the idea before polishing every detail. At the concept stage, discuss whether the direction serves the audience and message. At the production stage, review typography, crops, colour and factual accuracy. Separating these conversations helps avoid rebuilding a finished asset because the core idea was never agreed.

Write feedback against a visible version. Explain the problem, not just a personal preference: “The product name is difficult to read at phone size” gives the designer something to solve. Combine comments before sending them back and distinguish required changes from suggestions.

Finish with a reliable handover

An approved image is only part of delivery. Include the final exports, editable source, usage notes and any limitations on images, music or talent. Use filenames that identify the project, format and version. Keep obsolete exports separate so they are not accidentally published.

After launch, spend a short session discussing what delayed the work and what helped it. Choose one process improvement for the next project rather than adding many rules at once. This workflow is a practical starting point; adapt it to the size and responsibilities of your own team.

Try it in your next project

Brief

Audience + objective

Named owner
In progress

Product photographs

Named owner
Review

Check copy + crop

Named owner
Approved

Web exports

Named owner

An example board: each deliverable has an owner and a visible review stage.

Opening image: an AI-generated concept scene illustrating the creative process.

← Back to the journal