How to Force Your Brain To Think Like A Genius

Justin Sung calls the skill in this video “hypothesizing structure.” Faced with many related facts or concerns, a person deliberately proposes how they fit together rather than consider each point in isolation.

He draws on his coaching observations: experts may emphasize different things, but often give an organized account. The important claim is not that all experts arrive at one correct diagram. A structure can be useful as something to try, even when it later proves inadequate.

That changes the initial task. Instead of asking for an immediately brilliant answer, ask which grouping or relationship might make the problem easier to examine. The proposal remains open to correction.

Sung argues that unstructured problems are common outside formal education. A collection of goals and concerns arrives without a ready-made outline. Going over the same points can consume time without revealing how they influence one another.

A proposed structure supplies context: a point matters partly through its connection to other points. It gives attention somewhere to go and creates a way to ask whether the organization actually helps.

The video explains this through context and prediction error. Those are the author's account of why the exercise is useful, not a controlled result showing that this particular method guarantees a cognitive or clinical improvement.

His example asks whether a team should change its project-management software. There are ten considerations, including permissions and security, training time, cost, visibility, collaboration and workflows.

The first organization divides them into risks and benefits. Security, training and cost sit on one side; improved tracking, collaboration and execution sit on the other. Further grouping makes the page look more orderly.

That is a plausible starting point. It is not yet an answer to whether switching is worthwhile. To test the structure, Sung begins detailing the risks and comparing them with the benefits in the actual situation.

The problem appears when improving workflows is not merely a benefit. If the team cannot keep up with competitors without that improvement, leaving the workflow unchanged is also a risk.

Other supposed benefits can be inverted in the same way. The original categories overlap, and the attractive two-sided layout no longer helps Sung reason through the decision as expected.

The example does not show that every risk-benefit analysis is useless. It shows a local failure: this arrangement did not clarify this problem. A tidy picture should not be protected from criticism merely because it looks organized.

Sung says people often stop when their first structure fails. He instead asks them to remember what was being hypothesized: that this way of arranging the issue would help.

Using it produced a different result. That discrepancy is the prediction error in his explanation. It points toward changing the organization, rather than concluding that the problem cannot be understood or that the person is bad at thinking.

The skill therefore includes willingness to be wrong and another attempt. Generating many diagrams without applying them would miss the feedback step just as much as refusing to revise the first one.

Sung's second approach centers the workflow. Planning, execution, visibility, collaboration, recording and improvement become related parts of a system, rather than independent entries on two lists.

07:48View full image

This lets him ask where the bottleneck lies. Poor recording and logging may limit improvement; visibility can affect collaboration. He can then compare the cost and time of fixing the existing setup with those of adopting a new platform.

The revised map still needs testing. It does not prove that the team should buy new software, or that the drawn relationships hold in every organization. It gives a more specific comparison to investigate than the original overlapping categories.

Sung treats frameworks from books and courses as possible starting structures. Their value is in helping someone begin reasoning, not in requiring reality to fit the first template selected.

When stuck, he recommends focusing on a process: organize the parts, use that organization on the problem, identify the failure and revise it. Putting the ideas on paper can make the proposed relationships easier to inspect.

That is also an alternative to immediately labeling oneself a poor planner. The video's more useful promise is a concrete next action, not becoming a genius on command: make the thinking visible enough to learn why one structure fails and what another might reveal.