This document discusses using Soft Systems Methodology (SSM) to improve the client discovery process. SSM takes a more holistic approach that accounts for real-world complexities like unpredictable user behavior and multiple stakeholders. It is presented as an alternative to the traditional linear discovery process. SSM involves discovering each client's unique views and context through structured stages. This reveals interacting systems and defines the problems to be solved. Iterating SSM throughout the engagement allows adapting to changing conditions. The outcomes of SSM discovery include client-specific models of the key elements like customers, activities and environmental influences. It also produces purposeful activity models, milestone plans and action items to guide the project. Using SSM is proposed to save time and
10. CLIENT DISCOVERY TODAY
Sales contact
Questionnaire
Client meeting
Email, phone calls, more email, stand up
meetings, more mail, more phone calls,
internal meetings, client meeting (?), more
phone calls, more meetings, meetings about
meetings, email, email, email.
10
15. WHY IS A DISCOVERY
SESSION SO IMPORTANT
Because…
15
16. ENGINEERS THINK THAT …
User behavior is predictable
User behavior is consistent
Process can be automated
Transmission of the output (data) is the end
result
16
17. IN THE REAL WORLD
User behavior is…
Interpretive
Meaning is constructed in relation to unique
situation
User behavior changes due to changing context
Information is processed before and after the
system
17
19. OUTSIDE OF STAR TREK
The real world is…
Chaotic
Subjective
Constructivist active user
Holistic view that encompasses additional elements
for context
Internal cognition
Trans-situationality
19
21. 21
Everyday life develops in all of us trusted
intellectual structures which to us seem
good enough to make sense of our
experiences, and in general we are
reluctant to abandon or modify them
even.
22. SSM PROCESS
Use it to GET information needed for various
system components
IDENTIFY wide and sub systems to be
supported by new/modified system
STRUCTURE an analysis and design
process to facilitate mapping of information to
issues
22
23. STAGE 1: BUILD A CONSENSUS MODEL
Express the current situation and surface
the plurality of project team world views
23
24. STAGE 2: EXPRESS THE ISSUES
Discussion
Consensus
Model (represent)
24
25. STAGE 3: AGREEMENT & ACTION PLANS
Develop agreement and action plans
through process of accommodation
25
27. CATWOE
Customers who benefits from the system transform
Actors who facilitate the transformation
Transformation process where inputs become
outputs
World views that give the transformation meaning
Owner to whom system is answerable to
Environment or constraints on system
27
40. CLIENT –SPECIFIC CATWOE
Who are the customers?
Who does the work?
What are the world views that govern our work?
Who “owns” the project?
What are the environmental influences?
What are the systems and subsystems?
What inputs become transform into what outputs?
40
Unstructured problems are the bane of technology’s existenceSSM moves away from Problem=Absolute solution to Situation that is problematic and evolving – requires thinking that evolvesReal life problems that are rarely staticEnables participants to clarify interests and predicaments
Sometimes you have it…If you are luckyUsually just a kick off meeting disguised as discovery
IR systems have built in functional complexity to accommodate multiple aggregators and actors that are opaque to users (black box)The information system has the role of supplying knowledge and is not always the sole supplier of outputRole of knowledge support of specific actionInformation System/Soft System: information as socially constructedInformation Engineering: information as a concrete phenomenaProblem solving encompasses system, cultural and strategic concernsSSM incorporates system learning and experiential learning and applies to problem-solving
Intersection and Transformation of SSM: Mathiassen, Lars, Neilsen, Asid (2000)Idea is that there would be better systems of IT professionals had better understanding of the scope, nature, impact of the systemUser experience will be better if UX professionals have a better understanding of scope, nature and impact of designs on IT (there are always trade offs)
Soft System Methodology: A Thirty Year Retrospective: Peter Checkland (2000)Engineers struggle with how to incorporate this human element into their system design. Needed a way to deal with this complexity of real situations.Clients struggle with how to attract and retain customersWe struggle with how to understand our client issues, environments, methods and infrastructure.
SSM is about cycles of discussion, learning and debate – unlike IT system thinking that looks for absolute complete solution every timeSSM uses system and psychological foundations to develop models of human behavior – measurement of these models is problematic because not always quantitative
Stage 1: examine the background of the problem to expose issues, problems in structure, develop representation of relevant domains. Used for identification of knowledge gaps, elicit discussion with all of the stakeholder groups
Stage 2: Root definition = relevant systems that will provide insight into the problem. Used to ensure all points of view and intersect consideredSelect issues that warrant a closer look by project teamDevelop alternative viewsExplore creative scenariosDrill down into specific organization processes
Stage 3: Conceptual Model: expressed by verbs, usually focused on 3 sub systems (knowledge, criteria, application. Verbs are the first level of resolution, e.g. monitor and control. Output = human activity system to create evaluation of the real world
Outcome is a rich understanding of parts that results in a richer understanding of the wholeCATWOE can grow, change to scaleAlso BATWOVE where B=Beneficiaries and V = Victims (more complete view, aka SWOT = Strengths Weaknesses Opportunities Threats)
Remember the unstructured problems?Intangibles?They will attempt to derail the best laid plans.
Answered for us and the clientWould this become the first deliverable after signing?Precipitate the client questionnaire?
Selection of purposeful activity systems each based on a declared world view (client and team)
Comparison of the models developed against the real world situations that exist
Comparison outcome are the components of the Milestones and tasks
Action plans are subsets of the main improvement strategy – execution brings about the transformation
Everyone going in the same direction to the same place
So there you have it… 7.5 Ways or 9.5 Ways or 9.5 Ways plus 7.5 sins, so 17 whatever.