Book: The Girl I Haven't Met Yet

Download the PDF now!

Chapter 1

The Girl I Haven’t Met

I haven't met her yet.

At least, I don't think I have.

That's an important distinction.

There are billions of people in the world, thousands of people passing through a city every day, and hundreds of people a person might cross paths with without ever learning their names.

She could have walked past me already.

She could have stood behind me in a coffee shop.

We could have been on the same train.

Maybe I looked left when I should have looked right.

Maybe she did.

That's the problem I wanted to solve.

Not:

How do I force the universe to give me the girl of my dreams?

Something much more interesting:

How do I become exceptionally good at recognizing opportunities and doing the right thing when they appear?

I called my answer DNA.

Not because I thought I could speak English sentences to the molecules inside my cells and order them around.

DNA was simply the perfect name for my system.

Real DNA contains sequences. My system would contain sequences too.

Except mine would be made from words.

Short sequences.

Precise sequences.

Words designed to trigger something useful in my mind.

The idea started with an ordinary problem.

My glasses.

There are few things more ridiculous than searching everywhere for something you personally put somewhere.

Nobody stole them.

Nobody hid them.

I had performed the action myself.

Somewhere in my own memory was the answer.

So why couldn't I simply ask for it?

I stopped searching.

I stood still.

Then I said:

“Remember where my glasses always are. Mind!”

Nothing supernatural happened.

My glasses didn't fly across the room.

A mysterious voice didn't whisper their coordinates into my ear.

Instead, I pictured the places where I normally put them.

Table.

Desk.

Beside the bed.

Bathroom.

I mentally eliminated them one by one.

Then something surfaced.

I remembered taking them off earlier.

I went to look.

There they were.

That fascinated me.

The sentence hadn't magically located my glasses.

It had done something better.

It had given my mind a job.

Remember.

That was the beginning.

I started experimenting.

If one sequence could organize a memory search, what else could a sequence organize?

I tried:

“Keys. Last place. Replay. Mind!”

Instead of frantically checking pockets, I reconstructed the last few minutes in my head.

Another:

“What was I about to do? Previous thought. Mind!”

That was useful whenever I walked into another room and suddenly forgot why I was there.

Then:

“Problem. Options. Best one. Mind!”

That one wasn't about memory at all.

It was about decisions.

Soon I noticed that the words themselves weren't the most important part.

The structure was.

I was creating a tiny language for talking to myself deliberately.

I wrote down the basic formula:

TARGET → OPERATION → RESULT → MIND

The target identified what I was dealing with.

The operation told me what kind of thinking to perform.

The result described what I wanted from that thinking.

And MIND meant:

Do it now.

It was almost like having a command line for my attention.

But there was an obvious question.

If I could use this system to find my glasses, remember names, make decisions and overcome little obstacles...

Could I use it for something enormous?

I knew immediately what I wanted to test.

Her.

The girl of my dreams.

That presented a problem considerably more complicated than finding glasses.

Glasses are objects.

People aren't.

A woman has her own desires, plans, history, personality, attractions and decisions.

No word sequence could command another human being.

That became Rule One of DNA:

DNA controls my actions. Never hers.

That rule changed the entire project.

I wasn't going to create:

“Girl of my dreams. Find her. Mind!”

That was too vague anyway.

Instead, I needed to break an enormous objective into things I could actually influence.

Where do I go?

Who do I talk to?

What do I notice?

Do I remember people's names?

Can I recognize genuine interest?

Do I listen?

Do I approach when appropriate?

Can I tell the difference between attraction and compatibility?

Do I disappear into my own thoughts when I should be paying attention to the person standing directly in front of me?

Suddenly finding her didn't look like one impossible problem.

It looked like a thousand small ones.

And small problems were exactly what DNA was being built to handle.

I opened a notebook.

At the top of the first page I wrote:

OBJECTIVE: FIND HER

Then underneath:

Obstacle 1: I don't know who she is.

Obstacle 2: I don't know where she is.

Obstacle 3: I might encounter her and never realize it.

Obstacle 4: I might recognize her and fail to act.

Obstacle 5: I might act and say the wrong thing.

Obstacle 6: I might mistake the wrong person for the right person.

I stopped.

Number six bothered me.

It was easy to imagine building a system that made me more determined.

But determination isn't always intelligence.

Sometimes the smartest thing a person can do is abandon the wrong path.

So I wrote my first major safeguard:

“Evidence. Not imagination. Mind!”

I stared at it.

That might have been the most important sequence I'd invented.

If a woman wasn't interested, the system shouldn't help me invent reasons why she secretly was.

If we weren't compatible, the system shouldn't turn incompatibility into some obstacle I was supposed to conquer.

If something existed only in my imagination, DNA should push me back toward reality.

The system needed brakes as much as it needed an accelerator.

I added another:

“Her choice. Respect it. Mind!”

And another:

“Wrong path. Recalculate. Mind!”

Now I was getting somewhere.

Late that night I looked over the page.

There was something strange about seeing the objective written down.

FIND HER.

She had no name.

No face.

No address.

I didn't know what she was doing at that exact moment.

Maybe she was sleeping.

Maybe she was watching television.

Maybe she was laughing with somebody.

Maybe she was drinking coffee somewhere I'd never been.

Maybe she lived twenty minutes away.

Maybe twenty hours.

There was no sequence that could answer that.

And strangely, I liked that.

A system that already knew everything wouldn't be an adventure.

Mine had to work with uncertainty.

I drew a line underneath everything I'd written.

Then I wrote the principle that would govern the entire experiment:

I DON'T NEED TO KNOW THE WHOLE PATH.

I NEED TO GET THE NEXT MOVE RIGHT.

That was it.

DNA didn't need to tell me how the story ended.

It needed to help me with the next decision.

And then the next.

And the next.

Thousands of tiny corrections could produce a destination that no single brilliant decision ever could.

I closed the notebook.

Tomorrow I would begin building the vocabulary.

REMEMBER.

NOTICE.

SEARCH.

LISTEN.

COMPARE.

DECIDE.

ACT.

STOP.

RECALCULATE.

Nine operations.

Nine simple words.

Potentially thousands of sequences.

I didn't know whether the girl of my dreams was somewhere across the world or somewhere across the street.

But for the first time, that didn't seem like the question that mattered.

The question was:

If the opportunity appeared tomorrow, would I be ready to recognize it?

I looked at the notebook one last time.

Then I gave myself the first command of the real experiment.

“Tomorrow. Pay attention. Mind!”

And went to sleep.

5 points to remember

1. DNA uses words as instructions for yourself.

2. DNA controls your actions, never another person's.

3. Evidence must beat imagination.

4. Large goals can be broken into many small obstacles.

5. You don't need the whole path—you need the next move.

Chapter 2

The First Sequence

The next morning, I discovered the first problem with DNA.

It was too easy to invent commands.

I could write hundreds of them.

“Coffee. Make it. Mind!”

“Keys. Find them. Mind!”

“Get dressed. Mind!”

“Remember that thing I was supposed to remember. Mind!”

That last one made me laugh.

If DNA was going to become useful, it couldn't simply be ordinary thoughts with MIND! attached to the end.

There had to be a system.

I opened my notebook.

Yesterday I had written nine operations:

REMEMBER.

NOTICE.

SEARCH.

LISTEN.

COMPARE.

DECIDE.

ACT.

STOP.

RECALCULATE.

Today I added a rule.

RULE TWO: EVERY SEQUENCE MUST HAVE A JOB.

If I couldn't explain what a sequence was supposed to make me do differently, I didn't need it.

That immediately eliminated half my ideas.

Then I started with the easiest operation.

REMEMBER

I put my glasses on the table.

I looked directly at them.

Then I said:

“Glasses. Table. Remember. Mind!”

I walked away.

An hour later, I deliberately tried to remember where they were without looking.

“Glasses. Location. Remember. Mind!”

Table.

The image appeared immediately.

That gave me another idea.

Maybe there should actually be two kinds of memory commands.

One for putting information in.

Another for getting information out.

I wrote:

STORE

“Glasses. Table. Store. Mind!”

And:

RECALL

“Glasses. Location. Recall. Mind!”

Now DNA was becoming more precise.

STORE meant:

This matters. Pay attention while it is happening.

RECALL meant:

Search what I already know.

That distinction seemed small.

It wasn't.

A memory can't be retrieved very well if I never paid attention when it was being formed.

Maybe forgetting my glasses wasn't always a retrieval problem.

Maybe sometimes I hadn't properly noticed where I'd put them in the first place.

That gave me the first complete DNA pair:

“Glasses. Table. Store. Mind!”

Later:

“Glasses. Location. Recall. Mind!”

Input.

Output.

I circled both.

My first working sequence had become two.

Then I thought about her.

Not a particular woman.

Her.

Whoever she eventually turned out to be.

Suppose I met someone tomorrow.

What information would matter?

Her name, obviously.

Things she told me.

What she liked.

What she disliked.

Whether she seemed comfortable.

Whether I actually liked her personality instead of merely finding her attractive.

I imagined a conversation.

She tells me:

“My name is Anna.”

Old me might hear it, continue talking, and thirty seconds later think:

Was it Anna? Hannah?

DNA needed to catch information while it was fresh.

I wrote:

“Anna. Name. Store. Mind!”

Not spoken aloud in front of her, obviously.

That would be strange.

The sequences didn't always have to be verbal.

They could be internal.

A deliberate thought.

Anna → Name → Store.

Then if I encountered her again:

“Her. Name. Recall. Mind!”

Anna.

Simple.

But names were easy.

What about something meaningful?

Suppose she said:

“I paint.”

That could disappear into the enormous pile of information people hear every day.

Or I could deliberately register it.

“Anna. Painting. Store. Mind!”

Weeks later:

“How's your painting going?”

Now something interesting had happened.

DNA hadn't taught me a clever line.

It had helped me listen.

That was much more valuable.

I crossed out something I'd written yesterday:

FIND THE GIRL OF MY DREAMS.

Then rewrote it:

BECOME CAPABLE OF RECOGNIZING AND BUILDING A GREAT RELATIONSHIP.

That was different.

Finding someone was only the beginning.

NOTICE

My second experiment happened outside.

I decided to take a walk with one instruction:

“Environment. Differences. Notice. Mind!”

Then I paid attention.

Normally I moved through familiar places without really examining them.

Now I started seeing details.

A business I'd never noticed.

Someone walking a dog.

A poster.

A person laughing.

Someone looking irritated.

A couple talking.

A woman sitting alone.

Cars moving.

Doors opening.

People arriving.

People leaving.

Nothing extraordinary happened.

That was exactly what made the experiment interesting.

The environment hadn't changed.

My sampling of the environment had changed.

I wrote that sentence down as soon as I got home.

THE WORLD CAN CONTAIN AN OPPORTUNITY I DON'T NOTICE.

That applied to much more than relationships.

Jobs.

Friendships.

Ideas.

Information.

Problems.

Danger.

Beauty.

The unnoticed might as well not exist from my perspective.

So NOTICE became one of DNA's most important operations.

But I immediately saw a danger.

If I told myself:

“Girl of my dreams. Notice. Mind!”

I might start interpreting every coincidence as meaningful.

Someone glances at me?

Maybe it's her.

Someone smiles?

Maybe it's her.

Someone happens to be in the same place twice?

Maybe that's destiny.

No.

DNA needed protection against that.

I returned to yesterday's safeguard.

“Evidence. Not imagination. Mind!”

Then I expanded it.

DNA RULE THREE: NOTICE FIRST. INTERPRET SECOND.

Observation:

She smiled at me.

Interpretation:

She likes me.

Those were not the same statement.

Observation could be true while interpretation was wrong.

That distinction felt enormously important.

So I created:

“What happened? Facts. Mind!”

Then:

“What might it mean? Possibilities. Mind!”

Facts first.

Possibilities second.

I underlined that twice.

SEARCH

Searching was different from noticing.

NOTICE meant examining what was already around me.

SEARCH meant deliberately changing where I looked.

If I wanted to meet someone, sitting in the same chair every day wasn't much of a search strategy.

I wrote:

“Objective. New opportunities. Search. Mind!”

Then underneath:

Where could I go?

What could I try?

Who could I meet?

What routines could I vary?

The mathematics were obvious even without numbers.

If I repeatedly visited exactly the same places, at exactly the same times, around exactly the same people, I was sampling a narrow slice of the world.

