Created Persona 2: Jorge (The Aware Explorer) (markdown)

ajones5876 2017-01-26 16:44:11 +00:00
parent 5ac1decd04
commit 1a5c14d0ca

@ -0,0 +1,98 @@
Persona2_Dev_Jorge
1
Jorge - The Aware Explorer
Experience: Mid level
Specialisation: Fullstack
UI-”to begin with” developer (onboards using the UI) “of now” - actively tracks new technological trends, and is interested in learning how to use them and, as such has some container experience, though not much. Went from frontend to backend.
Could easily be the one to bring a new tool to the company he is long-term freelancing for.
Mainly uses the CLI, but if it proves too much trouble, he will pop back into the UI every now and then.
Needs: Quick and straightforward setup
Clear overview of what is going on - mental model of App
Easily do rollbacks and updates (and take other actions)
Wants: Be able to easily test new Code
Be challenged and learn new things
Worries: Over complicated and unnecessary UI
Not being able to quickly pick up how to use new tools
Inconsistent support-documentation and information
Boring and dull new technologies
We should (Our opportunity):
Give contextual, consistent and intelligent education
Give non-intrusive indications of alternative and easier ways to complete his tasks
Give clear signs on how to explore further
Show what happens when trying something new out
“Open up and unwrap” the tool in stages to keep it interesting
Scenario:
Jorge hears about Joyent through word of mouth and decides to check it out. He signs up and plays around with the Educational Dummy Project; decides to try out ROLLBACK
Flow:
Action
View
Register and Signs Up with an email address and no Two Factor Auth
Sign Up Process (need to add GitLab)
Skips billing details
Sign Up Process
Adds SSH Key
Sign Up Process
Finishes sign up and goes to being logged in
Individual User Dashboard, with prompts to create Orgs, Projects etc
(Tweak of organisation dashboard and add demo project feature)
Opt 1: Creates Own Project
Opt 2: Takes a walk through of demo project (View Only)
Chooses Opt 2.
Default Demo Project page view (topology of services), with all services running healthy
(Use Wordpress wireframes but change status or services, icons etc)
Toggles between project service views:
Topology
List Services
List Instances
Project Landing page in three view options
(Most components are already there but need to be copied to correct screens and tweaked)
Reads micro copy that suggests to create a issue with the service
Clicks “create issue” CTA
Rollbacks a service (a scenario of why this might be needed is presented using an educational component)
Select a version, confirm selection
(Components need to match WordPress example)
Rollbacks a project
Is the rollback happening? Did the service rollback? Did the project rollback? Did it help? How have the metrics been effected?
Project Landing Page with progress taking place, then the metrics from the changed “thing”
Visuals of journey (screenflow):
Pdf link:
https://drive.google.com/drive/folders/0B3yOoMWyvxlAT1JkZE1CLVV2aEE?usp=sharing
Marvel App link:
TBC