A Brief Should Survive the Person Who Wrote It

Most projects begin with a sentence that is not ready to carry them.

It may be an idea typed quickly between two meetings. It may be a note written after seeing a problem clearly for the first time. It may be a request sent to an AI tool because the person wants to discover what the idea could become. The sentence is valuable because it starts movement, but it is rarely complete enough to guide everything that follows.

For a while, we treated that first sentence as if it were the project’s centre.

That made sense when the work happened inside one conversation. The person remembered the context. The AI had the recent exchange. The next question was close enough to the first one that the gaps did not matter.

OFM was becoming a place for longer, more distributed work. Projects could contain several sessions, several tools, several people-shaped decisions, and several returns. In that environment, the first message was too fragile. It belonged to a moment, and the project needed something that could survive the moment.

On June 10, we started thinking about the brief differently. A brief should not be a formality before the real work begins. It should be a durable expression of what the work is trying to accomplish, clear enough to guide future decisions and open enough to change when the project teaches us something new.

Most importantly, it should survive the person who wrote it.

The original message is full of invisible context

People are surprisingly good at understanding their own shorthand.

An idea that looks incomplete on the screen may feel perfectly clear to its author because it is attached to a conversation, a frustration, a deadline, or an image in their head. They know which detail matters. They know what not to say. They know that “make this simpler” refers to three previous attempts and a specific feeling about the result.

The project does not know those things automatically.

An AI tool sees the words available to it. A future collaborator sees the words that remain. The person who returns a week later may still remember the broad intention but forget why one direction was rejected. The first sentence carries meaning, but much of that meaning is private to the moment in which it was written.

That is why a raw prompt is a poor long-term project document. It is designed for exchange, not necessarily for orientation. It can be an excellent beginning and a weak foundation.

The distinction became more important as OFM supported people who move between projects. When the work is spread across a product idea, a content series, a client engagement, and a personal experiment, the cost of reconstructing invisible context grows quickly.

The brief became a way to make the important context visible without requiring the person to preserve the entire conversation.

A brief is not a contract with the future

There is another mistake on the opposite side.

If a brief is meant to last, it can become too formal. People may treat it as a contract that must be completed before any exploration is allowed. The document becomes polished, but the project becomes less curious.

That is not what we wanted.

A useful brief should be strong enough to orient the work and flexible enough to be corrected by the work. It should name the intended outcome, the audience or situation that gives the outcome meaning, and the decisions that will shape it. It should also leave room for uncertainty where uncertainty is real.

This matters because early projects often change. A creator discovers that the audience’s need is different from the initial assumption. A builder realizes that a smaller outcome would be more useful. A researcher finds that the original question contains two separate questions. A client project reveals a constraint that was invisible at the beginning.

If the brief cannot absorb learning, it becomes an obstacle. If it contains no direction, it becomes a record of vague enthusiasm.

The right brief is neither rigid nor empty. It is a working reference.

The choice was between capture and translation

We considered the simplest approach: save the original message and make it easy to find.

That would preserve the source. It would not necessarily preserve the meaning. A person returning to a long exchange would still have to identify the intention, separate decisions from experiments, and remember which parts were temporary.

The other approach was to turn the initial thought into a clearer brief. This offered more value, but also introduced interpretation. Any translation can put words in someone’s mouth or make uncertainty look settled.

The decision was to treat a brief as a proposal for orientation, not an authority.

It could make the goal clearer. It could gather the important parts of the idea. It could expose open questions. It could be revised by the person before becoming the reference that guides further work.

This is a subtle difference, but it protects agency. The product can help shape a thought without claiming ownership of the thought. The person remains responsible for accepting, correcting, or rejecting the direction.

That boundary is especially important when an AI assistant helps create the first version. The result should be useful because it gives the person something to work with, not because it is presented as an objective interpretation.

What a durable brief gives back

A good brief gives back time.

Not by eliminating thinking, but by preventing the same thinking from being performed repeatedly. Without a durable reference, each new session begins with a small reconstruction: what are we making, for whom, why now, and what are we not trying to do?

That reconstruction is often necessary once. It becomes wasteful when every tool and every return asks for it again.

A brief also gives back consistency. When several sessions approach the same project, the work has a stable centre. Different tools may contribute different strengths, but the project does not become a collection of unrelated requests. A person can change the direction deliberately rather than drifting because the latest conversation happened to be more vivid.

