Just about every project has a gnarly part, a time when making it through to the end successfully seems like a distant dream. It’s important to be aware that you are in the gnarly part of the project, trust that this happens to everyone, and explore multiple paths forward.
The “gnarly part” might seem an odd term, but there’s a meaningful story behind it. A couple years ago, I tried to climb Snowmass Mountain with some friends. The hike itself is another story, but on the trail, a guy mentioned to our driver that the road down from the trail head (it was a one-way loop, so we hadn’t passed through this part yet) was a little challenging, but once you got past the “gnarly part” you were good to go. Well, the drive down to the main road took us the better part of 3 hours. And here’s why. The road down had switchbacks (thankfully) but in most cases there was barely room for the SUV we were in to get around a sharp rock jutting out into the road and often the driver had the car in first gear, pointed in a direction off the road, only to turn back in to get “around” the switch back. Other times there were rocks jutting up right in the middle of the road. In the beginning one person would get out to direct him how to drive over the rock and not bottom out. But in many cases all 5 of us had to get out of the car to help preventing it from bottoming out. A couple times there was a loud “BANG” as part of the car hit something. Us girls were told “it’s OK, it’s just the frame.” There were times I could have been in the car, but got out just because I was so afraid of falling of the cliff. So, yes, we found the “gnarly part”. And two hours and about a half mile later, after most of us walking through it and one person driving through it we made it to the main road which eventually took us to a nice hotel room with some pizza and beer, where we celebrated our little adventure.
So what does this have to say about information technology projects? In my experience, every project has a “gnarly part”. Some have many. Different people can experience them at different times. As a BA, this tends to happen at a point of time when your committed to a high-level strategy and solution. You’ve done a lot of research, you think you are prepared, and you start diving into the detail. Ack. There’s something you didn’t think of…what are you going to do with that? There’s a rock jutting into your pathway and you have to back up and find a new path or figure a way around it. It seems that around every corner your faced with some new unanticipated challenge that threatens to turn your project upside down. This is the gnarly part of the project. It’s also sometimes referred to as the state of “analysis paralysis.”
There are two paths through:
- Keep driving and modify your plan along the way to incorporate these new details. This requires an open mind, some flexibility, collaboration, and a steadfast focus on your objectives (i.e. let’s get down this darn mountain so we can drink some beer) combined with an extreme attention to detail (there’s a rock here, the edge is there, I’m in first, etc).
- Abandon the project. More than nine times out of ten this is not necessary and it does come at a hefty cost. Never persist at the danger of truly falling off the edge into complete project failure. But do reach deep inside and apply the best of all your faculties to wade through the “gnarly part.” Trust that you and your team mates will make it.
Many of us aren’t immediately self-aware that we’re in the “gnarly part.” It starts with a small challenge, maybe a rock in the road, and the challenges multiply until you are knee deep in what seems like a mess. Often our perception of the gnarly part surfaces with big questions about the project and if we’re on the right track. We question our abilities. We question the abilities of others on the project.
The absolute best thing you can do is to be self-aware of the challenge you are in. Take a step back, approach the problem at a different angle, and start moving forward again.
|
By Laura Brandenburg. Laura Brandenburg is an independent business analyst consultant. She is passionate about the BA profession and is committed to contributing by supporting this blog as a forum for business analysts to build on each other's experiences. View more blog posts by Laura Brandenburg |
Related posts:
{ 2 comments… read them below or add one }
Good article! You’re right, just about every project has one of these spots. They become so consuming and we’re so dedicated to pleasing the customer that we sometimes lose some perspective. Usually lives are not at stake and though the project might have its setbacks, it isn’t nearly the crisis we think it is at the time. Thanks for the reminder!
Hi Jeff, I agree, a little perspective can go a long way. Thanks for your comment!
Laura