Reputation
29,311
Next tag badge:
96/100 score
29/20 answers
Badges
3 48 89
Newest
 Nice Answer
Impact
~949k people reached

May
21
comment The coding monkey dilemma
@PariyaKashfi that is very true. Alas, it's still the correct solution. Often working in a large company is a constant game of catch-22 :)
May
21
comment The coding monkey dilemma
+10 for Lose the Silos. No, wait. +100!
May
21
comment The coding monkey dilemma
I like this. I'd maybe go a step further with 'good developers' and say a good developer not just defers to UX but actively collaborates with UX. (and the reverse is true as well...the more UX and Dev collaborates, the better then UX in general)
May
21
comment The coding monkey dilemma
@R.Barzell that's fine, but I think that heavily depends on process. In an Agile process, dev needs to be part of that creative thinking group as much as UX. In waterfall, dev tends to be simply told what to do (for better and worse).
May
21
comment What is the most important for customer in terms of content?
There's no real specific answer to this other than "The content you have should be relevant to the user's needs and wants"
May
20
comment How long should automatic doors delay closing?
They should stay open long enough for a person to pass through.
May
18
comment On forms, is inline placeholder text better than a label outside each field?
It's really important to point out that the Material Design example is not using placeholder text. It is using labels.
May
14
comment 'Fountain well' style of software development
"less unhappy" is maybe a safer way to put it. :)
May
14
comment 'Fountain well' style of software development
I wouldn't blame Agile on that, but rather how they are integrating UX into it. A lot of organizations (mine included) created an Agile process that didn't take UX into account. They now try to bolt it on and it doesn't work really well. Look into "Lean UX" which is an attempt at addressing this issue.
May
14
comment 'Fountain well' style of software development
Keep in mind that Agile is meant to handle exactly that...changes in business, technical and user requirements. You may not need to reinvent the wheel (though that's fun to do too).
May
14
comment 'Fountain well' style of software development
@MichaelLai to me, that sounds like typical 'enterprise process'. I work in an org that does the same thing. Often business requirements are written AFTER the UI is halfway built. I don't have a solution for that other than to say "Lot's of big companies simply have really bad processes and there is no magic bullet to fix it." :/
May
14
comment 'Fountain well' style of software development
Finally (maybe this should all be re-written as an answer!) you aren't totally off the mark, though. What you can do--even if you don't change the entire process--is to encourage a decoupled MVP framework. Have data not be directly coupled to UI output. That will give you the most flexibility.
May
14
comment 'Fountain well' style of software development
Ideally, however you do it, it's important to realize the end product is a complex one from front to back and the best way to hedge your bets towards success is to make sure that you aren't locking any one 'layer' of the system before the other 'layers' are built. The reason waterfall usually fails is that things always change. Agile came along to try and make that fact part of the process. Building the entire back end sans UI is, IMHO, as likely to fail as designing the ehtire UI sans back end. They have to be built in relation to each other (and each has to be willing to adjust as you go).
May
14
comment 'Fountain well' style of software development
It depends on what you mean by 'design'. In my book, development is design as much as UX is. You can't really develop something without also designing it--whether that's the developer or UX person or business lead or whoever. Ultimately, a prototype is a design. So, based on your last comment, I think you're actually referring to Agile. Get something built first then make it prettier as you go. (Also known as MVP: Minimal Viable Product)
May
14
comment 'Fountain well' style of software development
I don't quite know that I follow you, but I think you're talking about an MVP framework: en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93presenter In general, this is something developers and designers often lobby for...having distinct decoupling of UI from business logic. There are many ways to handle it technically. All that said, at the end of the day, there's still things that have to make sense logically between the UI and business logic, so it's not a magic bullet.
May
14
comment Intuitive colour pickers for non-expert users?
Apple's color picker is one I like--mainly because of the many many options and ways to pick a color it offers up.
May
14
comment Why are messages on the road printed in reverse?
@CodeMoose you are correct. Ultimately, it's a less-than-ideal situation to write multiple line messages on pavement. But it's the only practical way to read multiple lines when traveling at 60mph. A better approach is usually a sign, where you can have multiple lines of text easily readable from top to bottom.
May
14
comment Laptop + external monitor = virtual screen arrangement?
@EvilClosetMonkey it's like asking what the best desk is for people. It's going to be overwhelmingly a personal preference. If we had a specific task to evaluate, then maybe there'd be a configuration that would be a better default option, but there'd still be so much variance in preferences.
May
13
comment Are there any web presentation systems that does this?
For the type of audience I assume you may be targetting, I'd say a link to a live code example may make more sense. Otherwise, a simple video presentation would hit most of your features. Just keep it short.
May
13
comment Are there any web presentation systems that does this?
This doesn't appear to be a UX question but rather a production question.