What UX taught me about agile transformations

Diego Bohman
Jan 18 · 1 min read
Image for post
Image for post

When I first got in touch with UX, Usability, Design Thinking I was intrigued by the idea not to create solutions and then hope customers will like it, but vice versa first understand what the customer needs and then come up with ideas for solutions which you test with customers in early stages.

What I observed in agile transformations is similar: We throw solutions like Scrum, Kanban, Jira, etc. at teams. We don‘t distinguish between agile methods and Business Agility. Then we are surprised that there is no real change whatsoever.

So instead we should first ask „What need or challenge should be tackled by agile“? Secondly we need to figure out which aspects are missing in the company‘s environment to generate a fertile ground. Maybe we need to talk about things like openness, respect, courage, etc. before our agile seeds can take roots. Only then Business Agility can thrive.

Which challenges should Business Agility solve for you? Which factors in your environment prevent the agile seeds from taking roots?


#UX #agile #transformation #environment #behavior #change #values #respect #openness #courage #focus #purpose #trust #commitment

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store