All musings

The point of a processis not to slow the work down.

Creative work gets messy when nobody knows where they are.

No. 09 A seven-minute read Filed under: Process & momentum

That sounds obvious, but it is one of the most common reasons projects drift. Not because people are lazy. Not because the idea is bad. Usually because everyone is carrying a slightly different version of the brief in their head.

The client thinks the goal is one thing. The designer is solving a different thing. The developer is waiting for decisions that were never made. The copy is trying to hold the strategy together. Feedback arrives late, or sideways, or from someone who has only just seen the work.

That is how projects become expensive.

A process is not there to make the work feel formal. It is there to stop the wrong kind of chaos from taking over.

That is why we use the QC Process.

Good work needs a shared starting point

The first step is Consult.

Before we design, write, build or campaign, we need to understand what the work is supposed to change. That means talking through the business, the audience, the problem, the pressure points and the things that have already been tried.

A good consultation is not a sales call with nicer lighting. It is a way of finding the real brief.

Sometimes the real brief is obvious. Sometimes it is hiding behind a requested deliverable.

A client may ask for a new website when the deeper issue is service clarity. They may ask for a campaign when the brand architecture is doing too much damage underneath. They may ask for content when the offer itself needs to be sharpened.

The earlier we find that out, the less everyone pays for it later.

Collecting is creative work too

Collect sounds administrative.

It is not.

Brand guidelines, analytics, old pitch decks, campaign reports, customer research, stakeholder notes, photography, product information, previous design work, competitor examples, internal language, sales objections. This material shows how the organisation currently explains itself.

Some of it will be useful. Some of it will be out of date. Some of it will contradict itself.

That is the point.

You can learn a lot from the gaps between what a business says, what it sells, what customers ask for and what the website currently explains.

Good creative work does not begin with a blank page. It begins with evidence.

Collaboration is not design by committee

Collaborate is where the direction starts to take shape.

This does not mean every person gets to steer every decision. That usually produces safe work with no edge. But it does mean the right people need to be involved early enough to shape the thinking, not just approve the output.

There is a big difference.

Late feedback often sounds like taste. Early input often reveals constraints, priorities and opportunities.

A founder may know the sentence customers repeat back. A sales lead may know where prospects get confused. A support team may know which product feature creates the most friction. A marketing manager may know which promise performs, but also which one the business cannot keep.

Those details matter.

Collaboration works best when it gives the creative team sharper material, not when it waters the work down.

Plans protect momentum

Coordinate is the part clients rarely see as creative, but it is one of the most important parts of the job.

A clear plan answers simple questions before they become problems.

What are we making?
Who is responsible for what?
What needs to be approved?
What can move in parallel?
What is the order of decisions?
What does done look like?

Without that structure, projects often feel busy without moving forward.

A good plan does not remove flexibility. It gives the project enough shape that flexibility is useful. When something changes, everyone can see what it affects.

That is the difference between adapting and drifting.

Concepts make the invisible visible

Conceive is where ideas become something people can react to.

A strategy document can be useful. A moodboard can help. But sooner or later, people need to see how the thinking behaves in the real world.

A homepage concept. A campaign route. A messaging sample. A brand system test. A prototype. A rough execution.

These early samples are not the finished work. They are proof of direction.

They help everyone answer better questions. Does the idea stretch? Does the tone feel right? Can the system handle different messages? Does the brand still feel like itself? Is the work clear before it is polished?

This stage saves time because it tests the thinking before the whole machine starts moving.

Making is where the process earns its keep

Create is the visible part.

This is where the design is built out, the copy is written, the assets are produced, the site comes together, the templates take shape, the campaign becomes real.

It is tempting to treat this as the main event.

But the quality of this stage usually depends on the stages before it. If the brief is clear, the assets are gathered, the direction is agreed and the plan is sensible, making can move quickly without becoming frantic.

If those things are missing, the create phase becomes a rescue mission.

That is when teams start solving strategy problems inside design files, content problems inside layouts and approval problems inside revision rounds.

Nobody enjoys that.

Refinement is not failure

Clarify is where the work gets better.

Feedback should not be treated as an interruption. Used properly, it is part of the craft.

The important thing is to know what kind of feedback you are dealing with. Some feedback sharpens the work. Some reveals a missed requirement. Some points to a real audience issue. Some is just personal preference wearing a serious hat.

A good process gives feedback somewhere to go.

It lets the team sort signal from noise, adjust what needs adjusting and protect the parts of the work that are doing their job.

Refinement is not about sanding everything smooth. It is about making the work clearer, stronger and more useful.

Count what matters

Count is where the project stops being judged only by how it felt in the room.

Not every piece of creative work has the same metric. A website might need cleaner enquiries, better service navigation or stronger conversion. A brand project might need consistency, recognition and easier rollout. A campaign might need reach, response, leads or sales. A content project might need engagement, search visibility or better sales enablement.

The point is to decide what success should mean for the work at hand.

Measurement will not tell you everything. Some brand effects are slow. Some value is qualitative. Some of the best work changes how a team speaks about itself before it changes a dashboard.

Still, counting matters.

It keeps the work honest.

And yes, celebrate

The QC Process also makes room to celebrate.

That might sound small, but it is not.

Good projects take energy from both sides. Clients give time, attention, feedback, decisions and trust. Creative teams give thinking, craft, care and a fair amount of emotional stamina.

When the work is done, it is worth acknowledging that.

Not with empty applause. With a pause. A look at what changed. A clear handover. A proper launch. A shared sense that the thing has moved from idea to asset.

Then the next job starts from a better place.

The process is there to keep the work useful

The best creative process should feel calm, not heavy.

It should give the project enough structure that people can make good decisions. It should keep the client involved without making them manage the work. It should protect the team from guessing. It should create space for ideas without pretending that ideas are enough on their own.

That is what the QC Process is for.

Consult. Collect. Collaborate.
Coordinate. Conceive. Create.
Clarify. Count. Celebrate.

Not because alliteration is cute.

Because creative work is better when people know what is happening, why it matters and what comes next.

Offbrand is the Qualls journal: industry musings on messy briefs, useful brands and the work in between.

Start here

Want the calm version
of your next project?

Start the conversation