शैडोइंग अभ्यास: Why Do ERP Software Implementations Fail? [Top 5 Root Causes of ERP Failures] - वीडियो के साथ अंग्रेजी बोलना सीखें

अभ्यास मोड चुनें

हर मोड पूरी स्क्रीन का अभ्यास कक्ष खोलता है।

180 वाक्य

यदि वाक्य बहुत छोटे या लंबे हों, तो समायोजित करने के लिए Edit पर क्लिक करें।

It's no secret that most ERP implementations fail.

However, what is a secret is understanding why those implementations fail.

That's what I want to talk about here today.

My name is Eric Kimberling.

I'm the CEO of Third Stage Consulting.

We're an independent consulting firm that helps clients throughout the world reach their third stage of digital transformation success.

And there are many studies out there that show that anywhere between 70 to 80 percent or more of ERP implementations fail.

In fact, this statistic hasn't really changed much in the 25 years that I've been helping clients with their ERP implementations.

Technology has changed, the world has changed, and a lot of other things have changed,

but the one thing that seems to be consistent is that companies still struggle with their ERP implementations.

So what I want to do today is unpack this a bit more

and understand what those common root causes are of why ERP implementations fail

and more importantly help you understand what you can do differently to ensure that your project is successful.

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

and you avoid some of those root causes you are dramatically increasing your odds of success

and dramatically decreasing your odds of failure.

Now for more information about implementation best practices as it relates to your erp implementation

when you're done watching this video i encourage you to download

and read our lessons from 1000 erp implementations white paper it's a ebook

that we wrote that talks about 20 different best practices

and lessons learned from helping clients all over the world through their erp implementations

and digital transformations you can read

that ebook by scanning the qr code in front of you

or you can go to the links in the description field below.

The first common reason why ERP implementations fail is because organizations have unrealistic expectations to begin with.

And the reason this is so powerful is

because as fast as technology is changing and as much as technology can do today, it creates this false sense of hope

that we as an organization can quickly adapt to the software and we can quickly

realize business value from different technologies that are out there and don't get me wrong

erp software today can deliver dramatic value to most organizations the

problem is most organizations don't realize how difficult it is to

get from where you are today to where you could be with new technology and

so as a result what ends up happening is not only

do you have unrealistic expectations of how quick you might get to

that business value but when you realize

that a project is going to take longer than you expect it's going to cost more than expected

and require more resources than expected what ends up happening then is

that organizations end up scaling back

and throttling back on some of the key critical success factors

that are critical to make their project successful for example let's just say we have an organization

that thinks they can go through their erp implementation in 18 months

but 18 months was never realistic it was always going to take this organization say 24

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,

they start to realize that they have compressed a timeline that's just not at all realistic.

So they have one of two choices.

They can either delay the project and spend a lot more time and money than they expected,

which oftentimes is not possible with boards of directors and other executives holding the project team accountable,

or they can scale back on project activities and just try to force fit the ARP implementation into a shorter duration.

When they do the latter, what ends up happening is they end up cutting things that are absolutely critical to success.

They end up cutting things like organizational change management, or they'll cut a couple of iterations of user acceptance testing.

They might spend a little bit less time on requirements gathering up front

if they understand early on that they're behind the eight ball on the timeline.

So these are just a few examples of how organizations end

up making a bunch of bad decisions later in a project

because they had unrealistic expectations to begin with

so one of the biggest things you can do to ensure you avoid this pitfall is to ensure

that you have realistic expectations and do so by taking software vendor

and system integrator and implementation partner proposals on a time frame

and a budget take those with a grain of salt

and make sure you add your own dose of reality from an objective perspective to ensure

that you have the appropriate amount of time budget

and resources dedicated to the project the next common mistake

that organizations make that lead them to failure is

that they don't spend enough time and effort upfront in the implementation planning process

and this is a fascinating organizational dynamic that I've seen time

and time again throughout my career what ends up happening is you get an organization

that is committed to a digital transformation and an ERP implementation, they go through an evaluation process and they select the software

that they are convinced will be the right answer for them going forward

and it probably is it probably is the right answer

or a really good answer going forward and it's at

that point in the project that momentum

and excitement for the project is the highest it's never going to be

that high again so the team ends up rushing into the implementation

because they're excited they want to get started they want to start building stuff they want to see

and touch and feel the technology

and that's all good stuff you absolutely need to do that

but the problem with that is that

when you jump too quickly into the implementation phase without having a really solid plan

and a really solid vision of what it is you want to be

when you grow up as an organization you're going to spend a lot of time

and money later on spinning your wheels trying to figure out what it is you want to be

when you grow up when you're in the middle of an implementation

so the key here is to make sure you dedicate time

in your project it's sort of a phase zero an implementation

planning phase that's after the selection phase of the project

but it's before you get into the implementation and taking that time to really establish a blueprint for the project,

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,

mobilizing the resources, getting your change strategy in place, all that stuff, the more time you spend doing that up front,

