communication and its importance to a developer
TRANSCRIPT
Communication and its importance to a developer
Despot Jakimovski, Skopje, 2016
Communication at work by example- Offering a better solution or help
- Clarifying technical story with product owner
- Share knowledge
- Asking for help on your task
- Resolving an argument
- Handling objections
Communication is...● Exchange of information
piece of the puzzle
SPR
ING
How important is communication?Manager:
● ask
Employee (or applicant):
● acts smug
● interruptive
● not responsible for
● easy-going
Colleague:
● needs something
Absolutes:
● always agree?
● allow all interruptions?
● when needed, get most of it
Employee (or colleague):
● answer abruptly
● continue working
Important to you?
Type of communication?
Written
Body language
Spoken
● comfortable (most time)
● fast across (chat)
● availability (status, notification)
● larger info (email)
● answer / conclude at start
● big email trail -> conference call
● repeatedly required info (wiki)
● listen first
● ask more than tell
● eye contact
● crossed arms
● leaning
Some things about developers
true == false || true You are correct.
Communication towards developers- Story bliss
-
- plays music/happy-chatty
- question by you or another
- asking questions while reviewing story
- Focus breakers:
(ask before/look around)
- Discussion - views don’t match
- constructive?
- why? moody? repetitive?
(juniors ask on skype)
-
-
-
- a sign of interest
- a sign of doubt
- a reaction to a feeling of insult or attack
- a reaction to a compliment
Resistance is...● … an opportunity
● most of it - how?
● short answer, yes, and … behaviour
○ stimulates, is creative, cooperative, positive and inspiring
○ yes, but … behaviour - not respecting reactive, passive, suspicious
● neglect the power of silence?
● short pause
● ask open-ended question - lead conversation
● confirmation of receipt
Communication towards non-developers- Broader focus
- explain (hard enough between developers)
- no technicalities;
- client scared and lost;
- discredit yourself;
- meetings
- changing stories/priorities; burden you?
- we not I
-
-
- Say “no”
-
-
-
- Listen to the reaction
-
-
-
-
-
-
- Open question in future and suggest an alternative
-
-
-
-
-
- Underlying reason?
-
-
-
-
- why no is good for them
Communication towards non-developers 2- Someone asks you for something:
- impossible
- against company’s code of conduct
- unwanted.
- How to say NO properly:-
- understand person’s question
● be aware (your communication)
● small steps (work on it)
● listen first
● handle objections/resistance (in a proper way)
● when pile, prioritize (say why and when)
● say no when needed (in a proper way)
● enjoy in your better work setup - reward yourself!
Conclusion
Objectivity exercise
Communicationsituation
3 words describing actions
Q&Ahttps://mk.linkedin.com/in/despotjakimovski
http://www.tricode.nl/en/Updates/Blogs/communication-and-its-importance-to-a-developer-bdetail