レッスン詳細

日本と海外の意思決定スピードの違いについて話してみよう
作成したスクリプトは講師により添削されます。
Becase most of Japanies comanies hhave hierarchical structure. We have to get an approval from our boss. On top of that, there's a long process before I can even bring it to them.
We tend to prefer making decisions by consensus, so We have to get agreement from all our team menbers. While this isn't written officially, it's alomist like an obligation.
Because most Japanese companies have a hierarchical structure, we have to get approval from our boss. On top of that, there's a long process before one can even bring it to them.
We tend to prefer making decisions by consensus, so we have to get agreement from all our team members. While this isn't written officially, it's almost like an obligation.
Totally agree.
While it could hold things up, making consensus helps us move projects forward after approvals. Conflicts rarely occur.
When I dealt with an emergency project, I found it was very troublesome. We had to make our decision as quickly as possible, but we couldn't. Furthermore, once we did, it wasn't easy to change it.
I totally agree.
While it could hold things up, reaching consensus helps us move projects forward after approvals. Conflicts rarely occur.
When I dealt with an emergency project, I found it was very troublesome. We had to make our decision as quickly as possible, but we couldn't. Furthermore, once we did, it wasn't easy to change it.
In addition to emergency situations, when we develop something new, we should adopt a faster decision-making style, like the agile approach.
This is because we can't fully know what decisions are best for systems which no one has seen or used yet.
In addition to emergency situations, when we develop something new, we should adopt a faster decision-making style, like the agile approach.
This is because we can't fully know what decisions are best for systems that no one has seen or used yet.
Yes, I have. I'm working as systems engineer on a risk calculation system.
We adopted Agile methods for a project where we implemented a new risk model because no one knew what to do with the new risk model.
You know, we failed many times, thanks to the Agile methods, but we were able to adjust our plans flexbily. The last question is deep one, but I personally think that we shouldn't worry so much about small failures. I think Japanese people worry too much about failing. However, we should understand that small failures lead to big success.
Yes, I have. I'm working as a systems engineer on a risk calculation system.
We adopted Agile methods for a project where we implemented a new risk model because no one knew what to do with the new risk model.
You know, we failed many times, thanks to the Agile methods, but we were able to adjust our plans flexibly. The last question is a deep one, but I personally think that we shouldn't worry so much about small failures. I think Japanese people worry too much about failing. However, we should understand that small failures lead to big successes.
What do you think companies can do to create a culture that embraces small failures more openly? And do you think this mindset shift could work in other areas outside of tech or engineering?
To embrace small failures, it is important that people feel more comfortable pointing out others' failures. Japanese people typically avoid mentioning others' mistakes. However, we can't recognize small failures unless someone points them out.
In my view, to avoid this, we should have more conversations with each other.
If we usually communicate with each other and understand our character, we are able to feel comfortable to bring up failures.
To embrace small failures, it is important that people feel more comfortable pointing out others' failures. Japanese people typically avoid mentioning others' mistakes. However, we can't recognize small failures unless someone points them out.
In my view, to avoid this, we should have more conversations with each other.
If we regularly communicate with each other and understand our characters, we will be able to feel comfortable bringing up failures.
2. 'Regularly' is more appropriate when referring to consistent and habitual actions.
3. Use the plural form for general references.
4. This change clarifies the future conditional aspect of the statement.
5. The gerund is more appropriate following 'comfortable' in this context.
関連単語
- stalemate(行き詰まり)
- stonewall((形)議事進行妨害の、(動)~に協力しない、~を妨害する)
- risky(リスキー、危険な[を伴う])
- tenacious(粘り強い、しっかりつかんで離さない)
- consensus(ほぼ一致した意見、合意すること)
- committee(委員会)
- inclusive(すべてを含んだ、包括的な)
- feudalism(封建的な制度)
- streamline(無駄をなくして合理化する)
- rooted(根付いた、駄目になった)
関連フレーズ
- Perhaps foreign companies are too quick to take risks and do so without considering all possible consequences.(おそらく海外企業は、意思決定が速すぎてリスクを負うことがありません。そして全ての起こりうる影響を考慮せず決定します。)
- Deliberation is a very important component of the Japanese business culture.(念入りな審議は日本のビジネス文化でとても重要な構成要素です。)
- What happens when a stalemate is reached in a business discussion?(ビジネス討論で行き詰まったら何が起きますか?)
- Lengthy decision making is seen as the Achilles heel for Japanese companies.(決断するのに時間がかかるということは日本の会社の弱点とみられています。)
- Japan's decision making process has its roots in feudalism.(日本の意思決定におけるプロセスは封建制度に根付いています。)
- Do you think that Japanese companies are too cautious in their decision making?(決断をするにあたって、日本の会社は注意深すぎると思いますか?)
- The downside to collaboration and consultation is that it tends to be very time-consuming.(連携・相談のデメリットは、時間が非常にかかりがちなことです。)
- Foreigners sometimes get a bit frustrated when dealing with the relatively slow process of decision making in Japanese companies.(日本の会社の決断プロセスが比較的遅いことに関して、外国人は時々やや苛立ちます。)
- Why are decisions made so quickly among American companies?(アメリカの会社ではなぜそんなに早く決断がなされるのですか?)
- Is it better to streamline the decision making process or continue to involve all stakeholders?(意思決定の過程を能率的にする方が良いか、全出資者を関与させ続ける方が良いか。)
こんな方にオススメ
2. Rephrased for grammatical correctness and clarity.
3. Correct punctuation. We use a comma here instead to separate the dependent clause from the independent clause.
4. 'An' is unnecessary here as 'approval' is used in the general sense.
5. Correct pronoun usage.
6. There is no need to capitalise here.