| Course | BUS FPX 4013 Organizational Structure, Learning, and Performance |
|---|---|
| Assessment | Assessment 2 |
| Paper type | Organizational learning analysis |
| Length | About 1,080 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Business |
| Updated | September 2026 |
Free sample paper for BUS FPX 4013 Assessment 2
A Lesson the Organization Kept Failing to Learn: Field Technicians' Knowledge of a Recurring Pump Failure That Never Reached Design Engineering
Student Name
Capella University
BUS FPX 4013: Organizational Structure, Learning, and Performance
Instructor Name
Month Day, Year
One Lesson, Specifically Identified
At Northgate Appliances, the composite appliance maker whose warranty process was diagnosed earlier, field service technicians have known for about three years that a drain pump used in two dishwasher models fails early when customers use a particular high-temperature cycle frequently. The pump's seal degrades, and the dishwasher begins leaking. Technicians replace the pump, and many have learned to advise customers to use the high-temperature cycle less often, a workaround passed informally from technician to technician. The lesson is specific: the pump seal is not suited to repeated high-temperature cycles, and the design should use a different seal or limit the cycle. Stating the lesson this precisely matters, because a vague lesson, such as "pumps sometimes fail," could never be acted on. The organization, as distinct from individual technicians, has not learned it: the same pump is still used in current production.
The Path It Could Have Traveled
The lesson could have traveled from technicians to design engineering by several routes. Technicians record each repair in the service system, including the failed part and a free-text note on the cause. Service operations managers review repair data monthly. Quality engineering analyzes warranty data for defect trends and can request design changes. Design engineering updates products based on quality engineering's requests. The intended route was: technician repair notes, to service operations reports, to quality engineering analysis, to design engineering change. Each step existed, and each department was doing its job as defined. Argyris (1977) distinguished single-loop learning, in which an organization corrects errors within its existing practices, from double-loop learning, in which it questions the assumptions behind those practices; the technicians' workaround, advising customers to avoid the cycle, is single-loop learning, while changing the design would be double-loop. Mapping the path the lesson could have traveled shows that the route existed, which makes the failure a matter of where it was blocked.
The Block Named Precisely
The block is located precisely. Technicians recorded the pump failures accurately as part replacements, and about 60% of their free-text notes mentioned heavy use of the high-temperature cycle. Service operations reports summarized repairs by part and cost but did not include the free-text notes. Quality engineering's warranty analysis flagged the pump as having an elevated failure rate, about 3.1% within two years compared with a design target of 1%, but attributed failures to "customer usage" because the failures were concentrated among customers who used the high-temperature cycle, and the company's defect rules classified failures linked to how customers used a product as usage-related rather than as design defects. Usage-related failures do not generate design change requests. The block, then, is the defect classification rule in quality engineering: it treated a design unsuited to a normal, advertised cycle as a customer usage problem. The technicians' notes, which described the cause, never reached anyone who could question that classification, because the reports that crossed the departmental boundary dropped the notes.
Repetition as the Evidence
The evidence that the organization failed to learn is repetition. Over three years, technicians replaced the same pump about 4,800 times under warranty. The failure rate did not fall over those three years. The same free-text explanation appeared in thousands of notes. Two newer dishwasher models introduced during that period used the same pump, carrying the problem into new products. Customer reviews mentioning leaks rose. If the organization had learned, the repetition would have stopped: the design would have changed, and the failure rate in newer units would have fallen. Repetition of the same failure, with the same cause recorded, is the clearest evidence that knowledge held by some members did not become knowledge held by the organization. Individual technicians learned; the organization, which designs and builds the product, did not.
Why the Block Persisted
The block persisted because the classification rule served a purpose: it prevented design engineers from being flooded with requests to change products for misuse, such as overloading. The rule was reasonable in general but wrong for this case, because the high-temperature cycle is a normal feature that the company advertises. No one had a role in reviewing whether usage-related classifications were correct, so the rule was never questioned, even as the same explanation appeared in thousands of repair notes. Edmondson (1999) found that teams learn when members feel safe raising problems and questioning assumptions; here, the problem was not reluctance to speak but the absence of any route by which the technicians' explanation reached the people applying the rule.
The Cost of Not Learning
The failure to learn has been costly. At about 180 dollars per warranty pump replacement, including the part, technician time, and travel, the 4,800 replacements cost about 864,000 dollars over three years. The damage to the brand from leaking dishwashers, reflected in rising negative reviews, is harder to measure but likely larger. A design change to a better seal, estimated by engineering at about 2 dollars more per unit, would have cost far less than the repairs if made when the pattern first appeared.
A Fix to the Route
The fix changes the route rather than asking people to share more. First, service operations reports sent to quality engineering will include a summary of free-text notes for any part whose failure rate exceeds its design target, grouped by the most common explanations. Second, quality engineering's defect rules will be revised: a failure linked to a normal, advertised product feature is classified as a design issue, not as customer usage. Third, any part whose failure rate exceeds twice its design target for two consecutive quarters triggers a joint review by quality engineering, design engineering, and a senior field technician. Fixing the route ensures that the next lesson from the field can reach the people who can act on it.
Conclusion
Field technicians learned that a dishwasher pump fails under heavy use of a normal cycle, but the organization did not learn it for three years. The lesson could have traveled from repair notes to design changes, but it was blocked by a defect classification rule and by reports that dropped the technicians' explanations. Repetition of the same failure is the evidence, and the fix is to change the route so that field knowledge reaches design.
References
Argyris, C. (1977). Double loop learning in organizations. Harvard Business Review, 55(5), 115-125.
Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. https://doi.org/10.2307/2666999
What the BUS FPX 4013 Assessment 2 instructions ask for
The instructions ask you to analyze how an organization learns, or fails to learn, from experience. You identify a specific lesson or piece of knowledge, describe where it was learned and where it needed to go, trace the path it could have taken, identify what blocked it, explain why the block persisted, estimate the cost and recommend a change. Concepts such as single-loop and double-loop learning, knowledge management and absorptive capacity support the analysis. The best evidence is repetition: the same mistake happening again shows the lesson was not learned. The analysis often connects to the structural diagnosis from Assessment 1, since structure shapes how knowledge moves.
How the BUS-FPX4013 Assessment 2 example is put together
The lesson, the route, the block, the fix. The opening names what was learned and by whom, with enough substance behind it to show this was genuine knowledge rather than somebody's impression. The route block establishes where that knowledge needed to travel and by what path it could have, naming the people and the mechanisms available. The block itself is then located: a boundary it never crossed, a record nobody kept, a person who left, a channel that carried it to somebody with no authority to act. A short block asks what happened next time, since repetition is the evidence that learning failed. The fix addresses the route rather than the people. The closing says how anybody would know it had worked. Individuals stay unidentifiable.
Where the marks sit in the BUS FPX 4013 Assessment 2 scoring guide
Grading covers how precisely the lesson is identified, the path analysis, the block, the evidence, the cost and the recommendation. The lesson reaches Distinguished when specific, such as technicians knowing a seal fails in hard water, rather than a general claim that knowledge is lost. The path scores higher when it names who knew, who needed to know and every step between. The block earns credit when named precisely, like warranty reports with no field for cause of failure. Repetition as evidence strengthens the case. The cost of not learning should be estimated, and the fix should change the route rather than exhort people to share.
Common BUS FPX 4013 Assessment 2 mistakes, and how to avoid them
Students often describe organizational learning in general, with no specific lesson. Another common mistake is blaming people for not sharing, when the route for sharing does not exist. The path is not traced. Evidence is anecdotal. The cost is ignored, though repeated failures have real warranty costs. The recommendation is a knowledge-sharing culture, which cannot be implemented on Monday. A specific fix, such as adding a cause field to service reports reviewed monthly by engineering, turns the analysis into action. Name who owns the fix and how the organization will know the lesson has finally reached design, such as the next pump model using a different seal.
Get a BUS FPX 4013 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and your BUS FPX 4013 scoring guide, along with the organization your first assessment diagnosed. We write a custom example against those criteria and return it in 24 to 48 hours. The first custom sample is free, and following one lesson along its route is what separates this from a training paper. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More BUS FPX 4013 papers and BS in Business samples
- BUS FPX 4013 Assessment 1: Structure Diagnosis
- BUS FPX 4013 Assessment 3: Performance Systems Proposal
- BUS FPX 4014 Assessment 2: Quality and Capacity Study
- BUS FPX 4012 Assessment 2: Framework Application Case
- BUS FPX 4015 Assessment 2: Strategic Objectives Set
- BUS FPX 4011 Assessment 2: Collaboration Technology Evaluation
BUS FPX 4013 Assessment 2 questions, answered
What counts as an organizational lesson?
Anything the organization discovered that should change what it does next time. A failure mode, a customer insight, a shortcut that works, a supplier who cannot be relied on. The test is whether somebody elsewhere would act differently knowing it, because that is what makes the transmission worth analyzing.
Is this the same as knowledge management?
Related, and narrower here. Knowledge management usually means systems and repositories. This assessment asks what happened to a specific piece of knowledge, which often has nothing to do with a system and everything to do with whether the person who learned it ever met the person who needed it.
What if the organization did learn successfully?
Then analyze how, which is less common and just as valid. Identify what carried it: a short route, somebody who wrote it down, a review that forced the question. Explaining why a transmission worked demonstrates the same understanding as diagnosing why one failed, and it gives the recommendation something proven to build on.
Where can I find a free BUS FPX 4013 Assessment 2 sample paper?
This page holds the full learning analysis of the recurring pump failure, with the lesson, the path, the block, repetition as evidence, the cost and a fix to the route. It connects back to the structural diagnosis.
What is double-loop learning in BUS FPX 4013 Assessment 2?
Learning that questions the assumptions and routines behind a problem, not just fixing the immediate error. Changing how field knowledge reaches design is double-loop; replacing each failed pump is single-loop.