Weeknote w/c 20 May: thinking about ‘Smart Cities’ and counting votes (but not at the same time!)

A nicely varied week which wrapped up with a bank holiday weekend!

Thinking about ‘Smart Cities’

There’s been a lot of hype about ‘Smart Cities’ for many years now. It’s obvious that developments in technology and data are already having a big impact on the places we live and how we interact with services and one another (for example, I now take it for granted that I can always have instant access to real time updates on train and bus arrivals when planning my journeys). I find it interesting to mull over whether the future is likely to be utopian or really will take us towards a Matrix / Minority Report type world and also how much influence we (civic society) can have on how things develop.

I read an interesting research paper looking at the Sidewalk Toronto initiative over the weekend and that prompted me to pop a few thoughts into a blog post here: https://bytherye.com/2019/05/28/the-smart-city-is-as-much-a-political-challenge-as-it-is-a-technology-challenge/.


Sunday was spent at the Britannia Leisure Centre in Shoreditch Park with lots of other colleagues, counting the votes from Thursday’s elections for the European Parliament. This was the third time that I’d donned my bright yellow count supervisor t-shirt and I was pleased that the table I was responsible for was among the first to complete our count. Having finished second from last when I did my first count in 2017, I’d like to think that this was great progress and inspiring leadership on my part rather than luck of the draw…!


Other highlights from last week were:

  • We had a productive session catching up on the various strands of work that will help us move away from eDOCS (which includes but isn’t limited to broadening our use of Google Drive). We agreed a focused set of specific actions which we will check in on in a couple of weeks’ time.
  • Henry, Ollie and I met with colleagues from the Hackney Learning Trust ICT team to catch up on their progress setting up a pilot of G Suite. I’m pleased with the progress we’ve made in collaborating together and we identified some things we can do to help them move this forward.
  • We had our quarterly Information Governance Group meeting on Wednesday. I was particularly pleased to see the progress that has been made improving the Council’s performance in responding to Freedom Of Information requests. Our team have worked incredibly hard to support colleagues across the Council’s services to get their responses sent out quickly and while we’re not quite there yet it was great to see very positive progress over the last quarter – well done Katharine, Adam, Noelle and O’Cynthia!
  • It was also brilliant to have started the week with news from Sarah and Katharine that Hackney’s work with mysociety to develop a new digital service for Freedom Of Information requests had been awarded Innovation of the Year at this year’s Information and Records Management Society awards. Well done team!
  • Philippa, Richard and I had a very useful conversation with colleagues in Housing Services looking at how we can work together as part of seeing how the Spacebank project might help with booking of space in Hackney’s Community Halls. We’ve agreed to use a Discovery phase to help us better understand the opportunities and challenges before we develop more detailed proposals for what we do next.
  • I had my regular catch up with representatives from the Council’s Unions. I always find this a valuable way to check in on feedback from staff across the Council and get their thoughts on the work we’re doing.
  • Lucy and I joined colleagues from Adults’ Services at the ‘IT Enabler Board’ at the Homerton hospital. This brings together people from across health and social care in the City and Hackney area, and the discussion included a really useful conversation about next steps with the work we’ve been doing to look at how we might improve access to information about health, care and wellbeing services across the area.
  • And I wrapped up my week with a catch up with Ajman, the Director of Housing. I make sure that I have regular catch ups with senior colleagues in other services so that I can check in on their priorities and make sure that we’re focusing on the right things. I was very encouraged to hear the importance he is giving to the digital work our teams are doing together to support the transformation of housing services and we’ve agreed that we will take some time together to get closer to the details of some aspects of that.

Something I’m learning

One of the follow ups from our recent finance review is working with colleagues in Finance to set up the investment plans for the year ahead. As we move towards greater use of cloud services and supporting change through making the most of the technologies we’re putting in place this doesn’t fit the historic capital funding model as easily as was the case in the past. The Finance teams are being supportive in helping to find answers to this but I’m having to make sure that I explain stuff that feels obvious to me in layperson’s terms so that we can figure out the best solution together.

The ‘Smart City’ is as much a political challenge as it is a technology challenge

