For students, self-learners and teaching teams

A framework for learning the bricks of business development

Business development is a wide field assembled from several disciplines, and a learner meeting it concept by concept has to infer the relationships between them. That inference is the hard part, and it is where self-study most often stalls. The Omnigoal offers a map to hold the concepts before they arrive — what educational psychology calls an advance organiser — so that each new idea has somewhere to attach rather than having to be filed provisionally.

Made for
Students, career changers, teams onboarding
Works for
Self-study, course design, study groups
Pace
One core per week, or one object per day

The problem

Why this is harder than it looks

01

Concepts arrive without their relationships

A learner can define a value proposition and a brand promise and still not see how one constrains the other. Definitions accumulate faster than the structure connecting them, and structure is what holds when a real decision has to be made.

02

No way to tell what is still missing

Without a map of the territory, it is difficult to judge whether you know most of a field or a corner of it. Confidence and coverage then drift apart, usually in the less helpful direction.

03

Recognition is mistaken for understanding

Reading about a concept produces a strong feeling of familiarity that reliably outruns the ability to use it. It is one of the better documented effects in learning research, and it makes self-assessment unusually unreliable.

The method

How to work through the field

Seven habits. Each one corresponds to something reasonably well established about how people learn structured material.

  1. 01

    Learn the map before the detail

    Spend the first session on the eight cores alone — what each covers and where its boundaries lie. This is deliberately an advance organiser in Ausubel’s sense: a structure introduced ahead of the material so that later concepts can be attached rather than merely accumulated.

    • Aim to name all eight cores and say what each is responsible for.
    • Leave the objects until later; the map first, the territory after.
  2. 02

    Take one core at a time

    Depth before breadth at the start. Work through a single core’s objects until you can explain the whole core without notes, then move on. Studying across cores at random tends to exceed what can be held at once, which is the practical import of cognitive load research.

    • A week per core is comfortable; a day per object is intensive.
    • Finish a core before starting the next, even when another looks more interesting.
  3. 03

    Ask the same four questions of every object

    Consistency is what makes knowledge comparable across a field. For each object ask what it is, what decision it drives, what would go wrong without it, and what it constrains elsewhere. The four move deliberately up Bloom’s levels, from recall to analysis, and the fourth is where understanding rather than recognition is built.

    • What is it, in one sentence and without jargon?
    • What decision does it drive, and who takes that decision?
    • What breaks if it is absent?
    • Which object in another core does it constrain?
  4. 04

    Anchor everything to one real company

    Choose a company you can research and keep it for the whole curriculum. Fill in each object with what that company actually does. Concepts learned against a concrete case transfer better than concepts learned in the abstract, and the blanks show you what cannot be seen from outside a firm — which is itself worth knowing.

    • Prefer a company with public material; annual reports carry a great deal.
    • Keep the same company throughout, so the cores begin to connect.
  5. 05

    Trace the correlations

    The framework’s substance is in the relationships: a change to positioning in the Brand Core bears on channels in the Market Core and on the journey in the Omni Core. Tracing those chains deliberately is close to what concept mapping does, and it is the step that turns a list of parts into an understanding of a system.

    • For any object, name one object in another core that it constrains.
    • Trace a single change through three cores. That exercise teaches more than a chapter.
  6. 06

    Explain it to someone else

    Explain each finished core aloud, without notes. The points at which you hesitate are the objects you have recognised but not understood. Retrieval and explanation are among the better evidenced study techniques, and both are more useful than rereading.

    • Explain aloud rather than in writing; writing lets gaps be edited over.
    • Return to any object you could not explain cleanly.
  7. 07

    Return to the map periodically

    Re-read the eight cores every few months with everything learned since. The map does not change; what you see in it does. Spacing the returns rather than massing the study is well supported, and it is also how the framework describes knowledge working — through repeated cycles rather than a single pass.

    • Keep notes per object, so you can see your own understanding change.
    • Redo the four questions on any object that has come up in real work.

Take this with you

An eight-week study plan

One core per week, ordered so each builds on the last. Roughly three to five hours a week.

