Project Management Midterm Note

Chap 1: An introduction to Project management-2024

Portfolio: Projects, programs, subsidiary portfolios, and operations

managed as a group to achieve strategic objectives.
A portfolio refers to a set of projects, programs, subsidiary portfolios,
and operational activities that are managed collectively to fulfill an
organization’s strategic objectives.
Example: A major technology firm might oversee a portfolio that
encompasses software development initiatives, employee training
programs, and enhancements to internal systems. These various projects
and programs are coordinated to align with the company’s strategic aim
of expanding its global tech services.
Program: Related projects, subsidiary programs, and program activities
that are managed in a coordinated manner to obtain benefits not
available from managing them individually
A program consists of a group of interconnected projects, subsidiary
programs, and associated activities that are managed in a unified way to
achieve benefits that would be unattainable if managed separately.
Example: An urban development program could include multiple
projects, such as constructing schools, hospitals, and transportation
systems. These projects are handled together because they share a
common objective of enhancing the city’s quality of life and
infrastructure.
Project: A temporary endeavor undertaken to create a unique product,
service, or result. Projects can stand alone or be part of a program or
portfolio.
A project is a temporary effort undertaken to produce a unique product,
service, or result. Projects can function independently or be part of a
larger program or portfolio.
Example: A project aimed at constructing a bridge represents a
temporary initiative focused on creating a distinctive structure. The
project concludes upon the bridge's completion. This project may
operate on its own or be integrated into a broader infrastructure
development program.

Projects and Organization structures:

 Functional organization

Functional organization: Many companies are organized as a

hierarchy with functional departments that specialize in a particular type
of work, such as engineering and sales. These departments are often
broken down into smaller units that focus on special areas within the
function. Upper management may divide a project into work tasks and
assign them to the appropriate functional units. The project is then
budgeted and managed through the normal management hierarchy

Advantages and disadvantage of Functional organization

Applications:
Manufacturing Sector: In the manufacturing sector, a functional
organization might have departments such as metal cutting, painting,
testing, and packaging/shipping. Each department would be responsible
for a specific stage in the manufacturing process. This allows for
specialization and efficiency, as each department develops expertise in
its specific area.
Service Sector: Functional organizations are also found in the service
sector. Examples include word processing centers, where departments
may specialize in typing, editing, and proofreading, and diagnostic
laboratories, with departments for sample collection, analysis, and
reporting.

 Projectized Organization
  Features: : A project may be handled through the organization as
described above but with a special appointee to coordinate it. The
project is still funded through the normal channels, and the
functional managers retain responsibility and authority for their
portion of the work. The coordinator meets with the functional
managers and provides direction and impetus for the project and
may report its status to higher management.

Advantages of a Projectized Organization

 Good Project Schedule and Cost Control: The dedicated
resources and focused authority of the project manager promote
better control over project schedules and costs.
 Single Point for Customer Contact: This simplifies
communication and strengthens the relationship between the
customer and the project team.
 Rapid Reaction Time Possible: The dedicated and streamlined
structure allows for quicker responses to changes and challenges.
 Simpler Project Communication: Communication within the
project team is straightforward and efficient.
 Training Ground for General Management: Leading a
projectized organization can be valuable experience for developing
general management skills.
Disadvantages of a Projectized Organization
 Potential for Duplication of Resources: Projectized organizations
may lead to duplication of resources across different projects if
similar expertise is required.
  Difficulty Reintegrating Personnel: When a project ends,
reintegrating personnel back into functional departments can be
challenging.
 Less Focus on Organizational Learning: The strong project
focus may lead to less emphasis on sharing knowledge and lessons
learned across the organization.

Applications:

Large-Scale Infrastructure Projects: Projects like constructing a major

bridge, dam, or highway often necessitate a projectized organization.
These projects involve significant complexity, numerous stakeholders,
specialized expertise across multiple disciplines, and often span several
years. A dedicated project team with centralized authority and clear lines
of responsibility can effectively manage the intricate coordination and
long-term planning required.

