UCT Organisational Design and Development Online Course: Exam Notes and Study Guide

This study guide provides structured, high-yield exam notes for the University of Cape Town (UCT) Organisational Design and Development Online Course, with an emphasis on concepts, frameworks, and application in South African organisational settings. It is written to support revision, assignment preparation, and exam performance by combining theory with practical examples, model answers, and analytical tools. The guide also aligns the subject with the broader UCT HRM Online Short Courses cluster while remaining focused on organisational design and development as a distinct field of study.

1. Foundations of Organisational Design and Development

Organisational design and development sits at the intersection of strategy, structure, people, and performance. The core question is not merely how an organisation is arranged on paper, but how effectively its design enables it to deliver value, adapt to change, and coordinate work across functions, levels, and locations. In South African organisations, this topic has particular relevance because firms often operate under conditions of skills scarcity, inequality, regulatory complexity, labour relations pressure, and rapid digital transformation. A well-designed organisation supports execution; a poorly designed organisation creates duplication, delays, confusion, and low accountability.

1.1 What organisational design means

Organisational design refers to the deliberate process of configuring roles, reporting lines, decision rights, workflows, and coordination mechanisms so that strategy can be executed effectively. It answers questions such as:

  • Who does what?
  • Who reports to whom?
  • Where are decisions made?
  • How are tasks coordinated across departments?
  • Which structures best support customer needs and performance goals?

A key exam point is that organisational design is not the same as organisational charts alone. A chart shows formal hierarchy, but design includes the hidden architecture of work: processes, informal networks, information flow, incentives, and governance. In practice, a company may have a neat chart but still suffer from poor design if decision-making is centralised, roles overlap, or functions work in silos.

A useful way to remember the concept is to distinguish between:

  • Structure: the formal arrangement of roles and reporting relationships
  • Processes: how work moves through the organisation
  • People: skills, motivation, and culture
  • Systems: technology, metrics, and rewards
  • Strategy: the competitive direction the organisation is pursuing

A strong design aligns all five. If strategy changes but structure does not, execution suffers. For example, a retail business shifting from store-only operations to omnichannel commerce needs new digital capabilities, integrated logistics, and cross-functional coordination. The old structure may be too slow or fragmented to support the new model.

1.2 What organisational development means

Organisational development (OD) is the planned, systematic effort to improve organisational effectiveness and employee well-being through behavioural science knowledge, interventions, and change management. OD is concerned with how organisations learn, change, and improve over time. If organisational design is the skeleton, OD is the process of keeping the system healthy, adaptable, and responsive.

OD typically focuses on:

  • Change readiness and change management
  • Team development
  • Leadership development
  • Culture transformation
  • Conflict resolution
  • Process improvement
  • Employee engagement
  • Learning and capability building

OD is frequently misunderstood as “soft” or “humanistic” work only. In reality, OD is strategic because it links behaviour to performance outcomes. A poorly managed merger can destroy value through culture clashes, turnover, and uncertainty. A well-managed OD intervention can restore trust, improve collaboration, and accelerate results.

1.3 The relationship between design and development

Although organisational design and organisational development are distinct, they are deeply connected. Design provides the formal architecture; development builds the capacity to make that architecture work. A restructured organisation may have the right chart but still fail if managers do not understand new roles or if employees resist new processes. Similarly, an OD programme may improve teamwork, but if the structure itself is inefficient, the gains may be limited.

A simple exam formulation is:

  • Design decides how work should be arranged
  • Development helps people and systems adapt to make that arrangement effective

This relationship matters in change initiatives. For instance, if a university department wants to improve student service, it may redesign the front-office process, redefine staff responsibilities, and introduce a case management system. That is design. It may then run training, team coaching, and feedback sessions to help staff adopt the new way of working. That is development.

1.4 Key principles of effective organisational design

Several principles are repeatedly tested in exams because they are foundational:

Alignment with strategy

The structure should support the strategy, not contradict it. A differentiated market strategy may require decentralised decision-making and customer-facing autonomy, whereas a cost-leadership strategy may demand standardisation and tighter control.

Clarity of roles

Employees should know what is expected of them, where they add value, and how success is measured. Ambiguous roles create duplication and conflict.

Appropriate span of control

A manager’s span of control is the number of direct reports. Too narrow a span can create bureaucracy and excessive supervision; too wide a span can weaken coaching and oversight.

Balance between differentiation and integration

