| Course | MBAX 6005 Organizational Perspectives and Implications for Leaders |
|---|---|
| Week | Week 2 |
| Paper type | Structural analysis |
| Length | About 940 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Master of Business Administration (MBA) |
| Updated | October 2026 |
Free sample paper for MBAX 6005 Week 2
Published Lines Versus Real Decisions: A Structural Analysis of Riverbend Regional Transit's Contactless Fare Rollout Through Mintzberg's Configurations
Student Name
Walden University
MBAX 6005: Organizational Perspectives and Implications for Leaders
Instructor Name
Month Day, Year
Published Lines Versus Real Decisions: A Structural Analysis of Riverbend Regional Transit's Contactless Fare Rollout Through Mintzberg's Configurations
Introduction
Riverbend Regional Transit, a composite bus agency with 310 buses running from four garages, launched contactless fare payment last fall. Within weeks, validators on older buses were dropping offline, some riders were charged twice and drivers had been told to wave riders through when a validator was dark. This analysis compares the agency's published structure with the structure that actually carried decisions during the launch, explains the mismatch with Mintzberg's configurations and proposes a coordinating mechanism the launch lacked.
The Published Structure
The published chart places a general manager over four departments: finance, operations, information technology and customer service. The fare project sits inside finance, under the revenue manager, because fares are counted as revenue. Operations runs the four garages, each under a superintendent, and the drivers. Information technology maintains the agency's systems, including the new validators. Customer service runs the call center. On paper the logic is sound: each department owns a function, and the fare project belongs to the department that owns the money.
Where Decisions Actually Went
During the launch, decisions moved through people the published chart barely shows. Garage superintendents decided, bus by bus, whether a vehicle with a dark validator stayed in service; all four kept such buses running to meet the timetable. The vendor's account manager decided which faults to fix first, working from a ticket queue that information technology passed to the vendor. Garage supervisors, two levels below the superintendents, issued the wave-through instruction to drivers. The call center absorbed rider complaints but had no line to anyone who could act on them; agents logged tickets that went to finance in a weekly report.
The finance department, which owned the project, made none of these decisions. It was the right owner for counting fares and the wrong owner for the moment a rider boarded a bus.
Table 1
Where Launch Decisions Were Made
| Decision | Published owner | Actual decision-maker | |
|---|---|---|
| Keep a bus with a dark validator in service | Finance, as project owner | Garage superintendents | |
| Order of validator repairs | Information technology | Vendor account manager | |
| What drivers do when a validator is dark | Not assigned | Garage supervisors | |
| Response to double-charge complaints | Customer service | No one; tickets went to a weekly finance report | |
Composite organization.
A Machine Bureaucracy Meets a Novelty
Mintzberg (1980) described several configurations, each with a typical way of coordinating work. A transit agency is close to his machine bureaucracy: it coordinates through standardized work processes, the timetable, the run cut and the maintenance schedule, set by analysts in a technostructure. That configuration is very good at repeating the same service every day. It is poor at handling a task that has no standard procedure yet, because its rules assume that work has already been worked out.
The fare launch was exactly such a task. It crossed four departments, depended on a vendor and produced problems no procedure anticipated. Galbraith (1974) argued that when uncertainty rises beyond what rules and hierarchy can absorb, a unit has two choices: cut how much information its work requires or build channels that carry more, such as direct links between departments. Riverbend did neither. The hierarchy routed every cross-department question up to the general manager, who learned of the wave-through instruction a month after it was given.
The Missing Mechanism
What the launch required was mutual adjustment, Mintzberg's term for coordination through informal communication among the people doing the work. In practice that means a liaison role with decision rights across departments. This analysis proposes a fare operations lead, reporting to the general manager for the duration of the rollout, with authority to pull a bus whose validator is dark, set the vendor's repair priorities and direct the call center's response to double charges. Lawrence and Lorsch (1967) found that organizations with highly differentiated departments need integrating roles to perform well, and Riverbend's four departments are highly differentiated by goals and time frames: finance thinks in monthly revenue, operations in the daily timetable.
The role has a cost. Operations would surrender some authority over which buses run, and finance would surrender control of the project it nominally owns. Both are likely to resist, which is a sign that the structural analysis has reached the limit of what structure alone can explain.
What the Structural Reading Cannot Yet Explain
Two facts sit awkwardly with a purely structural account. First, the wave-through instruction spread to all four garages within two weeks, faster than any formal procedure at Riverbend has ever traveled. A gap in structure explains why no one stopped it, but not why supervisors at four separate garages chose the same response at the same time. Second, the general manager learned of the instruction a month late, yet several people in operations and finance knew of it within days. Information was not missing; it was not passed upward. Both facts suggest that people had reasons to prefer the gap to stay open, and those reasons belong to a different frame. Bolman and Deal (2017) recommend testing a structural diagnosis by asking what it cannot account for, and these two facts mark where the next analysis should begin.
Conclusion
The published chart assigned the fare project to the department that owns revenue, which made sense for counting fares and none for running a launch. The decisions that shaped riders' experience were made by garage superintendents, a vendor and supervisors, outside any formal line of authority. Mintzberg's configurations explain why an organization built to repeat a timetable struggled with a novel task, and a liaison role with real decision rights is the structural remedy.
References
Bolman, L. G., & Deal, T. E. (2017). Reframing organizations: Artistry, choice, and leadership (6th ed.). Jossey-Bass.
Galbraith, J. R. (1974). Organization design: An information processing view. Interfaces, 4(3), 28-36. https://doi.org/10.1287/inte.4.3.28
Lawrence, P. R., & Lorsch, J. W. (1967). Differentiation and integration in complex organizations. Administrative Science Quarterly, 12(1), 1-47. https://doi.org/10.2307/2391211
Mintzberg, H. (1980). Structure in 5's: A synthesis of the research on organization design. Management Science, 26(3), 322-341. https://doi.org/10.1287/mnsc.26.3.322
What the MBAX 6005 Week 2 instructions ask for
Week 2 asks you to analyze one organization structurally. Show the formal structure first, then show where decisions were actually made during the event you are studying, ideally on one page, so a reader can compare them at a glance. Use a structural theory, such as Mintzberg's configurations, to explain why the organization handled the situation as it did. Propose a coordinating mechanism the situation required and say what it would cost in authority, since every structural fix takes power from someone. Close by naming what the structural reading cannot explain, which keeps the analysis honest and prepares later weeks. Four pages with APA headings and one decision table is a workable length.
Inside the MBAX 6005 Week 2 example
The introduction states the three launch failures and what the two charts will show. A section describes the published chart and its logic. The next section and a four-row table place real decision-makers against nominal owners, ending with the observation that finance made none of the key decisions. A section applies Mintzberg's machine bureaucracy and Galbraith's information-processing view, noting the general manager heard of the wave-through a month late. The proposal section describes a fare operations lead and cites Lawrence and Lorsch on integrating roles, then names the authority operations and finance would surrender. A section flags two facts that suggest a political explanation, citing Bolman and Deal. The two charts appear before any theory, so the reader sees the gap before being told what it means.
Reading the MBAX 6005 Week 2 rubric
Structural analyses are graded on whether the gap between formal and actual structure is shown, not asserted. Presenting both before interpreting them earns credit. Theory should be applied to the case with precision; naming the configuration and explaining why it fits matters more than summarizing Mintzberg. The proposed mechanism should follow from the diagnosis and include the authority it would move, since a fix that costs no one anything is rarely real. Recognizing the limits of the structural reading shows analytical maturity and is weighted. Tables should be labeled in APA style. A paper that redraws the chart without saying why decisions moved where they did loses most of the analysis credit.
MBAX 6005 Week 2 help: mistakes that cost marks
Get the official organization chart, or draw it from what the organization publishes. Then list four or five decisions that shaped the outcome and write down who actually made each. Where those names fall outside the chart's lines, you have your finding. Ask what kind of organization this is, what it is designed to do well and what it struggles with. Then propose one change to how departments coordinate, and say honestly who would lose authority. Finally, list anything your analysis cannot explain. Drafts often stop at the chart, or propose a reorganization with no mention of its costs. If you would like help mapping decisions in your organization, describe the event to us.
Get a MBAX 6005 Week 2 example written to your instructions
Attach your structural analysis prompt and rubric, and describe your organization's reporting lines in a few sentences, or ask the desk for a composite. The custom analysis returns in 24-48h, the first free, with the published chart set against the one your situation actually reveals and Mintzberg applied to the distance between them.
More MBAX 6005 papers and MBA samples
- MBAX 6005 Week 1: Four Frames Discussion Post
- MBAX 6005 Week 3: Political Frame Analysis
- MBAX 6005 Week 4: Two-Reading Case Analysis
- MBAX 6005 Week 5: Reflective Memo on Training
- MBAX 6005 Week 6: Symbolic Frame Analysis
- MBAX 6005 Week 7: Two-Frame Applied Assignment
- MBAX 6005 Week 8: Leadership Brief Memo
- MBAX 6005 Week 9: Negotiated Change Proposal
- MBAX 6005 Week 10: Peer Critique Discussion Reply
- MBAX 6005 Week 11: Final Four-Frame Paper
- WMBA 6882 Week 2: Failed Change Case Reconstruction
- WMBA 6695 Week 2: Single-Reader Audience Analysis
- WMBA 6633 Week 2: Coaching vs Mentoring Comparison
- WMBA 6627 Week 2: Stakeholder Identification Register
MBAX 6005 Week 2 questions, answered
Where can I find a free MBAX 6005 Week 2 sample paper?
The structural analysis, decision table and liaison proposal are posted on this page and free to read.
What gap does the MBAX 6005 Week 2 paper find?
Finance owned the fare project on paper, but garage superintendents, a vendor and supervisors made the decisions that shaped riders' experience.
Which Mintzberg configuration fits the agency?
The machine bureaucracy, which repeats a timetable well but struggles with tasks that have no standard procedure.
What mechanism does the paper propose?
A fare operations lead with authority to pull buses, set repair priorities and direct the response to double charges.
What can the structural reading not explain?
Why all four garages adopted the wave-through within two weeks and why information about it was not passed upward.