Manage a tenancy: Weeknotes 24/04/2019

Manage a tenancy is a service we’re developing for housing officers to be able to carry out their visits and checks processes in residents homes using a mobile solution.

This week we held the Manage a tenancy show and tell at our Stamford Hill Neighbourhood Housing Office. Here’s the update from that session.

We’ve paused any further development work on the Tenancy and Household Check and Home Check processes. Most issues now being seen with these processes relate to issues with tenants’ data and need to be investigated as soon as resources are available.

The Introductory Tenancy Visit process will be able to be released as soon as issues with the ‘scheduler’ for automatically adding the process to the housing officer’s work tray is resolved. Issues with the Review and submit page were resolved.

Introductory tenancy vist start page
Introductory tenancy visit start page

ETRA (Enhanced Tenants and Residents Association) process to record issues raised at TRA meetings and send them to relevant service areas for response, continues with our apprentice developer doing great work in developing the UI in OutSystems and linking it up with APIs. Some issues around saving assets are to be resolved.

We’ve also deployed some improvements to the ‘hub’. Immediately noticed (and liked) by a housing officer at the Show and tell.

Managing people data project: Weeknotes w/b 08 April

We are two weeks into our discovery phase and the team has achieved so much already.
We have;
– collaboratively identified participants and created our participant list
– collaboratively developed our discussion guide
– 2 user research interviews interviews have already taken place and several others booked
– we have had one wash-up session and several others booked

Many thanks to Wingwo. Andrew, Kirstine, Gerard, Husain and Henry.

Re-engineering Hackney content: Weeknotes 23 April

Short week so we’re opting for bullets so you have time to read them:

– Populated most of our first section in Contentful
– Adapted test-driven development practices to hone the process of content population
– Designed the contact block and started to look at mapping with Liz Harrison’s team to make sure users can physically get to where they want
– Deconstructed OneAccount to ensure its user journeys are optimal
– Integrated Jest for automated testing and piloted an alternative to Circle CI for builds
– Looked at the site hierarchy to see if we can reduce from six levels and the simplify navigation (we can)
– Got a little over-excited about Find My Nearest

Next show and tell is Thursday 1 May.

Hackney Spacebank: Weeknotes w/b 15th April

As it is a short week, here’s three things you need to know about Spacebank

Putting aside niggling doubts
When someone wants to do “a thing” and needs somewhere to do it, what’s their first step? We did a Twitter poll this week to find out the answer as well as some guerilla research at Hackney Central Library.

We found that that the vast majority of people turn to Google as a starting point. A significantly smaller minority of people would ask a contact or visit the Council website. This nugget of information will shape how we construct our user journey.

Shifting our focus
In this phase of the project we are looking at how people access and book space at libraries. We’ve found out that of our three user groups it is voluntary and community organisations who are most likely to book library rooms for meetings or training.

Why is this important? Up until now we’ve been focused on a different set of users – resident groups. Despite some excellent contacts from colleagues and ruthless detective work from Sam Whitlock and Winston Mullings this group is very difficult to reach. Combined with the new information about library bookings and a review of our Discovery findings we’ve decided to shift our focus onto voluntary and community organisations.

This is a larger, more accessible, group with almost identical needs and pain points to resident groups. The key difference is that residents groups experience the difficulties more acutely because of a lack of time and resources. Our assumption is that if we improve access to library space for groups who use space now, we add value to a larger number of users quickly and we could help a brand new audience (resident groups) access library space in future.

Having more conversations
This sprint has shown us again the value of having good quality conversations early and frequently. It can be hard to challenge the ideas of others and to be open to other ways of seeing things. The team has handled this with honesty, good humour and integrity. We’ve agreed steps to make sure this keeps happening in a positive way. We’re changing the way we organise sprint refinement (a planning exercise) and how we use Trello cards (a way of tracking the granular work we do each sprint).