I’ve read a few pieces covering the Sidewalk Toronto initiative, which raises interesting issues about the way that authorities should engage with and try to shape ‘Smart City’ developments. I saw a link to a draft research paper yesterday which looks at the relationship between Sidewalk Labs and the City of Toronto and I thought it was an interesting read which prompted a few thoughts that I’ve put together in this blog post (although I don’t claim to know enough about the Toronto project to make any specific comments on that). The original is here: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3390610 and this version has my scribbled notes on the sections that I thought were especially noteworthy: https://drive.google.com/file/d/1wIUZiErfj2OhfmyakuM-ZOVLqwTLzU8-/view.

I’ve found myself in some fairly depressing conversations about ‘Smart Cities’ over the years. Some of those have involved bold statements about the importance of becoming a Smart City but with scant detail about what that actually meant or why it would be a good thing. Others have been alarmist declarations of the end of days whenever a new form of technology is proposed. (For the avoidance of doubt, none of those have been with my current employer!)

And whenever there’s a new trend in town there are also a healthy number of sales people offering all manner of different flavours of snake oil. AI, robots and ‘smart’ this and that clutter up my mailbox on a daily basis and are one of the reasons I’m pretty selective about which conferences and events I make time to attend.

But underneath it all there is some important stuff that we need to get to grips with. As the technology becomes ever more sophisticated, we need to find ways to make sure that we communicate the issues in ways that help our colleagues and political leaders understand why these need their attention and the levers that they have at their disposal to influence how things evolve. There might actually be some parallels with the ways that technology has changed the nature of public discourse through social media, and this could help underline why it’s so important that we are actively thinking about how technology and powerful uses of data will impact on our civic spaces and society.

I feel some way from having a formed view on what the answers are, but here are a few of the things that I’m trying to think through as I work to make sense of the ‘Smart City’.

The way the ‘Smart City’ evolves will have a big impact on where power lies in society

In a civic realm where huge volumes of data are collected and used to direct services and people, whoever has control of the way that the data is used will have enormous influence over people’s lives. Combined with increasingly complex technology it will become dramatically harder for authorities to apply regulation to manage the effects of this.

This might be comparable to regulation of news coverage where historically rules could be applied to the media with some prospect of them being (at least partly) effective. The personalisation of news feeds and distribution through massively complex global social media networks has blown this apart and governments around the world are grappling with the difficulty of responding to that. In a ‘Smart City’ where decisions are being made in real time based on data gathered from large numbers of sensors, how will democratic decision making keep up?

There are big questions we need to be asking about the implications for ‘Smart City’ developments, including:

  • What impact will these have on accountability?
  • Who are the winners and losers likely to be?
  • Is that compatible with our values?
  • And what we should be doing to influence the outcomes for society as a whole?

We also need to understand the relative power of the platform vs the apps which grow on the platform and the implications for the wider economy and opportunities for growth

I first became aware of Facebook when family members were trying to encourage me to sign up to join them in playing Farmville (I resisted the temptation, although I did join Facebook later on but have pretty much given up on it now). A fairly innocuous game that had been built on top of Facebook’s platform became an important driver in the huge growth of Facebook membership, powering their development into the behemoth we see today. Farmville, however, is pretty much a distant memory for most.

In a ‘Smart City’ context I think that the underlying platform of data sources and connections to that data is far and away the most important aspect from a societal perspective. It’s at this level that technical and political decisions will come together to determine what constraints of privacy will be acceptable, and the ability to turn data feeds off and on will also give huge influence over the sorts of economic growth that can happen through the development of ‘apps’ (software, businesses and communities) built on top of that.

How would we feel if a private provider can turn off access to other companies who are providing useful services that citizens have come to rely on? And what are the risks that data gathered through smart sensors will be used for new purposes which aren’t compatible with our original intentions? We need to be clear about who will control ‘Smart City’ platforms and how society can influence their development.

Our goal should be to find a way to balance democratic accountability with innovation and growth. But there are also real risks of excessive government control or monopoly privatisation that will be tricky to navigate, especially given the complexity of the technologies involved.