Research and Development Initiatives: Developing a new technology,

drug, or scientific breakthrough can be effectively managed as a
projectized organization. These initiatives often demand a high degree of
specialization, experimentation, and collaboration between diverse
research teams. A projectized structure allows for focused effort, rapid
decision-making, and efficient allocation of resources towards achieving
specific research objectives.
New Product Development: Launching a complex new product, such
as a cutting-edge electronic device or a sophisticated software
application, could be structured as a projectized organization. This
structure can facilitate the integration of design, engineering, marketing,
and manufacturing efforts under a unified leadership, ensuring a
coordinated approach to bring the product to market.

Software Development: As software development projects often require

a high degree of flexibility, iterative development, and rapid response to
changing requirements, they may not always be ideally suited for a
purely projectized structure. However, for large-scale, complex software
projects with well-defined scopes and timelines, a projectized
organization can provide the necessary structure and focus to manage the
project effectively.

Event Management: Organizing large-scale events, such as

international conferences, sporting tournaments, or music festivals,
might benefit from a projectized approach. These events require
meticulous planning, coordination of multiple vendors and contractors,
and effective management of logistics, security, and marketing. A
dedicated project team can ensure a smooth and successful event.

Disaster Relief Efforts: Responding to natural disasters or humanitarian

crises often requires a rapid, coordinated, and efficient deployment of
resources. A projectized organization can be quickly assembled to
manage the relief efforts, with a clear chain of command and focused
objectives, such as providing medical aid, shelter, and logistics support.
  Matrix: weak, strong, balanced
Matrix organization: In a matrix organization, a project manager is
responsible for completion of the project and is often assigned a budget.
The project manager essentially contracts with the functional managers
for completion of specific tasks and coordinates project efforts across the
functional units. The functional managers assign work to employees and
coordinate work within their [Link] arrangements are depicted
schematically in Fig. 6
 Composite organization

+ Features: Composite organization: A composite organization

combines elements of both functional and projectized organizational
structures, creating a flexible structure that allows an organization to
adapt to different project requirements. In this hybrid structure,
employees may have both a functional manager and a project manager,
depending on the project's needs and the organization's resources.

+ Application:
Rockwell International's NASA Contracts: The sources describe how
Rockwell International, when awarded contracts for the Apollo and
Saturn launch vehicle programs, established two distinct "programs"
with their own management, manufacturing plants, and specialized staff
(). This approach resembles a composite organization, as it combines
elements of projectized structures (self-sufficient project teams) with
aspects of functional organization within each program.

Business School Structure: A discussion question in the sources asks

the reader to consider how a school of business administration could be
structured to reflect either a functional or product orientation ().
Designing a business school structure necessitates a composite approach.
For example, a school could have functional departments (finance,
marketing, management) while also offering specialized programs
(MBA, executive education). This allows for the benefits of functional
specialization alongside the focused delivery of distinct educational
products.

Curriculum Development Project: Another discussion question

prompts the reader to develop a WBS for a project focused on designing
an MBA curriculum (). This project inherently requires a composite
organization to manage the interplay between the functional expertise of
different faculty members (representing various disciplines) and the
project goals of developing a coherent and integrated curriculum. The
WBS itself could be structured to reflect this composite nature, with
branches for functional areas (finance courses, marketing courses) and
branches for program-level milestones (first-year courses, elective
courses).
Thermal Transfer Plant Case Study: The sources present a case study
of a thermal transfer plant project and encourage readers to work in
groups to plan and control this project (). This collaborative exercise
implies the need for a composite organization to manage the project
effectively. The team would need to draw upon the functional expertise
of engineers, schedulers, contract specialists, and logistics personnel
while working together towards the common project goal of designing,
constructing, and operating the plant.

Combining OBS and WBS: The sources emphasize the importance of

