Protect the core

The August 27 D365 session addressed a situation under pressure: commitments coincide when available resources are not enough to resolve everything at once. Carlos Ocampo used a hypothetical exercise to ask what sustains an organization's ability to keep operating.

The question does not make every obligation optional. It proposes distinguishing each decision's effect on continuity, without confusing the intensity of a demand with its importance to operations.

Ocampo described the core through the ability to produce and deliver: the people, tools and processes that make work possible. He did not present it as an identical list for every company.

That distinction matters. A technology may be essential to one operation and secondary to another. A seemingly administrative process may sustain a delivery. Identifying the core requires understanding those relationships, not simply labeling expenses or departments.

The organizational reading of the session is to recognize dependencies: what needs to keep working, who makes it possible and what stops when one part fails. It is a coordination question before it is a cost-cutting formula.

In the exercise, the urgency of whoever was making a demand was not enough to order every decision. The proposed criterion was to ask how much each situation affected the ability to sustain operations. This note preserves that question without turning hypothetical numbers into a financial prescription.

For an internal conversation, it can become a record of questions:

• Which capacity to produce or deliver is at risk?
• Which people, processes or tools depend on that capacity?
• What information is missing to assess the impact, and who can provide it?

These questions are an editorial synthesis of the approach, not instructions to defer payments, breach contracts or alter employment rights. Any concrete decision requires reviewing applicable obligations and consequences with the appropriate responsible people.

The session distinguished reorganization and renegotiation from neglecting commitments. It also proposed reviewing priorities when circumstances change. Preserving that precision prevents “protecting the core” from becoming a justification for ignoring the rest of the organization.

Responsiveness needs context, agreements and review. It cannot rely solely on one person deciding under pressure what to postpone. That is why the approach connects with reading commercial signals: the less clear the information, the more important it becomes to distinguish knowledge from assumptions.

Toward the end, Ocampo returned to the need for a protocol for action and focus before an emergency. Preparation appears as a way to reduce decisions driven by the emotion of the moment, not a guarantee that a crisis can be avoided.

This leaves a question for the organization: is there a shared criterion for recognizing what sustains its operations, or will each department have to invent one when pressure arrives?

Editorial synthesis of the public D365 session of August 27, 2026, based on the available automatic transcript. Reference passages: 02:45–13:03 and 31:20–32:57. Unverified percentages, identifiable cases and current-affairs claims are omitted. This is an educational reading of organization and continuity, not personalized financial or legal advice.

Intellectual property and editorial use.