Read Time:
Lead each update with the problem it helps a colleague to solve.
A program coordinator in a graduate school revised how her office confirms thesis formatting with students. The new checklist and one-page template reduced the back-and-forth emails that used to fill the weeks before each deadline, and students began submitting with fewer corrections. She sent a short note to the other graduate coordinators describing what she had changed, what happened, and how to adapt the template. Within two weeks, a coordinator in another college had adopted it, and the associate dean asked her to describe it at the next coordinators’ meeting.
The program coordinator’s work became more visible because it was useful. The note described what happened and what colleagues could do with it, and her name was on it.
Many people in higher education are drawn to work that is built on service and collaboration, and for some of them, talking about their own accomplishments sits uneasily with those values. That instinct reflects commitments worth keeping, and it can also mean that useful work only stays known to a small circle. Colleagues can build on the work they know about, and leaders can weigh the contributions they can see. When a result stays within one office, decisions about priorities, collaboration, and next roles draw on less of what colleagues have already learned.
A helpful test for any piece of work is to ask who could use it, and in what form. When you answer that question, your update gives colleagues something to act upon, and you become known for the quality of the work.
Three practices make this routine. Members can read them below.
Members must be logged in to view this content.
How to Use Sophia as an Academic Leader
Building Trust“I’m new as [role] in [department/division]. [Name or title] has been here [number] years, has a lot of informal influence, and is set in their ways. Our unit needs to change [specific area]. Ask me questions to help me think through how to build trust before I push for change.”
