|
|
|
|
|
by Apreche
310 days ago
|
|
Sure. But they want it tomorrow. When you offer to build a real solution, that sure is a lot of work, time, and expense to give them something they could have instantly. A tough sell. Also, volunteering yourself to do a lot of work on top of the responsibilities you already have. |
|
This is why product teams have cadences of triaging and prioritizing the work. You need a PM (or someone who fulfills that role) who will listen to engineering as much as the business and allow for the time to get the right solutions in place. That way, it is not an additional burden on the dev team, it is part of the standard work process. Then it is not a tough sell, it is day-to-day communication with whomever prioritizes the work, which should already be happening.
Now, that being said, I fully recognize that many PMs are not good at this part of the job. But then your focus needs to be on working better with the PM. Because a good PM will push back and establish boundaries with the business to prevent last-minute, urgent "wants" from disrupting the actual development of the product.
This also brings us back full-circle to how performance goes down in the first place. Devs get sick of all this, PMs cave in, and just put in Google Analytics or some other tool in place. Once that hook is live, marketing can add all kinds of crap to the site. Look, they got their instant gratification on analytics! And took down the site performance in the process.
"We can get an instant solution" is a red flag to me as a PM, not a selling point.