Jump to content
Interesting stuff, although I’d love to hear more about how to be a good dance partner (the kind of advice that’s useful for both sides of the equation. This article feels more appropriate for an organisation where there is a more distinct handover from design to development. I’ve felt for some time that this approach is risky, since a lot of the issues that can arise with a design are only apparent once you start building and using the design. That said, I bridge the gap between development and design in my workplace, so a lot of people probably have a different working environment; there are still a lot of useful things to take home here.