Understanding Individual Behavior at Work: The Person, the Situation, and the Psychological Contract

Organizational behavior, in Stephen Robbins and Timothy Judge's widely used definition, is "a field of study that investigates the impact that individuals, groups, and structure have on behavior within organizations, for the purpose of applying such knowledge toward improving an organization's effectiveness" (Robbins & Judge, 2023). That definition names three levels of analysis: the individual, the group or team, and the structure or system the organization builds around both. Most management attention gravitates to the third level, strategy and structure, because it is where budgets and reorganizations live. But an organization produces results only through the specific choices of specific people: whether an employee discloses a quality problem before it reaches a customer, whether a supervisor enforces a safety rule consistently or lets it slide under deadline pressure, whether someone stays an extra hour to fix something that is not, strictly, their job.

Daniel Katz and Robert Kahn (1966) drew a distinction that is easy to lose sight of once structure and process dominate the conversation: the behavior an organization formally requires of a role is not the same as the behavior that actually makes the role work. People can do exactly what a job description says and still produce a department that functions badly, and they can exceed what the job description says in ways that keep a department running through a bad week. Individual behavior is not a soft add-on to organizational performance; it is the mechanism through which structure and strategy become results at all.

This lesson introduces three tools for understanding that mechanism: the interaction between a person and the situation they are in, the basics of how people attribute causes to behavior, and the psychological contract that governs what an employee believes they owe an organization and what they believe is owed back. A fourth section argues that individual differences are best treated as something a manager designs around, not only something a recruiter screens for. None of the four tools catalogs personality traits, perceptual biases in general, motivation theory, or how groups and power operate; Lessons 22 through 25 take up each of those in turn. What this lesson supplies is the groundwork those lessons will use.

In 1951, the social psychologist Kurt Lewin proposed a formula that remains one of the most quoted (and most frequently misquoted) ideas in the behavioral sciences: B = f(P, E). Behavior is a function of the person and the environment, taken together, not of either one alone. Lewin called the combination of a person's state and their psychological environment the "life space," and his point was that the two cannot be analyzed apart from each other without losing exactly what explains the behavior (Lewin, 1951). A conscientious, careful employee placed in a role with no authority to fix a broken process can look passive or indifferent. The same person, given the authority, may look like a different employee entirely. The trait did not change. The situation did.

Walter Mischel tested this idea against decades of personality research in his 1968 book Personality and Assessment, and the result reshaped the field. Reviewing studies that tracked the same people across different situations, Mischel found that behavioral consistency for most personality traits, aside from measures of cognitive ability, was far lower than trait theory assumed: people who acted conscientiously in one setting often did not act conscientiously in another (Mischel, 1968). The finding set off what became known as the person-situation debate, with one side arguing that broad, stable traits predict little on their own and that situational forces do most of the explanatory work.

The debate did not end with the situation winning outright. Mischel and his later collaborator Yuichi Shoda proposed that traits do predict behavior, but in situation-specific patterns rather than uniformly: a person might be reliably assertive with subordinates and reliably quiet with senior management, a stable "if-then" signature rather than an across-the-board trait score. The resolution kept both halves of Lewin's formula in play. Neither the person alone nor the situation alone does the explanatory work; the interaction does.

For a manager, the practical consequence is a discipline, not a conclusion. Before treating a performance problem as evidence about someone's character, it is worth asking what, in the situation itself, resources, authority, incentives, information, workload, would produce the same behavior regardless of who occupied the role. This does not mean the dispositional explanation is always wrong. It means the situational explanation has to be checked first, because it is usually the one a manager can act on without trying to replace the person.

If behavior depends on the person and the situation together, the next question is how observers, including managers judging their own staff, decide which one was responsible for a given instance of behavior. Fritz Heider's early work described people as acting like "naive scientists," inferring the causes of behavior from the evidence available to them. Harold Kelley (1967) turned that idea into a testable model, the covariation model, built on three kinds of information: consistency (does this person behave this way in this situation every time), distinctiveness (does this person behave differently in other, similar situations), and consensus (do other people in the same situation behave the same way). High consistency, low distinctiveness and low consensus point an observer toward a dispositional cause, something about the person. High consistency with high distinctiveness and high consensus point toward a situational cause, something about the circumstance that would produce the same behavior in most people placed in it.