Week 1 — Goal Core
Purpose, and the distinction between strategic, tactical, long and short term goals.
Week 2 — Vision Core
Vision and mission, and how they constrain rather than decorate.
Week 3 — Market Core
Audience, competitors, opportunity, channels and the customer journey.
Week 4 — Brand Core
Promise, identity, positioning, value, perception and narrative, kept distinct.
Week 5 — Business Core
The largest core, at twelve objects: value proposition, monetisation, finance, HR, competencies, assets, systems, manufacturing, supply chain, partners, stakeholders and compliance.
Week 6 — Omni Core
Journey mapping, feedback, support, UX and channel integration.
Week 7 — Data Core
KPIs, collection, analysis, reporting and governance.
Week 8 — Time Core
Project management, market timing, golden opportunities, contingency planning and the year wheel.

In week nine, return to week one. Rereading the Goal Core after seeing all eight is the point at which the framework stops reading as a list and starts reading as a system.

Standing on other work

What the method rests on

The study habits here are not particular to this framework. They are ordinary findings from learning research, applied to a field that happens to have a map.

Advance organisers

Learning the eight cores first

Ausubel’s finding that a structure introduced before the material improves how well later concepts are retained and connected.

Cognitive load

One core at a time

Sweller’s work on the limits of what can be held at once, and why breadth-first study of an unfamiliar field tends to fail.

Bloom’s taxonomy

The four questions per object

The questions move from recall through application to analysis, which is why the fourth is the difficult one.

Concept mapping

Tracing correlations between cores

Novak’s method for representing relationships between concepts rather than the concepts alone.

Retrieval practice and spacing

Teach-back and the quarterly return

Two of the better evidenced study techniques, and both more effective than rereading.

The fluency illusion

Why explanation is the test

Familiarity from reading reliably outruns the ability to use a concept, which makes self-assessment by recognition unreliable.

The framework contributes the map; the learning research contributes the method. Neither is doing the other’s work, and the combination is more useful than either alone.

Where it lives in the framework

How each core contributes

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.

Checklist

Signs a core has been learned

  • You can name its objects without notes.
  • You can say, for each object, what decision it drives.
  • You can say what breaks in a business if the object is absent.
  • You can name an object in another core that it constrains.
  • You have filled it in for one real company.
  • You can explain the whole core aloud to someone else.

In fairness

What this will not teach you

A map is a good beginning and a poor ending. These are the parts it does not cover.

  • Knowing the map is not the same as being able to use it. Application is where the learning actually happens, and it happens elsewhere.
  • The object list is a convention rather than a complete inventory of business knowledge. Organisational behaviour, innovation management, economics and finance all run considerably deeper than their place here suggests.
  • It offers structure, not judgement. Judgement comes from cases, from practice, and from being wrong where others can see it.
  • It is not a substitute for the primary literature. Where an object interests you, the underlying discipline has decades of work behind it.
  • A framework can make a field feel more settled than it is. Much of what is summarised in a line here is genuinely contested.

Questions

Frequently asked

The questions people ask most often about learning and The Omnigoal.

How do I learn business development from scratch?

Learn the structure of the field before its details. Start with the eight cores so you know what the territory contains, then work through one core at a time, asking the same four questions of every object: what it is, what decision it drives, what breaks without it, and what it constrains elsewhere. Anchor everything to one real company and keep that company throughout, so the cores begin to connect rather than accumulate.

What are the building blocks of business development?

In The Omnigoal they are the eight cores — Goal, Business, Brand, Vision, Market, Data, Omni and Time — and the objects within them, such as value proposition, brand positioning, target audience, KPI management and market timing. Around fifty objects in total, which makes the field finite enough to work through. The set is a convention rather than a definitive inventory, and other divisions are equally defensible.

How long does it take?

The map itself takes about an hour. A working command of all eight cores takes roughly eight weeks at three to five hours a week, one core per week. Fluency — being able to trace a change through three cores — comes from applying it to real decisions rather than from additional study, which is the usual finding for structured material.

Which core should I start with?

The Goal Core, since purpose and goal hierarchies underpin the others. The Vision Core makes a good second: it is small and foundational, and completing it early means finishing something before reaching the considerably larger Business Core.

Can this be used to teach or to onboard a team?

Yes. The framework is published under a Creative Commons Attribution 4.0 licence, so it can be used, taught, adapted and built on with attribution, including in course material and slides. The eight-week plan works as a course outline and the four questions work as a discussion structure for a study group or an onboarding programme. Renaming cores or dropping ones that do not fit your context is explicitly invited.

Is this a substitute for a business education?

No. It is a map of a field, and a map is a way of orienting rather than a body of knowledge. Each object here summarises a discipline with substantial literature behind it, much of it genuinely contested. The framework can make that literature easier to navigate and harder to get lost in; it cannot stand in for reading it.