YouMind
Sign in

Submitting Early: Who Loses and Who Gains?

@smark_x
JAPANESENov 19, 2026
375K
246
14
5
467

TL;DR

Submitting early doesn't guarantee good feedback if you show everything. By hiding non-essential elements like colors and photos, you force reviewers to focus on critical structural issues, leading to faster and more valuable corrections.

"It's still a rough draft, but I wanted to get your eyes on it early..." There is always one person in every workplace who sends over drafts with this note. Because showing it early = being a competent worker is the most widely accepted "correct" way to submit work. However, because this understanding lacks nuance, I believe more people are finding that submitting early actually lowers their evaluation.

First, even if you submit at the same speed, the feedback you receive falls into two types. If you submit everything included, you only get corrections on colors and photos. On the other hand, if you submit with everything except one key point left vague, you get feedback on the structure within 5 minutes.

This difference arises not from the speed of submission, but from the "scope of what you show."

I currently work with freelancers and often review their drafts. For example, suppose I ask two freelancers to draft a service introduction deck. Person A submits everything included. Person B submits with everything hidden except one point.

The conclusion is: If you want feedback on the structure, do not show anything else. Reviewers comment on the easiest thing to critique among what they see. In other words, the content of the feedback is determined by the submitter, not the reviewer.

Person A: Submits Everything

A: "It's still a rough draft, but I wanted to get your eyes on it early."

Me: "Thanks. The cover color might be a bit dark."

Me: "Also, the photo on slide 3 could be brighter. The sentence endings mix 'desu' and 'da'."

A: "How is the structure?"

Me: "Yeah, I think it's good."

Two days later, after reading the version where colors and photos were fixed, my first comment was to redo the structure from scratch.

Me: "...Who is this deck for again?"

Andy Grove, former CEO of Intel, wrote in the first chapter of "HIGH OUTPUT MANAGEMENT": Find and fix problems before you've invested effort in them.

高橋雅人 - inline image

This book is really interesting.

The example used is eggs: find and discard rotten eggs at the procurement stage, before customers find them. This is exactly the case here.

A did the right thing by showing it early, following this philosophy. But during that first early look, I was focusing on the cover color. When A submitted the restructured version, they added a line to the note:

Please only check the structure. Colors and photos are still placeholders.

Me: "Structure is OK. ...But I might change this photo."

A: "...Yes."

Even though I was asked to check the structure, my eyes got stuck on the photo again.

British historian C. Northcote Parkinson wrote an essay satirizing meetings called "Parkinson's Law of Triviality" (or the bicycle shed effect). Committees approve nuclear reactor plans quickly, but when discussing a bicycle shed—something anyone can visualize—everyone chimes in and argues endlessly.

In the context of drafts, colors and photos are the "bicycle sheds." Anyone can offer opinions on them, so as long as they are visible, feedback will gather there.

高橋雅人 - inline image

Person B: Hides Everything Except One Point

On the other hand, B's draft looks different the moment you open it. Only the heading arrangement is in black text; the body is gray bands, photo spots are gray boxes labeled "Photo," and the cover is black and white.

The note attached was:

The only thing I want you to look at is "Who is this deck for?" Colors, photos, and phrasing are intentionally left as placeholders (gray). Once this is decided, I will fill in the content and resubmit by Thursday.

Me: "Swap slides 2 and 5, and state who it's for first."

It took me 5 minutes to write the reply. Since the only visible thing is the heading arrangement, the only thing to think about is the arrangement. Still, I almost commented on the color.

Me: "What color are you planning for the cover?"

B: "Colors will be reviewed together on Thursday."

B simply noted my comment down.

B: "Next, I'll submit just the numerical data inside."

Me: "With this method, each reply only needs to address one point."

B's order of revealing layers is: Structure → Numerical Data → Phrasing → Colors & Photos. What we want to catch before investing effort is structural misalignment. Colors can be saved for last, as fixing them likely only involves the cover and a few slides.

高橋雅人 - inline image

Later, A asked me:

A: "But isn't hiding things dishonest?"

Me: "When shown everything, reviewers probably feel they must return something for every part."

Me: "To give feedback on structure, you have to think of alternative proposals. For color, you can just say 'it's dark.'"

I wasn't slacking off when I commented on the cover color either. Given everything, I tried to respond to everything, resulting in feedback starting from the easiest parts.

By hiding parts, reviewers don't need to search for where to give feedback. Deciding what to show is the submitter's job.

If you tend to submit everything (Type A), try making everything except the structure gray for the first round, and add a note specifying "the one thing I want you to look at" and "I will resubmit later."

If you already hide parts (Type B), it's even better to decide the order of revelation as "Structure → Numbers → Phrasing → Colors."

For more practical techniques, see this article.

https://x.com/smark_x/status/2119912361662538023

I also explain timely topics and "hints effective for tomorrow's work" structurally and clearly.

  • Overthinking prevents action.
  • Perfectionism or inefficiency leads to constant time shortages.
  • Wanting to blame "lack of sense" when hitting walls.
  • Work hasn't become easier despite using AI.

Since I have these traits myself, I use "logical thinking" to systematize work and make it easier while dealing with all these issues. I post daily, so please follow if you like. → @smark_x

Remix in YouMind

Turn one viral article into a full content workflow

Collect the source, decode the pattern, create assets, draft the story, and distribute from one AI workspace.

Explore YouMind
For creators

Turn your Markdown into a clean 𝕏 article

When you publish your own long-form writing, images, tables, and code blocks make 𝕏 formatting painful. YouMind turns a full Markdown draft into a clean, ready-to-post 𝕏 article.

Try Markdown to 𝕏

More patterns to decode

Recent viral articles

Explore more viral articles