Trust and transparency will be fundamental

It can be tricky ‘working in the open’ when issues are contentious and spark strong views. And given the commercial opportunities from investing in ‘Smart City’ technology I don’t find it very surprising that the Sidewalk Toronto work hasn’t been entirely transparent. But it’s also evident that this has had an effect in terms of the trust (or lack of it) that people have in the project.

Given the issues that this sort of initiative raises, I think there’s a real need to design in transparency and make the space for engagement and debate. But that doesn’t mean that it will always be an easy discussion to have, especially given the big differences in position between technology evangelists and people who are nervous about excessive surveillance and control of civic space. So this is where we need to help political leaders get a strong handle on the issues involved so that they can work with the citizens they represent to develop a vision for the type of future place they want and consider how ‘Smart City’ developments can help contribute towards that.

This is a big change in the nature of digital leadership. From a focus on technology choices, efficiency, costs and channel shift, to a much more profound focus on how society works and who it works for.

Being ‘leading’ is not a thing if we don’t know where we’re going

Given the amount of hype surrounding ‘Smart City’ opportunities at the moment, it’s not surprising that there’s a desire to be seen to be at the leading edge and not be left behind. But sifting through the sales pitches and exciting proposals to find the ones that will matter most, and most importantly the ones which will be most valuable in learning about the right way forward, requires careful thought.

How do we avoid ‘analysis paralysis’, where caution about emerging technology becomes a barrier to any progress, while also making sure that we don’t create costly mistakes that we live to regret in future?

This is definitely the realm of the uncertain where Agile approaches can help us to explore new ideas in a controlled way so that we also mitigate risks.

Nothing in life is free and we need to understand the value of the cards we hold

The rapid development of technology makes it a high risk for public sector investment, especially in times of austerity. Big technology companies have deep pockets, deep expertise and are highly incentivised to invest in research and development for future products. But when that product is a city we need to be clear that their motives might not be totally altruistic…

We are not powerless in this. The foundation of the ‘Smart City’ will be access to gather and use lots and lots of data. As a society we can choose what we make possible, the constraints we put on how data is used and the degree to which we can influence future development. It’s vital that we (civic society) don’t give up control of the gathering and access to data without understanding the consequences. Even if there’s a shiny ‘free’ pilot project being offered to tempt us.

We also need to understand how to guard against a slippery slope. Providing the minimum access to data to accomplish a goal can reduce the risk of future developments going unchecked. You can see this in the scandals that have engulfed Facebook where legitimate developer access to gather data was exploited for purposes that were very different from what was originally intended.

Society might well depend on some friction in the process to guard against negative outcomes

A final thought from the paper was that a completely frictionless world might not actually be a good thing. A key feature of civic society is compromise and trade offs between individuals, and a seamlessly efficient city driven by data and consumer demand without any checks and balances could well result in unintended consequences that we would want to avoid.

Is it good for our city if the popularity of certain services made possible through ‘Smart’ developments means that other services that people still rely on become uneconomically viable?

This further underlines the importance of making sure that the way that ‘Smart City’ developments evolve isn’t simply a technocratic exercise in software, hardware and data.

Weeknote w/c 13 May: money, money, money

My main area of focus this week was the finance review that we’ve been planning. I was pleased that our preparation helped us use the time we’d set aside really productively.

Finance review

I’ve mentioned in previous notes that we’d identified the need to do a deep dive into our finances. Changes in our team and the finance team have meant that there are a number of aspects of our budget management which aren’t as clear and well understood as they need to be. Getting this right will be critical to living within our means and getting best value from the money that we’re responsible for.

I think that the most important part of this was setting aside a decent amount of time for the work, clearing our diaries for two full days so that we could concentrate and minimise distractions. It was also really helpful to have Cate facilitating the work. I think our colleague from finance was a little surprised to find us unpicking budgets using Post-It notes, Sharpies and large sheets of brown paper, but it was a really useful way to bring out the key priorities that need to be worked on and helped us avoid getting lost in the rows and columns of spreadsheets.

