
TCP
Home | <Previous Issue | Next Issue> | Issue Archive | About TCP
I s s u e E i g h t
June 22, 1999
c o n t e n t s / t h i s m o n t h :
1 > The Customer Food Chain
2 > NPD On The Web: MRT Website
3 > Guest Commentary: "PDMIC Help Desk:
Virtual Co-Location"
4 > Top Ten Signs Your Team Leader Might Be
Darth Vader
5 > MRT News
6 > MRT Calendar of Events
SUBSCRIPTION INSTRUCTIONS
To begin or cancel your FREE subscription, please use the automated form on this page or send me an email - gregg@roundtable.com
Please send any feedback about this newsletter and its content to gregg@roundtable.com
a r t i c l e - o n e :
THE CUSTOMER FOOD CHAIN
Part I: "You're not the customer of me"
From the "tree falling in the
woods" department: If a person pays you money for a good or service and you
weren't there to witness the transaction, are they a customer?
I never thought it was an issue, but recently I've become
aware of conceptual problems people have in determining who their customer is, and if it
is multiple people, which ones they should listen to. A lot of this confusion is created
by the concept of the "internal customer."
The idea of the "internal customer" is an
attempt, and a noble one at that, to elevate the importance of collaboration between the
people who stand before, alongside and after you in the development workflow. You might
have a problem with Joe in dept. X not delivering his piece of the project at the agreed
deadline or in the agreed format. However, if he is TQM-schooled to consider you his
"internal customer," it should motivate him to provide the higher quality of
service required as if his paycheck depended on it. There are three problems with this
scenario.
Number one, this assumes that Joe cares about customers at
all. Number two, this creates a dangerous situation that might encourage people to believe
the title of "customer" is accompanied by a teflon coated, management approved,
deity status. Number three, the fact is, his paycheck ALWAYS did depend on this type of
attitude, in fact, everyone in the company's paycheck does, but few people are ever
connected to that system-level insight (otherwise there would be no need for these types
of semantic games in the first place).
While I respect the idea and intent behind the
"internal customer" concept, in truth, there is only one, true customer. Do they
need a name or label? Let's call them the "ultimate" customer. This customer may
not even be the product's user. But they are definitely the person who controls the
purchase decision. Some organizations take the concept further and design systems where
one dept. actually "purchases" goods (parts/components) or services
(engineering/mfg) from another dept. But again, these are games - they may be effective in
some environments, but they are customer relationship "simulations" at best.
There is still only one customer.
Sure, there are other people along the way that can be
considered 'customers', but this is fruitful only if it does not blur your vision from the
true customer. You must not satisfy the needs of an internal customer at the expense of
the ultimate customer. All other "customers", while still important, need to be
secondary to the "ultimate" customer.
The motivation and action that the "internal
customer" concept is meant to stimulate should really be the standard approach
employed in any collaborative situation. You need to look beyond internal customers, until
you can also try to see, even if you must squint, the internal customers of YOUR internal
customer, all the way to the ultimate customer. Only then can this concept reach its true
intent.
I realize that what I've written could be considered
inflammatory to some people reading this, so I promise "equal time"
consideration to any well thought-out rebuttals to the ideas posed here. Please send them
to me at gregg@roundtable.com. For an even closer look at this issue, there is an
interesting article from Fortune magazine, "Another Fad Worth Killing," posted
here: http://www.pathfinder.com/fortune/1997/970203/lea.html
Next month: Part II - The Voice of THE Customer vs. The
Voice of A Customer
Reader Responses to this article
* * *
a r t i c l e - t w o :
NPD ON THE WEB
"Management Roundtable Website"
Link: http://ManagementRoundtable.com
As nepotistic as it is to review our own website,
I can honestly say that our redesigned site is worth a visit. Now with an updated,
cleaner interface, it's now easier to surf our site and click through to the many
resources we have available, such as conference follow-up information, online articles
from our Best Practices Report newsletter,
and, of course, TCP archives. We have many
plans to increase the site's value in the near future, with unprecedented access to NPD
case studies, research, expert advice and other leading-edge resources for product
developers. If you have any constructive suggestions for how we can make our
Internet presence of greater value to you, we welcome your input.
Know a website we should review? Send the url to gregg@roundtable.com
* * *
a r t i c l e - t h r e e :
GUEST COMMENTARY:
"PDMIC Help Desk: Virtual Co-Location"
This months commentary provided by Brion Carroll, CEO, Life Cycle Solutions, Inc. and
Product Data Management Information Center (http://www.PDMIC.com).
QUESTION: Our company has
recently merged with another company of similar size and interest. We both design and
manufacture barcode scanning equipment and are both reasonably well-equipped with a
variety of automated design tools. My boss has asked me (as the process guy and PDM/tool
guy) to look into how we can cooperatively develop product designs even though our offices
are 2500 miles apart. I am ready to do this, however, I am not finding a lot of papers,
books, publications that would be a roadmap or provide any basic information.
Any hints on how to find a few resources dealing with
wide-area collaborative product design and design tool integration?
ANSWER: To paraphrase your
question (hopefully with accuracy), the issue you are really dealing with is a buzzword
tossed about in the information age known as "virtual co-location". There is an
added dimension here of course that your needs stem from a merger/acquisition, but I will
assume that you are more concerned with the technical/financial/implementation issues
rather than the cultural/political.
I do not know the size of your respective companies or the
scope of the projects you undertake. I can say that those who have pioneered solutions to
this problem mostly come from very large scale project/product management, along the scope
of the Boeing 777 or the Motorola Iridium project, both of which may or may not have
insight you find applicable. More close to home may be work from distributed teams such as
Hewlett-Packard's 690 ink-jet printer series or any number of Caterpillar engine projects,
again, though, this deals with very large teams and projects.
A good place to start is to pickup a book called
"Knights of the Tele-Roundtable" by a woman named Jaclyn Kostner and published
by Warner Books, ISBN#: 0-446-51714-3 (this is NOT an endorsement, merely a suggestion).
This book deals more with management issues rather than the specific "how do I share
designs, drawings, documents, etc and implement an effective collaboration process",
however, further probing along this line may uncover more of what you're looking for. I
also suggest you employ Altavista or other search engines to look up the author and direct
your questions to her as well.
Other sources:
PDMIC Help Desk: http://www.pdmic.com/help/index.html
* * *
a r t i c l e - f o u r :
TOP TEN SIGNS YOUR TEAM LEADER
MIGHT BE DARTH VADER
...from the MRT home office in Lexington, Massachusetts
10. Uses
Jedi "choking" technique to dispel obnoxious CAD salesman
9. Reason for choosing new team member: "The Force is
strong in this one"
8. Uses exceptionally large laser pointer during
presentations
7. Personal e-mail address: dvader@empire.gov
6. Can predict schedule slips by "sensing a
disturbance" in Microsoft Project
5. Refers to accounting department as "Beancounting
Droids"
4. Demands office air conditioning be set extremely low
because of "asthma"
3. Can manipulate 3D computer models without using a mouse
2. Despite advanced technology, products easily defeated by
small, third world company of hirsute, bear-like midgets
...and the No. 1 sign your team leader might be Darth Vader:
1. Originally hired into organization as a consultant
Send
your Top Ten List suggestions to gregg@roundtable.com
* * *
a r t i c l e - f i v e :
MRT NEWS
Most product developers hear the word
"supply chain" and immediately think "NOT MY PROBLEM." From what we've
learned researching our next conference on this subject, nothing could be further from the
truth. Check out these links to learn more:
* * *
U p c o m i n g M R T e v e n t s
"Product Development & The Supply
Chain: Better Flow from Design to Customer"
September 13-15, 1999 - Austin, TX
http://www.roundtable.com/Event%20Center/SUP99/SUP99.html
* * *
A D M I N I S T R I V I A
The Critical Path is a free monthly e-mail newsletter
written by:
Gregg Tong, Director of Product Development
Management Roundtable, Inc., 1050 Waltham Street,
Suite 410, Lexington, MA U.S.A.
Tel: (781) 676-0606 Fax: (781) 676-1951
Gregg@roundtable.com
Please feel free to forward this publication to any friends or
associates you feel could benefit from its message. We welcome any suggestions, stories or
comments that will help us improve the value of this newsletter. Please contact me
directly with your input.
This newsletter and archived issues can be retrieved directly from our
website at the following url: http://www.roundtable.com/Critical%20Path/Critical-Path-Index.html
SUBSCRIPTION INSTRUCTIONS
To begin or cancel your FREE subscription, please use the automated form on this page or send me an email - gregg@roundtable.com
For more information on Management Roundtable's events, publications,
and services: http://ManagementRoundtable.com
© Copyright 1999 by
Management Roundtable, Inc. All rights reserved.
# # #
TCP
Home | <Previous Issue | Next Issue> | Issue Archive | About TCP
Reader
Responses
NOTE: Our
e-mail server was down on the night of Tuesday, June 22 (immediately after this newsletter
was distributed) - if you sent me a message during that time, chances are I did not
receive it. Please resend it to me at gregg@roundtable.com.
Sorry for any inconvenience.
Dear Critical Path:
The concept of the internal customer must die!
You will only get support from me. In the automotive
industry, current relationships between most North American OEMs and suppliers are
confrontational, at best. I believe this high level relationship has set a poor
example for some internal relationships within supplier organizations I have seen
far too many internal relationships based on the attitude "Your my internal customer,
so you have to do what I tell you to satisfy my needs, or I will be an unhappy
customer."
In many of these cases I have witnessed, internal customers
do not understand internal supplier requirements to satisfy needs. For example, an
IT project did not receive funding because it did not meet the financial requirements of
the accounting department. The project team did not understand concepts like
internal rate of return and cost of capital hurdles, and the Accounting Department did not
recognise customer requirements to implement the project for future programs. Who is
the customer in this situation? After all, the Accounting Department is looking
after the profitability of the company, and, in a time where suppliers are pressured to
keep down prices, this function is important.
The Engineering Department wants to fund a program that is
going to help communications with the OEMs with the expectations of getting more business.
In closing this thought, I believe the concept of internal customer, if not managed
properly, can be a detriment to an organisation by fortifying the towers that separate the
divisions.
I attended a seminar yesterday where Charlotte Roberts talked about sustaining profound
change. At one point in her lecture, she talked about the history of relationships
within the business world. This history included explanations about boss <->
subordinate, teams, and partners. She included some of the flaws in the thinking
relationships. Ms. Roberts' finished with a new school of thought - community type
relationships. If you think about it, this concept really makes more sense.
Anyway, you may want to look up her books. I think it will be interesting reading.
Don Smith
CAD/CAE Manager
The Standard Products Company
TCP: Relationships are what it's all about, and
although we can surround teams with metrics and policy guidelines to exact aligned
behavior, something fundamental always seems to be missing. You're right, the sense
of "community" rather than the series of one-to-one relationships of the
internal customer approach is a better perspective. Your specific examples seem
typical of the average multi-functional corporation, that has multiple internal
objectives. Rarely is there a person with high-level authority that sees the big
picture and can prioritize around the many tradeoffs in a well-informed manner for the
good of the "community". Too often, placation of egos is also involved.
MRT has some white papers available for download
that discuss the role of relationships as concluded from surveys done on NPD practices.
I will try to look up Ms. Robert's work as well. Thanks. --
Gregg
Dear Critical Path:
Your remarks are not inflammatory, however, I do beg
to disagree, slightly.
In our business, we have many people whose jobs never, and I mean
never, interface with a real, paying customer. The only customers they have are
those internal customers who need something from them to service the real customer. These
never interface with the customer folks have a distinct dis-advantage in that they never
really get to see the reward in winning a big contract or feel the frustrations when one
is lost. Their jobs, to a lot of them, appear to be meaningless.
That is why at Halliburton, we initiated the "Knock Your Socks
Off Customer Service" plan several years ago. It was focused not only on the front
line people who deal with real customers, it was also focused on the behind the scenes
people who never see or talk to real customers. One thing for sure came from this. We all
developed quite an inter-dependence on each other for achieving 100% total customer
satisfaction. We're not the Nordstrom's of the oilfield yet, but, we're getting there.
The books primary theme? Which we instituted and try to practice
religiously:
IF YOU DON'T DIRECTLY SERVE THE CUSTOMER, YOU BETTER SERVE SOMEONE
WHO IS.
It works and thanks for letting me offer my opinions. I enjoy your
roundtable and felt compelled to respond as this is something very close to my heart.
Thanks and keep up the great work!
Alfred Webb
CPE Global Marketing Coordinator
Halliburton
Dear Critical Path:
Our company Quality Policy states that we are "To exceed
all internal and
external customer expectations..." The word 'exceed' has come under fire a lot but
the words 'internal' and 'external' have increased the focus of some of our internal
departments.
We all understand that our external (ultimate) customer is King (America's
Best - Industry Week's Guide to World Class Manufacturing Plants).
I lead the Industrial Engineering group and because of our Quality Policy
Statement we have defined our internal customers as Sales (Sales quotes
priority #1) and the Shop Floor (Cost Improvements goal #1). To this
end I have tested, encouraged, and designed department goals around these top
priorities and goals. This more clearly defined why we exist, increasing our focus
for why we do what we do...
A short coming has been that upper management has not been diligent in
establishing an internal customer focus plant wide. But for those
departments that have taken the time to realize exactly who their internal
customers are the focus of their mission has been increased. And in the
chaotic business world FOCUS is the difference between unproductive chaos and productive
chaos (Tom Peters - Thriving on Chaos).
Yes, there are a lot of games. But, great ideas only become games when they don't
make sense. And many times the difference between games making sense and not making
sense is the way upper management designs and implements a strategy, i.e. the use of
Internal and Ultimate Customers phrases in a company's culture.
Bob Schroer
Wizard of WOW
Hi-Stat Manufacturing
TCP: Thanks, Bob, for you and your company's
perspective on this issue. I feel that I should clarify my statements about internal
customer "games". Of course, programs and initiatives that are
effective are not disputable. I guess my negativity comes from the "change
for change sake" programs that are quite obviously designed with 'ideal' rather than
'realistic' mindsets, and are consequently rejected by the culture. These types of
things are usually imposed and mandated rather than implemented, and are difficult to
change when challenged. I think it's frustrating when behaviour that is so clearly
beneficial to the system requires programs intended to "fake out" the minds of
an otherwise intelligent workforce. Of course, it is not the company's
responsibility to instill the type of personal responsibility that results in good
"internal customer service", but it is their job to define and clarify the
strategic goals that can help guide policy deployment, such as what you employ.
-- Gregg
|
Return to MRT Homepage

© Copyright 1999 by Management
Roundtable, Inc. |