In principle, that is a reasonably careful procedure. In practice, people do not usually collect all three kinds of information before forming a judgment, and the errors that result are not random. Lee Ross (1977) named the most consistent of them the fundamental attribution error: the tendency to overweight dispositional causes and underweight situational causes when explaining someone else's behavior. A colleague who snaps at a client is "difficult"; a manager who misses a commitment is "unreliable." The situational information that might explain either, an unreasonable deadline, a system outage nobody disclosed, is often invisible to the person doing the judging, while the person themselves is immediately visible. Character fills the gap left by information the observer does not have.

Two further asymmetries compound the error inside organizations. People tend to explain their own behavior situationally while explaining others' behavior dispositionally, the actor-observer asymmetry; and people tend to credit themselves for successes while blaming circumstances for failures, the self-serving bias. The combination means that a manager and an employee can look at the identical missed deadline and arrive at opposite, equally sincere explanations, each person using the situational account for themselves and the dispositional account for the other.

This matters because performance appraisal, disciplinary decisions and promotion judgments are attribution exercises whether a manager recognizes them as such or not. A manager who diagnoses repeated lateness as an attitude problem without checking a disrupted commute, overlapping shift handovers or an unannounced change to dependent-care arrangements is not applying a neutral assessment; they are applying the fundamental attribution error to a specific person's record, with consequences that follow them into a file. None of this means situational explanations are automatically correct, or that attribution theory is a way of excusing genuine underperformance. It is a discipline against reaching the dispositional conclusion first because it is the easiest one to reach, not because the evidence actually supports it. The wider study of how perception forms in the first place, including stereotyping, selective attention and the halo effect, belongs to Lesson 22; what matters here is only the mechanism that turns an ambiguous instance of behavior into a confident, often wrong, explanation.

Employment relationships run on two documents at once. One is the written contract, covering pay, hours and formal terms. The other is unwritten, and it is often the one that determines whether an employee works with discretionary effort or strictly to the letter of the job description. Chris Argyris used the term "psychological work contract" in passing in 1960, and Harry Levinson and his colleagues at the Menninger Foundation gave the idea a fuller, psychoanalytic treatment in 1962, describing a set of reciprocal expectations, some of them barely conscious, that employees carried about their work. The idea that reshaped how the field uses the concept came later, from Denise Rousseau (1989), who relocated the contract from the relationship itself into the individual mind: a psychological contract is one person's belief in a reciprocal obligation between themselves and the organization, formed from promises the person perceives, whether or not the organization intended to make them and whether or not the organization holds the same belief about what it owes.

That last clause is the one that creates most of the difficulty in practice. Because the contract is a perception, not a shared document, two people occupying what looks like the same employment relationship can carry two different contracts, and an organization can breach an obligation it never knew it had made. Rousseau (1990) distinguished two broad types. A transactional contract is narrow and short-term: pay for hours, a closely specified exchange with little expectation that the relationship will extend beyond its stated terms. A relational contract is broader and open-ended: loyalty, development and a degree of job security in exchange for discretionary effort and identification with the organization, with far less of the exchange ever written down. Which type forms depends partly on how the relationship is introduced, a fixed-term contract framed in strictly transactional language will tend to produce a transactional contract, while recruitment rhetoric about "joining the family" invites a relational one, and partly on what the organization signals afterward, through job security during downturns, how promotions are actually decided, and whether informal promises made by a line manager turn out to be honored.

Sandra Robinson and Denise Rousseau (1994) tested how common it is for employees to perceive that an organization has failed to meet an obligation they believed it had taken on. Surveying new hires over their first two years, they found that a majority reported at least one such failure, concluding that psychological contract breach is "not the exception but the norm" in employment relationships. It is worth separating two things their work distinguishes: breach is the cognitive judgment that an obligation was not met; violation is the emotional reaction, often felt as betrayal, that can follow from a breach once the employee interprets it as a sign of bad faith rather than an unavoidable circumstance. The same missed promotion can register as a disappointing but understandable breach, or as a violation that permanently changes how much effort the employee is willing to extend, depending on how it is explained and whether the employee believes the organization could have done otherwise.

