When Too Much Info Takes a Toll

One time I unintentionally disclosed too many technical details to a customer during a project update. 
I started talking about implementation specifics, technology stacks, and abstract concepts, thinking it would demonstrate my expertise. 

We have a saying in Hungarian that goes 

Fordítva sült el a puska!

which perfectly applies to this situation. It highlights how things can unexpectedly backfire or turn out in an unintended way.

The customer became extremely interested in the nitty-gritty details. Before I knew it, he had me on the phone for hours, asking questions about every little aspect of the project. 

He even started giving suggestions on how we should modify our approach, despite not being a subject matter expert. I found myself trying to explain why his proposed solution wouldn’t work.
I remember feeling like I was hitting my head against a brick wall as he became increasingly defensive. 

My initial harmless technical monologue spiraled into a challenging situation that had a negative impact on my career and led me to make a tough call.

But I learned a valuable lesson: 

It’s crucial to avoid discussing implementation specifics, technical details, or abstract concepts with customers. Instead, focus on their needs, objectives, and the value your solution brings to them. This approach ensures smoother communication and a more effective working relationship.

So, I cannot stress this enough: 

Never, and I mean never ever, share technical information or code details with anyone who is outside of your development team. 

If your company’s policy requires you to share technical details or code with customers, my advice is simple: 

Run, and don’t look back!