A Cognitive Perspective On Boundary- Spanning IS Design Dr. Susan Gasson Assistant Professor College of IS & T Drexel University.

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

Analyzing Student Work
Management, Leadership, & Internal Organization………..
The Research Process.
Systems Development Environment
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
 Distributed Cognition emphasizes the distributed nature of cognitive phenomena across individuals, artifacts, and representations that are both internal.
Improving Your Business Results Six Sigma Qualtec Six Sigma Qualtec Six Sigma Qualtec – All Rights Reserved June 26, 2002 BEYOND SIX SIGMA: A HOLISTIC.
William H. Bowers – Understanding Users: Qualitative Research Cooper 4.
Collaboration, Trust and Knowledge Sharing in Information Technology Intensive Projects Luis Luna October, 2002.
Analytical methods for Information Systems Professionals
7 Chapter Management, Leadership, and the Internal Organization
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Supporting Design Managing complexity of designing Expressing ideas Testing ideas Quality assurance.
Unit 8: Tests, Training, and Exercises Unit Introduction and Overview Unit objectives:  Define and explain the terms tests, training, and exercises. 
Analysis Concepts and Principles
Copyright c 2001 The McGraw-Hill Companies, Inc.1 Chapter 4 Introduction to Qualitative Research Effective in capturing complexity of communication phenomena.
System Analysis System Analysis - Mr. Ahmad Al-Ghoul System Analysis and Design.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
1 Computer Systems & Architecture Lesson 1 1. The Architecture Business Cycle.
E-business competencies in SMEs Conceptual model and empirical results HØGSKOLEN I AGDER Agder University College Dr. Dag H. Olsen Agder University College.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Certified Business Process Professional (CBPP®) Exam Overview
Requirements Engineering Process – 1
socio-organizational issues and stakeholder requirements
User Experience Design Goes Agile in Lean Transformation – A Case Study (2012 Agile Conference) Minna Isomursu, Andrey Sirotkin (VTT Technical Research.
Organizational Learning (OL)
© 2006 by The McGraw-Hill Companies, Inc. All rights reserved. 1 Chapter 4 Introduction to Qualitative Research Effective in capturing complexity of communication.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
What is Business Analysis Planning & Monitoring?
Systems Analysis and Design: The Big Picture
Delmar Learning Copyright © 2003 Delmar Learning, a Thomson Learning company Nursing Leadership & Management Patricia Kelly-Heidenthal
Teachers mentoring teachers: A process of reflection and rejuvenation
Software testing and development for intended quality Tero Pesonen.
Unit 5:Elements of A Viable COOP Capability (cont.)  Define and explain the terms tests, training, and exercises (TT&E)  Explain the importance of a.
Towards an activity-oriented and context-aware collaborative working environments Presented by: Ince T Wangsa Supervised by:
Qualitative Research. When to do qualitative research  Cognitive research strategies tend to vary as a function of theory development. The earlier stages.
Qualitative Analysis Information Studies Division Research Workshop Elisabeth Logan.
Long-term twinning seconding and young talents’ involvement for the improvement of land administration development projects Fredrik Zetterquist Managing.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
OUR MODULES A Virtual On-line Institute of Interprofessional Education P. Solomon 1, S. Baptiste 1, P. Hall 2, R. Luke 3, C. Orchard 4, E. Rukholm 5, L.Carter.
“POLICY PSYCHOLOGY”: Social Psychology Perspectives of Policy Analysis & Stakeholder Communication Harn Wei Kua Dept. of Building, National University.
Elizabeth Godfrey 1.  Periodic assessment of results Appropriateness, effectiveness, efficiency, impact, sustainability  Identifies intended and unintended.
Chapter 11: Qualitative and Mixed-Method Research Design
A COMPETENCY APPROACH TO HUMAN RESOURCE MANAGEMENT
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
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.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
HOW TO WRITE RESEARCH PROPOSAL BY DR. NIK MAHERAN NIK MUHAMMAD.
Communications Skills (ELE 205)
Chapter 6 Team Work Blueprint By Lec.Hadeel Qasaimeh.
School Improvement Partnership Programme: Summary of interim findings March 2014.
Communications Skills (ELE 205) Dr. Ahmad Dagamseh Dr. Ahmad Dagamseh.
Open and Collaborative Innovation in US Healthcare: The Case of Health Insurance Exchange (HIX), Sudeep Krishnan, IIM Ahmedabad (IIMA), ICEIM 2014, Durban, SA, Conference Presentation
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Networks of Public Accounts Committees: Approaches to Capacity Building Mitchell O’Brien Governance Specialist Team Lead – Parliamentary Strengthening.
Staff All Surveys Questions 1-27 n=45 surveys Strongly Disagree Disagree Neutral Agree Strongly Agree The relative sizes of the colored bars in the chart.
New Product Development Page 1 Teddy Concurrent Engineering by Teddy Sjafrizal.
© 2005 Prentice-Hall, Inc. 6-1 Chapter 6 Groups and Teams.
Systems Analyst (Module V) Ashima Wadhwa. The Systems Analyst - A Key Resource Many organizations consider information systems and computer applications.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Requirement Elicitation Nisa’ul Hafidhoh Teknik Informatika
Organization and Knowledge Management
Chapter 6 Groups and Teams
Systems Analysis and Design
Action learning Session Two
Student Teaching Handbook as Boundary Crosser
Presentation transcript:

A Cognitive Perspective On Boundary- Spanning IS Design Dr. Susan Gasson Assistant Professor College of IS & T Drexel University

An Investigation of Boundary-Spanning IS Design  The nature of organizational IS design and the role of boundary-spanning knowledge management in high-level design.  Traditional (decompositional) process model vs. convergence model of design process.  Three views of design as social cognition.  Research study: participant observation and ethnographic data collection of boundary-spanning design process in organizational context over period of 18 months.  [If time] SSM as a tool for surfacing implicit understanding.  Research findings: the nature of a boundary-spanning design process.

Boundary-Spanning, Enterprise-Level IS Design  Organizational IS design is viewed here as a high-level, conceptualization process:  The giving of form to an organizational IS  Involves the co-design of business and IT systems  Distinct from the low-level “design” stage of SDLC.  Involves knowledge sharing and negotiation of consensus across multiple knowledge domains or organizational boundaries. Product engineering manager Financial accounting manager IS manager Bid process manager Marketing manager Operations finance manager Extent of shared understanding

Traditional Model Of Design Process  Individual, rational model of problem-solving (Alexander, 1964).  Assumes consensual, objectively-defined set of initial goals (Simon, 1973).  Empirical studies reveal emergent strategies:  “Opportunism” of expert software designers (Guindon, 1990).  “Improvisation” in designing IT-related organizational change (Orlikowski, 1996). Consensus on organizational problem and goals for change Agreed form of IS solution Gap analysis: process of design

Convergence Model of Design No longer goal-driven, but continual evolution of “gap analysis” between how we understand (frame) the problem and how we understand (frame) the solution.

Research Question  Does the convergence model offer a convincing alternative to the decompositional model of design and, if so, how does the convergence of problem- and solution-space take place in boundary-spanning group design?

Boundary-Spanning IS Design Process Convergence model still deals with individual processes – does this explain collaborative process? People are members of multiple social worlds, through their membership of different work and disciplinary groups (Strauss, 1983; Vickers, 1974). Organizational "problems" not consensual but emerge through interactions between the various social worlds to which decision-makers belong (Suchman, 1998; Weick, 1998).  Therefore, we need to examine processes of social cognition, to understand collaborative design process.

3 Views Of Social Cognition  Socially-situated cognition:  Situated action (Suchman, 1987; 1998): shared work-spaces are produced through social and contextual interaction; continually redefined.  Cognitive “frame” (Goffman, 1974) – “structures of expectation” guide how people predict and interpret context (Tannen, 1993).  Socially-shared cognition:  Shared frames: cognitive "shortcuts" provide shared interpretations of organization without the need for complex explanations (Boland and Tenkasi, 1995; Fiol, 1994).  Congruence between “technological frames” (Orlikowski & Gash, 1994).  Distributed cognition (Hutchins, 1995):  Understanding is not so much shared between, as "stretched over" members of a cooperative group (Star, 1989).  Coordination achieved through “heedful interrelating” (Weick & Roberts, 1993).

Research Questions  Does the convergence model offer a convincing alternative to the decompositional model of design and, if so, how does the convergence of problem- and solution-space take place in boundary-spanning group design?  IS design as socially situated cognition:  How do individuals' design frames interact, to form a group "framing" of an information system?  IS design as socially-shared cognition:  Does a design group develop a shared design-frame over time? If so, what aspects of the design are shared?  IS design as distributed cognition:  How does a boundary-spanning design group manage and mediate distributed design understanding?

Boundary-Spanning Collaboration in The Co-Design of Business and IT Systems Technical division Bid response Core design team Bid response Bid response Bid response Bid response Product/ customer strategy Customer interface & intelligence Financial strategy Product development Cost/effort estimation Production capacity planning Contractual policy  Commercial division Finance division Operations division Marketing division Participant observation & ethnographic data collection of group of 7 managers involved in design of IS to support the process of responding to customer invitations to bid for new business: IS Manager Process Improvement Manager

Framing in IS Literature  Concept comes from cognitive psychology  Orlikowski & Gash (1994) used concept of “Technological Frames” to represent different understandings of the role of technology in work.  Davidson (1996, 2002) extended concept to understand how IT system stakeholders understood what IT is required and the role that this would play.  Problem of granularity: this is behavioral and not cognitive research:  Frame congruence (Orlikowski & Gash, 1994) – frames are similar in content and structure (qualitatively coded).  Problem of explicit vs. implicit knowledge about IS:  Framing involves implicit knowledge, so employed Soft Systems Methodology (Checkland, 1981) to elicit.

Data Analysis Methods 1.Qualitative coding of “levels of problem decomposition”  Analyze goal-orientation and decompositional focus of group process  Qualitative coding of “contributions” to design meetings at 4 points, distributed throughout design project. 2.Qualitative coding of in-depth interviews, based on SSM (Checkland, 1981), to derive design “framing” concepts employed by individuals. 3.Discourse analysis of design meeting transcripts to understand how distributed understanding was managed.

Research Question  Does the convergence model offer a convincing alternative to the decompositional model of design and, if so, how does the convergence of problem- and solution-space take place in boundary-spanning group design?

Design Was Not Decompositional High-level design goals Detailed implementation mechanisms Predicted Actual Simulated Single Meeting

Research Questions  Does the convergence model offer a convincing alternative to the decompositional model of design and, if so, how does the convergence of problem- and solution-space take place in boundary-spanning group design?  Sub-questions, from a “framing” perspective:  How do individuals' design frames interact, to form a group "framing" of an information system?  Does a design group develop a shared design-frame over time? If so, what aspects of the design are shared?  How does a boundary-spanning design group manage and mediate distributed cognition?

Data Analysis Methods 2.Discourse analysis, to derive design “framing” concepts employed by individuals  Data collected (in interactive interviews) at 3 points:  beginning,  middle (approx.), and  end of design project  Interview questions focused on 3 aspects of design, reflecting the 3 elements of the convergence model:  Problem-framing  Solution-framing (target system goals and form)  Process-tasks required to get from problem to solution (gap analysis)  Employed Soft Systems Methodology techniques (Checkland, 1981) in interviews, to surface implicit frames/understandings.

SSM Goal Surfacing: 6 Definitions of “Achieve Higher Quality In Bid Process”

Example SSM Root Definition For Process-Task Root Definition: A system owned by the Managing Director where the Team leader identifies which processes need analyzing and obtain resources for this for the benefit of the people who operate the Bid response process and customers. This is necessary because the Bid response process is bound up in other business processes. It is constrained by the subsequent impact on wider processes which interface with any process that interfaces with the Bid process.

How do individuals' design frames interact, to form a group "framing" of an information system?  Organizational problem frames  noticeable convergence of individuals’ framing-perspectives.  Target system goals  converged to some extent towards the middle of the project  appeared to converge superficially towards the end  use of common metaphors, e.g. "electronic document library"  but differed widely in meanings attached to metaphors  overall, little convergence at the level of individual understanding  Design tasks required (gap analysis)  diverged widely at all stages. Product engineering manager Financial accounting manager IS manager Bid process manager Marketing manager Operations finance manager Extent of shared understanding

Does a design group develop a shared design-frame over time? If so, what aspects of the design are shared?  The use of shared metaphors in defining system goals or aspects of a solution did not indicate a shared understanding of what those goals/solutions entailed.  What was shared was an understanding of how the problem on which the group was focusing was structured  e.g. the use of the phrase “the big-arrow, little-arrow concept” indicated a shared understanding that the team’s problem was to find a way of defining the Bid process so that it was aligned with, but separate and parallel to the product lifecycle process.  But problem definitions were discarded when they caused perceived dissonance with individual frames.  Replaced by more sophisticated problem-structure that embodied some elements of previous structure, but also replaced other elements.

Does a design group develop a shared design-frame over time? If so, what aspects of the design are shared? Very different from the traditional model, design was driven by shared problem-frames, not shared goals.

How does a boundary-spanning design group manage and mediate distributed design understanding?  Through understanding problems in common, the group was able to develop sufficient levels of trust that they could delegate responsibility for parts of the solution definition, when this was too complex for one person to understand in detail:  "I know that Peter wants to fix the same things that I want to fix, so I'll trust him to sort out his end of the system [personnel training]".

How Do Groups Manage Distributed Knowledge In Design?  Shared attitudes and beliefs towards the design (why are we doing this and how do we want to change the company? – built through developing shared problem-structures) guide shared interpretations of the organizational environment.  This permits groups to negotiate distributed understanding of design tasks and how to perform them.  Negotiation is facilitated by the use of boundary objects (e.g. design models), that capture and communicate a joint knowledge of the design that is greater than the knowledge of any individual.  Knowledge of who knows what allows group to distribute work effectively among themselves.  Appears to be established through individual “specialization” in specific application-domain areas, during the design process.

Research Question  Does the convergence model offer a convincing alternative to the decompositional model of design and, if so, how does the convergence of problem- and solution-space take place in boundary-spanning group design?

Questions?