NivenPrasad
commented
4 years ago 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
ExperimentsInHonesty
Overview
We need to know who we are designing this website for
Action Items
Resources/Instructions
https://github.com/100Automations/Website/blob/master/100Automations_Project_One_Sheet.pdf
User Journey Mapping Doc