Adam Sawyer, Orion Health.  In an industry that has so few barriers, so much scope – why do we have so few interaction designers? Why do.

Slides:



Advertisements
Similar presentations
The Commitment Initial training will centre around short, foundation training in the theory and practice of sustainability as related to the Water Corporation.
Advertisements

The right tools for the job How to choose a web / bespoke development company.
References Prof. Saul Greenberg, University of Calgary, notes and articles INUSE 6.2 and RESPECT 5.3 Handbook Prof. , University of , Notes and articles.
Note: Lists provided by the Conference Board of Canada
Systems Development Environment
Agile Usability Testing Methods
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
HFSD Methods Nov HFSD Methods Objectives –To consider types of systems –To characterise methods for HF input into SD –To identify HF contributions.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
Requirements Engineering Process – 1
Lecture 3 Strategic Planning for IT Projects (Chapter 7)
Remedy, a BMC Software company Storyboarding the User Interface: Blueprint for an Application Shanaz Kanga | Michele Sarko Sr. UI Design Engineer | Manager,
Quality Management for the Localization of Marketing Texts.
Product Management & User Experience: Are they the right career paths for you? Rob Houser Sr Director, Product Sage.
Effective Methods for Software and Systems Integration
Keys to Developing a Winning STAR Story Presented by: Natalie Ackerman.
Copyright Course Technology 1999
Thinking Actively in a Social Context T A S C.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
William H. Bowers – Modeling Users: Personas and Goals Cooper 5.
Principles of User Centred Design Howell Istance.
Central concepts:  Assessment can measure habits of mind or habits of recall.  Tests have their limits.  It is important to know the purpose the test.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Quality Directions Australia Improving clinical risk management systems: Root Cause Analysis.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 3 Project Management for Strategic Goal Achievement.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
Industrial Software Project Management Some views on project managing industrial and business software projects.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
1 5.1 Software Engineering Practice  Provide value to the user  KIS—keep it simple!  Maintain the product and project “vision”  What you produce,
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Interaction Design Research to Industry Peter Reid.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
IT Job Roles & Responsibilities Shannon Ciriaco Unit 2:
Chapter 9 Design guidance and design rationale. UIDE Chapter 9 Sources of Design Guidance Standards Standards –User interface standard Design Guidelines.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Team Skill 6: Building the Right System Assessing Requirements Quality (29)
Systems Development Life Cycle
By Germaine Cheung Hong Kong Computer Institute
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Demonstrate employability skills required by business and industry.  The following elements should be integrated throughout the content of this course.
1CS 338: Graphical User Interfaces. Dario Salvucci, Drexel University. Lecture 7: Principles and Patterns.
CSPC 464 Fall 2014 Son Nguyen.  Attendance/Roster  Introduction ◦ Instructor ◦ Students  Syllabus  Q & A.
Smart Home Technologies
UELSU Programme Representatives Using your experience to demonstrate key skills Wed 25 th Nov 2015.
Software Engineering Principles Practical Advice and Steps for Managing Your Project.
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
UML - Development Process 1 Software Development Process Using UML.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Safety methods within Agile and RUP methods TORGRIM LAURITSEN BUCS project.
Multimedia Industry Knowledge CUFGEN01A Develop And Apply Industry Knowledge CUFMEM08A Apply Principles Of Instructional Design To A Multimedia Product.
© 2013 by Nelson Education1 Selection III: Interviewing.
Software Design and Development Development Methodoligies Computing Science.
MANAGEMENT INFORMATION SYSTEM
Flight Software Conference 2016
(Professional Business Analyst Training organisation)
Requirements Analysis Scenes
It’s not all about the tool!
Building the foundations for innovation
Gathering Systems Requirements
Requirements Engineering Process – 1
Gathering Systems Requirements
Presentation transcript:

Adam Sawyer, Orion Health

 In an industry that has so few barriers, so much scope – why do we have so few interaction designers? Why do so few companies employ it, and those that do, clearly show the point of difference?  Lots of other industries have discovered design as a solution ◦ Do engine builders design cars? ◦ Do builders design houses

 Design gives us beautiful buildings, stunning tools, elegant typography and aesthetic beautiful to use furniture.  So what happens when an electronic device is designed beautifully?

