@Brian-Cannon said in Season 3 Launch: Patch Notes + Development Letter:
annnnnnnnnnnd still no fix for the dice
@JuliusBorisovBeamdog said in Season 3 Launch: Patch Notes + Development Letter:
Sorry, have you even read the link?
@Brian-Cannon said in Season 3 Launch: Patch Notes + Development Letter:
I have Julius
@JuliusBorisovBeamdog said in Season 3 Launch: Patch Notes + Development Letter:
Sorry, then why did you comment that way?
I figured if I’m going to criticize a response - as I’ve always said, it’s very easy to criticize - much harder to state a specific course to follow that doesn’t likewise have issues. I cited what I considered wrong before, but not terribly detailed about why and what to do instead.
“annnnnnnnnnnd still no fix for the dice” - drawing out the “annnnnnd” you could characterize as an attack - but consider the speed of developer response (months and months) and the evasion (even if not deliberate) and denial (even if the issue wasn’t understood). When one party behaves unreasonably, it’s not reasonable to act as if that party HAD been reasonable. So best - considering the context - just to let it pass. (Even without context, it’s STILL best just to let stuff like that go, if you’re representing a company).
“Sorry, have you even read the link?” - terrible terrible response. Leading with “Sorry” could be a lead-in to an apology so is polite/neutral of itself. But the rest is just a vicious backhand. “Have you even read the link?” Not “Have you read the link”, which would be bad enough! But have you EVEN read the link? Did you EVEN bother to do the smallest modicum of what’s reasonable and appropriate? That’s the takeaway. As to “have you read the link” - of itself, that’s frankly insulting.
You could perhaps get away with that level of insult on some level if the development letter REALLY DID exhaustively address a “fix for the dice”. But it doesn’t.
Note there’s a difference between a representative of a company making an insulting assertion contrary to documentation, and a customer making an assertion that can be taken as insulting but that has LOADS of documentation.
What would have been an appropriate response?
- Lead with thanking the person for their time, and acknowledging the legitimacy of the inquiry.
Companies pay big money for metrics, and here’s someone that took their time - no matter how brief - to provide feedback. That’s stuff companies fight over, pay for, there’s scandals about people surrendering data - and here’s data, at someone else’s time and expense, provided to you, for free. That’s the mindset you need at the core. If you don’t have it, it’s going to reflect in your actions.
- If it is NOT POSSIBLE to acknowledge the legitimacy of the inquiry (for political reasons or whatever - say you don’t understand what they mean, or suppose you’re under orders not to respond directly to particular topics) - deflect. Not a blunt deflection that denies legitimacy - rather, a tailored deflection that acknowledges the question without directly responding, pointing to some way the customer feedback IS making a REAL difference, and pointing to some positive action that the developers DID take.
(Note - even tailored deflections frankly wear thin after a while. Especially after months. There is really only so much you can do, and you really need written orders or a voice recording of orders telling you to use even tailored deflections if it’s on a months-long basis. You have to cover yourself after all).
Example - suppose you can’t address the legitimacy of the dice at all (orders). Say you can’t mention the development team won’t be coming out with export tools (orders). Say all you can say is the team is looking at “stabilized dice”.
“Thanks for continuing to provide your valued feedback. We continue to track and monitor all feedback for future development of 1942 Online and other potential Axis and Allies titles. At this time, the development team is working on planning and implementing a “stabilized dice” option that we hope players will enjoy.”
And that’s it. Nothing more. If you get responses like “the development team didn’t do a good study” - don’t reply. Because you’re under orders not to - right? That’s why we’re assuming you didn’t answer that directly in the first place. (We could say you didn’t understand, but that’s less flattering so let’s just leave it, especially as the recommended action doesn’t change on that basis anyways). You tell the customer they’re valued. You say their reports make a difference. And on some level that’s true. If you’re just throwing out reports, surely you must empty your trash folder every so often. Or maybe you’re angry that you have to deal with so much whatever stuff. On some level - on SOME level - customer reports ARE being monitored. And if there were no customer feedback, you’d be out a job, and you don’t want that. So you DO appreciate and monitor feedback - on SOME level. SOMEHOW. That’s the truth. And if some legitimate offer comes along to pour two million dollars into the project (say), of course you’d bring it to your bosses (it would be weird that they weren’t approached directly, but whatever.) So yeah. You ARE monitoring feedback and providing it to the ones that are making decisions. On SOME level. This is just truth, okay. I don’t know how much repackaging it requires to BE the truth, but what does it matter? Then you end by saying the developers did something. And that’s the end.
And when posters give you and the development team flak for not addressing this and that and the fifty thousand other things - JUST SAY NOTHING. If nothing is being done, they’re absolutely right to complain. Blanket denials work in SOME situations, but not after months of the same issue being brought up. It’s really a question of acknowledging or denying now - and if you answer a question but “evade”, it’s even WORSE than a TOTAL NON-ANSWER because once you go with a pseudo-response you’re digging yourself either into the hole of losing integrity, or making people think you don’t know what’s going on. Rather than dig yourself into that hole, you just stand on the ground you CAN be sure of - repeat again and again, this is what’s being done, we’re monitoring things, then after some months people will give you flak for literally nothing happening or even being announced, but what are you going to do? You don’t have an answer. So don’t try to give an answer. Just say this is what there is to be said, that’s an end of it, if you MUST acknowledge things, don’t attack their legitimacy, that just invites discussion and controversy and a whole bag of things you don’t want to deal with. Just leave it.
“I have Julius” - straight. Hopefully you don’t find that insulting.
“Sorry, then why did you comment that way?” - ugh. If I say “Sorry, why are you such a tremendous troll?” “Sorry, why are you a so and so?” Sorry, etc.". helps nothing - it just comes off worse.
Here, you’re questioning why someone commented the way they did. If you genuinely don’t understand something, then you do have to ask a question. But saying “why did you comment that way” is normally interpreted as saying “you should not have commented that way, now provide justification for what you did (and even after you provide justification you’re STILL wrong).” Really! There’s a power dynamic involved, and nobody likes being stepped on - yet that’s exactly what you’re doing to others when you do that. Especially when it’s shaped as a question. Oh my, yes.
So you have to write it differently. How? Again, remember - you want to acknowledge the legitimacy of what people are saying. You want to make them feel like their input is not only valued, but used in a way that makes a difference. Then you want to wrap it up trying to say the developers are doing their best and are, in fact, performing to reasonable expectations. Even if they aren’t. Especially if they aren’t.
So - and again hopefully this isn’t following an unfortunate exchange involving something like “Sorry, have you even read the link?” - how WOULD you impart a question in a respectful way, if the act of questioning can itself be insulting? You have to make STATEMENTS.
In this hypothetical - let’s someone said an issue wasn’t addressed. Suppose you thought it was. You asked for confirmation, they provide confirmation.
At that point - you MUST NOT respond saying things like “why did you comment that way”? They made a statement. You HAD YOUR CHANCE to reply and inquire and shape the narrative. When they blandly repeat their original statement (even if in slightly different words), you MUST NOT repeat what you wrote. You HAD YOUR CHANCE. Whether it’s your fault for not imparting your meaning or their fault for not understanding, you’re the representative of the company. The question of who was ultimately responsible is irrelevant - as it’s going to land in your lap REGARDLESS. You’re the one that has to act in a professional manner. Only you! Doubling down and questioning customer actions is NOT the thing to do, ESPECIALLY not with a literal question that implies a power dynamic, and sticking a “Sorry” in front of that just comes off as a backhanded slap.
Instead, lead with a statement that acknowledges what they wrote, and leaves the onus of not understanding on you. (Which is where it really is anyways.) Something like “Sorry, I thought by “fix for dice” you meant positive developer action to address possible differences between PRNG output and actual random numbers, which is something we intend to address with “stabilized dice”. I understand now that is not what you meant, but so I may address your question correctly, may I ask what, exactly, you mean by “fix for dice”? Please provide as much detail as possible so I may correctly understand and address your concern.”
Again, a question is a power dynamic - but since it’s prefaced with an apology and a statement to clear up understanding that puts the onus of responsibility on you rather than the poster, it’s a soft sincere question instead of a hard confrontational question. Then at the end you again place the responsibility of understanding on you by saying you want to correctly understand and address the concern - the subtext is that you’re asking for details ONLY BECAUSE IT IS ABSOLUTELY NECESSARY (which it is, especially if you don’t understand what they mean, which IS the case if they’re just repeating themselves).
And notice how exactly “I understand now that is not what you meant, but so I may address your question correctly, may I ask what, exactly, you mean by “fix for dice”?” is structured.
You lead with implication that YOU were at fault “I understand now” means you did NOT understand THEN. Then you say “so I may address your question correctly” - acknowledging that YOU are responsible for answering THEIR question, not the other way around. Only THEN, with those things ESTABLISHED, with the fault and onus ON YOU, do you ask what they mean. Which you did before, but you pack that all in one summary sentence to restate the point, make it REALLY clear you only ask a question in the interests of serving them - it’s not that they have any obligation to explain themselves to you.
==
And with all this I want to make the point - this is out of Western cultural expectations for customer service. If you’re fluent in English, but operating out of Eastern Europe, say, then namby pambying around can be seen as weakness that wastes everyone’s time. Or if you’re operating out of China or India, you just say “this is how it is” and the subtext is “and be grateful you’re getting even this much!” Even in Western cultural expectations, operating a business often cuts to the point (especially if you have leverage). But this is Western cultural expectations for customer service, and you don’t have leverage.