Organisations divide work into specialised units, but they must also integrate activities to avoid silos. Mechanisms such as cross-functional teams, liaison roles, and shared systems support integration.

Fit with environment

An organisation operating in a stable environment may benefit from routine and predictability, while one in a volatile environment needs flexibility and faster decision-making.

Feasibility and sustainability

A design must be implementable with available skills, technology, and resources. An elegant structure that cannot be staffed or supported is not effective.

1.5 Why this matters in South African organisations

In South Africa, organisational design is influenced by practical realities such as:

  • The need for transformation and inclusion
  • Compliance with labour and employment legislation
  • Pressure to improve service delivery in public institutions
  • Economic volatility and cost constraints
  • The digital shift in banking, retail, education, and government
  • Skills shortages and leadership gaps

For example, a public-sector service centre may face high call volumes, outdated systems, and fragmented responsibilities. If the design is too hierarchical, response times worsen. If OD interventions do not address morale, training, and accountability, the formal redesign may fail. This is why the UCT Organisational Design and Development course is relevant not only to HR practitioners but also to managers, consultants, and change agents.

2. Core Theories, Models, and Analytical Frameworks

Exam questions on organisational design and development often require more than definitions. They ask for comparison, application, and critique. That means you must know the classic models and be able to explain when each is appropriate, where it fails, and how it interacts with real-world conditions. The strongest answers are not descriptive only; they demonstrate judgment.

2.1 The open systems view

An organisation can be understood as an open system that receives inputs from the environment, transforms them through internal processes, and produces outputs such as products, services, and social value. Inputs include labour, capital, information, technology, and materials. Outputs include sales, student success, public services, innovation, and reputation. Feedback from customers, employees, regulators, and communities shapes future action.

The open systems perspective is essential because it shows that organisational performance is not determined only by internal efficiency. External forces matter:

  • Competition
  • Regulation
  • Economic cycles
  • Technology
  • Labour market conditions
  • Political and social expectations

A common exam application is to explain why a structure that worked in one environment may fail in another. A highly centralised organisation may cope well in a stable market but struggle when customers demand speed and personalisation. Open systems thinking helps students avoid overly internal explanations for performance problems.

2.2 The McKinsey 7S Framework

The McKinsey 7S Framework is a popular diagnostic tool for assessing organisational fit. The seven elements are:

  • Strategy
  • Structure
  • Systems
  • Shared values
  • Style
  • Staff
  • Skills

The model is powerful because it reminds analysts that structural change alone is insufficient. If strategy changes but systems, skills, and culture remain old, the organisation will experience misalignment.

How to use 7S in an exam

A strong answer usually follows this pattern:

  1. Identify the strategic goal.
  2. Assess each of the seven elements.
  3. Show where alignment exists and where misalignment occurs.
  4. Recommend interventions.

For example, if a healthcare organisation is modernising patient services, the strategy may emphasise speed and digital access. Yet the existing systems may be manual, staff may lack digital skills, and shared values may still prioritise hierarchy over responsiveness. The 7S framework would reveal that the challenge is not only technical but cultural and behavioural.

2.3 Contingency theory

Contingency theory states that there is no one best way to organise. Instead, the best design depends on situational factors such as strategy, size, technology, environment, and culture. This is one of the most exam-relevant ideas because it rejects simplistic “best practice” thinking.

Key contingencies include:

  • Environmental uncertainty: turbulent environments need flexibility
  • Technology: routine technology may suit formalisation; non-routine work needs discretion
  • Size: larger organisations often require more formal structure
  • Strategy: growth, innovation, and cost control require different designs
  • People and culture: readiness for autonomy or control varies

A useful contrast is between mechanistic and organic organisations:

Feature Mechanistic design Organic design
Decision-making Centralised Decentralised
Rules High formalisation Low formalisation
Communication Vertical Lateral and networked
Suitable for Stable environments Dynamic environments
Strength Efficiency and control Adaptability and innovation

In practice, most organisations need a hybrid. A bank may use mechanistic controls for risk and compliance, but organic structures for digital innovation.

2.4 The socio-technical systems perspective

The socio-technical systems perspective argues that effective organisational design must optimise both the technical system and the social system. The technical side includes workflows, technology, tools, and task design. The social side includes relationships, motivation, roles, and culture.

This matters because technological improvements can fail if human factors are ignored. For example, a new HR information system may appear efficient, but if employees are not trained or fear job loss, adoption will be poor. Likewise, a team may be highly motivated but constrained by obsolete systems and unclear workflows.

