Roles, Responsibility & Product Development

We learn through experience.

Being responsible for the actions and outcomes of a role provides a context for getting experience.

Example: Movie Ticket Taker Role
Job: Stand near the entrance to the theatre and only let people in if they have a ticket.

  • Stand for a few hours - take short break every hour, a longer break every 3 hours
  • Greet each person trying to enter.
  • Ask for ticket if they don't hand it to you.
  • Confirm today's date and movie.
  • Tell them which theatre to enter with a kind greeting and gesture.

Once you get good at this role, you may be asked to take on another role.

In a movie theatre, there aren't many roles. Each of the roles requires less than an hour of training. Once you learn the skills, you may still make mistakes, but no single action has devastating consequences. It's safe to hire unskilled workers and train them on the job.

As I build out the project we're calling Bird In Public - this idea of on-the-job training hit me.

What people want is not another eCourse. They don't want a community of people they don't know and don't really want to know. It takes energy to develop relationships and much of what we provide should be self-service. They shouldn't need to hold hands to get results.

Moving forward, I want to develop a product in a specific way. People should be able to get great value on their own - and optionally join the community for connection and camaraderie.

These values reminds me a lot of Sam Ovens'. 

Scalability through self-serve. Self-serve that works through well designed systems.
2021-02-22 13:46:32