MT260 Unit 7 Decision-Making Analysis Example

Reviewed by Chester Goodwin, MBA Group and Organization Dynamics Purdue University Global Free custom sample in 24 to 48h

Four founders of a composite startup selling scheduling software to dance studios agreed in one afternoon to rebuild their whole product, estimated at nine months, and this MT260 Unit 7 decision-making analysis asks why the rebuild took twenty. A table shows what each knew and never said: the lead developer that only the payment module was failing, the writer as sales lead that three studio chains awaited a class-pass feature, the operations lead that cash covered fourteen months and the chief executive that an adviser had warned against a rebuild. Purdue Global MT 260 asks students to analyze a group decision in Unit 7, and the sample finds four of Janis's eight groupthink symptoms, then shows that Stasser and Titus's hidden-profile research explains the mechanism better. Its costs are counted. It counts toward the BS in Business Administration.

CourseMT260 Group and Organization Dynamics
UnitUnit 7
Paper typeDecision-making analysis
LengthAbout 1,130 words, 7 pages double-spaced
FormatAPA 7 student paper
SchoolPurdue University Global
ProgramBS in Business Administration
UpdatedOctober 2026

Free sample paper for MT260 Unit 7

1

Four Founders, Four Unspoken Facts: A Unit 7 Decision-Making Analysis of a Startup's Decision to Rebuild

[Student Name]

Purdue University Global

MT260: Group and Organization Dynamics

Unit 7 Decision-Making Analysis

[Instructor Name]

[Date]

The startup, its founders, the meeting and every figure are composite and illustrative; the sources cited are real.

What this part is doingPromising four unspoken facts in the lead sets up the analysis as a search for information the group never pooled.
2

The Decision

Barre Scheduling is a composite startup that sells scheduling and billing software to dance studios. It has four founders: a chief executive, a lead developer, an operations lead who also manages finance, and the writer, who leads sales. By its third year the company had about 340 studio customers, and its codebase, built quickly in the first year, had become slow and fragile. Pages took several seconds to load, and every new feature seemed to break something else.

At a half-day strategy meeting in February, the founders discussed the codebase for about ninety minutes and agreed unanimously to rebuild the entire application on a new framework. The lead developer estimated nine months. The rebuild took twenty, during which the company shipped almost no new features, lost two of its three largest prospects and came within two months of running out of cash.

What Each Founder Knew

After the rebuild, the writer asked each founder what they had known before the February meeting. The answers fill a short table.

Lead developer: most of the slowness came from the payment module, which handled billing and was badly written; the rest of the codebase was ugly but workable

Writer, sales lead: three studio chains, together worth about a fifth of projected revenue, were waiting on a class-pass feature that a rebuild would delay by many months

Operations lead: the company's cash covered about fourteen months of expenses at its current spending

Chief executive: an adviser with experience at two software companies had warned against rebuilding from scratch and suggested replacing the worst module first

Each of these facts pointed away from a full rebuild. Together they made a strong case for a narrower plan: fix the payment module, ship the class-pass feature and stay well within the cash runway. None was mentioned at the meeting.

What this part is doingSetting the four private facts side by side shows the better decision was available inside the room.
3

First Lens: Groupthink

Janis (1982) identified eight symptoms of groupthink: an illusion of invulnerability, collective rationalization, belief in the group's inherent morality, stereotyped views of outsiders, direct pressure on dissenters, self-censorship, an illusion of unanimity and so-called mindguards, people who filter what bad news reaches the rest.

Four of these appear in the meeting. The founders shared an illusion of invulnerability: they had built the product once and believed they could build it better and faster. There was collective rationalization: when the operations lead mentioned that the rebuild would be expensive, the chief executive said "we'll grow into it," and the discussion moved on. There was self-censorship: the writer did not mention the waiting chains, and the chief executive did not mention the adviser. And there was an illusion of unanimity, since silence was read as agreement.

The other four symptoms were absent. Nobody pressured a dissenter, because nobody dissented. Nobody acted as a mindguard. The founders did not stereotype outsiders or claim moral superiority. Groupthink explains part of the meeting but not its central feature, that each founder had information the others lacked and that information never entered the discussion.

Second Lens: The Hidden Profile

Stasser and Titus (1985) gave four-person groups a choice among candidates for student body president, with the facts about the candidates split: some went to every member, and some to only one. The better candidate could be identified only by putting the single-holder facts together, an arrangement later researchers called a hidden profile, and most groups missed it. Members discussed the information they all shared and rarely mentioned what only they knew, and the group chose what the shared information favored.

The Barre meeting fits this almost exactly. Everyone shared one piece of information: the codebase was slow and fragile. That shared fact pointed toward a rebuild, and the discussion stayed on it. The four unique facts, the payment module, the waiting chains, the runway and the adviser's warning, were each held by one founder and together pointed somewhere else. None was raised.

The meeting talked about the one thing everybody knew and decided on it.

Why did each founder stay quiet? The writer's own reason was that the waiting chains seemed like a sales problem, not a technical one, and the meeting was about technology. The lead developer later said he assumed the others wanted a fresh start and did not want to argue for keeping "his mess." The operations lead assumed the chief executive had already weighed cash. The chief executive did not want to seem to defer to an outsider. Each reason looks small. Together they hid the decision the founders would have made if they had pooled what they knew.

What the Decision Cost

The cost can be counted. The rebuild ran eleven months past its estimate. During those twenty months the company shipped two small features, compared with about one a month before. Two of the three waiting studio chains signed with a competitor that already offered class passes. The company's cash, which would have covered fourteen months at the old spending, ran low enough by month eighteen that the founders took a bridge loan on unfavorable terms. The rebuilt product is faster and easier to change, which was the goal. But a narrower plan, fixing the payment module first, would likely have delivered most of the speed in a few months without the lost customers or the loan.

