- PPF Points
- 2,888
Oh man, working with non-techy clients? It’s a wild ride. Sometimes it’s like playing charades with someone who’s never even heard of the game. You ask, “So, what do you want this app to do?” and they hit you with, “Uh, just make it like Airbnb, but... better?” Sure, buddy, let me just call up my team of unicorns.
Honestly, I learned pretty quick that you can’t just throw technical jargon at folks who think “backend” is a yoga pose. Visuals save lives here—wireframes, doodles on napkins, whatever. Anything to get everyone literally on the same page. If you can sketch it out or walk through a user story, suddenly the fog lifts a little.
You gotta get crafty with your questions, too. “Do you want a login system?” Nah, that’s a dead end. Try, “So, who’s actually using this? What do you want them to see or do?” That’s when you start hearing stuff that actually helps you build something real, instead of just reading their minds (which, spoiler: doesn’t work).
And man, clients love saying stuff like, “I want it to just work, you know? Like—magic!” Sure, cool, but let’s talk about what “magic” means. Is it one-click checkout? Is it that the site doesn’t crash every time grandma logs in? You gotta break it down Barney-style, otherwise you’ll both end up disappointed.
Patience is the name of the game. I’ve watched projects implode because devs expected clients to suddenly become tech wizards. Doesn’t happen. You have to translate, empathize, sometimes even play therapist when the budget panic sets in. But hey, if you can meet them where they’re at, guide them through the jungle, you usually end up with something that actually works—and nobody cries (much).
So, what do you do when the client can’t even explain what they want? Well, that’s when you break out the crayons, the metaphors, and about a gallon of patience. And maybe a stiff drink after work.
Honestly, I learned pretty quick that you can’t just throw technical jargon at folks who think “backend” is a yoga pose. Visuals save lives here—wireframes, doodles on napkins, whatever. Anything to get everyone literally on the same page. If you can sketch it out or walk through a user story, suddenly the fog lifts a little.
You gotta get crafty with your questions, too. “Do you want a login system?” Nah, that’s a dead end. Try, “So, who’s actually using this? What do you want them to see or do?” That’s when you start hearing stuff that actually helps you build something real, instead of just reading their minds (which, spoiler: doesn’t work).
And man, clients love saying stuff like, “I want it to just work, you know? Like—magic!” Sure, cool, but let’s talk about what “magic” means. Is it one-click checkout? Is it that the site doesn’t crash every time grandma logs in? You gotta break it down Barney-style, otherwise you’ll both end up disappointed.
Patience is the name of the game. I’ve watched projects implode because devs expected clients to suddenly become tech wizards. Doesn’t happen. You have to translate, empathize, sometimes even play therapist when the budget panic sets in. But hey, if you can meet them where they’re at, guide them through the jungle, you usually end up with something that actually works—and nobody cries (much).
So, what do you do when the client can’t even explain what they want? Well, that’s when you break out the crayons, the metaphors, and about a gallon of patience. And maybe a stiff drink after work.
