Planning is important. That's (fairly) self-evident. Planning implies that there is some logical structure and movement towards an outcome, that thought has been put into both the outcome and the process. This all makes sense. But what I have been wondering about is where documenting the plan fits.
I was talking about this to a friend who runs a web design company and he mentioned Agile Management, which got me thinking about a concept called 'Agile Coaching'.
The first thing to mention here is my belief that just because you invent a name for something doesn't mean you were the first person to do it, nor that you are an expert at it. The second thing to mention is that there are many times where I have 'invented' something only to find out that 100s (1000s?) of people had 'invented' it before.
Now for a story: I was talking to a multiple World Championship winning coach about training plans. He said that, yes, people were always asking for his training plans, athlete management plans, strength and conditioning plans and dept charts, but he found that they stopped asking at the end of the season if you won. In the end it took a lot less time not to write up and submit these plans.
The question, as always in coaching, is not whether something is of benefit, but what the time/cost analysis is. With unlimited time, there are many things a coach might do that, with finite time to achieve almost impossible things, he/she may not. So, to put the question more simply:
Are you better off implementing a badly documented plan well, or better off well documenting a badly implemented plan?
The answer, I think, is that it depends on what your priority is. If your fundamental priority is to win (or, achieve the goals of your team/program), then it is clear that implementing your plan is key. If your fundamental priority is to keep your job, then at times you are better off well documenting what you can do in order to demonstrate that even though you didn't succeed, you are on the right track.
Getting back to Agile Coaching, the critical point isn't that it justifies not writing things down, the critical point is that it focusses on what a coach is employed to do, which is coach. As a coach you must have a plan, which needs to clearly lead towards the desired outcome within the scheduled timeframe. Agile coaching urges you to work out your plan, then get started at a sprint. At the end of the sprint assess what has been done and plan for the next sprint, which may be refining what has already been done, or adding some new aspects. The key tenant is that you know more about the problem and the solution set after you have started than before you start. The chances of writing a perfect plan and implementing it are zero, and after you have started implementing it, you will always want to tweak it or possibly even scrap it if you find it is wrong.
Now, does this sound like what a coach already does? Particularly if you are coaching in season. You have a series of sprints, and between each sprint you evaluate what has happened, tweak what you are doing, and get started on the next sprint.
As I said earlier, I lay no claim to inventing Agile Coaching, it is what coaches have always done. But what they are being asked to do, more and more, is to document what they are doing. I'm not saying planning and documentation are not important, I'm asking, what sort of documentation is most appropriate for coaching.