ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: Why Do ERP Software Implementations Fail? [Top 5 Root Causes of ERP Failures]
กำลังสร้างบทเรียน...
1
It's no secret that most ERP implementations fail.
2
However, what is a secret is understanding why those implementations fail.
3
That's what I want to talk about here today.
4
My name is Eric Kimberling.
5
I'm the CEO of Third Stage Consulting.
6
We're an independent consulting firm that helps clients throughout the world reach their third stage of digital transformation success.
7
And there are many studies out there that show that anywhere between 70 to 80 percent or more of ERP implementations fail.
8
In fact, this statistic hasn't really changed much in the 25 years that I've been helping clients with their ERP implementations.
9
Technology has changed, the world has changed, and a lot of other things have changed,
10
but the one thing that seems to be consistent is that companies still struggle with their ERP implementations.
11
So what I want to do today is unpack this a bit more
12
and understand what those common root causes are of why ERP implementations fail
13
and more importantly help you understand what you can do differently to ensure that your project is successful.
14
The good news is that this isn't rocket science, there's no big surprises here, but when you understand what those root causes are
15
and you avoid some of those root causes you are dramatically increasing your odds of success
16
and dramatically decreasing your odds of failure.
17
Now for more information about implementation best practices as it relates to your erp implementation
18
when you're done watching this video i encourage you to download
19
and read our lessons from 1000 erp implementations white paper it's a ebook
20
that we wrote that talks about 20 different best practices
21
and lessons learned from helping clients all over the world through their erp implementations
22
and digital transformations you can read
23
that ebook by scanning the qr code in front of you
24
or you can go to the links in the description field below.
25
The first common reason why ERP implementations fail is because organizations have unrealistic expectations to begin with.
26
And the reason this is so powerful is
27
because as fast as technology is changing and as much as technology can do today, it creates this false sense of hope
28
that we as an organization can quickly adapt to the software and we can quickly
29
realize business value from different technologies that are out there and don't get me wrong
30
erp software today can deliver dramatic value to most organizations the
31
problem is most organizations don't realize how difficult it is to
32
get from where you are today to where you could be with new technology and
33
so as a result what ends up happening is not only
34
do you have unrealistic expectations of how quick you might get to
35
that business value but when you realize
36
that a project is going to take longer than you expect it's going to cost more than expected
37
and require more resources than expected what ends up happening then is
38
that organizations end up scaling back
39
and throttling back on some of the key critical success factors
40
that are critical to make their project successful for example let's just say we have an organization
41
that thinks they can go through their erp implementation in 18 months
42
but 18 months was never realistic it was always going to take this organization say 24
43
or 30 months to go through their implementation What ends up happening is when the organization gets partway through that project, maybe halfway through or two -thirds of the way through,
44
they start to realize that they have compressed a timeline that's just not at all realistic.
45
So they have one of two choices.
46
They can either delay the project and spend a lot more time and money than they expected,
47
which oftentimes is not possible with boards of directors and other executives holding the project team accountable,
48
or they can scale back on project activities and just try to force fit the ARP implementation into a shorter duration.
49
When they do the latter, what ends up happening is they end up cutting things that are absolutely critical to success.
50
They end up cutting things like organizational change management, or they'll cut a couple of iterations of user acceptance testing.
51
They might spend a little bit less time on requirements gathering up front
52
if they understand early on that they're behind the eight ball on the timeline.
53
So these are just a few examples of how organizations end
54
up making a bunch of bad decisions later in a project
55
because they had unrealistic expectations to begin with
56
so one of the biggest things you can do to ensure you avoid this pitfall is to ensure
57
that you have realistic expectations and do so by taking software vendor
58
and system integrator and implementation partner proposals on a time frame
59
and a budget take those with a grain of salt
60
and make sure you add your own dose of reality from an objective perspective to ensure
61
that you have the appropriate amount of time budget
62
and resources dedicated to the project the next common mistake
63
that organizations make that lead them to failure is
64
that they don't spend enough time and effort upfront in the implementation planning process
65
and this is a fascinating organizational dynamic that I've seen time
66
and time again throughout my career what ends up happening is you get an organization
67
that is committed to a digital transformation and an ERP implementation, they go through an evaluation process and they select the software
68
that they are convinced will be the right answer for them going forward
69
and it probably is it probably is the right answer
70
or a really good answer going forward and it's at
71
that point in the project that momentum
72
and excitement for the project is the highest it's never going to be
73
that high again so the team ends up rushing into the implementation
74
because they're excited they want to get started they want to start building stuff they want to see
75
and touch and feel the technology
76
and that's all good stuff you absolutely need to do that
77
but the problem with that is that
78
when you jump too quickly into the implementation phase without having a really solid plan
79
and a really solid vision of what it is you want to be
80
when you grow up as an organization you're going to spend a lot of time
81
and money later on spinning your wheels trying to figure out what it is you want to be
82
when you grow up when you're in the middle of an implementation
83
so the key here is to make sure you dedicate time
84
in your project it's sort of a phase zero an implementation
85
planning phase that's after the selection phase of the project
86
but it's before you get into the implementation and taking that time to really establish a blueprint for the project,
87
a blueprint for your business processes and what the organization is going to look like, which modules you're going to deploy and when, how are you going to resource the project,
88
mobilizing the resources, getting your change strategy in place, all that stuff, the more time you spend doing that up front,
89
you're going to save exponentially more time and money later on.
90
So it's critical that you spend time defining this implementation phase.
91
And to learn more about what this implementation phase should look like, I encourage you to check out this video right here.
92
This video for my YouTube channel dives into the implementation planning
93
and implementation readiness phase of the project in a lot more detail.
94
If you watch that video, it will describe some of the different activities you should be focused on to avoid this common pitfall.
95
Another common reason why ERP implementations fail is
96
because executives don't have a clear vision
97
or they haven't articulated a clear vision of what it is this ERP implementation is going to be to the organization.
98
Another common dynamic within this is that executive teams themselves oftentimes aren't aligned on what that vision is.
99
And so when you have an executive team
100
that doesn't have alignment amongst themselves and or they haven't clearly defined
101
and articulated to the organization what this ERP implementation means to the organization going forward, that's going to create a lot of problems,
102
confusion, chaos, and misdirection as it relates to the ERP implementation.
103
Now a lot of times executives will say well we're going to go through this ERP implementation because we have to.
104
Our software vendor is forcing us off our old legacy system
105
and now we need to move to a migration to a newer software.
106
Or it could be that our old system is old, it's broken, we can't scale as a company and therefore we need new technologies and tools to help us grow.
107
Those are good starting points, but that cannot be the basis and the foundation for the entire justification for why you're going through the project.
108
You need to have and articulate a clearer vision of what the ERP implementation is going to do for the organization.
109
For example, is it going to help us improve our customer experience?
110
If so, how?
111
Is it going to improve the employee experience?
112
If so, how?
113
What are some of the details of how that will look?
114
Is it going to help us improve our operations, help us be more efficient help us sell more
115
and generate more revenue whatever the business benefits are you want to not only define what they are
116
and what the value is to the organization
117
but get into more detail and granularity of what that operating model
118
and that organizational model is going to be in
119
that future state it's not enough to say we're just going to deploy sap
120
or oracle or microsoft or whatever it is you need to go beyond
121
that and clearly articulate what the vision for the project is.
122
And the more time and effort you spend defining this vision and the more effective you are at defining that vision,
123
the more tailwinds you'll have supporting you and the project team going through the ERP implementation.
124
So one of the biggest things you can do to avoid ERP implementation failure is to ensure
125
that before you get started on your implementation, that you have that clear alignment and vision from the executive team.
126
One of the most common root causes for ERP implementation failure is a lack of focus on organizational change management.
127
Or if there's a focus on organizational change management, it just isn't effective.
128
This is one of the root causes that can lead to a lot of other symptoms within an ERP implementation.
129
And simply put, if you don't address the people side of change, you don't ensure that your people are fully adopting new processes and new tools,
130
you're just going to end up with a bunch of shelfware or investments in technology that is not delivering business value,
131
and that has to lead you to the question of why are we doing this project in the first place
132
if we're not getting the business value that we could and should be getting from it.
133
So the key here is to not get too caught up in the technology pieces and components of your ERP implementation,
134
but instead to focus more time and effort on the organizational change management piece.
135
Because the better job you do on organizational change management, the more likely it is you are to be successful.
136
And when we look at ERP implementation failures, particularly as it relates to lawsuits that we've been hired to testify in in courts,
137
we find that the number one most common theme and pattern among those failures is a lack of organizational change management.
138
The organization did not focus, for whatever reason, enough on organizational change.
139
They didn't address the people aspects of change, and they focused too much time and effort on the technology sides of change.
140
So one of the biggest things you can do is ensure
141
that you have a solid and effective change management strategy and plan before starting your ERP implementation.
142
Now for more advice and tips on how to create that organizational change strategy and plan, I encourage you to check out my playlist, which you can find right here.
143
It's a YouTube playlist that has all of my YouTube videos that talk about organizational change management.
144
So check out this link right here.
145
That'll give you a playlist that you can go through
146
and watch some more videos
147
that describe how to go about the change management process now the fifth
148
and final reason I'll talk about today of why ERP implementations fail is
149
because the organization doesn't have a clear definition of success how
150
will we define success of our ERP implementation for some organizations it could be
151
that we're going to come in on time and on budget
152
and that alone is a tricky proposition and most organizations fail at even that most basic fundamental definition of success. But beyond
153
that, most organizations don't have a good vision of what it
154
is they want to get out of the ERP implementation after they've gone through it.
155
In other words, what is our business case?
156
What's the ROI?
157
Where are we going to get the business value?
158
Where are the dollars and cents going to come from?
159
Those are all things that need to be defined clearly on, not only so that we can ensure that we maximize the business value post -implementation, but just as importantly, so
160
that we have clear direction as we're going through the implementation itself in other words having
161
that clear vision of success can serve as a sort of a guardrail for the project
162
and a north star
163
that guides us in the right direction as we're going through the implementation every erp implementation room requires hundreds
164
if not thousands of decisions about how your business is going
165
to run how it's going to look what sorts of technologies you will
166
or will not deploy whether or not you're going to configure the software
167
or customize the software or integrate it to other third -party systems a lot of different decisions
168
that materially affect the scope and the cost and the risk of the project.
169
And if you don't have
170
that clear vision for what it is success looks like for the project
171
and what you want your organization to look like on the other side, then you're headed aimlessly into the darkness of digital transformation or an ERP implementation.
172
So these are five of the most common reasons why ERP implementations fail.
173
And hopefully I've given you some tips and guidance on how to avoid some of these common pitfalls.
174
For more information and best practices around ERP implementation, I encourage you to download our Lessons from 1000 ERP Implementation eBook,
175
and that eBook will provide a number of best practices and lessons that will help you through your digital transformation, including some additional risks and pitfalls to be aware of,
176
in addition to what I've talked about here today.
177
So you can read that eBook by scanning the QR code in front of you, or you can click on the links in the description field below.
178
So I hope you found this information useful, and hope you have a great day.
179
understand why that is I didn't like that some of those pipe pit that now the fifth and final
180
fifth and final what oh okay I'm like what are we talking about what's this video about I don't remember
✨ วิดีโอแนะนำ
C141 ประโยค
🚨 Most organizations don't fail ISO/IEC 27001 because they don't understand the standard...
Business EnglishUniversity StudentsWorking Adults
C11
180 ประโยค
Armchair Architects: Resiliency in the Cloud – Core Patterns
Business EnglishUniversity StudentsWorking Adults
C11
75 ประโยค
How to EASILY Create a Driver-Based Forecast (FP&A)
Business EnglishUniversity StudentsWorking Adults
B22
142 ประโยค
Lose Weight Easier -- Stop Doing These 5 Things!
Business EnglishUniversity StudentsWorking Adults
C14
36 ประโยค
Overcoming Service Blueprinting Frustrations
Business EnglishUniversity StudentsWorking Adults
C11
120 ประโยค
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table
Business EnglishUniversity StudentsWorking Adults
B21
496 ประโยค
Shopify CEO Tobi Lütke Shares His Secrets to Entrepreneurial Success
Business EnglishInterview EnglishUniversity Students
C14
32 ประโยค
What is the PMI MORE Strategy?
Business EnglishUniversity StudentsWorking Adults
C12
54 ประโยค
The art and science of failing well
Business EnglishUniversity StudentsWorking Adults
C11
443 ประโยค
Functional-Oriented Documentation in Automation - Eplan & IEC 81346 Explained
Business EnglishUniversity StudentsWorking Adults
C12
43 ประโยค
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
Business EnglishUniversity StudentsWorking Adults
C1480 ประโยค
Everything Valuable from an MBA in 25 minutes
Business EnglishUniversity StudentsWorking Adults
คำศัพท์และข้อสังเกตด้านการพูดสำหรับบทเรียนนี้
วิดีโอนี้มี 180 ประโยค และ 2601 คำ สำหรับฝึกพูดตาม ช่วงที่มีเสียงพูดยาว 13:44 ผู้พูดพูดเร็ว ประมาณ 189 คำต่อนาที จึงมีการเชื่อมเสียงและลดเสียงค่อนข้างมาก 86% ของคำอยู่ใน 3,000 คำที่ใช้บ่อยที่สุดในภาษาอังกฤษ ส่วนที่เหลือควรดูไว้ก่อนเริ่มฝึก
คำศัพท์สำคัญในวิดีโอนี้
คำที่ควรเรียนรู้ 15 คำจากวิดีโอ พร้อมคำอ่านและความหมาย:
| คำศัพท์ | คำอ่าน | ความหมาย |
|---|---|---|
| lesson คำนาม | /ˈlɛs.ən/ | บทเรียน |
| encourage คำกริยา | /ɪnˈkʌɹ.ɪd͡ʒ/ | ให้กำลังใจ, ส่งเสริม |
| resource คำนาม | /ɹɪˈzɔːs/ | ทรัพยากร |
| realistic คำคุณศัพท์ | /ˌɹɪəˈlɪs.tɪk/ | สมจริง |
| consult คำกริยา | /ˈkɑnsʌlt/ | ปรึกษา, หารือ |
| vendor คำนาม | /ˈvɛn.dɚ/ | ผู้ขาย |
| alignment คำนาม | /əˈlaɪn.mənt/ | การปรับแนว, การปรับตรง |
| proposal คำนาม | /pɹəˈpoʊzəl/ | ข้อเสนอ |
| select คำกริยา | /sɪˈlɛkt/ | คัดเลือก |
| delay คำนาม | /dɪˈleɪ̯/ | ดีเลย์ |
| hire คำกริยา | /ˈhaɪɹ/ | จ้าง |
| spin คำกริยา | /spɪn/ | หมุน, ปั่น |
| legacy คำนาม | /ˈlɛɡəsi/ | มรดก |
| objective คำนาม | /ɒbˈd͡ʒɛk.tɪv/ | เป้าหมาย |
| fundamental คำคุณศัพท์ | /ˌfʌn.dəˈmɛn.təl/ | พื้นฐาน, เบื้องต้น |
ไวยากรณ์ในวิดีโอนี้
โครงสร้างที่ผู้พูดใช้บ่อยที่สุด พร้อมคำพูดจริงจากวิดีโอ:
| โครงสร้าง | ในวิดีโอ |
|---|---|
| Present perfect have/has + กริยาช่อง 3 — เหตุการณ์ในอดีตที่ยังเกี่ยวข้องกับปัจจุบัน | hasn't really changed · has changed · have compressed |
| Passive voice be + กริยาช่อง 3 — เน้นสิ่งที่เกิดขึ้น ไม่ใช่ผู้กระทำ | is committed · are convinced · should be focused |
การออกเสียงที่ควรระวัง
ผู้พูดใช้รูปย่อและรูปลดเสียง 50 ครั้ง เช่น don't, you're, we're ให้พูดแบบสั้นตามที่ได้ยิน
- เสียง “th”: gather /ˈɡæðɚ/, throttle /ˈθɹɔ.tl̩/
- เสียง “sh” และ “zh”: implementation /ˌɪmplɪmənˈteɪʃən/, organizational /ˌɔː(ɹ)ɡənɪˈzeɪʃənəl/, transformation /ˌtɹæns.fɔɹˈmeɪ.ʃən/, expectation /ˌɛk.spɛkˈteɪ.ʃən/, rush /ɹʌʃ/
- คำยาว — ลงเสียงหนักให้ถูกพยางค์: implementation /ˌɪmplɪmənˈteɪʃən/, organizational /ˌɔː(ɹ)ɡənɪˈzeɪʃənəl/, transformation /ˌtɹæns.fɔɹˈmeɪ.ʃən/, expectation /ˌɛk.spɛkˈteɪ.ʃən/, articulate /ɑːɹˈtɪk.jə.leɪt/
วิธีฝึกกับวิดีโอนี้
- ฟังวิดีโอให้จบหนึ่งรอบโดยยังไม่ต้องพูด แล้วจดคำที่ยังไม่รู้จัก
- เริ่มที่ความเร็ว 0.75× พูดตามทีละประโยค แล้วกลับไปใช้ความเร็วปกติเมื่อเริ่มคล่อง
- อัดเสียงตัวเองแล้วเทียบกับต้นฉบับ โดยสังเกตคำอย่าง lesson, encourage, resource เป็นพิเศษ
เทคนิค Shadowing คืออะไร?
Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