| I wanted to share a recent event that is in line with our communication war stories topic. Over the last couple of days, my team has been trying to work a project and secure some critical data that is hard to get. Our different teams were tripping over each other trying to understand what we were doing.
Here is our situation: My company qualifies customers for services on estimated guesses. After the customer is installed and using the services, my company now gets real data and knows how well a customer can use a service and what additional services and speeds for which a customer can qualify. What we needed was the original qualification (the promise given to the customer), not what the actual data after the install says. We were using words like original loop qual, loop qual at point of sale, service promise, estimated loop qual, and calculated qualification.
Impact: This part of the project was in confusion and getting no where. Subsequent analysis dependent upon this data downstream could not proceed. This data was on the critical path. If the wrong data is pulled, we come up with the wrong conclusions or have to restart the data pull. Then, the project gets delayed or is implemented poorly.
Next steps and results: We had to get everyone on the phone and clear up the confusion immediately. Next, we had to clearly define what the actual ask is for that data. Last, we memorialized that definition so that there was no more confusion. Sounded like a lot of work, but it was absolutely necessary.
Did we do it right? Was there something else we should have done? |
by Marcos Arias
on: October 23, 2014 02:55 PM