Changing the sample changed what could happen.

I wrote:

DNA DOESN'T CONTROL CHANCE.

DNA CAN CHANGE HOW MANY CHANCES I ENCOUNTER.

Now the system was starting to feel powerful without needing anything supernatural.

LISTEN

This one bothered me.

I realized that listening was harder than hearing.

When another person speaks, part of my mind can already be constructing my response.

I'm hearing them while simultaneously thinking about me.

So I invented a brutally simple sequence:

“Her words. Understand first. Mind!”

Not:

What clever thing should I say next?

Understand first.

Then respond.

I imagined meeting her.

Maybe the woman of my dreams wouldn't arrive with dramatic music playing in the background.

Maybe she wouldn't instantly look extraordinary.

Maybe the thing that made her extraordinary would emerge twenty minutes into a conversation.

Or twenty days.

If I didn't listen, I might never discover it.

I wrote:

APPEARANCE GETS NOTICED QUICKLY.

CHARACTER TAKES TIME TO OBSERVE.

That became another principle.

By afternoon, my notebook was filling rapidly.

I stopped.

Too rapidly.

This was exactly the problem I'd anticipated that morning.

I didn't want 10,000 commands that I couldn't remember.

The system needed compression.

So I created a hierarchy.

DNA LEVEL 1 — OPERATIONS

STORE

RECALL

NOTICE

SEARCH

LISTEN

COMPARE

DECIDE

ACT

STOP

RECALCULATE

Ten words.

That was manageable.

Then:

DNA LEVEL 2 — TARGETS

The target could be almost anything.

Glasses.

Keys.

Name.

Conversation.

Opportunity.

Problem.

Decision.

Her.

Then:

DNA LEVEL 3 — MODIFIERS

Modifiers changed how the operation should happen.

Carefully.

Quickly.

Again.

Facts.

Options.

Last place.

Best evidence.

Suddenly I didn't need thousands of memorized sentences.

I could construct them.

Like language.

Keys + RECALL + Last place.

Problem + COMPARE + Options.

Environment + NOTICE + Carefully.

Conversation + LISTEN + Facts.

The vocabulary was small.

The combinations were enormous.

That was exactly what I wanted.

That evening I gave myself a test.

I put my glasses somewhere unusual.

I stopped.

Looked directly at them.

And thought:

“Glasses. Location. Store. Mind!”

Then I deliberately went about my evening.

Hours later I needed them.

For a fraction of a second, I started doing what I normally did.

Look around.

Check the table.

Check another table.

Then I stopped myself.

DNA.

“Glasses. Location. Recall. Mind!”

I closed my eyes.

Instead of searching the apartment, I searched backward through time.

What had I been doing?

Where was I standing?

What happened immediately afterward?

An image appeared.

I walked over.

There they were.

I smiled.

It was a tiny victory.

Almost embarrassingly tiny.

But that wasn't what interested me.

I had issued a sequence.

The sequence had triggered a procedure.

The procedure had produced an action.

The action had produced a result.

I opened the notebook again.

WORDS → PROCEDURE → ACTION → RESULT

That might be the real architecture of DNA.

Not words directly producing reality.

Words activating procedures that changed what I did inside reality.

And if that worked for something as insignificant as glasses...

What happened when hundreds of these procedures worked together toward one enormous objective?

I turned to a fresh page.

At the top I wrote:

PROJECT: HER

Then:

Phase 1: Become ready.

Phase 2: Expand the search.

Phase 3: Recognize opportunities.

Phase 4: Make contact.

Phase 5: Learn who she actually is.

Phase 6: Let her learn who I actually am.

Phase 7: Determine compatibility.

Phase 8: Build something together—or respectfully walk away.

I stared at the final words.

Walk away.

I didn't particularly like that part.

But DNA wasn't supposed to tell me what I wanted to hear.

It was supposed to help me navigate with reality.

Then another thought occurred to me.

There was an operation missing.

Something that might be more important than SEARCH, ACT, or even DECIDE.

I added an eleventh word.

VERIFY

Don't merely remember.

Don't merely notice.

Don't merely interpret.

Check.

The command became:

“Conclusion. Evidence. Verify. Mind!”

I circled it.

Someday, I suspected, that command was going to save me from making a very large mistake.

I just didn't know what the mistake would be yet.

And somewhere in the same city, perhaps, a woman I'd never met was going about an entirely ordinary evening.

She didn't know about the notebook.

She didn't know about DNA.

She certainly didn't know I was looking for her.

That was fine.

My job wasn't to control her story.

My job was to become better at writing mine.

Before going to sleep, I read the eleven operations once more:

STORE.

RECALL.

NOTICE.

SEARCH.

LISTEN.

COMPARE.

DECIDE.

ACT.

STOP.

RECALCULATE.

VERIFY.

Then I closed the notebook.

Tomorrow I would test the dangerous one.

ACT.

Because remembering where my glasses were was easy.

Walking up to someone I'd never met and saying hello?

That was going to require a different kind of sequence.

5 points to remember

1. Every sequence must have a job.

2. STORE puts information in; RECALL helps retrieve it.

3. NOTICE first; interpret second.

4. A small vocabulary can create enormous combinations.

5. Words work by triggering procedures that lead to actions and results.

Chapter 3

Words Without a Voice

Something about my system was wrong.

It took me a while to see it.

I had spent two days filling a notebook with words:

REMEMBER.

NOTICE.

SEARCH.

LISTEN.

COMPARE.

DECIDE.

ACT.

The words weren't the problem.

The problem was how I imagined them working.

I had accidentally created something that sounded like a conversation.

I would give DNA an instruction.

DNA would somehow process it.

Then, in my imagination at least, something would answer.

But that wasn't what I wanted.

DNA didn't talk to me.

There was no voice.

There was no little person inside my head waiting for instructions.

There was no:

Wendell, turn left.

No:

She's over there.

No:

Here's what you should say.

Nothing talked back.

And suddenly I realized something.

Nothing needed to.

I opened my notebook and crossed out an entire page.

Then I wrote:

DNA DOESN'T TALK.

Underneath it:

DNA DOES.

I stared at those three words.

That was closer.

Much closer.

I thought about my glasses again.

My original sequence had been:

“Remember where my glasses always are.”

What did I actually want from that?

I didn't want an imaginary voice saying:

Your glasses are on the table.

I wanted the remembering itself.

The output wasn't supposed to be another sentence.

The output was supposed to be a capability.

So I drew a new diagram:

WORDS → DNA → CAPABILITY → RESULT

I tried it with the glasses.

“Remember where my glasses always are.”

Then nothing.

No conversation.

No waiting for an answer.

Just the sequence.

And then I tried to remember.

An image came to mind.

The table.

I looked.

There they were.

That was it.

The sequence hadn't answered me.

I had remembered.

That difference changed everything.

I started looking at the rest of my vocabulary.

Maybe I didn't need commands that sounded like computer instructions.

Maybe I needed sequences that represented things I wanted to become capable of doing.

I wrote:

Remember where.

Recognize.

Find a way.

Notice.

Know the difference.

Get past.

Keep going.

Stop.

Choose.

Those felt different.

Less like orders.

More like keys.

A key doesn't explain how a lock works.

It doesn't talk to the lock.

You put the key in.

Something complicated happens inside.

The door opens.

That metaphor stayed with me.

THE WORD IS THE KEY.

THE CAPABILITY IS THE DOOR OPENING.

I circled it.

Then another possibility occurred to me.

Maybe sequences could become shorter.

Much shorter.

Suppose I repeatedly used:

“Remember where my glasses always are.”

Hundreds of times.

Eventually, maybe I wouldn't need the entire sentence.

Perhaps:

“Glasses. Remember where.”

Then:

“Glasses. Where.”

Maybe eventually just:

“Glasses.”

The word itself could become associated with the entire procedure.

Not because the word contained some magical power.

Because everything I'd repeatedly connected to that word could begin arriving with it.

That idea was enormous.

I turned to a fresh page.

COMPRESSION

Imagine learning to drive.

At first, a beginner might consciously think about mirrors, pedals, steering, speed, lanes, signs, distance and dozens of other things.

Eventually much of it becomes coordinated without consciously describing every movement.

The capability becomes compressed.

Or typing.

At first:

Where is the letter T?

Later, the fingers simply move.

Or walking.

Nobody wakes up thinking:

Contract this muscle.

Shift weight.

Move left leg.

Maintain balance.

Move right leg.

You think:

Go.

And an astonishing amount happens underneath that simple intention.

That was what interested me.

A tiny conscious input could sit above an enormous amount of complexity.

I wrote:

SMALL INPUT.

LARGE CAPABILITY.

Now I knew where I wanted DNA to go.

Not toward longer and longer instructions.

Toward shorter ones.

Then I remembered the real objective.

Her.

The girl I hadn't met.

I turned back to the page labeled:

PROJECT: HER

I'd originally imagined finding her as one gigantic task.

That suddenly seemed ridiculous.

If I wanted to get from one side of a city to the other, I didn't leap the entire distance.

I crossed one piece at a time.

Finding the right woman might work the same way.

So I wrote:

WHAT IS ACTUALLY IN MY WAY?

I started listing obstacles.

I don't know who she is.

I don't know where she is.

I might go to the wrong places.

I might walk directly past her.

I might notice her but not recognize an opportunity.

I might recognize the opportunity but hesitate.

I might speak but fail to listen.

I might forget something important she tells me.

I might misunderstand friendliness as attraction.

I might be attracted to someone completely wrong for me.

She might not be interested in me.

I might become so focused on finding “her” that I stop seeing women as individual people.

That last one made me stop writing.

It was important.

There was no reason the girl of my dreams had to fit a picture I'd invented before meeting her.

Maybe I was wrong about what I was looking for.

Maybe she would surprise me.

DNA needed to help me see reality more clearly, not force reality to resemble my expectations.

So I wrote another permanent rule:

THE SYSTEM MUST BE ABLE TO SURPRISE ME.

If I already knew every answer, I wasn't searching.

I was confirming.

Those were different things.

Now the obstacle list looked interesting.

Because I didn't have to solve all of it at once.

Take this:

I might walk directly past her.

What capability would help?

Notice.

Next:

I might hesitate.

What capability?

Move.

Next:

I might forget what she tells me.

Remember.

Next:

I might misunderstand her.

Observe.

Next:

I might convince myself she's interested when she isn't.

That needed something stronger.

I thought for a while.

Then wrote:

Reality.

One word.

Reality meant:

What actually happened?

Not what I hoped happened.

Not what I feared happened.

Not what I could creatively interpret.

What actually happened?

That word deserved a box around it.

REALITY

If she wanted to talk to me, wonderful.

If she didn't, reality.

If we got along, wonderful.

If we didn't, reality.

If I thought she was extraordinary but she thought I was simply some guy she met once?

Reality.

DNA wasn't going to manufacture somebody else's feelings.

My system ended where another person's freedom began.

That wasn't a weakness.

It was part of the design.

Then I noticed something about my obstacle list.

Nearly every obstacle could be paired with a capability.

Don't know where → SEARCH

Might miss → NOTICE

Can't remember → REMEMBER

Uncertain → COMPARE

Hesitation → MOVE

Confusion → CLARIFY

Wrong assumption → REALITY

Wrong direction → CHANGE

Failure → LEARN

Success → CONTINUE

Now I was excited.

This was no longer a collection of inspirational phrases.

It was becoming an obstacle system.

Something gets in the way.

Identify it.

Find the capability needed to get beyond it.

Associate words with that capability.

Use them.

Repeat.

Compress.

Move forward.

I wrote the entire mechanism as one line:

OBSTACLE → WORD → CAPABILITY → PAST THE OBSTACLE

That was DNA.

At least, that was DNA as I currently understood it.

I decided to test the idea on something completely unrelated to women.

I had something I'd been putting off.

Nothing dramatic.

Just one of those irritating little tasks that becomes larger every day precisely because you keep not doing it.

Normally I'd think:

I'll do it later.

Today I tried one word.

“Start.”

Then I started.

That was all.

I didn't wait to feel motivated.

I didn't negotiate with myself.

I didn't ask DNA what to do.

The word represented the capability.

START.

So I began.

Five minutes later I was already doing the thing I'd avoided for days.

I laughed.

Not because I'd discovered some supernatural secret.

Because I'd made something unnecessarily complicated.

Sometimes the obstacle wasn't enormous.

Sometimes I simply hadn't begun.

