Customer Reviews

Behind Closed Doors: Secrets of Great Management (Pragmatic Programmers)

5 star:		(22)
4 star:		(6)
3 star:		(0)
2 star:		(3)
1 star:		(1)

 

 

This is a book about line management of knowledge work - Programmers, Graphic Artists, CAD Drafters, Chemists, Engineers, Physicists, etc. This kind of management is a relatively new invention, and stands in stark contrast to manufacturing management. Previously, you had to read a host of authors like Drucker, DeMarco, Deming, and Jim Collins and read between the lines. Now you have this short, practical guide by Rothman and Derby. "Behind Closed Doors" is a practical book - Do this, then do that. The writing is clear and tells the story of a newly hired director of software engineering who brings focus and direction to a floundering team.

The writing is not novel-quality, but it does provide real actionable guidance in a way that keeps you awake and thinking. That alone puts it above the typical management text, at least in my book. Plus, the book is small: You will actually remember the points it makes and know how to do them.

Because it is small, the authors focused on that one aspect of management. "Behind closed doors" does not contain a great deal of philosophy. Also, while Project Managers may find it helpful, they will want to use this book to round out a library, not start one.

I give "Behind Closed Doors" five stars, because it does what it says and does it well. All of the other books I know in this space have some painful weakness: They are vague, theoretical, boring, try to cover too wide a subject, etc.

Bottom Line: If you are a direct manager of technical people, you can't go wrong. If you -are- a knowledge worker, buy it for your boss!

Overview

This is another Pragmatic Programmers book. As such, it is short (162 pages), and available in electronic form as well as in paper.

The text is a bit of a departure for the Pragmatic Programmers. Typically, this series has discussed techniques for software development, rather than techniques for managing software projects. Still, this kind of books is a must-read even for a neophyte developer, as it discusses techniques that your manager is likely using. Perhaps more importantly, it discusses the kinds of constraints that your manager is laboring under. From either side of the desk, knowing what options are available can make the difference between success and failure in negotiations.

The authors refer to several of Tom DeMarco's classic works, such as Slack and Peopleware, and the format of much of the book is reminiscent of Deadline. In Deadline, we followed Mr. Tompkins through the process of setting up a new software concern in accordance with every then-current software development theory. Rothman and Derby follow Sam, a new and eager senior manager, through taking over an existing development project, using agile techniques, and a variety of management techniques.

Structure

The book is structured into an introduction, seven one-week 'to-do' chapters with an illustrative parable about Sam, and a final 'techniques' chapter.

The introduction sets the hook well - in just a few pages, you learn that the authors view management as a people task, though supported by technology, and with technological deliverables. This focus stays through the book - solutions tend to be low tech, such as flip charts, stickies, and index cards, and tasks are resolved through meetings with subordinates, peers, and superiors. We do not see Sam interact with technology all that often.

My own experience shows that low tech techniques work well, as long as key information does migrate into electronic form eventually. Once the flip chart is filled out, someone ought to take a photo for the wiki, and I rather wish the point had been made more strongly by Rothman/Derby.

Each of the 'story' chapters covers a single week. In the early weeks, Sam is figuring out what his four subordinate managers are up to, and eventually teaching them the art of delegation. In later weeks, Sam is working on long term solutions, like training, hiring, and handling high priority changes from above in the organization.

Positive Points

One of the better sections in the books was on self control. Managers are in an authority position, and many of them do not realize how their underlings will take a casual comment, or even a facial expression. Further, many managers do not realize that their employees will occasionally burn out rather than face criticism. This is rather sad, as burnout cases usually produce work worthy of criticism.

I also applaud them for bringing up both old and new studies regarding ideal working hours. Overwork burns people out, and thus if you are running more than the efficient 40-45 hours a week, you really do need to cut back. Every job involves sprints, and everyone can do a sprint, but not if they are already worn down by needless extra hours.

For the authors of a management text to take this stance requires some courage, and they make it clear that the manager will need courage as well. There is always pressure to do more, and when the business depends on it, you must find a way. That said, every week should not be a crisis week, and they give a manager some of the needed facts to back that position up.

They also covered coaching in some detail. This was also a 'ring of truth' section, in that the authors were clearly describing situations they had seen, and had worked through in a number of ways.

Techniques

The final techniques section was the least engaging, but perhaps the most useful. It listed specific techniques for areas that many managers are weak on. I know of several managers in my own past that might have gotten use from the meeting organization and facilitation techniques. Merely knowing that you either facilitate or contribute would have helped me on more than one occasion, as tempting though it is to dip the oar in, you lose the ability to move a meeting along. The authors also reiterate how important it is to facilitate _only_ if you are interested in alternatives.

Odds and Ends

The chapter references were particularly fine; the footnotes for key points led to the source material. Thus, a technique, an idea, or a point of view of interest can be hunted down in more detail. The bibliography was extensive, and while I have read many of the books on that list, it added a number of new titles for me to look up.

Downsides

So what didn't work? I found that the story felt a bit too pat in spots. Sam never showed any particular flaws, so we did not really see how a manager should recognize a flaw, and how he should address it. DeMarco's Deadline did a bit better in this regard, as his hero did get angry and stubborn, and had to take both earned and unearned criticism.

I would have liked more focus on areas where managers and their reports have dissimilar goals, and how to get people to support goals only indirectly in their interest. Luke Hohmans's Journey of the Software Professional accomplished this with an unusual technique - each topic discussion was followed by different takeaway points for managers and employees. Without making a fuss, it made the point that managers and their reports have different priorities.

Final Thoughts

This book is not trying to replace solid management texts, and detailed books on estimation. It gives a stable of techniques that managers and their reports will find generally useful for the day-to-day work of getting the job done. It does so using a parable/story format that worked well enough at getting the context of management across.