combining the organizational breakdown structure (OBS) and the work
breakdown structure (WBS) to form work packages, which are assigned
to specific organizational units (). This process reflects a composite
approach as it integrates the functional structure (represented by the
OBS) with the project-specific tasks (represented by the WBS). The
work packages, formed at the intersection of these structures, embody
the essence of a composite organization, where functional expertise is
directed towards achieving project objectives.

+ Pros and cons

Flexibility and Adaptability: Composite organizations are highly
flexible and can easily adapt to changing environments, project
requirements, and organizational priorities. This is because they can
leverage the strengths of different structures as needed. For instance, a
company could have a functional structure for its core operations, but
establish project-based teams for specific initiatives.

Efficient Use of Resources: By combining elements of functional

structures, composite organizations can potentially optimize resource
 allocation and avoid duplication of effort. Specialists can be shared
across projects or departments when needed, while maintaining a base
within their functional area.

Improved Communication and Collaboration: Composite organizations

can facilitate better communication and collaboration by creating cross-
functional teams and breaking down traditional silos. This can enhance
knowledge sharing, problem-solving, and innovation.

Specialization and Project Focus: Composite structures allow for both

specialized expertise within functional departments and dedicated focus
on project objectives. This can lead to high-quality work in both routine
operations and specific projects.
Disadvantages of a Composite Organization

Complexity and Ambiguity: Composite organizations can be complex

and difficult to manage, as they involve multiple reporting lines,
overlapping responsibilities, and a potentially intricate web of
relationships.

Potential for Conflict: The combination of different structures can lead

to conflicts between functional managers and project managers,
especially if roles, responsibilities, and lines of authority are not clearly
defined.

Difficulty in Maintaining Balance: Finding the right balance between

different structural elements is crucial for the success of a composite
organization. Too much emphasis on one structure can undermine the
benefits of the others.

Increased Administrative Overhead: Managing a composite

organization often requires more administrative overhead compared to a
simpler structure, due to the need for coordination, communication, and
conflict resolution across different units.
Chương II: Stakeholder
Project Performance Domains
A project performance domain is a group of related activities that are
critical for the effective delivery of project outcomes. These domains are
interactive, interrelated, and interdependent areas of focus that work in
unison to achieve desired project outcomes. In other words, they
represent a system of interactive, interrelated, and interdependent
management capabilities that work together to achieve desired project
outcomes. The sources use the analogy of a system to illustrate this
concept, stating that project performance domains operate as an
integrated system, with each domain being interdependent on the other
domains to enable successful delivery of the project and its intended
outcomes.
There are eight project performance domains:

Stakeholders
Team
Development Approach and Life Cycle
Planning
Project Work
Delivery
Measurement
Uncertainty
Stakeholderd engagment :

Step 1 : Identify
The first step in stakeholder engagement is identifying all potential
stakeholders. This may include individuals or groups that are not
immediately obvious, such as regulatory bodies, community groups, or
competitors. The sources emphasize the importance of identifying
stakeholders early in the project life cycle to ensure their perspectives
are considered from the outset.

Step 2 and 3 : Understanding and Analyze

Analyzing Stakeholders
Once stakeholders have been identified, the project team should analyze
their needs, expectations, interests, and potential impact on the project.
This includes assessing their:
Power: The level of authority or ability to influence project outcomes.
Impact: The extent to which they are affected by project decisions and
activities.
Attitude: Their level of support for the project.
Beliefs: Their underlying assumptions and values related to the project.
Expectations: Their anticipated benefits and outcomes from the project.
Degree of Influence: Their ability to shape project decisions and
outcomes.
Proximity to the Project: Their level of involvement in the project.
Interest in the Project: Their level of concern and attention to project
developments.
The project team should also consider how stakeholders interact with
each other, as they may form alliances that could help or hinder the
project