I wrote:

Obstacle: inertia.

Sequence: START.

Then:

Result: movement.

That was my first one-word sequence.

The rest of the afternoon became an experiment.

Whenever something interfered with what I was trying to do, I tried to identify the obstacle before reacting to it.

Couldn't remember?

Remember.

Distracted?

Focus.

Uncertain?

Check.

Avoiding?

Start.

Wrong?

Change.

Frustrated?

Continue.

But I noticed something else.

The same word could mean more over time.

Continue didn't merely mean keep physically moving.

It could eventually contain:

Don't abandon something useful merely because it became difficult.

That was much larger.

One word could become a container.

Every experience associated with it could add something.

A sequence might begin as a sentence.

Then become a phrase.

Then perhaps a word.

The complexity wouldn't necessarily disappear.

It would move underneath.

I wrote:

THE GOAL ISN'T TO MAKE THE CAPABILITY SIMPLE.

THE GOAL IS TO MAKE ACCESS TO IT SIMPLE.

I sat looking at that sentence for a long time.

That might have been the entire system.

Then my imagination went somewhere strange.

Suppose a person developed a capability so complicated that explaining it required a thousand pages.

What would happen after enough practice?

Would the conscious trigger still need to contain a thousand pages?

Probably not.

A pianist doesn't consciously recite a music theory textbook before touching a piano.

An athlete doesn't describe every movement before moving.

Expertise can become accessible through surprisingly small intentions.

So how far could compression go?

I wrote a deliberately ridiculous example.

UP.

What could up eventually mean?

Stand?

Climb?

Jump?

Rise?

What if an unimaginably complicated capability were associated with it?

Could a single word eventually sit on top of thousands of learned steps?

I didn't know.

And I wasn't going to pretend I knew.

But now I had something worth investigating.

The word wasn't the ability.

The word was access.

That distinction mattered.

That evening I returned to the girl.

I crossed out:

FIND HER

Again.

This time I replaced it with:

GET PAST THE NEXT REAL OBSTACLE.

Maybe that was enough.

I didn't need DNA to somehow know where the story ended.

I didn't need it to whisper directions.

I didn't need a voice at all.

If there were one thousand obstacles between my present life and the life I wanted, then perhaps I needed one thousand solutions.

Or perhaps I needed one hundred.

Or ten.

Or maybe, eventually, a surprisingly small vocabulary could unlock combinations of capabilities far larger than the vocabulary itself.

I looked at the words I'd collected:

REMEMBER.

NOTICE.

SEARCH.

FOCUS.

START.

MOVE.

OBSERVE.

CLARIFY.

REALITY.

CHANGE.

LEARN.

CONTINUE.

Twelve words.

I wondered how far twelve words could take a person.

Then I thought of her again.

Somewhere out there was a woman living a life completely independent of mine.

I didn't know her name.

I didn't know what she looked like.

I didn't know whether we'd ever meet.

And DNA didn't know either.

DNA wasn't going to tell me.

That wasn't its job.

Its job began when something stood between me and what I was trying to accomplish.

An obstacle.

A word.

A capability.

Then forward.

I closed the notebook.

For the first time since I'd started the experiment, I didn't say anything to myself before going to sleep.

There was nothing to ask.

Nothing waiting to answer.

Just a system waiting to be used.

And tomorrow, I was going to find out what happened when the obstacle wasn't an object, a forgotten memory or an unfinished task.

Tomorrow the obstacle would be me.

5 points to remember

1. DNA doesn't talk—it does.

2. The output should be a capability, not another sentence.

3. The word is a key; the capability is what the key accesses.

4. Obstacles should determine which capability is needed.

5. REALITY protects the system from wishful thinking.

Chapter 4

One Word Can Hold a Thousand Steps

The obstacle was me.

I'd written that sentence the night before.

By morning, I knew exactly what I meant.

There were things I knew how to do that I still didn't do.

There were opportunities I could recognize and still ignore.

There were moments when I knew the sensible decision and somehow found myself doing something else.

Knowledge wasn't enough.

That created a problem for DNA.

If a word sequence merely reminded me of something I already knew, the system wasn't nearly as powerful as I'd imagined.

I wanted something deeper.

I wanted a word to become associated with an entire practiced capability.

That brought me back to the strangest word in my notebook.

UP.

One word.

Two letters.

Almost nothing.

Yet the word could mean an enormous number of things.

Look up.

Stand up.

Get up.

Move up.

Climb up.

Lift something up.

Wake up.

Cheer up.

Speed up.

The word itself didn't contain instructions for any of those things.

Context supplied the difference.

Capability supplied the rest.

That fascinated me.

So I wrote:

UP

Then underneath:

How much can one word eventually represent?

I decided to find out.

I started with something ridiculously easy.

Standing.

I was sitting in a chair.

I thought:

Up.

(My legs felt propelled to get me on my feet..but I still sat.)

What had actually happened?

A tremendous amount.

My body shifted forward.

My feet positioned themselves.

My balance changed.

Muscles contracted in a particular order.

My center of gravity moved.

My knees straightened.

My spine adjusted.

My head remained balanced.

My eyes continued processing the room.

Within seconds I was standing.

Yet consciously, I hadn't issued hundreds of instructions.

I hadn't thought:

Activate muscle number one.

Now muscle number two.

Shift body weight fourteen centimeters.

Correct balance.

Straighten left knee.

Straighten right knee.

I had simply intended to get up.

My body already possessed the capability.

The conscious thought didn't contain the procedure.

It accessed the procedure.

That was the distinction I'd been searching for.

I wrote:

A WORD DOESN'T HAVE TO CONTAIN THE STEPS.

IT CAN POINT TO A CAPABILITY THAT CONTAINS THE STEPS.

Now DNA looked completely different.

I thought about tying shoes.

Try explaining every movement required to tie a shoelace to someone who has never done it.

Which finger holds which lace?

How much tension?

Which lace crosses first?

Where does the loop form?

How do your fingers exchange positions?

Exactly when do you pull?

Written precisely enough, something that takes seconds could require pages of description.

Yet an experienced person thinks:

Tie my shoes.

And does it.

Complexity underneath.

Simplicity on top.

I drew an iceberg.

Above the water:

WORD

Below the water:

Memory

Practice

Coordination

Recognition

Timing

Correction

Experience

Thousands of tiny operations

That was what I meant by compression.

Not deleting complexity.

Putting simple access on top of complexity.

Then I wondered whether DNA could deliberately build that relationship.

Suppose I wanted FOCUS to become more than an inspirational word.

Every time I used it, I could perform the same routine.

Remove distraction.

Identify one target.

Ignore unrelated information.

Work for a period of time.

Return attention when it wandered.

At first, FOCUS might require me to consciously remember all five steps.

But after enough repetitions, perhaps the word itself would increasingly cue the routine.

So I tested it.

I picked something to read.

My phone was beside me.

Television was available.

My attention had plenty of exits.

I thought:

Focus.

Then deliberately performed the procedure.

Phone away.

One target.

Read.

Attention wandered.

Return.

Again.

Attention wandered.

Return.

Again.

The word hadn't magically given me concentration.

I was training an association between the word and the procedure.

That was much more interesting.

Because tomorrow I could repeat it.

And the next day.

And the next.

Maybe eventually FOCUS wouldn't mean:

Try harder.

It would mean an entire learned pattern.

That gave me a new formula:

WORD + REPEATED PROCEDURE = ACCESS POINT

And with enough practice:

ACCESS POINT → CAPABILITY

I circled that.

Then I made a mistake.

I started imagining unlimited possibilities.

If FOCUS could represent five steps, why couldn't a word represent fifty?

If fifty, why not five hundred?

If five hundred, why not five thousand?

My imagination jumped immediately to the extreme.

Could:

UP

eventually mean something incredible?

Could a person attach such an enormous capability to one tiny word that thinking UP produced something that once seemed impossible?

I stopped myself.

There was a missing piece.

A word could provide access only to capabilities that had somehow been built.

Calling something UP didn't create it.

I couldn't associate UP with playing a piano concerto if I'd never learned piano.

I couldn't associate UP with speaking Japanese if I didn't know Japanese.

I couldn't associate UP with flying through the air simply because I wanted to fly.

The word wasn't magic.

Compression couldn't manufacture missing ability.

I wrote the limitation in enormous letters:

YOU CAN COMPRESS WHAT YOU HAVE BUILT.

YOU CANNOT COMPRESS WHAT DOESN'T EXIST.

That rule saved DNA.

Without it, the system could become fantasy.

With it, the system became a method for building and accessing real capabilities.

Then I thought about experts.

A beginner sees complexity everywhere.

An expert often sees patterns.

A beginner chess player sees individual pieces.

A strong player can recognize familiar structures.

A beginner musician thinks about individual notes.

An experienced musician recognizes phrases and patterns.

A beginner cook follows every instruction.

An experienced cook can look at ingredients and already understand much of what can happen next.

Experience compresses information.

Patterns replace isolated pieces.

I wondered whether words could become names for those compressed patterns.

That gave DNA three stages.

STAGE ONE — BUILD

Learn the actual capability.

STAGE TWO — ASSOCIATE

Repeatedly connect a word or sequence with performing it correctly.

STAGE THREE — COMPRESS

Allow the word to become a convenient access point for the practiced procedure.

That was cleaner than anything I'd written so far.

Then I added a fourth stage.

STAGE FOUR — TEST

Because believing a word works isn't enough.

Use it.

Observe what happens.

If performance doesn't improve, change the procedure.

DNA had to survive contact with reality.

I tested another word.

REMEMBER.

Instead of simply thinking it and hoping information appeared, I built a procedure underneath it.

Stop.

Identify what I'm trying to remember.

Reconstruct the context.

Think backward.

Picture the environment.

Recall what happened immediately before and after.

Wait a moment instead of panicking.

Then check.

Now REMEMBER had machinery underneath it.

The next time I used the word, I performed the machinery again.

And again.

Eventually, I hoped, I wouldn't need to consciously enumerate every step.

The word would be enough to begin the pattern.

That was DNA.

And then, inevitably, I thought about her.

What words would matter when I finally met someone extraordinary?

NOTICE.

That could contain:

Look beyond appearance.

Notice how she treats people.

Notice whether conversation flows both ways.

Notice whether she asks questions.

Notice whether I feel comfortable being myself.

Notice whether she seems comfortable being herself.

Notice whether our values fit.

Notice whether her actions match her words.

One word.

Many observations.

Then:

LISTEN.

That could contain:

Don't prepare my next sentence while she's speaking.

Hear the actual words.

Notice what matters to her.

Remember important details.

Ask when I don't understand.

Don't assume.

Let silence exist.

One word.

An entire social capability.

Then:

REALITY.

That one was becoming enormous.

It could contain:

Don't turn friendliness into attraction.

Don't turn attraction into compatibility.

Don't turn compatibility into destiny.

Don't invent signals.

Don't ignore clear signals either.

Look at behavior.

Respect her answer.

Respect uncertainty.

Be willing to be wrong.

One word.

A safeguard against an entire category of mistakes.

I stared at it.

Maybe the most important words wouldn't be the ones that moved me forward.

Maybe some would prevent me from moving forward in the wrong direction.

I created a page titled:

HER VOCABULARY

Not words for controlling her.

Words for controlling what I brought to the encounter.

NOTICE

LISTEN

REMEMBER

COURAGE

RESPECT

REALITY

CLARIFY

PATIENCE

MOVE

STOP

LEARN

CONTINUE

Then I added:

MYSELF

That one surprised me.

What would MYSELF mean?

Don't perform.

Don't manufacture some personality because I think she'll like it.

Don't pretend to enjoy things I hate.

Don't agree with everything.

Don't hide every imperfection.

Let her meet the actual person she'd potentially be choosing.

Otherwise, even success would be failure.

If she fell for a character I'd invented, she hadn't found me.

So MYSELF became another compressed sequence.

It represented authenticity.

One word.

A thousand little decisions.

Then I saw something I'd missed from the beginning.

I had been thinking about the girl of my dreams as the destination.

But there were actually two people moving through this story.

Me.

And her.

I could improve my side.

She controlled hers.

Maybe we'd meet.

Maybe we'd like each other.

Maybe one of us wouldn't.

Maybe we'd both feel something immediately.

Maybe it would take months.

Maybe I'd meet someone I was absolutely convinced was right and discover I was wrong.

DNA couldn't guarantee the ending.

