As functional managers, it seems, we are our people’s
Part of a manager’s job is to coach his or her direct reports to increase their capability and effectiveness within the organization. Coaching can focus on either interpersonal skills or technical work that is relevant to the job. […] You may coach someone who has decided to work on a performance issue, or you may coach to develop new skills and insights.
Behind Closed Doors: Secrets of Great Management
(Johanna Rothman, Esther Derby)
But there are other options as well...
Managing people is different from coaching people. As a functional manager you might be responsible for interviewing job candidates, controlling budgets, negotiating salaries, checking daily reports, checking weekly reports, checking monthly reports, checking yearly reports, and reminding people how important it is that they give you those reports. So you can check them.
As a functional manager you must also make sure that people who need it have a personal coach. But that doesn’t have to be you! You can delegate this responsibility and empower (senior) people to coach the (junior) colleagues, in order to develop their skills and capabilities. In earlier centuries it was common for ‘masters’ in a trade to delegate the coaching of ‘apprentices’ to ‘journeymen’. In fact, the journeymen were often better at coaching than their masters.
Every person in the organization has just one manager, but they have zero, one, or even multiple coaches, for different areas of personal development. You don’t even have to be a coach for the senior employees. You can delegate that by hiring an external consultant. While still acting as everyone’s manager, you could save yourself a lot of time, while empowering people by giving them coaching responsibilities, all in a single stroke!
Coaching responsibilities of managers are a frequently recurring theme in management literature. I believe it is a fallacy that has grown from traditional hierarchical thinking, which assumes that managers have higher competency than their subordinates (often a primary reason to be moved up in the chain of command). From a complex systems perspective this is nonsense. Top managers cannot be superheroes. A manager is just as fallible as his subordinates. (Or even more so when the stakes are higher.) The only thing you need to be good at, is figuring out which persons, inside or outside the organization, would be fine coaches to assist in the various competences your people need to develop. Mary and Tom Poppendieck call them competency leaders, responsible for setting standards, and developing people:
What do competency leaders actually do? First and foremost they are committed to developing excellent technology in their organization. They begin by framing good software development in terms of an enabling architecture, mistake-proofed processes, evolutionary development, and technical expertise. […] They set standards, insist on code clarity, and make sure code reviews are focused on enhancing learning. […] Probably the most important role of a competency leader is that of a teacher who guides the purposeful practice necessary to develop expertise. […] Competency leaders are often line managers, but line managers are not always competency leaders.
Leading Lean Software Development: Results Are Not the Point
Mary Poppendieck, Tom Poppendieck
One last word of advice is appropriate here for people seeking mentors. A mentor is not a coach, though the words are often mixed up as if they are synonyms. A mentor deals with an employee’s personal life or career, has no specific agenda, and has focus only on the individual. A coach deals with a person’s tasks and responsibilities, has a specific agenda or development approach, and has a focus on a person’s performance. As a manager you may assign the coach, but you have nothing to do with someone’s mentor. Mentors are like lovers and mistresses. Whether someone has one or not is very interesting, but nevertheless none of your business.
(photo by image42)
This article will be part of the book Management 3.0: Leading Agile Developers, Developing Agile Leaders. You can follow its progress here.