The work helped us identify a number of things that we will do so that we can be confident in our financial position. These include:

  • A number of immediate actions such as tidying up cost codes and approver information, realigning some of our budgets so that money is in the correct place and making sure that we are clear about recharges to avoid faff at the end of the year.
  • Work to address key areas of financial pressure that we have identified, including the savings we are committed to delivering this year. This links to our investment planning and it’s important that we align those so that we know we’re investing in the right things.
  • Things we can do to make sure that our financial monitoring through the year is giving us an accurate picture of the forecast outturn at year end – in particular managing recharges effectively and tracking the delivery of the projects that will help us reduce cost pressures (eg our web platform changes which we expect to deliver savings).
  • There are also some areas where we will be doing more detailed follow up work to identify ways that we can make sure that our service is financially sustainable in the longer term. This includes planning for future skills needs and looking at how we can drive forward our end-user computing strategy to reduce the costs of expensive legacy technologies.

Cate and I will talk through this in more detail at the HackIT strategy stand up on Thurs 30 May.

Our challenge now will be to make sure that we don’t lose focus on the follow up actions that we identified. I’m confident that most of them can be completed quickly, and there are also a few which we’re planning to build into the agenda for our DMT away day on 12 June so that we get those done while it’s still early in the financial year.

Working in partnership

One of the most important aspects of our work is developing effective partnerships with colleagues in other services, working together to meet our users’ needs and expectations. You might have heard me saying that we shouldn’t use terms like ‘the business’ when we’re referring to colleagues in other services and I decided to dust down a half written draft blog post to explain in a bit more detail why I think that this and other aspects of how we interact with our colleagues are important. You can find that here: https://bytherye.com/2019/05/21/lets-talk-about-tech-getting-it-and-digital-out-of-the-basement/.

