Skip to main content

Aleks Krotoski, Cory Doctorow, Tim O'Shea and more: IT Futures on Disruption

I'm beginning to wind down for the xmas break - just the Student Systems Board tomorrow, a meeting of the Applications Architecture Governance Group, a review of the first phase of development for the new university web site, then a xmas curry with the web site team on Friday, and that will be me off for a couple of weeks.  But before I finish, I want to record some thoughts about our IT Futures conference for 2013, which was held last week.

We started planning this in January, when we were thinking about ideas for a theme and potential speakers.  I had the idea of inviting a science-fiction writer to give an outsider's view of what higher education might look like in the future.  This was tossed around a bit and Jen Ross suggested Cory Doctorow.  Meanwhile, the theme of "disruption" rose to the surface.  We put the two together and a potential agenda began to take shape.

The next step was to add a less technical and more people-oriented take on "disruption".  For this, the name of Aleks Krotoski was suggested.  So we contacted both Cory and Aleks and were very pleased when they both agreed to speak.  The Principal, Tim O'Shea, also agreed to give his views of the challenges facing the University.  We had a programme.

And on the day it went very well.  Aleks actually gave her talk by pre-recorded video and then joined a response / Q&A session via Skype, with Chris Speed engaging Aleks in a discussion about some of the key points; this format worked rather well given the theme of the day.  Cory also strayed from traditional academic style, sitting on a table and talking with no need for slides.  Our other presenters were more traditional (not being media stars) but made good points.

The only thing that went less well than planned was the audio for the concluding panel.   I had suggested that we structure this like a radio chat show rather than a traditional academic panel, to make it more engaging.  In terms of content, it worked - the discussion was rather interesting - but unfortunately the audio wasn't up to handling that number of microphones in close proximity and there was rather a lot of interference so that people at the back of the hall couldn't hear the conversation properly.

Overall though it was a very good day and I'm glad to have been a small part of it.  I really had little to do with the actual organisation of the event.  I'm not being modest - I simply didn't have enough time to devote to this on top of the day job, however much I would have liked to do so.  So my thanks to the rest of the team for turning all our ideas into reality.

Comments

Popular posts from this blog

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

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…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …