Food sovereignty and food security are often used in the same conversation, sometimes as if they mean the same thing. They do not. Both take hunger and reliable access to nourishing food seriously. Food security focuses on whether people can get enough safe, nutritious food. Food sovereignty includes that concern, then asks who gets to make the decisions about land, seeds, water, production, markets, cultural knowledge, and the stories attached to food.
That difference matters when a museum, community organization, funder, school, or public program brings food into its work. A program can be generous, well attended, and still make decisions before the people most connected to the foodways have been invited to lead. Knowing which question is being asked helps partners plan more honestly, share power more clearly, and avoid treating food as decoration for a story that belongs to someone else.
Food security asks whether people can eat well and reliably
Food security is about dependable access. The USDA’s framework distinguishes between households with reliable access to adequate food and households facing limited or uncertain access. It also recognizes that a family may have enough food in quantity while still experiencing a reduced quality, variety, or desirability of diet.
This is practical and urgent work. It can include making food affordable, strengthening distribution, supporting school meals, improving transportation, increasing benefits access, or responding quickly during a crisis. A pantry, a meal program, a community refrigerator, or a benefits navigator can reduce immediate harm. Those efforts deserve care, funding, and respect.
Food security does not have to be narrow. The Food and Agriculture Organization of the United Nations describes availability, access, use, and stability as interconnected conditions. The phrase is especially useful when a team needs to understand whether people can reliably get food that supports an active, healthy life.
Food sovereignty asks who shapes the system
Food sovereignty adds questions about authority, relationships, and self-determination. It asks whether people most connected to a place and its foodways have meaningful power in decisions about what is grown, gathered, prepared, sold, taught, and celebrated. It can involve land and water, seed keeping, labor, local economies, cultural continuity, and the right to define priorities without having them imposed from outside.
The term entered global public conversation through La Vía Campesina in the 1990s. A Food and Agriculture Organization resource notes an important distinction: food sovereignty is a political concept, while food security is both a technical term and a public goal. That does not make one more important than the other. It means they work at different levels of the same problem.
Food security asks whether food is there. Food sovereignty also asks whose knowledge, choices, and relationships are shaping how it gets there.

A comparison that keeps both concerns in view
It can help to think of food security as an access question and food sovereignty as a power question. Access without power can leave people dependent on systems they cannot influence. Power without access does not meet an immediate need. Thoughtful public work does not force a choice between the two. It takes reliable nourishment seriously while asking whether the process builds dignity, local capacity, and lasting relationships.
- Food security: Can people consistently obtain enough safe, nutritious food?
- Food sovereignty: Can people meaningfully shape the food system affecting their communities?
- Food security: What barriers keep food out of reach right now?
- Food sovereignty: Who sets the priorities, and whose knowledge carries weight?
- Food security: How do availability, affordability, and stability improve?
- Food sovereignty: How do cultural practice, ecological care, and community benefit remain central?
The distinction also protects against a common shortcut: treating culturally meaningful food as a theme rather than a relationship. A menu, market, or cooking demonstration may open a door, but it does not automatically create a community-led project. The planning process, compensation, credit, and decision-making structure are where intent becomes visible.
Three misunderstandings worth leaving behind
First, food sovereignty is not a synonym for local food. Buying locally can strengthen relationships and local economies, but proximity alone does not show who holds power. A locally sourced event can still be planned without the growers, cooks, or communities whose knowledge gives the food its context. The question is not only where an ingredient came from. It is whether the work respects the relationships around it.
Second, food sovereignty is not a label an institution can award itself. It is not proven by a mission statement, a social post, or a beautiful event. It becomes visible through practice: who was invited in early, who could say no, who was paid, who had authority over public language, and whether the work created a benefit that participants recognize.
Third, food security is not a lesser goal. When a household cannot reliably obtain enough food, immediate access matters. The comparison is not a contest between a practical need and a more ambitious idea. It is a reminder that emergency response and long-term power can belong in the same plan, as long as the people affected are not reduced to recipients of someone else’s solution.
Why the difference matters for Indigenous foodways
For Indigenous communities, foodways can be inseparable from land, water, language, seasonal knowledge, kinship, ceremony, and governance. No single article can speak for every Nation or community. That is precisely the point. Responsible work begins with the people whose foodways are involved, rather than applying one broad story, one set of ingredients, or one outside definition.
Food sovereignty can offer a useful frame because it makes room for those relationships and for community-defined goals. It does not give an institution permission to claim a relationship it has not built. It calls for patience, consent, clear agreements, and room for people to decide what should remain private. The earlier introduction to food sovereignty explores that wider context and the difference between an invitation to learn and a demand for access.

