The start of the academic year brings with it a plethora of new energy and new opportunities, as everyone who works in education knows. Once again, the summer months flew by too quickly, the to do list didn't really get any shorter, and we all feel like we are scrambling to prepare for the beginning of the year. That chaotic energy is electrifying for some, and exhausting for others, and the two are not mutually exclusive. This is also a time to remind myself and others of the importance of saying no.
Perhaps more than any other word, "no" is fraught with challenges and anxiety in higher education. The new year brings with it new opportunities, new research, and new initiatives. We have new chances to collaborate with others and move our own goals forward, having freshly set them for the new year. There is also a renewed pressure to perform and demonstrate that performance to others, whether it be on the way to tenure or a future promotion down the line. Perhaps you're in a new role and anxious to prove that folx made the right decision in hiring you. Whatever your story happens to be, it's pretty much a certainty that you are going to get asked to "do" or "serve" in all sorts of capacities.
The excitement others have for these new initiatives or projects very easily spills over into our world. In fact, a lack of excitement for that opportunity on the part of the person asking is probably a red flag warning you to stay away in the first place. However, that infectious energy can sometimes cause us to forget about our own goals and priorities. There can be a great deal of joy in helping someone else achieve their goals, and this can be a worthwhile endeavor in and of itself. At some point, though, we need to remember to focus on our own goals.
If created with intent, thoughtfulness, and deliberateness, your goals will most assuredly intersect with others' goals, and ultimately funnel back to the organization's strategic plan. When presented with an opportunity for additional involvement, it's important to ask ourselves how it relates to our own goals and that of the organization. Will the outcome of this work impact some other aspect of your work? Will you build relationships during this work that will be mutually beneficial in the future? Will you be involved in hiring someone that will be a key partner in your work in the future? Will you gain new skills as a result of this work that will be useful later? Would you work on this project if your name wasn't on it? Will I need to stop doing other work or step back from something else in order to contribute?
These are all important questions to ask yourself when considering whether to accept the invitation. Of course, sometimes the relationship is the thing. We all want to feel as though we belong, and positive working and social relationships help to facilitate that sense of belonging. Perhaps you simply enjoy the company of the individuals you'll be working with and you look forward to spending more time with them. Whatever your reason, be clear in advance, and track your responsibilities.
This brings us to the importance of knowing when to say no. I tend to think of this moment both in isolation and in context. On it's own, I'm considering the questioned mentioned earlier, as well as the various other political and social factors that influence such a complex web of human interaction. In context, I'm trying to be cognizant of the full scope of my responsibilities at any given point. I may really want to be involved in a new committee or opportunity, but I recognize that my plate is full and I'm not in a position to set anything aside at the moment.
Once we may the decision to decline, the delivery is important. Simply declining politely is always a straight forward option, but often we must consider the relationship and the future implications of that work, even if we aren't involved. Thus, explaining the lack of availability at the moment can be important, but it's also important to reiterate the interest in the work and the future outcomes. For me, this means following up on the work even if I declined to be involved at the moment. You never know when additional opportunities might present themselves.
When I think back over my career, there are many moments where I know I should have said no. I didn't have the bandwidth, and I overextended myself. I was genuinely interested and the desire to be involved in work that others are generally passionate about is strong. I'm certainly not alone in this reality, and you can no doubt think of a yes that should have been a no right now. So, just like an annual review of the terms of service, don't simply click accept, but truly take to heart the importance of saying no. There will always be more work than we have time for, but our time continues to be our most valuable asset!
