I have a lot of respect for Matt, he and I went thru a lot of "stuff" together over a very short+intense period (more on that in a moment) and managed to come through it while spreading a little bit of light. During that time I also pointed Matt in the direction of Agile development as a possible "way out of the madness", and he did his part to help make that a reality.Here's the story on that ... I worked with Matt back in 1999-2002 on what was then a hideously dysfunctional "death march" project that we were trying to pull out of it's own self-created and self-perpetuated hole. The product was an internal one, and Matt, a former testing Guru, was one of my key customer reps. The project suffered from just about everything under the sun:
- Bad management (failure to set+manage expectations & appropriate interfaces)
- Dysfunctional customer & internal organization (warring tribes, turf wars, political silos, and a severe lack of trusting/trustworthy mgmt leadership),
- Management that felt senior architects/designers aren't supposed to get their hands dirty in "coding"
- A tech-lead with great technical & project knowledge/skill/experience and strong passion for quality design but with an equally great reluctance to lead, overly trusting and possessing piss-poor leadership & communication skills at that time (me)
- Managers that had great communication skills, but no clue about successful software development, and no interest in learning it
- A highly talented team of young, promising developers, but with a total lack of software development experience/maturity (which wouldnt necessarily be a bad thing if not combined with all of the above)
The Mythical Manager Month -- adding more managament to a late & failing project just makes everything thing worse and everyone more miserable.I have to say, that project really taught me a lot about leadership and communication, particularly ...
- how leadership differs from management, and from cheerleading
- the importance of planning your communication and having a communication plan
- the huge impact of really good managers versus really bad ones,
- the difference between credibility and trust
- the difference between power/influence and authority
- how incredibly selfish, two-faced, and despicably unethical some folks can be
- how to recognize malevolent manipulators who appear to "befriend" you to gain your trust, but will betray and backstab to get what they want
- and how to recognize (and handle) a demagogue masquerading as a "heroic manager."
The books by Patrick Lencioni on team dysfunctions and how to overcome them, as well as organizational silos, politics & turf-wars would have done me a world of good back then if they'd been available (and if I'd had enough previous appreciation of those problems to have read-up on them and other works related discovering and raising my Emotional Intelligence).
That project marked my transition from "unconscious incompetence" about leadership & communication to "conscious incompetence" and really motivated me to navigate the path to "conscious competence." I yearn for the day when it becomes unconscious competence.
I'm not quite there yet. It's been a long leadership journey (much longer in experience and learning than in actual years) since that project, and I still have a long ways to go. But these days my bookshelf at home is replete with just as many books about leadership, EQ, influence, and communication as my technical bookshelf at work is with books on software development, and I think about a lot more than just the technical strategies/techniques/practices and lessons learned in my day-to-day work.