So I started to give myself challenges. I would see how long I could go with a client without ever mentioning the technology we planned to build on.
I love it! Thinking back, purely by accident, the longest-lasting and most successful business relationships I've gained have been the ones where the client and I discussed their business first (and upcoming business needs!) more than the ins-and-outs of the technology itself.
I think this helps when developing as well; after starting to understand someone else's business, the more excited and interested one can become, which makes doing the work itself even more enjoyable.
Fantastic blog post, thanks for getting me thinking!
> Thinking back, purely by accident, the longest-lasting and most successful business relationships I've gained have been the ones where the client and I discussed their business first (and upcoming business needs!) more than the ins-and-outs of the technology itself.
Yup.
If you bring up the technology, the conversation becomes a matter of the client figuring out whether or not you're good enough at the technology to do the job.
That's the wrong conversation. The right one is about what value you can provide to the client, and you simply exude the competence necessary to make your own technology choice.
It's a little different if you are a representative for that technology, because you're selling the tech rather than yourself.
I feel the same way. When I chat with clients about a project, I focus on their business and clients. I get involved a little bit, see what they are all about (and after that they want to hire me as their employee, but that's another story, I should start blogging about it, hah!) I will definitely try to take the "Do not mention technology" approach to see how this may change things.
This is always great advice and lets you (and the client) focus on the business needs, while keeping them from having to be interested/concerned with the technology powering the solution.
Comments
So I started to give myself challenges. I would see how long I could go with a client without ever mentioning the technology we planned to build on.
I love it! Thinking back, purely by accident, the longest-lasting and most successful business relationships I've gained have been the ones where the client and I discussed their business first (and upcoming business needs!) more than the ins-and-outs of the technology itself.
I think this helps when developing as well; after starting to understand someone else's business, the more excited and interested one can become, which makes doing the work itself even more enjoyable.
Fantastic blog post, thanks for getting me thinking!
> Thinking back, purely by accident, the longest-lasting and most successful business relationships I've gained have been the ones where the client and I discussed their business first (and upcoming business needs!) more than the ins-and-outs of the technology itself.
Yup.
If you bring up the technology, the conversation becomes a matter of the client figuring out whether or not you're good enough at the technology to do the job.
That's the wrong conversation. The right one is about what value you can provide to the client, and you simply exude the competence necessary to make your own technology choice.
It's a little different if you are a representative for that technology, because you're selling the tech rather than yourself.
I feel the same way. When I chat with clients about a project, I focus on their business and clients. I get involved a little bit, see what they are all about (and after that they want to hire me as their employee, but that's another story, I should start blogging about it, hah!) I will definitely try to take the "Do not mention technology" approach to see how this may change things.
This is always great advice and lets you (and the client) focus on the business needs, while keeping them from having to be interested/concerned with the technology powering the solution.