Culture is also built outside the office

Carlos Ocampo · Field Notes D31 · Based on D365-IRL, Day 362 · September 17, 2026

What value is there in bringing people together when the gathering is not intended to close a sale or deliver a project?

On Day 362 of D365-IRL, we discussed culture, leadership, team building, institutional events and community. The conversation opened a question about the spaces we dedicate to giving thanks, reconnecting and strengthening our relationships.

The session summary retained a central idea: gatherings can also serve the purpose of connection and trust-building. Evaluating them requires recognizing that purpose and remaining consistent with available resources.

At D31, we propose viewing these spaces as part of the work of building an organization.

Everyday operations allow us to know people through their responsibilities: who sells, who delivers, who authorizes, who resolves problems. A gathering outside that routine can open conversations that usually remain pending.

What is the other person experiencing? What effort have we failed to recognize? What difficulty do we share? What do we need to understand to work better together?

Culture takes shape in how we treat one another, what we recognize and what we do with what we hear.

Bringing a team together offers an opportunity to observe those practices. Who has room to speak. How a difference is received. Whether people can participate without feeling forced to expose themselves. Whether leadership listens with the same attention with which it expects to be heard.

The design of the gathering matters. So does what happens afterward.

Consider a gathering where two departments discover that they have spent weeks facing the same problem from different perspectives. The conversation may open a possibility for coordination. To turn it into an improvement, someone needs to revisit the issue, agree on an action and follow up.

That is where we connect shared experience with execution.

At D31, we propose that a team-building exercise have an understandable purpose: getting to know one another better, reviewing how we collaborate, recognizing contributions or addressing a team difficulty. That purpose guides the experience and allows us to evaluate what it left behind.

For a recognition event, we might ask whether people understood which contributions were valued. For an integration event, whether they could meet the people they need for collaboration. For a coordination event, whether agreements emerged that were later put into practice.

The experience gains continuity when what was lived finds a place in everyday work.

HFE™ can provide a rhythm for reviewing those agreements: what we committed to do, what changed and what needs attention. The conversation continues through observable actions.

Financial consistency is also part of the design. An organization needs to choose a format it can sustain and explain. The size of the event should respond to its purpose, its people and its actual possibilities.

This reflection connects with Caso Cero and our exploration of the autonomous company: what relationships allow people to take initiative, seek one another out and coordinate when a central instruction is absent?

Gatherings offer a space to cultivate those relationships. Their contribution must be observed in the willingness to converse, ask for help, enter into agreements and answer for them.

D365-IRL is part of that same question. Frequent conversation opens opportunities to get to know one another, recognize shared problems and support decisions. Each session allows us to examine what we are building together and how to bring it into everyday life.

If your team needed to coordinate in response to an unexpected event tomorrow, what relationships of trust would it have available?

Field note based on the recovered editorial summary of Day 362. The example of the two departments is illustrative; it is not presented as a documented case from the session.

© 2026 D31. All rights reserved.