Created Persona 4: Jim (The Observing Auditor) (markdown)

Persona-4:-Jim-(The-Observing-Auditor).md

@@ -0,0 +1,114 @@
+Persona4_Acc/Sec_Jim
+
+
+
+Jim - The Observing Auditor
+
+Experience: 			Senior
+Specialisation:		Data Analyst 
+
+
+
+A data analyst who doesn’t provision any instances or has much “hands on” interaction, but spends a lot of time on the platform ‘observing things’ - he is more of an audit user; he logs on to pull usage and billing data mostly, but also does has account management access and responsibilities, such as billing and occasionally team members and people management. 
+
+Needs:			To be notified when costs are spiralling
+Clear understanding of costs and billing
+Easily be able to change pay details
+				Easy permissions and access management
+Easy “house keeping” and admin
+View resources by policy - “What's publicly exposed on the internet?”
+
+Wants: 			Raise questions about data and point it at the right
+person
+				To be able to understand the platform-architecture 
+				Understand what is exposed where
+				To understand if a user caused a failure 
+
+Worries:			Not being able to quickly pick up how to use new
+tools
+			Not knowing when something has gone wrong
+			Complicated pricing structures 
+				Unclear and complicated UI
+
+We should (Our opportunity): 
+
+Help him to quickly get his head around the platform
+Allow him to easily see and pull the data that he is after
+Give clear indications of running costs
+Allow him to easily manage billing
+Make sure that his time on the platform feels like time well spent - good customer experience, assistance and communication
+Make sure he gains confidence in the tool and in Joyent
+
+
+Scenario:
+
+Jim receives his usual monthly report/ review via email. He follows the link in the email to check that all is ok. Once on the PROJECT LIST, he notices that one of the Projects in TESTING  environment has  a much higher monthly cost than the other.  He believes this is something that ought to be pointed out and raised to someone who can look into it. 
+Not too sure how to this, he opens “Support and Learn, where he reads about Flags. 
+He decides to RAISE A FLAG about this to Nicola. 
+
+
+Flow: 
+
+Action
+View
+Receives a monthly report via email
+Email
+Clicks on email link
+Email
+Goes to the organisation dashboard described in email
+Organisation dashboard (lists projects with price/hour and shows changes to monthly spend)
+Views (at least) three projects: 
+Production Price OK, 
+Test 1 Price OK, 
+Test 2 Price High 
+
+Organisation landing page
+
+(Use what we have but tweak)
+Why is one testing very high?
+Project landing page
+Open project 
+Project Landing Page
+
+(Change values to suit “Testing” project and name)
+Checks the price
+Project Landing Page - maybe more detailed price section
+Flags price in quick actions - now someone else job
+Project Landing Page - quick actions opened and flag placed on project
+
+(Potential item in quick action???)
+
+
+Visuals of journey (screenflow): 
+ 
+Pdf link: 
+TBC
+
+Marvel App link: 
+TBC
+
+
+Updated step by step journey: 
+
+Jim’s narrative
+- Receives an email invoice
+-Clicks on the Organisation link (BizTech)
+- Lands on Org dashboard - 4 projects 
+  - p1 in testing
+  - p2 in production
+  - p3 in testing
+  - p4 in production
+- changes “cost per day” to “per month”
+- Thinks p1 looks a bit pricey for testing only
+- opens each project to compare what is there
+- notices that p1 in testing might have too many instances for testing - What to do??
+- opens “Support and Learn” for help
+- reads about “Flags”
+- Creates a flag and sends to Nicola - “Do we need all these instances here?"
+- closes “Support and Learn
+- Flag sits on the dashboard “Raised bu Jim to Nicola…”
+
+
+AJ’s notes on video:
+Not convinced that the ‘Support and Learn’ is implemented correctly. Better to have tooltips than a huge amount of text.. (possibly)
+