One of the great challenges of any company is to understand whom they offer their service to and why they do it. So, why do we say we design for agile development teams?
The best way to explain this will be splitting the question into two parts.
A few years ago, when we started to work on interface design, we had different types of clients; some were programmers and others were design studios and advertising agencies. I remember that we had the opportunity to design a website for a graphic design agency in England.
When we finished the first round of designs, their feedback was: “I think it needs to be more pop kitsch”. Pop kitsch? That was not a profitable return at all! It clearly came from a less pragmatic designer/artist, and this was not the kind of feedback we used to receive when working with development teams. But, on the other hand, it helped a lot to clarify and define a little more with whom we wanted to make work teams and with whom we didn’t.
Design aims to ensure the effectiveness of communications. It is centered in the user; It is ethical because it is based on the knowledge of the “other” as different and respectable. – Jorge Frascara
Although the concept of “designer” is often deviated and is only thought to be someone who embellishes things, the reality is that designers and developers share very similar goals. Both seek the best solution to a problem.
We design for developers because we feel comfortable with their practical approach when developing a digital product, their passion for solving problems; they trust our work, they do not think about fonts or colors, just as we don’t think if it is more convenient to use Angular or Xamarin.
We believe that the best way to deliver value to the users is by taking small steps towards the final product. Observing, learning, correcting our mistakes and repeating the process again. We work together with agile teams because we consider ourselves agile, as designers, as a team, and as a company.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. – Principles behind the Agile Manifesto
We are not talking about teams that use Kanban, SCRUM or XP, nor about teams that only want to launch a product as soon as possible, but teams that have the courage to take responsibility for their actions, recognize their mistakes and learn from them quickly to correct them.
Agile was not originally conceived as a series of rules and ceremonies, it was invented as a set of principles that guided teams to achieve agility, or the ability to respond gracefully to the change around them. – Page Laubheimer
That’s the agility we seek in our work process and the agility we seek to promote to deliver products of great value to the users. We believe that this is the best way to do it. If not, we will stop, look back, reflect and correct our course, always agile.