A socio-technical approach often encourages:

  • Multi-skilling
  • Team-based work
  • Employee participation
  • Process redesign
  • Simplified communication chains
  • Better fit between technology and job design

2.5 Classical, behavioural, and modern approaches

Organisational design and development also draw from broader management theories.

Classical approach

The classical approach emphasises efficiency, hierarchy, division of labour, and formal rules. It is associated with predictability, standardisation, and control. Its strength is clarity; its weakness is rigidity.

Behavioural approach

The behavioural approach highlights motivation, leadership, groups, and human needs. It recognises that people are not mechanical resources and that performance depends on commitment, satisfaction, and social dynamics.

Modern approach

Modern approaches integrate systems thinking, contingency theory, and complexity. They accept that organisations are adaptive, interconnected, and shaped by uncertainty. Modern design is less about perfect control and more about responsiveness.

2.6 A practical comparison of models

Framework Main question Best use Limitation
Open systems How does the organisation interact with its environment? Environmental analysis Can be broad and abstract
7S Is the organisation internally aligned? Diagnosis and alignment checks Does not prescribe one structure
Contingency theory What design fits this situation? Structural decisions Can feel non-specific
Socio-technical systems How do technology and people fit together? Process redesign and innovation Requires cross-functional effort

A high-scoring exam answer usually combines frameworks rather than using one in isolation. For example, you might use open systems to assess the external environment, contingency theory to choose a design, and 7S to check internal alignment.

3. Organisational Structures, Roles, and Design Choices

This section is central because many exam questions ask students to compare structures, explain reporting lines, or recommend a design for a specific organisation. Good answers demonstrate that structure is a strategic choice, not a neutral administrative detail.

3.1 Common organisational structures

Functional structure

A functional structure groups people by specialisation, such as finance, HR, marketing, operations, and IT. It is efficient because expertise is concentrated and duplication is reduced. It works well for organisations with stable products and clear technical specialisation.

Advantages

  • Clear accountability
  • Economies of scale
  • Specialist development
  • Simple reporting lines

Disadvantages

  • Silos
  • Slow coordination across functions
  • Weak customer orientation
  • Overloaded top management

Divisional structure

A divisional structure groups activities by product, geography, customer, or service line. Each division has greater autonomy and can respond quickly to its market.

Advantages

  • Better market focus
  • Faster decisions
  • Greater accountability for results
  • Suitable for growth and diversification

Disadvantages

  • Duplication of resources
  • Potential competition between divisions
  • Higher cost
  • Inconsistent standards

Matrix structure

A matrix structure combines two dimensions, often function and project or product. Employees may report to both a functional manager and a project manager.

Advantages

  • Encourages collaboration
  • Useful for complex, cross-functional work
  • Improves resource sharing
  • Supports innovation

Disadvantages

  • Dual reporting confusion
  • Conflict over authority
  • Slow decision-making if not managed well
  • Requires mature culture and clear governance

Network structure

A network structure relies on relationships with partners, suppliers, contractors, and external experts. It is flexible and can scale quickly without building everything internally.

Advantages

  • Agility
  • Access to specialist capability
  • Lower fixed costs
  • Adaptability

Disadvantages

  • Dependence on partners
  • Control challenges
  • Coordination complexity
  • Risk of inconsistent quality

3.2 Choosing the right structure

A common exam mistake is to describe structures without justifying fit. The correct approach is to link structure to context. Consider these examples:

  • A small professional firm may use a functional structure because expertise and direct oversight matter.
  • A diversified consumer company may use divisional units because different product lines need independent focus.
  • A research-intensive engineering organisation may use a matrix structure because projects require both technical depth and cross-disciplinary coordination.
  • A fast-growing digital startup may use a networked structure or a light hierarchy to remain agile.

The decision depends on:

  1. Strategy
  2. Size
  3. Geographic spread
  4. Complexity of products or services
  5. Skill requirements
  6. Need for innovation
  7. Need for compliance and control

3.3 Span of control and hierarchy

Span of control is a recurring design concept. It refers to the number of subordinates a manager supervises directly. The ideal span depends on the nature of the work. Routine, standardised work may allow a wider span. Complex, uncertain, or high-support work may require a narrower span.

A flatter structure with wider spans can reduce bureaucracy and speed communication, but it can also weaken support if managers are overloaded. A taller structure with narrower spans can improve oversight, but it often increases costs and slows decisions.

