The Dev Who Sat in a Sales Call
ag404labs.com
The Dev Who Sat in a Sales Call
1–4 of 4 posts
Re: The Dev Who Sat in a Sales Call
#2I still fight regularly for a meeting with clients that isn't a list of ideas or features, but is a "why do you want to do this thing" explanation from the very top. I don't always get it, but when I do the new feature right out of the gate, almost every dang time.
Re: The Dev Who Sat in a Sales Call
#3I worked at a company that for a very short time had engineering, tech support, and sales and such all follow a person from another department around for a little while. It opened up communication and understanding far beyond anything ever had, but it of course ended after a short while. It was inconvenient, and I think it upset some managers who were the gatekeepers of communication and process and otherwise useless…
When engineers can talk directly to customers, when support understands the product, when sales knows what's actually possible, suddenly half the middle management layer has nothing to do.
Re: The Dev Who Sat in a Sales Call
#4I worked at a company that for a very short time had engineering, tech support, and sales and such all follow a person from another department around for a little while. It opened up communication and understanding far beyond anything ever had, but it of course ended after a short while. It was inconvenient, and I think it upset some managers who were the gatekeepers of communication and process and otherwise useless…