Are we getting closer?

 Intro to Orion and Adam done  What is design - done  What are the challenges of design? How do software companies traditionally design?  What do software companies do?  What’s it like to be international?  What makes an interaction designer

  A company of nearly 300 people, based in Auckland, with offices in USA, Canada, Australia, UK and Spain.  We make software that allows clinicians to access information which means patients get treated better  Wholly New Zealand owned, fabulous place to work

 Started life as a geomorphologist (I know about rocks in rivers, you can ask me later) in the UK  Went into Health IT management in Auckland  Moved onto Health software design  …..

 Intro to Orion and Adam  What is design  What are the challenges of design? How do software companies traditionally design?  What do software companies do?  What’s it like to be international?  What makes an interaction designer

 Cooper – About Face, Inmates are running the Asylum  Donald Norman – the design of everyday things  Bruce Tognazzini – first principals of interaction design

 In this context lets talk interaction design of a software application in a complex environment consisting of people, places, space, information  How a user feels, how he works, how this interface affects his day

 Systematic  Dynamic  Scientific  Creative  Involving  Communicative

 A guess

 It is purposeful and helps people to achieve goals  It makes people feel competent and..  It stops users feeling dumb..  It is elegant and the simplest complete solution  It makes products great to use

 Creates rigour  Creates auditable outcomes  Creates great artifacts Actually solves the problem at hand, not some theoretical one in the developers/salespersons mind. The CEOs favourite widget……

1. Clarify business requirements and conduct user research 2. Modeling users as personas 3. Requirements of personas 4. Create the design framework and boundaries 5. Refine design and leave artifacts for developers 6. Contribute to development process

 Users are generally unable to tell you what they require, customers even less  Requirements need to be defined based on business goals  Neither business stakeholders nor developers are capable of elucidating this  An end-to-end designer is tasked with capturing this information

 Research has its emphasis on qualitative  Based on interviews and time with users in their environment  Specifically not self-referential nor leading

 Identify usage patterns of researched users  Analyse workflows  Assess work environment and technical factors  Create personas (archetypal users representing the needs of many) and identify and write down their goals  Review with stakeholders

 Identify risks  Construct scenarios  Create lists of functional needs  Review with stakeholders  Make trade off decisions on major requirements

When I create/read an alert I want to capture/see meaningful information about the alert, so myself and other users can assess its significance. User Story Scenario Day 2 The operation to correct Clive's leg proceeds as planned and there are no complications. Just before the operation, the anaesthetist, Dr Slumberpond reads Clive's clinical record and it is highlighted on the screen that a clinical alert exists for Clive. Dr Slumberpond, therefore checks these to ensure that the drugs she is going to give Clive won't cause an adverse event.

 Define the data objects  Define the functional elements  Sketch and iterate elements  Develop visual style  Review with stakeholders A guide to ensure clarity of communication, demonstrating visual and user style of product Style guide

 Iterate through more detailed scenarios  Work closely with development to ensure feasibility  Illustrate every detail, pixel and control on screen  Develop a visual style guide  Conduct usability testing  Create form and behavior specification  Document, communicate, Illustrate

 Design consultation on issues as they arise  Maintain quality throughout  Assure development trade offs are appropriate and negotiate with stakeholders

Not Waterfall, Not Agile, and not prescriptive of a development methodology Design Development Time Effort

 Intro to Orion and Adam  What is design  What are the challenges of design? How do software companies traditionally design?  What do software companies do?  What’s it like to be international?  What makes an interaction designer

 Time vs Quality: Companies naturally need cashflow to survive, and sector is faster moving than say, furniture making….  Access to subjects: How to access our users without being a provider?  Finding specialist designers: skilled designers with BA skills, creative thinking skills that can be applied to the user interface are very rare

 Intro to Orion and Adam  What is design  What are the challenges of design? How do software companies traditionally design?  What do software companies do?  What’s it like to be international?  What makes an interaction designer

 OrionHealth lives by its values – we want to make a difference to the lives of the clinicians and patients  Support teams, 24:7, Marketing, Sales, Consulting, Professional onsite installation, web development, java development, design, testing, integration, finance, …..even IT!  Ongoing products as well as bespoke development.

 Intro to Orion and Adam  What is design  What are the challenges of design? How do software companies traditionally design?  What do software companies do?  What’s it like to be international?  What makes an interaction designer

 An International company is an one exciting to work in, meeting new professionals, opening new markets  Health is a sector that brings the best from staff, the challenge is making our teams empathetic to our end users  How do you run medical software in the Spanish islands?

 Intro to Orion and Adam  What is design  What are the challenges of design? How do software companies traditionally design?  What do software companies do?  What’s it like to be international?  What makes an interaction designer

 Insightful – can you look beyond the actual to find the goal?  Listener –can you listen to the hidden cues?  Creative – can you invent? Can you create a solution from a parallel industry?  Technical…….?  Organised – Must be able to follow process and be iterative through this  Systematic – its just too easy to skip to the design and build part

 Questions  If this is you…..