Atiba de Souza.Start a conversation
WritingLeadership

They Wanted Stick Figures: What Your Angriest Customer Is Actually Telling You

By Atiba de Souza

Atiba de Souza sitting on a couch with his hand resting on his chin, appearing thoughtful. The cover reads: LEADERSHIP Complaint arrives First move

Three and a half weeks, and they wanted stick figures

I spent three and a half weeks teaching an image engine to produce convincing, realistic human scenes. Version two, for my pharmacy-industry partners. I thought it was phenomenal. I sent it over expecting it to land.

It didn't. They hated the realistic imagery. They would rather have stick figures.

Read that again, because the shape of it matters more than the subject. Three and a half weeks of work that was not rejected for being bad. It was rejected for being the wrong thing, made excellently.

Yes, my feelings were hurt. Yes, I was pissed. I say that part out loud on purpose. You are going to get your version of this, and I do not want you blindsided by your own reaction when it lands.

Here is the fork, and it is not the one people assume. The reflex is to hear the complaint as a verdict on the work. A grade. So you defend the imagery. You mention the three and a half weeks. You take the feedback seriously by spending one more cycle making the exact thing better that they already told you they do not want.

The rejection cost me nothing. The cycle after the rejection is the expensive part.

Three and a half weeks of excellent work, and the sentence that killed it was free. You cannot buy research that good. You can only refuse to hear it.

The fear is real, and it comes back three times

I know what you are afraid of in that moment, because I have been afraid of it. It is not the refund. It is not the lost sale. It is that if you do not defend the work, you have just agreed the work was not good enough.

That fear is real, and it is not a character flaw. But here is what a clean framework will never tell you. It is not a gate you pass through once at the beginning. It comes back. It comes back three times while you design the response to a complaint, and it wears a different costume each time.

It shows up when you sit down to write the Win and see what an honest Win actually costs you.

It shows up when you pick the one step to fix and realize you are leaving two other things on the floor.

It shows up when you have to put the cheapest version of your idea in front of a human before it is ready to be seen.

If a complaint process hands you five tidy steps and never mentions that, it is not a process. It is a poster. So let's use the real thing.

The framework: the 7 Practices of Effective Marketing

Everything my team builds runs on the 7 Practices of Effective Marketing. The framework treats marketing as communication, and it puts the ICP first, before any tactic ever gets named. Three of the seven carry almost all the weight with an angry customer: The Win, Thinking Steps Not Tactics, and Narrow the Focus.

You should know exactly what this framework claims and what it does not. It does not rank those three for you. The one ordering claim it makes is blunt: no tactic gets proposed until the steps exist.

Which means the moment a customer complains and your first thought is a refund, a coupon, or a paragraph your team can copy and paste, you have proposed a tactic before you have a step. We go in order.

Tactic before step

Win, Steps, Focus

Defend the work

Hear it

Complaint arrives

First move

Busy, goes nowhere

Write The Win

Map steps, not gestures

Narrow to one step

Which branch

Pay the same cycle again

Pay the admission: I built the wrong thing well

Practice 1: Write The Win before you write a word

The Win: a measurable outcome statement that every downstream step and artifact gets evaluated against. On a complaint, "the ticket is closed" is not a Win. A closed ticket is cleanup.

If your Win is a closed ticket, you will build a fast, polite, cheap machine that closes tickets, and every apology script and refund tier gets evaluated against closing. It will work. That is the trap. It works. You close the ticket and lose the customer in the same motion, and nothing in your reporting can see it, because the Win you wrote down was never about them.

Now the fear. This is the first place it shows up. Writing "they come back" as your Win means the number you have been winning on, closed fast, closed politely, stops being the number. You are about to trade a metric you hit every week for a metric you cannot control. That is why your hand hovers over the keyboard.

Write it anyway, and write it as the thing you actually want. One sentence. This customer buys again. This customer renews. This customer sends somebody. The moment that is your Win, the finish line moves. "They stopped being angry" is no longer the end. It is not even the middle.

Practice 2: Steps, not gestures

Thinking Steps Not Tactics: an ordered sequence of steps from the current state to The Win, with dependencies identified. A refund is a tactic. It lives inside a step. It is not the step.

The instinct in marketing is to jump straight to tactics. Funnels, ads, launches, campaigns. On a complaint the same instinct puts on a friendlier shirt: a refund, a coupon, a beautifully written apology. Those are tactics too. Tactics execute a step. They do not replace it, and skipping the steps is the most common reason this work feels busy and goes nowhere.

So draw the map first. Yours will be specific to your business. The shape is usually this.

  • They reach you.
  • You learn what actually broke in their world, which is frequently not what the ticket says.
  • You decide what changes in the world, not in the sentence.
  • They see the change.
  • They decide whether you are the kind of company that gets it.

Notice where the refund lives. Inside step three. One tactic, in one step, and the refund is the tactic that gets promoted to the entire process.

Here is the test I run whenever someone hands me a problem they have already diagnosed. Imagine the thing they named is completely solved. Then ask what actually changes.