It could improve how I traveled toward it.

That was enough.

I wrote:

THE SYSTEM DOESN'T GUARANTEE THE DESTINATION.

IT IMPROVES THE TRAVELER.

That sentence felt important enough to leave alone.

Later that evening I looked at UP again.

I'd originally chosen it because it was absurdly small.

Now it represented something much larger to me.

Not flying.

Not magic.

Not impossible abilities.

It represented the principle itself:

A small input can access a large practiced capability.

So I gave UP its first official meaning inside DNA.

UP = ACCESS WHAT HAS ALREADY BEEN BUILT.

It wasn't meant to replace every other word.

It was proof of concept.

A reminder that conscious language didn't need to reproduce every operation underneath a capability.

I looked at the entire notebook.

Hundreds of sentences had already begun shrinking.

What once took a paragraph could become a phrase.

What took a phrase could become a word.

But only after the meaning underneath it had been constructed.

That gave me one final rule for the day:

NEVER COMPRESS TOO EARLY.

First understand.

Then practice.

Then associate.

Then compress.

Otherwise the word was empty.

Before bed I imagined a future version of myself.

Maybe months from now.

Maybe years.

A difficult situation appears.

Old me might need fifteen minutes to think through it.

Future me recognizes the pattern.

One word comes to mind.

Not because the word contains the answer.

Because behind that word sits everything I've learned about that kind of problem.

Thousands of experiences.

Corrections.

Mistakes.

Successes.

Knowledge.

All compressed into accessible structure.

That was the version of DNA I wanted.

And if I became good enough at building those structures, perhaps the obstacles between me and the girl I hadn't met wouldn't look like one enormous wall anymore.

They'd look like individual problems.

One at a time.

Notice.

Remember.

Reality.

Courage.

Move.

Stop.

Change.

Continue.

Each word opening something larger underneath it.

I closed the notebook.

Then something happened that I hadn't planned.

I thought about tomorrow.

Going outside.

People everywhere.

Possibilities everywhere.

And for the first time since beginning Project Her, I felt nervous.

Not imaginary nervousness.

Real nervousness.

Because eventually I had to stop designing a system for meeting people...

and actually meet people.

I knew exactly which word belonged to that obstacle.

I wrote it at the top of tomorrow's page.

COURAGE

Underneath it I wrote:

A word is useless if I never build what's supposed to be behind it.

Tomorrow I would start building it.

5 points to remember

1. A word doesn't contain all the steps; it can point to them.

2. Complexity can exist underneath a very simple conscious trigger.

3. BUILD → ASSOCIATE → COMPRESS → TEST.

4. You can compress what you've built; you cannot compress an ability that doesn't exist.

5. Never compress too early.

This is why UP becomes so important. It represents the possibility that a tiny conscious input can sit above a much larger learned procedure.

Chapter 5 — Almost

Opening scene: “UP”

Wendell is sitting in the same chair.

He doesn't deliberately decide to stand and then use UP as a label for the decision. This time he tries the experiment differently.

He remains relaxed and says only:

“Up.”

Something happens.

His body doesn't stand.

But he almost stands.

Maybe his weight shifts forward. His legs prepare. His torso moves slightly. There is the unmistakable beginning of the familiar action—and then it stops.

That distinction becomes the entire chapter:

I didn't stand up. I almost stood up.

The mystery of “almost”

Instead of dismissing the failed movement, Wendell becomes fascinated by it.

Why did anything happen?

He writes three possibilities:

Word → thought of standing → beginning of movement

Word → learned association → beginning of movement

Word → DNA system → beginning of movement

He cannot yet distinguish between them.

That's important to the story. He doesn't declare victory after one experiment.

Instead:

Almost wasn't proof of my explanation. But almost was something I could investigate.

Repeating the experiment

Now he tries UP repeatedly under different circumstances.

Sometimes nothing happens.

Sometimes he feels the preparation to move.

Sometimes he leans forward.

Once his muscles engage strongly enough that he thinks he's about to rise—but he remains seated.

This gives him a new measurement system:

0 — Nothing

1 — Thought of movement

2 — Preparation

3 — Partial movement

4 — Almost

5 — Complete action

Now DNA isn't simply WORKED / DIDN'T WORK.

He can measure progress.

The major discovery: partial outputs

Until now, Wendell assumed a sequence should either produce its capability or fail.

UP → stand

But perhaps capabilities can emerge in pieces.

He writes:

A sequence doesn't necessarily cross the entire distance at once.

And underneath:

INPUT → PARTIAL CAPABILITY → PRACTICE → STRONGER ASSOCIATION

That becomes his new working theory.

Connecting it to Project Her

Then Wendell realizes “almost” describes many obstacles between him and the girl of his dreams.

He almost notices someone.

Almost says hello.

Almost remembers her name.

Almost asks the important question.

Almost recognizes that someone isn't right for him.

Almost has enough courage.

Instead of treating those moments as complete failures, DNA treats them as partial outputs that can potentially be strengthened through practice.

COURAGE gets redesigned

This changes Chapter 4's proposed direction.

Wendell tries:

“Courage.”

He doesn't suddenly become fearless.

Instead, maybe he gets 5% closer to acting.

That's enough to interest him.

So courage becomes something he can build in increments:

COURAGE 1: Look up.

COURAGE 2: Don't look away.

COURAGE 3: Smile.

COURAGE 4: Say hello.

COURAGE 5: Start a conversation.

Eventually those separate abilities might compress underneath:

COURAGE.

The critical safeguard

Wendell also realizes that wanting something to happen can make him believe a tiny movement means more than it does.

So he creates a rule:

Never turn ALMOST into DID.

If UP produces a slight forward movement, record a slight forward movement.

Don't write:

“UP made me stand.”

Write:

“I said UP. I shifted forward. I remained seated.”

That keeps his experiment grounded while allowing the mystery to remain.

The chapter-ending breakthrough

Near the end, he tries UP again.

He says it.

His body prepares.

He moves forward.

For an instant he is right at the boundary—

but doesn't quite stand.

This time Wendell smiles instead of being disappointed.

He opens the notebook and writes:

ALMOST COUNTS.

Then pauses and corrects himself:

ALMOST COUNTS AS ALMOST.

Underneath:

Don't exaggerate it.

Don't dismiss it.

Build from it.

And then the relationship connection:

Somewhere between me and the girl of my dreams were probably hundreds of almosts.

Almost noticing.

Almost remembering.

Almost understanding.

Almost acting.

Almost getting past the obstacle.

Maybe I didn't need every word sequence to work completely on the first try.

Maybe I needed to learn how to turn almost into a little more.

For the first time, I wasn't trying to make UP mean stand. I was trying to discover what stood between UP and standing.

5 points to remember

1. Almost is different from success and different from failure.

2. Measure what actually happened.

3. Capabilities may develop incrementally.

4. Small pieces of COURAGE can be trained before the whole capability is compressed.

5. Never turn ALMOST into DID.

Chapter 6

The Distance Between a Word and an Action

I said it again.

“Up.”

My body moved.

Barely.

There was a shift forward.

A preparation.

Something that felt like the beginning of standing.

Then it disappeared.

I remained in the chair.

Yesterday, that would have frustrated me.

Today, I was interested in the distance.

There couldn't have been much of it.

I knew how to stand.

I'd stood thousands upon thousands of times.

My legs worked.

My balance worked.

The movement was completely familiar.

And yet:

UP

had gotten me only partway there.

I opened the notebook.

At the top of the page was yesterday's question:

WHAT STANDS BETWEEN UP AND STANDING?

I started underneath.

Understanding the word?

Obviously I understood it.

Knowing what standing is?

Obviously.

Knowing how to stand?

Yes.

Physical capability?

Yes.

Beginning the movement?

Sometimes.

Completing it?

No.

That was strange.

The capability already existed.

The word already existed.

The association between them existed at least in the ordinary sense.

But something was missing.

I drew:

UP → ? → STAND

The question mark became the most interesting thing in my notebook.

I needed to understand exactly what almost consisted of.

So I stopped experimenting for a moment and simply stood normally.

No special word.

No DNA.

I decided to stand.

My body rose.

I sat down.

Did it again.

Sat down.

Again.

This time I paid attention.

Before I actually rose, several things happened.

My attention shifted.

My intention formed.

My torso moved.

My weight changed.

My legs prepared.

Pressure moved through my feet.

Then came the upward movement.

Balance adjusted continuously.

Finally:

Standing.

What normally felt like one action was actually a sequence.

I wrote:

1. Orientation

2. Intention

3. Preparation

4. Weight shift

5. Initiation

6. Rising

7. Balance

8. Completion

Then I stared at the list.

Eight stages.

Probably there were really hundreds.

Maybe thousands if I described everything happening in muscles, nerves and the brain.

But eight was enough for my experiment.

Now I could ask a better question.

When I said UP, how far through the sequence did I get?

I sat down.

Relaxed.

Waited.

“Up.”

Something.

Attention.

Preparation.

Slight forward movement.

Stop.

I marked:

1 ✓

2 ?

3 ✓

4 partial

5–8 no

Interesting.

Again.

“Up.”

This time almost nothing.

I wrote it down.

Again.

A stronger forward shift.

Still seated.

Wrote it down.

Again.

Nothing.

Again.

Preparation.

Again.

A twitch of movement.

Again.

Nothing worth mentioning.

My results were inconsistent.

That bothered me.

But inconsistency was information too.

If DNA worked like a mechanical switch, I would expect:

UP → STAND

every time.

That wasn't happening.

So whatever I was observing, I couldn't pretend I had discovered a reliable automatic command.

I wrote:

RESULT: INTERESTING, NOT PROVEN.

Then:

NEVER MAKE THE RESULT BIGGER THAN THE RESULT.

That rule was becoming increasingly important.

But another question appeared.

What if UP was too far away from the completed capability?

Maybe I was trying to compress too much, too quickly.

In Chapter 4 of my notebook, I'd written:

Never compress too early.

Maybe I'd violated my own rule.

I had taken an entire familiar action and tried to place it underneath a single word without deliberately building the connection.

So I tried something different.

Instead of training:

UP → STAND

I trained:

UP → BEGIN

That was smaller.

I sat.

Said:

“Up.”

Then deliberately performed only the beginning of standing.

Lean forward.

Stop.

Again.

“Up.”

Lean forward.

Stop.

Again.

“Up.”

Lean forward.

Stop.

I repeated it.

The word wasn't supposed to produce standing anymore.

Its job was to become associated with the first piece.

That felt much more manageable.

After a while, I stopped deliberately trying to lean.

I relaxed.

Waited.

Then:

“Up.”

I felt the familiar preparation.

A small movement forward.

Still not much.

But now the result matched what I had actually trained.

I smiled.

Maybe the missing distance wasn't supposed to be crossed in one leap.

Maybe I could build a bridge.

I drew it.

UP

↓

BEGIN

↓

SHIFT

↓

RISE

↓

BALANCE

↓

STAND

Now there were intermediate points.

Instead of asking one word to somehow produce an entire result, I could associate the word with the beginning, then connect the beginning to the next part, and continue.

I called these:

LINKS

A capability could be a chain of links.

Some links were already extremely strong because I'd practiced them throughout my life.

Others might be weak.

And if a sequence produced only an almost, perhaps I needed to identify which link wasn't carrying through.

That gave me another DNA principle:

DON'T ONLY ASK WHETHER IT WORKED.

ASK WHERE IT STOPPED.

That changed everything.

I immediately thought about the girl.

Of course I did.

Suppose I saw a woman I wanted to meet.

My goal might be:

Talk to her.

That sounded like one action.

It wasn't.

There could be another chain.

NOTICE HER

↓

RECOGNIZE INTEREST

↓

DECIDE WHETHER APPROACHING IS APPROPRIATE

↓

MOVE

↓

SAY HELLO

↓

LISTEN

↓

RESPOND

↓

DISCOVER WHETHER SHE WANTS TO CONTINUE

Suddenly:

“Talk to her.”

looked almost as complicated as:

“Stand.”

Maybe more complicated.

Because standing depended mostly on me.

Conversation depended on two people.

I couldn't control the second half of the chain.

I drew a line down the page.

On the left:

MINE

Notice.

Decide.

Approach appropriately.

Speak.

Listen.

Be myself.

Respect.

On the right:

HERS

Notice me.

Respond or don't.

Continue or don't.

Like me or don't.

Trust me or don't.

