Earlier quoted context omitted.
That's hilarious - I can't help but think of this dilbert cartoon on making change: https://dilbert.com/strip/1993-03-20 (I am not putting you down)
Years ago I worked at a store with registers that didn't calculate change; myself and the other cashiers would need to calculate the change mentally. Once in a while I would get people like this who threw out convoluted amounts of change. Normally it was fine, but sometimes towards the end of a long day when my brain was tired I wanted to strangle them. The store actually had really great employees overall and I susp…
How many of you know that the team is working on something that no-one wants?
161–170 of 428 posts
Re: How many of you know that the team is working on something that no-one wants?
#162My chances to know beforehand what customers want is 50/50.*
So I am very humble by now. Launch super early. Get Feedback. Quantity wise and quality feedback (listen closely if you made their life any better). Iterrate and/or change path.
Yes, like flipping a coin. Sad that, quite a lot of managers have a way lower hit rate as they have an inherent ”the customer is like me and users are stupid” bias (both at the same time, so that makes them...)
Re: How many of you know that the team is working on something that no-one wants?
#163Earlier quoted context omitted.
Jobs where this kind of attitude prevails suck to work at. Frustration waits around every corner. And the more pointless projects and dysfunction permeates a company the more chance the other shoe will come crashing down any moment and the company will fall apart and people will lose their jobs.
Some people are busy raising a family and just need a paycheck. It's not me either but I get it.
Re: How many of you know that the team is working on something that no-one wants?
#164“Agile teams that truly iterate with the customer can often avoid these problems because the customer is there the whole way through and the team continuously pivots to close gaps discovered by the customer throughout the project, thereby building something the customer actually needs and wants.” I‘m 2 years into my first role as a product owner (made the switch from design) and working at a fortune 100. The thing th…
I've worked 6 years as a PM, last 4 at FANG Here's some advice, which you are free to take or to leave, (and that's very reasonable since my advice is generic and I can't speak to your exact circumstances) 1) Just start doing it. Don't wait for someone to give you permission to prioritize customer needs. Pick up the phone and call them. Go to a store and watch them shop for your product. Talk to people. When you set…
Re: How many of you know that the team is working on something that no-one wants?
#165Earlier quoted context omitted.
Solve self driving? How bout market prediction and just play the market forever. Why would you risk failure when you can just do nothing and make trillions?
Ahem, actual humans cannot consistently predict the market.
- your ceoRe: How many of you know that the team is working on something that no-one wants?
#166Earlier quoted context omitted.
Previous employer did something similar. Hired a crazy expensive data scientist, spent truckloads of money on a data swamp, er, lake, and then didn’t really have any goals for what to do with all that capacity. The new hire got lucky, as there was some low hanging fruit (optimizations we all knew about). The obvious solution was implemented and then he ex post facto claimed 100% credit for the revenue enhancement. Si…
So you all knew about optimizations 10x a data scientist salary, but didn't act on them? Actually good that the company hired him then.
Sadly, most engineers aren't allowed to pursue that kind of stuff. Normal dev jobs can be stifling.
Re: How many of you know that the team is working on something that no-one wants?
#167Earlier quoted context omitted.
Previous employer did something similar. Hired a crazy expensive data scientist, spent truckloads of money on a data swamp, er, lake, and then didn’t really have any goals for what to do with all that capacity. The new hire got lucky, as there was some low hanging fruit (optimizations we all knew about). The obvious solution was implemented and then he ex post facto claimed 100% credit for the revenue enhancement. Si…
So you all knew about optimizations 10x a data scientist salary, but didn't act on them? Actually good that the company hired him then.
I did this several times in my early career and was paid a lot and it was win/win
You have to phrase it carefully, but if you phrase it as a win/win with no risk, they’ll sign off on it
Re: How many of you know that the team is working on something that no-one wants?
#168I was cheering a little inside while reading this and agreeing mightily until I realized it was an ad. Boo.
Re: How many of you know that the team is working on something that no-one wants?
#169Yes, so I put analytics in to prove it. I told the project leader that nobody wants a share button there, because of the nature of the data, nobody will share it. They disagreed strongly, suddenly the share button was super important. So I put tracking on it. A year after launch, guess what? Yep that’s right, nobody clicked the button. Not a single user. So I showed them the data and told them I was right. I told the…
Re: How many of you know that the team is working on something that no-one wants?
#170I was a pretty new hire at a small computer repair company with an absolutely manic CEO. The guy was an egomaniac and thought that because he owned a computer repair company (mind you, he has zero tech skills, his partner was the one who did all of that), he was the next Steve Jobs.
I originally got hired at the company to do work on their web SEO "business division".
By "business division", it was a 12 man team building Wordpress sites for about 5 clients. No version control, no backups (unless you count zipping the WP install and leaving the archive in the same directory on the server), paying nearly $1200 for Enterprise Azure for traffic that didn't even equal 10,000 hits/mo across all clients.
It eventually got around I knew what I was doing, so I got pulled off to another project--one to architect a custom backend for a new idea the CEO had.
One of the other coworkers at the company (who did everything in PHP--and I mean literally everything), had built a wheel interface in a web browser.
The CEO saw the wheel, and decided that the interface was going to be a social media app. Literally form over function.
The app quickly got convoluted because there was literally zero project management. We would literally get ideas from the CEO in an email and we'd start to work on it until he got the next big idea. There was zero accountability to what we were building. We would be interfaces and logic that would get torn down or hacked 6 months down the line. We spent literal months building this convoluted 6-7 layer deep wheel interface to make a Yelp rip-off clone.
Imagine you wanted an estate lawyer? You would have a wheel of 7 elements. One was "professional services". You'd circle the wheel around and click on it. You'd then get 7 more wheel elements. You'd circle the wheel around to "lawyers". Once on lawyers, you'd scroll around until you found the icon for "estate lawyer" and when you hovered to it, you'd get an interface on the top of recommended lawyers based on some constantly changing algorithm of friend recommendations and geo locations.
This app was in development for nearly a year and didn't see a single user until around 9 months in (where we posted "gigs" to Craiglist, promising money if you were a "top user", but I don't think anyone got paid).
We never did a formal launch because we kept building and building and building.
We added business recommendations first. Then it became movies and other media. Then we build a friends list that let you put in contact information about your friends (we rebuilt contact list). Then we built a tracker that would ping your location at few minute intervals and store it and a timestamp on our server. Then we built an aggressive scraper that would scrape your call history and contact list, store it to our server in plaintext, and then query each phone number in a plaintext query to Google to see if we could match it. We build a "pre-fetcher" that would aggregate data and scrape images from Google Images and build business profiles we'd pass off as our own.
The list went on and on and on--all while rebuilding the friends privacy settings over and over.
The entire time, I desperately wanted to find a new job, but couldn't because the economy was shit. I constantly was berated and yelled at. Promised equity but never got a statement. Pay was terrible (they bait and switched me with the SEO pay).
Finally after some unreasonable disagreement with the CEO, I was "indefinitely on unpaid leave" (I was basically fired without being fired), so I just quit. I got a call with a death threat days later.
Luckily, I landed another small time job shortly after. I ended up suing the previous company, but they hired the biggest defense firm in the state to stall out--so my lawyer bailed. Not before they called me, leaving me a second death threat for hiring a lawyer.