For students, project groups and supervisors
Academic business projects are usually assessed less on what was found than on whether the choices behind it can be defended: why this scope, why this method, why these theories. The Omnigoal offers a map of a company organised along the same four levels a methodology chapter already has to move through — ontology, epistemology, methodology, methods — so scope and delimitation become arguments you can make rather than positions you have to concede.
The problem
A case company has hundreds of moving parts, and a project has to leave most of them out. When the map of the whole is never drawn, what stays in tends to be whatever the group found first — a defensible narrowing done for an indefensible reason.
Method sections are often written to satisfy a requirement rather than to justify the work that follows. The chapter names a paradigm, the analysis proceeds without reference to it, and the examiner notices the gap before the student does.
Analysis in one chapter and recommendations in another are frequently connected only by the author’s intent. Without a structure that names the part of the business a finding concerns, the link stays implicit — and implicit links are what get questioned at the defence.
The method
Six steps. The order matters, because each one produces the material the next one argues from.
Place what you already know about the company on the eight cores and their objects. Write in note form, one line per object you can say something about, and leave the rest deliberately blank. The purpose is not to produce text but to produce a visible account of what you know and what you do not.
A problem statement that names an object is easier to research and easier to assess than one that names a topic. “How does the firm’s content calendar in the Market Core relate to the seasonality of its sales channels?” is answerable; “digital marketing at the firm” is not. Check that data is obtainable before you commit — an elegant question with no accessible evidence is a long semester.
Delimitation is a claim about relevance, so it reads better as a list of decisions than as an apology. Naming the cores you exclude, with a reason for each — inaccessible data, no bearing on the question, insufficient scope — turns an omission into a defensible choice. It also gives you a ready answer to the question examiners reliably ask.
The framework has no grouping above the eight cores, and does not need one. But for a methodology chapter it helps to read them in four clusters, because they fall into the same sequence such a chapter moves through — ontology, epistemology, methodology, methods — which is the hierarchy set out by Crotty and popularised through Saunders’ research onion. That correspondence gives you a structure for the chapter that is already connected to the analysis, rather than sitting in front of it.
Different objects call for different evidence: Target Audience rewards interviews, KPI management rewards figures, Brand Perception usually needs both. Choosing method object by object is what produces a genuine mixed-methods design — and it has a paradigm behind it, since pragmatism is the position under which combining qualitative and quantitative evidence is coherent rather than merely convenient.
Give each analysed object its own section with a consistent internal shape — what the theory holds, what the evidence shows, what the gap is — and end each with the finding in a single sentence. Recommendations then attach to the object they concern, which makes the chain from evidence to advice visible instead of assumed.
Take this with you
The map converts fairly directly into a report structure. This is one defensible outline among several, not a required form.
For supervisors, the same table works as a review sheet: a chapter that cannot be placed on the map is usually a chapter whose role in the argument has not yet been settled.
Standing on other work
The Omnigoal does not replace the instruments you are expected to use. It gives them a shared address, so a reader can see why each one appears where it does.
Across all eight cores
Ontology, epistemology, methodology and methods line up with the Goal Core; Business, Brand and Vision; Market and Time; and Data and Omni. The clusters are a reading aid for the chapter, not a level in the framework.
Market Core, with Compliance in the Business Core
Macro conditions belong to the environment the firm reads, not to the firm itself.
Market Core — Competitors, Market Opportunities
An industry-level instrument; it says nothing about internal capability, which is why it needs a companion.
Business Core — Core Competencies, Business Assets
Barney’s inside-out counterpart to Porter’s outside-in analysis.
Spans Business Core and Market Core
Osterwalder’s canvas describes a model; the cores show what the canvas leaves untouched.
Market Core and Brand Core
Kotler’s STP divides cleanly: segmentation and targeting outward, positioning as a brand decision.
Data Core, anchored in the Goal Core
Kaplan and Norton’s perspectives are a way of populating KPI management against stated goals.
A synthesis across cores
Most defensible when each entry is tagged with the core and object it came from, so the analysis behind it is traceable.
Naming where an instrument sits is also a way of naming its limits. A reader who can see that Five Forces occupies one core can see immediately what the analysis has not yet covered.
Where it lives in the framework
The Omnigoal is holistic: all eight cores are in play here, each supplying something the others cannot. Follow any of them to see the objects it contains.
Ontology in the framework’s own terms: what the firm holds itself to exist for. Also where your project’s own purpose belongs.
Learn the core
Vision and mission as primary documents — stated positions you can compare against observed behaviour.
Learn the core
The outward-facing analysis: opportunities, competitors, target audience, channels and journey.
Learn the core
Promise, positioning, perception and narrative — often the richest material in a communication or marketing project.
Learn the core
Operations, resources, value proposition and finance, where most case analysis in fact takes place.
Learn the core
Touchpoints and journey mapping, where students can most realistically gather primary data first-hand.
Learn the core
KPIs and performance evidence — the difference between a claim and a documented finding.
Learn the core
Market timing and contingency in the case, and your own project plan and hand-in dates.
Learn the coreChecklist
In fairness
Worth stating in your own methodology chapter, because a framework used with its limits acknowledged is harder to argue with than one presented as complete.
Questions
The questions people ask most often about school projects and The Omnigoal.
One that covers the whole firm, so that narrowing is a decision you make rather than an accident, and that can be connected to your methodology rather than sitting apart from it. The Omnigoal’s four core groups follow the ontology–epistemology–methodology–methods hierarchy familiar from Crotty and from Saunders’ research onion, which lets the framework do work in the method chapter as well as the analysis.
State which cores the project covers and which it excludes, and give each exclusion its own reason — data inaccessible, no bearing on the problem statement, beyond the scope of a single semester. A delimitation written as a set of separate decisions is considerably easier to defend than one written as a single apology, and it gives you a prepared answer to the question examiners most reliably ask.
That is the intended use. The framework is an organising layer, not a competitor: Five Forces and PESTEL sit in the Market Core, VRIO in the Business Core, the Business Model Canvas across Business and Market, STP across Market and Brand. Placing each instrument also makes visible what it does not reach, which is often the more useful observation.
The framework states its own position — systemic ontology, iterative epistemology, mixed-methods methodology, methods chosen per task — and organises the cores along those same four levels. It also names the three perspectives it moves between: relationships (systems theory), objectivity (critical rationalism, positivism) and subjectivity (phenomenology, hermeneutics), held together pragmatically. You can adopt that position, or argue against it; both make for a stronger chapter than a paradigm named and then not used.
The written model and its diagrams are published under a Creative Commons Attribution 4.0 licence, so it can be cited, reproduced and adapted with attribution to Andreas Baggesen and a link to the licence. Where you describe the reasoning in your own words the attribution is a courtesy rather than a requirement, but naming it is what lets a reader trace it back and read it in full.
Frameworks are ordinarily accepted as organising structures rather than as evidence, and are judged on whether their limits are acknowledged and their use is consistent. Stating plainly that The Omnigoal is descriptive rather than predictive, and that its core boundaries are conventions, tends to strengthen a project rather than weaken it. Requirements differ by institution, so check the assessment criteria for your programme.