Want to see me again or don't.

That line was permanent.

DNA could work on the left side.

Never the right.

Then I saw something else.

Maybe my biggest obstacles wouldn't occur at the end of a chain.

Maybe they'd happen between links.

I could notice someone...

and stop.

I could decide I wanted to say hello...

and stop.

I could walk toward her...

and stop.

I could start a conversation...

then become so nervous I stopped listening.

Each failure had a location.

That meant each failure could teach me something.

Instead of:

“I failed.”

I could ask:

“Where did the sequence stop?”

That was much more useful.

I made up an imaginary encounter.

A woman is sitting in a coffee shop.

I notice her.

Good.

I think she seems interesting.

Good.

I consider saying hello.

Then:

Nothing.

I stay where I am.

Where did I stop?

Between DECIDE and MOVE.

So the entire social problem wasn't:

I can't meet women.

That was far too large.

The obstacle might be:

DECISION → MOVEMENT

Now I had something small enough to work on.

Maybe COURAGE didn't need to mean:

Become fearless and confidently talk to anybody.

Maybe the first version of courage meant:

When I've decided an ordinary hello is appropriate, move instead of sitting there rehearsing it twenty times.

That was trainable.

Small capability.

Small link.

I wrote:

COURAGE DOESN'T NEED TO REMOVE FEAR.

IT NEEDS TO HELP THE NEXT LINK HAPPEN DESPITE FEAR.

That felt right.

Later I returned to the chair.

One more experiment.

This time I wasn't trying to prove anything.

I simply wanted to observe.

Sit.

Relax.

Wait.

“Up.”

Preparation.

Forward.

My legs engaged.

For a moment I thought I was going to rise.

I didn't.

I settled back.

Almost.

I wrote:

UP trial: reached initiation. No standing.

Nothing more.

No celebration.

No disappointment.

Accurate result.

Then I tried something different.

I said:

“Up.”

Felt the beginning.

And when the movement reached the point where it normally stopped, I consciously completed it.

I stood.

That was obviously not UP making me stand.

I had deliberately finished the action.

But now I had experienced the entire chain with the word attached to its beginning.

I sat.

Repeated it.

“Up.”

Beginning.

Then consciously complete.

Standing.

Again.

Again.

Again.

I wondered whether repetition could gradually reduce how much conscious assistance I needed.

Not:

word → miracle.

But:

word → beginning → practiced chain → completion.

That was a hypothesis I could actually test.

I gave the process a name.

BRIDGING

When a word produced only part of a capability, I wouldn't pretend it had produced the whole thing.

I would identify the point it reached.

Then deliberately practice the missing connection.

Almost → identify gap → practice gap → test again.

That became:

THE BRIDGE METHOD

1. Choose the result.

2. Use the sequence.

3. Observe what actually happens.

4. Find where it stops.

5. Practice the next link deliberately.

6. Repeat.

7. Test without helping.

Simple.

And potentially useful far beyond standing.

Memory could have bridges.

Word → search memory → partial image → context → recall.

Focus could have bridges.

Word → attention → distraction → return → sustained concentration.

Courage could have bridges.

Word → willingness → movement → hello → conversation.

Even relationships had bridges.

Meet → talk → know → trust → care → choose → build.

Nobody jumped from stranger to love.

There were links.

There were distances.

There were bridges.

And every bridge had to be crossed from both sides.

That last thought mattered.

If I moved toward someone and she didn't move toward me, DNA didn't tell me to push harder.

It told me:

Reality.

Observe what is happening.

Respect it.

Change direction when necessary.

The girl of my dreams wasn't going to be the woman I finally became skilled enough to overcome.

She would be someone who wanted to cross the distance too.

I underlined that.

That night I looked back at the first pages of my notebook.

I'd started with:

“Remember where my glasses always are.”

Then I'd imagined sequences.

Then capabilities.

Then compression.

Then UP.

Then almost.

Now almost had revealed something I hadn't expected.

A failure could contain a map.

If I tried something and got halfway there, halfway wasn't merely a disappointing result.

It showed me where the missing distance began.

I wrote:

ALMOST SHOWS THE EDGE OF WHAT I CAN CURRENTLY DO.

Then:

THE NEXT STEP BEGINS AT THE EDGE.

I liked that.

Because Project Her was no longer about somehow constructing one perfect sequence that carried me directly to a woman I'd never met.

That would have been ridiculous.

There would be hundreds of edges.

Hundreds of links.

Hundreds of tiny distances.

Some might eventually become automatic.

Some might always require conscious thought.

Some would depend on circumstances.

And some would depend entirely on another person's choice.

My job was simpler.

Find the next real obstacle.

See how far I could get.

Don't exaggerate the result.

Build the missing bridge.

Try again.

I closed the notebook.

Then reopened it.

One final thought.

At the top of the next blank page I wrote:

WHAT IF WORDS CAN BE JOINED?

I'd spent days investigating what one word could access.

But DNA had begun with sequences.

If UP could reach the beginning of one capability...

what might happen if one word prepared the next?

NOTICE. COURAGE. MOVE.

Three access points.

Three capabilities.

One sequence.

For the first time, I wondered whether the real power of DNA wouldn't come from finding one extraordinary word.

Maybe it would come from learning how ordinary words could work together.

And somewhere inside that possibility was a path I hadn't seen yet.

Not a path directly to her.

A path through the obstacles between us.

5 points to remember

1. A familiar action is actually a sequence of smaller processes.

2. Find exactly where the process stops.

3. Train a smaller bridge instead of demanding the complete result immediately.

4. The result must never be exaggerated.

5. One word may prepare the next capability rather than accomplish everything itself.

Chapter 7

Words in Sequence

I woke up thinking about three words.

NOTICE.

COURAGE.

MOVE.

Individually, I understood them.

Together, they looked different.

Until now I'd been asking how much capability I could place underneath a single word.

UP had taught me something important.

A word might get me started.

It might prepare an action.

It might bring me almost to the edge.

But sometimes there was still a gap.

So perhaps I had been asking the wrong question.

Instead of:

How powerful can one word become?

I wrote:

WHAT CAN WORDS DO TOGETHER?

That was the original idea, after all.

DNA wasn't just words.

It was word sequences.

And sequences had order.

I started with something simple.

Getting out of the chair.

Instead of:

UP

I tried:

UP. MOVE.

Nothing dramatic happened.

I felt the familiar preparation.

Then I deliberately moved.

Standing.

Obviously I'd still consciously participated.

So I tried again.

UP. MOVE.

Preparation.

Forward movement.

Standing.

Again.

Again.

Again.

I couldn't say that the words were automatically producing the action.

But something about the structure made sense.

UP represented initiation.

MOVE represented carrying initiation forward.

Two words had two jobs.

I wrote:

ONE WORD = ONE LINK

Then immediately crossed it out.

Too absolute.

Sometimes one word could represent many links.

So I replaced it with:

ONE WORD CAN HAVE ONE CLEAR JOB INSIDE A LARGER SEQUENCE.

Better.

I began experimenting on paper.

Suppose the objective was remembering my glasses.

Maybe:

GLASSES → REMEMBER

was enough.

But if it wasn't?

I could expand it:

GLASSES → LAST → REMEMBER

The additional word changed the procedure.

Don't search every possible location.

Go backward toward the last interaction.

Or:

GLASSES → USUAL → REMEMBER

Different search.

Now I wasn't looking for the last location.

I was accessing the usual location.

That was interesting.

One word could alter another word.

The sequence wasn't simply a list.

Its order and combination could specify which capability I wanted.

I wrote:

GLASSES. LAST. REMEMBER.

Then:

GLASSES. USUAL. REMEMBER.

Same target.

Different route.

That was the beginning of grammar.

I almost laughed when I wrote that.

DNA GRAMMAR

Now I was inventing a language.

Not a language for talking to DNA.

A language for organizing access to things I could practice doing.

I tried to identify the simplest structure.

TARGET → ROUTE → CAPABILITY

GLASSES → LAST → REMEMBER

Target: glasses.

Route: last location.

Capability: remembering.

Then another:

SITUATION → CAPABILITY → ACTION

OPPORTUNITY → COURAGE → MOVE

And:

INFORMATION → QUALITY → OPERATION

MEMORY → ACCURATE → CHECK

Suddenly I could see why sequences might become much more useful than isolated words.

One word could be broad.

The next could narrow it.

The next could direct it.

The sequence could become a tiny map.

But maps could become too complicated.

I discovered that almost immediately.

I wrote:

NOTICE. OBSERVE. REALITY. COMPARE. DECIDE. COURAGE. MOVE. SPEAK. LISTEN. REMEMBER. VERIFY. CONTINUE.

I read it back.

Ridiculous.

If I had to consciously run twelve commands before saying hello, the woman would probably have finished her coffee and gone home.

DNA was supposed to reduce conscious complexity.

Not create more of it.

So I wrote:

THE SHORTEST SEQUENCE THAT WORKS.

That became another rule.

If one word worked, use one.

If two were needed, use two.

If three were needed, use three.

Don't use ten because ten sounds more sophisticated.

The best sequence wasn't the longest.

It was the smallest sequence capable of reliably opening the procedure I needed.

Then I noticed something else.

Some words belonged together naturally.

NOTICE → REALITY

Notice something.

Then distinguish observation from interpretation.

DECIDE → MOVE

Make the decision.

Then stop endlessly deciding.

LISTEN → REMEMBER

Pay attention first.

Retain what matters second.

WRONG → CHANGE

Recognize an error.

Change direction.

These were almost like little DNA fragments.

I gave them a name:

PAIRS

A pair was a two-word sequence that represented a familiar transition.

Then came:

CHAINS

Several pairs could connect.

NOTICE → REALITY → DECIDE → MOVE

But I still didn't want to consciously recite the entire chain every time.

The eventual goal was compression.

Practice the chain.

Strengthen it.

Then perhaps give the whole thing a shorter access point.

I drew:

NOTICE → REALITY → DECIDE → MOVE

↓

APPROACH

One word could eventually represent the trained chain.

But only after the chain underneath it was understood and practiced.

That was Chapter 4's rule again.

Never compress too early.

I decided to test sequences somewhere other than my notebook.

Nothing romantic.

Nothing dramatic.

I went out with one sequence in mind:

NOTICE. DIFFERENT.

The job was simple.

Notice something outside my normal pattern.

I started walking.

At first, everything looked ordinary.

Then I began noticing differences.

A route I rarely took.

A business I'd never entered.

People I wouldn't normally encounter.

A place where people actually stopped and talked instead of simply passing through.

I hadn't discovered the girl of my dreams.

I hadn't expected to.

What I had discovered was that SEARCH didn't necessarily mean searching for a person.

It could mean changing the conditions under which encounters became possible.

That produced another sequence:

ROUTINE. CHANGE.

I tried it.

Instead of doing exactly what I normally would, I changed one harmless part of my route.

Then another.

The world didn't transform.

But my sample of it did.

Different surroundings.

Different people.

Different information.

Different possibilities.

I wrote later:

IF I ALWAYS SAMPLE THE SAME ENVIRONMENT, I KEEP GETTING SIMILAR INPUT.

DNA couldn't guarantee what a changed route would contain.

But it could help me stop searching the same square meter of reality forever.

Then something happened.

A woman looked at me.

That was all.

She looked.

I noticed.

Immediately my imagination tried to perform its favorite trick.

Was that something?

DNA.

NOTICE. REALITY.

What actually happened?

A woman looked at me.

Anything else?

No.

Then that's the data.

Not:

She likes me.

Not:

She's the one.

Not:

Destiny.

A look.

I continued walking.

And I felt strangely pleased.

Not because I'd gotten anywhere with her.

Because the sequence had prevented me from inventing information.

That counted as success.

The system wasn't merely helping me act.

It was helping me not act on things that weren't there.

Later, another interaction gave me something more useful.

Someone spoke to me.

Nothing romantic.

An ordinary exchange.

But I decided to test:

LISTEN. REMEMBER.

Instead of concentrating on what I would say next, I paid attention to one specific thing the person told me.

I continued the conversation.

Several minutes later, I could still recall it.

Tiny result.

But real.

I wrote it down.

LISTEN → REMEMBER

worked as a useful behavioral sequence.

Not perfectly.

Not magically.

But the first word improved the conditions for the second.

That was important.

You can't remember information you never properly took in.

The sequence had internal logic.

Maybe that was another requirement.

