Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Related Rants
Once, I overheard a conversation between my former PM and a client during a phone call.
Client: I will send the final draft of the project by Thursday.
PM: That's great to hear!
Client: When can I expect the updates to review the changes after the draft is sent? I need to present it at a meeting this weekend.
PM: It should be ready by Friday without fail!
Client: Excellent! Thank you. I will be expecting it.
PM: Sure, goodbye.
(After the call, PM joined the team.)
PM: So, team, the client for Project-A will be sending us a new draft for review and updates. They are putting a lot of pressure on us and need it to be ready by Friday at the latest. We need to treat this with a sense of urgency.
(After hearing this, we felt compelled to respond.)
Me: There's no way they would expect us to deliver an unseen draft within a day. Both the backend and Figma team members were forced to work last weekend, on Saturday, because you mentioned that Project B was behind schedule and the client needed an update by Monday. We simply can't continue working like this.
Backend guy 2: I also worked last Sunday on Project B.
Me: We overheard you telling the client that they should expect an update by Friday. It seems like you're the one directly putting the team under pressure, even though we still have three ongoing projects with tight deadlines.
(The office fell into an uncomfortable silence.)
(PM left the office without saying a word.)
Later on, I heard that he contacted the client to reschedule the expected time of arrival (ETA) after receiving the draft.
rant
wk385
mad mad pm