Systems Chart Review: The Workflow Wasn’t the Problem — The SOP Was

I was training our team on a new A/B thumbnail testing process for clients.

At the time, I thought the explanation was clear.

But within two weeks, questions started flooding in.

Not because the team lacked capability.
Because the operational system lacked clarity.

I had introduced the process verbally, but I hadn’t done the three things that actually create consistency:

• updated the SOP,

• added the subtasks to our project management system,

• or recorded a short training walkthrough.

So the team had no true source of truth.
No place to verify assumptions.
No step-by-step operational guidance.

Once I slowed down and documented the process properly — updating the SOP, building the subtasks into the workflow, and recording a quick training video — the confusion disappeared almost immediately.

The result wasn’t just fewer questions.
It was faster execution, better consistency, and less operational friction across the team.

We introduced a new A/B thumbnail testing process and explained it verbally to the team. But because the SOP wasn’t updated, the subtasks weren’t built into the workflow, and no training walkthrough existed, confusion spread quickly. Once the process was properly documented step-by-step, integrated into the PM system, and supported with a short training video, execution became consistent almost immediately.

The lesson: Don’t systemize a process until the SOP is operationally clear. Otherwise, you’re simply scaling ambiguity.