EACH WORD SHOULD PREPARE SOMETHING USEFUL FOR WHAT FOLLOWS.

Now DNA began looking less like a collection of commands and more like a chain of conditions.

NOTICE gives REALITY something to examine.

REALITY gives DECIDE better information.

DECIDE gives MOVE a direction.

MOVE creates an opportunity for SPEAK.

SPEAK creates conditions for LISTEN.

LISTEN gives REMEMBER something worth storing.

Each link changed what became possible at the next link.

That was much closer to what I'd been looking for.

At home I drew the longest sequence yet.

Not one I intended to memorize.

A model.

THE ENCOUNTER SEQUENCE

SEARCH

↓

NOTICE

↓

REALITY

↓

DECIDE

↓

COURAGE

↓

MOVE

↓

SPEAK

↓

LISTEN

↓

REMEMBER

↓

COMPARE

↓

CLARIFY

↓

RESPECT

↓

CONTINUE / STOP

I stared at it.

There she was.

Not a particular woman.

Not a face.

Not a fantasy.

But the structure of how I might eventually get from strangers to knowing whether we actually wanted each other in our lives.

And something jumped out at me.

The sequence didn't end with:

GET HER.

It ended with two possibilities.

CONTINUE

or

STOP

That was necessary.

A useful system had to be able to produce either result.

If every road always ended with CONTINUE, I wasn't evaluating reality.

I was chasing an objective regardless of evidence.

Sometimes successful navigation meant discovering that a road wasn't mine.

Then I drew a second sequence beside it.

HER SEQUENCE

I stopped.

I couldn't fill it in.

That surprised me.

I could guess.

But I couldn't know.

She would have her own thoughts.

Her own decisions.

Her own reasons.

Her own history.

Her own version of courage.

Maybe she'd notice me first.

Maybe she'd speak first.

Maybe she'd be shy.

Maybe she wouldn't be shy at all.

Maybe the girl of my dreams wasn't waiting passively at the end of my sequence.

Maybe she was moving through sequences of her own.

That changed the picture.

We weren't:

ME → HER

We were:

ME → ? ← HER

Two independent paths potentially meeting.

I drew a circle around the question mark.

MEETING POINT

DNA could help me reach meeting points.

It couldn't decide who else arrived there.

That was reality.

That evening I returned to UP.

The little word that had started this entire new direction.

I sat.

Relaxed.

Then:

“Up.”

Preparation.

Movement.

Almost.

I stopped.

Then tried:

“Up. Continue.”

I felt the beginning.

I consciously allowed the familiar movement to proceed.

I stood.

Again, I couldn't honestly say the words had automatically stood me up.

But the second word represented something important.

The first word reached an edge.

The next word pointed beyond it.

That gave me the clearest description of a word sequence I'd written yet:

WHEN ONE WORD REACHES ITS EDGE, THE NEXT WORD CAN REPRESENT THE NEXT CAPABILITY.

I sat back down.

Now I understood why sequences mattered.

One word didn't need to contain everything.

Neither did the second.

Or the third.

They could divide an obstacle into manageable transitions.

And after enough successful repetition, perhaps several transitions could eventually compress into one familiar sequence.

I opened to a blank page.

There was one problem left.

A serious one.

If I created hundreds of sequences, how would I know which one to use at the right moment?

Having the right sequence somewhere in a notebook was useless if I couldn't retrieve it when the obstacle appeared.

That was almost funny.

I'd created a system designed to help me remember, notice, decide and act.

Now I needed a system for remembering the system itself.

I wrote:

THE RIGHT WORD AT THE RIGHT TIME.

Then underneath:

How does the obstacle select the sequence?

I stared at that question.

Maybe I'd been organizing DNA backward.

Maybe I shouldn't begin with words at all.

Maybe I should begin with obstacles.

An obstacle appears.

Recognize its type.

The type points toward a sequence.

The sequence accesses the capability.

The capability produces the next useful action.

I drew:

OBSTACLE → RECOGNITION → SEQUENCE → CAPABILITY → ACTION

For the first time, DNA looked complete from beginning to end.

Except for one thing.

I still had to learn how to recognize the obstacle quickly enough.

I closed the notebook.

Tomorrow's page already had its title.

THE OBSTACLE CHOOSES THE WORD

Somewhere between me and the woman I hadn't met were obstacles I couldn't possibly predict.

That no longer bothered me as much.

Maybe I didn't need to predict them.

Maybe I needed a system capable of recognizing them when they arrived.

5 points to remember

1. One word doesn't need to do everything.

2. The next word can begin where the previous capability reaches its edge.

3. Sequences divide complicated obstacles into manageable transitions.

4. Sequences must respond to reality rather than force a predetermined outcome.

5. Two people are following independent paths.

Chapter 8

The Obstacle Chooses the Word

I had built myself a new problem.

Too many words.

That morning I opened the notebook and counted them.

REMEMBER.

NOTICE.

SEARCH.

FOCUS.

START.

MOVE.

OBSERVE.

CLARIFY.

REALITY.

CHANGE.

LEARN.

CONTINUE.

COURAGE.

LISTEN.

COMPARE.

DECIDE.

STOP.

VERIFY.

RESPECT.

And those were only the obvious ones.

I could easily invent another hundred.

Eventually a thousand.

Then what?

Imagine encountering the girl of my dreams and thinking:

Hold on. I have exactly the right DNA sequence for this.

It's somewhere around page 274.

Useless.

The system had to operate when I needed it.

Not twenty minutes later.

I looked at yesterday's final question:

HOW DOES THE OBSTACLE SELECT THE SEQUENCE?

Maybe the answer was hidden inside the question.

I had been organizing DNA around words.

Perhaps I should organize it around problems.

I started with the glasses.

What was the obstacle?

Missing information.

I didn't know where they were.

What capability answered missing information?

REMEMBER.

So:

MISSING INFORMATION → REMEMBER

Simple.

What if I couldn't remember?

Then perhaps:

UNCERTAIN MEMORY → VERIFY

What if I knew where the glasses were but kept putting off getting them?

INERTIA → MOVE

Same objective.

Different obstacle.

Different word.

That mattered.

The object didn't choose the sequence.

The obstacle did.

I wrote:

DON'T ASK:

“WHAT WORD DO I USE FOR GLASSES?”

ASK:

“WHAT IS STOPPING ME RIGHT NOW?”

That was better.

Much better.

I started creating categories.

OBSTACLE 1: I DON'T KNOW

Possible words:

SEARCH

REMEMBER

ASK

LEARN

VERIFY

Then:

OBSTACLE 2: I KNOW, BUT I'M NOT DOING

Possible words:

START

MOVE

COURAGE

CONTINUE

Then:

OBSTACLE 3: I DON'T KNOW WHAT'S TRUE

Possible words:

REALITY

OBSERVE

COMPARE

VERIFY

CLARIFY

Then:

OBSTACLE 4: I'M GOING THE WRONG WAY

Possible words:

STOP

CHANGE

RECALCULATE

Then:

OBSTACLE 5: TOO MUCH INFORMATION

Possible words:

FOCUS

SIMPLIFY

PRIORITY

Then:

OBSTACLE 6: ANOTHER PERSON IS INVOLVED

I stopped.

That category was different.

I couldn't solve another person.

People weren't obstacles in the same sense as forgotten glasses or a difficult task.

The obstacle might be my uncertainty about another person.

Or my fear.

Or my misunderstanding.

Or conflicting desires between us.

But the person herself wasn't something for DNA to overcome.

I crossed out the heading.

Then wrote:

OBSTACLE 6: I DON'T UNDERSTAND THE OTHER PERSON

Possible words:

LISTEN

ASK

OBSERVE

CLARIFY

RESPECT

REALITY

That was much better.

I looked at the categories.

Something interesting was happening.

Hundreds of possible situations were collapsing into a handful of obstacle types.

Lose my glasses?

I DON'T KNOW.

Forget someone's name?

I DON'T KNOW.

Unsure where I'm going?

I DON'T KNOW.

Different situations.

Same underlying structure.

Then:

Avoiding a task?

I KNOW, BUT I'M NOT DOING.

Afraid to say hello?

Possibly:

I KNOW, BUT I'M NOT DOING.

Standing at the door knowing I should leave but continuing to delay?

Again:

I KNOW, BUT I'M NOT DOING.

The surface details changed.

The obstacle underneath could be the same.

That meant I might not need thousands of completely unrelated sequences.

Maybe I needed a small number of obstacle families.

I wrote:

MANY SITUATIONS.

FEWER OBSTACLE TYPES.

FEWER CORE CAPABILITIES.

That looked promising.

Then I tested it.

I picked a small unfinished task.

Normally I would have thought:

I should do that.

Then continued doing something else.

This time I asked:

What's stopping me?

Did I not know how?

No.

Was information missing?

No.

Was I uncertain whether it needed doing?

No.

Did I simply not feel like beginning?

Yes.

Obstacle family:

I KNOW, BUT I'M NOT DOING.

Word:

START.

I started.

Again, nothing supernatural.

But the classification had removed a lot of unnecessary thinking.

I didn't need to analyze my entire personality.

I didn't need a motivational speech.

The obstacle was simple.

So the word was simple.

START.

Later I couldn't remember something.

My first instinct was to strain harder.

Then:

What's stopping me?

Missing information.

But was the information actually missing?

No.

I'd known it earlier.

So this wasn't really SEARCH.

It was:

REMEMBER.

I reconstructed the context.

Part of the memory returned.

Not enough.

Now the obstacle changed.

I had a memory, but I wasn't sure it was accurate.

New obstacle:

UNCERTAINTY.

New word:

VERIFY.

That was interesting.

One problem could change categories while I was solving it.

I drew:

REMEMBER → VERIFY

The first capability produced something.

That something created the next obstacle.

The next obstacle selected the next capability.

DNA didn't necessarily need the entire sequence in advance.

The sequence could be constructed while moving.

That was a major breakthrough.

I wrote:

I DON'T HAVE TO KNOW THE WHOLE SEQUENCE.

THE NEXT OBSTACLE CAN SUPPLY THE NEXT WORD.

I sat back.

That felt strangely familiar.

Chapter 1.

I'd written:

I don't need to know the whole path. I need to get the next move right.

Now the same principle had appeared inside DNA itself.

Maybe sequences weren't always fixed sentences.

Maybe they could be generated by reality.

Obstacle.

Word.

Action.

New situation.

New obstacle.

Next word.

That looked like:

OBSTACLE → WORD → ACTION → NEW REALITY

Then repeat.

I drew it as a circle.

That was different from:

NOTICE → COURAGE → MOVE → SPEAK → LISTEN

That sequence assumed I already knew what would happen.

Real life didn't work like that.

Suppose I noticed a woman.

NOTICE.

Then what?

Maybe she smiled.

Maybe she looked away.

Maybe she spoke first.

Maybe somebody joined her.

Maybe I realized she was waiting for someone.

Maybe I discovered I wasn't actually interested.

Each outcome created a different next step.

So instead of forcing the same sequence every time, DNA could branch.

I wrote:

DNA IS NOT A SCRIPT.

That deserved a box.

DNA RESPONDS TO WHAT ACTUALLY HAPPENS.

Now the system was becoming less like a memorized routine and more like navigation.

Navigation.

That word stayed in my mind.

When you're traveling somewhere, you have a destination.

But you don't control the road.

Traffic appears.

A street is closed.

You miss a turn.

Weather changes.

You encounter construction.

Good navigation doesn't insist:

Continue straight because that was the original plan.

It updates.

Maybe DNA should do the same.

I wrote:

OBJECTIVE

↓

NEXT OBSTACLE

↓

CAPABILITY

↓

ACTION

↓

OBSERVE RESULT

↓

UPDATE

That was the loop.

Then I gave it a name:

THE DNA NAVIGATION LOOP

1. Know what I am trying to accomplish.

2. Identify what is stopping the next useful step.

3. Recognize the obstacle family.

4. Access the appropriate capability.

5. Act.

6. Observe what actually happened.

7. Update.

8. Repeat.

This might have been the most complete description of DNA I'd written.

Naturally, I applied it to Project Her.

Objective:

Build a loving relationship with the right woman.

Current obstacle:

I haven't met her.

What family?

At first I wrote:

I DON'T KNOW.

But that wasn't quite right.

I didn't simply lack information.

I lacked contact.

So what capability increased contact with new people?

SEARCH.

