| Course | MGT 820 Using Business Analytics for Competitive Advantage |
|---|---|
| Topic | Topic 4 |
| Paper type | Routines assessment |
| Length | About 1,030 words, 4 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for MGT 820 Topic 4
What a Rival Cannot License: Assessing the Routines a Restaurant Franchisor Built Around a Commercial Analytics Platform
[Author Name]
College of Doctoral Studies, Grand Canyon University
MGT-820: Using Business Analytics for Competitive Advantage
Topic 4 Assignment
[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.
What a Rival Cannot License: Assessing the Routines a Restaurant Franchisor Built Around a Commercial Analytics Platform
The Question and the Platform
Copperleaf Kitchen, a composite fast-casual franchisor with 340 restaurants, credits much of its recent growth to analytics. Four years ago it licensed a leading commercial analytics platform that combines point-of-sale data, location demographics and loyalty app activity. The question this assessment asks is whether Copperleaf's analytics capability would survive a competitor licensing the identical software.
The platform can be described in a paragraph because it is not where the answer lies. It stores transaction data from every restaurant, produces standard dashboards on sales, ticket size and daypart mix, scores potential sites with a demographic model and supports controlled tests of menu items across matched groups of stores. Every competitor of Copperleaf's size can license the same product, and two of its nearest rivals already have. Whatever distinguishes Copperleaf must lie in what it has built around the software.
Why Routines and Managerial Skill
Two literatures point to the same place. Mata et al. (1995) applied the resource-based view to information technology and concluded that capital, proprietary technology and technical skills are unlikely to sustain an advantage because they can be bought or copied, while managerial IT skills, the ability of managers to understand business needs and work with technical staff to apply technology to them, are the attribute most likely to do so. Nelson and Winter (1982) described routines as the organization's memory, patterns of action that store knowledge in practice rather than in documents, which makes them slow to build and hard to transfer. Feldman and Pentland (2003) added that routines have both a stable pattern and a performed part that adapts as people carry them out, so a routine is not simply a written procedure that can be copied.
Routine One: The Weekly Results Review
Every Tuesday, the eight franchise business consultants and three analysts meet for ninety minutes to read the previous week's results together. Consultants bring knowledge of particular franchisees and local events; analysts bring the data and its limits. The review produces a short list of restaurants where a consultant will visit with a specific question, such as why a store's dinner sales fell while its neighbors' rose. The routine took about two years to settle. In its first year the analysts presented and the consultants listened; the turning point came when consultants began bringing their own hypotheses to test. It depends heavily on one senior analyst, who designed the format and translates statistical caution into terms consultants accept. When she was on leave for six weeks last year, the meeting shortened and produced fewer visits.
Routine Two: The Site-Selection Argument
The platform scores every candidate site. Copperleaf's rule is that no site goes to the real estate committee on the score alone: the development manager and the regional franchise consultant must each write a one-page argument, one for and one against, that sets the score against local knowledge such as traffic patterns the model cannot see or a competitor's planned opening. The committee reads both. Of 46 sites approved over three years, 11 were approved against the model's ranking and 7 sites ranked highly were rejected. Copperleaf's new restaurants have reached their sales targets at a higher rate since the rule began, though other factors also changed. This routine took about eighteen months to form and depends less on individuals, because the written arguments are archived and new managers learn from them.
Routine Three: The Menu-Test Archive
Every menu test since the platform was licensed, 37 so far, is recorded in a short written file: the hypothesis, the stores, the result, what the team believed caused it and what it would do differently. New staff in the menu and marketing teams are expected to read the archive before proposing a test, and proposals must cite any earlier test on a related item. The archive prevents the firm from retesting ideas it has already rejected and records the causal judgments that the platform's statistics do not capture. It is the routine least dependent on any one person, since the memory is written, but it depends on the habit of consulting it, which the head of menu development enforces.
How Long a Rival Would Need
Table 1
Estimated Time for a Rival to Reproduce Each Routine, Illustrative
| Routine | Formation time at Copperleaf | Could hiring shorten it? | Estimate for a rival |
|---|---|---|---|
| Weekly results review | About two years | Partly: hiring an experienced analyst helps | 12 to 18 months |
| Site-selection argument | About 18 months | Little: depends on internal norms | 12 to 18 months |
| Menu-test archive | Four years of entries | No: past tests cannot be bought | Three to four years for comparable depth |
Table 1 estimates how long a determined competitor would need to reproduce each routine from scratch, separating what hiring could shorten from what only practice builds.
The Embedded Best Practice Objection
The platform's vendor argues that best practice now ships inside the product: built-in testing workflows, recommended dashboards and site-scoring defaults encode what leading firms have learned. The objection holds for reporting and test mechanics, which the product does standardize, and a rival adopting it would gain those quickly. It does not hold for the judgment exercised in the site arguments and the menu archive, which depends on Copperleaf's own restaurants, franchisees and history, and which no vendor can supply because it does not exist outside the firm.
Ranking the Routines
Ranked by durability, the menu-test archive comes first, the site-selection argument second and the weekly review third. The review is the most valuable day to day but the most fragile, because so much of it rests on one analyst. Its loss would matter more than its ranking suggests. The review is where consultants learn which questions the data can answer, and the site arguments and menu proposals they write draw on that learning. Without it, the other two routines would slowly become paperwork attached to the platform's scores, and Copperleaf's capability would come close to the platform alone, the one thing every rival can buy. Copperleaf should therefore document the review's format, pair the senior analyst with a successor, and treat the archive's upkeep as a standing duty rather than a habit.
References
Feldman, M. S., & Pentland, B. T. (2003). Reconceptualizing organizational routines as a source of flexibility and change. Administrative Science Quarterly, 48(1), 94-118. https://doi.org/10.2307/3556620
Mata, F. J., Fuerst, W. L., & Barney, J. B. (1995). Information technology and sustained competitive advantage: A resource-based analysis. MIS Quarterly, 19(4), 487-505. https://doi.org/10.2307/249630
Nelson, R. R., & Winter, S. G. (1982). An evolutionary theory of economic change. Belknap Press of Harvard University Press.
The MGT-820 Topic 4 assignment instructions
In Topic 4, MGT-820 asks doctoral learners to look past analytics technology to the organizational capability around it. The prompt assumes competitors can license the same software, so the question becomes what a firm has built that cannot be licensed. A paper meets the brief when it sets the platform aside early, identifies specific routines that a reader could observe, and examines how each formed, whom it depends on and what happens when those people leave. Learners should use the resource-based research on managerial IT skills and the evolutionary account of routines, estimate how long a rival would need to reproduce each routine and answer the vendor claim that best practice now comes inside the product.
How this MGT 820 Topic 4 example is built
The finished assessment spends little time on the platform and most of it on what surrounds it. It describes the licensed software in a paragraph and states that every competitor of comparable size could license the same product. Attention then moves to three routines: a standing review in which franchise consultants and analysts read results together, a site-selection process where model scores must be argued against local knowledge, and a written record of past menu tests that new staff consult before proposing another. Each routine is examined for how long it took to form and whether it depends on particular people. The paper draws on Mata, Fuerst and Barney's resource-based finding that managerial IT skills, not technology, are the attribute most likely to sustain an advantage, and on Nelson and Winter's account of routines as organizational memory.
Where the marks sit in the MGT 820 Topic 4 rubric
An Excellent assessment earns credit by describing routines, not culture. The rubric rewards papers that follow each routine from input to decision, name the roles involved and test what happens when a key person is absent, as the six-week leave in the example shows. Faculty look for Mata, Fuerst and Barney cited for managerial skill rather than technology, and Nelson and Winter for routines as memory. Strong papers separate what hiring could shorten from what only practice builds when estimating a rival's timeline. The vendor objection should be granted for workflows and rejected for judgment. Top marks go to a ranking by durability that names the routine whose loss would hurt most.
MGT 820 Topic 4 help: mistakes that cost marks
Where this assessment goes wrong, it usually turns into a platform review. Comparing feature lists, dashboards and cloud architecture examines the one component every competitor can buy, and faculty in many sections treat that as missing the topic. A related loss comes from naming people and process in general terms, a data-literate culture or strong leadership, without describing a single routine a reader could observe. Papers rarely ask what happens when the analyst who runs the review leaves, which is where a capability either proves organizational or turns out to be personal. Citing the resource-based literature for claims about software rather than managerial skill inverts Mata, Fuerst and Barney's conclusion. The objection is often left out, and the vendor argument that process now comes packaged is the one a practitioner reader would raise first.
Get an MGT-820 Topic 4 example written to your instructions
Send the MGT-820 Topic 4 instructions, the rubric from your classroom and the organization or case your section is analyzing. We write a custom example to those criteria, with the platform set aside, specific routines examined for formation time and dependence on individuals, and the embedded-practice objection answered, in 24 to 48 hours. Your first one is free.
More MGT 820 papers and DBA samples
- MGT 820 Topic 1: Analytics Advantage Thesis
- MGT 820 Topic 2: Data Asset Inimitability Analysis
- MGT 820 Topic 3: Analytics Decision Rights Map
- MGT 820 Topic 5: Rival Imitation Timeline
- MGT 820 Topic 6: Reporting Gain Dq Response
- MGT 820 Topic 7: Decision Anchored Business Case
- MGT 820 Topic 8: Advantage Durability Assessment
- MGT 825 Topic 4: Routine Decision Exposure Brief
- MGT 805 Topic 4: Matrix Strain Analysis
- MGT 830 Topic 4: Systems Archetype Analysis
- DBA 965 Topic 4: Unsettled Questions Section
MGT 820 Topic 4 questions, answered
Why focus on routines rather than technology?
Because technology is sold on the same terms to every firm that can pay, while routines form through practice inside one organization and resist quick copying. Nelson and Winter described routines as a kind of organizational memory, which is the property the example leans on. A rival can buy the franchisor's software this quarter; reproducing the way its consultants and analysts argue over results takes much longer.
What did Mata, Fuerst and Barney find?
Applying resource-based reasoning to information technology, they concluded that managerial IT skills, the ability to align technology with business needs and work across functions, were the attribute most likely to produce a sustained advantage, while capital, proprietary technology and technical skills were more easily matched. The example cites them for that conclusion only and extends it to analytics by argument.
Can a capability be too dependent on one person?
Yes, and it is a common finding. When one analyst holds the relationships and judgment that make a review work, the capability leaves when that person does, possibly for a competitor. The example tests each routine for that dependence and treats documented, shared practice as more durable than individual expertise, while noting that some tacit judgment never transfers fully to a written record.
Where can I find a free MGT 820 Topic 4 sample paper?
The franchisor routines assessment appears here in full: the question, the platform paragraph, the framework, three routines, the rival timeline table, the vendor objection and the durability ranking. Describe the organization and its software and a free assessment can be prepared.
Which routine is most fragile in MGT 820 Topic 4?
The weekly results review. It is the most valuable day to day but depends on one senior analyst, and when she was on leave for six weeks the meeting shortened and produced fewer restaurant visits.