| Course | BU 502 Leadership and Team Dynamics |
|---|---|
| Unit | Unit 3 |
| Paper type | Behavioral diagnosis |
| Length | About 950 words, 6 pages |
| Format | APA 7 student paper |
| School | Herzing University |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for BU 502 Unit 3
"The Board Is Always Wrong": A Behavioral Diagnosis of Book-First, Fit-Later on a Composite Moving Company's Coordination Team
Student Name
Business, Herzing University
BU 502: Leadership and Team Dynamics
Instructor Name
April 20, 2026
"The Board Is Always Wrong": A Behavioral Diagnosis of Book-First, Fit-Later on a Composite Moving Company's Coordination Team
The Symptom in the Team's Words
Among the people who coordinate moves at this company, one sentence comes up more than any other: the board is always wrong. Coordinators say it when a customer calls about a job that has moved. The dispatchers say it when a crew lead phones at 6:30 a.m. about a truck that is not where the plan put it. Estimators say it when they offer a date the board showed as open and later hear it was not. In the eight weeks of the log, from February 9 to April 3, 2026, someone said it or wrote it in the huddle on 17 of 38 mornings.
The complaint locates the problem in a piece of software. This paper argues that the board is accurate about what people do to it, and that the problem is a repeated sequence of actions that the team's working conditions keep rewarding. The analysis describes behavior rather than personality, so no one is characterized as careless or difficult; the people in each role are doing what their situation makes sensible.
The Behavior Record
The log recorded every change to the board made after the Thursday planning session closed the following week. The record covers counts and sequences, not names.
| What happened after Thursday close | Count in 8 weeks | Who acted first | Who absorbed it |
|---|---|---|---|
| New job added to a closed day | 34 | Estimator | Senior dispatcher rebuilt the day |
| Customer asked to change a confirmed date | 15 | Coordinator | Dispatcher, then coordinator |
| Truck or crew unavailable | 12 | Crew manager | Junior dispatcher |
| Plan rebuilt after 4:30 p.m. | 19 of the 61 changes | Senior dispatcher | Senior dispatcher |
The Pattern as a Sequence
The largest category has a consistent shape. An estimator in a customer's home offers the date the customer asks for, including closed days and month-end dates. The estimator enters the job and, on 22 of the 34 occasions, also sends the senior dispatcher a direct message asking whether one more job can fit. The dispatcher says yes, then rebuilds the day by moving crews from other jobs or requesting a subcontracted truck. A coordinator then calls the customers whose crews or arrival windows changed. When the move day comes, the changed jobs produce more same-day problems: of the 19 Saturday problems the weekend coordinator reported, 13 involved a job moved or added after Thursday.
I call the pattern book first, fit later. The board looks wrong because it is being used as a record of decisions made somewhere else, in customers' homes and private messages, after the planning meeting has ended. The board is correct about what people do; the plan it shows on Thursday is simply not the plan anyone keeps.
The Conditions That Keep It Rewarded
Behavior that recurs this reliably is usually being rewarded. Kerr (1975) described organizations that pay for one behavior and then hope to get a different one, and that is the condition here. Four features of the team's situation pay each step of the sequence.
Estimators are paid for a signed date, not a delivered move
Estimators told me their monthly bonus counts signed bookings. A date refused in a customer's home is a lost booking, visible to the estimator and to the sales lead. A date offered that cannot be met costs the estimator nothing, because the cost appears later on someone else's desk.
The rescue is praised; the prevention is invisible
The general manager's Monday email thanks the people who saved difficult weekends, and in the eight weeks the senior dispatcher was thanked by name five times for late rebuilds. No email has ever thanked someone for a plan that did not need rebuilding. Repenning and Sterman (2001) describe this trap: firefighting earns visible credit, while the work that prevents fires earns none, so effort drifts toward firefighting.
Saying yes is the dispatcher's informal role
The direct message arrangement grew up alongside the formal process. It is quick, it feels helpful, and it gives the senior dispatcher a central position that the formal process does not. Refusing a request would mean refusing a colleague in a private conversation with no rule to point to.
The cost signal never reaches the people acting
I approve office overtime, and I have approved every rebuild request. Subcontracted trucks are charged to the operations budget rather than to any booking. Neither the estimator who added the job nor the dispatcher who absorbed it ever sees what the change cost. Wageman et al. (2005) treat the reward system a team works under as one of the conditions that shape its behavior, separate from the people in it, and on this team that system is silent about the cost of a late change.
The Diagnosis
The team's complaint is a symptom of a book-first, fit-later pattern at the estimator handover. The pattern persists because every step pays someone in the short term: the estimator keeps the booking, the dispatcher earns thanks and a central role, the customer gets the date and the lead gets a solved week. The costs, which include evening work, subcontracted trucks, Saturday problems and some of the damage claims, land later and diffusely, where nobody connected to the decision feels them. This also explains the stall described in Unit 2. The team cannot settle who owns the date, because the current arrangement rewards everyone for leaving the question open.
What the Diagnosis Does Not Claim
None of this means the estimators are wrong to want the booking or that the dispatcher ought to refuse every request. Some late additions are good business, and customers' closing dates genuinely fix some moves. It also leans on reports in two places: the bonus rule comes from the estimators' own description, and what is said in customers' homes reaches me only through the estimators. Unit 4 looks closely at one episode where the pattern produced open conflict, and that episode is a direct test of whether the sequence described here holds when it is watched closely.
References
Kerr, S. (1975). On the folly of rewarding A, while hoping for B. Academy of Management Journal, 18(4), 769-783. https://doi.org/10.5465/255378
Repenning, N. P., & Sterman, J. D. (2001). Nobody ever gets credit for fixing problems that never happened: Creating and sustaining process improvement. California Management Review, 43(4), 64-88. https://doi.org/10.2307/41166101
Wageman, R., Hackman, J. R., & Lehman, E. (2005). Team diagnostic survey: Development of an instrument. The Journal of Applied Behavioral Science, 41(4), 373-398. https://doi.org/10.1177/0021886305281984
BU 502 Unit 3 instructions, in plain terms
The third BU 502 unit asks for a diagnosis that starts with a symptom and ends at a behavior pattern and the conditions sustaining it. Expect to state the symptom in the team's own words, build a record of what happens, how often and in what order, name the pattern, and show which features of the work environment keep it rewarded. Assignment instructions at this level want sequences rather than traits, so nobody is labeled lazy or careless. Graduate work also asks the writer to look at their own behavior, and most instructors expect the leader to appear somewhere in the conditions. A colleague's performance problem should not become the subject; the pattern, not the person, is under analysis.
Inside the BU 502 Unit 3 example
The paper quotes the complaint and counts how often it surfaced, then reframes it: the board accurately records decisions being made elsewhere. A table sorts 61 post-close changes by type, first actor and who absorbed the work. The pattern section walks the sequence from an estimator's offer in a customer's home to a direct message, a late rebuild and a customer callback, and links 13 Saturday problems to it. Four run-in subsections then explain the conditions: bonuses for signed dates, praise for rescues, the dispatcher's informal yes role and a cost signal that never reaches anyone acting. The diagnosis ties back to the Unit 2 stall, and a closing section marks what rests on reports.
Reading the BU 502 Unit 3 rubric
Points in this unit typically go to the symptom statement, the behavior record, the named pattern, the explanation of sustaining conditions, the writer's self-inclusion and the writing itself. A symptom earns full marks when it is given in the team's language and its frequency is shown. The record criterion rewards counts and sequences over impressions. Naming the pattern is not enough on its own; the higher bands require that each step be connected to a condition that rewards it. Frameworks such as Kerr's earn credit when they explain this team rather than decorate the paper. Many rubrics reserve their top band for diagnoses that include the leader's own contribution without turning into confession.
Common BU 502 Unit 3 mistakes, and how to avoid them
Diagnoses go wrong when the cause is a person: a dispatcher who cannot say no or an estimator who overpromises. That reads as blame and ignores why the behavior is sensible from where each person sits. Some papers describe the symptom at length and never reach the pattern. Others list conditions without linking each one to a step in the sequence, so the explanation floats free. Leaving the leader out is a common gap; in the sample the lead's automatic overtime approvals hide the cost. If you are stuck turning a vague team complaint into a counted pattern, our writers can work from your notes to draft one for your own team.
Get a BU 502 Unit 3 example written to your instructions
Drop the BU 502 Unit 3 instructions into the thread with the rubric your classroom posts and any case the assignment attaches. We write a custom example that states the symptom in plain terms, records behavior as sequences, examines what keeps the pattern rewarded and answers the alternatives. First custom sample free, back in 24 to 48 hours.
More BU 502 papers and MBA samples
- BU 502 Unit 1: Team context and evidence base
- BU 502 Unit 2: Development stage analysis
- BU 502 Unit 4: Conflict episode analysis
- BU 502 Unit 5: Leadership style assessment
- BU 502 Unit 6: Psychological safety analysis
- BU 502 Unit 7: Intervention design
- BU 502 Unit 8: Team development plan
- BU 506 Unit 3: Root cause analysis
- BU 525 Unit 3: Gap analysis
- BU 530 Unit 3: Contingency and situational analysis
- BU 531 Unit 3: Risk profile per option
BU 502 Unit 3 questions, answered
How is this different from an undergraduate behavior case?
An undergraduate paper applies a named theory to a situation and shows the fit. This one starts from a symptom the team is living with and works back to what maintains it, with the writer accountable for the team in question. Theory is used where it explains something and left out where it does not, which is the graduate difference.
Can the diagnosis point at my own behavior?
Yes, and papers that do usually read as stronger. A leader who assigns urgent work to whoever answers fastest is part of the pattern that produces an overloaded colleague. Write your own actions in the same sequence form you use for everybody else, without confession or apology, since the point is the mechanism rather than blame.
Is it safe to describe a colleague's performance problem?
Only as a behavior pattern with the person de-identified, and never as a case for handling them. Performance ratings, warning letters and coaching records are employer documents and stay at work. Describe what happens in the flow of the work and what follows, keep the individual as a role, and leave any real employment matter to your organization's own process.
Where can I find a free BU 502 Unit 3 sample paper?
Nothing is held back: the BU 502 Unit 3 behavioral diagnosis appears in full at no charge, with the change counts, the four conditions and margin notes. Have a different team? Send the assignment and a short description and we will write a matching diagnosis free, typically within two days.
Does the BU 502 Unit 3 diagnosis need a theory?
It needs one that explains why the behavior keeps paying off. The sample uses Kerr on rewards that contradict stated goals and Repenning and Sterman on why firefighting earns credit while prevention earns none.