Post funny things about programming here! (Or just rant about your favourite programming language.)
source: https://twitter.com/wagslane/status/1637910671781404673
image description:
a girl is smiling in front of the camera, not directly looking at it. in front of her is a big cake. the text on her reads, "PM showing off latest features"
just on the left and a little behind is a guy, out of focus, blankly staring at the cake. the text on him reads, "dev getting 0 credit"
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.
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.
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.
Eh, I don't want to present features to stakeholders. It's pretty thankless, in my experience. The real worthwhile merit is in presenting architecture designs and reviews to tech leadership.
I'm not an architect, but I've sat in on architecture presentations and the most rewarding feedback I've seen is "Any objections? Ok, approved".
The rewarding feedback is often during your next compensation review, if you razzle dazzle 'em enough.
Good to hear it happens, even if the praise is all behind closed doors.
When they offer you a 3% uplift, rather than 2% with inflation running higher.
In my current project, we hold reviews together with our customer, because supposedly they work together with us on this project (they have done nothing of value since project start).
And it's so miserable, because among us colleagues, we really don't know what everyone else actually developed, because you obviously don't want to go into deep technical discussions, nor be too critical, when the customers all sit there.
In every dev job I've ever held it's been me or one of the other devs doing demos (usually me though). Granted I haven't worked on anything truly high profile that a demo would be An Event.
Success has many parents. Failure is an orphan.
I prefer my accolades in the form of bonus cheques. I've got a git history for anyone else that matters
they rejected my request for raise because "you already are amongst the ones with highest percentage raise in the past"(which is in single digit, BTW). meanwhile peers who do nothing all day are more paid.
i'm not jealous. just feel like I'm underpaid and overworked
As a former PM/PO who has moved up the chain, your PM is full of shit and you should look around. Looking out for your top talent is how you succeed as a PM.
thank you mates, I'll definitely look elsewhere.
Then find another company and negotiate a salary you should be on. Maybe add on a bit more so that can negotiate you down to what you want. Ignore the question of how much you are on as much as possible. Answer with "I am looking for £x".
And if it comes down to how much you're making now, simply lie.
Honestly you should shop around on LinkedIn
Been there. I didn't even know that there had been a product launch party until the next day when people were wearing pins with the product logo & talking about the great time they had. Nobody thought to invite literally the only developer.
feels bad man
I got the last laugh. After I left to triple my salary, they couldn't support the product, sold their IP to their biggest competitor, and shut down.
Don't you just present the stuff yourself as dev? Our sprint review demo's are done by us, not the PO or something. I thought that'd be standard
There are different audiences for demos though. It should be that way at the "working level". When you start moving up the chain with more senior leadership in your org, it starts to make more sense to have the PM do the demos/briefs.
Usually devs don't particularly care or want to and sometimes they aren't really qualified to--its not their skillset. But if it's a good PM, that's where they shine. That's the value they bring to the project. They (should) know the politics, landmines, things that specific leaders would care about (and to highlight for them), and how to frame it to current business needs. They have the context to understand when a seemingly innocuous question is actually pointed. They might not know the intricacies of your code, but they (should) know the intricacies of the organization. That's not something most developers know, and why should they? That's not their job.
Sometimes it even involves groundwork meetings and demos to make sure you have support from other key components in your org-- like getting your CTO excited because one of his performance goals was x and your project is the first real implementation of x. Now, you have the CTO ready to speak on your behalf in front of the CIO. As a PM you know that the CIO has been getting flack from the CFO because there hasn't been a good way to capture costs for Y, but your system starts the org down the path to fix that. Now they are both excited about the project and in your corner. Etc etc
A product owner is not the same as a project manager.
This. Many devs will never even meet their Product Manager because they are "too high level to be needed in technical calls".
Translated to "I only want to tell people how much money this is going to make them without even knowing what it does"
How it is where I work. How it should be.
In the end, how is that different from not praising all the library coders and open source parts?
Praise goes to the marketing guys. And rightly so. Without them, nobody of consequence would buy or use the code. ;)
The biggest thank you is to give engineering a commission on sales... If not, it doesn't matter who does the presentation.
Easy fix for that
Nobody's reading that code after launch. Certainly not customers.
And it always works ….