Send the exact assignment or rubric from your classroom and a custom sample written to it lands in 24 to 48 hours, the first one free. MBA 687 is SNHU’s Leading Organizational Change course. It centers on diagnosing why an organization needs to change, then leading it through the resistance and the reinforcement that decide whether the change holds. Searches like "mba 687 module 4 assignment example", "MBA687 sample paper", and "MBA 687 module samples" land on this page.
What MBA 687 is really about
MBA 687 is the course where the MBA stops being about analysis and starts being about people who do not want what you decided. The reading moves through diagnostic models, Kotter and Lewin among them, plus culture, communication planning, stakeholder mapping and the behavioral research on why competent adults resist sensible improvements. Most of the class has lived through at least one reorganization or system rollout that failed, and those memories are useful raw material. The course wants them structured, though. A grader is looking for a change effort you can describe as a sequence with named owners, not a story about how leadership handled things badly, and that shift catches people out on the first graded item.
Items in MBA 687 carry the usual SNHU label, a module number followed by a hyphen and the item's slot inside that module, which is why 3-2 Assignment turns up in searches far more often than any reading title. Many sections build toward a change plan or leadership memo delivered in pieces, with diagnosis and stakeholder analysis coming before the plan itself and the plan before the reinforcement section. That ordering is a common shape rather than an announced one, since instructors set their own sequence and syllabi stay inside the classroom. What does not vary is the destination: a document someone could hand to a leadership team, with an owner beside every action and a date range beside every phase.
What MBA 687’s assessments ask for
Discussions put a change scenario in front of the class and ask which model explains it, then expect you to answer a classmate who read the same scenario differently. Written items usually work from a company in trouble or in transition: diagnose the gap between current and desired state, map who gains and who loses, draft the message that goes to each group. Stepping stones assemble the final plan section by section, and the feedback attached to each one is supposed to reshape the next. The final deliverable is judged as a whole plan, so the resistance you predicted in an early section has to be handled in the later ones. Cite the models you lean on, and keep the recommendations specific enough that a reader can tell who does what.
Where students lose points in MBA 687
Two sections go missing from almost every weak change paper, and they are the two the rubric weights most. The first is resistance. Drafts name a communication plan, assume everyone reads it, and never say what happens when the shift supervisors quietly keep the old process running. The second is what comes after launch. Plans stop at go live, as though behavior holds by itself once training ends, when the research says it decays in the first few months without reinforcement. Write both. Name the group most likely to resist, say why their objection is rational from where they sit, and answer it. Then describe how the new behavior is measured, rewarded and corrected once the project team disbands.
The MBA 687 drawers
MBA 687 Module 1 Correspondence on a Failed Change example
Module 1 correspondence to a new general manager explaining why the branch's last system rollout collapsed: an email mandate from headquarters, no local sponsor, training at the wrong hour and the cynicism it left behind. Full sample paper, annotated.
MBA 687 Module 2 Stakeholder Analysis Memo example
A module 2 memo on why stakeholder analysis matters before a platform consolidation: eight groups rated for power, legitimacy and urgency, what each stands to gain or lose, and how the map changes the plan. Full sample paper, annotated.
MBA 687 Module 3 Milestone One Change Readiness Assessment example
Milestone One: a change readiness and cultural needs assessment for a U.S. software branch facing a global platform mandate, with survey results on five readiness beliefs, a culture analysis across the Pacific and the needs the plan must meet. Full sample paper, annotated.
MBA 687 Module 4 Change Model Diagnostic Report example
A module 4 report that diagnoses a software branch with the Burke-Litwin model, factor by factor, then compares Lewin, Kotter and ADKAR and explains which combination fits the platform change and why. Full sample paper, annotated.
MBA 687 Module 5 Milestone Two Change Management Plan example
Milestone Two: the draft change management plan for a software branch's platform move, with key stakeholders and why they matter, four strategic goals, changes to organizational systems, cross-border team collaboration and each expected objection answered. Full sample paper, annotated.
MBA 687 Module 6 Strategic Considerations Presentation example
A module 6 presentation to branch and headquarters leaders on rolling out a platform consolidation: three client migration waves, a named owner for each action, a message for each affected group, the launch sequence and the gates that decide whether to proceed. Full sample paper, annotated.
MBA 687 Module 7 Model Leadership Behavior Memo example
A module 7 memo to a branch leadership team on the behaviors leaders must model during a platform change: five behaviors with what they look like on a Tuesday, the habits to stop and how employees will judge whether leaders mean it. Full sample paper, annotated.
MBA 687 Module 8 Final Project Change Management Plan example
The final change management plan for a software branch's move onto its parent's global platform: the justification, readiness findings, operating plan by wave with owners and gates, workforce development, resistance and the measures that keep the change in place after launch. Full sample paper, annotated.
Your classroom shows something else?
Southern New Hampshire University revises courses; module counts and deliverables shift between terms. Send what your classroom shows and the desk matches it exactly.
Using a MBA 687 sample the right way
Read a sample with two questions in hand: where does resistance first appear, and how far past launch does the plan run? Those two answers tell you more about why it scored well than the diagnosis section will. Then compare against your own outline and see whether either section exists in it yet. Send the posted instructions and rubric from your section and the first custom sample is free, back inside 24-48h and written to what you were actually assigned. Treat it as a working model, not a finished submission. The organization, the people who will resist and the plan you would defend to them are yours.
How these samples are written
The discipline behind every paper here: the rubric is the outline, each row gets its section, milestone sequences stay coherent so the final submission reads as one build, and the format layer ships exact. Send your dash-code and rubric with a request and the sample matches them, revisions included.
MBA 687 questions, answered
Do I have to use Kotter, or can I pick another model?
Any established model is acceptable as long as you carry it through. The failure is not choosing the wrong one, it is naming a model in the introduction and then writing a plan that follows none of its stages. Pick the one that fits your scenario, cite it, and let its structure show up in your headings so the grader can see the fit.
How much detail does the resistance section need?
Enough to name specific groups and specific objections. Saying employees may resist earns little; saying the regional managers lose discretion over scheduling and will slow adoption until the incentive changes gives the grader something to score. One paragraph per affected group, each with the objection and your response to it, usually covers what the rubric wants without padding the plan.
Can the change effort be one I actually led at work?
Yes, and it tends to produce a stronger plan because you already know where the friction sat. Two constraints keep it safe: strip anything that identifies a person or exposes employer confidential detail, and build the argument on published research rather than on your authority as the person who was there. Your experience selects the case; the sources carry the claim.