Every month we host the monthly gathering of the Aberdeen Data community.
We combine service design thinking, an open data mindset and experience across government, commerce, and education in our practice. We are absolutely focused on the importance of validation, ideation and realisation in answering tough questions about improving life in cities.
We know that code is impressive. Code feels like work. Code looks and sounds like progress.
It’s fancy. It’s unambiguously ‘doing something constructive’. ‘Have you started coding yet?’ is always asked in an excited voice.’ It’s a milestone. It’s important. It’s also toxic. The need to start coding early ‘to stay on track’ actively disadvantages projects every day.
We work on a different clock. We measure progress in a more meaningful, more people centred way. We don’t see the move from post-its to browsers as a major milestone. We see a tighter definition of the problem as a major milestone.
We see the identification of key stakeholders as a major milestone. We see the transition from divergent to convergent activity as a major milestone.
Whether these transitions happen in code or on whiteboards, post its, word docs, or even Lego is unimportant. What matters is that these transitions represent a more realistic indication of the status of the project. It tells us more about the work that has been done, and the work ahead.
This is the principle that has shaped our service offering.