There is a quieter benefit too. A durable brief makes it easier to notice when the project has changed. If the current work no longer matches the original intention, that difference becomes visible. The brief does not only preserve the plan; it creates a reference point against which learning can be recognized.

That is one reason we did not want the brief hidden inside a conversation. It needed to be available as part of the project’s identity.

The brief has to remain readable to a human

AI systems can work with dense context. People still have to live with the project.

That means a brief must be readable when someone is tired, returning after a gap, or trying to make a quick decision. It should not require the person to remember the exact language of a previous interaction. It should use concrete words where possible and keep the distinction between fact, intention, assumption, and open question visible.

We became wary of documents that sounded complete because they used polished language. A brief can be elegant and still hide the decision that matters. It can contain all the expected sections and still fail to tell the next person what not to do.

The test is not whether the brief looks finished. The test is whether it helps someone make a better next choice.

That choice might be to continue. It might be to narrow the scope. It might be to ask for missing information. It might be to stop. A brief that supports only forward motion is not durable; it turns every uncertainty into pressure.

Why the author should not be the only reader

The phrase “survive its writer” is not only about collaboration.

It also describes the future self. The person who writes a brief today is not the same person who reads it after a difficult week. The future self has different priorities, less patience, and fewer details available from the original moment.

If the brief is written only to satisfy the present author, it may fail its most important audience. It should carry enough of the reasoning that a later version of the same person can understand the project without recreating the entire origin story.

This is particularly relevant to people creating in public or managing several independent projects. Ideas often begin with energy and continue through quieter maintenance. A project must remain legible after the initial excitement becomes routine.

The brief is a bridge between those two versions of the work: the idea as it was imagined and the project as it is now.

That bridge should not erase the distance between them. It should make the distance visible enough to cross deliberately.

The danger of asking the brief to do everything

Once a brief becomes useful, there is a temptation to make it the centre of every decision.

We resisted that impulse. A brief is a compass, not an autopilot. It cannot replace discovery, judgement, or conversation. It should not become a reason to reject a good idea merely because the idea was not present in the first version.

Projects need room to surprise their authors.

The durable part of a brief is not that every sentence remains true. It is that the project has a visible set of intentions and boundaries that can be revisited. When those change, the brief should be allowed to change with them. The record of the change can be valuable, but the old wording should not quietly govern the new work.

This is another reason to keep the document human-readable. People are better at noticing a meaningful change in direction when the reference is clear enough to compare with reality.

The goal is not to create a perfect specification. The goal is to keep the project from becoming a series of disconnected moments.

What this means for people using OFM

For someone using OFM, a brief can become the place where a project’s intention is easiest to recognize.

It can help when an idea is still forming, when several sessions need a shared direction, or when a person returns after enough time has passed for the original context to fade. It can also help when the project needs to be explained to another person without forwarding every conversation that came before.

The important point is that the brief remains editable and accountable to the person. It is not a hidden interpretation that silently controls the work. It is a visible reference that can be questioned.

That makes it useful for different kinds of advanced AI work. A creator can clarify the promise of a series. A builder can keep a product decision in view. A researcher can distinguish a question from a conclusion. Someone working with several tools can carry the same project intention between them.

The project becomes easier to re-enter because its purpose is not trapped in the first exchange.

The test we still apply

When we look at a brief now, we ask a simple question: could someone return to this project later and understand what deserves attention?

Not everything. Not every historical detail. Just enough to recover the thread.

We also ask whether the brief distinguishes what is known from what is hoped, what is decided from what is being explored, and what is explicitly outside the project’s scope. Those distinctions protect the work from a common AI failure: making an incomplete idea sound more certain than it is.

The brief should help the product move, but it should also help the person pause intelligently.

That is the standard we are still refining as OFM grows. Different projects will need different levels of detail. A short creative experiment should not require the same weight as a long-running product. The durable reference has to be proportional to the work it serves.

The brief is also a boundary

One of the most useful things a brief can preserve is what the project is not trying to do.

Beginnings are expansive. Every related idea can look like a possibility, and AI tools are very good at producing more possibilities. Without a boundary, the project can grow in every direction while still sounding productive. The work accumulates material but loses a reason for choosing one path over another.

