Embracing Agile Design

We’re working in an entirely new space, in an environment of continual change, with an evolving technology creating new products and services where there is not much time (or patience) for planning and up-front design.

We’re simultaneously trying to discover how these new products and services are going to be used, how will they behave in emerging market conditions, and in the end, we’re even trying to discover how we’re going to build them.

Design looks empathically at the customers we’re building the product for, understanding and addressing their core needs and coming up with a solution that meets those needs, are technically feasible and viable for their business.

Embracing continuous learning

We know that our first attempt will inevitably require revisions. Maybe less from the technical aspect but more from the customer behaviour aspect.

The sooner we get something out to our customers, test and validate our ideas, the sooner we learn from it and know exactly what our next revision will be. Waiting too long to get feedback is wasteful.

Accepting the iterative nature of design and software development requires the support of a high-functioning and collaborative teams. We as a team understand (or should be thinking this way) that we’re most likely not going to get it right the first time and that we’re all working together to iterate our way forward through continuous feedback loops and learning.

Agile Design in practice

General rules

<aside> 💡 The product of our work as designers is not the mockup we hand off at the end of our workday; it’s every decision we made with the team and how we influenced the organisation at large.

</aside>

How to request design work