I made a promise to myself what feels like a long time ago to not only blog about the successful things in my life, but to also mention the un-successful moments.
“If you only reflect on your successes, then you aren’t learning as much as you could be… You can’t just completely let go of un-successes because then you can’t use them to fuel better actions next time, but you also can’t dwell on them to the point of madness; it’s when you find the balance that you can learn.” – My Un-Success Reflection (The Life of Pinya)
I wish to honor my previous promise to myself, so here is a story of an un-success of the past few weeks.
For the past few weeks I’ve been working with a team of Innovation Diploma members as consultants for the City of Sandy Springs to decreases traffic at MVPS by 10% (#reMoVe10). The hypothesis is that if we can develop a plan to decrease traffic at our school, then we could create a plan that could be replicated at other schools too. If enough schools decreased their own traffic, then the traffic in Sandy Springs during rush hour times would decrease as well. It’s a lofty goal, but I think we’re on a good path right now.
Our first client meeting went very well two weeks ago; however, the days leading up to that meeting were not so great. Our team has had some major communication problems lately. We’ve done a good job of dividing up responsibilities, but apparently we didn’t do a good job of checking in to make sure everyone was on the same page about why we were doing certain things.
One day I was meeting with a faculty member that has been acting as an external mentor to our team, and when I got back half of our team of 4 was missing. No one knew where they went. We were searching around the school and texting them and then finally we learned that they were out counting cars in the parking lot. We had discussed the value of taking observational data multiple times, so the idea was valid, but not at 10:15 when there isn’t any traffic in and out of the school… Somehow this idea wasn’t communicated well. Moreover, the reason they said they were out there is because they discovered they wouldn’t be able to get a piece of technology working in time for our meeting, so they didn’t know what to do and thought counting cars would be productive.
On the one hand I’m grateful to have a team where members are trying to take initiative and go out and do and observe things rather than always working on a computer; however, this was a major fail-up moment because the data they got from counting cars was information we could have concluded by just sending a quick email to find out how many teachers and students have on campus parking spots, so an entire day was just wasted by half of the team. Furthermore, when one member was asked questions by the facilitators, the member was not able to answer questions about why we were even having a client meeting later that week let alone answer questions about what we were going to talk to them about.
Overhearing this conversation was when it hit me that we really had a problem and part of this is on me.
The team has established that I’m project manager, so this un-success day made me realize that if that’s going to be my role, then I need to do a better job of helping to make sure that everyone understands not only what needs to be done and who needs to do it, but also understand why we are doing it.
I also felt bad because when I later talked to these members about why they thought it would be a good idea to wonder off to count cars without telling anyone, they said they were scared to tell me that they wouldn’t be able to have the tech devise working in time. They had underestimated how difficult the task would be, but they knew the importance of that task, so they were trying to at least get some number so they went out to manually count cars.
I don’t want people to be scared to tell me things, and I’m glad at least that they told me that they were. I tried explaining that I’d never be mad about them not being able to do something based on their skills as long as they were honest about their capabilities upfront so we can plan accordingly as a team. The issue was that they were the only ones with knowledge about the technology since they were working with it, so when they said they could have their experiment up and running by that day, we assumed it would be done. It was frustrating then when the task wasn’t done because for the past few weeks we had been reassured that the timeline was an accurate assessment of when we thought we could have things accomplished by. How do I make it so that people aren’t afraid to tell me when things are not going as planned? I’ve noticed this problem outside of ID too and don’t know what to do about it, because I don’t mean to come off as intimidating but know that I can sometimes according to others.
I’m not really sure if I’m explaining this situation very clearly which is kind of ironic since the whole problem had to do with poor communication between our team. However, at least I can say that we’ve grown some from these hiccups since we’ve learned and improved in some ways.
Our team was able to turn things around before our client meeting, and that went really well! The meeting helped our team we focus and gain clarity in our group understanding of our mission and next steps which was very helpful, plus we impressed our clients which is nice. I hope that my teammates are no longer or at least getting to be less scared to tell me when things aren’t going as planned because I know a team needs to have lots of trust in one another; I don’t know how to help with this yet though. I also think entire team now sees the real importance of being honest and upfront about each of our capabilities that way we don’t have another situation where we essentially waste an entire days worth of work…
At the same time though, we’ve still had a couple instances where teammates will wonder off without telling anyone and not come back for a while, so I know we still have a ways to grow as a team in our communication. This whole post has actually made me realize more-so that our team probably needs a good heart-to-heart conversation, but I’ve never been good about making that happen even when noticing that it needs to; it’s probably the area I most need to grow in terms of responsibilities of a project manager. In school typically the job of bringing a team together to acknowledge dis-connects is done by a teacher or some other adult, and it’s not something you ever get taught despite it being a crucial part of team work. Guess it’s time to learn.