We’ve been wondering how best to communicate what we’ve been working on, what’s currently being worked on and what we have planned in. In the past we’ve tried weekly video updates, which seemed popular but weren’t easy to keep short and pithy. So we thought we would try a monthly update here on the blog – we would really welcome your thoughts on the format as our aim is to keep you in the loop.
Firstly, this is our task board, loosely based on a kanban board. It documents the tasks, in as ‘discrete’ a way as we can, as they go from research to development, review, acceptance and deploy. There’s a heap of writing around agile ways of working and I’m not going to go into it here – but we try to be agile in the way we work to be as productive as we can be (being a small team of mainly part-time staff). The tasks to the left are the backlog – tasks ready to bring in when we have the resources to do so. These backlog tasks are organised by ‘feature request’ and ‘bug / issue’.
In the last month the main tasks we’ve been working on are:
- Undertaking user testing among buyers and sellers – the main findings of which are: search needs to be more obvious; section pages need to be improved to support browsing (not goal-orientated search); shipping dates are too ambiguous for buyers who want to know when something will be delivered.
- Reworking the server architecture to better manage SSL certificates (we’re about to deploy a froxy server as the front end, which will host the SSL certificate).
- Getting the homepage elements into the beta app (our development environment has an older Alpha codebase and a newer Beta codebase and we’re migrating different aspects of folksy.com to the newer codebase, bit by bit). So far the smorgasbord and the drop-down nav have been done (using the JS test framework).
- I’ve been researching community investment and community businesses.
- Camilla attended the excellent Sprint Feverbee workshop and conference which discussed best practice community practices and we’re working on practical ways we can enable buyers and sellers to organise groups.
- Squashing bugs: banner resizing issues; adding scroll to the ‘buying from me’ field, making the basket more obvious in mobile view (it was hidden in the menu), fixing button wrapping in android / mobile chrome, fixing a postage fees bug on non-UK shipping.
- Updating our GoCardless integration.
- Reviewing search performance (seeing how items and shops are represented in Google).
- Launching and running “Twitter Hour” which in its second week was the second most significant trending item on Twitter, second to some big scandal on EastEnders (that I know nothing about as I don’t watch Eastenders but see from a quick google search that it involved someone called Lucy. Poor Lucy.)
- Integrating search terms into sitemaps (code implemented, although we’ve not pushed the terms, yet).
Of course, there are a ton of things I haven’t listed that we do on a regular basis (marketing activity, support tickets etc) and we’ve taken these as a given, even though they are very important.
Coming up in March
- We’re having a review of the service, to see how we can improve the way folksy.com is seen, especially by people searching on Google (we follow best practice in SEO but wanted to have a review of what we could be doing that may have a positive impact).
- Tom Stafford is working with me on analytics and data (he’s spending the next 2-3 months as our Data Scientist in Residence) and he’s going to be blogging about some of the things the data tells us about how people shop on Folksy.
- We’re going to start work on bringing tags / keywords back into Folksy. If you have a long memory you might remember that we stopped using tags back in 2012 as they were becoming unwieldy to manage and maintain. But they were popular and we know they can help support browsing around Folksy and now we have a strategy to make it relatively easy to maintain them. It’s a small thing but we’re really excited by it.
- Planning a way to help groups within Folksy self-organise (teams / groups are something we’re really keen to support). This may bleed into April, but the process will start this month.
- Camilla is undertaking a workshop on events – to help us work out how we can support sellers in their offline activity and what should follow the successful Folksy Summer School and Folksy Workshops.
If you have any suggestions for features you would like to see implemented on Folksy, you can add your ideas and vote for others on our Knowledge Base >>