Why does a single unmet promise change the whole relationship rather than staying a single, isolated disappointment? Because a relational contract is relational precisely in the sense that each side's obligations are read as evidence about the other's good faith going forward, not as a list of separate, unconnected items. A felt breach does not just subtract one promise from the ledger; it revises the employee's estimate of how much the rest of the ledger can be trusted, which is why withdrawal after a breach, reduced discretionary effort, lower trust, earlier exit, tends to extend well beyond the specific item that was not delivered.

The following example is constructed for this lesson and does not describe a real company. Consider a mid-sized ready-made garment exporter that recruits floor supervisors with a verbal assurance, never put in writing, of a permanent position and a realistic path to assistant manager within two years. Operational pressure then leads the firm to extend several supervisors' probation repeatedly, each time for a specific, defensible reason: a slow order quarter, a factory audit, a reorganization. No single extension looks unreasonable. From the firm's side, nothing has been promised in writing, so nothing has technically been broken. From the supervisors' side, a relational promise has been deferred four times running, and the pattern itself, not any one extension, becomes the evidence that the firm's word cannot be relied on. What follows is predictable once the mechanism is understood: supervisors begin treating the role as transactional regardless of how it was sold to them, informal comparison among supervisors spreads the perception faster than management can respond to it, and the firm loses exactly the discretionary effort, covering a line when a machine breaks, flagging a quality issue before a shipment, that it was counting on when it used relational language to recruit.

If behavior is genuinely a function of the person and the situation together, individual differences among employees, in ability, prior experience, personal circumstances and the values they bring to a role, matter to a manager in two distinct ways, not one. The familiar way is as a selection criterion: screening for the differences that predict good performance in a given role before anyone is hired. The less obvious way, and the one this section argues deserves more attention than it usually gets, is as a design variable: shaping the situation so that the range of people already on a team produces consistent, good behavior rather than unpredictable variance driven by how well each person happens to fit a one-size policy.

The mechanism is the same interaction Section 2 described, applied forward rather than backward. An identical policy, a fixed start time, a single appraisal format, a uniform set of performance targets, can be a reasonable fit for one employee's circumstances and preferences and a poor fit for another's, producing different behavior from the same rule rather than a reliable, uniform response. This is one reason policies and practices documented as effective in one organization sometimes underperform when copied into another without adjustment, a point Lessons 18 and 19 in this series examined in the specific context of high-performance work systems and HR architecture; the individual-differences version of the same problem is that a workforce is rarely uniform enough for a single design choice to land the same way twice.

Two opposite errors are worth naming so neither becomes the default. Treating a workforce as if it will respond uniformly to any policy ignores real variation in ability, constraint and circumstance, the situation-only error. Treating every variation in behavior as evidence of a stable personal trait, convenient and lower that trait before deciding, ignores Section 2's lesson that the situation is doing real work too, the person-only error. The skill a manager needs is not a rule that resolves this in advance; it is the habit of asking, in each specific case, which lever, the person or the situation, is actually movable, and at what cost, before choosing which one to pull.

The three tools in this lesson point in the same direction without collapsing into one argument. Before attributing a behavior to someone's character, Lewin's formula says to check what the situation itself would produce in almost anyone placed in it. Before trusting the first explanation that comes to mind, Kelley's and Ross's work says to notice whether the explanation is being judged as an outside observer or as the person involved, and to look for consistency, distinctiveness and consensus rather than settling for the dispositional account by default. Before assuming an employee reads the employment relationship the way the organization intends it, Rousseau's work says to ask what promises, explicit or merely implied, the employee believes they were given, because the belief, not the intention, is what drives their behavior next.

