536
and when it sucks, devs get all credit
(discuss.tchncs.de)
Post funny things about programming here! (Or just rant about your favourite programming language.)
Hate this. I work as a PO. Praise my devs every chance I get both internally and towards our clients. Always pass on positive feedback and use negative feedback only translated into priority weights.
I see my job as keeping stakeholders at bay and let them do their job. I bundle requests into feature requests that cover as many current and future needs as possible, but never without internal meetings first.
Just getting sales to stop making deals on feature requirements with clients was a very long uphill battle that we have mostly won. Now it all goes through my team first and we always do estimates with our development teams. Takes a bit of time, takes a bit longer, but never have I seen a client get back to us with the same urgency as they request a quote anyway. If they can not wait a week, they won't be a good fit for what we are doing and how we do things.
Posts like these make me feel accomplished :D
Sounds like you are doing good PO work, keep at it!
Thank you, I'm sure trying. I got a good 30-35 years left in this, I'd rather not be miserable or make people miserable for the duration.
Glad to hear we're not the only ones with salespeople promising the moon and the stars to clients without asking first lol
I once had a sales-bro tell the client we'd "monitor the internet for X". That has remained one of the most important hammers for me to wield when discussions even start coming up. How the fuck does one "monitor the internet" to a degree that fits the clients interpretation of this phrase. Sales guy is still with us and a good lad, he owns that mistake. But fuck was it ever crazy.
I have to imagine it's quite difficult to do that job well without actually knowing how technology works
Yeah my take away there is if that's the tech level of your sales guys you need to have a tech sales role and a strict ban on the pure sales people even attempting talking tech. Sales should be talking business and business needs that the solution can adress.
Yes, it's fun when you make an estimate and planning for the lastest sale and it turned out the three weeks sold is three months of work. No, I don't care what you promised, it'll be ready in three months. Ask for an estimate before you make that promise next time.
We've decoupled timelines from estimates almost entirely and to the ire of all our sales and C-Level only give out Quarter based estimates anymore. "End of Q3 or early Q4". When we deliver mid Q3, everyone is happy. The funny bit is that since we've made these changes, we've not noticed any drop in client interest at all. What we do notice is that we actually ship what we promise (sometimes even more). We also don't have clients who think we'll do 10 hours of work for free anymore, because we've anchored the value of every little bit we do properly. We also filter the stingy clients who are completely pointless and are just wasting our time, while engaged with our competitors.
There's a lot, a looooot of FOMO in sales on the side of our own sales people. So they lowball their shit to make sure we close. Then we can't keep what's promised and nobody is happy and contracts that would only be profitable after like 3 years don't get renewed and we lose a client. Great stuff. Then try and get them back after a shitty experience like that.
The mind boggles.
As a sales guy myself by training and tech sales by profession that sounds very much like there are some very fucked incentive structures at play that need to be addressed. If they're only monitored on number of deals closed then you get shit like that trying to meet targets and get the bonus that is extremely standard in the sales profession and account for a large share of the yearly salary. If they're measured on profitability then you wouldn't see that, they'd drop stingy clients themselves for wasting their time. Another solution I've seen is having a larger bonus for customer satisfaction and renewals / growing the contract but that only really works out if your sales also doubles as account managers.
Possibly. It's entirely opaque where I work. I have no clue how they're compensated whatsoever. We managed to fix it for the most part. I like the customer satisfaction approach via renewals as a target. Especially since you can basically give that to everyone involved on the project. Then again, some customers are dissatisfied as a policy. Worked with some miserable folk who always communicated in a horrible, horrible way but kept renewing and never balked at the cost. It was simply a "you're a service provider, you're beneath us" thing. Some people truly suck.
Amen, can't fix everything or one.
I'm a PM in a different field (science stuff). If anyone asked me to present on behalf of the science team, I would say no. It's their work. Managing a team and timelines and budget does not mean I do the work. I think this is why when job searching I get a lot of interviews with dev and other tech. They just want competent managers. Some of them, anyway.
In swoops the project team to sign a contract with a software vendor without any architectural or Product input, then expects you to implement changes for whatever the software does and however it works. They do not know.