Reading a Bogotá MSME Diagnosis Through the PMBOK Guide: What the Principles and Performance Domains Actually Offer By Stacy Camila Ortiz León
A Framework Born for Business, Tested on a Classroom Project
across
contexts
(Calle,
2024).
That
portability is precisely what makes it a fair
Most people who have heard of the PMBOK
lens for an academic diagnostic project, even
Guide picture it inside a construction firm or
one with no budget, no client contract, and
a software company, guiding a project
no construction crew.
manager through Gantt charts and budget lines. It is worth asking, then, whether a document
written
by
the
Project
Management Institute for that world has anything useful to say about a university research seminar built around a survey of 193 small food businesses in Kennedy, Suba, and Engativá. The short answer, after working through both the guide and the diagnostic study it is being compared against, is yes, and not only in a superficial way. The seventh edition of the PMBOK Guide moved away from a rigid, step-by-step process model toward a set of principles and performance domains meant to travel
This piece argues that the shift matters. A framework
built
only
for
predictive,
industrial projects would sit awkwardly next to a descriptive, cross-sectional study run through Google Forms. A framework built around principles of value, stakeholder engagement, and adaptability, however, fits research work almost naturally, because research is itself a form of project management: it has interested parties, a plan, a delivery of value in the form of knowledge, and no shortage of uncertainty along the way.
What the PMBOK Guide Is, and Why the Seventh Edition Changed Course
with
The PMBOK Guide is best described as a
intended to make the guide flexible enough
compendium
and
for both traditional and adaptive project
techniques for directing projects, assembled
environments (Aldridge, 2026). In practice,
by the Project Management Institute to give
this means the current PMBOK Guide asks
practitioners a common structured language
fewer questions about which template to fill
regardless of industry (Calle, 2024). It is not
in and more questions about what a project
a rulebook that must be followed line by line;
is actually trying to achieve and for whom.
of
practices,
tools,
twelve
principles
and
eight
performance domains, a change explicitly
it functions closer to a reference point, something a project team consults to decide
Twelve Principles, One Underlying Idea
how much planning is enough, how to
The twelve principles set out in the seventh
organize a team, and how to keep an
edition cover a wide range of concerns, from
initiative aligned with the outcomes it was
professional and ethical responsibility, to
meant to produce.
collaborative team leadership, stakeholder
Earlier versions, including the widely used sixth edition, were organized around process groups and knowledge areas, an approach that walked practitioners through initiating, planning, executing, monitoring, and closing a project in a fairly linear sequence. That structure worked well for large, predictable projects but proved less comfortable for teams working in agile, iterative, or hybrid environments, where requirements shift and deliverables emerge gradually rather than all at once. The seventh edition responded to that tension by replacing the process-and-knowledge-area
architecture
engagement, a focus on value delivery, navigating complexity, effective leadership, adaptability, quality, risk and uncertainty management, optimization of resources, continuous
improvement,
and
the
management of change itself (Aldridge, 2026). Read individually, they can look like a checklist. Read together, they point to a single underlying idea: a project succeeds not because every task was completed on schedule, but because the people who depend on it received something of genuine value, delivered by a team that behaved responsibly and adjusted course when circumstances demanded it.
That distinction is easy to overlook,
and managing their expectations; the team
especially in a student project, where the
domain concerns building and leading the
temptation is to treat completion of the
people who will carry the work out; the
survey, the data tables, and the final report
development approach domain concerns
as the whole of success. The principles push
choosing between predictive, agile, or
back on that narrow view. They ask, in effect,
hybrid ways of organizing that work;
whether the people surveyed actually
planning
benefited from being asked, whether the
objectives, and the resources needed to
findings will be usable by someone beyond
reach them; project work concerns the
the classroom, and whether the team
coordination that keeps daily tasks moving
adapted its methods when the field did not
toward the deliverables; delivery concerns
behave the way the proposal assumed it
making sure the project produces something
would.
bureaucratic
of real value; measurement concerns
questions; they are the difference between
tracking performance against meaningful
research that sits in a drawer and research
indicators;
that changes how a handful of small
identifying and responding to risk before it
businesses sell their products.
derails the effort.
Eight Domains, One Continuous Thread of Delivery
None of these domains function as an
Where the principles describe the mindset a
groups did. They run in parallel and feed
project team should hold, the eight
back into one another throughout a project's
performance domains describe where that
life, which is part of why the seventh edition
mindset gets applied. The seventh edition
presents them as a system rather than a
organizes project work around stakeholders,
sequence. A research diagnostic, it turns out,
team, development approach and life cycle,
moves through very much the same system,
planning,
even though nobody on the team ever called
Those
are
project
not
work,
delivery,
measurement, and uncertainty (Calle, 2024). The
stakeholder
domain
concerns
identifying who has an interest in the project
concerns
and
defining
uncertainty
scope,
concerns
isolated stage the way the old process
it that at the time.
Where the Principles Meet a Bogotá Survey of 193 Agri-Food MSMEs
afterward. A diagnostic that stopped at
The project under review here diagnosed the
to the four strategic lines that followed,
level
would have delivered data but not value.
of
digital
tool
adoption
for
description, without connecting its findings
commercialization among micro and small agri-food businesses in three localities of Bogotá, drawing on a structured survey applied to 193 enterprises out of an estimated population of 13,300. Framed against the PMBOK Guide's principles, four stand out as doing most of the work: the focus
on
value
delivery,
stakeholder
engagement, adaptability, and quality (PMI,
Stakeholder engagement shows up just as clearly, though less obviously, because the stakeholders here were not investors or executives but small business owners in Kennedy, Suba, and Engativá who agreed to answer a Google Forms survey about their own commercial habits. Treating that population seriously, understanding what would make them willing to participate
2021).
honestly,
and
later
designing
Value delivery is arguably the clearest fit.
recommendations that respected their real
The whole point of measuring how many
constraints, such as limited time and low
surveyed
digital
businesses
use
confidence,
reflects
the
same
Business, accept digital payments, or
commitment to understanding interested
generate
through
parties that the guide describes as a core
digital channels was never the measurement
principle rather than an afterthought
itself; it was to produce a diagnostic accurate
(Aldridge, 2026).
meaningful
revenue
enough that a real strengthening strategy could be built on top of it. When the findings showed that 43% of respondents were not actively using WhatsApp Business, or that 62.2% obtained less than 10% of their sales through digital channels, those numbers only mattered because they fed directly into the strategic roadmap the study proposed
Adaptability enters through the practical reality of academic fieldwork. A population of 13,300 small businesses spread across three localities does not respond uniformly to a digital instrument; access, willingness, and time available to answer all vary, and a rigid data-collection plan would have
struggled against that variability. The
The stakeholder domain is where the study
decision to work through a structured but
begins, in practical terms, since identifying
flexible online instrument, and to accept a
the population of micro and small agri-food
sample of 193 firms rather than force an
businesses across the three target localities,
unreasonably large one, is itself a small
and deciding how to reach a representative
demonstration of the principle of adapting
slice of them, determined nearly everything
method to circumstance rather than the
that
reverse.
governed
Quality, finally, relates less to polish and more to the credibility of the diagnostic itself. A descriptive, cross-sectional study built on self-reported survey data is only as useful as its methodological rigor, its clear objectives, and its honest reporting of both strengths and limitations, such as the low
followed.
The
the
planning
choices
domain
behind
the
quantitative, descriptive, deductive, nonexperimental, and cross-sectional design, along with the decision to use a structured survey instrument delivered through Google Forms rather than, say, in-person interviews that the available time and resources could not have supported.
levels of formal digital training reported by
The project work domain is less visible in a
71.5% of respondents. Holding that bar is
final report but was arguably where most of
what separates a diagnostic that can support
the actual effort went: distributing the
real strategic decisions from one that
survey, following up with non-respondents,
cannot.
cleaning the resulting data, and organizing it into the categories that later became the
Where the Domains Meet the Same Project Turning to the eight performance domains, five map onto the diagnostic project with unusual precision: stakeholders, planning, project
work,
measurement,
uncertainty (Calle, 2024).
and
findings on smartphone ownership, internet access, WhatsApp Business usage, and digital
payment
acceptance.
The
measurement domain then took over once that
data
percentages,
existed,
translating
such
the
as
89.1%
raw of
respondents owning a smartphone or the 29%
who
cited
training
gaps
and
implementation
leading
forcing a fit that is not really there, that any
barriers, into indicators that could actually
sufficiently flexible framework can be made
support conclusions rather than sit as
to describe almost any organized activity
isolated figures.
after the fact. There is something to that
Uncertainty,
the
costs
final
as
the
domain
worth
highlighting, ran underneath the entire effort. A student research team working with a fixed academic timeline, a sample drawn from a population an order of magnitude larger than what could realistically be surveyed, and a topic, digital confidence, where responses can be shaped by social desirability, faces exactly the kind of ambiguity the PMBOK Guide asks project teams to name and manage rather than ignore (PMI, 2021). The near half of respondents, 49.7%, who reported low trust in digital platforms is itself a reminder that even the data-gathering process was operating
inside
an
environment
of
hesitancy and uncertainty that the team had to account for in how it interpreted the results.
A Fair Objection, and Why It Does Not Undercut the Comparison
concern, and it should temper any claim that the PMBOK Guide is indispensable to research design specifically, since the study in question was clearly guided primarily by its academic methodology, its deductive quantitative approach, and its research objectives, not by project management theory. Even so, the exercise of mapping the guide onto the diagnostic is not empty. It surfaces
a
genuine
parallel:
both
a
commercial project and a piece of applied research live or die on whether they understood their stakeholders correctly, planned realistically, tracked the right indicators, and adapted when uncertainty appeared. The PMBOK Guide simply gives that intuition a shared vocabulary.
Closing Thought The value of reading a research diagnostic through the PMBOK Guide's seventh edition is not that it teaches researchers something
It would be reasonable to object that
they did not already know about running a
stretching a corporate project management
study. It is that it names, in transferable
standard over an academic diagnostic risks
terms, the discipline that a well-run diagnostic already practices: understanding
who the work is for, delivering something
pmbok-7-principios-y-dominios-
they can actually use, staying flexible when
explicados/
the field does not cooperate, and treating measurement as a means to a decision rather than an end in itself. Applied to the Bogotá
agri-food
MSME
study,
that
discipline is visible in how the low rates of digital payment acceptance and WhatsApp Business use were not left as bare statistics but were carried forward into a four-part strategic
roadmap
covering
training,
progressive digital implementation, security, and follow-up support. That, more than any formal checklist, is what the guide's principles and domains are ultimately describing.
References Aldridge, E. (2026, February 6). PMBOK® 7 vs PMBOK® 8: Key differences & 2026 updates.
Project
Academy
Management Resources.
https://projectmanagementacadem y.net/resources/blog/pmbok-7-vspmbok-8-differences/ Calle, M. (2024). Revisión del PMBOK 7: Principios y dominios explicados. https://marcocalle.com/que-es-el-
Project
Management PMBOK
Institute.
(2021). guide.
https://www.pmi.org/standards/pm bok