| Course | BUS 799 Graduate Capstone |
|---|---|
| Module | Module 5 |
| Paper type | Discussion post |
| Length | About 475 words |
| Format | Discussion post with APA 7 citations |
| School | Aspen University |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for BUS 799 Module 5
Module 5 Discussion: Initial Post
The People Who Decide Whether the Billing Cutoff Survives
My capstone at a composite electrical subcontractor found that about 19 of our 71 days of receivables come from our own practices: a 12-day lag before we submit payment applications, missing lien waivers that get applications rejected, and change work started before the change order is signed. The fixes are not technically hard. A firm billing cutoff, a document checklist, and a rule that no change work starts without a signature would do most of it. Whether they survive depends on people, so this week I mapped our stakeholders. Not every cause is ours to fix; research on construction payment finds that the financial position of other parties drives many delays (Ramachandra & Rotimi, 2015), which is why my plan concentrates on the parts we control.
Mitchell et al. (1997) argued that managers attend to a stakeholder in proportion to how many of three attributes it holds: the ability to impose its will, a claim others accept as proper, and a claim that demands prompt action. Applying their framework, the owners have power and legitimacy, and after seeing the findings they have urgency too; they are the definitive stakeholders who approved the project. The general contractors, especially our largest customer, have power, since they approve and pay our applications, and a legitimate interest in complete paperwork, but little urgency about our cash. Project managers are the surprise. On paper they have little formal power over the project, but in practice nothing changes unless they submit quantities by the cutoff, and they can quietly let it slip. Billing staff have legitimacy and urgency, since they absorb the late scramble every month, but little power. Field foremen matter for the change order rule, because they are the ones who hear a general contractor's superintendent say "go ahead."
Kotter (1995) listed errors that sink change efforts, and three shape my plan. First, not establishing enough urgency: I will show project managers what 21 days means in cash, about $2.19 million, and that the company borrows to cover payroll while it waits. Second, not creating a powerful guiding coalition: the change group will include the controller, one owner, and two respected senior project managers, so the cutoff is not seen as an accounting rule imposed on the field. Third, not planning for short-term wins: the pilot on two projects will report the first month's billing lag and rejection count at a company meeting, so people see the change working before it spreads. I will also try to remove an obstacle Kotter emphasizes, by having billing staff pre-fill applications from the schedule of values so that project managers only confirm quantities.
Question for classmates: in your capstones, did the stakeholders with formal authority or the ones who do the daily work turn out to matter more for whether the change stuck?
References
Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59-67.
Mitchell, R. K., Agle, B. R., & Wood, D. J. (1997). Toward a theory of stakeholder identification and salience: Defining the principle of who and what really counts. Academy of Management Review, 22(4), 853-886. https://doi.org/10.5465/amr.1997.9711022105
Ramachandra, T., & Rotimi, J. O. B. (2015). Causes of payment problems in the New Zealand construction industry. Construction Economics and Building, 15(1), 43-55. https://doi.org/10.5130/ajceb.v15i1.4214
Reading the BUS 799 Module 5 assignment instructions
Aspen's BUS 799 Module 5 discussion typically asks you to identify stakeholders for your capstone's changes and describe how you will lead the change. Summarize the changes briefly. Use a recognized framework to assess each stakeholder. Look for stakeholders whose informal influence exceeds their formal power. Apply a change model to plan specific actions. Note what your plan cannot control. Invite replies with one question. Hold to the posting length, and keep the organization composite, describing people by role rather than name, since classmates do not need to know who your colleagues are to follow the analysis.
How this BUS 799 Module 5 example is built
The post opens with the capstone's finding and the three fixes. It notes that not every cause is the company's to fix. It introduces Mitchell and colleagues' salience framework and applies it role by role: owners as definitive stakeholders, general contractors with power and legitimacy but little urgency, billing staff with urgency but little power and foremen who hear verbal go-aheads. A highlighted sentence identifies project managers as the surprise: little formal power, but nothing changes unless they meet the cutoff. Three of Kotter's errors shape the plan: urgency through showing $2.19 million in cash, a guiding coalition with respected senior project managers and short-term wins from the pilot. The post adds pre-filled applications to remove an obstacle and asks classmates which stakeholder surprised them.
Reading the BUS 799 Module 5 grading rubric
Discussion posts in BUS 799 earn marks for accurate use of a stakeholder framework, specific change actions, insight into informal influence and engagement. This post earns credit by identifying project managers as the critical stakeholders despite their low formal power, which shows graders analysis rather than a list. Mitchell, Agle and Wood's 1997 article in the Academy of Management Review supplies the salience framework. Kotter's 1995 Harvard Business Review article supplies the errors that shape the plan, and Ramachandra and Rotimi's 2015 study explains why some causes lie outside the company. Translating 21 days into cash to build urgency connects the change plan to the financial case. The closing question invites comparison across classmates' projects.
BUS 799 Module 5 help: mistakes that cost marks
Stakeholder posts often list groups without assessing them. Use a framework. Another common gap is ignoring informal influence; ask who can quietly stop the change. Students also cite Kotter's eight steps without choosing actions. Pick the errors that matter most and plan against them. Show urgency in numbers. Build a coalition with respected insiders. Plan an early win. Note what you cannot control. Keep within the word count. Describe people by role. In replies, suggest a stakeholder a classmate may have missed. Finally, connect the post to your findings module, since stakeholder plans are strongest when they target the specific behaviors the data showed must change.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
More BUS 799 and MBA sample papers
- BUS 799 Module 1: Capstone Project Proposal
- BUS 799 Module 2: Capstone Literature Review
- BUS 799 Module 3: Capstone Methodology
- BUS 799 Module 4: Capstone Findings
- BUS 799 Module 6: Capstone Recommendations
- BUS 799 Module 7: Capstone Financial Justification
- BUS 799 Module 8: Final Capstone Presentation
- BUS 560 Module 1: Personal Values and the Manager
- BUS 552 Module 7: Game Theory in Venture Decisions
- BUS 510 Module 5: Product Costing
- BUS 551 Module 1: Agency Theory
BUS 799 Module 5 questions, answered
What does the BUS 799 Module 5 discussion usually ask for?
Discussions in the middle of a graduate capstone often ask about stakeholders, change management or implementation challenges for your project. Aspen does not publish module deliverables, so your classroom's instructions govern.
What is stakeholder salience?
A framework by Mitchell, Agle and Wood holding that managers pay attention to stakeholders according to their power, the legitimacy of their claim and the urgency of that claim.
What are Kotter's reasons change efforts fail?
Among them are not establishing enough urgency, not forming a powerful guiding coalition, undercommunicating the vision, not removing obstacles, not planning for short-term wins, declaring victory too soon and not anchoring changes in the culture.
Where can I find a free BUS 799 Module 5 sample paper?
The full BUS 799 Module 5 post is above, mapping stakeholders by power, legitimacy and urgency for a capstone's billing changes and planning the change with Kotter.
Why are project managers the key stakeholders in BUS 799 Module 5?
They have little formal power over the capstone, but the cutoff fails unless they submit quantities on time, and they can let it slip quietly, so two respected senior project managers join the guiding coalition.