None of these three tools fully diagnoses an individual behavior problem by itself, and none replaces the deeper study of personality, motivation, group dynamics and power that Lessons 22 through 25 take up next. What they give a manager, taken together, is resistance to the cheapest available explanation for someone else's behavior, which is almost always some version of "that is just how they are." That resistance has a real cost: diagnosing a situation properly takes longer than pronouncing a verdict on it, and most organizations reward decisiveness more visibly than they reward the slower work of checking an explanation before acting on it. That tension, between the discipline this lesson describes and the pressure every manager is actually under to decide quickly, does not resolve here. It returns, in different forms, through the rest of this module.

Identify one specific, non-trivial instance of workplace behavior that you observed directly, or that is documented in a published case, news report or company disclosure you can cite (do not invent one). Examples include a disciplinary decision, a resignation, a sustained drop or rise in someone's performance, or a conflict between a manager and a direct report.

Write a report of 1,500 to 2,000 words that:

1. describes the behavior and its context factually, distinguishing what you directly observed or what a cited source reported from any inference you are adding;
2. applies Lewin's person-situation framework explicitly: identify at least two specific features of the situation (resources, authority, incentives, information, workload, or similar) that could plausibly explain the behavior independent of the person's disposition;
3. applies Kelley's covariation model to your own evidence: what do you know, or what could you find out, about consistency, distinctiveness and consensus for this case, and what does that evidence suggest about a dispositional versus situational cause;
4. identifies whether a fundamental attribution error, an actor-observer asymmetry, or a self-serving bias shaped how the people involved (including you, if you were involved) initially explained the behavior, and how you know;
5. assesses whether a psychological contract, transactional or relational, is relevant to the case, and if so, whether a breach or violation played any role; and
6. states, honestly, what remains uncertain in your analysis and what additional information would resolve it.

Cite at least four academic sources, including at least three from this article's reference list. Where your evidence is incomplete or your case is your own professional experience rather than a published source, say so explicitly rather than presenting inference as fact.

Assessment rubric (100 marks)

1. Robbins, S. P., & Judge, T. A. (2023). Organizational behavior (18th ed.). Pearson.
2. Lewin, K. (1951). Field theory in social science: Selected theoretical papers (D. Cartwright, Ed.). Harper & Row.
3. Mischel, W. (1968). Personality and assessment. John Wiley & Sons.
4. Kelley, H. H. (1967). Attribution theory in social psychology. In D. Levine (Ed.), Nebraska symposium on motivation (Vol. 15, pp. 192–238). University of Nebraska Press.
5. Ross, L. (1977). The intuitive psychologist and his shortcomings: Distortions in the attribution process. In L. Berkowitz (Ed.), Advances in experimental social psychology (Vol. 10, pp. 173–220). Academic Press.
6. Rousseau, D. M. (1989). Psychological and implied contracts in organizations. Employee Responsibilities and Rights Journal, 2(2), 121–139. https://doi.org/10.1007/BF01384942
7. Rousseau, D. M. (1990). New hire perceptions of their own and their employer's obligations: A study of psychological contracts. Journal of Organizational Behavior, 11(5), 389–400.
8. Robinson, S. L., & Rousseau, D. M. (1994). Violating the psychological contract: Not the exception but the norm. Journal of Organizational Behavior, 15(3), 245–259.
9. Katz, D., & Kahn, R. L. (1966). The social psychology of organizations. John Wiley & Sons.
10. Argyris, C. (1960). Understanding organizational behavior. Dorsey Press.

Verification notes: all ten sources were checked via live web search against publisher or secondary citation records (title, journal or book, year, and volume/page details where stated) immediately before drafting; none were read in full. The Levinson, Price, Munden and Solley (1962) psychoanalytic treatment of the psychological contract is referenced in Section 4 as established background on the concept's origin, following the secondary sourcing found for Argyris (1960) and Rousseau (1989); it is not included as a separate numbered reference because its own publication details could not be independently confirmed in this research pass. The garment-sector supervisor example in Section 4 and the branch-operations officer scenario in Section 3 are both original, fictional teaching material constructed for this lesson and are explicitly labeled as such; no real company, person, or dataset is described by either.

Next in The Human Capital MBA series: Lesson 22 examines personality, perception, attitudes and workplace values in depth.