Exam answers should show that span of control is not a fixed number. It is shaped by:

  • Task complexity
  • Employee competence
  • Geographic dispersion
  • Managerial capability
  • Use of technology
  • Need for coaching or supervision

3.4 Centralisation, decentralisation, and decision rights

Centralisation means decision-making authority is concentrated at higher levels. Decentralisation means authority is distributed to lower levels or units closer to the work.

Centralisation can be useful for:

  • Standardisation
  • Risk control
  • Regulatory compliance
  • Strategic coherence

Decentralisation can be useful for:

  • Speed
  • Customer responsiveness
  • Local adaptation
  • Employee empowerment

In many organisations, the best design is selective decentralisation. Core policies may remain centralised while operational decisions are delegated. For example, a university may centralise academic standards but decentralise some student support decisions to faculties or departments.

3.5 Formalisation and standardisation

Formalisation is the extent to which rules, procedures, and documentation govern behaviour. Standardisation ensures work is done consistently across units. These are useful for quality control and compliance, but excessive formalisation may reduce initiative and responsiveness.

A strong analysis will identify when formalisation helps and when it harms. In a hospital, formal protocols are essential for patient safety. In a creative agency, too much formalisation may suppress innovation. The challenge is to formalise what must be stable while leaving room for discretion where judgment adds value.

3.6 Organisational roles and job design

Structure becomes real through jobs and roles. A role defines expected behaviour and responsibilities. Poorly designed roles cause overload, overlap, and confusion. Good job design should consider:

  • Task variety
  • Task identity
  • Task significance
  • Autonomy
  • Feedback
  • Skill use

These dimensions are important because they influence motivation and performance. A role that is repetitive and tightly controlled may generate compliance but not engagement. A role with meaningful autonomy and visible impact is more likely to encourage ownership.

3.7 Example: redesigning a university support unit

Imagine a university support unit responsible for admissions, records, and student queries. It initially operates in separate silos: admissions handles applications, records manages registration, and student services answers complaints. Students are transferred repeatedly and staff duplicate data entry.

A better design may include:

  • A single service centre for front-line queries
  • Specialist back-office teams for complex cases
  • Clear escalation paths
  • Shared digital case management
  • Cross-training for front-line staff
  • Service-level targets

This redesign reduces fragmentation while preserving specialist expertise. The OD component would include training, change communication, and staff involvement to manage resistance.

4. Change, Intervention, and Organisational Development Practice

Organisational development is not just analysis; it is intervention. Once a gap between current and desired performance is identified, OD professionals plan and implement change. This section is highly examinable because it links theory to practice and requires students to show sequence, logic, and sensitivity to human behaviour.

4.1 The change process

A classic way to understand change is through three broad stages:

  1. Unfreezing: creating awareness that change is necessary
  2. Changing: introducing new behaviours, systems, or structures
  3. Refreezing: stabilising the new way of working

While this model is simple, it is still useful for exam purposes because it shows that change is not only technical. People must let go of old habits, learn new ones, and experience reinforcement before new practices become normal.

A more contemporary view treats change as continuous rather than linear. In modern organisations, change may be ongoing due to digital transformation, market disruption, or regulatory shifts. Even so, the basic logic of preparation, implementation, and reinforcement remains useful.

4.2 Types of change

OD interventions may involve different kinds of change:

  • Structural change: altering reporting lines, departments, or levels
  • Process change: redesigning workflows, systems, or service delivery
  • Cultural change: shifting norms, assumptions, and values
  • Technological change: introducing new tools and platforms
  • People change: building skills, leadership, or team capability

These often occur together. For instance, implementing a new customer relationship platform may require process redesign, role changes, training, and culture change. Treating it as a purely technical project is a common mistake.

4.3 Common OD interventions

Team building

Team building improves trust, communication, conflict handling, and shared goals. It is useful where interdependence is high and performance depends on collaboration.

Survey feedback

This intervention uses employee surveys to identify organisational issues and then shares results with teams so they can plan action. It is useful for diagnosing morale, engagement, and communication problems.

Process consultation

A consultant helps a group diagnose its own process problems, such as poor meetings, unclear decision-making, or conflict. The goal is not to impose solutions but to improve the group’s ability to solve problems itself.

Structural intervention

Structural interventions modify formal arrangements, such as departmental reorganisation, decentralisation, or workflow redesign.

Training and learning