The virtues generally outweighed the flaws. I rate this a four out of five, and recommend it highly to managers. Even old hands will find good things lurking in it and in the books it references. It is joining my bookshelf in the management section.

Behind Closed Doors confronts the unspoken myth that star individual, technical performers will naturally want to be and, conversely, know how to be star managers. Technically-skilled folks don't transform into gifted managers on their own. They need help. This is an excellent book full of specific tips and pragmatic advice on the most fundamental and key aspects of management. I'd recommend this book to any first-time managers, managers new to a department, anyone managing by the seat of their pants, or anyone thinking of making the leap from technical to management.

I found the narrative style helpful in that it shows managers just how to hold a meeting or discussion with their direct reports. There is plenty of specific advice that can be implemented today, without delay. And should you want to dig deeper into a topic, the bibliographies at the end of each chapter make it easy to find additional resources.

I have 25 years of IS experience - some as a developer or analyst and some as an IS manager and certainly when I started out as a manager, this book would have been invaluable!!

Perhaps my only issue is glossing over some of the gnarlier situations I believe most IS managers have to confront eventually - for instance what happens when you give negative feedback and the person doesn't relate in any way what you're telling them or perhaps agrees but thinks the issue is unimportant? To me the easy case is when you give feedback and the person agrees or at least comes up with some cogent reasons why they think I'm wrong. At this point I know the person thinks I'm the pointy haired manager and I'm totally certain I'm not the only manager that experienced this. The book says such a person will "not change" - no kidding but where do you go from here?


I actually have a longer list than this - but the point is I think there are a lot of real and challenging situations especially for IT and technical management not covered. OTOH, the suggestions the book does comes up with are mostly excellent well explained and easy to implement and I think anyone with any level of management experience will pick up priceless suggestions from this book - and I'm usually extremely cynical about new management methodologies!!

Maybe a later more intermediate/advanced book will cover some of the more difficult situations? If there's a website, blog, set of seminars etc available I'd be interested in hearing about it!!

have just finished (as in read the last page) of Esther Derby's and Johanna Rothman's book "Behind Closed Doors". Your gut reaction is wrong on this one. It is not another how to be a manager in 30 days or less book,



You might ask, why would this old bald guy buy a book like this? My reason is very sensible for someone with 30+ years of exhilarating frustration in this business - I usually have a fresh prescription of Paxil - or a new Bourbon so that I have a quick fix to the depression these kind of books bring on.



NOT THIS ONE.



Those of you making the transition from doing the work to managing to get the work done through others need to read this so you can understand how not to devolve into a `PHB' (pointy haired boss).


And yes they made me buy my own copy and then beg for an autograph.

This book is for true managers who are inspired to become leaders; it is not for supervisors who care only about their own well-being and don't think much about people working for them. (Did I just cut the audience by 95%?) I also recommend it for anyone who has a manager -- to learn what are the basics of effective management.

At first I felt that the material covered in the book is basic, and it may be useful mostly to an ***AMATEUR*** manager. Later I changed my mind. In my long professional life I worked for a few companies, large and small, where I met many career managers. Well, only occasional few practiced most of the obvious and basic winning management techniques. Thus, I think that any professional and CARING manager may benefit from the book.

The authors tried to make this book entertaining and helpful at the same time, and they achieved their goals. The book tells a fictional story of one software development manager that just started working for a software development shop. Step by step, he manages to get things done by enabling, delegating, communicating, explaining, thinking in a way that makes professionals around him happier and more productive. Isn't this what a manager is supposed to do? It does sound a bit utopistic, especially in the today's real world. But the situations in the book are real, and the lessons drawn from it do help in the real world.

The book does not discuss enough team management in the complex and dense atmosphere of corporate politics in the software development industry, where most of the managers do not understand technical side of the business and often make decisions for the benefit of someone's personal agendas rather than the needs of the business. This is why I give the book 4 stars.

This is an excellent work that guided me though my first formal management experience. The book weaves its lessons into a story which helped you to understand how to apply what you learned. Like many important books, it explains some simple rules that can be difficult to execute in practice. The downside of reading this book is that you may realized that you're not being managed well (or have not been in the past) and you can no longer live in blissful ignorance. All technical managers at all levels should have read a copy of this book. The section on having one on ones by itself is worth the price.

Too many management tomes offer large philosophical discussions or get too far into the weeds of addressing complex situations. Few really give solid, implementable advice about what effective managers do on a daily basis. Behind Close Doors offers a practical viewpoint of management that's relatively simple (though not necessarily easy) to implement, step by step. Rothman and Derby have described the whole enchilada of effective management practices for beginning managers, and provided a great refresher for experienced ones. I'll definitely make it a part of my recommended toolkit for new managers. I'll also recommend it to people who want help their own managers improve. It's a book for project managers and functional managers at all levels.

Practical approach to management. This book shows the application of good management practices using real-world scenarios. It is easy to read and written in such a way that you can instantly start applying its concepts in your environment.

I am very skeptical of most business improvement books and one size fits all methodologies, but I can tell you that this book absolutely shines as a glint of hope in the sea of business improvement noise. As opposed to trying to force a given technique that will apply to everyone in every business, this book provides some very "real" examples that exist in the software development world and some very simple concepts and techniques that can be used. This book is not written like an academic book of problems and solutions, but more of a story based book on a "real world" scenario, which truly solidifies the pragmatic name of the publisher. This pragmatic approach makes the book very easy to read, understand, and ultimately use. I think if you use at least one or two of the techniques presented in this book such as One-on-Ones and Big Visual Charts (BVCs) that the book will have more than paid for itself in terms of the time you will have spent reading it and of course the money!