KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesTheoretical Perspective and Philosophical FrameworkProject Delivery · Research ProjectsLesson 16/50← PrevNext →
GuidePublished 16 Aug 202612 min readBy KEVOS Editorialtheoretical perspectivephilosophical frameworkresearch paradigmepistemological assumptions
On this page

Ask about this page

KEVOS AITheoretical Perspective and Philosophical Framework

KEVOS knowledge first · trusted web sources when needed

KEVOS/Project Delivery/Research Projects/Introduction to Research Methods
Project DeliveryResearch ProjectsCoreResearch Philosophy

Theoretical Perspective and Philosophical Framework

Between the assumptions you arrive with and the data you eventually collect sits a layer most project studies never name. Naming it is what makes a methodology defensible rather than merely conventional.

Reading time14 minutes
LevelCore
Topic streamResearch Philosophy
Source materialIntroduction to Research Methods
Updated2026-08-16

In brief

  • The source defines the theoretical perspective in six words: the philosophical framework informing the methodology.
  • Its function is to carry assumptions. Ontological and epistemological assumptions are described as embedded in the theoretical perspective, which is embedded in the methodology.
  • The source makes a strong claim about your workplace — that the framework a project adopts reflects the organisational context in which it is undertaken — and never evidences or qualifies it.
  • There is no map from the eight philosophies at the base of the pyramid to the fourteen methodologies above them. That argument is yours to build.
  • Declaring no perspective does not give you none. It gives you an unexamined one, usually inherited from whatever instrument you borrowed.

The layer the source names

From the source

The definitions, as supplied

Theoretical perspective — "The philosophical framework informing the methodology."

Epistemology — "The theory of knowing; embedded in the theoretical perspective and thus in the methodology."

Ontology — "Assumptions about the nature of being: embedded in the theoretical perspective and thus in the methodology."

And from the Week 2 prose: "The epistemological and ontological assumptions are embedded in the theoretical perspective deployed in the research, and this is embedded in the research methodology used in the study."

Two of the five elements are defined by reference to this one. That is unusual and it is the point: the theoretical perspective is not a topic sitting beside ontology and epistemology, it is the container that carries them into the design. All five elements are set out at the five basic elements of a research project.

For a practising project manager, the useful reading is functional. The theoretical perspective is the layer where a private assumption becomes a public commitment that a reader can check against your methods.

Two glosses in the same week's material

The supplied source contains two terminology tables that define the surrounding terms differently. Both are in the material; neither is marked as superseding the other.

THE SAME TERMS, TWO SETS OF WORDS

TermFirst tableSecond table
OntologyAssumptions about the nature of being, embedded in the theoretical perspective and thus in the methodologyWays of looking at work — associated terms: paradigm, philosophy
EpistemologyThe theory of knowing, embedded in the theoretical perspective and thus in the methodologyRelationship between researcher and topic being researched
MethodsThe way in which the data to be used in the study is gatheredWays of gathering and analysing data — associated term: techniques

The second table's gloss of epistemology as a relationship is materially different from the first's theory of knowing. Both appear in the same week's teaching.

Source gap

Present both, choose one, say which

The source never reconciles the two glosses, so a page or a chapter that quotes only one is quietly editing the material. Quote both, then state which you are working from and why.

The difference is not cosmetic. If epistemology is the theory of knowing, your methodology chapter argues about the status of knowledge. If it is the relationship between researcher and topic, that chapter has to describe you — your access, your role in the setting, your distance from the people you studied. The second reading demands a paragraph the first does not, and it is the reading that forces a project manager researching their own workplace to describe their position in it. Both terms have their own treatment in this library, beginning with epistemology: how knowledge is created.

The embedding chain, and where it goes quiet

The source's figure and its prose agree on the ordering: philosophy sits underneath everything, methodology sits on top of philosophy, and methods sit on top of methodology. Assumptions travel upwards through the layers into the instrument you eventually hand to a participant.

  1. Ontological and epistemological assumptions
  2. Theoretical perspective
  3. Methodology
  4. Methods
  5. Data
  6. Claims

Run the chain downwards and it becomes an audit. Take a claim from your draft conclusions, and ask which data supports it, which method produced that data, which methodology selected that method, and which perspective made that methodology the right choice. A break anywhere in that line is a finding you cannot defend. The figure itself is unpacked at the methodological pyramid.

8philosophies named at the base of the pyramid
14methodologies named in the middle tier
13data collection methods named at the apex
0mappings the source gives between the tiers
Source gap

The chain has no wiring diagram

Thirty-five labels are arranged in three tiers and not one line is drawn between them. The supplied source never says that a positivist perspective requires an experiment, or that an interpretive perspective rules out a survey.

That silence is a limitation of the material, not a licence. It means the fit between your perspective and your methodology is an argument you must construct and cite, and it is precisely the argument an examiner or a sponsor's technical reviewer will test first.

