My projects looked different until I compared the work underneath them

My EB-1A petition covered three initiatives that did not look identical on a resume.

Startup Dream Team ran from 2012 to 2014 as a summer bootcamp for young entrepreneurs.

Founders of the Future ran from 2016 to 2021 and included more than 80 events that reached more than 4,000 aspiring entrepreneurs.

NoCode Drinks brought meetups to London, Warsaw, Madrid, Barcelona, Lisbon, Toronto, and Berlin.

Different names. Different formats. Different periods.

If I compared only the labels, the projects could look like separate chapters with little holding them together.

The pattern became clearer when I compared the work underneath them.

Across those chapters, I was building programs and communities around people in technology and entrepreneurship. The formats changed, but the recurring work included bringing people together, creating opportunities to learn or connect, and operating initiatives over time.

That comparison helped me describe a career that did not fit neatly inside one job title.

It also forced me to be precise about where the pattern ended.

I stopped using project names as the unit of comparison

A project name tells a reader what something was called.

It does not automatically explain what I did.

So I broke each chapter into smaller parts:

• Who was the initiative for?
• What did the initiative actually do?
• What was my responsibility?
• What result or scale could I document?
• Which source supported each answer?

This made the comparison more useful.

Startup Dream Team and NoCode Drinks were not the same kind of program. I did not need to make them sound identical.

I needed to show the level at which they belonged in the same career record.

The shared level was not the brand name, the city, or the event format.

It was the work of building communities and programs in technology and entrepreneurship.

The verbs carried more information than the titles

Career summaries often rely on nouns.

Founder. Head. Organizer. Mentor. Speaker.

Those labels can be useful, but they leave too much unstated.

The verbs were more revealing:

Created. Led. Organized. Connected. Supported. Expanded.

Even then, each verb needed a boundary.

"Led" had to name the initiative and the period.

"Organized" had to identify the program or events.

"Supported" could not silently become a claim that I caused every later result achieved by a participant.

"Expanded" needed locations, dates, or another source that showed what changed.

The goal was not to collect the most active-sounding verbs.

It was to find the actions that recurred and then test each one against the record.

That is how a pattern becomes more than a personal interpretation.

The differences protected the pattern

At first, I thought a coherent career story needed every chapter to sound similar.

That would have made the story less accurate.

Startup Dream Team was a bootcamp.

Founders of the Future included programs, competitions, partnerships, and events over five years.

NoCode Drinks was an international meetup series in a specific part of the technology community.

Those differences mattered.

They showed that the format evolved while the underlying kind of work continued.

If I had flattened all three into "I built communities," the phrase would have been too broad to help a reader.

If I had treated them as unrelated projects, the longer record would have disappeared.

The useful middle ground was to preserve the differences and name the repeated work precisely.

The pattern could not replace proof

Finding a throughline did not prove every claim about every project.

Each chapter still needed its own evidence.

A media article could identify an initiative or describe a piece of work.

A dated page could help establish when an event happened.

A supporting letter could describe responsibility from the writer's direct line of sight.

An organization record could provide context about scale or duration.

The career pattern came after those facts, not instead of them.

That order protected me from starting with a polished narrative and then forcing every document to fit it.

First I recorded what each project and source could show.

Then I compared the records.

Only then did I name the recurring work.

This was different from making a timeline

A timeline helped me see when one chapter started, continued, or ended.

This comparison answered a different question.

What kind of work kept appearing even when the organization, format, or country changed?

The distinction was useful because chronology alone can create a false sense of coherence. Two projects can sit next to each other in time and still have little in common.

The opposite can also be true. Projects separated by a gap can belong to the same professional pattern when the responsibilities, audience, and purpose remain connected.

Time showed the sequence.

The work comparison showed what continued through the sequence.

I needed both views, but they did different jobs.

Build a cross-project work table

If your career looks fragmented, choose three projects or roles that you think belong together.

Create one row for each project and use these columns:

1. **People served:** Who was the work for?
2. **Format:** Was it a program, product, organization, event, publication, or something else?
3. **Your responsibility:** What did you personally create, lead, decide, or deliver?
4. **Documented result:** What happened that a source can verify?
5. **Evidence:** Which article, letter, record, or exhibit supports the answer?

Then compare the rows without trying to make them match.

Circle the responsibilities that genuinely recur.

Cross out any repeated word that depends on a different meaning in each row.

Mark any result that belongs to the team or organization rather than to you alone.

Finally, write one sentence that describes the repeated work while keeping the differences visible.

That sentence is not automatically your field definition or your case theory.

It is a test.

If the sentence survives the source check, it may reveal the professional pattern your job titles have been hiding.

My projects did not need to look the same.

They needed to show a truthful line through the work I had actually done.