top of page

More Than a Title: Rethinking the Coordinator Role

  • russellsmichalak
  • 17 hours ago
  • 5 min read

Why "coordinator" can mean real authority, accountability, and a pathway to leadership.

There is persistent skepticism about the coordinator title in many professional environments, including libraries. The critique is usually that coordinators are given responsibility without authority. They are expected to lead, but with no real power to hold people accountable, shape expectations, or make consequential decisions. The title, in this reading, is a way of assigning labor without conferring the legitimacy that makes that labor effective.


However, there can be a different framing. Not because the concern is entirely unfounded, but because it conflates a poorly structured role with an inherently limited one. Done right, the coordinator role can be a genuinely substantive position of authority, one that develops leaders, strengthens teams, and serves organizations well. The problem is not the title. The problem is when organizations fail to back it up.


What Coordinators Actually Do (When Given the Chance)

Consider what a well-structured coordinator role looks like in practice. The coordinator provides leadership and direction for a unit or team. They set expectations, establish priorities, and create the conditions under which people can do their best work. They give feedback, evaluate performance, and help team members grow professionally. They serve as the connective tissue between organizational strategy and day-to-day operations.


That is, in all meaningful senses, supervision. The fact that the position is called "coordinator" rather than "manager" or "director" does not change the substance of what it requires. What matters is whether the organizational structure is built to support that authority, and whether the people above and around the coordinator treat it as real.

In libraries specifically, coordinator roles often emerge in functional areas such as instruction, digital initiatives, research services, or outreach, where teams need someone to provide cohesion and leadership without the full administrative apparatus of a department head. These are legitimate, complex leadership roles. When they are staffed thoughtfully and supported institutionally, they work. When they are treated as administrative conveniences with ambiguous standing, they fail, and that failure is organizational, not inherent to the position.


The Case for Structured Authority

What does it mean, practically, to structure a coordinator role so that it carries genuine authority? A few things matter a great deal.

First, the reporting lines need to be explicit. If people are "working with" a coordinator rather than "reporting to" one, that ambiguity will undermine the role every time. Coordinators who manage performance must have clear, formal authority to do so, including responsibility for annual reviews, professional development conversations, and accountability processes. Supervision without formal standing is not supervision; it is an awkward negotiation.


Second, the coordinator's scope of authority needs to be defined and communicated broadly. When a coordinator sets a direction for the team, that direction should carry institutional weight. When they make decisions within their area of responsibility, those decisions should hold. This requires that senior leaders actively reinforce the coordinator's standing, especially in contexts where the title might invite skepticism.

Third, coordinators benefit from being included in relevant decision-making structures. If a library has a leadership team that meets regularly to discuss priorities and resources, the coordinator responsible for a major service area should have a seat at that table, or at least a meaningful channel for input. Exclusion from those conversations signals that the role is peripheral, even when the responsibilities are not.


Unit Cohesion as a Leadership Function

One of the most undervalued things a coordinator does is build and sustain unit cohesion. This is not a soft skill or an interpersonal extra; it is a core organizational function. Teams that lack cohesion are less effective, less innovative, and harder to sustain. The work of building shared purpose, establishing norms, navigating conflict, and helping people feel they belong to something meaningful is demanding work. It requires attention, intentionality, and leadership.


Coordinators who excel at this function create teams that can absorb change, respond to pressure, and develop internal capacity over time. That is a significant organizational contribution, one that is often invisible until it is absent.


A Stepping Stone, Not a Ceiling

The coordinator role is also, for many professionals, a critical developmental stage. It is where people first experience what it means to be accountable for a team's performance, to set direction rather than follow it, and to navigate the interpersonal and institutional complexity that comes with leadership. Done thoughtfully, the coordinator role prepares people for positions of greater scope and responsibility.


Organizations that treat coordinator roles as genuine leadership positions and invest in developing the people in them build stronger internal pipelines. They create conditions in which people can demonstrate leadership capacity before they are asked to do so at scale. That is a strategic asset, not just a staffing arrangement.


For the individual in the role, it is worth approaching the coordinator position with the same intentionality you would bring to any leadership role. Seek feedback actively. Invest in your own development. Pay attention to how you are building your team's culture and capacity. Use the role to learn, not just to do. The experience you gain will serve you throughout your career, whatever title comes next.


The Honest Caveat

None of this means that all coordinator roles are structured well. Many are not. Some organizations genuinely do create positions that carry the expectations of leadership without the authority to exercise it. People in those positions face a real and frustrating challenge. If you find yourself in one, it is worth naming the gap directly to your supervisor, advocating for the structural clarity the role requires to function, and honestly assessing whether the organization is willing to make the necessary changes. Not every role can be fixed from within.


But the existence of poorly structured roles does not mean the model is broken. It means the implementation needs work. The coordinator role, at its best, is not a consolation prize or a category trick. It is a serious leadership position that develops capable leaders and serves organizations well. It deserves to be designed and supported accordingly.


Further Reading

Bolman, L. G., & Deal, T. E. (2013). Reframing organizations: Artistry, choice, and leadership (5th ed.). Jossey-Bass.


Drucker, P. F. (2008). The essential Drucker: The best of sixty years of Peter Drucker's essential writings on management. Harper Business.


Galbraith, J. R. (2014). Designing organizations: Strategy, structure, and process at the business unit and enterprise levels (3rd ed.). Jossey-Bass.


Hackman, J. R. (2002). Leading teams: Setting the stage for great performances. Harvard Business Review Press.


Hill, L. A. (2019). Becoming a manager: How new managers master the challenges of leadership (new ed.). Harvard Business Review Press.


Mintzberg, H. (1980). Structure in 5's: A synthesis of the research on organization design. Management Science, 26(3), 322–341. https://doi.org/10.1287/mnsc.26.3.322


Yukl, G. (2012). Effective leadership behavior: What we know and what questions need more attention. Academy of Management Perspectives, 26(4), 66–85. https://doi.org/10.5465/amp.2012.0088


 
 
 

Recent Posts

See All
The Importance of Trust and Honesty in Leadership

It seems fitting to write a post about trust and honesty in leadership, especially as we are in the midst of the election cycle in the U.S., and we are bombarded with commercials and other material ab

 
 
 

Comments


bottom of page