I treated every critical-role claim as two separate cases

The leading or critical role section of my EB-1A petition looked like one argument.

While drafting it, I found it more useful to treat it as two.

The first case was about the organization.

What was it? What had it done? What reliable evidence helped a stranger understand its standing?

The second case was about me.

What was my role? What was I responsible for? Which documents or people with direct knowledge could verify that responsibility?

Those two cases met in the same section, but they were not interchangeable.

A recognizable organization could not prove my role.

A senior-sounding title could not prove the standing of the organization.

Separating the two made the gaps easier to see before I tried to hide them inside polished prose.

I built the organization file first

An organization name can feel self-explanatory when you know its history.

The officer does not share that history.

So I needed a compact record that could answer basic questions without relying on reputation alone:

• What was the organization or initiative?
• When did it operate?
• What did it do?
• What scale or outcomes could I document?
• Which institutions, publications, or public records supplied outside context?

Founders of the Future gave me concrete facts to work with. It ran from 2016 to 2021, held more than 80 events, reached more than 4,000 aspiring entrepreneurs, and launched at 10 Downing Street.

Those facts helped define the initiative.

They did not automatically prove everything I wanted to say about it.

The launch location supplied institutional context. The event count described activity over time. The number of people reached described scale. Dates showed duration.

Each fact had a narrower job than the adjective "distinguished."

That was useful. A collection of traceable facts was easier to evaluate than a paragraph that kept repeating a conclusion.

Then I built the role file

The organization file could explain the setting.

It still could not explain my personal responsibility inside that setting.

For that, I needed a second record:

• My exact role and the period I held it.
• The decisions, programs, or work I personally led or created.
• The difference between a team result and my contribution to it.
• The source for each responsibility claim.
• A person or document with direct knowledge where the public record stopped short.

This is where a title became a starting point rather than a conclusion.

"Co-founder" identified a relationship to the initiative.

It did not, by itself, show which work I led, which decisions I made, or why my role mattered to what the initiative achieved.

I had to add verbs.

Created. Led. Organized. Decided. Built.

Then I had to test each verb against a source.

Could a program page verify it?

Could a dated public record verify it?

Could a supporting letter from someone with direct knowledge explain the part that the public documents could not show?

If the verb was broader than the source, the sentence needed to become narrower.

That edit protected both the claim and the people who did the work with me.

Team results stayed on the organization side

The hardest facts to place were often the most impressive ones.

More than 80 events and more than 4,000 people reached are useful numbers. They describe what Founders of the Future accomplished.

They do not automatically describe what one person did.

I could connect my role to those results, but I could not silently convert a shared outcome into an individual achievement.

So I kept the statements separate while drafting:

1. **Organization result:** What did the initiative accomplish?
2. **Personal responsibility:** What part did I lead, create, or deliver?
3. **Verification:** What evidence supports the relationship between the first two statements?

That structure prevented two opposite mistakes.

The first was overclaiming the work of a team.

The second was becoming so careful that my own role disappeared.

Accuracy required both levels to remain visible.

The same document could not always do both jobs

Some evidence naturally belonged in one file more than the other.

A media article about an initiative might help establish its public context while saying little about my day-to-day responsibility.

A supporting letter might describe my role in detail while offering limited independent evidence about the organization's broader standing.

An event page might verify a date, program, or location without explaining who made the key decisions.

That did not make any of those documents useless.

It meant I had to stop asking one exhibit to prove the entire section.

I found it cleaner to label each source by job:

• organization identity
• organization scale
• outside recognition or context
• role and dates
• personal responsibility
• connection between the responsibility and the result

Once the labels were visible, duplication became easier to cut.

Two articles proving the same event happened did not solve a missing role claim.

Another letter praising my work did not replace a missing public source for the organization's history.

The gap determined the next document I needed.

I joined the two cases one claim at a time

Only after the files were separate did I combine them into prose.

The order was simple:

1. Identify the organization or initiative.
2. Give the few facts that establish the relevant context.
3. State my role and the period clearly.
4. Describe one responsibility at a time.
5. Put the supporting source close to the sentence it could verify.
6. Explain the connection without turning a team result into a personal one.

This produced a section that moved between two subjects without blurring them.

The organization did something worth understanding.

I held a particular responsibility inside it.

The evidence showed both parts.

That is more disciplined than starting with a sentence such as "I played a critical role at a distinguished organization" and then making the rest of the paragraph repeat the labels.

The labels belong in the argument.

The facts have to carry it.

A two-column audit

Before drafting a leading or critical role section, open a blank page and draw two columns.

Label the left column **Organization**.

For each organization, record:

1. Identity and time period.
2. Documented work, scale, or outcomes.
3. Outside sources that provide context.
4. The exact exhibit for every important fact.

Label the right column **Role**.

Record:

1. Your title and dates.
2. The responsibilities you can describe precisely.
3. The team results those responsibilities connect to.
4. The source that verifies each connection.

Then look for uneven rows.

If the organization column is full and the role column is vague, another paragraph about the organization's reputation will not fix the section.

If the role column is detailed and the organization column contains only a name, another responsibility bullet will not explain the setting.

If both columns are full but the sources do not support the connection between them, the bridge still needs work.

That was the value of treating one criterion as two cases.

It replaced one broad question, "Does this sound important?", with smaller questions I could answer from the record.

First prove the setting.

Then prove the responsibility.

Then show how they connect without asking either side to do the other's job.