how to build great relationships with your clients
TRANSCRIPT
WHO WE ARE
“Netguru is full stack, remote, upmarket software services company. Our clients and employees feel that
we are a valuable partner and recommend us.”
HOW TO BUILD GREAT RELATIONSHIP WITH
CLIENTS
HACKS FOR BETTER PM FOR REMOTE TEAMS
WORKING REMOTELY
NETGURU
iSENSOR
NDAPOLICY
MONTE
GG
BENCHIFY
➜ contact via devices ➜ different time zones ➜ product approach
These are not our blockers - we can deal with it.
WORKING REMOTELY
TRUSTThe base of our cooperation with clients.
➜ daily chats ➜ weekly calls➜ constant updates ➜ e-mail summaries
PM makes sure that client and the whole team are on the same page.
TRANSPARENT COMMUNICATION
COMMUNICATIONOur best practices.
ADVISING INSTEAD OF ASKING
ASKING: Maybe we could move from Jira to Pivotal…= We don’t really know but maybe it’ll help.
ADVISING: We recommend to move the project from Jira to Pivotal as this will improve…= We have experience with both and found Pivotal to be better because… You need to trust our judgment.
DON’T TRY - just DO
TRYING: Kate will try to finish this feature today= Kate is not very experienced and we are not sure if she can make it.
DOING: Kate will focus on this feature today = Kate is smart and by focusing she can deliver most value.
TELLING INSTEAD OF ASKING
ASKING: Is it enough if Kate joins the meeting, or should John join as well?= You are “the boss” and you know best how to manage this project.
TELLING: We recommend that Kate joins this meeting. We can skip John & Mark as they are involved in other part of the project. Let me know if that suits you guys.= We are a professional consulting company that has PM skills and experience in thing like that.
COMMUNICATION - SUMMARY
LEARN CLIENT’S LANGUAGE
➜ ask questions➜ write down
summaries➜ business seconds:
casual are more informative
➜ explain how goals will impact tasks
TEACH WHAT YOU KNOW
➜ use experience of team members
➜ use client’s feedback
PREDICT
➜ pay attention to signs along the road
➜ try new solutions
➜ time tracking➜ executive summary
➜ current tasks➜ next tasks➜ commits/task
TRANSPARENT WORK
➜ 3 boards ➜ one task/developer➜ task stage ➜ 3 task types
KEEPING THE DEADLINE
ESTIMATION
0p < 4h1p = 4h2p = 8h3p = 12
4p - divide ticket
ITERATION
tickets amount
“extra” label
DEADLINE
do we deliver iterations on
time?
TOOLS WE USE
➜ code availability➜ code quality➜ application performance
➜ staging server
