And yes, you are right: that's the direction. One thing I'd recommend is to purposely avoid to create client dependency on your team. You are there to do a job, but not "their" job.
You should solve a problem for them as much as you should educate them so that they are able to run independently.
And yes, you are right: that's the direction. One thing I'd recommend is to purposely avoid to create client dependency on your team. You are there to do a job, but not "their" job.
You should solve a problem for them as much as you should educate them so that they are able to run independently.
If this sounds like you're leaving money on the table, don't worry.
They'll never be able to pull that off, but you left them with all the ammunitions.
Thanks for the nice words, first of all!
And yes, you are right: that's the direction. One thing I'd recommend is to purposely avoid to create client dependency on your team. You are there to do a job, but not "their" job.
You should solve a problem for them as much as you should educate them so that they are able to run independently.
If this sounds like you're leaving money on the table, don't worry.
They'll never be able to pull that off, but you left them with all the ammunitions.
This means they'll call you back.