| Course | MKT 838 Complexity of Marketing |
|---|---|
| Topic | Topic 2 |
| Paper type | Hit attribution post-mortem |
| Length | About 960 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for MKT 838 Topic 2
Two Matched Launches, One Hit: A Post-Mortem That Finds the Divergence in Feedback, Not in the Campaign
[Author Name]
College of Doctoral Studies, Grand Canyon University
MKT-838: Complexity of Marketing
Topic 2 Post-Mortem
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Two Matched Launches, One Hit: A Post-Mortem That Finds the Divergence in Feedback, Not in the Campaign
Two Launches
A composite mobile game studio launched two puzzle games a month apart. In pre-launch playtests the games scored almost identically: day-one retention of about 41 percent for the first, Tile Garden, and about 40 percent for the second, Gem Loop, with similar session lengths and ratings. Both launched with matching campaigns: the same budget, the same twelve creators paid to post gameplay videos in the first week and the same app store advertising. Tile Garden reached the top-grossing chart within three weeks. Gem Loop faded within a month. The studio's internal review credits Tile Garden's campaign, citing its creators' videos. This post-mortem reconstructs the first fortnight of each launch and locates the divergence in feedback rather than in anything the campaign did. Figures are illustrative.
The First Fortnight, Reconstructed
For the first two days, the launches looked alike: about 9,000 installs a day for each, driven by the paid creator videos and advertising. On day three, a popular streamer who had not been paid played Tile Garden for an hour on a live broadcast, apparently by chance. Installs that day rose to about 21,000. On day four, Tile Garden entered the top 50 of the store's puzzle chart, where the store's own listing gave it visibility to people browsing the category. Installs rose to about 30,000 a day and stayed there, pushing the game higher. Gem Loop, with no comparable event, peaked at about 11,000 installs on day three and stayed just outside the top 50, where chart visibility drops sharply.
Table 1
Daily Installs Over the First Fortnight, Illustrative
| Day | Tile Garden installs | Gem Loop installs | Note |
|---|---|---|---|
| 1 | About 9,000 | About 9,000 | Paid campaigns begin |
| 2 | About 9,500 | About 9,400 | Campaigns identical |
| 3 | About 21,000 | About 11,000 | Unpaid streamer plays Tile Garden |
| 4 | About 30,000 | About 10,500 | Tile Garden enters top 50 |
| 7 | About 34,000 | About 8,000 | Chart visibility compounds |
| 14 | About 41,000 | About 5,000 | Gem Loop leaves the chart range |
Where the Divergence Lies
The campaigns were matched and performed similarly in the two days they alone drove installs. The divergence began with an unplanned event on day three and grew through a feedback loop. Chart rank drove visibility, visibility drove installs, installs raised rank, and more players produced more ratings, reviews and word of mouth, which drove more installs. Sterman (2000) describes such reinforcing loops as the source of exponential growth and of the sensitivity of outcomes to small early differences. Once Tile Garden crossed into the top 50, the loop carried it; Gem Loop, just below, never got the loop started.
Increasing Returns and Small Events
Arthur (1989) showed that in markets with increasing returns, where each adoption makes further adoption more likely, small chance events early in a competition can determine which product wins, and the outcome can lock in even if the winner is not the better product. App store charts create such returns: rank brings visibility, which brings more adoption. Salganik et al. (2006) demonstrated experimentally that when people can see others' choices, outcomes become more unequal and less predictable, and that similar products can meet very different fates depending on early luck. The two games fit that pattern closely: nearly identical products, identical campaigns, different early luck, very different outcomes.
Checking the Explanation
The feedback explanation makes predictions that the studio's data can check. If chart visibility drove Tile Garden's growth, the share of its installs coming from store browsing, as opposed to search or links, should have jumped when it entered the top 50, and the store's analytics show that share rising from about 20 percent to about 55 percent within two days. If the campaign drove the difference, installs attributed to creator links should have been higher for Tile Garden, but they were about the same for both games throughout the fortnight. And if the games' quality differed, retention among players acquired in the first days should differ, but it remained nearly identical. Each check points the same way.
What the Studio's Review Got Wrong
The internal review credits Tile Garden's campaign because the campaign is what the studio controlled and what it can repeat. But the campaign cannot explain the difference between the two games, because the two campaigns were the same. Crediting it risks the wrong lesson: spending more on creator videos for the next game in the belief that they produced a hit, when the hit came from a feedback loop the campaign started equally well in both cases.
What the Studio Can Learn
The studio cannot plan for an unpaid streamer, but it can plan for the loop. If chart position near the top 50 is the threshold at which visibility compounds, the studio can concentrate its launch spending in the first few days to push a game past that threshold, rather than spreading the same budget across a month. It can monitor installs daily and add spending when a game approaches the threshold, as Gem Loop did on day three. And it can stop judging launch campaigns by whether the game became a hit, since that outcome depends heavily on events no campaign controls, and judge them instead by whether they delivered the installs and ranking they were designed to deliver.
Conclusion
Two nearly identical games with identical campaigns diverged because one encountered a chance event that pushed it over a ranking threshold, where reinforcing feedback took over. The campaign did not cause the hit, and crediting it would teach the studio the wrong lesson. The better lesson is to design launches around the feedback loop and to judge campaigns by what they can control, such as reach, cost and the quality of early reviews, rather than by outcomes that luck decides.
References
Arthur, W. B. (1989). Competing technologies, increasing returns, and lock-in by historical events. Economic Journal, 99(394), 116-131. https://doi.org/10.2307/2234208
Salganik, M. J., Dodds, P. S., & Watts, D. J. (2006). Experimental study of inequality and unpredictability in an artificial cultural market. Science, 311(5762), 854-856. https://doi.org/10.1126/science.1121066
Sterman, J. D. (2000). Business dynamics: Systems thinking and modeling for a complex world. Irwin/McGraw-Hill.
What the MKT 838 Topic 2 instructions ask for
The Topic 2 assignment in MKT-838 asks doctoral students to explain why similar products launched in similar ways met different fates. Strong post-mortems reconstruct the early period in detail, locate where outcomes diverged, and explain the divergence with theory on reinforcing feedback, increasing returns and social influence. Students should test the explanation against the organization's data, show why crediting the controllable campaign teaches the wrong lesson, and recommend how future launches and their evaluation should be designed. The explanation should be checked against data the organization already holds.
How the MKT-838 Topic 2 example is put together
The finished post-mortem sets the twin launches side by side, day by day, for their first two weeks. Divergence begins on day three, when the eventual hit received an editorial feature slot that the studio did not buy and whose timing it did not choose. Chart position then fed visibility, visibility fed installs and installs fed position again, a loop the critique draws with the store's ranking rules described from public documentation. Arthur's work on increasing returns frames the pattern, showing how small historical events can lock a market onto one of several possible outcomes. MusicLab, the artificial music market run by Salganik, Dodds and Watts, supplies the evidence that such outcomes resist prediction, since the same songs finished at very different ranks in parallel worlds. The campaign is credited with raising both games' chances and with nothing beyond that.
Reading the MKT 838 Topic 2 rubric
Faculty reward a post-mortem that locates divergence in feedback. An Excellent paper tables daily installs and shows identical campaigns until day three. Credit goes to Sterman's reinforcing loops and Arthur's increasing returns and lock-in. The rubric values Salganik, Dodds and Watts on unpredictability with visible counts. Strong papers check the account against store-browsing share, creator-link installs and retention. Top marks go to concentrating launch spending near the chart threshold and judging campaigns by what they control. Post-mortems that credit the controllable campaign without comparing launches miss the topic.
MKT 838 Topic 2 help: mistakes that cost marks
Crediting the winning campaign because it came before the hit is the characteristic error here, and a critique that repeats it in softer language has only renamed the review. Papers also slip when they call the result pure luck, which ignores the loop that turned one chance placement into a lasting lead. The twin game is the strongest evidence available, yet many drafts analyze the hit alone and leave nothing to compare it against. Readers who take MusicLab to show that quality is irrelevant have misread it, since the study found the best songs rarely finishing last and the worst rarely winning. Post-launch ratings are frequently offered as proof of superior quality, although they were collected from an audience the hit's visibility assembled. A rewritten attribution that still names a single cause leaves the review's logic intact.
Get an MKT-838 Topic 2 example written to your instructions
Send the MKT-838 Topic 2 instructions, the rubric your classroom shows and the launch or case your section assigned. A custom example is written to those criteria, with the compared cases set side by side, the amplifying loop located, the quality objection answered and the attribution restated in defensible terms, and it arrives in 24 to 48 hours. The first one is free.
More MKT 838 papers and DBA samples
- MKT 838 Topic 1: Near-decomposability Essay
- MKT 838 Topic 3: Peer Effects Literature Review
- MKT 838 Topic 4: Product Seeding Memo
- MKT 838 Topic 5: Contribution Claim Dq Post
- MKT 838 Topic 6: Emergent Brand Meaning Case Study
- MKT 838 Topic 7: Agent-based Model Critique
- MKT 838 Topic 8: Interaction-aware Budget Recommendation
- MKT 834 Topic 2: Causal Identification Essay
- MKT 832 Topic 2: Consideration Set Construction Analysis
- MKT 830 Topic 2: Redefinition Trace Paper
MKT 838 Topic 2 questions, answered
Why can't a studio predict which launch will become a hit?
Because in markets where people see what others choose, early differences compound. The MusicLab study by Salganik, Dodds and Watts demonstrated it in an online music market split into separate worlds: where participants saw download counts, the same songs finished at very different ranks from world to world. Quality set limits, since the strongest songs seldom came last, but the middle of the field stayed open. The example applies that finding to game charts.
What are increasing returns in a market?
A condition in which an option becomes more attractive the more people have already adopted it, through visibility, compatibility or social proof. W. Brian Arthur showed how, under increasing returns, minor chance events early on can lock a market onto one of several possible outcomes, not necessarily the best. The example finds that condition in the app store's ranking rules and uses it to explain why one feature slot decided a launch.
So did the campaign do nothing?
Not necessarily, and the example avoids that overcorrection. Both games received matching campaigns, which likely raised each one's chance of catching the early attention the loop amplifies. What the evidence cannot support is crediting the campaign with the difference between them, since the campaigns were the same and the outcomes were not. The rewritten attribution sentence keeps the campaign's plausible role and drops the claim of decisive cause.
Where can I find a free MKT 838 Topic 2 sample paper?
The post-mortem is printed here in full: two launches, the reconstructed fortnight, where divergence lies, increasing returns, checks of the explanation, what the review got wrong, lessons and the conclusion. Describe the two launches your course compares and a post-mortem follows at no cost.
Why not credit the campaign in MKT 838 Topic 2?
Both games had the same campaign and similar results until an unplanned streamer session pushed one over the chart threshold. The campaign cannot explain a difference between two identical campaigns.