RHILLANE Ayoub · September 23, 2026
The file was called final_v9. It had been saved at 21:40 on a Saturday.
I noticed it the way you notice these things, sideways, while looking for something else in a shared folder on a Monday morning. Our designer had been with us a bit over a year, was twenty-six, and was good. She had also, according to the version history I then went back and read properly, saved work on eleven of the previous fourteen weekends.
Nobody had asked her to. That was the part that bothered me most, because it meant nobody had noticed either, and I run a team of fifteen people spread across Morocco, Dubai, and the United States where noticing is most of the job.
What Was Actually Happening
I asked her about it and the answer took forty seconds to arrive and about six months to fix.
The client, a retail chain, had a marketing coordinator who had discovered something convenient. Instead of routing requests through the scheduled process, she messaged the designer directly. Small things. A resize for a different placement. One more color option. A version for a partner's channel.
Each request took twenty minutes and each one arrived phrased as a favor, and the designer, who was twenty-six and speaking to the person representing the account that paid part of her salary, said yes every single time.
Twenty minutes, forty times a month, is thirteen hours. Thirteen hours a month that were never scoped, never billed, and had to come from somewhere, and where they came from was Saturday.
She was not being weak. She was being asked to do something I had never trained her to do, never given her permission to do, and never done in front of her. I had asked a designer to be a commercial negotiator with a buyer, in writing, alone, in real time.
A designer working late at a desk, the pattern that revealed unscoped client requests were being absorbed by one team member. Photo by Vitaly Gariev on Unsplash.
The Management Reflex That Was Wrong
My instinct, the first day, was to coach her. Teach her how to push back. Give her some phrases. That instinct is extremely common among small business owners and it is usually a way of turning a structural problem into a personal development plan for somebody else.
The structural problem was this: the person doing the work should never be the person defending the scope of the work. Those are opposing jobs. One requires you to be helpful, responsive, and invested in the client's outcome. The other requires you to be willing to disappoint that same person before lunch. Asking one employee to hold both is a design flaw, and the more conscientious the employee, the faster the flaw shows up as unpaid weekends.
Harvard Business Review's body of work on delegation keeps landing on the same point from different directions, which is that delegating a task without delegating the authority that makes the task possible is not delegation at all. I had delegated the design work and kept none of the protection that should have traveled with it.
What We Changed
Four things, and only one of them was a rule about clients:
- Every scope conversation routes to an account lead, never the person producing the work. If a client messages a specialist with a new request, the specialist's entire job is one sentence: "Let me get that to your account lead today." She does not judge whether it is in scope. She does not have to.
- Anything outside the agreed scope gets a written change note within one working day. One short paragraph naming what was asked, what it costs in hours, and whether we are absorbing it or pricing it. Half of them say, "we are doing this at no cost, noting it so you can see the pattern." That sentence has repriced more accounts than any negotiation tactic I have used.
- A standing thirty-minute slot each week where the client can raise anything. Most of the direct messaging was not manipulation, it was impatience. Give people a predictable door and a surprising number of them stop climbing through the window.
- I say no in front of the team, out loud, on calls they are on. This one mattered more than the other three combined. A rule in a document tells people what is permitted. Watching your boss tell a paying client that something is not included, in a normal tone of voice, with no drama, tells them it is survivable.
A manager leading a small business team meeting where client requests and scope are discussed openly. Photo by Christina @ wocintechchat.com M on Unsplash.
The Part That Surprised Me
I expected friction. What actually happened with that retail client was that their coordinator sent one slightly cool message, then adapted within a fortnight, and four months later the account renewed at $1,400 a month more because the change notes had made visible a volume of work nobody on their side had known was happening.
Across the whole book of clients, unbilled hours logged against active retainers dropped from around 64 a month to 11 over the following quarter. That was not the point, but it was the number that made the change permanent, because it turned a management instinct into something the business could see.
The designer is still with us. She now runs the account lead conversation herself on two clients, which she can do precisely because she was never forced to learn it while exhausted and outranked.
What This Actually Taught Me About Managing People
Most management advice for small business owners is about motivation. Very little of it is about the fact that a team member's willingness to please is a resource that will be spent by whoever is nearest, and that protecting it is a management job rather than a personality trait you hope your staff arrive with.
Because a digital marketing agency like ours sells retained hours of specialist time rather than units of product, the pressure in our case arrives as client requests landing on a designer or a paid media specialist mid-campaign. In a shop it comes from a customer who wants a discount and asks the youngest person on the floor. In a workshop, it comes from a supplier renegotiating with whoever answers the phone. The mechanism is identical. Somebody with less power than the person asking is placed at the point of contact and left there without cover.
Gallup's long-running research on what actually drives engagement at work puts clarity of expectations at the base of everything else, ahead of recognition and development. An employee absorbing undefined requests from a client has no clarity of expectations by definition, no matter how many times you tell her the team appreciates her.
You find out whether you are giving cover by looking at timestamps, not by asking people if they are fine.
They will say they are fine. They said yes to the client for the same reason.
If your team keeps absorbing work nobody agreed to, the fix is almost never a conversation with your team. We help founders build the account structure that stops it at Rhillane Marketing Digital, the digital marketing agency I run across Morocco, Dubai, and the United States.