What IEs Need to Know about Change Management ◾ 25
stakeholder team solution. When completed, the IE solution will not be delivered into a vacuum,
but into an organization that is working “all out” to produce today’s products and services. If the
IE has not actively worked the stakeholders’ needs and requirements into her solution, the deliv-
ered solution is likely to become dead weight on a dusty shelf.
◾ Every IE problem or assignment always has an important team dimension that absolutely
must be considered and worked.
15. Industrial Engineers Must Speak the Language of
Operations, not the Other Way Around
Many an IE career has lost traction (or been terminated) because of the IE’s use of technical IE
language rather than the language of her organizational customer. Translating an IE solution into
the customer’s language is a vital step in completing any deliverable. Technical razzle-dazzle and
the latest buzz words do not increase credibility; they reduce it, frequently to a point that will
disqualify an IE for any presentations to management. If the customer’s language is not used, the
likely assumption is that the IE does not know enough about the business to be taken seriously.
◾ IEs speak the language of their customers.
16. No Way of Doing Business Lasts Forever
IEs live and work where change is the rule. For today’s organizations, change is no longer the
exception but the rule. Change is here to stay, and organizations (and technical professionals)
had better become very good at it. Today’s statistics say that 70% of organizational changes fail
to meet management’s intentions and expectations. IEs work to ensure their organizations are in
the 30% of the companies that succeed in making organizational changes; on target, on time, and
on budget.
◾ IEs lead and support organizational change, not undermine it.
17. Competent Organizational Decision Makers Should Always Process
Input from the Bottom up and Then Lead from the Top Down
What we know about leadership and management today is that the best decisions for organiza-
tions are based on top management’s consideration of input from the bottom of the organization up
and implementation of the decision from the top down. Following that contemporary best practice
requires the eective IE to perform well on two important organizational responsibilities.
e rst responsibility is to provide thoughtful, competent input up the organization through
his boss, by volunteering to be on a task team, by speaking up at employee meetings, or by post-
ing to the company’s intranet or bulletin board. Competent input should be tailored to t the IE’s
business competence (i.e., providing input about how the organization could implement a strategic
option, not about what that strategic option should be).
e second responsibility is to go “all in” to support the management decision that comes from
the top down. No regrets, no Monday morning quarterbacking, no whining or grumbling; just a
full-faith eort to support that decision.