You hired an expert, so let them be one

By · Published · Updated

You hire an expert because you don’t know their field. Then you often approve every detail of their work yourself, and that can stall a website project.

I was talking with someone who runs a design agency, and I told him what I’m trying to crack with clients: “This whole idea that they hire us because they don’t know this shit. But then they are the ones approving the work. It’s so weird. If you hire a plumber, I’m not approving their rounds.”

A website project is two jobs. Deciding what success looks like is yours, and deciding how to get there is the expert’s. Most approval processes blur the two. Owners can end up redesigning the homepage in a comment thread.

The useful question is whether a change gets you closer to the goal.

Staying involved is fine. Just change what you approve. Sign off on the messaging framework first, on its own, before anyone designs anything. After that, judge each page by outcomes: does it make the right people curious, and does the headline keep a stranger reading? Whether you like the font is the expert’s call. “You don’t want to pay me to go back and forth, back and forth, back and forth.”

Judging whether the work is working is the part of the project only you can do. In Webflow it’s literally a different mode: “You’re either editing or you’re designing, and I want you to be editing.”