The officer is not inside your industry
One mistake I had to watch for in my EB-1A petition was writing like the reader already understood my world. They did not.
One mistake I had to watch for in my EB-1A petition was writing like the reader already understood my world.
They did not.
The officer was not inside the London startup ecosystem.
They were not inside the no-code community.
They were not automatically tracking why a founder program, a university judging invitation, a media feature, or a community initiative mattered.
That context had to be on the page.
Not too much context.
Just enough.
Industry shorthand is dangerous because it feels obvious to you.
"Founder community" may mean a real network with events, selection, outcomes, and institutional partners.
To a stranger, it may sound like a meetup.
"No-code" may describe a serious technology movement with builders, tools, companies, and public events.
To a stranger, it may sound like a hobbyist label.
"Judging" may mean evaluating the work of entrepreneurs in a structured program.
To a stranger, it may sound ceremonial unless the role is explained.
The fix is not to over-explain everything.
The fix is to translate the term into evidence language.
For each insider phrase, add the missing context:
- What was it?
- Who was involved?
- What was my role?
- Why did it matter in the field?
- Which document proves it?
If the answer takes a full page, the claim may be too muddy.
If the answer takes one clean sentence, the petition gets stronger.
My rule would be:
Assume the officer is intelligent, busy, and outside your industry.
Do not talk down to them.
Do not make them decode your ecosystem either.
Translate just enough so the evidence can do its job.