Step 4: Prioritize
After the analysis, the project team needs to determine which
stakeholders require more attention and resources based on their level of
influence and importance.
Setting priorities helps allocate resources efficiently to optimize
stakeholder management efforts.
It’s important to consider timing and the project phase, as stakeholders
may change in importance throughout the project lifecycle.
Step 5: Engage

Engaging Stakeholders
Effective stakeholder engagement involves working collaboratively with
stakeholders to:
- Introduce the project.
- Elicit their requirements.
- Manage expectations.
- Resolve issues.
- Negotiate priorities.
- Problem-solve.
- Make decisions.
This requires strong interpersonal skills, such as active listening, conflict
management, and leadership.
The sources highlight the importance of tailoring engagement strategies
to the specific needs of each stakeholder or stakeholder group.
Communication Methods
Communication is a key part of stakeholder engagement. It involves:
+ Determining how stakeholders prefer to receive information.
+ Providing timely and relevant information.
+ Establishing feedback loops to ensure understanding.
There are three main communication methods:
Push Communication: Sending information to stakeholders,
such as memos, emails, or reports. This is a one-way form of
communication that should be used deliberately.
Pull Communication: Stakeholders seek out information on
their own, such as by visiting an intranet or conducting internet searches.
This can provide indirect insights into stakeholder concerns.
Interactive Communication: Two-way communication
involving an exchange of information, such as conversations, phone
calls, or meetings. This is the most effective form of communication for
building relationships and fostering collaboration

Step 6: Monitor
Stakeholder engagement is an ongoing process that requires continuous
monitoring and adjustment. The project team should track stakeholder
engagement levels, identify any emerging issues or concerns, and adapt
their engagement strategies as

For Model Example:

Salience Model of Stakeholder Engagement
The Salience Model is a tool used in project management for identifying
and classifying stakeholders based on their prominence or importance
to the project. The model was developed by Ronald K. Mitchell, Bradley
R. Agle, and Donna J. Wood, and it utilizes three key attributes for
assessing stakeholders:
Power: This refers to the stakeholder's ability to influence the project,
its outcomes, or the organization. It can stem from formal authority,
control over resources, expertise, or influence over other stakeholders.
Legitimacy: This pertains to the stakeholder's perceived right to be
involved in the project. It can arise from contractual obligations, legal or
regulatory mandates, moral claims, or societal norms.
Urgency: This relates to the time sensitivity and criticality of the
stakeholder's claims or concerns. It reflects the stakeholder's need for
immediate attention, either due to time constraints or their significant
stake in the project's outcome.
The Salience Model posits that stakeholders who possess one, two, or all
three of these attributes – power, legitimacy, and urgency – are more
salient, meaning they demand more attention and engagement from the
project team.
Visual Representation
The model is often visualized as a Venn diagram with three overlapping
circles representing power, legitimacy, and urgency. The overlapping
sections denote different stakeholder categories:
Latent Stakeholders: Possessing only one of the attributes. For
instance, a stakeholder with power but lacking legitimacy or urgency
might not be actively involved in the project but has the potential to
influence it if their interests are triggered.
Expectant Stakeholders: Possessing two of the three attributes. For
example, a stakeholder with legitimacy and urgency but lacking power
might have valid claims and demand immediate attention but may not
have the means to significantly impact the project.
Definitive Stakeholders: Possessing all three attributes – power,
legitimacy, and urgency. These stakeholders are the most prominent
and require the highest level of engagement from the project team. They
have the ability and the right to influence the project and their concerns
are time-sensitive and critical.
Stakeholders falling within the central overlapping section of the Venn
diagram, where all three attributes intersect, represent those with the
highest salience and require the most focused attention from the project
team.
Applying the Salience Model
The Salience Model helps project teams:
Identify stakeholders: By considering the three attributes, the
model prompts a comprehensive identification of stakeholders, including
those who might be overlooked.
Prioritize stakeholders: It allows ranking stakeholders based on
their salience, enabling the team to allocate resources and effort
effectively.
Develop engagement strategies: By understanding the specific
combination of attributes possessed by each stakeholder group, the team
can tailor their communication and engagement approaches.
Adaptability and Benefits
The Salience Model is a flexible tool that can be adapted to various
project contexts. For instance, some versions substitute 'proximity'
(level of involvement with the project work) for 'legitimacy', making it
particularly suitable for teams.2
The model is valuable for:
Large complex projects: It aids in navigating projects with numerous
and diverse stakeholders.
Projects with intricate stakeholder relationships: It helps understand
the dynamics and interconnections within the stakeholder community.
Example of Salience Model:
XYZ Company – a new electric vehicle manufacturing company in
Vietnam.
Scenario:
XYZ Company is developing a new electric vehicle targeting young
urban customers, with plans to launch within a year. To ensure project
success, the company needs to manage its stakeholders effectively. The
Salience Model will help them prioritize each stakeholder’s importance.
Key Stakeholders
The project’s key stakeholders include:
 Senior management
 Investors
 Production and engineering team
 Potential customers (young urban consumers)
 Government regulators (Ministry of Transport, Ministry of
Industry and Trade)
 Dealers and distributors
 Local community near the production plant
 Marketing and sales staff
