Signals and practice
Organizational culture from day zero: the habits a founder creates
English translation of the original Spanish publication. Original dates, authorship and documentary images are preserved.
A founder’s decisions, protocols and example turn principles into habits. A field note on culture, delegation and team coordination.
Watch the D365-IRL session behind this note
Origin: D365-IRL · Day 390 · 2026-10-27.
A company's culture begins in repeated decisions: how customers are treated, what quality is accepted, how mistakes are handled and which behaviors are tolerated. Designing it early helps a team understand how to work when the founder is absent.
D365-IRL Day 390 placed this responsibility at the center. Drawing on Tech Week conversations and community experiences, the session connected culture, leadership and working systems.
Principles need observable behavior
Juan Miguel described a restructuring experience shaped by a gap between the company's original culture and the culture that had developed over time. His account raises an operational question: do people mean the same thing when they talk about delivering, collaborating or doing good work?
A principle becomes useful when it supports a decision. Discussing quality requires explaining what should be checked before delivery. Discussing autonomy requires clarifying what each person can resolve and when they need support. Founders communicate these rules through their instructions and their own actions.
Document the work and sustain the practice
The description includes Karen's account, from Mimetate, of introducing safety and organizational protocols in her architecture business. She reported initial resistance and a need for persistence; over time, the processes became part of the team's habits.
The editorial lesson is that documentation becomes more useful alongside practice, explanation and follow-up. A document makes a standard accessible; daily work reveals whether people understand it and can meet it.
To examine your own system, choose a recurring situation and answer together: what result do we expect, who decides, which limit must be respected and how do we report a problem? These questions are an application proposed here, not a protocol tested during the session.
Developing people also builds capacity
The conversation addressed difficulties finding certain profiles. As a participant reflection, it opened several possibilities: developing people, broadening the search, revisiting the role or changing how work is organized.
Before adding someone, make explicit what they will need to learn and which support is available. Delegation requires that a person can recognize a good decision and has room to develop that judgment. A leader's consistency is part of that learning.
Bring culture into a working conversation
If you are building a company and want support with these decisions, explore the D365-IRL 2027 route for founders.
If your team needs to connect perspectives, focus priorities and translate them into agreements, request a PowerDay proposal. Scope and continuity options are defined in the proposal.
When this review concerns the impact of Mexico's labor reform on costs, processes and coordination, explore AUTONOMÍA and discuss the impact on your company — page in Spanish. Legal and operational assessment depends on each organization's circumstances.
Questions this note addresses
When does organizational culture begin? When the first decisions and behaviors start repeating. It does not need to wait for an HR department.
Is documentation enough to delegate? A document helps, but explanation, practice and follow-up are needed to turn it into a team capability.
Continue with learning to teach before delegating.
Editorial source: official description of D365-IRL session 390, accessed October 31, 2026. This note develops its lessons; it is not a transcript or an independent verification of participant accounts.
Offer scope, terms and availability are governed by the current landing pages.