But SEARCH sounded too much like hunting for a specific person.

Maybe:

EXPAND.

I liked that better.

Expand where I went.

Expand whom I met.

Expand the situations in which conversation could naturally happen.

Expand without treating every woman as a candidate.

I wrote:

EXPAND

That became a new core word.

Then I asked:

What comes after EXPAND?

I almost wrote NOTICE.

But I stopped myself.

I didn't know.

That was the entire lesson.

Maybe nothing came after it.

Maybe I'd expand my world and meet nobody interesting that day.

Maybe I'd make a male friend.

Maybe I'd discover a place I liked.

Maybe I'd meet a woman who became a friend but nothing more.

Maybe I'd meet someone who introduced me to somebody else six months later.

Maybe I'd meet her.

I couldn't know the next word until reality supplied the next obstacle.

So Project Her became:

EXPAND → ?

That question mark didn't bother me anymore.

The question mark was where reality entered the system.

I went outside.

Not on some grand romantic expedition.

I simply changed part of my normal routine.

EXPAND.

Different place.

Different surroundings.

Different people.

Then I stopped thinking about the system.

That seemed important too.

DNA couldn't become something that occupied every second of my attention.

The system should help me participate in life.

Not replace participation with constant analysis.

So I walked.

Looked around.

Did ordinary things.

Then I noticed her.

Not her.

I had to stop doing that.

A woman.

That's all I knew.

She was standing some distance away.

I noticed her because she seemed familiar.

I looked again.

Had I seen her before?

Maybe.

Now an obstacle appeared.

I don't know.

My mind reached automatically for:

REMEMBER.

Interesting.

I hadn't consciously searched the notebook.

The obstacle had suggested the word.

I tried to reconstruct where I might have seen her.

Nothing definite.

Then my mind wanted to turn uncertainty into certainty.

Maybe she was the woman who'd looked at me yesterday.

Maybe this meant something.

I caught it.

New obstacle:

I don't know what's true.

Word:

REALITY.

What did I actually know?

A woman looked familiar.

That was it.

Could I verify?

Not without staring at her or behaving strangely.

Was verification necessary?

No.

Then the correct action was surprisingly simple.

Nothing.

I continued with my day.

And that felt like DNA working properly.

It had helped me stop.

That evening I realized something I'd never expected when I started this project.

A system designed to get me past obstacles was teaching me that sometimes the obstacle was my urge to turn uncertainty into a story.

DNA wasn't always:

GO.

Sometimes it was:

WAIT.

Sometimes:

CHECK.

Sometimes:

ASK.

Sometimes:

STOP.

Sometimes:

I DON'T KNOW.

That last one deserved to become part of the vocabulary.

UNKNOWN

Not failure.

Not confusion.

A legitimate state.

If the evidence wasn't sufficient:

UNKNOWN.

No need to fill the empty space with imagination.

I wrote:

UNKNOWN IS BETTER THAN A FALSE ANSWER.

Then underneath:

LEAVE ROOM FOR REALITY TO SUPPLY MORE INFORMATION.

I looked again at the obstacle families.

They were becoming almost like a map.

Missing knowledge → LEARN / SEARCH

Missing memory → REMEMBER

Uncertain truth → REALITY / VERIFY

Inaction → START / MOVE

Fear → COURAGE

Confusion → CLARIFY

Overload → FOCUS

Wrong direction → CHANGE

Another person's meaning → LISTEN / ASK

No evidence → UNKNOWN

Boundary reached → RESPECT / STOP

Failure → LEARN

Progress → CONTINUE

I didn't need to memorize every possible sentence.

I needed to become good at one question:

WHAT IS THE OBSTACLE NOW?

Not yesterday.

Not five steps from now.

Now.

Before bed I returned to UP.

I sat in the chair.

Said:

“Up.”

Preparation.

Forward movement.

Almost.

The old obstacle.

Where did it stop?

Initiation.

What was missing?

Completion.

I could consciously complete it.

But tonight I didn't.

I remained seated.

Because suddenly UP wasn't the interesting part anymore.

The interesting part was that I could identify exactly where the process stopped.

The obstacle had become visible.

And once an obstacle became visible, I could begin designing around it.

I wrote:

YOU CAN'T SELECT THE RIGHT CAPABILITY UNTIL YOU KNOW WHAT IS ACTUALLY IN THE WAY.

Then I turned to Project Her.

There was one uncomfortable possibility I hadn't considered.

What if I eventually met an extraordinary woman...

and there was no obvious obstacle?

What if she liked me?

What if I liked her?

What if conversation was easy?

What if the path opened instead of closing?

I'd spent all this time designing DNA to overcome problems.

But relationships weren't supposed to be endless obstacles.

At some point, if I found the right person, maybe the system would need to recognize something completely different.

Not:

What's stopping me?

But:

What's working?

I turned the page.

At the top I wrote:

DON'T FIX WHAT ISN'T BROKEN.

Then another thought:

If DNA could recognize obstacles...

maybe it also needed to recognize green lights.

Signs that something was going well.

Mutual interest.

Comfort.

Trust.

Reciprocity.

Progress.

Maybe finding the girl of my dreams wouldn't only require getting past what stood in my way.

Maybe I'd also have to recognize when, for once...

nothing was standing in the way.

5 points to remember

1. Ask: “What is the obstacle now?”

2. Recognize the obstacle's type before choosing a capability.

3. DNA is navigation, not a rigid script.

4. UNKNOWN is a legitimate answer.

5. Reality supplies the next step.

Chapter 9

Green Lights

I'd built a system for problems.

That was the problem.

Everywhere I looked, I was beginning to see obstacles.

Missing information?

REMEMBER.

Uncertainty?

VERIFY.

Fear?

COURAGE.

Wrong direction?

CHANGE.

Confusion?

CLARIFY.

No evidence?

UNKNOWN.

It was becoming automatic.

Something got in my way, and I wanted to classify it.

That was useful.

But life wasn't made entirely of things getting in my way.

Sometimes something worked.

What word did I have for that?

I opened the notebook to last night's final sentence:

NOTHING IS STANDING IN THE WAY.

I stared at it.

Then wrote one word.

CONTINUE

Maybe it was that simple.

I thought about driving, even though I wasn't driving anywhere.

Traffic lights.

Red was easy.

Stop.

Yellow required judgment.

But green?

Green didn't mean:

Analyze the intersection for fifteen minutes.

It meant the path was presently open.

Proceed appropriately.

That gave me a new category.

I'd spent days designing DNA around red lights.

Obstacles.

Maybe I needed green lights too.

Things that indicated:

This is working.

Don't interfere unnecessarily.

Continue.

So I started listing them.

Not specifically for relationships.

For anything.

Progress.

Consistency.

Improvement.

Accuracy.

Ease.

Reciprocity.

Results.

Then I wrote:

RED LIGHT → SOMETHING REQUIRES ATTENTION.

GREEN LIGHT → SOMETHING IS WORKING. ALLOW IT TO CONTINUE.

Simple.

But I immediately saw the danger.

What if I wanted something to be a green light so badly that I interpreted it as one?

Back to:

REALITY.

Of course.

Even green lights needed evidence.

I tested the idea with UP.

That word had become my laboratory.

I sat.

Relaxed.

“Up.”

Preparation.

Forward movement.

Almost.

Red light?

Not exactly.

Something had happened.

The sequence had reached partway.

That was progress compared with nothing.

But I still hadn't stood.

So perhaps DNA needed more than red and green.

I drew three categories:

RED

Stopped. Wrong. Unsafe. Boundary.

YELLOW

Partial. Uncertain. Almost. More information needed.

GREEN

Working. Appropriate. Continue.

I looked at UP.

Yellow.

Obviously.

Not failure.

Not completion.

Almost.

That word had finally found its category.

I wrote:

ALMOST IS YELLOW.

That meant:

Don't claim success.

Don't throw the experiment away.

Observe.

Learn.

Continue carefully.

Then I applied the same system to Project Her.

That became much more complicated.

What would a red light look like?

Easy.

She says no.

Red.

She repeatedly avoids interaction.

Red.

She establishes a boundary.

Red.

Respect it.

Stop.

What about yellow?

I can't tell whether she's interested.

Yellow.

Conversation is polite but unclear.

Yellow.

I think there might be something there, but I don't have enough evidence.

Yellow.

No fantasy.

No certainty.

Just:

UNKNOWN.

And green?

I stopped.

That required more thought.

A smile wasn't automatically green.

A look wasn't automatically green.

Being friendly wasn't automatically green.

What would actually count?

I wrote:

She chooses to continue the conversation.

That's something.

She initiates conversation another time.

Stronger.

She remembers things about me.

Interesting.

She asks questions because she wants to know me.

Interesting.

She makes time to see me.

Stronger.

I make time to see her, and she welcomes it.

Mutual.

Then the word appeared.

RECIPROCITY

That might be the most important green-light word in the entire relationship system.

Not:

I move toward her.

But:

We move toward each other.

I wrote:

INTEREST THAT ONLY MOVES IN ONE DIRECTION IS NOT THE GREEN LIGHT I'M LOOKING FOR.

That changed Project Her again.

Until now, I'd imagined myself moving through obstacles toward some unknown woman.

But perhaps the final part of the journey couldn't work that way.

At first:

I move.

Then eventually:

We move.

The transition mattered.

I drew:

SEARCH → ENCOUNTER → INTEREST → RECIPROCITY → RELATIONSHIP

Then immediately corrected it.

Too neat.

Reality wasn't guaranteed to follow a straight line.

So:

SEARCH

↓

ENCOUNTER

↓

?

From there anything could happen.

No interest.

Friendship.

Attraction from one side.

Attraction from both.

Compatibility.

Incompatibility.

Good timing.

Terrible timing.

A relationship.

Nothing.

The question mark remained.

I was getting comfortable with question marks.

That afternoon I decided to experiment with something I'd been neglecting.

Instead of asking:

What's wrong?

I asked:

WHAT'S WORKING?

It was surprisingly difficult.

My mind was much better at finding problems.

So I looked deliberately.

What was working in DNA?

Short words were easier to remember than long instructions.

Green.

Classifying an obstacle sometimes helped me choose what to do next.

Green.

REALITY prevented me from exaggerating uncertain situations.

Very green.

UP still wasn't reliably producing standing.

Yellow.

Some sequences were getting unnecessarily complicated.

Yellow.

I was creating new words faster than I could practice them.

Yellow approaching red.

Interesting.

The green-light system had revealed a problem.

That seemed contradictory at first.

Then I understood.

Recognizing what works makes it easier to see what doesn't.

I didn't have to throw away the entire system because one part was weak.

I could preserve the green parts and work on the yellow ones.

That produced another principle:

KEEP WHAT WORKS.

MODIFY WHAT DOESN'T.

Obvious.

Yet people violate it constantly.

Sometimes we change everything because one thing failed.

Sometimes we preserve everything because one thing succeeded.

DNA needed finer judgment.

Then something happened that I hadn't expected.

I was out.

Ordinary day.

Ordinary place.

I noticed a woman.

Again, not her.

A woman.

I reminded myself:

REALITY.

Nothing had happened yet.

Then she looked at me.

Yellow.

Maybe meaningless.

I looked away.

A little later, our paths crossed again.

This time she smiled.

My mind immediately wanted to upgrade the situation.

I stopped it.

Smile.

That's all.

Yellow.

Then she said hello.

That was new information.

I said hello back.

There was a short conversation.

Nothing extraordinary.

But she participated.

She asked me something.

I answered.

I asked something.

She answered.

Then the interaction naturally ended.

I continued on my way.

No phone number.

No dramatic moment.

No mysterious certainty.

But later I realized something.

I'd done it.

Not found her.

Something more basic.

I'd participated in an interaction without turning it into either extreme.

I hadn't thought:

She's definitely interested.

And I hadn't thought:

That meant nothing.

I had simply allowed the event to be what it was.

A pleasant conversation with a woman.

Maybe nothing more would ever happen.

Maybe I'd never see her again.

That was okay.

I wrote:

GREEN DOESN'T MEAN FOREVER.

GREEN MEANS CONTINUE WHILE THE CONDITIONS REMAIN GREEN.

That might have been my best definition yet.

Then I wondered:

What would I have done differently before DNA?

Maybe overthought it.

Maybe tried to determine immediately what everything meant.

Maybe wondered whether I should have said something different.

Maybe replayed the conversation looking for hidden information.

