Debugging communication
How does communication work? How can we break it down into segments or steps? What problems occur in each "step"? How to fix this?
A lot of issues on projects haappen due to bad communication. However, it is tricky to determine exactly when, where and why this happens.
In this talk I would like to break communication down into 4 main steps and analyze problems that occur between each of them:
- What your idea you wish to say is
- What you actually say
- What the other person actually hears / reads
- What the other person walks away with
I would also like to offer practical advice how to make sure you get your message across throughout this communication process.
Friday, 2017-10-06 @ 17:25
>
Skill level:
elementary
>
Duration: 25 min
Mario Mucalo
Mario is a senior full stack .NET / AngularJS developer with 10 years of experience in software development and a M.Sc. degree in computer engineering from Faculty of Electronic Engineering and Computing, University of Zagreb.
..* Worked as a PHP web developer in Progresivne tehnologije d.o.o. in 2007.
..* Worked as a Java developer in Novateh Terra d.o.o. from 2009 - 2011.
..* Worked as a .NET developer in Lemax from 2009 - 2011.
..* Worked as a presales technical manager in Lemax from 2011 - 2013. Was in charge of gathering client requirements and communicating them to the development team.
..* Worked as a Director of Engineering in Toptal LLC from 2013 - 2017. Was in charge of communicating with clients, understanding their projects and their needs, and finding best possible talent to meet their requirements.
..* Worked as the Head of the technical screening team in Toptal LLC from 2015 - 2017. Was in charge of leading a team of 30 engineers who were in charge of conducting the technical screening process in Toptal.
..* Founder and leader of Intellegens j.d.o.o., a Croatian software development company since 2013.
