This document discusses converting from user stories to job stories when planning software features. It provides examples of how a typical user story is structured, problems with the user story approach, and how a job story alternative is structured instead. A job story focuses on the user's work context, motivation and desired outcome rather than predefined personas. The document also provides examples of how job stories were used to plan and test features for open source projects like Jekyll and Rails.