Conversation

Notices

1. Embed this notice
   Scott Miller 🇺🇦 🇺🇸 (scottmiller42@mstdn.social)'s status on Friday, 09-Feb-2024 18:28:14 JST Scott Miller 🇺🇦 🇺🇸

   Responding to a request or suggestion for X with "we already do X" shuts down the conversation & forces the requester's hand. Requestor must then choose between abandoning the request or start an argument that X is not being done. Either way leads to hard feelings.

   At minimum, VERIFY that you are doing X before responding. Ask "does this example meet your needs?" Handle it like a step in the conversation, not a conversation ender.

   #OfficeWorkerGripes #UserFeedback

   • clacke likes this.
   • Embed this notice
     Kit Rhett Aultman (roadriverrail@signs.codes)'s status on Friday, 09-Feb-2024 19:34:22 JST Kit Rhett Aultman

     in reply to

     @scottmiller42 I have a similar gripe around people, almost always in IT or developer tools, who respond to my needs with "Why don't you just <suggested workaround>?" Thing is, that typically didn't work a month ago when I tried it because it was the first suggested workaround in a very visible document...and it didn't work. Or often the thing I should "just do" only works for backend devs on Macs and I am a firmware dev on Linux. Better phrase: "Have you tried <workaround>?"