Resetting project expectations isn’t a bad thing

dream-catcherThe project I’m working on is perfect. I have the all the money, resources and time I need to be successful. The stakeholders are really engaged, the success criteria is clear and we are moving along on the project timeline exactly as we originally defined it.

Yes, that was a lovely dream. Unfortunately, we all know that most projects don’t go like this. I was working on a project that should have been a quick implementation, but immediately after the kickoff it became apparent that the scope defined in the sales process didn’t align to the requirements of business stakeholders. This made for some interesting project discussions. A couple of weeks in, just as the project was on the brink of derailing, we were able to have a very honest discussion and reset the project expectations.

This was a necessary step in making this project successful. There was definitely a miss in the early scoping process, but as a result of the communication among the business stakeholders and the project team, these issues were identified early. It also helped that this was a case where we didn’t lose any time working on unnecessary components. All the work that had been done before the project reset was still a valuable contribution to the project. Too often, project teams are hesitant to have these very honest conversations. Instead, time is wasted dancing around the problem, or implementing solutions that don’t meet customer needs.

To enable recovery from a project that is going awry, you need

  • Business stakeholders who are involved and advocate for their needs from the beginning
  • Project manager and leadership that is open & honest about the existing scope
  • An entire project team who (project implementation team, decision makers, business stakeholders) want the project to be successful and are willing to re-evaluate and reset the project scope and timelines accordingly.

 

Do you want to be Joan of Arc or Martin Luther?

I participated in a panel discussion on Wed. March 8th for International Women’s Day. The panelist were challenged to talk about their bold moments in our careers and life. As I was thinking about this and deciding what I was going to say, I talked to my husband and dad. I’ve had quite a few moments where I made a decision and took action on something others might consider bold, where I saw them as a necessity to stay true to myself. Was I going to talk about leaving St. Croix at 17 to pursue college and my life in Washington, DC away from family and friends? Or the time I quit my “good” job working for a big, public company in 2011 without another job lined up? Or do I talk about the next time I quit my job to run a consulting company with my husband? I determined leaving St. Croix wasn’t bold, it was necessary. While I see the other two events as necessary as well, I also didn’t think it was too appropriate to talk about as the only person on the panel who didn’t work at the company hosting the event.joan-of-arc

In talking to my husband, he reminded me of some advice my father gave me when I was struggling to find my place years earlier. My dad told me “you can be Joan of Arc or you can be Martin Luther. Are you going to very publicly and loudly air your grievances, potentially going down in flames; or are you going to quietly nail your list of grievances to the door and live to see another day.”

martin-luther As we identify challenges in our work places or in society, we need to determine how we pursue “justice.” Each situation is different and you’ll need to make that decision each time. You need to weigh the risks and the rewards. For me, personally and professionally, the risks were always minimized by what I knew about myself. I will land on my two feet.

When I left St. Croix for college to a city relatively unseen with no family, I was encouraged by the fact that I had family in Philly, NJ, NY, all just a few hours away. I opted for a small, Catholic college in a city I loved minimizing the importance of the diversity of island life and the small thing that I wasn’t Catholic. I figured if I didn’t like it, I could transfer somewhere else. And that’s just what I did.

When I was struggling to find my place in that job in 2011, I took a hybrid approach to lay out the list of issues, and bring solutions to the table. Ultimately, I ended up quitting anyway as my sense of urgency didn’t align to the organization. As my husband says, I was the worst quitter ever, delivering volumes of documentation and hiring my replacement. The organization ended up delivering on their word, heavily investing in resolving the issues. I was told at the time that I needed to stay and work it out, learning to navigate corporate america if I was ever going to be successful. They brought me back as a consultant a couple years later.

And that time I quit my job again, to run a business with my husband? Three years later, business is good and no bridges were burnt. We’ve managed to grow and thrive, and still do work for our previous employers.

Life is made up of choices. As we are reminded to #BeBoldforChange, make sure to figure out who you are and what choices you plan to make.

Not at the top of my game this week

I was not at the top of my game this week. I don’t really know why. Yes, it was has been a busy week, but that’s usually not an issue. I’m working on a few different projects, all in different phases, and different level of engagement. That made for some comedic moments, but again, I don’t think that was the reason for overwhelming sense of chaos.
chaos And unfortunately, I did demonstrate my sense of chaos very publicly amongst my peers. Thankfully, it wasn’t so much evident to the customer teams I worked with, but it was clear to the internal teams I engage with.

On Wednesday, I expressed an extreme sense of frustration being adamant and forceful about pursuing an open issue that I felt was being brushed under the rug and told “that’s not an issue.” I was sure I was right. I compiled the “facts” and sent an email trying to communicate the necessary details so we could get it resolved. I coordinated a meeting about the issue on Friday, the earliest time I could get the right people on the call.

In the meantime, I did other work. On Friday, i get online and start checking different things. And on 3 different issues, I was told it was resolved but when I checked it I wasn’t seeing the resolution. The call comes around and we get on it and it was clear that I was a bit crazy. One of the attendees was able to explain what I was seeing, and clearly demonstrate that it wasn’t an issue for the customer. Not just on the issue from Wednesday, but also my other issues. At that point, I said was done and clearly needed to take the rest of the day off. I did go ahead and send an email to some of the team members thanking them for their patience and apologizing for wasting their time.

Ultimately, I probably wasn’t wrong for pursuing a customer issue that wasn’t getting the proper attention. But I wasn’t as respectful as I should have been in my behavior towards my fellow team members. I can say tomorrow starts another week, and it will be better. I can’t dwell on the mistake I made yesterday.