


What is Experience
Personal Experience comprises the responses that people
feel, think, express and otherwise endure when they encounter and interact with nature, artifacts and each other.
calm
satisfaction
pleasure
trust
familiarity
clarity


anxiety
frustration
pain
doubt
foreignness
confusion
Personal Experience also comprises the knowledge and associations learned from those encounters and interactions.
Past Experiences condition future Experiences.
People engaged in activities to fulfill needs and goals
delineate a general concept of
Experience
that encompasses context and intention in addition to personal responses



What is Experience Design
Experience Designers conceive and design artifacts, environments and relationships that produce positive personal experiences and outcomes across a range of cultural, business, and everyday contexts-of-use.​



To do that
Experience Designers adopt a Design Thinking methodology in which they use research techniques to empathize with and understand people and businesses in order to conceptualize, define, ideate, prototype and test new ways of accomplishing goals.
​
Experience Designers conduct research to include human capabilities, limitations and characteristics as factors in the design process.
​​
Human Factors include, among others:
-
human performance and reliability
-
attentional demands and workload
-
cognitive bias
-
stress and fatigue
-
motivations and goals
-
accessibility considerations
-
individual differences
-
expertise and skills
Experience Designers study the operational goals of people and businesses and analyze the interactive activities that people and businesses perform to achieve their goals.
They determine the optimal allocation of functional responsibilities between people and technology.
​
They design optimal task sequencing and interaction mechanisms for people to use the technology to perform the activities and accomplish their goals.
​​
The objective is to render a design that:
​
-
Invokes desired personal experiences from users
-
Enables intended performance and outcomes
-
Is well suited across the range of intended contexts-of-use
-
Has utility for all stakeholders
Outcomes refer to the success or failure to perform desired activities and satisfy goals.

Factors such as probability of success and perceived fairness also impact experiences.

Contexts-of-use comprise specific spatial, temporal, environmental and other situational variables within general social, cultural and functional scenarios.



What Comprises an
Experience Design Process

COLLABORATE, EMPATHIZE
and
UNDERSTAND
​
People and Businesses
Collaboration among experience designers, users, managers, customers, marketing, and technology organizations is necessary throughout the design process.
I have worked with these diverse stakeholder groups to incorporate their knowledge and perspectives into designs that meet interdisciplinary goals and constraints. The objective is to understand (not just to identify) needs, intentions, motivations, lifestyles, pain points, brand identities, and corporate cultures.
Collaboration provides insight into holistic needs by considering all experiences, touchpoints, contexts-of-use and dependencies.
Design Thinking, ethnographic research, persona development, user modeling, empathy mapping, activity analysis, contextual inquiry, and knowledge from psychological research are some research methods I use to incorporate a multitude of diverse perspectives into a holistic vision for a product or system design.

INNOVATE
and
CONCEPTUALIZE
​
Possibilities
Conceptual designs focus on possibilities for solutions that break new ground in making things better for people and businesses.
The innovations may be narrow, such as enhancing a specific function of an existing solution, or far-reaching, entirely changing the way particular human or businesses goals are achieved.
Conceptual solutions take into account possible technological capabilities to ensure their feasibility. For, example, a conceptual design may be reliant on Artificial Intelligence to be realized.
Design Thinking, low-fidelity prototyping, journey mapping, activity analysis, and technological knowledge are some methods I use to develop concepts for innovative solutions. Designs are fashioned working in collaboration with users, customers and other stakeholders.
DESIGN, PROTOTYPE
and
ITERATE
Designing is the activity of fashioning artifacts, systems, and environments that are relational, experiential, and useful in serving people's needs.
I have experience working on designs in computing, telecommunications, aerospace and biomedical sectors including designs for intelligent pilot aiding systems, smartphones, enterprise-level business systems, and mobile applications, among others. I have experience designing systems and products that incorporate Artificial Intelligence, Adaptive, and Context-Driven behavioral mechanisms.
Design Thinking, Journey and Empathy mapping, Scenario analysis, User story definition, Participatory design with users, Heuristic evaluation, and walk-through design playbacks are some Human-Centered and Holistic design methods I have used within Agile methodologies and a DesignOps organization.

TEST
and
MEASURE
Designs need to be tested with representative users doing real-world activities with the designs to determine the degree to which the design invokes desired experiences, operational performance goals and outcomes.
Obtaining both objective and subjective data by conducting various applicable testing and measurement methods is performed periodically throughout the design process.
Methods I use include:
Usability testing (moderated and unmoderated)
A/B Testing
Usability metrics collection
Focus Groups
Surveys

AGILE
Software Development is predominantly done within an Agile process comprised of a series of short cycles called Sprints.
In each Sprint, a limited number of functions, that had been previously researched and designed are selected from a backlog of requirements in the form of user stories.
Software releases of developed functions can occur after one or more Sprints are completed and the functions have been tested.
Agile provides several benefits. Requirements can be flexible and easily redefined. Added capabilities are given to the users regularly and quickly, and the process is not overly burdened with documentation