Other highlights from last week were:

  • A great conversation with another Director who really got the potential for the work we’re doing to refresh end-user devices as an opportunity to rethink the way that their teams work.
  • Working with Cate to look through the findings from the survey that we carried out recently to get people’s feedback about the ideas we’re developing for future provision of mobile phones. We got nearly 600 responses, which was great! The feedback has helped to clarify the things we’ll need to consider as part of a final recommendation to Hackney Management Team, and we’re hoping to firm that up over the next few weeks. (I also discovered that WhatsApp Business let’s users send and receive WhatsApp messages using a work number, even on their personal phones – very neat! https://www.whatsapp.com/business/)
  • We saw some great examples of the benefits of working in the open. Sharing in this way is hugely positive – partly because we can help the wider local government sector to deliver better services for citizens across the country by sharing our work, and also because the feedback we receive can help us improve services for Hackney’s residents. The examples this week included:
    • a brilliant response to Soraya’s blog post on using GOV.UK Notify (https://blogs.hackney.gov.uk/hackit/gov-uk-notify-in-action), which got a lot of interest from colleagues at other councils
    • an interesting discussion with colleagues from the Scottish government’s cyber team, who visited us as a follow up to a presentation that Keith gave about our ‘web first’ approach to access and security
    • and a very positive set of responses to Amy and Tom’s sharing of the guidance that’s been developed to help users with using G Suite to collaborate internally and with external partners
  • I also had some very useful discussions with Matthew looking at how we might support the Member customer services board that is being set up, and with Lucy looking at the recommendations for moving forward with the Directory of Services work that we’ve been doing.

Something I’m learning

There are some times when I find myself in meetings because I feel that I ‘ought’ to be there but where the value of the time isn’t obvious to me. I need to think harder about how I make sure that I find the value where it’s there or prune my allocation of time to make sure that I’m getting the most out of each day.

Let’s talk about tech – getting IT and digital out of the basement

It’s hard to think of an area of life where technology and data haven’t been part of huge changes over the last 10 – 30 years. Well rehearsed examples of that include travel, shopping and banking, where ease of access to doing transactions online is just part of a fundamental change to business models and user experience that is reshaping the way that economies and societies work. Seemingly indomitable companies have vanished and new upstarts have risen up to take their place.

I find it concerning that in many organisations (in both public and private sectors) it is still too common to find technology and data discussed as if they are separate to ‘real work’, with IT teams * hidden well away from their colleagues and seen as ‘back office’ functions. It’s vital that our profession makes a shift from out of date customer / supplier type relationships towards working in real partnership.

That’s what we are working to do in the HackIT team. Our goal is to work closely with our colleagues in other services as equal partners, working together to deliver better outcomes for our borough’s residents and businesses.

Our ‘HackIT manifesto’ (http://hackit.org.uk/how-we-work/how-to-hackit) was created by the team and sets out the ways that we are doing this, with eleven principles that underpin our ways of working. It’s now a couple of years since we created that and lots of great new people have joined our team, so now’s a good time for us to refresh it and make sure that it is still working as a useful guide for the way we work.

With that in mind, I’ve been thinking through some of the ways that our interactions can impact on our relationships with our colleagues, and am keen to make sure that our updated ‘manifesto’ reflects some of that.

The language we use must make it clear that we are an integral part of achieving our organisation’s core mission

We need to be consistent in talking in a way that demonstrates that we have something valuable to contribute. Using terms like ‘the business’ or ‘customers’ when we’re referring to colleagues in other services is unhelpful, because it can suggest that we’re simply service providers who don’t have a role to play in helping to shape policies and decisions.

And we must guard against only focusing on our operational work and processes when we explain what we do, because these are simply means to an end not the end itself.

We also need to make sure that we explain concepts (whether that’s technical stuff or describing the way we deliver our work) in layperson’s terms so that colleagues can understand why these matter to their services and users. There’s a risk that people might assume that our work is ‘too techie’ for non-IT folk to understand and it’s up to us to show that isn’t the case.

We need to listen, learn and work together and share one another’s successes

Genuine transformation happens when we learn from our users to understand their needs, and when we combine other teams’ experience and knowledge with expertise in technology and data. No one individual will have the answer, but by working well together in effective multi-disciplinary teams we’re much more likely to be able to take big steps forward.

It’s also essential that the job titles on our name badges don’t distract us from the shared responsibility to deliver results. Whether it’s making a project happen, responding to an operational issue, managing our money and assets well or understanding what we need to do to protect the privacy and security of people’s data, if something is important it is all of our responsibility.

This is also true for the colleagues we are working with. Services don’t outsource their technology and transformation to us and we need to help them understand what we need from them to help deliver successful outcomes and we also need to support them in doing that. That includes taking the time to provide training and advice on roles like being a Product Owner as well as working with colleagues to help them fit in with the rhythm of delivery. But it also means having the confidence to highlight where engagement needs to improve so that we are genuinely delivering together, not just observing other people’s work.

And when we complete a piece of work it’s essential that we take the opportunity to reinforce the trust we want to build across teams by always being generous in the way that we celebrate the success. We mustn’t underestimate the impact of reminding people of the value their contribution as part of a team has made.

We need to be open to new possibilities

It is important that we respect the experience of the past but we also need to make sure that ‘we’ve always done it that way’ or ‘we tried X before and it didn’t work’ doesn’t become an excuse for failing to make the most of new opportunities. It’s surprising how often the impossible can become possible if we let it (especially if we can work together to think around the problems that might stand in the way), and letting ourselves consider flights of fancy from the opportunity presents itself can help make sure that we don’t unnecessarily self-limit ourselves.

But we also need to avoid tech fetishism

Cylindrical voice assistant A or B may well be very clever, but they aren’t silver bullets that will magically solve the challenges facing public services. Trying out new technologies and exploring how they might help our users is something that we should always make time for, but it’s equally important that ‘being innovative’ doesn’t become an end in itself. If we can’t explain why a new technology might be genuinely beneficial for users we probably shouldn’t be spending precious time playing with it. ‘Minimum Viable Product’ type approaches can be a really helpful way to test out new ideas while also minimising the risk of expensive mistakes.

Focus is very important

I find this one of the hardest things to do, and it’s always a struggle to avoid flitting from one thing to the next without seeing through the task in hand. I’m finding it really encouraging to see how using Agile delivery approaches can help to sharpen our focus and accelerate our pace.

Working in the open (eg sharing weeknotes with the team *and* making the time to read them! **) also helps avoid wasted effort as it makes it easy to keep up with the progress and decisions other colleagues are making, with much less faff than traditional project boards etc. It’s essential that we remember that these can help across all areas of our work, not just ‘digital’ projects.

And finally, a bit of pragmatism can be helpful too

As Matthew noted in his post about holding a great show and tell (https://blogs.hackney.gov.uk/hackit/holding-a-great-show-and-tell), there will be times where it makes sense to adapt our approach so that we are working in a way that makes sense for our users. So, whether that means changing the terminology we use, flexing our expectations of roles in a team so that colleagues are able to contribute effectively or looking for other ways that we can bring out the best from people and circumstances, it’s all good.

What really matters is that we are delivering for our users.


* I think that the distinction of ‘IT’ and ‘digital’ is artificial – but that’s a different blog post! https://bytherye.com/2017/10/07/a-digital-detente/

** I’m pretty unsympathetic if anyone says that it’s hard to make time to skim the weeknotes from across our team – they’re an easier read than traditional highlight reports and take significantly less time than a project board.

Weeknote w/c 6 May: thinking about the future workforce and agreeing the first LOTI priorities

A shorter week thanks to the bank holiday, but I don’t think the resulting weeknote is any shorter!

Workforce development

I joined an interesting discussion about Hackney’s workforce development strategy at the start of the week. This builds on lots of work that’s already been taking place, including:

  • The Council’s award winning apprenticeship programme
  • Our new recruitment site (https://recruitment.hackney.gov.uk), which is designed to help promote the opportunities that Hackney offers and will also save money on ‘microsites’ for supporting recruitment campaigns
  • The simpler ‘check in’ process for performance management that was introduced last autumn
  • Work to provide a rich set of learning and development opportunities
  • And new ways of working together, including growing use of ‘show and tells’ and online communities to share our work with colleagues

The Council’s ambition is to be the best place to work in local government and we discussed ways that we can continue our journey to achieve this. Ideas that I thought were especially important included:

  • Sustained commitment to broadening diversity (especially at senior levels) both through our recruitment and also by supporting our people to progress so that we are continuing to build a diverse workforce for the future which reflects the borough we serve
  • Encouraging curiosity and exploration of ways that technology, data and new ways of delivering services can help us to deliver excellent services for our residents
  • Continually looking for ways that we can showcase and role model the innovative and sector leading work that is happening across the Council to help inspire further progress and promote Hackney as a place to do great work

LOTI (the London Office for Technology & Innovation)

On Wednesday morning I caught up with the other members of the core group of 15 councils who have committed to working together to launch LOTI. This followed the workshop a few weeks ago where we looked at the governance arrangements (https://bytherye.com/2019/04/08/weeknote-20190408/). For this session we focused on the initial set of priorities that we will work on together.

I liked that we took an action oriented approach, identifying some things that we can crack on with right away ahead of the new LOTI team starting in post in the summer. These initial pieces of work will help lay the foundations for follow on work and build momentum.

One of these initial priorities we agreed is working together to grow the number of digital apprenticeships across the boroughs, building on the 20 digital apprenticeships we have at Hackney and related work that the other LOTI councils have been doing. We believe that by sharing our experience and helping managers and apprentices to work together across our boroughs we can make a big impact on digital skills, create new work opportunities and help to build the diversity of our teams. Cate and I have agreed to lead on this and we’re hoping to bring a working group together within the next month or so to agree our objectives and get things moving.

Other highlights from last week were:

  • Cate and I spent some time with finance colleagues to plan for the review of our finances that we’ll be doing this week. This is important to make sure that our budgets are well managed and that we are prioritising the right areas of work to respond to future financial risks and opportunities.
  • We had a really good Delivery DMT. The approach we introduced in January (https://bytherye.com/2019/01/15/weeknote-20190115/) to help us focus on key cross-cutting priorities seems to be working well and is helping us to think in a joined up ‘one team’ way. We noted some positive progress on areas of work that we had identifed as needing focus and agreed that for this month we will focus on:
    • refreshing our ‘HackIT manifesto’, including offering new members of our team the opportunity to help shape our service’s culture
    • completing the finance review
    • shaping the ‘digital support services’ work
    • work to refresh our strategic approach to recruitment to help us continue to hire great people into our team
    • working with colleagues in other services to set up a new cross-cutting Member customer services board to help drive forward the transformation of resident facing services across the Council
  • I joined an interesting meeting with another supplier where we discussed our views on the direction technology should be taking. We heard again that the supplier wants to move faster towards web and mobile computing, which aligns with our direction, but that many of their clients are asking for a much more traditional approach. How might we encourage more local authorities to push the technology market towards a modern approach?
  • And on Friday I joined the other members of the Council’s ‘GOLD’ team for a second training day where we had a (surprisingly engaging) session on the legal requirements for emergency management and did some scenario based thinking to test out our skills.

Something I’m learning

On Wednesday I learned that it’s possible to get a remarkable amount of stuff done using a watch as your only connected device (I chose to leave my phone at home because I was taking part in a run at the Olympic Park in the evening). Battery life was, however, a challenge… More on that here: https://bytherye.com/2019/05/08/the-future-is-here-it-just-doesnt-last-the-whole-day-yet/.

The future is here (it just doesn’t last the whole day yet)

It’s almost four years since I blogged about my initial experience of using my first Apple Watch (https://bytherye.com/2015/05/10/apple-watch-a-few-thoughts-after-my-first-week/).

At the time I could see that it had lots of potential, but ‘unless you’re a bit of a geek I’d probably recommend waiting a bit before leaping in.

Roll forward to today and I’ve just experimented with leaving my phone and iPad at home and using the Watch (now a Series 4 with mobile data, coupled with Bluetooth headphones for listening to audio) as my only connected device for the whole day. I decided to do this because I was taking part in a run this evening and wanted to minimise what I carried with me, but it also seemed like a good opportunity to see how far things have come since 2015.

It went pretty well. But I have spent a day with major battery anxiety!

The good stuff was that I could do loads of stuff without needing my phone, including:

  • Making and receiving phone calls, text messages, other instant messages (including Hangouts and WhatsApp) and emails
  • Listening to podcasts and music
  • Paying for food and my train fare
  • Checking my diary and travel times
  • Tracking my running time and counting down the kilometres until the finish line

It wasn’t as easy to use for the written communication as my phone is (and I got a sore arm if I wrote for too long!), but for keeping in touch and short messages it worked really well. The scribble feature that lets you doodle what you want to write is a major improvement from the initial ways to compose messages.

And for some of the things I needed to do (eg paying, listening to stuff and tracking activity) I find the Watch vastly superior to the phone because I can now carry one less thing.

The newer Watches are also much, much faster than the original one. So my reservations about that are happily a thing of the past.

The big draw back was battery life. Normally I comfortably get a couple of days between charges, but I hadn’t properly accounted for how much more quickly it would drain if I was on 4G all day rather than tethered to my phone. I started with a full charge and was in the mid-80% range by the time I started my first meeting. And I found that I needed to do some quite aggressive power management to last the day (including switching off data when I didn’t need it, using theatre mode to stop the screen waking up when I lifted my wrist and turning it off altogether for a couple of hours when I had a laptop to hand). It kept going until seconds after I’d made my last tap out at the station this evening * and then gave up the ghost. A close run thing!

Overall, I think I’m happy to revise my original view and strongly recommend the Watch, even if you’re not as much of a gadget enthusiast as I am. ** But I don’t think it’s wise to give up the smartphone just yet, unless you’re fairly comfortable going off grid and / or are happy to carry a charger for top ups when needed. That’ll change though and I reckon that it seems increasingly likely that we’ll find ourselves using smartphones a bit less frequently and wearable computing more often in the years ahead. Food for thought…

* This is important because Transport for London don’t automatically match the card number used for Apple Pay on a phone or Watch with the number of the physical debit card that I had with me as a contingency (the card numbers are different even though they link to the same account). So if I had had to tap out with the debit card instead of the Watch I’d have been charged much more than the correct fare for my journey.

** And yes, there are other brands of wearable. I’ve not tried those but I spot more and more people sporting them so I’m confident that there’s something for most tastes now.

Weeknote w/c 27 April: more focus on how we work, both now and in the future

This was a good week. We’ve made progress with some important pieces of work and my Weeknotes have successfully joined my (less frequently updated) blog in a shiny new home.

How to HackIT

On Wednesday a group of us got together for a follow up session on the ‘How to HackIT’ guides we’re developing. This worked very well and we broke out into pairs to peer review one another’s work and by the end of 90 minutes we had published five new guides online. You can find them here: http://hackit.org.uk/how-we-work/how-to-hackit.

This growing collection of guides is designed to provide a light touch set of protocols we can follow across our teams to help us with the consistency and rhythm of our work, in line with our governance principles. By making the guides open on the web we can also help other teams elsewhere (and get feedback which will help us improve), help new starters understand how we work before they join our team and also help suppliers who will be working with us make sure that they’re prepared.

We’ve agreed five more guides that we will prioritise and are going to try to have those ready to publish in two to three weeks’ time.


An important part of developing our service is looking at our system management practices to make sure that we are developing and supporting new digital services well. This is an important challenge and as well as introducing new ways of working it involves technologies which are relatively new to us and will also require new skills. It touches on all aspects of our work, from designing, developing and delivering change through to running and supporting our systems and services.

On Monday afternoon Peter and I visited the Ministry of Justice, where we met with Tom Read their Chief Digital Officer to see what we can learn from their experience of similar changes. I was reassured to find that they’re asking very similar questions to the ones we’re considering and we took away some useful ideas and lessons which will help us with the work here.

On Thursday the team from Digi2al, under the guidance of Felix who joined our delivery team this week, began their discovery work which will help shape the way we take this forward. It’s good to be starting this with a discovery, because  it’s a complex and important area and we need to make sure that we understand the different dimensions and how we will link in across different teams before we set out any detailed plans for the work.

As I said at Thursday lunchtime’s strategy stand up, I would strongly encourage everyone across the team to take time to keep in touch with this work through their Show & Tells, Weeknotes and joining the Slack channel that Felix has set up. This project will be very important in defining how we do large parts of our work in future and your involvement will help us make sure we do that well.

Other highlights from last week were:

  • On Monday I took part in a training day for the people who part of the Council’s ‘Gold’ rota (being on call as ‘Gold’ means you are the Council’s designated lead for any emergency planning responses over a week long shift every couple of months). It was a useful day and a good reminder of the responsibilities which come with this role.
  • On Wednesday I joined the show and tell delivered by the team who are working on delivering web based single sign on for our systems and services. This was a useful update and helped me understand the team’s progress and the trade offs that will need to be considered when their current assessment work completes.
  • The Spacebank team have been making good progress looking at how we might make it easier for residents and local groups to book rooms in the Council’s libraries (the area that they’re focusing on for this phase). On Thursday I joined them for an update with Cllr Kennedy and Cllr Selman, the Cabinet leads for this work, and it was great to see that the team’s progress was well received.
  • Next week we have a workshop to agree the priority protects for LOTI (the London Office of Technology and Innovation which will formally launch very soon). On Thursday I had a pre-meet phone call to talk through some of the questions we’ll be looking at and offer my thoughts on how we might make sure that LOTI gets off to a good start.

Something I’m learning

I decided that I wanted to bring my blog and Weeknotes together, and I also decided that it was a good time to look at other publishing platforms rather than Medium, as I’ve been getting annoyed with some of Medium’s ‘features’ and am wondering whether the direction they’re taking is a good thing for online publishing. I was pleased to find that it was fairly straightforward to move everything over to WordPress and was chuffed that I managed to fathom out the DNS changes needed so that it works using my own domain. This wasn’t massively complex once I’d worked it out but it was outside of my technical comfort zone so it felt rewarding to make it work!