Thanks for the note. That is a perfect example of a company, who just can't afford to wait. The window is closing to turn the tide, if it hasn't closed already.
Fair comment, part of the point of the article is to challenge the notion that it takes X long to build something. I think sometimes we talk ourselves into believing it is going to take longer to build something than it could.
That I can possibly agree with, when it is ourselves we are challenging with the deadlines and when we are talking about a launch or not situation. For teams I think that mentality more often than not leads to poor results and quality. Rushing without taking the time needed to do something "right" (I'll leave it as an exercise for the reader to determine what's "right" for them) just isn't sustainable long term.
I think there is a subtle difference for rushing and coding bad in the process as opposed to be excruciatingly focused on a deadline and thinking of clever ways to do things faster. I will be sure to check out that blog though. Thx
Well I have come across really good UX folks that encompass both traits. I think it is less a question about job, but the role they play and skillset. A product needs a sherpa, no matter who plays the part.
Thanks for reminding me about the grammar, constant challenge :)
I have lots of examples, perhaps I will do a follow up on that. I will have to talk about most of those examples with a beer in hand, that is a prerequisite.
