It’s only day two back and it’s already apparent that several things fell apart while I was gone. This is not to say I’m such a superstar that my absence is the direct cause of the chaos (although it has been made abundantly clear to me that I was sorely missed). It’s more the nature of project work and IT project work specifically: crap happens, things go wrong, and perverse incentives exist that cause people to hide bad news until it’s too late. Yeah, OK and some of it is because I was gone.
The task before me is to quickly get back up to speed at a deep level of detail so I can get back to working my mojo and getting things moving forward again. I need to diagnose just what the heck is going on and then I need to ensure we are moving, moving MOVING FORWARD people!
Here are my favorite techniques:
1. Play dumb. I’ve been away for four months so I’ve missed a lot of the history, nuance and back story. I get to ask all the dumb, naive questions I can think of, and play that magical role called “new person” even though I’m technically not new. Having to answer the dumb, obvious questions can help people cut through the spin, justifications and finger-pointing. Plus, I really need all those dumb details! Did I mention it is such a relief to let my inner dumb come out of the closet?
2. Ask for post-mortems. What happened? Why did it happen? What specific cascade of events occurred? Tell me about it in plain English. Where are the exact points where things broke down? Are we likely to repeat these mistakes? How can we ensure this doesn’t happen again?
3. Set the standard for no finger-pointing. Goodness knows, the team has done enough of that already. Business blames IT, IT blames the business, project managers blame the clients, fingers pointed all around. Say aloud, to everyone, over and over again: “I’m not interested in pointing fingers. I just want to understand what happened. What’s important is what we do now on our way forward.”
4. Bias for action. Corollary to #3. Once I understand exactly what happened and what the current state is, I want to know what we will do about the current state. I do not want the team, partners or clients moaning and bemoaning. I want some specific next actions. I do not want an overblown, over-engineered, re-engineered gantt chart. I do not want a month of planning or a 60 day rebaseline. I want some specific, concrete, do-able next actions. I want some small, achievable wins (to help morale and momentum). I want them time-bound and deadlined, and I want them executed.
5. Open the communication floodgates. When *@#%ing messes are developing, communication clamps down. People don’t want to share bad news so they keep it to themselves. People are pointing fingers, so they talk behind each other’s backs to sympathetic ears. Decisions aren’t being made and time pressure is mounting, so communication stops. Time to open back up the communication floodgates and send clear, simple messages to all the stakeholders. No overwrought, convoluted status reporting, just simple clear current state and way forward statements, and consistent messages. Use multiple communication channels — one-on-one statuses with leaders, broadcast emails to the virtual team, broadcast emails to the stakeholders, in-person steering committee meetings, etc. Give consistent statements and clear facts, avoid finger pointing, clearly outline accountability (who will do what now, and by when). But tailor the style of message to the audience.
6. Re-introduce discipline. Once the way forward, and specific time-bound next actions are identified and publically announced, ensure that the plan is being worked. Pull the core group together for regular status updates. Communicate those updates. Work the plan, mitigate the risks. If the facilitator or manager of the project execution is largely to blame (no public finger pointing!) for things falling apart, replace them. (But no public finger-pointing! This step is for leaders to handle behind the scene). Do a deeper dive into timing/action; set milestones. But don’t plan to plan. Motivate the team. Light a good fire. Get them moving forward again.
7. Re-introduce feedback. Keep a pulse on client happiness. Schedule regular in-person or email check-ins. How are things going? How do they feel about the way forward? Keep a pulse on the project team. Are they executing? Are they burnt out? Do they buy into to the end goal? Answer concerns as promptly as possible. Insist on people talking directly to each other (not complaining to third parties), but if they have bad blood or poor communication styles, help them out. Use every interaction to ask, “What can I start, stop or continue doing to help you? Do you have feedback for me or my team?” Hold the partners and virtual team members accountable — provide specific, actionable, behavior/consequence based feedback as soon as possible, but not in public.
8. Celebrate wins. Bomb the team and clients with positive feedback when warranted. Publically celebrate (announce, aknowledge, point out, you know what I mean) small wins, big wins and interim milestones achieved. Catch people doing things right. Catch them some more. Catch them some more. Reward what you want more of.