Hacker News new | past | comments | ask | show | jobs | submit login

There's no reason a creative developer couldn't foresee the barber's predicament without speaking with the barber.

Patiently visualised, devised imagined scenarios. Phone rings, barber says "excuse me" to his client and walks over to the phone. But does he put the comb down first? Perhaps. Barbers have trays handy, but they might walk around, tools in hand. (This is obvious, and doesn't take research to imagine.)

The phone needs to be next to the computer - no screen savers, the scheduling software always on, with clear and large fonts, minimal clutter (generally good interface design anyway). Think "high quality app design", not "looks like Excel".

A beautifully designed interface that would impress the barber if demonstrated. Custom default views and all that.

It's ok to start from the blue sky and work down to the reality instead of working up from "what the barber likes with his paper calendars". Which isn't the wrong way, but could skew the potential. Top down isn't wrong, if you've done your visualising!

Not that research and getting out into the world isn't valuable. (obvious). I'd probably take a look at the book anyway... sounds ok.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: