Gone are the days of wandering round a building trying to find the meeting room your next meeting is meant to be in. Now a days, in the new world of working from home and virtual meetings I seem to be wandering round the internet trying to find my next virtual meeting host.
I’ve had to download a load of new software/ sign up for new accounts etc; and have already (just the once thankfully) gotten lost and sat in the wrong virtual meeting space wondering why no-one else has turned up.
The art of remote working isn’t new to me (in the old world I worked at home 2-3 days a week anyway) but as everyone moves to this new way of working; I’ve gained a lot more meetings and workshops; and skipping between meeting spaces is a new challenge, and one I suspect i’m not alone in facing.
So here are some top tips I’ve learnt so far:
Make sure meetings are 45 mins out of an hour; this leaves people 15 mins between meetings to stand up, move around, get a cuppa etc, before they load up their next meeting.
Make sure the meeting location is highlighted in the location, and again in the meeting text. I’ve spotted in a few meeting invites (possibly because we use G-suite) that hangouts seems to be in there, even when the meeting is actually on Zoom etc.
Check when setting up a meeting that everyone can access that meeting space (I can’t access Skype as we don’t use Microsoft) and ensure you’re highlighting the dial in option for those that need it.
As individuals taking ownership of our calendars and blocking out time when we are free for calls, or need to do something else* and aren’t available for meetings, to ensure we are not constantly running from one meeting to another with no time to ‘do stuff’
And as meeting organisers we should enable and encourage people to dip out of meetings when they get a phone call they have to take or need to do something else*, and come back when they can!
Don’t be afraid to recognise when you aren’t adding value to a meeting, or when you can add more value elsewhere and allow yourself to leave meetings you don’t have to be in; and as meeting organisers we should be calling our and encouraging people to do just that.
*Especially with more people having children at home, or others in the house also working from home.
The main takeaway for me is that it’s much easier when working from home to just sit at your desk all day; as I no longer have the onus on me to walk to my next meeting; or pop over to a colleagues desk for a chat; so I need the time between meetings to move around and stretch if nothing else. Secondly I’m more likely to leave a virtual meeting open even when I have other work to do and I can’t give it my full attention, as it’s just another screen; whereas before I was much better at being careful and prioritising my time when I had to be in the room physically; a bad habit and one I ( and others) need to make sure we’re not falling afoul of.
The world is changing and we need to change our working habits to stay healthy and productive. We can’t just make everything virtual, we need to adapt our working practices to make virtual work for us. Who knows if, or when, we will ever return to our old meeting rooms!
In a previous blog I discussed the importance of understanding the value you are trying to add, and how you measure cost vs vale. How we measure value and ensure we are delivering a valuable return on investment is one of the ‘big’ questions at the moment, that never seems to go away.
Scott Colfer has equally blogged before on the complexity of measuring value when there is no profit to measure against. When working in the public sector it’s not an easy problem to solve. There is a lot of conversations about making sure we don’t waste public money, but how do we actually make sure public money is being spent in a valuable way?
The first principle of the Agile Manifesto is “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” But what is valuable?
At a kick off session this week, for a new project we’re shortly going to begin, a client said one of their hopes was that all code deployed would work first time; and someone else stated that they ‘didn’t want rework’. When we broke these thoughts down to understand where these fears were coming from, it was the need to add value and not waste money; which itself was coming from previous issues caused by a long time to deploy, and the cost to make changes.
There was equally the fear that by swapping out suppliers mid project we (as the new supplier) would want to redesign and rework everything to make it our own; which would slow down delivery and drive up cost even more.
There is obviously no value for anyone in doing that. The value comes by having a short feedback loop, co-designing and constantly testing, learning and iterating, working together in short weekly or fortnightly sprints, to get things delivered. Making sure there is little time as possible between designing something, to getting it tested and used by real users; ensuring it meets their needs as quickly as possible.
Through examining what has been delivered already against the user needs and the outcomes the organisation is looking to achieve; by identifying gaps and pain-points we reduce waste; and by prioritising the areas where improvements can be made we ensure that reworking only happens when there is actual value in doing so.
At a talk this week I was asked how we prioritise the work that needs doing and ensure that we do deliver. The important thing is to deliver something, but ideally not just any old thing, we want to ideally be delivering the right thing. Sometimes we won’t know what that is, and it’s only by doing something that we can establish whether that was the right thing or not. But that’s why short feedback loops are important. Checking back regularly, iterating and testing frequently, allows you too recognise when there is value in carrying on vs. value in stoping and doing something different.
When I’m trying to decide where the value is, and where is the best place to start, I consider things like:
Why are we doing this?
Why are we doing it now?
What happens if we don’t do this now?
Who will this affect?
How many people will it impact?
How long could this take?
Any indicative costs?
Any key milestones/ deadlines?
Any critical dependancies that could affect our ability to deliver?
Will this help us deliver our strategy? Or is it a tactical fix?
Once we have started work, it’s important to agree measure of success (be they financial, reducing time, staffing numbers; or things like improved uptake or a better customer experience) and keep measuring what is being delivered against those targets.
At Difrent a key part of the value we add is about the people, not just the technology or processes; there is value in us working in the open, by being transparent; running lunch and learn sessions or talks; blogging or speaking at events etc. we can add wider value outside of a specific project or service.
When we are considering what adds value, the other thing it’s important to consider is the culture we are delivering in. Are there communities of practice in place already, any design patterns we should be adhering too? There is value in building in consistency, as this helps us ensure we are delivering quality.
There are many different ways to determine what adds value, and many different kinds of value, but the importance is by focusing on making positive improvements, and by constantly learning from mistakes and ensuring they don’t get repeated so no time is wasted and real value can be delivered.
Back when I started working in Digital as a Product Owner in 2011, and I did my agile training course, one of the first ‘principles’ that was discussed was ‘There is no such thing as a stupid question”. Which as a newbie in the agile/digital world was great to hear, because I felt like I knew literally nothing.
This concept has always been something I’ve repeated to the teams and people I’ve been working with. There will always be something you don’t know, it is impossible to know everything. Therefor we have to be able to ask questions and find out information without fear of being made to feel stupid.
However, as digital transformation and agile begins to roll out and spread, that acceptance of ‘not knowing’ seems to have become less common. I hear a lot from colleagues outside of digital that ‘agile is a cult, or digital is a clique’ with it’s own language that doesn’t welcome in those who don’t know the ‘lingo’.
A friend of mine had a scrum coach in to speak to their team and deliver some training to their organisation (if you don’t know what scrum is, that’s ok, here’s a link), and she said the way that he spoke to them was as if they were all idiots who knew nothing, and that he made scrum sound like a religion for zealots. There was no opportunity to question, only to agree. This isn’t what should be happening. There’s no better way to foster feelings of exclusion and frustration than be treating people who don’t know something as ‘lesser’.
The public sector has always struggled with acronyms, and while we regularly hear about the drive to reduce the use of them with the greatest will in the world, everyone will find themselves slipping up and using them sometimes, because they are everywhere and we assume that everyone knows them. But we have to remember that they don’t.
At a global digital conference last year in The Hague I was happily chatting away to someone working for the Dutch Pensions service and kept referencing several Government Departments by their acronyms without thinking, leaving the poor person I was speaking to rather lost.
Similarly in my interview for my current role, I was too embarrassed to check an acronym (PnL) and just assumed I knew exactly what I was being asked about. It was only after 10 minutes of waffle I was politely corrected that I was not been asked about Procurement frameworks and instead about my experience of managing Profit and Loss. Obvious in retrospective, but never an acronym I’d heard before and who want’s to look ignorant in an interview?
Clare made a point that often we’re not actually saving time by using acronyms, but we are gatekeeping and increasing that siloed attitude, which is counterproductive to the work we’re doing. This is especially important, as Rachelle pointed out, given how inaccessible acronyms often are, and that they are actually not unique. One random set of letters to me may mean something completely different to someone else working in a different organisation or sector or with completely different experiences. We are actually increasing the chance for confession and misunderstandings while not saving time or effort.
There is a lot of great work happening in the Public sector, using the Digital Service Standards (primarily standard 4 – make the service simple to use, and 5 – make sure everyone can use the service) and the principles of the Plain English Campaign, to simply the content we provide to users, to make it clear, concise and easy to comprehend. However when it comes to how we talk to each other, we are forgetting those same standards.
My conversation this week has reminded me how important it is, as a Senior Leader to:
firstly try and not use acronyms or digital/agile jargon, or to not make assumptions about other peoples knowledge without checking first their experience and understanding.
Secondly, speak up and ask more questions when I don’t know things. To show by doing, that it is ok to not know everything.
After-all, there are no stupid questions, just opportunities to learn and share knowledge.
So you’re a leader in your organisation and Agile is ‘the thing’ that everyone is talking about. Your organisation has possible trialed one or two Agile projects within the Digital or Tech department, but they haven’t really delivered like you thought they would, and you think you can ‘do more’ with it, but honestly, what even is it in the first place?
It’s a question that comes up fairly regularly, and if you are asking it, you are not alone! This blog actually started from such a conversation last week.
First and foremost there is Agile with a capital A, this is the project methodology, predominantly designed for software development, as defined here. It “denotes a method of project management, used especially for software development, that is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans.”
However nowadays, especially in the public sector, agile doesn’t only apply to software. More and more of the conversations happening in communities like #OneTeamGov are about the culture of agility. How you create the environment for Agile to succeed, and this is where many people, especially leaders, are getting lost.
So how do you ‘be agile?’
Being agile is borrowing the concepts used in agile development, to develop that culture. As Tom Loosemore says when talking about Digital, it’s about “applying the culture, processes, business models & technologies of the internet-era to respond to people’s raised expectations.”
But it’s more than what you transform, it’s how you do it.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
When you consider individuals and interactions over processes and tools, then you remove unnecessary hierarchy and empower people to make decisions. You don’t enforce rigid processes for the sake of it, but iterate your governance based on feedback of users (in this instance your staff!). By being agile you focus on communicating directly with human beings, looking to how you can accommodate more actual conversations, and time together, rather than relaying on emails and papers as your only way to communicate.
By prioritising working software over comprehensive documentation you are constantly testing and iterating what works based on what is meeting your user needs, rather than deciding upfront what the answer is before knowing if it will actually work. You involve user research in your policy and strategy discussions. You analyse and test your new processes before you implement them. You change your funding and governance models to allow more innovation and exploration, and base your decisions on data and evidence, not theory. By being agile you are able to demonstrate working product or tangible services to stakeholders and customers, rather than just talking about what will be done.
Customer collaboration rather than contract negotiation is about bringing people along with you and working in partnership, achieving results together. Embracing and managing change to be innovative and deliver value whilst still being competitive and minimising unproductive churn and waste.
When thinking about responding to change over following a plan, it’s about being able to innovate and iterate. Prioritising and working on the most important work first. Building in short feedback loops and taking on board feedback.
Why is ‘being agile’ important?
Because as the market changes, and users expectations change, companies that can not take onboard feedback and iterate their products and services loose out. This is also true when it comes to companies themselves in terms of what they offer their staff, less people now go to work just for the money, people want more job satisfaction, empowering staff to make decisions and cutting bureaucracy are not only ways to cut costs, but also increase the value to both your users, your stakeholders and your staff.
Resources to help:
Scrum.org have a decent blog on Agile Leaders which can be found here
For Leaders in the Public Sector, the Digital Academy has an Agile for Leaders course, details of which can be found here
The Centre for Agile Leadership has a blog on business agility here (and for those in the US they run courses)
And the Agile Business Consortium have a white-paper describing the role of culture and leadership within Agile which can be found here
One of the key reasons I joined @Difrent was their commitment to #TechForGood. In my experience #TechForGood is one of those phrases that gets batted around, as such I was very keen when I started to understand what that phrase meant to Difrent and if it really meant anything at all!
Much to my delight, I found that it was not just a meaningless motto for the company, but a value we as a company use every day. Be that the hoodies all staff are given (made from sustainably used cotton) to the work we do and the clients we will work with.
As such, when the opportunity to volunteer and or attend the #OneTeamGov#OneGreenGov appeared, it was obvious that at least one person from Difrent would be headed there.
OneGreenGov was a one-day event held in multiple locations around the world for those working in and with the public sector to discuss ways to combat climate change. With events happening in London, Wolverhampton, Helsinki in Finland and Canada.
On the day itself, there were a lot of fascinating conversations, ranging from some more scientific presentations on the effects of climate change on both geography and people’s health to sessions on how people can make a personal difference to climate change and even how Wikipedia can help the climate change battle.
You can see some of the conversations that happened on the day here. Throughout the day there was chat about the Trees for Life page set up at #UKGovCamp a week earlier and a discussion of what other initiatives could be set up to help the climate.
One of the things I learned from the event was the importance of reviewing your data regularly and removing out of date data, this is because the transmission of data via the internet can be very polluting, contributing to between 2-4% of our greenhouse gas emissions, there’s a Defra blog here about ways to try and reduce your digital carbon footprint.
Some of the conversations were happening in the room, some happened with the help of technology to cut down on the carbon footprint! As well as there being great conversations happening in the physical (and virtual) room, the sharing of ideas didn’t stop once the event was over.
In terms of the event itself, all the plates and cups used were biodegradable and all the food leftover was donated, so that nothing went to waste, which was lovely to see.
The whole day was full of energy and passion and it was fantastic to see so many people committed to making a difference and let’s just hope that we will see that difference continue in the days and weeks going forward.
No, don’t worry, I’ve not passed on and started speaking from beyond the grave; but given I’m now 3 months into my role at Difrent I thought it might be worth reflecting on how I’ve found things on the other side of the commercial table so to speak.
In the first 3 months I’ve worked with our teams, been in multiple contract meetings, client meetings, negotiations, done my first ever bid presentation and helped win my first piece of work for the organisation.
In the 15 years I spent in the public sector I have done my fair share of time working alongside procurement, drafting Pre-Qualification Questionnaires and Invitation to Tenders as part of a commercial team, or assessing bid responses and pitch’s as a programme lead. But if I’m honest in all that time I never considered the work that suppliers put into their Tender responses; the effort different commercial frameworks might require nor how companies pick and choose which work to bid for.
It’s been fascinating within the Difrent SLT talking about the kind of work we want to be bidding for, assessing what work aligned with our #TechForGood goals and values. It’s also really been reassuring to be involved in conversations where we have decided not to bid on work that doesn’t align with the company values.
One of the things I’ve quickly had to get my head around is the complexities of the Digital Marketplace and the ins and outs of the different commercial frameworks, be that G-Cloud, DoS or PSR. If I’m honest I’d never really got my head around the pros and cons of the different frameworks before taking this role, it was always one of those things I simply had to approve before.
While I have previously managed projects and programmes, and managed the suppliers working with us to deliver the work; it was equally never a thing I massively had to dwell on, beyond the question of ‘are they delivering what we need or not?’
In the last three months I’ve really gotten to understand the amount of work that has to be put in to make sure they answer to that question is ‘yes’.
One of the trickiest aspects to that relationship is making sure as a partner we are providing the right amount of rigour, challenge and reassurance so that our clients feel assured that we are doing the right things in the right way to deliver the outcomes they are looking for. Balancing the need to challenge and ask why to ensure the work we are doing is right, with the need to keep the client happy, engaged and onside. Not the easiest thing to do, but definitely vitally important in order to ensure value is actually delivered.
As a supplier I now realise how tricky it is to walk the tightrope of helping the client deliver the right thing, when this might mean a scope change that means more time or people (ie. more money) vs. wanting to ensure you deliver on time and within budget.
As a Product Person, I have always spoken about the importance of prioritisation and focusing on the problem the organisation was trying to solve. I used to find it incredibly frustration trying to get suppliers to understand and deliver what we needed, not just doing the work, but helping us do the work right. I was involved in multiple conversations across government about good suppliers vs. bad. Those that actually challenged us to do the right thing, and those that just delivered ‘what it said on the tin’ without helping check the label on the tin was right.
Now working on the other side of the table, I am doubly as determined to make sure we are delivering both the challenge and the outcomes our clients are looking for, to help deliver truly meaningful products and services and add real value to our clients and their users.
Yesterday Dominic Cummings, the PM’s senior aid, wrote in his blog about the need for number 10 to hire assorted super talented weirdos, unusual software developers, fantastic communicators and great project mangers (amongst other things).
This clarion call for change in the public sector followed up from his previous statements about the need for change in the civil service. Whether you agree with his politics or not, or even agree 100% with his message about the civil service; many of his points do ring true; and the need for a radical reform in the culture, methods and leadership of the civil service has been the focus behind #OneTeamGov for years now.
Having worked in the public sector for 15 years I can recognise that Mr Cummings is right when he says that the civil service is full of “people that care, they try hard” and that, at least in the start of my career it very much felt like “The people who are promoted tend to be the people who protect the system and don’t rock the boat.”
However, I don’t think that is 100% true anymore, certainly not in some areas. The growth of Digital within government departments has certainly led to more of the ‘weirdos’ Mr Cummings mentions finding homes (at least temporarily) within Digital, and more of the radical thinkers and champions for change getting promoted and having successful careers.
However, in the last 18 months, many of my peers have, like myself, left the civil service and moved agency side into the private sector; so why is that? Is it because, as Mr Cummings states The Public sector “ruthlessly weeds out people who are dissenters, who are maverick and who have a different point of view.”
There certainly seems to be a ‘ceiling’, at which point all the change agitators and ‘new wave’ of civil service leaders leave. These people tend to reach Deputy Director and then, as I did, decided that it’s time to look outside the civil service for their next role.
However when you look around, none of us have gone very far, few have been lost to the likes of Apple; Vodaphone or HSBC. Instead we’ve all moved to the likes of Difrent, FutureGov or ThoughtWorks. For me this shows that these people still care passionately about the public sector and what it is trying to deliver, but that the red tape and restraints that bound us in the civil service were becoming too much.
For myself, Difrent gives me the chance to work somewhere that still allows me to make a valuable different, to work on the problems that effect society and to deliver change at scale and pace (which was hard to do within the public sector). Everyone I’ve spoken to, who has made similar moves, says similar; but we all agree we would return to the Civil Service, and indeed many like myself are planning to, but for now they needed a change and a change to truly deliver.
I personally don’t think this is a bad thing, gaining experience outside of the civil service can help us all grow, open us up to new ideas and ways of working, help us to become better leaders. However, the number of people who have made this move this year is interesting; especially on the back of the #OneTeamGov conversations.
While Mr Cummings states that “People in SW1 talk a lot about ‘diversity’ but they rarely mean ‘true cognitive diversity’. They are usually babbling about ‘gender identity diversity blah blah’.” Personally, I believe that it is different life experiences that bring different perspectives; however I do whole heartedly agree with Mr Cummings when he calls for “genuine cognitive diversity” within the public sector.
I think this is especially needed within the Senior Civil Service. As Kit Collingwood wrote a few years ago regarding the need for Civil Servants to become experts on empathy “we must be able to understand and accurately predict how policy will affect people’s behaviour. We must be able to understand other humans’ motivation to change, to walk in their shoes.”
Making decisions on homelessness and poverty is very hard when no one in the team or the leadership has ever had to make their limited food supply feed a family for over a week. We also need to be able to understand the links between poverty, health and crime. There are so many different factors at play when trying to write a policy on reducing knife prevention, that if you have a policy team who all look and sound alike, you will never be able to understand or deliver the changes society needs.
The Civil Service has recognised for years that it has struggled with recruiting a diverse workforce, and looking at how it recruits and the messages it is putting out there, as well as the culture that potentially puts candidates with some back grounds off is definitely key. Even within Digital, recruitment could still feel siloed and closed off to some people. I’ve blogged before about problems with role names and job descriptions putting off people who could very likely do the job just because they didn’t 100% match with the job description or found the process to apply off putting. The problem is we often make assumptions about the kind of people we are looking to hire that put off people we may never have considered.
Mr Cummings states that “I don’t really know what I’m looking for but I want people around No10 to be on the lookout for such people.” For me this open approach (wether you agree with the actual method or not) seems like a good way to try and reach the ‘cognitive diversity’ we need within the Public Sector to deliver the radical change we need.
I believe a lot of the people Mr Cummings is looking for are around; either already within the public sector, working alongside it, or trying to get inside but struggling to find their way in.
I think we do need to think outside the box when it comes to recruitment, however it’s not just about recruiting the right people. We need to change the culture within the Public Sector to take on the lessons we have learned within Digital about User Centric design and the positive impact of multidisciplinary teams and reflect on how we can bring ‘cognitive diversity’ into the whole of the public sector. It requires a culture that invests in those people, their development and that allows them to successfully deliver. To change the system, you have to build a culture that enables the system to change.
This year has been a year of big change for me; I started a new job, left the public sector, moved cities, moved in with my partner, bought a new house, and most importantly, we got a dog.
As a Pagan, I celebrate Yule and the Winter Solstice; At the Winter Solstice we reach the longest night of the year. Darkness has reached its peak; and with the end of the longest night we celebrate the return of the Sun, the return of light, hope and promise.
As the year comes to an end I thought it would be worth reflecting on the year that is coming to a close, what I have learnt from it, things I’m still working on and taking forward into the year to come.
This year has been an interesting one, full of frustration and challenge; but also opportunities and excitement. I’ve always talked about the importance of finding your tribe, of being true to be yourself and being able to bring your whole self to work. For most of this year , if I’m honest, I was in a role that was not a good fit for me and I had never felt more cut off from my tribe. It taught me a lot.
What I have learnt:
What good leadership looks like
Reflecting on my time at the CQC, the fantastic opportunities that made me want to join the organisation when I was first offered the role, and the disappointment and frustration I felt in the last 6 months of the role after a change of line management left me being excluded and ignored. While CQC was a good fit for me at the start, a OneTeamGov event earlier this year on Leadership made me realise the impact a good (or bad) leader can have on an organisations culture.
The opportunities the organisation were facing were (and still are) real, but some of the recent hires brought in more recently made me realise that perhaps its readiness to embrace change at pace was not as real.
The difference within Difrent has been almost breath taking. From day one I’ve been empowered to get on and do things, with full support from my manager (the wonderful Rach) who has reminded me that there are good leaders out there fully capable of caring about their people.
By the time I left CQC’s culture, and its ways of working, were no longer right for me, it felt more insular and less a part of the Digital movement. I felt more cut off from my tribe than ever before, it was a lonely feeling. I think something I have learned in the last year, you can not change everything on your own; nor will you always fit in everywhere; someplace’s are just not right for you (which doesn’t necessarily make them bad, but bad for you), sometimes you need to make a change. But note, even when you can’t see it, change is happening. You are not alone.
Why the right culture matters
My frustrations with the culture in CQC, along with some advice from my mentor made me make a move outside of the public sector for the first time in my career. It’s something I thought long and hard about, as frustrated as I was at the CQC I didn’t want to just leave for any old role. The CQC made me realise I needed to find the right role, at the right organisation, with the right culture.
The senior leadership within Difrent talk constantly about our values, but it’s not just talk, it’s obvious everyone truly want to improve things together. Two months into the role, the suggestion we run a retro for the leadership team was met with open arms not disdain; everyone bought into the session and it felt very positive.
That’s not to say everything is perfect, it’s obvious that moving from ‘start up’ to ‘scale up’ means the culture has to adapt and change as well. But one thing I have learnt in the last year is good leaders don’t shy away from that challenge, they welcome it and talk about it in the open. That good leaders don’t just see ‘culture’ as a token word or a by product, but as a thing to invest in.
You need to believe in yourself
I am an optimist, which made me ignore the initial doubts and worries I felt at the CQC; made me assume the problems I was facing were unintentional, that things would improve, and my desire to make things better things and to protect my team meant I pushed aside my doubts and tried hard to work things out. It took me a long time to realise the cumulative effect that was having on my own confidence.
Two months into my role at Difrent and I think it was absolutely the right move for me. After months of being disempowered and isolated by a manager who did not welcome challenge and for whom Digital was only about the technology, not the people; my role in Difrent has been a reminder that people matter, that I matter, and I am good at what I do.
Within days of starting at Difrent I dived straight into contract negotiations and client engagement; talked to teams about what support they might need to enable them to deliver and within my first 60 days I lead on delivering my first (successful) pitch for business. I felt like I’ve achieved and delivered more in my last 2 months than the previous six months.
The importance of finding your own voice
My year has been a good one blog wise, many of my blogs were born from the frustrations I was feeling at the CQC, but also it felt like I finally hit my stride and found my tone of voice. While this blog has never been about ‘getting hits’ and more about sharing information, it’s been a very pleasant surprise to see how well they’ve done, the blogs about Thomas Cook and the Parliamentary Petitions site in particular seemed to strike a cord with people.
My goals for the year ahead:
My aim for next year is to keep building on the blog, but too also to try and get back into the swing of speaking at events. A year ago I was speaking at events fairly regularly, but the CQC hit my confidence more than I would like to admit. It’s hard to stand up in front of a crowd and feel like you have things to say when your manager regularly ‘accidentally’ leaves you out of the conversations your male colleagues seem to be invited to.
Since moving to Difrent I’ve already thrown my hat in the ring to speak at two conferences, and my aim is to try and have done 6 speaking events by the end of 2020. We shall see how that goes!
While politics at the moment is worrying, and has led some to question whether there is still empathy in the world, I’m approaching the next year full of hope. News like that of Twitter users recently joined together to develop a free Food Bank app highlight why the #TechForGood movement is so important and why I’m so proud to work for somewhere that is doing what it can to make a difference.
By this time next year I want to be able to stand up and talk about the things I have personally delivered. Up until now, while I’ve worked on amazing projects, very few of them I’ve been able to see through to delivery (either because of funding cuts, reprioritisation of projects, or promotions meaning I’ve move on before I got to see things through) the main reason for me taking the role at Difrent was to change that, to truly be able to deliver things that matter.
Both personally and professionally I’m doing what I can to add value, and learn from mistakes in the past to ensure the future is better.
One of the most universal truths is that if you don’t talk about what you are doing, how will people know?
Everyone leads busy lives, we live in our own bubbles, and while we do generally try and be good humans and notice and recognise other people doing good things, it’s not always that easy to do.
That’s why I personally find things like twitter, reading Blogs and attending networking events or conferences useful, they give me a change to see what else is happening out there, who is doing what good things; they are opportunities to connect and share.
However that is predicated on the basic foundation of having things to share. One of the things I’ve found, upon joining Difrent, is that we are not that great on sharing the great stuff we are doing. Which is a shame, as we are doing some really great stuff!
Thankfully Rach and I are on the same page (perhaps unsurprisingly given we are both rather massive extraverts) so we’ve been having some good conversations within the SLT on what more we can do to develop better content and support our teams and people to be more confident in sharing what they are doing.
Last week we had @RachelleMoose from Strange Digital come in and deliver a two day workshop for us on content strategy, focusing on how we could use video better to tell Difrent’s story.
While I’ve always found the projects and culture video’s we developed at DWP Digital to be great, I’d never actually researched or seen any of the stats on why video is a good medium for sharing content from a business point of view. I knew I liked them, but I didn’t understand why there were useful! But the workshop taught me things like: videos generate 135% more traffic to a site than static content alone; and that 92% of people who watch a video on mobile devices, go on to share that video with others.
It was especially interesting from an accessibility angle, to consider how we make sure our content as accessible to everyone, not simply in terms of sticking subtitles on all our videos, but things like understanding that audio needs to be understood and edited to ensure it doesn’t clash with anyone speaking and how different formats work etc. For example, more than 85% of social videos are watched without sound, which helps explain why Closed Captions and Titles on videos are important.
I found the workshop a really good session to do as a Senior Leadership team, it really made us think about what messages we wanted to put out there, what we felt was the right way to tell our story and who we are as a company.
We also did some competitor analysis to see what other content is out there; what messages resonated with us, and what didn’t; as well as discussing the formats we liked as a group etc. I got to put post it notes on a wall, which is always the sign of a good day for me.
What I found especially beneficial, being new to the company, was asking some of our staff their thoughts on our culture and what they would like to see in the videos. Within Difrent we pride ourselves on encouraging and enabling everyone to be themselves and able to bring their whole selves to work; hearing from people how they felt Difrent embodies that was really encouraging.
I’m really looking forward to seeing the output of the videos once they are made, and really think they will help us within Difrent work in the open better, talk about our amazing people and show the great work we are delivering.
Last month I started with Difrent, my first job in the Private sector after 15 years in the public sector, which felt very much like a change of scenery and a new start, whilst also being a familiar continuation of what I know.
So at the end of my first month I thought it would be worth reflecting on what I’ve learnt and done so far.
First things first, still lots of meetings! In the last month I’ve been in lots of conversations and meetings about our contracts (which is one of the reasons I took this job, to get that experience, so I’m not complaining!) but what I hadn’t realised, from the public sector client side point of view, is the amount of effort and time that is put into contract bids etc. It’s been fascinating to see and experience the hustle and bustle of getting a bid together, ensuring you have the team you’ll need, getting your evidence together, to then just wait and hear whether you have got the work. It’s like constantly doing job applications!
Secondly, the people, lots of the folks at Difrent I had come across (generally on Twitter) before, so I knew of them but hadn’t had the chance to work with them. Part of my role at Difrent is to ensure that we have the agreed standards and principles for our ways of working to ensure we can deliver the right things in the right way for our clients. I’ve spent the last few weeks getting to know the people within Difrent, and the clients we are working with.
What’s been interesting for me has been the culture that comes with a company moving from start up to scale up. Within the Public Sector I’ve only ever worked in organisations that are 4.5K plus. Working somewhere with under 100 people is very different. The infrastructure and organisational governance that comes with working for a huge well established organisation isn’t necessarily there, but nor is that necessarily a bad thing!
In the old work, conversations like office locations, or what our Target Operating model should be would take months if not years; with unions consulted, multiple consultations with staff forums and people groups etc. Within Difrent it’s much easier to have conversations with all our staff, be that in TownHalls or just on our Slack channel. The conversations themselves are similar, but how we have them, who gets to be involved, and how quickly we can get things done is definitely different.
The work, so far most of the team’s I’ve been working with have been working on projects within the Public sector, so the environment for me has been very familiar. The other thing that’s familiar is the conversations we are having, about KPI’s and measures. The need to understand what we are trying to deliver and ensure that we can measure our success in delivering it, not just be ticking off story points, but ensuring we are delivering value for both our customers and their users is key.
For the next few months my focus will be on working with our clients helping them shape and deliver the vision’s they have set. Measuring the value we are adding to them, and the value the products and services we are delivering are adding value to their users. Ensuring we have the right resources for our teams based on what the needs of our clients are, and that we as an organisation are supporting our people the best way we can.
These things have always been important to me, and always been key parts of my roles. So it seems whether it’s the public sector or private sector, French Critic Alphonse Karr was right in some ways….
And you know what, I am glad about that. If everything were radically different I might be worried that either the public or private sector was doing it wrong. But the fact is the common problems are very similar, it’s just how we approach solving them that might be different; and having a different perspective to how you solve problems is important, as it means you’re considering all the options there are and hopefully avoiding making the same mistakes over and over.