In the corporate era, leadership is defined by rigid hierarchies and structures. However, the digital age has fundamentally rewritten these rules. As I reflect on my journey at UWC from a student to a Class Representative, and now to a Graduate Lecturing Assistant (GLA). I have realised that digital leadership is not about having all the answers. It is about creating an environment where the best answers can emerge. Leading in technology-driven environments requires a blend of transparency, technical excellence, and the agility to pivot leadership styles based on the urgency of the task at hand.
Transparency
One of the most significant mindsets I have adopted in my role as a tutor and GLA is the leveling approach. In tech environments, problems compound exponentially. A small error can snowball into a project-ending crisis if left unaddressed.
I believe responsible leadership is rooted in a ridiculous amount of transparency. By empathising with my tutors and students and making it clear that I value honesty over immediate perfection, I am practicing a form of “Agile Leadership.” This creates psychological safety, a concept essential for organisational agility. When team members feel safe enough to admit they are stuck before a problem becomes massive, the organisation remains lean and responsive. In this context, my leadership capability isn’t just about managing people. It’s about managing the flow of information to prevent bottlenecks.
Collaboration
Leadership is often mistakenly viewed as a solo performance, but my experience as a GLA has shown me it is a collaborative craft. I am particularly fortunate to work with a specific tutor whose willingness to help goes beyond his basic duties. He has become a vital part of my leadership development because he provides a safe space for me to test my ideas and strategies but, most importantly, to be vulnerable.
By being willing to go beyond his role, he allows me to refine my leadership style. Whether it’s discussing how to approach a difficult grading session or brainstorming more efficient ways to manage student queries, his feedback helps me stay grounded. This relationship embodies the mindset of continuous iteration. Just as software is refined through user feedback, my leadership is refined through the willingness of those I “lead” to engage with me honestly. It reminds me that a leader’s most important capability is the ability to listen and adapt based on the insights of their team.
Vulnerability
While I often find myself in the position of the “expert” leader, the last two weeks have forced me to confront the other end of the spectrum. I have experienced the discomfort of being the person depending on others, only to find myself coming up short. This shift from being the provider of solutions to the dependent has been a stark reminder of the pressures my own team members face.
Managing this state of dependency is difficult, especially when you are used to leading. It has highlighted a critical leadership capability: the grace to be managed. I’ve found it challenging to navigate the feeling of falling behind, yet this experience is vital for developing true empathy. To lead responsibly, one must understand the weight of a deadline from the perspective of someone who is struggling. This recent period has taught me that agility isn’t just about moving fast; it’s about how a leader supports those who are struggling without crushing their morale.
Despite these recent personal hurdles, I recognise that in projects like the UWC x HNU hackathon or technical platform development, leadership often gravitates toward technical proficiency. In these high-pressure environments, we didn’t always have the luxury of formal elections. Leadership was emergent.
Because I was often consulted for technical direction, I had to lead through influence rather than authority. This is a hallmark of the digital age. The most effective leaders are often those who can do as well as direct. However, leading through technical excellence requires a specific mindset. One must remain humble enough to be corrected while being confident enough to provide a roadmap. This experience taught me that agility is boosted when the person with the most relevant knowledge is empowered to lead the current phase, regardless of their formal title.
Balance
Finally, the concept of Organisational Agility hinges on the ability to switch between leadership modes. My natural preference is for an approach where everyone feels they have contributed. However, as I have experienced with tight academic and development deadlines, there is a tipping point where inclusion can become an obstacle to progress.
Responsible leadership requires situational leadership. When the clock shows we are running out of time, I have learned to pivot from a facilitator to a delegator. This isn’t about abandoning agility. Being able to decisively assign tasks and enforce accountability during a crunch period is a capability that prevents project failure.
Conclusion
Leadership in the digital age is a balancing act. It requires the soft skills of empathy and transparency to keep the team healthy, the collaborative spirit to learn from those we lead, and the hard skills of technical proficiency to keep the project viable. My recent struggles, paired with the support of my team, have added a layer of humility to this perspective. I am learning that an agile leader must be as good at supporting the struggling team member as they are at directing the successful one. Moving forward, I aim to maintain this. I recognise that the best leaders are those who can navigate the complexities of both human vulnerability and technical architecture.

