The worst designer I've ever worked with was also the most productive.

This ambitious young designer produced more canvases in a single day than more experienced designers would produce in a week. The leadership adored him. They saw the speed, the volume, the energy of the "beast mode"—and mistook it for value creation.

Under pressure to sign a potentially life-saving contract with a major client, they praised their results without understanding the value or assessing the risks.

By rewarding speed and volume at the expense of quality and necessity, they created a dangerous feedback loop: the more he produced, the more praise he received—and the more resistant he became to a rational, user-centered design process.

What they failed to see was a growing pile of unaudited, untested, and misaligned design work—a ticking time bomb of inconsistency, technical debt, and costly rework that would ultimately cost the team far more than it saved.

Flooding the backlog

He produced so much work that we lost the ability to evaluate it.

What began as an impressive impulse turned into an uncontrollable torrent. Screens were appearing in the backlog faster than anyone could analyze them— without criticism, without usability testing, without standards.

Most of it went completely unnoticed by the team: there was no oversight, no alignment, no time to check if any of them could solve a real problem or if they would work within our design system.

This work accumulated pending tasks and confused the teams — impossible to manage, impossible to question, overwhelming the design process with volume.

The work went straight from Figma to Jira, inflating the pipeline with decisions that no one had the time or space to challenge, creating an illusion of progress. The pile grew. The thinking became thinner.

This is what political agitators call "flooding the zone": overloading the space until discernment and critical thinking collapse. It's a powerful tactic for destroying scrutiny and accountability.

In design, pure productivity is equally corrosive. Flood a team with results and no one else will know what good is.

Build the right thing and build the right thing.

John Maeda defines power as Do less to achieve more. . But this ambitious young designer did so much and kept himself so busy that he lost his power, as well as any notion of how a good design should be.

He didn't question the product documentation. He didn't read the results of user research. He didn't conduct design reviews or usability tests. Ironically, he frequently complained that he was "too busy" for the process—as if the process were a luxury, not the work.

His initial ideas became his final results. Repeatedly.

Design is not just production. It is discernment — the discipline of questioning, testing, refining, and making choices.

As Marty Cagan says, great teams build the right thing, and they build it correctly. That means not just doing... something , But to do the right thing, at the right time, for the right reasons.

Something that works for people's real needs at a fair price.

Flooding the area is easy. It looks impressive. It generates promotions. But it's not progress. It's just production. And without critical thinking, production becomes theater—things that look beautiful, but solve nothing.

Good designers slow down when necessary. To clarify the problem. To align the team. To create results that matter.

When someone boasts about how much they've sent, don't applaud. Ask where that money has led. Ask who it helped. Ask what would have happened if they had done nothing. That's the real measure. Everything else is a waste.