(kindly ignore punctuation errors... this is a long post typed into a little window with less time)
There ARE people who need coaching... both managers and lower-level employees. And one of the things that managers need to know is that coaching their employees (i.e. providing direction) is part of their job. However, that's only true to an extent (within reason and constraints), and it's beyond that limit that your services as a coach are valuable. Here's an example:
A project manager such as myself simply cannot (and should not) know every detail of every job under his control. A certain amount of trust has to be vested in the employees that will have to do the actual work. The project manager has to provide the direction and communicate the goals of the project. Specifically, he must clearly communicate specific goals to each employee. He has to elicit feedback to determine whether those goals are realistic, and then evaluate and act on the feedback if necessary.
One of my early projects involved some rather complex changes to a system. It doesn't matter what the changes were, except that they were specific, inflexible mathematical algorithms that were worked out by external subject matter experts. 'Bob' was a senior programmer/analyst assigned to the the team. Once he saw the math involved, 'Bob' had a very difficult time getting motivated to do the work. I worked out the overall structure I had in mind for the system asked him for his estimate on his portion of the work. I always include the team early in the design process if possible, especially if I have to make assumptions for areas with which I'm not familiar (which happens A LOT in this industry).
"Gee, I dunno, this is hard," he'd respond. Now, of course, I didn't know the programming language required for those particular components, but I am an accomplished programmer in other languages. So I described a possible approach made a quick estimate and asked, "Is this approach feasible? Can you do this part in 3 weeks?" 'Bob' replied again with, "Gee, I dunno, this is pretty hard." Several times, to the point where we had to table that part of the discussion and move on with the rest of the team's input.
Now, we have a finite amount of time for estimation and design, and the customer requires some fairly firm numbers for budgeting and SLAs. I'm one who likes to come in under budget, so I'm fairly conservative with estimates, so I'm pretty easy so long as I can still 'sell' the schedule to the client. It's another reason I include the team early if possible... I want THEM to be comfortable with the schedule, too. But repeatedly responding "this is hard" is no way to further the process, especially since everyone else in the team caught on pretty quickly. So my response was to say, "Bob, I know it's hard. You've told me it's hard, and I'm going to take your word for it. Now get past that. HOW hard is it? Is it three weeks worth of hard, or do you think you need more time?"
Now I'd asked for a senior P/A precisely because I needed a team that could work independently. It was pretty clear to me that if we ran into any roadblocks 'Bob' wouldn't even begin to solve them, and I as a manager unfamiliar with that system wouldn't be able to help him. I replaced him with an eager junior programmer from the pool who not only 'got' the design but who saw the task as a challenge rather than an boatload of work he'd rather not do. 'Bob' went on to another project and left the company not long after.
I suppose you could look at this as a 'pointy-haired boss' episode with me in the starring role, but the fact of the matter is that NO IT manager on a cross-platform project is going to know every aspect of every system. That's why we carefully select team members. That's why we hire programmer/analysts and not typists. And that's why we ask for input from the team early, to check assumptions, refine the estimates and the design, and make changes before we're locked into a budget. I absolutely HAVE to trust the team, and I don't have the luxury of blaming any one of them if they can't pull their weight. It's my job to recognize and fix those sorts of problems. But as a manager I'm in charge of delivering results... I have the time to provide direction, but I can't hold the hand of a team member who's job description clearly indicates he should be able to deliver to a certain standard. I have to direct and assess his performance in accordance with that standard.
IF the corporation had a coaching program, I'd have recommended 'Bob' for inclusion. Frankly, I don't think he should have been promoted to Sr.P/A without the ability to analyze the requirements he's given and to estimate his own ability to deliver. It's possible that he needed assertiveness training. It's possible he needed some exercise in focus or prioritization. Maybe he felt better suited to another career, or perhaps he had a bloody medical condition. I don't know. The fact is he didn't indicate anything of the sort even when asked, and once I get to the "throw me a bone" stage, I've got to move on with my own priorities and not feel guilty about his.
If you're a 'Bob' or you know a 'Bob' then it's possible that Plan B or something like it is just the ticket. Also, I might recommend seminars for people on a promotional track to help ensure that 'Bobs' don't get promoted above their abilities... or better yet, that they have gained the necessary abilities before they're promoted.
But consider this. If 'Bob' does lack assertiveness then he might just be too timid to do that on his own. If 'Bob' is a manager promoted through the Peter Principle, then he might be afraid to go to a 'coach' because his own manager might find out and wonder why a decision-maker has to go somewhere else to help him make decisions. That's where selling it to HR and trickling the idea down through upper management is a good idea. It may be that for some organizations a coaching 'leg up' is a more cost-effective investment than firing somebody and training a new employee from scratch.