Training builds knowledge and skills required for new roles or systems. It is especially important when redesign changes expectations.

Leadership development

Leaders often determine whether change succeeds because they translate strategy into behaviour, model values, and manage resistance.

4.4 Managing resistance to change

Resistance is not always irrational. It may signal fear, loss, uncertainty, or practical concerns. People may resist because they think the change is poorly designed, because they do not trust leadership, or because they lack the skills needed for the new environment.

Typical sources of resistance include:

  • Fear of job loss
  • Loss of status or power
  • Unclear communication
  • Past change failures
  • Workload pressure
  • Inadequate participation

Effective change leaders do not ignore resistance. They diagnose it and respond appropriately through communication, involvement, negotiation, support, and visible leadership commitment.

4.5 Lewin, Kotter, and other change frameworks

Lewin’s model

Lewin’s model is compact and useful for foundational understanding. It stresses that change requires destabilising the old pattern before the new one can take hold.

Kotter’s eight-step model

Kotter emphasises urgency, coalition-building, vision, communication, empowerment, short-term wins, consolidation, and anchoring change in culture. This model is especially useful when a large-scale transformation needs sustained momentum.

Action research model

This approach integrates diagnosis, action, and evaluation. It is valuable in OD because it treats change as participatory and evidence-based.

A strong answer may compare these models as follows:

  • Lewin: simple, stage-based, foundational
  • Kotter: detailed, leadership-focused, useful for large transformations
  • Action research: cyclical, participatory, diagnostic

4.6 Measuring OD success

OD cannot be judged only by whether a new policy exists. It must be evaluated through outcomes such as:

  • Employee engagement
  • Turnover
  • Absenteeism
  • Service quality
  • Cycle time
  • Customer satisfaction
  • Error rates
  • Financial performance
  • Team effectiveness
  • Leadership behaviour

Importantly, measurement should include both hard metrics and soft indicators. A restructuring may reduce costs but damage trust if managed badly. A good OD evaluation asks whether the change is sustainable, not only whether it is implemented.

4.7 Example: restructuring a service organisation

Suppose a provincial service agency faces long queues, inconsistent response times, and low staff morale. Management decides to redesign the front-line structure. The intervention may include:

  1. Mapping the current process
  2. Identifying bottlenecks
  3. Redefining roles at the service desk
  4. Introducing a digital queue and case system
  5. Training staff in customer service
  6. Setting service targets
  7. Running feedback sessions after implementation

This case shows the need for both design and development. A new structure alone would fail if staff remain uncertain or unsupported. The OD intervention helps the redesign become a working system.

5. Exam Frameworks, Application Strategies, and High-Scoring Answers

This final section converts knowledge into performance. In an exam, students are rarely rewarded for memorised definitions alone. They are rewarded for clarity, structure, depth, and the ability to apply theory to realistic organisational scenarios. The following frameworks are designed to help construct strong answers under time pressure.

5.1 How to structure an exam answer

A strong organisational design and development answer usually follows this pattern:

  1. Define the key concept
  2. Explain the relevant theory or model
  3. Apply the theory to the case or scenario
  4. Analyse advantages, limitations, and trade-offs
  5. Conclude with a justified recommendation

This approach prevents answers from becoming either too theoretical or too anecdotal. It also demonstrates balance, which is essential in higher-level university writing.

5.2 A practical diagnosis framework

When given a case study, use the following diagnostic sequence:

Step 1: Strategic context

  • What is the organisation trying to achieve?
  • Is the strategy about growth, cost efficiency, innovation, quality, or transformation?

Step 2: Environmental pressures

  • What external factors are shaping the problem?
  • Are there regulatory, competitive, technological, or labour-related pressures?

Step 3: Structural fit

  • Is the current structure functional, divisional, matrix, or networked?
  • Does the structure match the strategy?

Step 4: Process and systems fit

  • Are workflows clear?
  • Are systems integrated?
  • Is information flowing effectively?

Step 5: People and culture

  • Are skills adequate?
  • Is leadership aligned?
  • Is the culture supportive of change?

Step 6: Intervention choice

  • What must be redesigned?
  • What must be developed?
  • Which OD tools are most appropriate?

5.3 Common exam themes and how to answer them

Theme 1: “Explain the difference between organisational design and organisational development”

A top answer should distinguish formal structure from planned change and improvement. It should then explain how they interact in practice.

Theme 2: “Recommend a suitable structure”

