Agile is a neverending topic when it comes to optimizing processes, basically production processes and to be more specific: production of code.

July 25, 2017

As a designer, I am frequently challenged to bring design (iteration and creation) work into a more productive process.

This means: "Why can't you work agile?"

The answer is not easy.

We also have production phases in which an agile approach can make sense in design work. But if we talk about the ideation process, where things are less planned because it means creating/designing something new out of nothing, rigid phases can be a stopper in a process or a direction that could be worth following.

It is interesting to examine what being agile means in the original context of transforming large companies or corporations.

Within the digitalisation of everything, we try to achieve non-digital processes to achieve faster results, outcomes, or revenues. 

Organizations and companies are forced to optimize their working processes, so it is no wonder that agile methods, even in non-production environments, are demanded everywhere.

I had to think about that when I was working on a project that aimed to bring agility into a large company. I had a look at what agility means in the original context and found this on Wikipedia:

Agility or nimbleness is the ability to change the body's position efficiently. It requires integrating isolated movement skills using a combination of balance, coordination, speed, reflexes, strength, and endurance.

I've translated these habits to apply them to large corporations or companies, and this looks something like this:

• balance - be flexible out of your comfort zone

• coordination - act with a sense

• speed - be effective

• reflexes - the capacity to react

• strength - follow a goal

• endurance - resist pressure

So, is your organization/company prepared for agility?