Taking Care of Little Big Details on an Off-Site Bootcamp
A few weeks ago, we went on a two-day off-site with the Clarabrige Engage development team for an event we dubbed "improvement bootcamp". It's the second time we did something like this and since it was fun and we got quite a lot of stuff done, we wanted to share our story. Maybe it could work for your team as well.
The problem with roadmaps
The idea behind a bootcamp is "drop everything, let's work on something else, someplace else for a few days". For two days, we were hidden away in a beautiful house in the fields of Waasland where we focused solely on what we like to call "little big details".
Over the course of the 6+ years that our product has existed, we have built up a huge database of customer requests. Prioritization and implementation of those requests is a constant process; in fact, almost all of our roadmap is compromised of client-requested features. We take logging these requests very seriously. Feature requests come to us through our ideas forum (where clients can post & up-vote ideas), via our Live Chat, and via our dedicated Customer Success team. All of this information (what is requested, who is requesting it, if it's technically possible/feasible, etc.) is then ranked by priority and, after being curated by the Product Team, makes up the roadmap.
That roadmap becomes our daily job, at least when we're not playing Batman. We always have a detailed roadmap for the next release of our product (around three months), and a more general one for the upcoming 12 months. This balance works for us; we can commit certain projects to our customers, while on the longer term we can stay flexible, react quickly to changing customer demands, and implement new social functionality when it becomes available.
When we try to do all at once
But, as it often goes, projects aren't perfectly defined from the start (their scope often grows) and we developers tend to underestimate projects, so getting everything finished on-time sometimes (more often than we’d like) results in neglecting some of the details. Those are the details that make a product stress-free, or - why not - even fun to use.
The "improvement bootcamp" is our initiative to force ourselves to periodically step back and focus on these little big details.
Little Big Details
But what do we mean with “little big details”? It can be anything from natural sorting of elements in tables, consistent design of similar pages throughout the application, to friendlier wording of messages in the application.
Often, they're simple things. Often, they're not real “new” features. Often, you might not even know you were missing them.
Have you noticed how, when using Google Maps to get directions to another place, the walking man icon changes into a person with a backpack and walking sticks? Or how Spotify congratulates you on your good taste in music when you click 'Lyrics' on a song that Spotify doesn't have lyrics for?
Little big detail in Google Maps
It's stuff like this that makes good products even more enjoyable to use.
For our tool, a few of the candidates we selected for the bootcamp include:
- A more consistent loading/empty view of widgets around the different dashboards that Clarabrige Engage offers;
- Requiring people to type the name of the topic they want to delete;
- Remembering the text you typed in the reply bar, so that if it fails, users can easily try again;
- Make the "click area" of widgets bigger when selecting widgets to add to a dashboard;
None of these features will win awards, nor will they ever be on the top of most requested features lists; sometimes they're just small nuisances. But they do have an impact; it's details that make the difference between a good software product and one that's actually fun to use.
The action plan
Spreadsheet with the action plan
This was our action plan to get as much of this done, in a short timeframe, and have some fun while doing it:
- To start, we asked all members of the Clarabrige Engage team, from Sales to Marketing, to tag improvements in our Github repository that they thought would fit the goal.
- These were scored on a few aspects:
- Priority: Indicator of how aligned the idea is with our product vision.
- Impact: How many customers are requesting it or would benefit from it?
- Workload: How long would it take us to implement this? (If it's expected to take longer than 4 hours, it's probably not a good candidate.)
- Coolness: Sometimes the really fun ideas need a little bump, don't they?
- The candidates were sorted according to the formula
(Impact * 1.5) + (Priority * 5) + (Workload * -2) + Coolness. This would be the order in which we would tackle them.
- The top 50 items in this priority list were discussed with everyone in the development team and assigned.
- We started working on them on Wednesday morning with the goal of finishing work by Thursday evening.
- During the coding, we kept track of our own and each other’s progress on a Github project board; indicating whenever a certain improvement was implemented, ready for review, reviewed, and ready for production.
- On Thursday evening, we presented internally to the development team what everyone was able to accomplish.
Github Project Board
On Friday afternoon - our weekly beer-o'clock in the Gent office - we presented the results of the bootcamp to the whole Clarabrige Engage team. In total, we were able to get 42 things done. The list included a bunch of internal improvements - thus making our support ninjas happy - and it included some longstanding customer requests.
Slide from the presentation to the team
It did take a few more days to put everything from the bootcamp into production, because we still had to hand it over to QA, prepare any customer communication, and make sure the merges happened in a coordinated way.
If you would argue that details and fun stuff like this should be part of the standard product and development workflow, I totally agree. And while events like this might look like "patching", they actually contribute to installing that mindset by making everyone in the team aware of the importance of these.
A bootcamp like this has the pleasant side effect of actually proving what we as a team are able to accomplish in a short timeframe. That feeling of speed, and accompanying pride, is a bit harder to find when you're working on bigger, long-term projects that involve lots more nuts and bolts. Working outside of your comfort zone, by working on features in the code base you haven't seen before, or more literally, by not sitting at your desk, increased team communication and trained new team members.
And of course, you get to learn new stuff about your colleagues after hours. Like how passionate Gheerwijn is about analog cameras. And that's about all the info you’ll get, because: "what happens at the bootcamp, stays at the bootcamp". Let this vague Polaroid picture of the team be a little testament to that.
Want to join our next bootcamp? We’re always on the lookout for bright people to join the team. Read about how it’s like to work in our team.