Some time back one of my managers sent out an email announcing that we had just won an account. This was a very big deal for us as our product was new to the marketplace and we were working hard to gain acceptance with customers. Several of us responded to the email expressing our excitement over the new account. One of my managers responded with "I've got concerns" and listed off a series of issues with servicing the account. All of the issues that the manager brought up were valid issues; the problem is that I didn't know who was expected to do what regarding the issues.
When situations like this happen with me, I like to have the one that raises the issue get with a small subset of interested parties to come up with a resolution to the issue, and hold the person who raised the issue accountable for reporting back to the rest of the team as to the resolution. What I've found in doing this is that the quality of the solution is much better than a solution that any one person could have come up with because the interested stakeholders have all put their thumb-print on the resolution.
Next time one of your team members raises an issue, consider putting the issue back to a few of your team members, asking the person who raised the issue to drive resolution to the issue, and reporting back to the team the proposed resolution. You'll get a better quality resolution and you’ll reduce churn with the team.
Keynote Speaker | Board Director | Autism Advocate | Author | Project Management Expert | Microsoft/Accenture Veteran
See his books on Amazon.
Contact Lonnie about article reprints. Please specify article you wish to reprint.
See Lonnie's Amazon Author Page