simonsayscode

This sounds simple, and in theory it is, but go to where your potential users are. A lot harder to execute than to do, to be honest. So what do I mean by that - I mean if your product is B2C then go to where those consumers are. But wait - segment your target users first. What demographics are they? Where can you find them when they're in their idle time? Is it a park? Is it a pet store? Is it in at the gym?

If you're looking for tips in how to approach, I like to reference http://www.designkit.org/ for practical steps and directions. If you're nervous about finding users still, and want them to come to you, you'll probably have to pay for that privilege but luckily you can use something like (https://www.userinterviews.com/signup/MTI3Ni0x) Full disclosure - if you sign up for that link you'll get 3 free user interview sessions (but you'll still have to pay the users themselves) and I'll get 3 free participants too for referral.

End of the day though, you've got to just suck it up and just walk to someone and put yourself out there. I like to think of it as you're acting like you're a confident, approachable person who's got a really interesting thing to talk to them about. It helps me overcome my shyness that's my "normal" self.

Also, a must do though, is think through beforehand what you want to ask them. Create a script that way you can standardize what you want to cover. You can do some test runs of these scripts with friends who would most resemble your users. That way you can build up confidence in your delivery and content.

Best of luck!

I don't think that this is meant to be sold to the poor demographic. I would rather think that this is just applying design principles and the design sprint as an exercise to an untouched piece of technology.

That being said, I could easily imagine some charity that either sells these designs at an extremely (or free) discounted rate to these workers in an effort to relieve back pain and the myriad of other physiological issues the traditional pole yields.

Doesn't this go against Netflix's Terms of Use (https://www.netflix.com/TermsOfUse) by scraping for data, if you're not relying on the now shut down public API?

I'm pretty sure it was a jibe at the fact that only 3 real Star Wars live-action films were made.

You're mixing politics with good engineering.

I would argue that a quorum of engineers would generally agree with whatever is justifiably deviating from best practices. If it makes sense to you because of good engineering reasons, then it should probably make sense to other engineers. Reality perhaps dictates otherwise, but that's what it should strive for.

I disagree with your statement. I believe that "best practices" means that "this is probably how it should be in the majority of uses." Obviously each situation is different and not everyone's solution will work for you, but I'd be willing to be that more often than not, it would.

Whenever something deviates from best practices, I would think that that raises a red flag for justification of difference.