Your customer says support is too slow. Fine. Imagine it instant. What changes? If the honest answer is "nothing, they still cannot do the thing they bought," speed was never the constraint. You were about to buy a faster version of the wrong step.

I run the same test when a client tells me they need more leads, or more awareness. A million of the wrong people knowing your name changes nothing about the constraint. Adding a service does not create customers. It creates something else nobody knows exists. A complaint behaves the same way. Adding a gesture does not create a fan. It creates a cheaper transaction.

And if the answer someone gives me is "we need better sales conversations," I go looking for the lead first. You cannot have a sales conversation without a lead, so a conversion answer is usually a lead answer in disguise. On a complaint, the apology is the conversion. The step is the lead.

Now the fear, because this is the second place it shows up. Mapping the steps takes a day and produces nothing you can send. You will feel the pull to skip it and ship something warm and immediate instead.

Do not. Write the steps. Then put a date next to the step where the customer actually sees the change. Anything you want to send before that date is a tactic, and it is not ready.

Practice 3: Narrow to one, and know when to walk away

Narrow the Focus: at any moment there is usually more than one important thing in front of you. A complaint hands you at least three. Narrowing is choosing the one that carries The Win and letting the rest be evidence instead of projects.

Practically, those three are: the thing that broke, the way they feel about it, and the relationship itself. The temptation is to fix all three at once, and the result is that all three get done badly. Over-apologize for the feeling, under-fix the break, never touch the relationship.

Pick one. The Win decides which. If your Win is that they come back and send somebody, the step the Win hangs on is rarely the sentence you send them. It is whether they can do the thing they bought.

Third fear. Picking one means admitting you are not fixing the other two, and the one you need to pick is usually the one with no visible work product. You cannot screenshot a relationship. You can screenshot a refund.

When not to do any of this. Not every angry customer is a fan waiting to be made. Some are telling you, clearly and usefully, that you are not for them. Trying to convert that customer produces someone who complains forever, and it teaches your team that every complaint is a rescue mission.

For those, be generous and fast. Give them their money, take the lesson, open the door. That is not free, and I will not pretend it is. It costs you the revenue and it costs you the admission that you sold to the wrong person. Both are cheaper than the alternative.

The fork, priced

Back to the stick figures, because that is where this actually lives.

I had a choice on version two and I did not see it. I could have shown my pharmacy-industry partners the cheapest possible version of the stylistic choice first, before spending weeks making that choice excellent. I did not. I made it excellent, then learned in one sentence that the choice itself was wrong.

Both branches cost you. That is the part that gets left out.

Defend the work and you pay the same cycle again, three and a half weeks, on something you now know is wrong.

Hear it and you pay the admission. Out loud. To yourself and to them: I built the wrong thing well.

There is no free branch. There is only the question of which price you would rather pay, and how many times.

BranchWhat you payWhat it costs you
Defend the workThe same cycle againThree and a half weeks on something you now know is wrong
Hear itThe admission, out loudI built the wrong thing well

Here is the move

Questions

What people ask next

If I only narrow down to one of the three things a complaint hands me, what happens to the other two - do they just stay unresolved, or is there a point where they come back around?
They do not become separate projects you still owe someone. The framework's own language is that the other two become evidence instead of projects, meaning they inform how you execute the one step you chose rather than getting a parallel fix. The failure mode this avoids is doing all three badly at once, over-apologizing for the feeling, under-fixing the break, never touching the relationship.
How do I actually tell the difference between what the customer says broke and what really broke, especially when they're insisting loudly on their version of it?
Run the test: imagine the thing they named is completely solved, then ask what actually changes for them. If the honest answer is nothing, if they still cannot do the thing they bought, then what they're insisting on loudly was never the real constraint, it's a symptom wearing a confident voice. The volume of their complaint tells you how they feel about it, not what actually broke in their world, and those are two different pieces of information.
If writing an honest Win means giving up a metric I've always been measured on, how do I defend that trade to a boss or team who still cares about the old number?
Point out directly that the old number can go up while the thing it was supposed to protect goes down, a fast closed ticket still loses the customer in the same motion, and nothing in that reporting can see it because the Win behind it was never about the customer. The defense isn't abandoning the number, it's naming that the number was a proxy that stopped correlating with the outcome you actually want, like a repeat purchase or a referral.
When the 'imagine it's already solved' test shows the complaint isn't the real constraint, do I still do the thing they literally asked for, or do I just ignore their request entirely?
You don't ignore it, but you also don't let it run the whole response. The thing they asked for is a tactic, and a tactic lives inside a step, it does not replace the step. So you fix the actual constraint first, and if the literal request still makes sense, it gets done as one piece inside that step rather than being promoted to the entire process.
Does this whole three-practice process apply to every single complaint that comes in, or only the ones that matter enough to justify a day of mapping steps?
The article doesn't give a cutoff rule, but it does say mapping steps costs a day and produces nothing you can send immediately, which only pays off when the stakes match that cost. The Win itself is the filter, if what's on the line is whether this customer buys again, renews, or sends somebody, the day is worth spending; if it genuinely isn't, that's a judgment call the framework doesn't make for you.