Greetings!
How about some real-world management cases?
That's what this Newsletter/E-zine is about. Real cases with real results.
First there's a discussion of how to motivate people. Motivation is obviously critical if you're going to be managing direct reports!
Then two examples of real-world situations.
- One with my solution.
- And one that is left for you to solve.
- You can think about how you might handle the situation and you can email me with your suggested strategy (I'd be interested to know your thoughts) or you can wait until next month and I'll tell you how I delt with it, or you can do both.
Please enjoy and be well.
Steven Cerri
Note: If you have missed any of my previous e-zines/newsletters you can find them archived at: Archived E-zines/NewslettersNote-Note: I could have put short summaries in each section and then sent you through links to different web pages, but who wants to bounce around. Everything is right here in this one email. No links to other URLs. Just click on the article titles immediately below this box to move to those topics you are interested in and avoid those you're not. This newsletter/e-zine is a 20 minute read.
|
Article #1: "Motivation By Reference." (10 minute read)
|
Have you ever noticed how people make decisions? Most of us haven't analyzed this topic. But how we and others make decisions is directly tied to motivation. And the way we process data directly relates to how we make those decisions to be motivated to do something or not.
Let me give you an example. Many years ago I purchased my first single-lens-reflex (SLR) camera. I was at a point in my life where I wanted to buy an SLR and as a college student it was a big investment. So I wanted to buy a camera that I knew would be what I wanted.
And that was the major question. "What do I want and why?" Perhaps because I was an engineer I decided to build a matrix. The matrix was on a large piece of paper (2' x 3') so I could view all the information at once. I took every conceivable parameter that I could evaluate and compared those parameters in twenty different SLR cameras.
Using the matrix and all the parameters in my matrix, I narrowed my search down to three cameras. Then I went to a camera store and asked to see and hold each of the three finalists. I held each camera as if I was using it to take pictures. I played with the controls. I took off each of the lenses. I asked the attendant questions. Finally, I selected the one that "felt" the best in my hands. I purchased that camera and I've loved it ever since.
That is how I made my decision to buy my camera. But was it a random process or was their some predictability to it? Do I do that every time I buy something? Have you noticed how you make decisions or is it something that you don't give any thought too?
I can tell you that the process is not random. It is predictable. In fact, if you watch closely you will notice that there are certain people who make decisions based on reviewing evidence, talking to people, and gathering information. They gather as much "external" data as possible before making a decision. If they want to buy a car, they read magazines, they go on-line to read reviews, they talk to people who own the cars they are considering. They believe the idea that word of mouth is the most important type of marketing and the most important source of accurate information. This is exactly what I did in the first part of my decision process by doing research and constructing a matrix.
You've probably noticed other people who seek information from no one, but instead make decisions based on a set of rules "inside their heads"? They want a personal experience or they go through a personal, internal process to make their decisions. If they are interested in buying a car they'll go for a test drive. They'll rent the car for a week and see how it feels, how it drives. They'll decide what car to buy based on their own experience of the car. This is what I did in the second portion of my camera buying decision by holding each of the cameras and running scenarios as if I was taking pictures with each.
Therefore, in the first portion of my decision-making process I sought out external information, while in the second portion I wanted to experience it for myself.
Now you might say, "Well that was about buying a camera and that was a long time ago. That probably doesn't have much to do with the present or with management in my technical organization." Well, let's see.
Lets fast-forward from my college days to just a couple of years ago and see if my purchasing strategies had changed over time.
Several years ago I wanted to buy a kayak. I decided to make my decision by learning all I could about kayaks. This seemed reasonable since there a many different types of kayaks and I wanted to understand what my choices were.
I searched the Internet, read magazines, and talked to dozens of people about the different types of kayaks. In the course of a couple of weeks, I had accumulated more than enough "research" information for my decision and although I didn't make a matrix of the data I had a "sense" of the groups I would choose from. But I didn't know how to choose the right kayak from the narrowed field I had developed. I felt overwhelmed by the different choices and I didn't have an innate sense of how to prioritize and filter the remaining choices.
My next step was to attempt to find some way to "personally" experience the various kayaks I had placed in the final group. That meant I had to do something that would give me the personal experience I needed to filter and prioritize and decide which kayak to buy. I needed to actually use each kayak that I thought would be a choice. I sought out an opportunity to use several different kayaks. I found an outdoor store that was sponsoring a day on the water with kayaks. Potential customers could use as many kayaks as they wanted for the day to get a sense of what kayaking was all about. I now had my chance to actually use several different kayaks. So I jumped at the chance to spend a day on the bay.
It soon became clear to me which kayak I wanted to buy. Not because someone told me but because of my personal experience using it. I could now make my decision based on my own experience, my own "internal" experience.
If you look closely at my two buying strategies, for the camera and the kayak, you'll notice that they are the same. In both cases I did "external" research until I reduced the possible candidates down to something I could experience, and then I had an "internal" experience of each. From there it was easy to make my decision.
In the vocabulary of communication, management and linguistics, we say that when I was doing research I was being "externally referenced" and when I was gathering information from my own personal experience I was being "internally referenced".
Therefore, my buying strategy for purchasing both the camera and the kayak was to be "externally referenced" first, by seeking information from the outside world and to be "internally referenced" second, by gaining a personal experience. This allowed me to feel comfortable that I understand my choices and then to feel confident in my decision.
Why is this such a big deal?
The reason I'm spending time on these examples is that I want you to understand that decision-making strategies are not arbitrary, they are predictable. Human beings have "processes" that we use over and over again because, from our personal perspective, they work.
And I'm not making arbitrary distinctions. Just as a computer has software applications that we run to solve certain types of problems, each of us has a set of internal mental programs I call Personal Behavioral Sub-Routines (PBSR) that we "run" when we want to solve problems or make decisions. Some people use certain PBSRs that allow them to make their decisions using "external references". That is, they seek information from the outside world. They want to know what others think, what others have experienced. Other people use PBSRs that rely instead on their own "internal experience" to decide. They rely on an "internally referenced" program to make a decision. And some people use a combination of both and in different order.
Does this has to do with management?
What does this have to do with technical management and with motivation? Actually, everything. Whether we are talking about your technical customer, your boss, your direct reports, or your colleagues, each person makes decisions using data from a specific set of sources and by a specific set of processes. People also use these processes (their PBSRs) to either be motivated to do something or to not do it. People either gather data from certain types of external sources or they use their own internal source and / or some combination of both, but the process is predictable.
And here is the significant point; if a person can't get the information the way they want it (i.e., either internally or externally referenced in the way they want it) then they won't make the decision or they won't be motivated. As in the examples of my camera and kayak purchases, if I had been unable to get the internally referenced information, I would not have made the decision. In your business world, if your boss, your colleagues, or your customer, can't get their information the way they want it, they won't make the decision they and you want them to make. This means that if you don't motivate someone according to their "motivation" Personal Behavioral Sub-Routine they won't get motivated. It's that simple and that subtle.
Therefore, what makes this so important for management is that if you attempt to convince a person by using a strategy that doesn't match theirs, one that doesn't match their PBSRs, you will frustrate them and they will resist your influence.
My basic premise in management is that everyone is doing what they think is best at the time. Therefore, if someone is resisting you it's not because they want to be difficult. It's probably because they truly believe that they are doing what is best for them, for the company, and for the task. If this assumption is true then it is your responsibility, the person who is trying to motivate them, to change your motivation strategy to fit what they need to see, hear, and know in order to be motivated. In reality, this is the way it works all the time, even if you don't know it on a conscious level. Everyone is motivated to do anything; have dinner with you; take your direction; vote for a presidential candidate; like a specific song; all because the communication and the data they receive resonates and matches the data they want in the way they want it.
Some Examples: Let's take several examples. Let's say you have a client to whom you are trying to sell your product. If your client is internally referenced they will want a personal experience of your product or service, or they'll want to understand the subject for themselves. If you keep offering them the names and phone numbers of your other satisfied customers for them to contact, you are giving them external references. That's not what they want and they will become frustrated. They want to experience and understand your product for themselves.
On the other hand, if your client is externally referenced, they will want to talk to others who have used your services or your product. If you attempt to give them a direct experience of your service or product, or if you keep explaining your product to them you will frustrate them as well. They are being externally referenced and you are feeding them internally referenced information.
This is also be important when motivating people. If you are managing an internally referenced employee, you will frustrate them by giving them too much direction. You'll be thinking that you are helping them and they'll be thinking, "Just let me start. I'll figure it out once I get into it."
However, an externally referenced employee will want to know everything you can tell them about the task before they start. They'll take the position, "There's no use reinventing the wheel. I might as well get as much information as possible before I start."
Without understanding these two differences, you may be communicating in ways that make your desired outcome harder to achieve. Imagine giving too much guidance to an internally referenced employee or giving too little to an externally referenced employee.
You'll also find that highly externally referenced people want to have meetings with all the potentially affected departments before making a major decision. Whereas highly internally referenced people make decisions on their own, and then wonder why other departments are so upset for not being included.
Imagine putting a highly externally referenced person on a team with a highly internally referenced person and making them relatively equal in power and authority. (This is exactly what happened in one major company I was working with.) The internally referenced person will want to move forward based on their internal understanding of what they believe is right. The externally referenced person will want to talk to all potentially affected people and departments and then make the decision. The internally referenced person will think that the externally referenced person is incapable of making a decision, and the externally referenced person will think the internally referenced person "shoots from the hip" and is not a team player.
The bottom line is that if you attempt to influence in a way that is not aligned with the way a person makes decisions, you will often frustrate them and therefore, fail to influence them. This may not be because your argument is weak, or because you haven't enough information. It may be because you've packaged your message in a way that is counter to the way the listener wants to receive it.
Those of you who are more externally referenced will want to read more about this topic.
Those of you who are more internally referenced are probably wondering what your own PBSRs and strategies are.
Which approach feels better to you?
|
Case Study #1: "Sam Won't Give Up His Software because it just isn't perfect! (less than 5 minute read)
|
Sam was a young programmer with a BS in computer science. He'd been with our company for about three years. He was sharp, confident, personable, and a good programmer. He was our chief engineer in charge of the development of the user interface for a large database we were developing for a very important customer.
The contract called for rapid prototyping of the user interface, allowing us to receive customer feedback on the human-machine interaction as early in the development cycle as possible; at least that was the plan. Sam had agreed to a three-month prototype development schedule. But five weeks had passed and Sam was a week behind schedule on the delivery of the first iteration of the prototype interface. The program manager asked Sam when the prototype would be delivered to the customer for interface input and Sam said; "Just a few more days." A few more days passed and again Sam indicated that the interface was not ready. He needed "a few more days". This went on for another week until six and a half weeks had passed since the beginning of the contract. Sam was close to being three weeks behind schedule, and the customer was getting worried, as was the program manager. Tom seemed reluctant to release the prototype interface to the customer.
The program manager asked for my help, pleading that Sam must release the prototype interface immediately. Unfortunately, the program manager didn't understand the software well enough to know if Sam was being reasonable or if he was being a perfectionist. Reasonable was fine. A perfectionist we didn't need. This was after all the rapid prototyping phase to get customer feedback.
What would you have done in this situation? Would you have ordered Sam to deliver the prototype software? Would you have given him all the time he wanted? Would you have renegotiated the contract? Would you have threatened Sam? Would you have put an expert with Sam to evaluate the software status? Would you have reasoned with Sam? What would you have done?
My Actions: This is what I did. First, my basic assumption is always that people are doing what they think is right. I don't believe people are trying to be difficult. I believe people are always doing what, in their mind, is the best, most reasonable thing for them to do. That meant that Sam's hesitation in releasing the software had some reasonable rationale in Sam's mind.
So I wanted to understand why Sam was unwilling to release the software, and since I believe people will basically tell you the truth. I asked him. I said: "Sam, I understand you aren't yet willing to release the prototype software to the customer. What are you attempting to accomplish?" Then I listened and I just let him talk.
He responded that he wanted the prototype interface loaded with enough ideas so he could get all the feedback he possibly could from the customer before developing the final program. Now I knew that Sam was after the same thing we all were; good customer input.
This was the key. If I could find a way to satisfy Sam's goal and get the software in the customer's hands immediately, everybody wins. So I next said to Sam; "You know Sam, you have just about enough time, if you give the software to the customer tomorrow, to actually get one more iteration of the customers' input. Seems to me that rather than delaying delivery and getting only one iteration, you could release it tomorrow and actually get a second opportunity for the customers' input. That would make your interface much more of a match with what the customer really wants, because they'll get smarter as the project goes along, and so will you. Just think about it Sam." And I walked away. The software was in the customer's hands the next day.
What did I do in my conversation with Sam? I actually matched what Sam wanted with what our company and our customer wanted. I could have ordered Sam to deliver the software but that was only one choice. By my conversation with Sam, I refocused Sam's intention so that he was motivated to release the software as soon as possible. Why be autocratic when I could just as easily motivate Sam to deliver the software using his own internal motivation? Internal motivation can often be much more powerful than external motivation.
By understanding the motivational maps of colleagues, direct reports, and customers, you can have impact beyond that provided by positional authority.
|
Case Study #2: "The Engineering Team Takes the Financial Computers" (less than 5 minute read)
|
I was the general manager of a corporate division office. Our company developed large software systems. I had four program managers reporting to me, each with a program worth between $3 and $5 million. Bob was one of those program managers.
I arrived at work one Monday morning at 8:00 am. By 8:01am every member of the finance department was lined up outside my office complaining that someone had stolen all their PC's right off their desks.
The first question I asked was, "Had we been robbed?" By 8:15am we knew the answer. No robbery had occurred. The PCs weren't taken from the building, they had just been moved. All the PCs from the finance department had been found on the desks of Bob's engineering team. Bob's team was made up of 15 system analysts and programmers working on a 2-year program worth about $3.5 million.
I instructed the financial staff to leave the computers on the engineer's desks for now, until we could figure out exactly what happened. The financial staff was understandably ready to tar and feather Bob, while my job was to keep everybody calm. Without any real information, my goal was to make sure everybody remained calm and didn't come to their own conclusions.
By 8:30am Bob had arrived at the office, but none of his team had yet arrived. When Bob arrived I asked to see him in my office, alone. "What the heck happened, Bob?" I didn't yell it out, I just said it with emphasis on the word "What".
Bob calmly explained that his team had committed to the customer that a specific deliverable would be in the customer's hands by Monday morning. The team decided the only way to get it done was to work through the weekend. By Saturday afternoon they realized they were not going to get it done unless they had more computing power. So they took the computers off the desks of the finance department. They worked through Sunday and late into Sunday night and got the product delivered to the customer on time, Monday morning. When they left Sunday evening they were just too tired to put the PCs back on the desks of the financial staff. So Monday morning when the financial staff arrived they found no messages, no thank-you notes, no explanations, and no computers.
Bob's team had worked hard, and had delivered the product to the customer on time. The financial staff was upset but the customer was happy.
There you have the case. What would you do? Would you chastise Bob for not anticipating the problem and tell him he should have foreseen the problem? Would you praise him for getting the product to the customer on time regardless of the consequences to the staff?
Would you tell the financial staff to "just forget about it", or "get over it"? Would you stay out of it and let Bob and his team and the financial department solve their own issue to get past this? Would you get in the middle of this situation or stay out? What would you have told Bob? What would you have told the financial team?
|
|
|
| Free Stuff
|
Check out the page http://stevencerri.com/index.php/articles/index/ (also known as the "FREE STUFF" button). There you'll find several articles and other useful information, all of it FREE. Some of the Free Articles include... - 10 Pitfalls to Advancing Up the Technology Management Ladder
- Definitions
- Being Right versus Being Effective
- Motivating People by Reference
- Case Studies
- So You Want To Be A Manager
- Mechanical Engineering Magazine Feature Article: Going Soft
|
| Skype Has Been Added
|
For those of you who would rather use Skype for our coaching sessions, especially those who are international, Skype has now been added as a capability. Just download Skype to your computer and set up an appointment, and we can conduct a tele-coaching session with both voice and video!
|
| Blog
|
The blog is updated every Monday. To check out the latest ideas go to: steven's blog
|
|
"Have you ever wondered what it would be like to be as successful dealing with people as you are dealing with your technology?"
Steven trains, coaches, and facilitates engineers and technical managers to BE the answer to this question. Steven is unique because he has made this transition himself. Get Steven's latest thoughts at: http://www.stevencerri.com
I hope you find the information in this newsletter/e-zine and other products useful in your career advancement. Send questions, comments, and suggestions to: steven@stevencerri.com
Copyright©2008
STCerri International and Steven Cerri. You are free to pass this
information on to others and to reproduce it. If you reproduce
sections in whole or part please give attribution to Steven Cerri.
Thank you.
Be well,
Steven Cerri
STCerri International
|
|
|
|
 |
Most of us believe that the behaviors that made us successful at one level of our technical career will make us successful at the next. You might be surprised by the answer! (Check out the articles at the left)
|
Private Coaching
|
Take that next step into your future with private tele-coaching or in-person coaching.
Call: 925-735-9500 and set up your 30 minute free interview or Skype stevencerri
|
|
|