Loading...
The intention is to deal with the situation quickly, but the opponent feels it is an attack. We have compiled sentences/rules to reduce misunderstandings in asynchronous communication.
Sentences like “fix this” and “until today” feel cold.
The text has no expression/tone, so the shorter it is, the stronger it becomes.
Add only 1 buffer: **1 line of context + 1 line of request**
“Why did you do this?” seems like an attack.
If the intent (curiosity/quality) is not shared, it becomes an interrogation.
Intention first: **“This is a quality check question”**
If I don't have an answer, I feel like the other person is ignoring me.
In asynchronous, the absence of ‘waiting rules’ increases the emotion.
SLA agreement: **“Response within 4 hours, @mention if urgent”**
It's not about work, but about emotional battles.
This is a misunderstanding that would not occur if it were offline.
When trust is shaken, the text becomes sharper.
Reduce short sentence aggression.
Example: “I’m checking because of my schedule. Please do it before 5 o’clock today.”
It sounds like collaboration, not interrogation.
Example: “What was the intention of this part (quality check)?”
Systemize your waiting.
Example: “Answer within 4 hours, @ if you’re in a hurry.”
Don't fight over text.
Example: “This could cause some misunderstanding, so can we just talk for 5 minutes?”
Try saying: “I’m checking because of the schedule. Can it be reflected before 5 o’clock today?”
Try saying: “(Confirmation of intent) I’m curious about the background of this choice. This is a quality check question.”
Try saying: “It’s not urgent, so please answer when it’s comfortable. Can you do it today?”
A. Even if you add just one line, the tone you feel will become significantly softer. If the ‘why’ is visible, it is less likely to be read as an attack.
I have a meeting, but when it's over, it feels like there's nothing left. We have organized a structure where decisions cannot be made and words/rules for reaching conclusions without breaking the team spirit.
A team where only the talkative people keep talking, and the quiet people speak separately after the meeting. How to reduce the variation in speaking volume through ‘rules’ rather than ‘people problems’.
A team that loses speed while trying to reduce risk. This is not to abandon perfectionism, but it is a way to ‘stage’ perfection so that the team can safely become faster.
A team that is quiet in meetings, but whose complaints only leak out behind the scenes. We have organized devices that change feedback from being a battle between people to a ‘fight for results.’