Applying the Salience Model
1. Definitive Stakeholders – High Power, Legitimacy, and Urgency
 Senior Management: They hold the power to make final
decisions, have legitimate involvement, and require immediate
updates as this is a strategic project.
Management Strategy: Provide continuous updates, complete
transparency on key milestones, and involve them in major decision-
making processes.
2. Dominant Stakeholders – High Power, Legitimacy, but Low
Urgency
 Investors: They have power through financial backing and
legitimate interest due to their stake in the company, but they don’t
require daily updates unless there are major changes in finances or
timelines.
Management Strategy: Provide regular reports on progress and projected
returns, focusing on financial aspects of the project.
3. Dependent Stakeholders – Low Power, High Legitimacy, and
Urgency
 Potential Customers (young urban consumers): Although they
lack power in the project, they are the end-users of the product and
have a legitimate stake, with urgent needs to be addressed in order
to create a product that meets market demands.
Management Strategy: Gather feedback through surveys, beta testing,
and market research to align the product with customer needs.
4. Dangerous Stakeholders – High Power, Low Legitimacy, but High
Urgency
 Government Regulators: They have the power to enforce
regulations or halt the project if standards are not met, even though
they are not directly involved in production. Regulatory
requirements are urgent and must be met.
Management Strategy: Ensure compliance from the start, maintain
regular contact with regulatory bodies to confirm that the project meets
legal standards.
5. Discretionary Stakeholders – Low Power, High Legitimacy, but
Low Urgency
 Marketing and Sales Staff: They have a legitimate role in
supporting the product’s sales, but they lack influence over
technical development, and their role becomes more important
later in the project.
Management Strategy: Provide periodic updates on product development
and prepare them for the launch phase as the project nears completion.
6. Dormant Stakeholders – High Power, Low Legitimacy, and Low
Urgency
 Dealers and Distributors: They have significant power in product
distribution post-launch, but their active involvement isn’t
necessary now as the project is still in the development phase.
Management Strategy: Keep them informed periodically and prepare a
partnership plan for marketing and distribution once the project is closer
to launch.
7. Non-Stakeholders – Low Power, Legitimacy, and Urgency
 Local Community near the Production Plant: They are not
directly related to the electric vehicle project, although they might
be indirectly impacted by manufacturing activities.
Management Strategy: Maintain good relations with the community and
be responsive to any feedback, especially regarding environmental
impact.
*

Definition and Purpose:

