REALITY CHECK. Fabienne Schoeman UI/UX Design

Transcription

1 UX considerations for the development of SaaS applications REALITY CHECK Fabienne Schoeman UI/UX Design

2

3 IBM Design Thinking Hills focus your project On big problems and outcomes for users, Not just a list features requests. Sponsor Users help your design expriences fo real target users, rather than imagined needs. Playbacks align your team, stakeholders, and clients around the user value you will deliver, rather than line items.

4 Where we come from USABILITY DESIGN SOFTWARE DEVELOPMENT Executive Feedback USER TEST 1 YEAR

5 What we do now SPRINT 1 SPRINT 2 SPRINT 3 SPRINT 4 SPRINT 5 SPRINT 6 User Research Low Fidelity vison design DESIGN DESIGN DESIGN DESIGN DESIGN DESIGN PLAYBACK PLAYBACK PLAYBACK PLAYBACK PLAYBACK PLAYBACK 6 WEEKs 1 WEEK 1 WEEK 1 WEEK 1 WEEK 1 WEEK 1 WEEK

6 What do we gain On Premise SaaS INSTALL UPDATE MIGRATE USE CUSTOMIZE USE

7 What changed On Premise BUY CUSTOMIZE EDUCATE USE SaaS GOOGLE BUY USE

8

9 GETTING STARTED Do you want to learn about IBM Runbook Automation? Learn what this is all about! RESOURCES Learn from others and share your experience. What is IBM Runbook Automation? How does Runbook Automation work with other IBM products? Start using IBM Runbook Automation Watch a video or walk through a tutorial to get an idea of what Runbook Automation is all about! Simplify your daily operational jobs by using runbooks. My Runbooks Documentation Share your experience and provide runbooks. Add Runbook Documentation Create a new version of a runbook. Edit Runbooks Documentation Create a trigger and match it to an existing runbook. Add Trigger Documentation Create a new connection. Add Connection Documentation Automate repetitive tasks. Add Automation Documentation

10 What happens

11

12 IBM RunBook Automation RELEASE BLUEPRINT:

13 Starting in Nov 2014 we need Beta availability for InterConnect 2015 Produced end to end Vision UX storyboard Reviewed and improved with constant customer sessions Key UX capabilities used to seed a sprint plan over few months Weekly agile development, keeping UX design 1-2 weeks ahead of dev The development team has been incredible at delivering what we dream up

14 Challenges Faced Making it ridiculously easy to create and use runbook automations.

15 Hills HILL 1 A service delivery engineer can define a runbook to automate a response to an event or incident, and link it to an event in less than 2 hours including test. HILL 2 An operations analyst gets all the information she needs to promptly react to an event in the context of the event, in less than 10 minutes and without manual log-in to remote endpoints. HILL 3 A war room team, SME, or analyst in any problem resolution activity, can create a runbook automation from collaboration interactions and selected automations in less than 2 hours.

16 Demo Scenario HILL 1 HILL 2 HILL 1 Brock creates runbooks Annette runs runbooks driven by the events Brock creates a trigger to map events with the machting runbooks

17 Demo Scenario Hill 1 Brock Service Delivery Engineer Brock creates a runbook to help operators to clean up the Linux filesystem. Using the runbook, operators can work faster, without help from their collegues, and much more reliable. Brock runs the following steps: 1. Brock adds a new runbook. 2. He writes down the stepwise description using steps, parameters, and automations. 3. He saves the runbook as draft and asks Jim (Subject Matter Expert) to review the runbook. 4. Once approved, he publishes the runbook and writes an to all operators to notify them.

18

19 Hill 2 Making it ridiculously easy to reduce noise, delegate problems faster and more efficiently. An operations analyst gets all the information she needs to promptly react to an event in the context of the event, in less than 10 minutes and without manual log-in to remote endpoints. Annette Operations Analyst

20 Demo Scenario Hill 2 Annette Operations Analyst Annette is sitting in her office, monitoring the events. She figures out, that the Linux filesystem sends an event, that the filesystem needs to be cleaned up. She takes the following actions: 1. She opens the context menu. Here she can find the entry Runbooks. 2. In the submenu of Runbooks, she can find all the runbooks that are related by an trigger to this event. She picks Runbooks -> Clean up Linux file system 3. As this is a manual runbook, the details of the runbook opens and she has to enter the parameter values. 4. Then she runs the runbook. At the end, she provides a rating and comment for future use.

21

22 Hill 1 Making it ridiculously easy to diagnose and fix problems faster, and build operational knowledge. A service delivery engineer can define a runbook to automate a response to an event or incident, and link it to an event in less than 2 hours including test. Brock Service Delivery Engineer

23 Hill 1 Brock Service Delivery Engineer Annette asked Brock to create a Trigger for the event that indicates, that the Linux filesystem needs to be cleaned up. As she is running into this use case on a frequent base, the trigger matches events to the runbook that solves the issue. Brock runs the following steps: 1.Brock opens the Manage Trigger page and adds a new Trigger. 2.He specifies the query to run over the event summary field. 3.He picks the related runbook Clean up Linux filesystem.