As Project Managers and Developers, we’ve all been there.
A non-tech customer asks for a “quick text change” and expects it to be as easy as editing a Word doc.
But for us, even a “simple” change involves:
• Finding the right file in the codebase
• Making the edit in the code
• Pushing it to the branch
• Running Unit Tests (UT)
• Merging with master
• More testing, more approvals
• Deploying to UAT, staging, then production
And don’t even get me started on design tweaks, percentage changes, or plugin hunting—each “small” ask has layers of complexity that customers rarely see.
The real kicker?
The understanding gap between tech teams and non-tech customers can kill a project.
I’ve seen perfectly good projects fail, budgets overrun, and timelines explode because the client just didn’t realize the time, effort, and expertise that goes into every single task.
But here’s the thing: it’s not their fault—they simply don’t see what happens behind the curtain.
So, how do we make sure our clients:
• Respect the process
• Understand the pain points
• Trust our expertise
Do you have strategies that work?
Or do you feel like you’re constantly stuck in the “education loop”?
💬 Drop your experiences, frustrations, or tips below.
Let’s have a real conversation about the realities of managing non-tech clients!