Which Lens Explains More

Groupthink describes the mood of the meeting: confidence, rationalization and silence. The hidden-profile research explains its mechanism: the founders discussed shared information, never unique information, and chose accordingly. Forsyth (2019) notes that groups often outperform individuals only when they surface and combine members' unique knowledge. Barre's founders were four well-informed individuals who made a poorer decision together than any one of them might have made alone with all four facts.

What Would Have Helped

Three practices could have surfaced the hidden facts. Each founder could have been asked, before the meeting, to write down the one fact most relevant to the decision that the others might not know. The meeting could have assigned someone to argue against the rebuild. And the decision could have been split into a smaller first step, rebuilding the payment module, with a review after three months. Barre's founders knew each other's areas well; what they lacked was a habit of asking each area what it knew before deciding.

What this part is doingProposing practices that target unshared information shows the writer chose remedies that fit the mechanism found.
4

The Writer's Part

The writer held one of the four facts and did not speak. Of all the explanations in this paper, that is the one the writer can change.

5

References

Forsyth, D. R. (2019). Group dynamics (7th ed.). Cengage.

Janis, I. L. (1982). Groupthink: Psychological studies of policy decisions and fiascoes (2nd ed.). Houghton Mifflin.

Stasser, G., & Titus, W. (1985). Pooling of unshared information in group decision making: Biased information sampling during discussion. Journal of Personality and Social Psychology, 48(6), 1467-1478. https://doi.org/10.1037/0022-3514.48.6.1467

MT260 Unit 7 instructions, in plain terms

Unit 7 asks students to analyze a group decision that went wrong, using two or more decision-making frameworks. Begin with what was decided, by whom and what happened. The strongest analyses then reconstruct what each member knew before the decision, often through conversations afterward, because that shows whether the group had the information it needed. Apply each framework to specific evidence and say which explains more. Groupthink is a common choice but should be tested symptom by symptom; hidden-profile research is useful when information was spread unevenly. Propose practices that target the mechanism you found. Five pages is about right, with three or more scholarly sources cited in APA 7.

How the MT 260 Unit 7 example is put together

The analysis summarizes the company, the codebase problem and the February meeting that approved a full rebuild. A table lists each founder's private fact, and a margin note shows the better decision was available in the room. Janis's eight symptoms are checked, four present and four absent. The hidden-profile section describes Stasser and Titus's candidate experiment and applies it: the founders discussed the one fact they shared, and the highlighted line says they decided on it. Each founder's reason for silence is given. A section counts the cost in months, customers and a bridge loan. Forsyth helps judge which lens explains more, practices that would surface unshared facts follow, and the writer's own silence closes it.

Reading the MT260 Unit 7 grading rubric

Decision analyses are marked on an accurate account of the decision, evidence about what members knew, careful application of frameworks and a reasoned judgment between them. A table of what each member knew turns speculation into analysis. Instructors reward testing groupthink symptom by symptom, including those absent, rather than asserting it. Applying a second framework that explains the mechanism, and arguing which fits better, shows depth. Counting the decision's costs makes the stakes clear. Remedies should match the mechanism found, for example practices that surface unshared information. Including the writer's own part and citing the research accurately complete the rubric. Describing the original experiments correctly, such as the candidate choice Stasser and Titus used, matters because misdescribed studies lose credit quickly.

MT260 Unit 7 help from the desk

Students often call any bad group decision groupthink without checking whether the group was cohesive, pressured or defensive. Another common error is analyzing only the meeting, without asking what each member knew beforehand. Some papers describe Stasser and Titus's research inaccurately or apply it to a group where everyone had the same information. Others recommend vague fixes such as better communication. Report each member's reason for silence fairly, ideally in their own words from later conversations. A paper that treats everyone's silence, including the writer's, with the same care reads as analysis rather than blame. Tell us about the decision and who knew what, and a writer can build the information table and apply both frameworks to it.

Get an MT260 Unit 7 example written to your instructions

Pick a group decision that went badly and reconstruct what each person knew beforehand, as best you can. Pair that list with the Unit 7 prompt and the rubric. Written to your instructions and returned inside 24-48h, the first analysis is free, and people appear by role rather than name. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More MT260 papers and BS in Business Administration samples

MT260 Unit 7 questions, answered

Does the decision have to be a big one?

No. A small decision with a clear record often produces better analysis than a major one you know only secondhand. A committee choosing a venue, a team adopting a tool or a family deciding on a move can all work, provided you can reconstruct who knew what and how the discussion unfolded before the choice was made.

Is groupthink the only model I can use?

No, and many strong papers test it against an alternative. Hidden-profile research, the Abilene paradox, escalation of commitment and bounded rationality each explain different kinds of bad decisions. Choose the one your evidence supports, and if your section requires groupthink, apply it carefully and say where the fit is weak. A tested model earns more credit than an assumed one.

What if I was the person who made the mistake?

Say so plainly and analyze your part as you would anyone else's. The course asks how the group's structure shaped behavior, including yours, so explaining why you stayed quiet or pushed a view is analysis rather than confession. Instructors generally respect an honest account more than one that places the writer safely outside the decision.

Where can I find a free MT260 Unit 7 sample paper?

You can read the full MT260 Unit 7 decision-making analysis here. It examines four startup founders who agreed to a full rebuild while each held an unspoken fact against it, using groupthink and hidden-profile research.

Why does the MT260 Unit 7 sample prefer the hidden-profile explanation?

Groupthink fits the meeting's mood, but only four of its eight symptoms appear. The hidden-profile research explains the mechanism: the founders discussed the one fact they all shared and never pooled the four facts each held alone.