Do not merely name a structure. Justify it using strategy, environment, size, and coordination needs.

Theme 3: “Analyse resistance to change”

Treat resistance as information, not just obstruction. Explain causes, impacts, and management methods.

Theme 4: “Assess the effectiveness of an OD intervention”

Discuss objectives, process, stakeholder involvement, implementation quality, and measurable outcomes.

Theme 5: “Compare theoretical models”

Identify similarities and differences, then explain which model best fits a given scenario.

5.4 High-value keywords and phrases for exam writing

Using precise language improves the quality of the answer. Useful phrases include:

  • Strategic alignment
  • Structural fit
  • Decision rights
  • Differentiation and integration
  • Environmental uncertainty
  • Cross-functional coordination
  • Change readiness
  • Organisational effectiveness
  • Employee engagement
  • Sustainable transformation
  • Socio-technical fit
  • Behavioural adoption
  • Governance and accountability

These terms should be used accurately, not mechanically. An examiner can usually tell when a candidate understands the concept versus when they are simply inserting buzzwords.

5.5 Mini-case application framework

Consider a South African financial services organisation introducing hybrid work and digital service channels. A high-scoring answer could say:

  • The strategy is to improve customer convenience and reduce turnaround time.
  • The old functional structure may slow coordination across digital, operations, and customer service teams.
  • A more integrated design, perhaps with cross-functional squads, would improve speed and customer focus.
  • However, decentralisation must be balanced with risk controls and compliance requirements.
  • OD interventions should include leadership alignment, digital training, new performance metrics, and team-based coordination routines.
  • Success should be measured through response times, customer satisfaction, employee engagement, and error rates.

This kind of answer demonstrates both theory and context-sensitive judgement.

5.6 Revision table: key concepts at a glance

Concept Core meaning Why it matters Common exam pitfall
Organisational design Structuring roles, processes, and decision rights Enables strategy execution Treating it as just an org chart
Organisational development Planned improvement and change Builds adaptability and effectiveness Describing it as training only
Contingency theory Best design depends on context Avoids one-size-fits-all answers Giving universal recommendations
7S Framework Alignment among seven organisational elements Diagnoses misfit Listing elements without analysis
Socio-technical systems Joint optimisation of people and technology Improves implementation success Focusing only on systems or only on people
Centralisation Authority concentrated at top Improves control Ignoring speed and empowerment costs
Decentralisation Authority delegated downward Improves responsiveness Ignoring governance and consistency issues
Resistance to change Pushback due to fear, loss, or uncertainty Helps plan change management Treating resistance as irrational behaviour

5.7 Common mistakes to avoid

  • Defining concepts too narrowly
  • Using only one theory for a complex case
  • Ignoring the environment
  • Recommending structure without explaining why it fits
  • Forgetting the people side of change
  • Overlooking measurement and evaluation
  • Writing descriptive answers without analysis
  • Confusing formal structure with actual work practices

5.8 Final integrated revision framework

A strong revision strategy is to remember that organisational design and development always revolve around four linked questions:

  1. What is the organisation trying to achieve?
  2. How should work be arranged to achieve it?
  3. How will people adapt to the new arrangement?
  4. How will success be measured and sustained?

If those four questions are answered clearly in an exam, the response will usually be well structured and persuasive. In the context of the UCT Organisational Design and Development Online Course, this integrated view is especially important because the course is not just about theory recall; it is about applied organisational thinking in real organisational settings, including South African workplaces where change is often constrained by scarce resources, legacy systems, and complex human dynamics.

Quick Revision Summary

  • Organisational design is about arranging work, roles, and decision-making for strategic fit.
  • Organisational development is about planned change and improvement in behaviour, culture, and capability.
  • Structure, systems, strategy, staff, skills, style, and shared values must align.
  • No single best structure exists; the right design depends on context.
  • Resistance to change is normal and should be managed through communication, involvement, and support.
  • OD success must be measured through both performance and people outcomes.
  • Exam answers should combine definition, theory, application, evaluation, and recommendation.

This guide is designed to support confident, analytical revision for the UCT Organisational Design and Development Online Course and related UCT HRM Online Short Courses.

Select the fields to be shown. Others will be hidden. Drag and drop to rearrange the order.
  • Image
  • SKU
  • Rating
  • Price
  • Stock
  • Availability
  • Add to cart
  • Description
  • Content
  • Weight
  • Dimensions
  • Additional information
Click outside to hide the comparison bar
Compare