A Stakeholder Register is a project document that meticulously
records information about project stakeholders, including an assessment
and classification of these individuals or groups. This register functions
as a centralized repository of stakeholder-related information, helping
the project manager and team understand and manage stakeholder
expectations and engagement effectively.
Content and Structure
While the sources don't prescribe an exact format, they highlight key
information typically included in a Stakeholder Register:
Identification Information: This section captures basic details about
each stakeholder, ensuring clear identification. It typically includes:
Name: The full name of the individual or group.
Organizational Position: The stakeholder's role within their
organization.
Location: The stakeholder's geographical location, relevant for
communication planning.
Contact Details: How to reach the stakeholder, including email address
and phone number.
Role on the Project: Their specific function or involvement in the
project.
Assessment Information: This section focuses on understanding the
stakeholder's relationship with the project:
Major Requirements: What the stakeholder needs or expects from the
project
Expectations: Their anticipated benefits and outcomes from the project.
Potential for Influencing Project Outcomes: Their capacity to affect
the project's success.
Phase of the Project Life Cycle where the Stakeholder has the most
influence or impact: Identifying when the stakeholder's input or actions
are most critical.
Stakeholder Classification: This section categorizes stakeholders to
understand their position and engagement needs better:
Internal/External: Whether the stakeholder is part of the performing
organization or an outside entity.
Impact/Influence/Power/Interest: Classifying based on their level of
influence, interest in the project, and power to affect it.
Upward/Downward/Outward/Sideward: Categorizing based on their
position in the organizational hierarchy.
The specific classification models used can be chosen by the project
manager, ensuring adaptability to the project's needs.
Uses and Benefits
The Stakeholder Register is a dynamic document, updated as the project
progresses and understanding of stakeholders deepens. Its uses and
benefits extend throughout the project life cycle:
Aids in Identifying Stakeholders: The process of creating the register
encourages a thorough identification of all potential stakeholders.489
Facilitates Stakeholder Analysis: The gathered information enables
analysis of stakeholder needs, expectations, and potential impact,
informing engagement strategies.
Guides Stakeholder Engagement Planning: The register helps develop
tailored engagement plans for different stakeholder groups, ensuring
effective communication and relationship management.
Supports Risk Management: Understanding stakeholder interests and
potential influence helps identify and assess risks related to stakeholder
engagement.
Tracks Stakeholder Engagement: As the project unfolds, the register
helps monitor stakeholder engagement levels and adjust strategies as
needed.
Provides a Centralized Repository: This ensures that all team
members have access to consistent and up-to-date information about
stakeholders.
Connections to Other Processes and Documents
The Stakeholder Register interacts with various other project
management processes and documents, reflecting its integrated role:
●
Project Charter: The initial stakeholder list from the charter often
serves as a starting point for the register.22
●
Business Case: The business case offers insights into stakeholders
affected by the project and their expected benefits.23
●
Requirements Documentation: Requirements analysis can uncover
information about stakeholders and their needs.9
●
Risk Register: Risks related to stakeholder engagement are recorded in
the risk register.24
●
Communication Management Plan: The register informs the
development of communication strategies for different stakeholders.25
●
Stakeholder Engagement Plan: The register provides essential input
for creating this plan, outlining specific engagement strategies.14
Conclusion
The Stakeholder Register emerges as a critical tool for effective
stakeholder engagement, a key aspect of project success. Its structured
yet adaptable format accommodates diverse projects and stakeholder
communities, fostering proactive and informed engagement throughout
the project life cycle.

