Have you ever been driven up the wall by a mainliner? "What's a mainliner?" you ask. Read on. You likely are already familiar with the type and how they can cause havoc in your company.
Mainliners cannot be bothered with elementary groundwork.
These players will plunge into any project without so much as a pretense of preparation or planning. They rely on their instincts and agility. They are usually from the group who never bothered to do their homework in high school. Later, they wrote their college papers the night before they were due, without inhibiting themselves with trivia such as a trip to the library. In a pinch, they used someone else's notes. The solution is always at hand if the player is observant enough and clever enough to recognize it.
Mainliners assume that actually knowing how to do a job is irrelevant.
The essence of this technique is seeing that "knowing how" only limits and inhibits the range and flexibility of expert players.
The blind spot here for non-Players is in understanding what "knowing how" refers to. The uninitiated think that "knowing how" means you have specific knowledge and skills related to the task or problem. They also think that related experience is useful.
Dyed-in-the-wool mainliners understand that, for them, these kinds of things are not important. The only skill they need is an ability and willingness to dive in and to keep poking. Usually, things have a way of working out. If not, truly creative mainliners either abandon the task or call in a specialist, taking full credit for saving the day. -- Read and learn.
Liz is an engineer assigned to troubleshoot a lockup problem with a computer installation at a small retail business. For some reason, the main application and the operating system are not interfacing correctly. The result is that the system is lockingup and the business is having trouble staying open.
Liz's first approach is to say that the people operating the system are causing the problem. When this does not hold up, she next attributes the difficulties to a hardware problem or bug in the operating system. Again, the explanation does not stick. Finally, she reverts to type as an experienced mainliner.
There are a few minor deviations from specifications in the way the business uses the system. One part of the application is one no other customers use.
"You are the only user who has tried to use this function. It's only an add-on to the main application. We did not expect it to be used on a daily basis. That is what your problem is."
"Well, it's important for us to use this function. How soon are you going to fix it so it doesn't keep locking up?"
Sure, Liz knows just what to say. "This problem is unique to your system. You will need to exercise your support agreements with the hardware and operating system vendors. They will need to straighten out your problems with their installations before we can help."
"We bought the system from your company. Aren't you going to stand behind your sales?"
Liz is again ready. "We will support you 100 percent. Just as soon as you get the other problems worked out, I will see you have a specialist assigned to the problem." A specialist? Yes indeed. That is someone, anyone other than Liz. That's the way to pass the old buck!
Mainliners start before understanding what you expect.
This technique is axiomatic for mainliners. To find out what you expect is a waste of their time. Adroit players have no intention of doing anything other ...