Skip to main content

Time out: co-mentoring


A year ago I completed a year-long course run by the Leadership Foundation for Higher Education.  This course brought together 18 IT and library managers from universities across the UK and Ireland, made us look at who we are, what we value and how we work, and then gave us lots of pointers for how to lead our teams and projects more effectively.

This week we all gathered for a reunion and for meetings of our "action learning sets".  These sets are groups who help each other with problems we encounter in our jobs.  Sometimes these are practical problems; sometimes they are about relationships with other people; sometimes we just ask the others to help us understand our own thoughts and feelings.

I'm blogging about this because everyone in my action learning set has found it hugely valuable to have someone we can talk to who will give us their honest response, in an atmosphere of trust.  The fact that we are all from different institutions mean that our reactions are not tinged by concerns about how we will interact outside the group.  This trust allows us to challenge each other as well as to provide mutual support: we don't get an easy ride from the other members.  Our meetings tend to be both intense and exhilirating.

I've found it very worthwhile to have someone I can talk to like this, outside of work and family.  Several other people have also told me that they have benefited from mentors of some form or another.  So if an opportunity arises for anyone reading this blog to get this sort of advice and feedback, I'd definitely recommend that you give it a go.

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…