Create and then add personas to readme

[Cleop]

Linked to #212 #192 and https://git.io/fh1Hu

As a team member
I want to see a set of personas in the readme
So that I can easily recall and consider the end user while building the product

As a starting point, here's a little about our users:

users "dwylers" are "people who want to proactively track their time/progress on important tasks so that they can (a) stay focussed on their highest priority, (b) see where their time is being spent and (c) never be "stuck" for what work on next."
That is a fairly broad definition and I go into why in this comment: #192 (comment)
We will need to create personas for a few "target" people but the first person should be someone you know who has trouble with time/task/priority management (or generically a "Creative Technologist" similar to you, who is less time-effective and needs to track their time both at work and while training for {competitive-sporting-event} to discover why there are never enough hours in the day...).

In order to build the persona we need to list the target person's:

Name: e.g: "Thomas Timepoor"
Age: 31
Background: "amusing but realistic bio here..." [please add when you open "Personas" Issue]
Goals: track time on tasks to achieve ambitious goals while maintaining work-life balance"
Pain Points: "regularly over-runs on work/task estimates, never has enough time to exercise and gets distracted by shiny objects ... want's to cure all of these by using a systematic tool"
Why?: Feels
Note: none of these points are reflective of Cleo who is consistently good at estimates and finds time to exercise, etc. These are generic points for our "target person".

[nelsonic]

@iteles how many personas do you think we need during our MVP
and what types of people do we want to have profiles for?

What are your thoughts on making ourselves the Personas?

e.g. "Nelson NoSystem". Age 33. Software Developer | Digital Content Creator | Carpenter
Has too many things competing for his attention and thus underachieves in all areas.
He needs a systematic way to keep track of everything in his head so that he can make meaningful progress on his goals and does not forget anything important! etc.

Or do you prefer to have representative (fictional) people so that it's not quite as personal?
I honestly don't mind being the subject of a persona as a reminder that I'm building this App for myself ... I need this App every bit as much as anyone else. But totally understand if anyone else in the team has reservations about making themselves a persona. 💭

As we have previously (verbally) discussed and to an extent captured in #192,
we need to cover the Individual use case first.
I'm busy elaborating on this in my current Product Roadmap enhancement PR: https://github.com/dwyl/product-roadmap/pull/22/files#r442534157 (will assign shortly)

[iteles]

Having ourselves as personas is essential because we are the people we know best and we certainly both need the app - I'll write one out for me.
But I also think it would be ideal to have a couple more personas so that we don't lose sight of making this application useful for people more generally (as is our mission https://github.com/dwyl/start-here/blob/master/mission.md#what-is-dwyls-mission) with incredibly specific features too early on.

Having other personas, even if we're not building too many features only for them, will help us think through each feature from their point of view too, which I reckon is essential.

I'll make a list of suggestions and we can pick a couple to prioritise early ❤️