The organisational-context claim

From the source

The claim, in the source's own words

"Every research project is situated within a particular philosophical framework. The philosophical framework adopted by the research project reflects the organisational context in which it is undertaken."

"Every aspect of the research project, as it is developed by the researcher, should 'fit' with the philosophical framework within the organisation in which the research project is situated."

This is the most distinctive claim in the philosophical material, and it is the one that speaks directly to a project manager researching inside their own workplace. It also carries two quite different readings, and the source does not tell you which it intends.

Read as a description

  • Organisations already hold assumptions about what counts as evidence
  • A firm that decides by dashboard has an operating epistemology, whether or not anyone names it
  • Your study inherits that context whether you engage with it or not
  • Useful consequence: name the context in your methodology so the reader can see what you were working within

Read as an instruction

  • Your design should conform to the framework of the host organisation
  • A study whose evidence the organisation cannot recognise will not be acted on
  • Useful consequence: check early which forms of evidence your sponsor will accept
  • Risk: taken literally, this forecloses any position critical of the organisation's own arrangements
Caution

Where the instruction reading collides with a position

One of the epistemological positions in the same material is defined by beliefs and values critical of the status quo. Requiring every aspect of a project to fit the organisation's own framework sits badly with a position designed to question it, and the source does not address the collision.

Handle it in scope and ethics rather than in philosophy — agree the question and the reporting arrangements before collection, and record the tension as a stated limitation rather than resolving it by softening the question.

Choosing the perspective you will declare

The source lists the positions but gives no selection rule. The decision aid below routes you by the shape of your question to the page that treats each position properly — this page deliberately does not restate them.

Route by the shape of your question

IfYou have a prior proposition, a measure that can be applied identically to every case, and a population you can define
ThenRead positivism and post-positivism — and note which of the two your sampling will actually support
IfYour question is about how people understand a thing, and you expect several defensible views of it
ThenRead constructionism and constructivism, including the naming inconsistency you will have to handle in your own prose
IfYour question is about how people explain a situation or account for a behaviour
ThenRead interpretivism and phenomenology, and check what the six associated traditions do and do not give you
IfYour question is about who an arrangement works for and who carries its costs
ThenRead critical inquiry and standpoint research, then settle the scope with your sponsor before collection
IfNone of the four fits cleanly, or two seem to fit equally
ThenDo not average them. Follow the source's own advice on methodology choice — read significant papers in your field, see what perspective they declare, and take advice from your supervisor

The four fit tests the source does give

The material is thin on selection but explicit on fit. It states that every step in the research project should be appropriate to the nature of the study, the aim of the study, the population of the study and the context of the study, and that every step as designed by the researcher should fit with the purpose and focus of the research.

Run each design decision through four tests

  • Nature — does this step suit the kind of thing being studied, or is it borrowed from a study of a different kind of thing?
  • Aim — does this step move the stated aim forward, or is it there because it is customary?
  • Population — can the people you need actually be reached, and will this step work with them rather than at them?
  • Context — does this step survive the setting: the site access, the timeframe, the organisation's tolerance for the question?
  • Purpose and focus — read your aim and your instrument side by side; if the instrument would produce interesting data that does not answer the aim, the fit has failed

These tests are the practical content of coherence, and they are applied step by step at methodological coherence.

Worked example: a maturity benchmarking study

A design in the exemplar volume of master's project management research set out to establish and benchmark project management maturity. It explored existing maturity models, selected one, surveyed a sample of employees using the selected model, established a baseline, benchmarked against companies of similar size, identified gaps and recommended improvements — presented as a case study model other organisations could follow.

Source example — illustrative only

Where the perspective entered that design

  • At model selection. Choosing an existing maturity model imports its assumptions about what maturity is and how it can be observed
  • At the instrument. A model-based survey defines in advance what will count as evidence of maturity, which is an epistemological commitment made before the first response
  • At benchmarking. Comparing against similar-sized companies assumes maturity is comparable across organisations, which is an assumption about the nature of the thing being measured
  • At the recommendation. Gaps against a model are treated as deficiencies to close, which is a value position, not a measurement

None of that makes the design weak. It makes it a design with a perspective, and the difference between a strong and a weak version of the same study is whether that perspective is stated in the methodology chapter or left for the reader to infer. This is the general lesson: assumptions usually arrive with the borrowed instrument, and they arrive whether or not you notice them.

Writing the section

Six paragraphs that do the job

  1. Name the perspective and cite it

    One sentence naming the position, with a citation to a methods text rather than to a teaching handout — this material gives one-line definitions only.

  2. State the ontological assumption

    What you are taking the thing you study to be: a measurable state, or something people construct and account for. Two sentences is enough.

  3. State the epistemological assumption

    How knowledge of it can be created. If you are using the source's second gloss, describe your relationship to the topic and your access to the setting here.

  4. Show the chain

    Perspective to methodology to methods, with the reason at each hop. This is where the source's silence about mappings is answered by your argument.

  5. Apply the four fit tests

    Nature, aim, population, context — explicitly, in a short paragraph. Reviewers look for this and it is cheap to write.

  6. State the organisational framework and any tension

    Name the context the study sits in, and say plainly if your question runs against it. A disclosed tension is a limitation; an undisclosed one is a credibility problem.

