5
5
0
We hear it all the time, to be a good leader is to know when to make the right call. Over the past few months, I've had the honor of taking a course here in Pittsburgh that was designed to help Veterans take their existing leadership skills and develop them to better serve the area by learning more about the Greater Pittsburgh area. During this class, we were broken down into small groups and teamed up with different agencies to help pull together a program that would benefit that agency. One of the groups was teamed up with a City Council member and her office and their idea was to pull together this home fair.
Sadly, because of the short time frame we had, they had to shift their focus from trying to do this fair because they reached a point where they had to either try to squeeze something out that would not be at the high level of quality they wanted or to cancel it. As leaders, they decided to cancel it and change their scope into putting together a packet, a how-to basically, of the information they gathered and gave it to the council woman's office as a way to help them still do this fair but on a more realistic time line.
So as we were all presenting our different projects as the class comes to an end, this group gets up to presents and shares all this with us. And it got me thinking of some great leadership quotes and examples I've seen or heard of. I've once heard that to be a great leader you must be willing to order the destruction of the thing you love. I've seen commanders looking over battle plans to figure out which of the options was the least bad. I've sat in meetings where leaders had to make tough calls on issues that everyone was passionate about. Yet during this presentation, the one thing I pulled away from it is to be a good leader, you must be willing to stand up and say "No". While this is not the original outcome we would want, it is sometimes the best outcome for all.
So the question to RallyPoint I have today is this. When, as a leader, have you had to say "No" to something because you knew that trying to push something through would be even worse? What lessons can we as leaders gain from saying "No"? Is saying "No" ever completely wrong?
Sadly, because of the short time frame we had, they had to shift their focus from trying to do this fair because they reached a point where they had to either try to squeeze something out that would not be at the high level of quality they wanted or to cancel it. As leaders, they decided to cancel it and change their scope into putting together a packet, a how-to basically, of the information they gathered and gave it to the council woman's office as a way to help them still do this fair but on a more realistic time line.
So as we were all presenting our different projects as the class comes to an end, this group gets up to presents and shares all this with us. And it got me thinking of some great leadership quotes and examples I've seen or heard of. I've once heard that to be a great leader you must be willing to order the destruction of the thing you love. I've seen commanders looking over battle plans to figure out which of the options was the least bad. I've sat in meetings where leaders had to make tough calls on issues that everyone was passionate about. Yet during this presentation, the one thing I pulled away from it is to be a good leader, you must be willing to stand up and say "No". While this is not the original outcome we would want, it is sometimes the best outcome for all.
So the question to RallyPoint I have today is this. When, as a leader, have you had to say "No" to something because you knew that trying to push something through would be even worse? What lessons can we as leaders gain from saying "No"? Is saying "No" ever completely wrong?
Posted in these groups: 
Leadership
Leadership Development
Leadership Leadership Development
Posted >1 y ago
Responses: 7
3
3
0
This depends on who I'm saying no to. As far as a boss goes, I have had to tell him no I will not work my Maintenance Department over the weekend unless he explicitly orders it himself. The reason was that we had given a 3 day weekend as a reward for hard work and a lot of long days including a couple of weekends. The need to work that weekend was 100% due to an Operations and Headquarters failure to plan. I told him I was not going to go back on my word and tell them that although we gave them Friday off they would have to work Saturday and maybe Sunday. He ended up siding with me, but standing my ground cost me later in a ranking situation. Not the way it should have happened but I am still glad I made the call.
Several times I have had to tell people that worked for me that their request or desire to do something could not be accommodated. One of the biggest of these is leave requests that are routed up with almost no time before the leave is. I have had to deny leave to someone who bought non-refundable tickets, but they failed to route their request until 2 days before the leave and we literally didn't have someone else to cover their shift the following week. Again, a decision that made me unpopular, this time with those that worked for me.
Several times I have had to tell people that worked for me that their request or desire to do something could not be accommodated. One of the biggest of these is leave requests that are routed up with almost no time before the leave is. I have had to deny leave to someone who bought non-refundable tickets, but they failed to route their request until 2 days before the leave and we literally didn't have someone else to cover their shift the following week. Again, a decision that made me unpopular, this time with those that worked for me.
(3)
(0)
SGT Ben Keen
Leadership is never about being popular as you illustrated so perfectly in your comment LCDR (Join to see). Some great examples of when a leader had to say "No" because it was what was best.
(0)
(0)
LCDR (Join to see)
SGT Ben Keen thank you.
In my opinion it should always be hard for us to say no. That means that we WANT to accommodate reasonable requests and take care of both our bosses and our subordinates. The tough part is not saying yes at the wrong times and ending up in no-win situations.
If I had "caved" to my Commander in the first situation, I would have irritated the entire department and lost some credibility. Furthermore, I would have also lowered the Commander's esteem. Most of the troops didn't know how close they came to losing that liberty they had worked hard to earn, and if it had happened command climate as a whole would have suffered.
In my opinion it should always be hard for us to say no. That means that we WANT to accommodate reasonable requests and take care of both our bosses and our subordinates. The tough part is not saying yes at the wrong times and ending up in no-win situations.
If I had "caved" to my Commander in the first situation, I would have irritated the entire department and lost some credibility. Furthermore, I would have also lowered the Commander's esteem. Most of the troops didn't know how close they came to losing that liberty they had worked hard to earn, and if it had happened command climate as a whole would have suffered.
(0)
(0)
2
2
0
Does it violate policy? Can a troop get hurt or killed? Is it part of "best practices" or the Creed? Does it go against the K.I.S.S. principle? Will it make you part of the next safety brief? How much a** are you willing to loose in the 1SG and CDR's office? Will you be fired or relived? Can you LIVE WITH that decision? Important questions to think about when making that yes or no answer.
(2)
(0)
1
1
0
One does not need to take a course to be a good leader, whether military or civilian. In all situations, one looks at the objective given by top management and does what it takes to accomplish that objective. How it is accomplished does reflect on the person saying yes or no. My practice was to listen to all relevant information, then make a decision and explain why that was the result. If anyone had strong feelings, I invited them to my office, after working hours and explained it on a personal level
(1)
(0)
Read This Next
Continue with Facebook 
Continue with Google