Co-design in disability services: lessons from a hackathon
Hack-a-what?
By BA3 · Originally published 14 June 2017
Original article and dated context
Rahul Soans and Anna McCracken are from BA3, which provides consultancy, workshops, tools and resources to families and early childhood intervention providers to help the community manage the change presented by the NDIS. You can read Rahul and Anna’s full bios here. The move from block funding to the NDIS is in equal parts exciting and scary. Exciting because service providers are no longer mandated to provide services that are dependent on funding. Scary because for the first time they have to be ‘innovative’. A Hackathon (as the title of this piece alludes to) is an event. An event that typically runs for 24-48 hours with the sole intention of collectively solving a problem. The term itself originated in the technology sector as a mashup of the words hack and marathon. A hack here meaning a way to creatively problem solve – a skill that would be prized for service providers moving from block funding to a market-based system such as the NDIS Why do this? The technology sector in the late nineties realised that to be innovative in technology they couldn’t work in silos. They needed to open up and bring in people with different styles of thinking, different ways of looking at the world, different personalities – or they were in danger of creating products just for white men between the age of 19-23. So they brought in designers, engineers, project managers and customers (depending on who they were solving for). For many, innovation is an ambiguous term. For most of us it seems out of reach, best left to the geniuses among us. In the technology world it’s the Steve Jobs and the Bill Gates (creators of Apple and Microsoft respectively). But innovation is really about solving a problem. It is well within the grasp of anyone. It could be looking at the problem from a bird’s eye view and seeing if it’s been solved in other areas. Steve Jobs, when he was setting up the Apple store, knew that he wanted a different experience to traditional retail. So instead of trying to upend the retail experience, he asked himself, “where do people like hanging out?” And the answer was the lobby of 5 star hotels. So he put his staff through the Four Seasons training program to find out why. One of the answers was the hotel concierge, someone who was friendly to talk to and who could answer your questions. Hence the Genius Bar at Apple stores. What is needed for innovation is exposure – exposure to wide variety of people, ideas, technology and culture. Hackathons bring these elements together and are a breeding ground for new ideas. They get the creative and problem-solving juices flowing. Unlike a day-in-the-life of a disability service provider, where risk-taking may be frowned upon (or in the case of block-funding, completely unnecessary), a hackathon ensures everyone has equal say and that the cost of failure is low. Outsiders to the sector bring a new energy and diverse perspectives to the challenges that are being looked at. The move from block funding to the NDIS presents a whole raft of challenges for the disability sector. The need for new ideas is now more important than ever.A hackathon for disability services
Why is this important?
Clickability editorial update: October 2026
Make participation accessible before asking for ideas
Define the problem in terms participants recognise and explain what decisions their input can influence. Offer useful formats, enough time and alternatives to a fast group discussion. Ask how people want to contribute and how access or participation costs will be addressed.
Record what was heard, which ideas will be tried and who is responsible. Test changes with proportionate safeguards and report the result back, including ideas not adopted. Provider governance standards help connect a creative workshop with accountable service improvement.
Ask what influence your contribution will have
Check whether the workshop is seeking ideas, making a decision or testing a proposed change. Ask what support is available to participate and how your words will be used. You should be able to disagree or decline a photograph without losing access to the service. Ask when you will hear what happened after the session.
Questions readers ask
Does running a workshop prove meaningful co-design?
No. Examine access, influence and what happens to the contribution.
Find a provider that listens and follows through
Compare Clickability reviews and profiles, then ask how providers involve participants in service improvement. Look for clear communication about decisions and changes.