| Course | MGT 830 Management of Business Complexity |
|---|---|
| Topic | Topic 1 |
| Paper type | Framework comparison paper |
| Length | About 1,060 words, 4 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for MGT 830 Topic 1
Complicated or Complex, and Does the Label Change the Next Move? Comparing Cynefin, Wicked Problems and Perrow's Grid on Four Problems at a Hotel Group
[Author Name]
College of Doctoral Studies, Grand Canyon University
MGT-830: Management of Business Complexity
Topic 1 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.
Complicated or Complex, and Does the Label Change the Next Move? Comparing Cynefin, Wicked Problems and Perrow's Grid on Four Problems at a Hotel Group
The Managerial Question
Managers are often told that some problems are complex rather than merely complicated. The distinction matters only if it changes what a manager does next. This paper compares three frameworks that draw the line in different ways, the Cynefin framework, the wicked-problem tradition and Perrow's grid of interactive complexity and coupling, by applying each to the same four open problems at Saltgrass Hospitality, a composite group of 46 hotels. The question is not what complexity is in general but whether classifying a problem with each framework would change the group's next action.
Three Frameworks in Brief
Snowden and Boone (2007) describe the Cynefin framework, which sorts situations into domains. In complicated situations, cause and effect can be worked out in advance by experts, so the right response is to sense, analyze and respond. In complex situations, cause and effect become clear only looking back, so the right response is to probe with safe experiments, sense what happens and respond by amplifying what works. Each domain carries its own response.
Rittel and Webber (1973) described wicked problems in social planning as problems with no definitive formulation, no stopping rule and no true-or-false solutions, only better or worse ones, where every attempted solution changes the problem. Their tests are useful because they can be observed: a team can check whether it agrees on what the problem is and whether it can say when the problem would be solved.
Perrow (1984), studying industrial accidents, classified systems by two properties. Interactive complexity means components can interact in unexpected ways that are hard to see; tight coupling means one failure spreads quickly with little slack. Systems high on both, he argued, will eventually have accidents however well they are managed. His properties can also be checked before anyone knows how an intervention will turn out.
Four Problems, Three Classifications
Table 1
Four Saltgrass Problems Classified by Each Framework
| Problem | Cynefin | Wicked-problem tests | Perrow's grid |
|---|---|---|---|
| Replacing the reservation system | Complicated: vendors and experts can specify it | Not wicked: agreed definition, clear finish | Linear interactions, tight coupling at cutover |
| Retrofitting chiller plants | Complicated: engineering analysis settles it | Not wicked | Linear, loosely coupled |
| Guest review scores falling across properties | Complex: causes differ by property and shift over time | Wicked: no agreed definition, no finish line | Interactive, loosely coupled |
| Front-desk turnover | Complex | Partly wicked: definition disputed, finish unclear | Interactive, loosely coupled |
Table 1 applies each framework to Saltgrass's four problems. The disagreements are the point of the comparison.
A Complex Problem Handled as Complicated
The review-score problem shows why classification matters. When scores fell, Saltgrass bought a service playbook from a consultancy and rolled it out to every property with training and checklists. That is a complicated-domain response: analyze, specify the best practice and implement it. Scores fell further at several properties. Interviews suggested why: the causes differed by property, including renovation noise at some, staffing shortages at others and a new online travel agency's review prompts at a few, and the playbook's checklist added work for already thin front-desk teams. A complex-domain response would have started with small probes at a few properties, watched what changed and expanded what worked.
The three frameworks agree on this problem, which is reassuring. The reservation system is where they diverge in a useful way: Cynefin and the wicked-problem tests treat it as expert-knowable, while Perrow's grid warns that the cutover weekend is tightly coupled, so a failure in one interface could spread to every property at once. That warning changes the plan, adding a parallel run and a rollback, without changing the domain.
The Other Two Problems
The chiller retrofit is the easiest case and a useful control. All three frameworks classify it as expert-knowable and loosely coupled: engineers can calculate loads, compare equipment and sequence the work hotel by hotel, and a delay at one property does not spread to others. Saltgrass handled it as a complicated problem, with a consulting engineer's study and a phased plan, and the retrofits are on schedule and within budget. The frameworks would not have changed anything, which is what a good classification should show for a problem already handled well.
Front-desk turnover is harder. Cynefin places it in the complex domain, since the reasons agents leave interact with scheduling, local wages, guest behavior and managers' styles in ways that differ by property. The wicked-problem tests give a mixed result: the group disagrees about whether the problem is pay, scheduling or the job itself, which suggests no definitive formulation, but it can name a stopping point, turnover back below its pre-2020 level. That partial result is informative. It suggests running a few small experiments on the disputed causes while measuring progress against the agreed target, a combination neither framework alone would prescribe.
The Circularity Objection
The strongest objection to Cynefin is that it is an unvalidated consulting heuristic whose classifications are circular. A problem is called complex after analysis fails, and analysis fails because the problem is complex. The objection is fair. Cynefin is a sensemaking framework, not a tested theory, and nothing in it tells a manager in advance which domain a problem belongs to.
The answer is to fix the classification test before any outcome is observed, and the other two frameworks supply such tests. Rittel and Webber's questions, whether the team agrees on the problem's definition and can say when it would be solved, and Perrow's properties of interactive complexity and coupling can be checked at the start. Had Saltgrass applied them to the review-score problem, it would have found no agreed definition and strong interaction among causes before buying the playbook.
Verdict
Each framework earns a different job. Cynefin is the most useful for choosing a response, because each domain carries one, and the response is what managers need. It is weakest at classification, where it offers labels without tests. The wicked-problem tradition and Perrow's grid supply the tests: observable signs, checked before acting, that analysis alone will not settle a problem or that a failure could spread. Saltgrass should classify its problems with the structural tests first and then use Cynefin to choose what to do, which would have kept the reservation system on an expert plan with a rollback and sent the review-score problem to small experiments at a handful of properties.
References
Perrow, C. (1984). Normal accidents: Living with high-risk technologies. Basic Books.
Rittel, H. W. J., & Webber, M. M. (1973). Dilemmas in a general theory of planning. Policy Sciences, 4(2), 155-169. https://doi.org/10.1007/BF01405730
Snowden, D. J., & Boone, M. E. (2007). A leader's framework for decision making. Harvard Business Review, 85(11), 68-76.
Reading the GCU MGT 830 Topic 1 instructions
Topic 1 in MGT-830 asks doctoral learners to distinguish complicated from complex problems and to show why the distinction matters for management. Defining complexity in general is not the task. A paper meets the brief when it compares frameworks on the same concrete problems, makes their disagreements visible and asks whether each classification would change the next action. Learners should state each framework's central distinction accurately, avoid attributing empirical validation to Cynefin, cite Perrow for interactive complexity combined with tight coupling, and answer the objection that a problem is called complex only after analysis fails. The verdict should say which framework does which job rather than crowning one, and should apply that division of labor to the case.
How this MGT 830 Topic 1 example is built
What the reader receives is a comparison table followed by an argued verdict. Four items from the composite hotel group's operating agenda supply the test material: replacing the reservation system, retrofitting chiller plants, guest review scores falling across properties, and front-desk turnover. Each framework is applied to all four. Snowden and Boone's Cynefin framework separates complicated problems, where an expert can work out cause and effect in advance, from complex ones, where cause and effect become clear only in retrospect. Rittel and Webber's wicked problems have no definitive formulation and no stopping rule. Perrow sorts systems by interactive complexity and tight coupling. The verdict favors Cynefin for choosing a response, since each domain carries one, and borrows the observable tests of the other two so that its classification step can be checked rather than asserted.
MGT 830 Topic 1 rubric: what Excellent looks like
The rubric rewards a comparison in which every framework meets the same problems. An Excellent paper summarizes Cynefin, wicked problems and Perrow's grid briefly and accurately, then classifies each of the four hotel problems with all three in one table. Credit goes to an example of misclassification with consequences, here the playbook applied to falling review scores. Faculty look for the paper to notice where the frameworks diverge, such as Perrow's warning about the tightly coupled cutover. Strong papers grant the circularity objection and answer it by fixing structural tests before outcomes are known. Top marks go to a verdict assigning classification to the structural tests and the choice of response to Cynefin.
Common MGT 830 Topic 1 mistakes, and how to avoid them
The commonest casualty in this comparison is a paper that summarizes three frameworks and never applies them to the same problem, so the reader cannot see where they disagree. A close second classifies every item on the hotel agenda as complex, which erases the very distinction the comparison is built on and leaves the reservation system, an expert-knowable project, with no plan at all. Some papers borrow the Cynefin vocabulary and then recommend a detailed rollout for the review-score problem, a linear answer to a situation the paper itself called complex. Attributing statistics or empirical validation to Cynefin overstates what is a sensemaking framework. Perrow is sometimes cited for complexity in general, when his argument concerns interactive complexity combined with tight coupling. Without the circularity objection, the verdict has never been tested.
Get an MGT-830 Topic 1 example written to your instructions
Send the MGT-830 Topic 1 instructions and the rubric from your classroom, with any frameworks or cases your section assigned. We write a custom example to those criteria, with the frameworks applied to shared problems, the classification made checkable and the circularity objection answered, in 24 to 48 hours. The first one is free.
More MGT 830 papers and DBA samples
- MGT 830 Topic 2: Causal Loop Analysis
- MGT 830 Topic 3: Backfire Case Critique
- MGT 830 Topic 4: Systems Archetype Analysis
- MGT 830 Topic 5: Incremental Action Dq Post
- MGT 830 Topic 6: Safe-to-fail Experiment Design
- MGT 830 Topic 7: Reversible Reorganization Proposal
- MGT 830 Topic 8: Planning Under Uncertainty Position Paper
- MGT 825 Topic 1: Exposure Triage Paper
- MGT 820 Topic 1: Analytics Advantage Thesis
- MGT 805 Topic 1: Structural Trade-off Essay
MGT 830 Topic 1 questions, answered
How does Cynefin separate complicated from complex problems?
In Snowden and Boone's account, a complicated problem has cause and effect that an expert can work out in advance, so good practice exists and analysis pays. In a complex problem the relationship can be seen only looking back, because people in the system respond to each other and to whatever the manager does. The practical difference is the response: analyze first for the former, probe first for the latter.
What are wicked problems, and why include them?
Horst Rittel and Melvin Webber described wicked problems in planning as those with no definitive formulation, no stopping rule, and solutions that are better or worse rather than true or false. Their argument predates Cynefin and was aimed at public planning. The example uses those properties as tests a manager can check, not as a separate category, which is how it avoids calling every problem complex.
Is Cynefin a validated theory?
It is better described as a sensemaking framework developed in practice, which is how the example uses it. Empirical tests of its domain boundaries are limited, and a doctoral paper should not attribute findings to it that no study reported. Its value in the example is practical, linking each kind of problem to a different response, while the classification itself rests on observable structural tests borrowed from the other two frameworks.
Where can I find a free MGT 830 Topic 1 sample paper?
The hotel group framework comparison is on this page in full: the managerial question, the three frameworks, the classification table, the playbook case, the other two problems, the circularity objection and the verdict. Name the organization in your prompt and a free comparison can be built on its problems.
Which framework wins in MGT 830 Topic 1?
None alone. Cynefin is best for choosing a response, since each domain carries one, while the wicked-problem tests and Perrow's grid supply observable ways to classify a problem before anyone knows how an intervention will turn out.