Skip to content
This repository has been archived by the owner on Oct 7, 2022. It is now read-only.

Write a MagicBox user persona and tie it to mission statement (blocked by #32) #33

Open
jwflory opened this issue Apr 23, 2018 · 0 comments
Labels
community Supporting and building the project community docs Adding or updating documentation priority:low We're not thinking about it yet

Comments

@jwflory
Copy link
Member

jwflory commented Apr 23, 2018

After writing a mission statement (see #32), write one user persona for MagicBox and tie that persona to our mission statement; publish the persona to our ReadTheDocs documentation

How to do it

  1. Go back to list of users from Write a general, 2-3 paragraph "mission statement" for MagicBox development #32: of those users, choose one whose use case is important and helpful to highlight to a new contributor / team member
  2. Write a persona about one of these users: What do they need from MagicBox? How do they use MagicBox?
  3. Review persona with other team members, get feedback
  4. After feedback / revisions, add as new personas page to ReadTheDocs documentation

Why do it

A persona helps us keep who our users and their needs in mind when developing. A persona is also a story: it's an opportunity to show an outsider how this project actually meets the goals and purpose it meets from our mission statement (#32). This does two things:

  • Appeals to the unique nature of our project and demonstrate value in contributing
  • Helps a new contributor understand our project and user needs better

Writing a persona for an important user of MagicBox introduces the project for us automatically through documentation.

@jwflory jwflory added priority:low We're not thinking about it yet community Supporting and building the project community docs Adding or updating documentation labels Apr 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
community Supporting and building the project community docs Adding or updating documentation priority:low We're not thinking about it yet
Projects
None yet
Development

No branches or pull requests

1 participant