What this changes for a public program
A team planning a food-centered event does not need to claim food sovereignty for every gathering. In fact, restraint is often more credible than expansive language. If the work is a tasting, say so. If the goal is food access, name that. If a partnership is community-led, make the structure behind that claim real. Honest language earns more trust than a borrowed framework.
When the project does involve cultural foodways, the most useful planning questions are straightforward. Who defined the purpose? Who has authority to change the format? Who is being paid for expertise and labor? How will credit be given? What does a meaningful benefit look like after the audience leaves? And what stories, recipes, locations, or practices should not be made public?
Those questions can reshape the practical work: the budget, the timeline, the partners, the invitation, the stage, the menu, and the follow-up. They can also prevent a familiar failure, where a team asks a knowledge holder to validate a program that was designed without them. The better route is to bring people in before the decisions harden, and leave enough time for the collaboration to change the plan.
At the table, clarity builds trust
Food-centered work often begins with enthusiasm. A partner has an idea for a dinner, a workshop, a market, or a public conversation. Enthusiasm is useful, but it is not a substitute for clarity. Before invitations go out, name the purpose, the commitments, and the limits. Decide what success will mean for the hosts as well as the audience. Make the terms visible enough that people can point to them when the project changes.
This is especially important when a program is asking someone to share lived knowledge. A respectful invitation includes enough information to make an informed choice: what will happen, who will be present, what will be recorded, how compensation works, how public language will be approved, and what follow-up is expected. It leaves room for someone to decline, change the format, or ask that part of the story remain offstage.
That degree of care is not a barrier to a compelling event. It is often why an event becomes more memorable. Audiences can feel when a gathering has been shaped with people rather than around them. The specificity shows up in the welcome, the pacing, the context, the voices on stage, and the choices that continue after the room is empty.
For partners, the same clarity makes collaboration easier to sustain. It gives everyone a way to discuss changes before they become misunderstandings, whether a sponsor request, a venue constraint, a media opportunity, or a shift in budget. The goal is not a flawless plan. It is a working relationship with enough honesty and room to adapt when the work asks for something different, while keeping the people most affected by the program close to every decision and giving them a clear path to shape the next one.
Four ways to move from intent to practice
- Start with relationships, not a finished concept. Learn what is already happening and ask whether a public partnership would be useful before drafting a program around someone else’s foodways.
- Pay for the work. Knowledge, preparation, travel, facilitation, translation, and follow-up are work. Build compensation into the first budget, not the last conversation.
- Share decision-making early. Invite collaborators to shape the purpose, format, public language, and boundaries. Consultation after a plan is fixed is not shared leadership.
- Measure what lasts. Attendance may matter, but so can repeat partnerships, paid opportunities, local purchasing, audience learning, and whether participants want to work together again.

How Tarra Lazos Creative helps
Tarra Lazos Creative helps partners build public experiences around place, food, memory, and community with the relationships at the center. The studio’s expertise and community engagement consulting pages show the kinds of planning, partner coordination, and cultural production that can support this work. The events and programs page offers a closer look at how food, storytelling, and gathering can come together in public.
For Arizona partners seeking local context, the site’s food and agriculture facts provide a sourced starting point for a conversation about the state’s agricultural landscape. For a project that needs a thoughtful beginning, the next useful step is a conversation about the people who should be in the room, what needs care, and what a respectful outcome could make possible.
Frequently asked questions
Can a project support food security and food sovereignty at the same time?
Yes. Meeting an immediate need for affordable, nourishing food can sit alongside work that gives community members real influence over the food system. The key is to be clear about which goals are present and who holds decision-making power.
Does food sovereignty mean total self-sufficiency?
No. Food sovereignty does not require every community to produce everything it eats. It focuses on meaningful participation in the choices that shape food, including trade, production, cultural practice, and local priorities.
How should an organization describe a food-centered program?
Use language that matches the work. If the program focuses on access, say so. If it is community-led, show that through paid partnership, shared decisions, and clear credit. Do not claim a framework the program has not earned.
Planning a food-centered public program?
Build the conversation before you build the event.
Start a conversation