you're going to save exponentially more time and money later on.

So it's critical that you spend time defining this implementation phase.

And to learn more about what this implementation phase should look like, I encourage you to check out this video right here.

This video for my YouTube channel dives into the implementation planning

and implementation readiness phase of the project in a lot more detail.

If you watch that video, it will describe some of the different activities you should be focused on to avoid this common pitfall.

Another common reason why ERP implementations fail is

because executives don't have a clear vision

or they haven't articulated a clear vision of what it is this ERP implementation is going to be to the organization.

Another common dynamic within this is that executive teams themselves oftentimes aren't aligned on what that vision is.

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

ऐप डाउनलोड करें

धाराप्रवाह बोलने के लिए ज़रूरी सब कुछ

AI उच्चारण स्कोरहर वाक्य का स्कोर

IPA अभ्यासहर ध्वनि में महारत

शब्दावलीअपना शब्द भंडार बनाएँ

शब्द गेमखेलते हुए सीखें

QR स्कैन करें

Download on theApp Store Get it onGoogle Play

✨ अनुशंसित वीडियो

4 वाक्य

Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table

Business EnglishUniversity StudentsWorking Adults

7 वाक्य

Communication Barriers

Business EnglishWorking Adults

75 वाक्य

How to EASILY Create a Driver-Based Forecast (FP&A)

Business EnglishWorking Adults

69 वाक्य

7 Programming myths that waste your time

Business EnglishUniversity StudentsWorking Adults

57 वाक्य

Top 5 Soft Skills For 2026 | Soft Skills Training | Most Important Skills To Learn | Simplilearn

Business EnglishWorking Adults

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो में शैडोइंग के लिए 180 वाक्य और 2601 शब्द हैं। बोला गया हिस्सा 13:44 लंबा है। वक्ता तेज़ बोलता है, लगभग 189 शब्द प्रति मिनट, इसलिए जुड़ी हुई और कमज़ोर ध्वनियाँ ज़्यादा मिलेंगी। 86% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं; बाकी शब्द अभ्यास से पहले देख लेना अच्छा रहेगा।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:

शब्द	उच्चारण	अर्थ
implementation संज्ञा	/ˌɪmplɪmənˈteɪʃən/	कार्यान्वयन
transformation संज्ञा	/ˌtɹæns.fɔɹˈmeɪ.ʃən/	रूपांतरण
lesson संज्ञा	/ˈlɛs.ən/	पाठ, सबक़
encourage क्रिया	/ɪnˈkʌɹ.ɪd͡ʒ/	प्रेरित करना
resource संज्ञा	/ɹɪˈzɔːs/	संसाधन
expectation संज्ञा	/ˌɛk.spɛkˈteɪ.ʃən/	आशा, अपेक्षा
realistic विशेषण	/ˌɹɪəˈlɪs.tɪk/	वास्तविक
odd विशेषण	/ɑd/	विचित्र, निराला
dynamic विशेषण	/daɪˈnæm.ɪk/	क्रियाशील, गतिशील
proposal संज्ञा	/pɹəˈpoʊzəl/	प्रस्ताव
establish क्रिया	/ɪˈstæb.lɪʃ/	स्थापना
select क्रिया	/sɪˈlɛkt/	चुनना, चयन करना
aspect संज्ञा	/ˈæspɛkt/	पक्ष
delay संज्ञा	/dɪˈleɪ̯/	देर, विलंब
hire क्रिया	/ˈhaɪɹ/	नियुक्त करना

इस वीडियो का व्याकरण

वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:

संरचना	वीडियो में
Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है	hasn't really changed · has changed · have compressed
Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है	aren't aligned · we've been hired · be defined

ध्यान देने योग्य उच्चारण

वक्ता 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× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर implementation, transformation, lesson जैसे शब्दों पर ध्यान दें।

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: Why Do ERP Software Implementations Fail? [Top 5 Root Causes of ERP Failures] - वीडियो के साथ अंग्रेजी बोलना सीखें

अभ्यास मोड चुनें

ऐप डाउनलोड करें

5 Strategies Of A Successful Project Engineer

Why people don't buy or use products

Introducing: Company Knowledge

RECAST - Why You Will Fail Without a COO | Cameron Herold (Podcast 598)

ALL OF BUSINESS Explained in 58 Minutes (No BS, No Fluff)

10 Human Resource Management Basics You Must Know

PHONE SALES TECHNIQUES THAT CLOSE (MY TOP 7)

Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table

Communication Barriers

How to EASILY Create a Driver-Based Forecast (FP&A)

7 Programming myths that waste your time

Top 5 Soft Skills For 2026 | Soft Skills Training | Most Important Skills To Learn | Simplilearn

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो की मुख्य शब्दावली

इस वीडियो का व्याकरण

ध्यान देने योग्य उच्चारण

इस वीडियो से अभ्यास कैसे करें

शैडोइंग तकनीक क्या है?