Transforming the Quality of Your Work with 70% Output

Why does the clock stop at your desk?

Sometimes, do you find yourself pushing too hard to achieve 100% perfection?
However, that obsession with that 'last step' can actually stop the clock for the entire organization.

While you are adjusting the font of a document by a single point, a colleague at the next desk is already moving the project forward with a 'draft'.

You get so caught up in the layout of a document that you are late to realize the direction of the essential content is off.

The tragedy of having a beautiful slide deck you stayed up all night to create dismissed in the next morning's meeting because 'the premise is wrong to begin with' is not uncommon in the workplace.

Time spent stalled in one person's hands may be nothing more than an 'information void' for the team.

70% is a baton pass of trust

Releasing work at 70% completion is by no means cutting corners. Instead, try viewing it as a 'baton pass of trust' to your colleagues in the next stage of the process.

Output that has been polished into a finished product is difficult for the recipient to provide input on.
Conversely, if there is a little 'white space' left, it becomes easier for those around you to contribute their opinions, such as 'maybe it would be better to change this part'.

Aim for 120% by mixing in the perspectives of the entire team rather than one person's 100%.
To do that, you need the strength to intentionally release work into the world while it is still unfinished.

Are you protecting the results, or yourself?

It might be scary to expose unfinished work.
'Will people think my work is sloppy?'
'Will I be evaluated as incompetent?'
These anxieties trap us in a suit of armor called perfectionism.

However, please think about it for a moment.
Are you trying to protect the quality of the deliverable, or are you protecting yourself from getting hurt?

It is important not to think of your output as being synonymous with your own self.
It is merely 'material for verification'.

Just as prototypes are iterated quickly in the IT world, our daily work is also a repetition of 'hypothesis and verification'.

When you let go of your attachment, the quality of your work will begin to improve with surprising ease.

Intentionally lowering the 'resolution' of your mind

A tip you can practice starting now is to create a system that lowers the 'hurdle for publication' within yourself.

For example, start by developing the habit of sharing work with the magic phrase, "This is just a rough draft."
Just by doing this, the expectations of the recipient are appropriately managed, and your own psychological safety is secured.

Also, instead of judging by quality, it is effective to set boundaries by time, such as "submitting whatever is done in one hour."

Your boss and those around you are actually waiting for "speedy consultation" rather than your "perfection."
The atmosphere of the organization should also change little by little.

An arrow shot returns in a different form

The 70% finished product that you courageously let go of will gain the nourishment of team feedback and grow into a form you could never have imagined on your own.

If you take off the heavy armor of perfectionism, not only will your work speed increase, but your own breathing should become much easier.

Why not start by showing someone an unfinished email or a document in progress just as it is?

That one step will surely show you a new landscape of work.

[Random Notes] Four Concepts to Improve Productivity

In the business world, especially in the IT industry where a sense of speed is required, the idea of "abandoning perfectionism and submitting at 70%" is not mere cutting corners, but can be called "strategic resource allocation."

1. The mechanism by which perfectionism lowers productivity

I will organize the background of why aiming for "100%" becomes a risk.

- Law of Diminishing Returns
The effort to go from 70% to 100% often takes several times more effort than the effort to go from 0% to 70%, and the return on investment (ROI) drops significantly.

- Delayed Feedback
The more you hold onto work out of a desire for perfection, the later you receive course corrections from others, and the rework becomes massive if it turns out the "direction was wrong" in the end.

- Psychological Hurdles (Delayed Start)
The pressure of "I must do it perfectly" delays starting the task, which ultimately causes a drop in quality right before the deadline.

2. The benefits brought by "70% completion"

These are the concrete positive effects of releasing and sharing at 70%.

・Agile Course Correction
By sharing prototypes or outlines at an early stage, you can frequently align with stakeholders and reach the final "correct answer" faster.

・Securing Mental Bandwidth
Setting a goal of "70% to start" lowers the psychological barrier to beginning a task, making it easier to enter a flow state.

・Collaboration Based on "Incompleteness"
At 70%, it is easier for others to provide input, creating room to integrate the collective wisdom of the team into the output.

3. Redefining "Output Quality"

We redefine "quality" not just as "beauty in the details," but as "functionality" in a business context.

・Speed as an Element of Quality
In modern business, especially in the IT sector, there are many situations where a 70% result delivered tomorrow is more valuable than a 100% result delivered in a month.

・Being "Verifiable"
By making it public, you gain "objective data" in the form of market or user reactions. Improvements based on this data are the shortcut to achieving true quality.

・Purity of Core Value
In the process of narrowing down to 70%, you must distinguish what is "truly essential to convey (functionality)," which sharpens your message.

4. Concrete Rules for Releasing at 70%

These are practical guidelines for having the courage to release your work.

・Separating "Framework" from "Details"
If the logic and structure (framework) are 70% complete, release or consult on it even if the decoration or fine-tuning (details) are incomplete.

・Introducing Timeboxing
Instead of judging by quality, set constraints based on a timeline, such as "release whatever is done in X hours."

・Declaring a "Draft"
By explicitly stating, "This is currently a 70% draft for discussion" when releasing, you ensure psychological safety and avoid the risk of negative evaluation.