Got a Problem? Own It Before You Complain.
Problems keep IT employed. If everything worked the first time, if nothing needed to be managed, if all things we implemented were nothing more than 'set it and forget it' solutions - most IT folks wouldn't have a job. It's the reality of what we do, and solving problems is why we have jobs.
Going back to my younger years in the field, it was easy enough to *find* a problem. "Hey, this isn't working as well as it should - we've got problems because of it; I'll complain to my peers and management about it." I did that once - and was fortunate (actually - my initial feeling was dreadfully *unfortunate*) to have a Director that knew how to "guide" me to solve it. I was immediately told - "Good job, thanks for brining this to my attention - now, how are you going to fix it? You own it - keep me posted - it's now a goal for you at the end of the year..."
Honestly - I didn't have a clue what to do when I complained it needed to be fixed, but I was tasked to fix it. So I did. First thing I had to do was learn *why* things were they way they - *anyone* can complain about a problem (critics live to complain - most critics, however, cannot do), but not just anyone will take the effort to understand *why* it became a problem, nor can anyone understand the history behind why decisions were made that lead to the creation of the problem, nor (silos create *this* issue) can anyone be enabled to work with the teams who own the solutions and managment behind the perceived problem area to actually *fix* the problem. Truth be told (here comes the rant), in larger IT shops - individual groups only care about their piece of the puzzle only. Anything else - we'll - that's not my job. You all have been there, and done that. We all have - and it's wrong.
Fortunately, I was in a place and worked under leadership that enabled me solve the problem. Truth is, I regretted ever bringing it up at first, but over time and seeing the success I brought to resolving the problem, I realized I was making a positive change by understanding, engaging, and ultimately resolving the issue at hand. It was a great lesson and a challenge learned that has driven me to be the employee I am today.
From that experience, I learned a few things to solve my criticisms of problems -
1. If you find a problem - learn the history first before you complain. No one person or no one group implements a solution with the sole purpose of causing problems. They implement it first to solve a problem. However, over time, people supporting solutions move off to other roles, inexperienced teams inherit the solutions, *tactial* business decisions modify the solution to meet the buisness decision of the hour - history can explain more often than not why problems are problems far more than the techicalities of the issue themselves.
2. If you see the problem - understand the true impact of the problem. Is the problem client facing? Does the problem keep the client base from making money for the organization? Does it cause issues for the client or IT staff? Prioritize what the problem truly is before moving your complaints up the ladder.
3. If you want to solve the problem - understand the changes and impact to the organziation should you feel it should be fixed - and document what the solution should be. Many times, fixing the problem can create far more issues than the problem truly was for the business. Sometimes, the solution may be less effiecient for the business that the solution that had the problem in the first place. Be wise in what it takes to solve it. Don't cause business distruption just because a 'problem' needs attention. Don't create problems to solve problems.
4. Finally - if you're going to complain about the problem - see 1., 2., and 3. - and own it. Have an answer to the problem - investigate options - the solution may be nothing more than improving a management process or practice of the existing solution. The improvement may also be a true re-architecture of a solution to radically improve what it is you need to provide to the business. Could be anything in the middle as well. You won't know until you learn first. Know what it should take to solve the problem first, before any discussion above you occurs. Lean on other teams for advice and guidance. Don't point blame to any one group or solution for the problem itself - and show how fixing the problem provides value to the business. Anyone can whine, mope, and groan. Don't be a critic - be a solution provider.
Own the answer to something you know should be better to support the business, and know what you should do to fix it before you criticize. Most critics complain because they can't do what it is they complain about. Nobody likes a critic.