Whose Budget, Whose Purpose?

There are things I would like to make simply because I like them. I may be drawn to a particular pace, an image, or a way of telling a story. Those preferences are part of being a maker.

But a project funded by a client carries a different responsibility. If I want the freedom to make exactly what I want, I can pursue it with my own money. When I accept someone else's budget, I need to understand and serve the purpose they are paying to achieve.

The question is not only whether the result looks good to me. It is whether the commissioning organisation can be satisfied with what it has asked us to make.

The budget belongs to a purpose

A client may need to explain an activity, introduce a service, communicate an institution's identity, or support a particular event. The requested film or website is a means of doing that.

The brief does not always explain the whole purpose at first. Some expectations may be familiar inside the organisation but unfamiliar to the person making the work. Understanding them requires questions, not assumptions about what a “good” result should look like.

This does not make the maker's professional judgment less important. It gives that judgment a context. My experience should help the organisation achieve its aim, rather than quietly replace that aim with my own.

Self-funded work gives me room to choose the question I want to explore. Commissioned work begins with a purpose someone else has entrusted to me. I need to be honest about which kind of work I am doing.

Taste should contribute to a decision

I do not think I need to remove my taste from client work. Taste helps me notice rhythm, clarity, unnecessary detail, and choices that weaken a result. It is part of what I bring.

But when I recommend a direction, I should be able to explain how it helps this project. Saying that I prefer it is different from showing why it makes the message clearer or suits the intended use.

A minimal composition may look elegant to me while leaving out information the organisation needs to communicate. A sequence that impresses another producer may be difficult for an unfamiliar audience to follow.

Those are reasons to test a preference against the purpose, not reasons to abandon all preferences. The important distinction is whether my taste is helping the work or becoming a private standard the client never agreed to.

Satisfaction needs a shared reference

“Make it good” leaves a great deal unresolved. So do words such as “modern,” “warm,” or “impactful.” People can use the same word while imagining very different results.

We need more specific references. Where will the result be used? Who will encounter it? What must they understand? What information cannot be omitted? What was unsatisfactory about an earlier version?

An outline, a proposed structure, or a relevant example gives us something to discuss together. It helps reveal differences that can remain hidden in a conversation made only of adjectives.

The discussion is not complete because I have explained my proposal. I also need to understand what the client has accepted and why. A shared reference makes later revisions easier to discuss because we can see which expectation has changed.

Professional advice should help the client judge

There are times when a request seems poorly suited to its purpose. It may scatter the emphasis, leave an important explanation out, or require more time than the available schedule allows.

I should say so. I should explain the likely consequence and offer a more suitable option. Avoiding that discussion would not be respectful if it left the client unable to make an informed decision.

Then I need to listen to the reason behind the request. There may be an internal requirement, an intended setting, or a practical constraint that I do not yet know. An idea cannot be judged fully without understanding where it will be used.

If the direction changes, the effect on time, scope, and cost needs to be discussed as well. Serving the client's purpose includes making those trade-offs visible. It does not mean promising every change without considering its consequences.

The organisation's needs must reach its audience

The commissioning organisation and the audience may approach the same result differently. The organisation knows its activities well and wants to communicate what matters to it. A viewer may arrive knowing very little and need a clear way into the subject.

Part of my work is to connect those perspectives. The organisation's important information needs to be presented in a sequence someone outside it can understand.

This is also why satisfaction should not be treated as a last-minute approval. The purpose needs to remain visible while we plan, select material, edit, and respond to feedback. A usable result gives the organisation a stronger reason to remain satisfied after delivery.

At the end, I want to be able to ask whether I understood what was entrusted to me, protected it through the work, and explained my decisions clearly enough for the client to judge them.

I want to work as a maker with a point of view. I also want that point of view to be useful to the people who hire me. When another organisation pays for the work, meeting its needs is not a compromise I reluctantly accept. It is part of the responsibility I agreed to carry.