But the system gave me a simpler answer.

What is the current obstacle?

None.

Then don't invent one.

That became a sequence:

GREEN → CONTINUE

Not:

GREEN → ANALYZE UNTIL IT BECOMES RED.

I laughed when I wrote that.

Because I knew exactly how easily a person could do it.

Something good happens.

Then we think about it until we've discovered seventeen imaginary problems.

Maybe sometimes intelligence meant knowing when to stop solving.

That night I returned to the imaginary girl of my dreams.

For months, years, however long it took, I might encounter red lights and yellow lights.

Wrong people.

Wrong timing.

My own hesitation.

Their lack of interest.

My lack of interest.

Confusion.

Almosts.

Mistakes.

But if I eventually encountered the right woman, something different should happen.

The system shouldn't have to drag the relationship forward.

She would participate.

I'd ask a question.

She'd ask one.

I'd remember something about her.

She'd remember something about me.

I'd make time.

She'd make time.

I'd want another conversation.

She would too.

I wouldn't need DNA to overcome her.

There would be nothing to overcome.

That thought landed heavily.

I wrote:

THE GIRL OF MY DREAMS IS NOT THE FINAL OBSTACLE.

Then:

SHE IS THE PERSON I HOPE TO BUILD WITH AFTER THE OBSTACLES BETWEEN US HAVE BEEN CROSSED.

That was completely different.

Project Her wasn't:

Defeat enough obstacles until I obtain her.

It was:

Become capable of reaching a place where two people can freely choose each other.

And once that happened, DNA's role would change.

Less:

MOVE.

More:

LISTEN.

Less:

COURAGE.

More:

TRUST.

Less:

SEARCH.

More:

BUILD.

That word was new.

BUILD

I put a box around it.

Maybe BUILD was what came after FIND.

Maybe I'd been so focused on finding the girl of my dreams that I hadn't thought enough about what happened after finding her.

Finding was a moment.

Building could take a lifetime.

I turned to a fresh page.

GREEN-LIGHT WORDS

CONTINUE

RECIPROCITY

TRUST

ENJOY

LEARN

GROW

BUILD

Then one more:

APPRECIATE

That felt important.

If something good finally entered my life, I didn't want to be so busy searching for the next improvement that I failed to experience what I'd already found.

Maybe DNA needed to help me recognize success as much as overcome difficulty.

Not everything needed fixing.

Not every silence needed filling.

Not every uncertainty needed an immediate answer.

Not every good moment needed to become something bigger.

Sometimes:

APPRECIATE.

Before sleeping, I performed the old experiment.

Chair.

Relax.

“Up.”

Preparation.

Forward movement.

Almost.

Yellow.

I smiled.

I didn't force it.

Didn't exaggerate it.

Didn't dismiss it.

Tomorrow I could work on the bridge again.

But tonight, something else was green.

The system itself had changed.

At the beginning, I thought DNA would be about getting what I wanted.

Then I thought it would be about overcoming obstacles.

Now I was beginning to understand something larger.

A good navigation system needed to recognize three things:

WHEN TO STOP.

WHEN TO INVESTIGATE.

WHEN TO GO.

Red.

Yellow.

Green.

And maybe finding the girl of my dreams would depend just as much on knowing when the road was open as knowing how to get around something blocking it.

I closed the notebook.

Then reopened it one last time.

I wrote:

WHAT HAPPENS WHEN TWO PEOPLE BOTH SEE GREEN?

I stared at the question.

For once, I didn't try to answer it.

I had a feeling I was going to need someone else for that.

5 points to remember

1. Not everything is an obstacle.

2. RED = stop/problem/boundary.

3. YELLOW = uncertain/partial/almost/investigate.

4. GREEN = working/appropriate/continue.

5. Don't interfere unnecessarily with something that is already working

Chapter 10

When Two People Both See Green

I saw her again.

That was the first thing that surprised me.

The woman from the short conversation.

The one I'd deliberately refused to turn into a story.

I'd assumed there was a good chance I'd never see her again.

Apparently reality had other plans.

I noticed her before she noticed me.

Immediately, the machinery started.

NOTICE.

Then:

REALITY.

What did I actually know?

I'd spoken with her once.

The conversation had been pleasant.

She'd participated.

She'd asked questions.

Nothing more.

Yellow, perhaps.

Maybe light green.

Definitely not destiny.

I almost laughed at myself.

Then she saw me.

And smiled.

Not the polite little smile people sometimes give strangers.

Recognition.

She remembered me.

Then she did something that eliminated my next problem.

She walked toward me.

I hadn't planned for that.

“Hey.”

“Hey.”

“You again.”

I smiled.

“Apparently.”

She laughed.

And just like that, something strange happened to DNA.

I didn't need it.

At least not immediately.

There was no obstacle.

No missing bridge.

No moment requiring COURAGE → MOVE.

She had moved.

The conversation had already started.

For eight chapters I'd been designing a system to help me reach moments like this.

Now that one had arrived, my first instinct was to start analyzing it.

Then another word surfaced.

GREEN.

Don't fix what isn't broken.

So I talked to her.

Her name was Maya.

This time I made sure I remembered it.

Not with some elaborate internal sequence.

I simply paid attention when she said it.

“Maya.”

“Wendell.”

She repeated mine too.

That registered.

Not proof of anything.

Information.

We talked.

Nothing cinematic happened.

No music started playing.

Nobody stopped in the street.

I didn't suddenly know that she was the girl I'd been looking for.

In fact, I knew almost nothing about her.

And that was exactly what made the moment different from the imaginary version I'd carried around for so long.

The imaginary girl had been perfect because she contained no inconvenient information.

Maya was real.

Real people come with information you didn't invent.

Opinions you didn't select.

Preferences you might not share.

History you weren't present for.

Bad days.

Contradictions.

Surprises.

The possibility of disappointing you.

And the possibility that you might disappoint them.

I realized something while she was talking.

The girl of my dreams could only exist in my dreams.

The woman I could actually love would have to exist in reality.

Those weren't necessarily the same person.

That thought stayed with me.

I nearly missed something she said.

My mind had wandered into DNA again.

I caught myself.

LISTEN.

That was all.

Return.

She was telling me about something she'd done earlier in the week.

I listened.

Asked a question.

She continued.

Then she asked me something.

And I noticed the rhythm.

I speak.

She listens.

She speaks.

I listen.

I ask.

She asks.

Neither person carrying the entire interaction.

There it was.

RECIPROCITY.

I'd written the word in a notebook before I'd properly experienced what I meant by it.

Now I understood it differently.

Reciprocity didn't mean keeping score.

I asked three questions, so she owes me three.

That would be ridiculous.

It meant something more organic.

Both people were contributing energy.

The interaction wasn't something I was doing to her.

It was something happening between us.

That was green.

Eventually we had to go separate ways.

This was the point where old Project Her thinking might have become frantic.

Don't lose the opportunity.

Do something.

Say the perfect thing.

What's the sequence?

Instead, I noticed what was actually happening.

We were both lingering slightly.

Conversation finished.

Then restarted.

Then almost finished.

Then restarted again.

Interesting.

Reality.

Not proof of love.

Not destiny.

But information.

I decided to take one step.

“Would you want to grab coffee sometime?”

There.

No complicated sequence.

No trick.

No strategy.

Just a question.

Maya smiled.

“Yeah.”

Green.

Then she added:

“I'd like that.”

Greener.

Walking home, I wanted to celebrate.

Then I caught myself.

What exactly had happened?

I had met a woman twice.

We enjoyed talking.

She agreed to coffee.

That's all.

That was good.

Very good.

But DNA had taught me not to make a result larger than the result.

So I opened the notebook when I got home and wrote:

Maya agreed to coffee.

Period.

I stared at the sentence.

Then underneath:

DON'T TURN GREEN INTO FOREVER.

That was going to matter.

Green meant:

Continue while conditions remain green.

It didn't mean:

The entire road ahead is guaranteed clear.

Tomorrow could produce yellow.

Next week could produce red.

Or green could continue.

I didn't know.

And for once, not knowing felt exciting rather than threatening.

Our coffee happened a few days later.

I arrived first.

That gave me too much time to think.

My mind immediately began trying to predict everything.

Would she arrive?

Would conversation still feel easy?

Had I misunderstood?

Would I like her as much after an hour?

Would she like me?

I recognized the obstacle.

UNKNOWN.

Normally unknown information irritated me.

Today I tried something different.

I left it unknown.

Then Maya arrived.

Green.

She smiled when she saw me.

Green.

She sat down.

And within minutes, we were talking.

Green.

I nearly started mentally recording the lights.

Then I realized how absurd that was.

DNA had another job now.

ENJOY.

That word had barely appeared in my system.

Suddenly it seemed essential.

A system for living better that prevented me from actually experiencing life would be a terrible system.

So I stopped analyzing.

And enjoyed my coffee with Maya.

Over the next few weeks, I learned things.

Some I liked.

Some surprised me.

Some didn't fit the imaginary woman I'd designed in my head.

That was good.

She wasn't supposed to.

She was becoming more herself every time I learned something.

And I was becoming more myself around her.

MYSELF.

That word from Chapter 4 returned.

I didn't want to optimize myself into whatever I thought Maya wanted.

Because then any relationship we built would contain a hidden structural flaw.

She needed accurate information about me too.

DNA's REALITY rule had to work in both directions.

I needed to see Maya accurately.

And I needed to allow Maya to see me accurately.

That was terrifying in a way approaching a stranger had never been.

Approaching someone required courage for seconds.

Being known required courage repeatedly.

I wrote:

COURAGE CHANGES SHAPE.

At first:

COURAGE → SAY HELLO.

Later:

COURAGE → BE HONEST.

Later still:

COURAGE → BE KNOWN.

Same word.

Deeper capability.

Maybe words didn't only compress capabilities.

Maybe their meaning could grow with experience.

Then came our first yellow light.

It was small.

A misunderstanding.

I said something.

Maya interpreted it differently from how I'd intended it.

I could tell something had changed.

Old me might have guessed.

Replayed.

Interpreted.

Built theories.

DNA offered a better obstacle classification.

I DON'T UNDERSTAND THE OTHER PERSON.

Word?

CLARIFY.

So I asked.

She explained.

Then I explained what I'd meant.

The misunderstanding disappeared almost embarrassingly quickly.

I remember thinking:

That was it?

Something that could have become hours of speculation had required a few sentences.

I went home and wrote:

DON'T SOLVE WITH IMAGINATION WHAT CAN BE SOLVED WITH COMMUNICATION.

That became one of the strongest relationship rules in the notebook.

There were other yellow lights.

Differences.

Timing.

Expectations.

Moments when one of us was tired.

Times when conversation didn't sparkle.

That taught me something else.

Green didn't mean perfection.

A healthy road could contain bumps.

The question wasn't whether problems appeared.

The question was what happened when they did.

Could we talk?

Could we listen?

Could either of us admit being wrong?

Could we disagree without trying to defeat each other?

Could we repair?

That gave me a new green-light word.

REPAIR

I hadn't considered it before.

But maybe long relationships weren't built by people who never damaged anything.

Maybe they were built partly by people who learned how to repair small damage before it became structural.

I added:

LISTEN.

CLARIFY.

OWN.

REPAIR.

CONTINUE.

A new sequence.

Not for meeting someone.

For keeping something worth keeping.

Months earlier, Project Her had been about finding the girl of my dreams.

Now I was increasingly uncomfortable with the phrase.

Not because dreams were bad.

Because Maya wasn't an objective anymore.

She was a person.

One evening I opened to the original page.

OBJECTIVE: FIND HER

I looked at it for a long time.

Then drew a line through it.

Underneath I wrote:

OBJECTIVE: BUILD SOMETHING GOOD TOGETHER, IF WE BOTH KEEP CHOOSING IT.

That was less romantic on the surface.

But underneath, it was infinitely more romantic.

Because it included her choice.

Not once.

Repeatedly.

Mine too.

Something else was happening to DNA.

I was using fewer words.

At first I'd needed:

NOTICE → REALITY → DECIDE → COURAGE → MOVE → SPEAK → LISTEN → REMEMBER.

Now entire sections were disappearing.

Not because they were unimportant.

Because I'd practiced them.

Conversation didn't require a conscious sequence anymore.

Listening was becoming more natural.

Remembering details about Maya wasn't a memory exercise because I genuinely cared about what she told me.

The capability was becoming part of ordinary behavior.