Check before you proceed

Before the methodology chapter goes out

  • The perspective is named once and used consistently — not positivist in chapter three and interpretive in chapter five
  • Every methodology and method in the chapter is traceable back to the named perspective
  • Both glosses of epistemology in the source have been considered, and you have said which you follow
  • The organisational context is described, not assumed known by the reader
  • The claim you intend to make in your conclusion is one this perspective can carry

What to carry forward

  1. The theoretical perspective is the philosophical framework informing the methodology — the layer that carries assumptions into the design.
  2. The source defines ontology and epistemology twice, differently. Quote both and declare the one you are using.
  3. No mapping exists between the pyramid's philosophies, methodologies and methods; the fit is an argument you construct and cite.
  4. The claim that the framework reflects organisational context is the source's, unevidenced, and reads either as description or as instruction — say which you are taking it as.
  5. Every design decision faces four fit tests from the source: nature, aim, population and context of the study.

Frequently asked questions

Is the theoretical perspective the same thing as the theoretical framework?

No, and the supplied source uses them for different things. The theoretical perspective is the philosophical framework informing the methodology; the theoretical framework is described in the Week 3 material as containing the literature review and emerging from the conceptual framework. One is about your assumptions, the other is about the body of work you are joining.

Do I have to declare a perspective at all?

For a master's-level project the expectation in the source's own five elements is that you can account for it, because epistemology and ontology are described as embedded in it and therefore in your methodology. Practically, declaring nothing does not remove the perspective — it just leaves you unable to answer when a reviewer asks why your method suits your question.

What if my organisation's framework does not match the perspective my question needs?

Say so in the methodology and handle it in scope. The source states that every aspect of the project should fit the organisation's philosophical framework, but it offers no procedure for a mismatch. Agreeing the question and the reporting arrangements with your sponsor in writing is the practical answer, and the mismatch itself becomes a stated limitation.

Can one project use more than one perspective?

Mixed designs are common in the exemplar volume, where surveys and interviews are combined and triangulated with the literature. What is not defensible is leaving the perspectives unattributed, so each claim in your findings should be traceable to the part of the design that supports it and to the assumptions that part rests on.

How long should the philosophical framework section be?

The source sets no length, and length is not the measure. Six short paragraphs that name the perspective, state the two assumptions, show the chain to methods, apply the fit tests and describe the organisational context will outperform several pages of general philosophy that never touches your design.

References and source attribution

  1. Bryman, A. 2016, Social Research Methods, 5th ed., Oxford University Press, Oxford.
  2. Quinlan, C. 2011, Business Research Methods, 1st ed., Cengage Publishing (Chapter 1, p. 50 — source of the methodological pyramid reproduced in the teaching material).
  3. O'Leary, Z. 2017, The Essential Guide to Doing Your Research Project, 3rd ed., Sage Publications, London.
  4. Naoum, S. G. 2013, Dissertation Research & Writing for Construction Students, 3rd ed., Routledge.
  5. An edited volume of master's degree research projects in project management, 2018, academic publisher, 378 pp. (the exemplar volume; design summaries paraphrased from published abstracts).
  6. The supplied teaching source: Week 2 study notes, slide deck and terminology tables, 'Introduction to Research Methods', for a master's-level research subject in project management.

Suggested questions for Ask KEVOS

  • Draft the six paragraphs of a philosophical framework section for my research question.
  • Trace one of my draft conclusions back through data, method, methodology and perspective.
  • Which glosses of epistemology and ontology should I quote, and how do I say which I am using?
  • Is my organisation's operating view of evidence compatible with the design I have chosen?
  • Where does my methodology chapter change perspective without saying so?

Related KEVOS knowledge

The Five Basic Elements of a Research ProjectCore · research philosophyOntology: Assumptions About the Nature of RealityCore · research philosophyEpistemology: How Knowledge Is CreatedCore · research philosophyThe Methodological PyramidCore · research philosophyMethodological Coherence: Making Every Step FitAdvanced · research philosophyStep 5: Designing Your ResearchCore · research process
KEVOS® · Project Delivery · Research Projects Page KVS-PM-RES-0016 · v1.0.0 · content 2026.08 Last reviewed 2026-08-16

Continue learning

Epistemology: How Knowledge Is CreatedGuide · Research ProjectsNEXT LESSON →Positivism and Post-PositivismGuide · Research ProjectsOntology: Assumptions About the Nature of RealityGuide · Research ProjectsConstructionism and ConstructivismGuide · Research Projects
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®