Perceptual Constraints:
Physical Constraints: The project faces numerous physical constraints
inherent to the site and the construction process. These might include:
Geographical limitations: The bridge must span a specific
waterway with challenging terrain on either side, potentially limiting
design choices and construction methods.
Material availability and accessibility: The required construction
materials may be scarce or located in remote areas, impacting
transportation logistics and costs.
Weather conditions: The local climate, including extreme
temperatures, precipitation, or wind, can significantly impact
construction schedules and safety protocols.
Perceptual Constraints: Alongside these physical constraints, the
project team might encounter perceptual constraints. These are
limitations arising from how individuals perceive and interpret
information, potentially leading to miscommunication,
misunderstandings, and errors in judgment.
Here are some examples of perceptual constraints within the bridge
construction project:
Differing interpretations of design blueprints: Team members
with varying levels of experience and expertise might interpret the
complex engineering drawings differently, leading to inconsistencies in
construction.
Conflicting risk assessments: The team might hold contrasting
views on the likelihood and impact of potential risks, such as the
structural integrity of the bridge under extreme loads. This could lead to
disagreements on safety measures and contingency plans.56
Confirmation bias: Some team members might selectively focus
on information confirming their pre-existing beliefs about the project,
potentially overlooking critical data that contradicts their views. This can
lead to flawed decision-making and project delays.7
Ambiguity in communication: Unclear instructions or
terminology used during construction can result in misinterpretations,
leading to errors in execution and rework.
Impact of Physical Perceptual Constraints: The interplay of
physical and perceptual constraints can significantly impact project
success. For instance:
Delays and cost overruns: Miscommunication or differing
interpretations of design plans can lead to rework, requiring additional
time and resources to rectify errors.
Compromised safety:** Conflicting risk assessments or
overlooking critical safety data due to confirmation bias can result in
accidents and jeopardize worker well-being.
Project failure:** In extreme cases, the inability to effectively
address and overcome these combined constraints can lead to the
project's ultimate failure.1
Mitigating Physical Perceptual Constraints: To mitigate these
challenges, project teams can:
Foster clear communication: Employ standardized terminology
and visual aids, such as 3D models and simulations, to ensure a shared
understanding of design plans and construction procedures.
Encourage diverse perspectives: Actively solicit input from team
members with varying expertise and backgrounds to challenge
assumptions and uncover potential blind spots.4
Implement robust risk management processes: Establish a
systematic approach to risk identification, assessment, and mitigation,
considering a wide range of potential scenarios and perspectives.51013
Cultivate a culture of open communication and feedback:**
Create an environment where team members feel comfortable raising
concerns, sharing observations, and challenging prevailing views.

1. Perceptual Constraints
Perceptual constraints are limitations in human perception that influence
how we interpret the world around us, often limiting our understanding
or actions based on our sensory or cognitive systems. These constraints
shape our behavior by defining what we can or can’t see, hear, or
comprehend in a particular context.
2. Physical Perceptual Constraints
Physical perceptual constraints are limitations caused by the physical
characteristics of our sensory organs and environment.
Example: Imagine a dashboard warning light in a car. If the light is very
small or not bright enough, it may go unnoticed by the driver, especially
in bright daylight conditions. Here, the physical limitation is the eye’s
ability to perceive the light in certain conditions. This constraint limits
the driver’s awareness of a potential issue in the car.
Another Example: The sound frequency range that humans can hear is
between 20 Hz and 20,000 Hz. If a warning alarm in a factory emits a
sound at 25,000 Hz, workers wouldn’t be able to hear it. This physical
constraint limits the effectiveness of the alarm for human workers.
3. Ontological Perceptual Constraints
Ontological perceptual constraints arise from how people mentally
categorize and understand the world around them based on their beliefs,
knowledge, and prior experiences. These constraints are based on
cultural, social, or personal contexts that influence perception.
Example: If a software interface uses icons that are unconventional or
culturally specific, users might misinterpret their meaning. For instance,
a floppy disk icon commonly represents "save" in Western cultures, but
younger users or those from different cultural backgrounds who haven’t
seen floppy disks may not understand the icon’s meaning. This
misunderstanding arises from an ontological constraint, where users lack
the cultural knowledge needed to interpret the icon correctly.
Another Example: In a complex data visualization, if the color red is
used to denote profit and green to denote loss, users accustomed to red
for "loss" and green for "profit" might misinterpret the data. Here, their
understanding is constrained by existing knowledge and associations.