Are you still calling it UX?

And why you can win the argument but lose the point.

Something happened in a sprint planning meeting that would change the way integration between Agile and UX methodologies will be done in the future.

And with the swift stroke of a blue ballpoint, UX integration was complete.

Lets just think about the significance of this.

By removing the term UX, the blackbox that shrouded the UX activities is also gone (and you no longer have to try and recover it after the project crashes and burns).

By replacing it with the term design gives you the ability to break up the design activity into both conceptual design work (i.e. sketches, wire frames, mockups, etc.) and research/analysis work (i.e. contextual enquiry, customer journey, persona, etc.).

  • Do you care whether doing design work and not UX design work is going to cost you lots of extra $$$ in your next job?
  • Do you care whether doing design work and not UX design work is going to make your work seem more or less important?
  • Do you care whether doing design work and not UX design work is going to result in a better overall user experience?

Like I said before, you can win the argument but still lose the point…