Visioning ITM 734 Fall 2006 Corritore. 2 Visioning Goal – to create a vision of how your system will support your users’ work. * says what the new work.

Slides:



Advertisements
Similar presentations
A method for addressing any large problem. Carefully consider the problem. Define the problem. Ask yourself the following questions: What is it that I.
Advertisements

Time Management By Zahira Gonzalez.
Alberto Camacho Jessica George Maria Moya Rekeisha Scott Stephanie Williams Group B:
The design loop Integrated Technologies The Design Loop Grade 9 Integrated Technology.
Building Leadership Chapter 3
Presentation Skills: The Do’s & Don’ts. Overview Purpose (Why we give presentations) Structure (How we give presentations) Preparation (What do we need.
From Scenarios to Paper Prototypes Chapter 6 of About Face Defining requirements Defining the interaction framework.
How To Write A Speech Objectives: Use effective strategies to organize and to outline presentations, use effective verbal strategies in presentations,
The Basics of Team Building. What is A TEAM?  A Group of People Working Towards a Common Goal.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Logic and Problem Solving Advanced Computer Programming.
CQI (TQM) Tools and Time Management. CQI or TQM?? u CQI – Continuous Quality Improvement or u TQM – Total Quality Management Technically, there are some.
The UX Connection Driving Innovation on an Agile Project Hugh Beyer Cohealo.
Concepts and Prototypes CS584. Concepts (Conceptual Model) Pre-prototype. Explore how to address some aspect, eg: The interface metaphor (eg, desktop,...)
S556 Systems Analysis & Design Week 12: November 18, 2008.
Overview Prototyping and construction Conceptual design
Design, prototyping and construction CSSE371 Steve Chenoweth and Chandan Rupakheti (Chapter 11- Interaction Design Text)
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
| House of Leaves [day3] Schedule: 1.Attendance & Questions? 2.Twilight 3.Discussion groups 4.Large Group 5.Discussion groups, revisited 6.HW.
COMP 208/214/215/216 Lecture 3 Planning. Planning is the key to a successful project It is doubly important when multiple people are involved Plans are.
Mobile Aps: Agile Mentoring Review
Becoming A Mediator Nature of Conflict Types of Conflict Elements of Conflict Peer Mediation.
Communication & Collaboration Communicate Clearly  Articulate thoughts and ideas effectively using oral, written and nonverbal communication skills in.
Affinity Diagrams ITM 734 Fall 2006 Corritore. 2 Affinity diagrams Brings issues and insights about customers/users together  Fastest and best way Affinity.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design & Putting it Together Reading: ABF: Ch. 9 CD Ch.s 14, 15, 16,
Modeling Work and the Interpretation Session ITM 734 Fall 2006 Corritore.
PHIDD/Preliminary Team Idea Fall 2015 Northeastern University1 Title of your app Team name Team members Problem solved and impact on health? Answer here.
Storyboarding The Why and the How…. A set of drawings that represent screen layout sequences First used by filmmakers to plan the sequences of movie scenes.
© ABSL Power Solutions 2007 © STM Quality Limited STM Quality Limited Brainstorming TOTAL QUALITY MANAGEMENT Brainstorming.
Quality Tools. Decision Tree When to use it Use it when making important or complex decisions, to identify the course of action that will give the best.
UI Design without Prototypes ala Holtzblatt et al ITM 734 Fall 2006 Corritore.
Strategic Planning Prototype Feedback Cycle 2 March 2015.
Source : The Problem Learning and innovation skills increasingly are being recognized as the skills that separate students who are.
Z556 Systems Analysis & Design Session 10 ILS Z556 1.
Product design challenge Fall the theme  Any product that uses Computer Science to create it  Possible areas:  Safety  Entertainment  Family/relationships.
Overview of Writing/Illustrating a Story For LC Students.
Engineers create what has never existed!
1 Integrated Managing for Results Managing for Results: USAID Nigeria & IPs  Day 4: Performance Information Management.
© BLR ® —Business & Legal Resources 1408 Problem Solving For Supervisors.
Date : 04 Nov 2015 Web Design Fundamentals Planning and Documentation.
Users and Data Models CMPT 455/826 - Week 3, Day 2 (Various sources) Sept-Dec 2009 – w3d21.
Problem Solving Skills
Treboo-What? Ms. Stanton Pre-Calculus. Treboo-Shay… Yay!
/0904 © Business & Legal Reports, Inc. BLR’s Training Presentations Creative Problem-Solving.
Mr. Tanaka.  Task: Design the best cell phone holder ever!! Follow EDP.
Brainstorm Brainstorming involves bringing a group of people together to generate many different ideas. 9 Communicate Results Design Process 2 Brainstorm.
Writing a Science or Engineering Paper: It is just a story Frank Shipman Department of Computer Science Texas A&M University.
Overview Prototyping Construction Conceptual design Physical design Generating prototypes Tool support.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Be* Broadband Member Services Participatory Design Workshop.
PROBLEM SOLVING LEADERSHIP. 4 STEP PROCESS 1._________ 2._________ 3._________ 4._________.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design: Reading: CD Ch.s 14, 15, &16 Monday Midterm CS 321 Human-Computer.
BUS 1040 PROJECT MANAGEMENT Week 11 Agenda: Presentations Review Matrix Orgs. Monitoring and Problem Solving Close out continued and review. Final Group.
The Writing Process for Narrative Writing What is a Narrative?  A Narrative is prose that: Tells a story about a real or fictional event Develops a.
Creating Effective Assignments and Activities Barbara Tewksbury Hamilton College
User Stories- 2 Advanced Software Engineering Dr Nuha El-Khalili.
TEAM BUILDING. WHY IS TEAM BUILDING IMPORTANT? YOUR ABILITY TO GET ALONG WITH OTHER PEOPLE, AND USING TEAMWORK WILL LARGELY DETERMINE HOW SUCCESSFUL YOU.
University of Washington HCDE 418 Storyboarding HCDE 418 Winter 2014.
Concepts of Engineering Module 2 Test Review. Review Questions Design problems are broken down into sub- problems because smaller problems must be solved.
Team Contracts We can work together! Copyright © Texas Education Agency, All rights reserved. 1.
Medium-fi Prototyping
Creating Animations in Alice
Unit 1: Science, Technology and Engineering
Coaching through challenges
Software Quality Engineering
Teamwork and Problem Solving टीमवर्क आणि समस्या सोडवणे
Introducing the Ideas One of Six Traits:
Practical tools for conflict resolution
Creative Design Solutions: Design Thinking
Tiffany Ong, Rushali Patel, Colin Dolese, Joseph Lim
1.02 Creative Design Solutions: Design Thinking
Presentation transcript:

Visioning ITM 734 Fall 2006 Corritore

2 Visioning Goal – to create a vision of how your system will support your users’ work. * says what the new work practice will be but not how it will be implemented. What it is: hand-drawn graphical representation of a hi-level story of the personas’ new practice told from users’ point of view

3 Concepts Tell the story of what the new life will be like if you introduce the new system Grounded brainstorming and story-telling  Grounded: walk the data beforehand  Brainstorm: within data, present any idea that occurs without evaluation  Story-telling: weave a story of how the personas address the issues identified to accomplish the tasks from the sequences. Told from perspective of user, builds from one person to the next Sketch on flipchart  Hi-level (widgets) Generate multiple visions, one at a time  No evaluation as generate

4 Overall Process Create 3-4 visions on flipchart Evaluate each vision – ID what works and doesn’t ( + and - ) Take good parts of each vision, overcome bad parts, create final consolidated vision

5 Create a vision: the roles The Pen – person drawing the vision  Talk to the Pen  In service of the team (cannot contribute and don’t filter)  Encourage others to talk  Weave ideas into the vision The Poker – keeps on eye on issues team needs to consider – reminds them in the lulls

6 Create a vision Consolidate the ‘hot ideas’ Vote which to start with Label flipsheet with hot idea Pen asks “who am I and what am I doing” Start from the hot idea  Work out details in Storyboarding, not here  Evaluate in later step Develop a coherent story about the redesigned work  Each team member chimes in and builds Conflicting ideas – written off to Hot Ideas list for later visioning OK to be too big for first version – can cut down later

7 So now what? End up with 3-4 visions  Each represents different focus of the work, different design directions  Treat each vision as a collection of options (like a database of design ideas for the project) Synthesize a new solution incorporating the best of each vision  Don’t compromise – synthesize!

8 Evaluation of visions For each vision  List positive points of all Reasons it is good, fits the customer work, solves real problems, easy to build Attach to the vision  Negative points of all Why it would be hard to build or would break customers work practice Attach to the vision  If come up with fixes for the negatives, attach with post-its for later use (put on post-its and post when done by the negative – don’t discuss)

9 Evaluation of visions (cont.) Look at positives across all visions  How combine these into a coherent whole?  Add in fixes for negatives Create/draw a new consolidated vision Write a narrative of the new vision

10 Examples Pg Holtzblatt et al handout