Identify Audience for website and create personas about website HOT 5 OPEN

@NivenPrasad I added a lot of content from the above to https://github.com/100Automations/Website/projects/2. - lets talk about this at our next meeting.

from website.

Software developers of all skill levels
Motivations:
Build personal portfolio - get attention from prospective employers or industry
Skill practicing
Learn how to create automations
Meet other like-minded developers - network
Improve reputation by association (preferential attachment)
Giving back to the open source community
Get and give feedback from peers through mentorship, advice, reviews
Receive community support in keeping automations up to date
Make automations more usable by creating distinct and well documented repositories

People with ideas for automation
Motivations:
Get the automation developed
Share automation with others
Get credit for an idea
Validate feasibility

People looking for automations (Project Managers, Business Analysts, Portfolio Owners)
Motivations:
Accomplish something without replicating work
Use something trustworthy

Employers
Motivations:
Find proven talent
Review code

Open source advocates
Motivations:
Use 100Automations as a positive example of effectiveness of open source
(Note from Ops meeting: could this firmed up? How does it compare to other solutions - what is the compelling value prop?)

Product Managers
Motivations:
Get publicity for their project by sharing an automation and having their project be the example of it in use
Giving back to the open source community

How these people will participate:
Developers will take on one of the tasks in the Participate section below
Product Managers, Employers, Open Source Advocates will use the search function
Open Source Advocates will direct traffic to the website

(Note from Ops meeting: how do we know these are good personas? People are using it. How do we prioritize these?)

(Note from Ops meeting: are there any wider buckets that could roll some of these facets up e.g. Community. ReadMe to be clearer on who is the main audience is)

PARTICIPATE
Automations that need maintenance
Automations that need refactoring
Automations that need peer review
Automations that need to be built
Automations that need to be researched
Automations that need advice

(Example Labels: Need: Maintenance or Need: Refactoring)

READY TO DEPLOY
Automations ready to deploy

COMING SOON
Automations in development

from website.

Just asked Ops team to review: https://hackforla.slack.com/archives/CV7QGL66B/p1598138195008400

from website.

Reviewed audience list with Ops team on 08/25. Feedback:

• How does 100Automations compare to other solutions in the open source automations space - what is the compelling value prop?
• How do we know these are good personas? People are using it. How do we prioritize these?
• Are there any wider buckets that could roll some of these facets up e.g. Community. ReadMe to be clearer on who the main audience is.

from website.

Last remaining item is creating proto-personas from the cards in https://github.com/100Automations/Website/projects/2
This will be used as the basis for creating a new page that tells how each persona uses the site. Think landing pages to be used in marketing campaigns.

Personas should contain:

• Name
• Job Titles
• Industries
• Motivations
• Goals
• Frustrations (pain points)
• Bio
• Communication Style
• Objections
• Senario (that brings them to site)
• Why us? (value proposition)

General list of things it could include for discussion if necessary.

1. Characteristics
2. Functions
3. Industries
4. Publications
5. Job titles
6. Tools
7. Challenges
8. An average day
9. Goals
10. Motivations
11. Buying criteria
12. Objections
13. “Ah-ha” moments
14. Why us?
15. Keywords
16. Recordings of interviews with real people from the persona group

from website.