4 ms·
> Also, in my team we have close contact to business, oftentimes spontaneous 1-on-1 calls that can get off topic. In these situations our clients appreciate if
by TeMPOraL 5y ago
> Also, in my team we have close contact to business, oftentimes spontaneous 1-on-1 calls that can get off topic. In these situations our clients appreciate if you have the big picture.
I'm wary of such situations because, in my experience, sometimes it's a customer or someone in a different team fishing for information that your PM doesn't want to give them. Your PM may have a good reason to be vague about things, and carelessly delving into details may make your team's job harder.
- beingflo 5y agoI agree. This requires some understanding of the strategy and the PM ideally mentions what shouldn't be told to the customer.
- JohnFen 5y agoI agree. Direct contact between devs and customers should be unusual, and should be focused narrowly on a particular technical issue the dev is handling. Everything else, especially big-picture questions such as the general state of a project, is something that should be dealt with by someone else. To do otherwise is unfair to the devs (because it's not their job and perhaps not their skillset), unfair to the customer (because they'll be getting information that may not be entirely correct), and unfair to the company (because it reduces the company's ability to provide accurate information to the customer, it may expose confidential information, and it's burning expensive dev time)