tl;dr
Transmission separates rituals from habits. A habit dies with the person; a ritual belongs to a role and outlives whoever holds it.
Rituals reduce behavior change and increase adoption rates.
Venture-scale density = a small entry point already holding the ingredients of a much larger company.
One of the first questions I ask a founder about a workflow tool is “will anyone actually stop and use/do/reference this?”
Documentation products die on this question all the time. Asking busy people to pause and narrate their work, for the benefit of some future reader, is asking for a habit that almost nobody sustains.
A few weeks ago I spent an hour with a founder building voice software around after-action reporting. The premise, stripped to its simplest form: after consequential work, the people involved should record what happened and what they learned, and software should turn that account into something the institution can actually use.
The product, in other words, was entering a moment of reflection the institution already performs, rather than attempting to create reflection from nothing. The behavioral question shrinks from “will people adopt a new habit” to “will people let a tool into a habit they already have.”
Intuitively, we’ve always loved these products that create data exhaust, but recently we’ve started identifying the very specific, narrow wedge they target as a ritual.
Recommended for you:
Your Guide To Corporate Venture Capital
If you ask ten founders what corporate venture capital is, you’ll probably get ten different answers.
Job, ritual, workflow
Founders and investors already have good vocabulary for two adjacent ideas, and the ritual sits between them.
The job to be done answers why someone needs to act. In the after-action case, the job is to learn what happened and prevent recurrence. The unit of analysis is the outcome someone wants.
The workflow answers how the work moves from beginning to end. Here: capture the accounts, synthesize them, compare them against expectations, assign what follows. The unit of analysis is the sequence of tasks, handoffs, tools, and outputs.
The ritual answers a different question: when, with whom, and under what obligation does the action occur? In this case, the relevant team gathers immediately after the event to debrief. The unit of analysis is the recurring, role-bound institutional moment.
A ritual is more than something that happens repeatedly.
It has a recognizable trigger: the consequential event just ended.
It has understood participants: the people who were there, sometimes joined by whoever is responsible for what happens next.
It has roles: someone leads, others contribute what they saw, someone carries authority over the follow-up.
It has shared language: participants belong to the same institution and describe the work in its terms.
It has obligations and consequences: it exists precisely when the work carries stakes.
It has an expected output: it could be as simple as a shared understanding and a few commitments.
The ritual sits alongside the job to be done and the workflow and the three layers are complementary rather than competing. Specifically because each one answers a question the others cannot.
The job tells you the progress people want, but a job floats free of any particular time or place; people want to learn from failure continuously and abstractly.
The workflow tells you what the work looks like once it begins, but a workflow says nothing about why it ever begins.
The ritual supplies what both are missing: the where, the when, the who, and the obligation. It locates the abstract job in a concrete institutional moment and gives the workflow its starting gun.
Layers make a stack
The relationship among them is the useful part: the wedge enters through the ritual, improves the workflow, and helps complete the job.
Consider what a software product normally has to establish on its own before anyone uses it well:
When the product should be used
Who should participate
Why they should care
What information should enter it
What artifact or decision should emerge
What happens next
Most products manufacture these conditions from scratch. They send reminders to create a trigger. They chase seats to assemble participants. They run change management to generate urgency. They beg for data entry. They evangelize an output nobody asked for. Much of what we call go-to-market is really the expensive construction of context.
A ritual supplies that context before the product arrives. The trigger exists: the event just happened. The participants are assembled: the moment already draws them together. The urgency is real: the work was consequential, and the institution expects an account of it. The information is present, still fresh, in the heads of people standing in the same room. The expected output is understood, because the ritual has always produced one, however informally. And the moment already points at what happens next, because the debrief exists to shape it.
The wedge therefore has a reliable insertion point. It appears when attention is already concentrated and action is already expected. That is a rare and valuable position for a narrow product, and it is worth distinguishing from the usual situation of a tool waiting hopefully in a browser tab. A product outside a ritual competes for attention against everything else in the workday. A product inside one arrives at the single moment when the institution has already cleared space for exactly the work the product does.
None of this amounts to free distribution or guaranteed adoption. The ritual creates favorable conditions; the product still has to be useful, trusted, and well fitted to the moment it enters. What the ritual removes is the burden of inventing the moment itself. But the conditions are borrowed rather than owned, which raises a question about durability I return to below.
Behavior change, narrowed
A ritual narrows the behavior change without eliminating it. Some new behavior remains, and the product’s fit with the moment decides whether what remains is acceptable.
The after-action case makes the point through the question of capture, where there are three options.
The first is to ask workers to record insights as they occur. This requires a new habit with no context, no trigger, and no social support, and it fails for the reason most documentation initiatives fail.
The second is to record everything continuously. Ambient capture removes friction, but it also removes the boundary that tells people when they are speaking for the record. Continuous recording reads as surveillance, and the trust cost lands on exactly the people whose candor the product depends on.
The third is deliberate capture inside the understood debrief. Someone pushes to talk and everyone present knows why. The recording has a purpose, an audience, and a boundary matching one the ritual already maintained, so the behavior change shrinks to a gesture that makes sense to the people performing it.
That answer belongs to the ritual rather than to the problem, and elsewhere it inverts. Outside sales teams in pharmaceuticals hold what amount to windshield calls: reps phone one another between appointments to talk through what the customer pushed back on and how somebody else has answered it.
The moment takes that form for a regulatory reason, since the rules governing what a representative may say constrain the official channel tightly enough that the knowledge gets squeezed out of enablement and into the car. In the debrief, producing the record is the point.
In the car, the absence of a record is what permits the candor, and a tool that captured the conversation would end it. The design problem becomes capturing the output without capturing the exchange that produced it.
This is what it means to fit snugly into a wedge. The ritual has a timing, a cast, a tone, a set of norms, and a product that violates them does not inherit the moment’s advantages but contaminates them. Fitting the ritual is the price of the adoption conditions above.
Where institutional judgment becomes visible
The moment is valuable for a second reason: it concentrates information that exists nowhere else in the institution.
Walk one compact loop. Several participants contribute perspectives on the same event, and those perspectives differ because each person saw the work from a different position. Their accounts become one structured record of what happened, in what order, and decided by whom. Here, rituals can do more than push institutional knowledge downward. They expose where it should change, because the debrief is one of the few moments when practice and doctrine are held against each other by people with the standing to say which is right.
Notice what accumulates in a single recurring moment: information hours old rather than quarters old, tacit knowledge nobody has written down, conflicting accounts whose conflict is itself the signal, the rules invoked as the standard of comparison, the exceptions surfaced and examined, and the authority to decide what follows.
A product living inside that moment captures something the institution has never held in durable form. The transcript is raw material; the asset is institutional memory, a connected record of what the organization actually does, how that differs from what it says it does, and how the gap gets resolved event after event.
No system built from forms and fields contains it, because the information surfaces only in the ritual and otherwise decays with turnover.
Expansion follows the consequences
The expansion path is unusually legible, because the ritual sits inside a web of dependencies the product can follow: improve the ritual, own its artifact, connect occurrences across time, then influence the systems before and after it.
Improving the ritual earns the place. Owning the artifact follows, because once the debrief produces its structured record through the product, the product is the system of record for that moment. Connecting occurrences is where compounding begins: one debrief is an anecdote, two hundred are a dataset about how the institution operates, where it deviates, and what those deviations cost or save. It is also where the product stops depending on the moment that admitted it, since the institution comes to depend on the artifact more than the product depends on the occasion. The ritual is the entry, not the permanent residence.
From there, follow what feeds the moment and what the moment feeds. Policy, training, staffing, plans, and prior incidents sit upstream, and the debrief exists to test the work against them. Assignments, retraining, policy changes, escalations, and performance records sit downstream, and the debrief exists to trigger them. Whoever owns the connected record holds the evidence those systems run on, and the larger company emerges one adjacency at a time, each justified by what the ritual produced.
This is a different logic from horizontality. A capability that could apply anywhere gives you a list of markets, each won from a standing start. A ritual gives you a chain of consequences that tells you what to build next, and every adjacency is one the customer already connects to the moment, which makes the expansion legible to the buyer as well as the builder.
Nor is the pattern confined to after-action review. A shift handoff opens onto operating history, staffing, and quality. An inspection opens onto the asset record, maintenance, and compliance. A financial close opens onto controls, planning, and finance operations. Each has its own trigger, cast, and artifact, and each sits inside its own web of dependencies waiting to be followed.
Recurrence alone is insufficient
The concept degrades if every repeated task gets called a ritual, so it is worth stating what qualifies. Would the moment still occur without the product? Is there a recognizable trigger, and are the participants and their roles understood? Would a new participant be absorbed into it without being told it exists? Is participation reinforced by policy, regulation, professional norms, or operational necessity? Does consequential information surface there, must something binding emerge, and does skipping the moment carry an identifiable cost? And what holds the moment in place would that thing survive better tooling?
The cleanest line between a ritual and a habit is transmission. A habit belongs to a person and dies with them, while a ritual belongs to a role that outlives whoever occupies it, so a replacement is absorbed into the moment rather than trained into it. This is why the standing status meeting is the instructive failure rather than the obvious one. It recurs and it has a cast, but nothing triggers it except the calendar, nothing binding emerges from it, and attendance is a courtesy; it disappears the week the manager who convened it leaves. The habit dies with its holder and the standing meeting dies with its convener. A ritual survives both, because nobody in particular is holding it up.
Rituals also differ in what holds them there, and the difference decides whether a wedge is buying a fixture or a countdown. Some moments are held by consequence: physics, liability, regulation, an asset that runs through the night whether or not anyone is watching. Better software does not repeal the reason those exist. Others exist only because coordination is currently expensive, like the reconciliation meeting that convenes because two systems cannot speak to each other, and those are workarounds wearing the costume of a ritual. They pass every other test right up until the constraint that produced them is removed, which makes this the failure mode worth guarding against: it is the one that looks most like success.
Formality, finally, is evidence of institutional reinforcement rather than the thing itself. The debrief that started this essay was informal, and no regulation required it, yet operational necessity produced it reliably, with understood roles and real consequences. What matters is that the institution, in some fashion, insists on the moment.
Calendared repetition tells you a product might get opened weekly. A ritual tells you the product sits where the institution concentrates its people, its information, its authority, and its risk.
Why Daring notices rituals
Much of our time goes to narrow wedges in institutional settings, and the recurring difficulty is judging which narrow things can become large. A wedge locked into a genuine ritual is a signal we weight heavily, because so much of what we look for is already concentrated in the moment: an adoption occasion supplied by the institution, identifiable users and roles, existing urgency, proprietary information that surfaces nowhere else, stakes high enough to have produced the ritual in the first place, and expansion paths running in both directions. Together they amount to venture-scale density, a small entry point already holding the ingredients of a much larger company.
A ritual is optional. Plenty of significant companies began with wedges that created new behavior outright, and we would not hold its absence against a founder. The concept earns its place as a diagnostic, a way of seeing why a narrow product is adoptable now and expansive later, when the same product described capability-first would look like a feature.
When a founder can point to the moment their product enters, name who is standing in it, and explain what record must come out of it, we pay closer attention.