4 ms·
Is it a surprise that people don't all work in the supportive environment that you have? Here's a more accurate example for me: "This feature will take about 3
by paxys 4y ago
Is it a surprise that people don't all work in the supportive environment that you have? Here's a more accurate example for me:
"This feature will take about 3 weeks to ship."
"Why so long? It's just a button that does stuff. Can't you just..."
When the other side of the argument is a PM who can't describe what an HTTP call is, it's hard to look at it as a good faith discussion.
- Dylan16807 4y agoYour hypothetical conversation is not improved very much by removing the word "just".
- fardo 4y agoContext would matter here, but the above question on its own wouldn’t typically rise to bad faith, even if phrased as written. The job of the PM often demands creating project schedules, delegating assignments, spurring their team to deliver assigned tasks on time, and managing the team. It very much is their business to have some sense of how long things take, why they take so long, and get a sense whether the bottleneck is a personnel skill or motivation issue or the technical nature of the problem space. A good faith answer would likely include an explanation why shipping a button took 3 weeks, would likely explain the relevance of those HTTP calls in your use case, and would help to give them a better sense of the work involved so they can better mentally cost out new interface items without creating expectations you’d be unlikely to meet.
- quelltext 4y ago> Is it a surprise that people don't all work in the supportive environment that you have? No, but what I'm saying was that usage of "just" is not the issue, a shitty environment is. If your boss / coworker / PM doesn't use "just" but still constantly makes it seem like a task should be easy to do in other ways (e.g. telling you your estimate is way too high for a task) and puts pressure on you not listening or accepting to your reasoning, is that better than them using the word "just", you explain why and they get that things aren't as simple as they thought? The underlying issue is not the particular choice of word. You might say as advice "don't presume a task is easy, if you want to avoid people think/misunderstand it can help to avoid the following words:...". But the really important part would be the first part of this advice. Though to be fair I don't even know if I'd agree with that advice either. Stuff is misunderstood or not well understood all the time. Expectations exist if you want them to or not. Maybe it's better to communicate those expectations. > "Why so long? It's just a button that does stuff. Can't you just..." a) The core aspect to address is not the word "just", but that the person asks you something they consider simple. Changing the wording (removing "just" or other such words) doesn't change the actual sentiment. b) The "just" in the example does emphasize to the listener further that the speaker is underestimating the task at hand or doesn't yet grasp the full context. While I would see this as problematic usage, it precisely is what can help the listener in identifying that they might have to spend some time to address that misconception in their follow-up reply. Whether it's ultimately super useful or not I don't know, but it does provide extra signal. I personally would rather have someone use "just" if they do in fact think the task is simple/trivial than beating around the bush. I then understand that there could be an issue of misalignment or even disagreement on difficulty. You really do want to get that out of the way instead of each party in silence, paralyzed, thinking "I still don't get why we cannot / need to do X / Y, but I don't want to sound like ...". And that goes both ways. I have definitely gotten a good reset and ended up agreeing with the speaker that a solution can in fact be simpler albeit not perfect. And if the speaker and I then agree that it's sufficient, why not. I'm digressing. Important is that communication happens in good faith. Politeness likely doesn't fix this if that's not the case.