A brief can protect the original intention by giving the project a limit. That limit is not a restriction imposed on creativity. It is a way to make creativity legible. When the scope is visible, a new idea can be welcomed as a deliberate expansion or declined as a distraction. The person no longer has to decide from a vague feeling that the project is becoming too large.

This is another reason the brief must remain editable. A boundary can change when the project teaches us something important. But the change should be seen. Otherwise the project quietly becomes something different while everyone continues to use the original language.

The durable brief gives that evolution a place to be acknowledged.

A project can outlive its first explanation

There is another reason this matters. A project rarely changes in the neat order in which it was first imagined. The first explanation may be written before the difficult trade-offs appear. A later session may reveal that an apparently central idea was only a temporary bridge. Another person may look at the work and see a possibility that was invisible at the beginning. If the brief is treated as a frozen statement, each new discovery becomes a contradiction. If it is treated as a living account of intent, the discovery becomes part of the story.

That distinction changes the emotional weight of returning. Opening an old project can feel like opening a message from a past version of yourself. Sometimes the message is useful. Sometimes it is embarrassingly certain. Sometimes it contains a question that was never answered because the day ended before the work did. A durable brief does not remove that distance, but it gives the present version of the person a fair way to meet the earlier one.

This is also why we are careful about what a brief should not become. It should not be a diary that records every hesitation. It should not be a performance of certainty written for an imagined audience. It should not become a second product to maintain, with its own elaborate rules and rituals. The value is in the small amount of context that prevents the project from becoming anonymous again.

For someone working across several projects, that small amount can be the difference between continuing and restarting. A client engagement, a personal experiment, and a content project may all require different kinds of attention. They do not need the same brief. They do need a clear enough beginning that the next session can answer a basic question: what was I trying to make possible here?

The answer may change. That is healthy. The brief gives the change somewhere to land.

We see this as one of the quieter design principles behind OFM. The product should help a person keep the meaning of work close enough to act on, without claiming that meaning is permanent or complete. That requires restraint. A system that records everything may look thorough while making the important parts harder to find. A system that records nothing leaves the person to reconstruct the past from fragments.

The useful middle is not a perfect summary. It is a point of re-entry.

When we revisit this feature, the question will not be whether the brief can contain more. It will be whether it helps the person make a better next decision. That is a harder measure than completeness, and it is more connected to the reason the project exists.

The writer begins the brief, but the future reader is part of its design.

On June 10, the insight was not that every project needs more documentation.

It was that projects need a place where their intention can survive the speed of their beginnings. The first message can remain important without remaining sufficient. The conversation can remain valuable without being the only record. The person can keep changing their mind without losing the ability to see what changed.

A durable brief creates that possibility.

It gives the project a centre that is clear enough to return to and flexible enough to grow. It respects the person who started the work, the person who may join later, and the future version of the author who will need a reminder rather than a transcript.

The brief also creates a more honest relationship with progress. A project can move forward while its central question becomes weaker. It can produce pages, files, and conversations without getting closer to the outcome that mattered. Returning to the brief makes it possible to notice that before activity becomes proof by itself.

This is especially important in AI-assisted work because activity can arrive very quickly. A person can generate alternatives, reorganize a thought, and produce a polished draft before deciding whether the direction is right. Speed is useful, but it can make an unresolved decision look like a completed task. A brief gives the project a slower reference point, one that asks whether the work still serves the intention behind it.

The reference should never become a justification for refusing to learn. If the project has changed, the brief should help explain why. If an assumption has failed, the brief should make the failure easier to name. If a new opportunity appears, the brief should make it possible to compare that opportunity with the original purpose instead of accepting it simply because it is new.

That is how a document can be durable without becoming rigid. Its value is not that it remains untouched. Its value is that changes to it become meaningful.

There is also a human benefit to writing this way. When the project is difficult, a clear brief can separate the quality of the idea from the mood of the day. A person may be tired, distracted, or temporarily unconvinced by work that still deserves attention. The brief does not make the decision for them, but it gives them something more stable than the feeling of the moment.

That does not mean the brief should judge every step. It should give the person a reference point from which judgement is possible. Sometimes the right conclusion is that the original goal was too small. Sometimes it is that the project needs to stop. A durable brief supports both conclusions because it preserves the intention rather than demanding a particular ending.

That is why a brief should survive its writer.

Not because the writer is replaceable.

Because the work deserves to remain understandable when the moment that created it has passed.