Back in August I wrote a post about the Digital Workplace project that I’d been invited to participate in as Product Owner, and I promised I’d share updates along the way. In that post I also mentioned that I wanted us to use a solution selling model as a way to drive adoption across the University, and that’s the element I want to touch on today. I also want to point out a couple of things that the solution selling model doesn’t quite nail, and talk about how important it is for us as a project to address those shortcomings.
Applying a startup mindset to internal IT projects
A few weeks back I wrote a post about the kick off of a Digital Workplace project, encompassing synchronous collaboration (such as live chat), asynchronous collaboration (document sharing/collaboration) and project planning/management. I wrote about two strategies that jumped to mind – using a Solution Selling approach to drive adoption (noting that the tools we’re looking at are already freely available, if not readily used), and to ‘dogfood’ the tools within the governance group before expanding out to ‘real’ customers.
Today I want to add a third strategy – applying a startup mindset and principles to what is an internal IT project.
The power of the uncomfortable keynote
I was privileged in the last 48 hours to attend two of the best keynote presentations, actually no, the two best keynote presentations I’ve seen in my twenty years of attending education-related conferences. Three things made them stand out for me:
- Diversity: Neither of them looked like me, sounded like me, or had grown up in a world that I have any meaningful knowledge of;
- Quality: Both were inspirational in their contributions to society, and spoke from the heart with passion, expertise, wisdom and eloquence; and
- Dissonance: Both made me feel, at times, quite uncomfortable within myself as I listened to their stories.
I want to touch on all three of these, but devote more focus to the third.
Learning from agribusiness and the value of looking outwards
In my three years working at Flinders and the seven years before that doing consulting work across a whole bunch of other unis, it has struck me that the Higher Ed sector isn’t always brilliant at ‘looking outwards’. I’ve been guilty of it myself on many occasions – in the face of a problem, the first point of call is often to reach out to my counterparts in other Unis and ask how they’ve tackled a similar situation.
Not that this is all bad, in fact it makes perfect sense in a lot of cases to avoid reinventing the wheel. Where it falls down is the potential for having the same sets of eyes with the same knowledge and experience finding the same solution for a similar problem, leading to ‘institutional isomorphism’, i.e. every organisation ending up looking the same in how they operate (Simon Marginson talks about this at a more organisational level in some of his papers like this one, but it applies just as well on a smaller scale I think).
The IT project governance group – kickstarting Agile behaviour change in a Digital Workplace project
I scared an Agile coach this week.
I’ve recently taken on a project role as Product Owner for an IT project we’re calling the Digital Workplace project, which aims to more effectively leverage several collaboration technologies (such as live chat, document sharing/collaboration and project planning/management) across the professional services teams at the University. Although I’ve called it an IT project, there’s really very little new technology in it, and it should really be called a behaviour change project underpinned by accelerated technology adoption – or something. In fact, all three likely tech tools involved are already available to all staff, it’s just that very few people actually use them.