How to talk about technicalities

“Will I catch on?”

When you come up with an idea for a new digital product, this question often comes up as well. After all, when you run a business, you don't need to be versed in technical issues that, let's be honest, can be intimidating for many. 

If you're a product developer and you're also reading the text, yes, this applies to you too. After all, it's good to know how to get along with your customers without overwhelming them with tons of incomprehensible information.

Talk to be understood

The key to understanding is, of course, communication. Two-sided. Without just talking or just listening. Here you need to talk and make sure that at each stage of product creation, its technical elements are understood by all involved.

We have a list of some hints for you on how to keep good communication throughout the process. But let's start with what is "good communication"? It is first of all making sure that we speak in such a way that everybody understands what we mean. Sure, you can use a million industry-specific phrases in every email or meeting, but what for? At the end of the day, it's about not having to say "that's not what I meant" or "I thought you meant something completely different." Good communication when creating a digital product is one that doesn't make one guess what the author also meant.

Believe me, this approach helps to avoid a lot of disappointment, lengthy projects and fixes due to misunderstandings.

Simple things sound better

Well then, it's time for some tips on how to put together a good communication.

• Basic rule: don't be afraid to ask. No matter on which side of the project you work, if something is unclear, ask. It is worth remembering that there are no stupid questions. Yes, some things may be obvious to developers, but not necessarily to other people.

• Try to avoid jargon/slang. It may be a good idea to create a glossary of the most commonly used phrases by technical team members. 

Hint: once prepared, it can be used in subsequent projects as well.

• Use examples. Describe functionality, show specific solutions in other products. This is the best way to talk about technology in a specific and understandable way. 

These are simple steps that can be implemented at any stage of a project, and they definitely make it easier to communicate with each other. What’s more,they make the whole project simpler to implement.