Unit I — Foundations of OB / Chapter 01
Nature & Scope of OB
M-IGO-B · 2026 Teaching Edition
Learning outcomes
- Explain nature & scope of ob and distinguish the chapter's central concepts.
- Use Task performance, Organizational citizenship behaviour (OCB), Counterproductive work behaviour (CWB) to frame a workplace diagnosis.
- Interpret the reported indicators while distinguishing observation, inference and missing evidence.
- Compare the case alternatives and justify a decision using theory, trade-offs and an evaluation plan.
Understanding the concept
A fall in output is an outcome, not a diagnosis. Organizational Behaviour begins by asking how a person's work is shaped by colleagues, equipment, rules and expectations. The same worker may perform very differently under a clear, fair system than under a confusing one. Moving between individual, group and organizational levels prevents a manager from treating every operational problem as a motivation problem.
Organizational Behaviour studies how individuals, groups, and organizational structures interact to affect behaviour within firms, at three nested levels of analysis: individual, group, and organization. Managers use this lens to diagnose whether a performance problem originates in a person's ability/motivation, a team's dynamics, or systemic organizational design. Task performance (formal job duties), organizational citizenship behaviour (OCB, discretionary helpful acts), and counterproductive work behaviour (CWB, deliberate harmful acts) together determine organizational effectiveness.
Task performance concerns the responsibilities formally attached to a job. Citizenship behaviour extends beyond those responsibilities, as when an experienced operator helps a newcomer. Counterproductive behaviour undermines people or organizational goals. These categories are useful distinctions, but a single output measure cannot reveal all three. A worker producing many units may also bypass quality checks; a colleague who stops production to report a hazard may protect the organization while appearing less productive in the short term. Effectiveness therefore requires a balanced account of quality, cooperation, safety and sustainability.
- 1Concept: explain the mechanism
- 2Construct: define what matters
- 3Evidence: examine the signals
- 4Decision: weigh and justify
- 5Review: learn from consequences
Core components and theoretical lenses
Use the following distinctions to unpack the chapter's central idea. Each identifies a different aspect of the problem; their relationships matter as much as the labels themselves.
- 01
Individual level: ability, personality, perception, motivation, job attitudes
- 02
Group level: team dynamics, communication, leadership, conflict, norms
- 03
Organization level: structure, culture, HR policies, technology, environment
- 04
Behavioural outcomes: task performance, OCB, CWB, turnover, absenteeism
- 05
Effectiveness criteria: productivity, quality, employee well-being, adaptability
Conceptual constructs
A construct names an idea used to interpret behaviour. It is not directly interchangeable with a survey score or a single incident. In this chapter, the constructs below organize the diagnosis; examine how they could explain the observations before deciding what to change.
- Task performance
- Organizational citizenship behaviour (OCB)
- Counterproductive work behaviour (CWB)
- Organizational effectiveness
- Levels of analysis (micro-meso-macro)
Observable and measurable indicators
Indicators connect an abstract explanation to something that can be observed. Check the operational definition, reporting period and comparison group. A survey average can conceal differences between teams, and an administrative record can reflect willingness to report as well as underlying behaviour.
- Absenteeism rate — unplanned absence days divided by scheduled days, monthly
- Productivity index — units produced per labour hour versus standard, weekly
- OCB frequency — supervisor-rated helping/voice behaviours on a 5-point scale, quarterly
- CWB incidents — recorded disciplinary actions, theft, sabotage reports per quarter
- Employee turnover rate — voluntary exits divided by average headcount, annually
- Grievance count — formal complaints filed per 100 employees, monthly
Storytelling / hypothetical teaching case
A workplace decision
Anand Auto Components, a 450-employee tier-2 manufacturing plant near Pune supplying gaskets to two major OEMs, has seen line productivity fall 14% over two quarters while absenteeism on the night shift has risen from 4% to 11%. The plant HR manager, Radhika Iyer, initially assumed the night-shift supervisor was simply a poor leader, but exit interviews reveal complaints about outdated machines, unclear shift rotation policies, and a new incentive scheme that inadvertently rewards individual output over team quality checks. Some workers privately blame a few colleagues for taking excessive breaks and slowing the line, while others say management never explains scheduling decisions. Radhika must decide whether the root cause lies with individuals, the shift team's dynamics, or the plant's broader systems before recommending a fix to the plant head.
The organization, characters and reported figures are supplied teaching material, not a verified corporate case report.
Reading the case evidence
Separate what the case reports from what you infer. A figure can establish the scale of a problem without establishing its cause. Note what information is absent and how that gap affects your confidence in a recommendation.
| Signal | Reported teaching-case evidence |
|---|---|
| Productivity decline | -14% over two quarters |
| Night-shift absenteeism | 4% -> 11% |
| Machine downtime (night shift) | 18% of shift hours |
| Incentive scheme | Rewards individual units, not team quality |
| Grievances filed (last quarter) | 27, up from 9 |
| Exit interview theme | Unclear rotation and scheduling policy (61% of exits) |
Decision alternatives and trade-offs
Alternatives represent different priorities and assumptions. The advantages and limitations below are the existing module's analytical prompts. Compare them against the same evidence rather than choosing first and finding a theory afterward.
AIndividual-level intervention: performance coaching and discipline
Target specific low-performing workers with coaching, warnings, or reassignment, treating this as an individual motivation/ability problem.
Potential advantages
- Fast, visible action
- Addresses genuine free-riders if they exist
Limitations and risks
- Ignores systemic incentive design flaw
- Risks scapegoating and morale damage if root cause is structural
BGroup-level intervention: team-building and shift norms reset
Run facilitated sessions to rebuild shift-team cohesion, clarify roles, and reset norms around breaks and mutual accountability.
Potential advantages
- Improves communication and trust
- Can surface informal norms undermining quality
Limitations and risks
- Does not fix the incentive scheme driving individualistic behaviour
- Effects may fade without structural follow-through
COrganization-level redesign: fix incentive scheme, machines, and scheduling transparency
Redesign the incentive scheme to reward team quality outcomes, invest in machine maintenance, and publish a transparent rotation policy.
Potential advantages
- Addresses root systemic causes
- Signals fairness, likely to reduce grievances and turnover
Limitations and risks
- Higher cost and longer implementation time
- Requires plant-head and corporate sign-off
DDiagnostic pilot: combine limited coaching with a structural audit before full rollout
Run a 6-week diagnostic on one line combining light-touch individual coaching, a team norms workshop, and data collection on machine/incentive effects before committing to a plant-wide fix.
Potential advantages
- Evidence-based, reduces risk of wrong diagnosis
- Builds buy-in through visible experimentation
Limitations and risks
- Delays relief to a plant already losing productivity
- Requires disciplined measurement capability
Evidence-based discussion
Read the plant's absence, downtime and grievance evidence together. Each supports a different possible explanation, and none alone establishes causation. Compare shifts, examine the timing of policy changes and ask employees how the incentive scheme influences choices. An intervention should address the level where the mechanism operates. Coaching cannot repair a faulty machine; maintenance cannot by itself rebuild a damaged team norm. A defensible recommendation explains both the immediate action and how subsequent evidence will test the diagnosis.
Theory-linked interpretation from the module
OB theory suggests behaviour is jointly determined by person and situation (Lewin's B = f(P, E)); before attributing the productivity fall to individual failings, managers should rule out situational/systemic causes such as flawed incentive design, which is a classic case of rewarding the wrong behaviour. The evidence pattern here (falling productivity, rising absenteeism, an incentive scheme misaligned with quality, and grievances about policy transparency) points toward organizational-level and group-level causes rather than individual deficiency alone, so any credible answer should show a diagnostic sequence rather than jumping to blame.
Your managerial judgement
Which level of analysis (individual, group, or organization) should Radhika prioritize first, and what specific action should she recommend to the plant head?
Write a recommendation that identifies a preferred alternative, uses the reported evidence, acknowledges uncertainty and specifies a review point. Another choice can be defensible when its assumptions and trade-offs are made explicit.
Possible consequences
The module offers the following projections for discussion. They depend on implementation and context; they are not guaranteed effects or verified forecasts.
- Short-term: choosing individual discipline without fixing incentives likely triggers further grievances and possible unionized pushback
- Short-term: a diagnostic pilot delays a company-wide fix but produces defensible data for the plant head
- Long-term: correcting the incentive scheme should realign OCB and reduce CWB such as corner-cutting on quality checks
- Long-term: transparent scheduling policy is likely to reduce absenteeism and turnover over 2-3 quarters
- Reputational: how this is handled affects trust in HR's fairness across the wider plant, not just the night shift
Reflection questions
- How would you distinguish a genuine individual performance problem from a symptom of poor organizational design?
- What data would you want before concluding the incentive scheme, not the workers, is the primary cause?
- How might OCB and CWB be simultaneously present on the same shift, and what does that tell you?
- What risks does Radhika face if she acts only at the individual level to look decisive quickly?
Practice: Know → Analyse → Decide
These are the original module questions. Reading or printing this textbook does not change quiz scores, completion or certificate eligibility.
Know Question 1.1
Organizational Behaviour typically analyses phenomena at which three levels?
- Individual, group, organization
- Strategic, tactical, operational
- Financial, marketing, HR
- Local, national, global
Answer and explanation
A. OB is conventionally studied at the individual, group, and organizational levels of analysis.
Analyse Question 1.2
In the Anand Auto case, which piece of evidence most strongly suggests an organization-level (not purely individual) cause?
- A few workers take excessive breaks
- The incentive scheme rewards individual output over team quality
- The night-shift supervisor is disliked by some workers
- Overall plant headcount is 450
Answer and explanation
B. A misaligned incentive scheme is a structural/systemic design flaw affecting everyone's behaviour, not an individual trait issue.
Decide Question 1.3
Given the mixed evidence of both individual complaints and systemic issues, what is the most defensible first step for Radhika?
- Immediately terminate the lowest performers on the night shift
- Ignore the issue and wait for the next quarter's numbers
- Run a short diagnostic pilot combining coaching, team norms work, and a structural audit before a full rollout
- Announce a plant-wide incentive overhaul the same week without data
Answer and explanation
C. A brief diagnostic pilot balances the need for timely action with the risk of misdiagnosing the true root cause across levels.
Continue with interactive learning
Interactive module: https://migob.lovable.app/learn/1 · Decision Lab: https://migob.lovable.app/decision-lab