Hacker News new | ask | show | jobs
by zacharypinter 5103 days ago
I had a co-op job with the Navy (civil service) while in college. I sat next to a really nice lady named Peggy who was on the phone every day fielding lost password requests. She'd reset the password, then read the new password to the person over the phone, day after day after day.

I went to my boss and offered to add a forgot password link to the site. His response: "But then what would Peggy do?"

3 comments

This is what I imagine when I hear the phrase "job creation."

If you want something done - your lawn mowed, a meal made, etc - you'll hire someone. But a job for its own sake? What, are you going to hire somebody to move a pile of rocks back and forth across your yard?

A job starts with a need, not vice versa.

I have a pile of rocks in my yard... need work?
After a couple days of rock moving, I'll just build a pick-n-place robot in my garage to do the work for me, ok?
I know you say this in jest... but if you can solve unstructured pick-n-place (ie. non-uniform, unmodeled objects in arbitrary configurations with difficult outdoor perception), you could make some serious bank. This is actually a _very_ difficult problem.
He'd rather just go home early than share his robot.
So much of the software work I've done is around getting computers to do the things that computers are good at. My response to the "what would Peggy do?" question is always "something that only Peggy can do"

Automation doesn't have to be about reducing staffing costs, firing people, or hiring fewer people, it can be about getting more and better output from the humans on your team. Humans are great, and are wasted by reading passwords over the phone.

I've worked with plenty of otherwise competent people who could spend 5-10 minutes trying to find a website link or form submit button that was right in front of them.

Peggy provides better, faster feedback than a "forgot password" link does for the vast majority of the population. Not everyone knows their way around a computer; the HN crowd is definitely not representative in this respect. But plenty of people, especially in older generations, know how to use a phone and talk to someone.

Think of Peggy as a UX hack: she makes non-technical employees more efficient by cutting down by 75-80% the amount of time such people would spend trying to reset their password (using the "forgot password link" method). Alternatively, think of her as internal customer service. Either way, she actually does/did provide value to the organization if the organization was large enough that she could spend essentially all of her workday resetting passwords for people.

O guess there is room for both Peggy and the link, because I would rather deal with a computer than a stranger for password reset.