The Double Helix methodology arises out of a simple fact: technology and business process are interdependent.

1. Doc
No.
General-07093
M
Human-Centered
Design
Training
Course
Module
4.2:
Double
Helix
Detail
Double Helix Model The Double Helix Model was developed at GD Viz during the
original CPOF project.The Double Helix Model should be
used to facilitate drastic change to both technology and
process when both customer and consultant agree to
actively collaborate toward a shared vision.
Double Helix relies on three fundamental things that are different from other systems engineering processes:
1) A visionary Business Process Team on the customer side must be engaged.
2) The entire group must be willing to let requirements emerge from frequent “crossover events.”
3) Constant collaboration between business process and technology development must occur.
Each crossover event includes:
• Agenda: a plan that sets the stage for the testing scenario and Hot Wash.
• Scenario: a crisis situation scripted out.
• Prototype: a physical embodiment or representation of the design.
• Location: an environment that provides optimal context for the scenario.
• People to test: end-users and leaders.
• Design team: Business Process Team plus Technology Design Team.
The Double Helix Model has two threads,
the Business Process Team and the
Technology Design Team. Each thread has
a visionary with the power to lead real
change.The people on these two teams
together form the Design Team.
Note that this is not a traditional
customer/developer relationship.These
teams work together in a deeply
collaborative manner.
1999 2000 2001 2002 2003 2004
1st Cav
C
2
U
C
a
m
p
P
e
n
d
l
e
t
o
n
C
2
U
F
t
L
e
a
v
e
n
w
o
r
t
h
C
2
U
J
T
C
C
2
U
W
o
r
k
s
h
o
p
B
l
o
c
k
P
a
r
t
y
4
B
l
o
c
k
P
a
r
t
y
5
C
o
l
l
a
b
E
x
1
C
o
l
l
a
b
E
x
2
C
o
l
l
a
b
E
x
3
C
o
l
l
a
b
E
x
4
C
o
l
l
a
b
E
x
6
C
o
m
m
a
n
d
E
x
2
C
o
m
m
a
n
d
E
x
1
DISCOVERY
• Understand the problem
• Disposable prototype
DESIGN
• Iterative development
• Functional prototype
DEPLOY
• Conceptual learning
• Version 1.0 release
Crossover events happen early and often.
They are typically conducted every 6-12
weeks, thereby punctuating a process of
constant prototyping and constant
collaboration. For example, in the course
of the CPOF project 13 crossover events
happened over a 5-year period of time
that is an average of once a quarter.
At crossover events, the divergent goals
of the Business Process Team, the users
and the Technology Team are revealed.
This allows teams to understand and
work toward shared goals; increasing
their core strength in collaboration.
CROSSOVER EVENT
Prototype
Users
Scenario
BUSINESS
PROCESS
Team +
Visionary
TECHNOLOGY
DESIGN
Team +
Visionary
REQUIREMENTS EMERGE!
Double Helix is characterized by crossover events
where the prototype is put to the test in a scenario-
based exercise.The Business Process Team brings the
expertise to the scenario/exercise.The Technology
Team brings the prototype. Users are recruited to
participate.
Together the Design Team and users test a prototype
in the scenario to failure.Then, together they conduct
a review and design exercise called a Hot Wash. From
this activity...
There are three kinds of crossover events:
Crossover events in CPOF development
Double Helix is a form of participatory Human-Centered Design. Participation
occurs when both users and the Design Team are testing prototypes and
iterating on the design solution together. Here are some of the HCD methods
that are used:
Before crossover During crossover
HUMAN-CENTERED DESIGN METHODS:
• Rapid prototyping
• Scenarios
• Engaging participants
• Sketching
• Think Aloud
• Role Playing