D31
Back to the archive
D31 / FIELD NOTES#058

Signals and practice

Platform adoption begins with the first step

Origin: D365-IRL · Day 394 · November 3, 2026

Carlos Ocampo · Field Note #058

English translation of the original Spanish publication. Original dates, authorship and documentary images are preserved.

A D365-IRL session shows how registration, email confirmation, and hands-on support reveal the friction people encounter when adopting a new digital platform.

D365-IRL™ · Day 394

Loading the session…

Watch the D365-IRL session behind this note

Thesis

Registration is the first encounter between a community’s promise and a person’s ability to participate.

Field coordinates

Date: November 3, 2026, identified by Carlos Ocampo

Location: virtual D365-IRL session; physical location not documented

Time: not documented

Source episode: Day 394, as identified for this delivery

Type: signals and practice

Source video: https://www.youtube.com/watch?v=8kwG5ZbGApQ

Status: editorial note based on an automated session summary

What does a community need to adopt a new digital platform?

A community needs to understand the platform’s purpose, complete an initial step, and find help when progress stops. During the November 3, 2026 D365-IRL session, registration and email confirmation required part of the team’s attention. The proposed lesson is to observe those difficulties and use them to improve how people enter the experience.

The project begins when someone tries to enter

The session introduced the D365-IRL platform for 2027. It included participation options, a referral scheme, and a preparation period ahead. Yet an important part of the work focused on a more immediate action: creating an account and confirming an email.

The summary records registration questions and difficulties showing the platform. Carlos moved to step-by-step guidance. Preparing the next cycle took a concrete form: helping participants enter and understand what would follow.

That moment raises a question relevant to many digital rollouts: what happens between announcing that a tool is available and enabling someone to use it?

An existing account does not resolve a new transition

The conversation explained that the previous Monday registration would not replace an account on the new platform. For people already participating in the community, this added a step that needed explanation.

The new account was presented as part of a structure for following projects and their goals. Its purpose needed to become clear alongside the instructions for completing registration. Otherwise, participants could understand it simply as another administrative task.

The observed gap was practical: the team knew the entry process, while some people still needed guidance through it. Making that difference visible helps identify the missing explanation, instruction, or support.

Field note

Synthesis of the session summary, not a verbatim quotation from Carlos: the team asked people to report registration difficulties and offered individual help to resolve them.

Choosing how to participate also requires clarity

Carlos presented open participation and options offering different levels of support. He also distinguished the situation of participants considering capital for 2027, advising them to keep an open registration and wait for a later call.

The editorial lesson is that entering a community involves different decisions. A person needs to understand how to gain access. They can then evaluate the support that suits them and the conditions they accept. For those exploring capital, it also matters to understand which information and requirements remain outstanding before discussing specific opportunities.

Clarity about those decisions makes better questions possible. Creating an account alone does not demonstrate that a participant understands the next step.

Working definition · v0.1

Supported adoption: helping a person understand and complete an initial action within a tool, recording the difficulties they encounter, and using that information to adjust the experience.

Friction needs to lead to a correction

WhatsApp support was a concrete response to registration difficulties. Participants were also asked for feedback to help correct the process.

That signal suggests a practice for any team introducing a platform: record where a person stops, establish what information they needed, and test the journey again after making an adjustment. This is a proposal derived from the session. The summary does not establish that a measurement system already exists or that friction has decreased.

Evaluating the hypothesis would require observing, for example, how many people start and complete registration, which obstacles recur, and how many complete their first action. Those data are not available here.

A D31 reading

The experience connects with High Frequency Execution™: shortening the distance between action, learning, and adjustment. During onboarding, useful information emerges while someone tries to use what the team has built.

The working hypothesis is that support becomes more useful when it both resolves the immediate case and helps correct difficulties other people may encounter. Its value must be tested in the next user journey.

Building in public makes it possible to show that learning without presenting a launch as a finished experience. It also requires distinguishing what was announced, what people could actually do, and what still needs adjustment.

Timeline

  • November 3, 2026: session identified by Carlos for this note; introduction of the platform and registration guidance
  • November and December 2026: preparation period described in the summary; each participant should confirm their current schedule
  • December 2026: capital-related call announced during the session; its terms have not been verified in this record
  • January 2027: cycle launch discussed during the conversation

Sources and evidence

  1. Automated D365-IRL session summary provided by Carlos Ocampo. This is a summarized source, not a transcript or a complete audio verification. Verifiable personal archive. Evidence collection is ongoing.
  2. D31, public information about D365-IRL 2027, accessed November 6, 2026: D365-IRL 2027
  3. D31, High Frequency Execution™: https://www.d31.mx/field-notes/high-frequency-execution?lang=en
  4. Editorial interpretation: the relationship between support, entry difficulties, and improved adoption is a working hypothesis. No outcome metrics are presented.

Next action

Observe someone’s first journey through your platform. Identify where they need help and choose an improvement you can test again.

To explore D365-IRL 2027 and review current participation conditions:

D365-IRL 2027

Editorial note

Schedules and conditions described during a session may change. Before purchasing or applying to a call, always consult the program’s current information.

Legal notice

Informational, educational, and analytical content. It does not constitute financial or legal advice, or a promise of investment or results. D365-IRL 2027 conditions, pricing, schedules, and availability are governed by D31’s current offer.

Keep exploring

Let’s talk
Digital onboarding: from registration to participation