I tested my petition by reading only the headings

My EB-1A cover letter was long enough that I could not judge its structure by reading one polished paragraph at a time. A paragraph could sound clear on its own while sitting in the wrong section. Two adjacent sections could make the same argument with different words. A missing step could stay hidd

My EB-1A cover letter was long enough that I could not judge its structure by reading one polished paragraph at a time.

A paragraph could sound clear on its own while sitting in the wrong section. Two adjacent sections could make the same argument with different words. A missing step could stay hidden because the sentences around it were smooth.

So I used a simpler test.

I read the headings without the paragraphs.

The outline of my cover letter moved from a summary of qualifications to the criterion sections, then to final merits, my plan to continue work in the field, the prospective benefit to the United States, and the conclusion.

Inside a criterion, the headings narrowed again. In the leading-role section, one branch addressed the organization and another addressed my role inside it.

That outline did not prove the case.

It showed whether the document gave each part of the case a clear place to be proved.

The outline exposed the route

When I read only the body text, I could get absorbed in a single claim or source.

The heading-only view forced me to look at the route a reader had to follow.

Could someone see where the summary ended and the detailed proof began?

Could they tell that final merits asked a broader question than an individual criterion?

Could they find the section about future work without searching through the evidence history?

Could they see where the petition stopped proving past work and started explaining what came next?

Those questions were easier to answer from the outline than from a paragraph-level edit.

The test was not whether every heading sounded impressive. It was whether the sequence made the document navigable.

A child heading had to narrow the parent

A useful subheading should make its parent more specific.

My leading-role section first named the criterion. It then identified Founders of the Future within Founders Forum Group. Below that, separate headings addressed the organization's standing and my role.

Each level narrowed the question.

That gave me a structural check:

  • The criterion heading named the evidence category.
  • The organization heading named the subject of the claim.
  • The next level separated the organization's record from my responsibility.
  • Smaller headings grouped the facts that belonged to each part.

If a subheading merely restated its parent, it did not help the reader move deeper into the argument.

If a subheading introduced a new project, field, or conclusion without a bridge, the outline showed the jump immediately.

The hierarchy had to carry meaning, not just numbering.

Sibling sections needed comparable jobs

I also compared headings that sat at the same level.

Under original contributions, the major subsections covered Startup Dream Team, Founders of the Future, and NoCode Drinks. Those were comparable units: three initiatives discussed under the same part of the argument.

A heading about one initiative's detailed outcome would have been out of place beside two headings that only named projects. The levels would no longer match.

This matters because an uneven outline often creates uneven prose.

One section becomes a full argument. The next becomes a label followed by several pages. Another becomes one narrow example that should have lived lower in the hierarchy.

The heading-only read made those differences visible before I spent time smoothing transitions.

A heading could not replace the claim

There was another trap.

A heading can announce a conclusion that the paragraphs underneath have not earned.

Words such as **impact**, **recognition**, **significance**, and **leadership** can sound as if the section has already done its work.

The heading still needs a testable body beneath it.

For each section, I asked:

  1. What question does this heading promise to answer?
  2. Which facts answer that question?
  3. Which sources support those facts?
  4. Does the last paragraph actually resolve the question named at the top?

If I could not answer those four lines, changing the heading would not fix the gap.

The outline could reveal the problem. The evidence and prose still had to solve it.

Missing structure often looked like a writing problem

Some paragraphs were difficult to edit because they were carrying two different jobs.

A paragraph might begin by describing an organization and end by describing my personal responsibility. Another might move from an individual article to a claim about recognition across thirteen years.

I could keep shortening those sentences and still feel that the section wandered.

The outline suggested a different fix: separate the questions.

Once the organization and role had their own places, each paragraph became easier to write. Once criterion evidence and final-merits synthesis lived under different headings, I did not need one paragraph to do both.

The problem had looked like word choice.

It was often information architecture.

That distinction saved me from polishing a paragraph that needed to be moved or split.

The table of contents became a quality check

My cover letter included a table of contents because the document had multiple levels and major sections.

That table also gave me a compressed view of the petition.

I could scan it for three problems:

  • **A missing step:** the argument moved from one question to another without a section that explained the connection.
  • **A duplicate step:** two headings promised substantially the same discussion.
  • **An uneven step:** headings at the same level described units of very different size or purpose.

The table of contents did not need to tell the whole story.

It needed to make the path through the story intelligible.

If the path looked confused in one page of headings, more prose would usually make the confusion longer.

Run the heading-only audit

Make a copy of your current outline.

Delete every paragraph and keep only the headings in their numbered order.

Next to each heading, write one sentence that begins:

**This section helps the reader answer ______.**

Then check the structure:

  1. Does every child heading narrow the question above it?
  2. Do sibling headings perform comparable jobs?
  3. Does any important question appear in two places?
  4. Does the document jump from criterion proof to a broader conclusion without a visible bridge?
  5. Could a reader locate the detailed proof, the whole-case synthesis, and the future-work discussion from the outline alone?

Do not rewrite the headings first.

Use the answers to decide whether a section should move, split, merge, or stay where it is.

Then return to the paragraphs.

Good prose makes a section readable.

A clear outline makes the whole petition readable in the right order.

Subscribe to Vislify Journal

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe