take a look at our content focussed documentation:
watch documentationNot every project ends in a shiny prototype. But instead of hiding that, I’d like to use it as a platform to talk about what happens when things don’t go as planned and how we can use it as a learning session.
Design isn’t always a success story
Our project Jet Engines didn’t turn out the way we hoped. We struggled with technical implementation, underestimated complexity, and ran out of time before we could bring the interaction to life.
That’s how we embrace failure
We learned the hard way how crucial early prototyping and tighter scope definition are, especially when working with custom hardware. It reminded us that interaction is only as strong as its technical foundation and project management.
That would be better next time
Start testing earlier. Define MVPs. Communicate limitations more transparently.And most importantly: fail early and learn fast.