In this module you will study a real world ethical problem, the Toysmart case, and employ frameworks based on the software development cycle to (1) specify ethical and technical problems, (2) generate solutions that integrate ethical value, (3) test these solutions, and (4) implement them over situation-based constraints. This module will provide you with an opportunity to practice integrating ethical considerations into real world decision-making and problem-solving in business and computing. This whole approach is based on an analogy between ethics and design (Whitbeck).
Large real world cases like Toysmart pivot around crucial decision points. You will take on the role of one of the participants in the Toysmart case and problem-solve in teams from one of three decision points. Problem-solving in the real world requires perseverance, moral creativity, moral imagination, and reasonableness; one appropriates these skills through practice in different contexts. Designing and implementing solutions requires identifying conflicting values and interests, balancing them in creative and dynamic solu tions, overcoming technical limits, and responding creatively to real world constraints.
Each decision point requires that you take up the position of a participant in the case and work through decision-making frameworks from his or her perspective. You may be tempted to back out and adopt an evaluative posture from which to judge the participants. Resist this temptation. This module is specifically designed to give you practice in making real world decisions. These skills emerge when you role play from one of the standpoints within the case. You will learn that decision-making requires taking stock of one's situation from within a clearly defined standpoint and then accepting responsibility for what arises from within that standpoint.
Cases such as Toysmart are challenging because of the large amount of information gathering and sorting they require. Moral imagination responds to this challenge by providing different framings that help to filter out irrelevant data and structure what remains. Framing plays a central role in problem specification. For example, Toysmart could be framed as the need to develop more effective software to help negotiate the exchange of information online. In this case, a software programming expert would be brought in to improve P3P programs. Or it could be framed as a legal problem that requires ammending the Bankruptcy Code. What is important at this stage is that you and your group experiment with multiple framings of the case around your decision point. This makes it possible to open up avenues of solution that would not be possible under one framing.
Tackling large cases in small teams also helps develop the communication and collaboration skills that are required for group work. Take time to develop strategies for dividing the work load among your team members. The trick is to distribute equally but, at the same time, to assign tasks according the different abilities of your team members. Some individuals are better at research while others excell in interviewing or writing. Also, make sure to set aside time when you finish for integrating your work with that of your teammates. Start by quickly reviewing the information available on the case. This is called "scoping the case." Then formulate specific questions to focus further research on information relevant to your problem solving efforts. This includes information pertinent to constructing a socio-technical analysis, identifying key "embedded" ethical issues, and uncovering existing best and worst practices.
A case narrative, STS (socio-technical system) description, and two ethical reflections have been published here. This module also links to websites on bankruptcy and privacy law, the Model Business Corporation Act, consumer privacy information, and the TRUSTe website.
- 1099 reads
