Following our Hackathon, we held a retrospective to reflect on the week, a productive session exploring the challenges we faced and the opportunity for improvement when it comes to process, project, and progress. Have a read below of our key takeaways.
The cross-pollination of creativity and collaboration
Within our nifty team, we have a huge cross-section of interests, skills, and areas of expertise, making for a perfect exchange of ideas and inspirations. By bringing the non-designers into the full scope of the creative process, there’s now a broader understanding of the journey from idea to outcome, giving our ops team clarity around communicating the creative process both internally and with clients.
The importance of a daily roadmap to follow and respond to
Something we would include in future Hackathons would be a roadmap detailing actions and priorities to help clarify outcomes and make it easier for the team to work independently. Using platforms beyond Figma and Slack will help to build a fuller scope of the project – tools like Notion provide vital support to our internal systems and client work, ideal for collaboration, communication, and co-creation.
How can we safeguard time around client work and priorities?
Our time and client commitments created some challenges during the Hackathon, with a lot of the team splitting their extra workload around our daily calls and catch-ups. For future collaborative projects, we’ll plan further ahead of time to manage full sign-offs from client work for a team-wide immersive week.
Could we explore the idea of a five day week to capture the full breadth of the sprint?
The sprint method spans a full five day week instead of our 34 hours over four days – for next time we are considering shorter days over five days to align more closely with the structure, checking in with our team’s other commitments to make sure they’re not working overtime! The fifth day provided time for testing and QA, a great opportunity for final touches.
The joy of autonomy, agency, and making decisions as a team
Working as a team with two all-hands workshops each day was an exercise in intensive team-led collaboration – it was at once enriching and exhausting, but overall an unusual chance to make decisions as a creative team over client wishes. ROAM bypassed the traditionally tech-based coding event that Hackathons are so often thought of as, instead connecting IRL issues with achievable digital design solutions.