Why Google Picks the Hardest Problems Instead of Assigning Solutions

Problems, Not Prescriptions

Most leaders hand teams a solution and ask them to build it.

Google flipped that. Leadership named the hardest unmet need, then trusted the team to find the answer.

Search relevance was one such need. Monetizing search was another.

The output was PageRank and AdWords. Neither was specified from the top.

What Counts As Hard

Not every gap deserves this treatment.

The pattern works when the need is significant and unmet, meaning nobody has a good answer yet, including leadership.

Search relevance qualified. Ranking pages well was genuinely unsolved.

If the solution is already obvious, naming it is faster. Reserve problem-framing for the open questions.

PageRank: Relevance As A Problem

The stated need was search relevance. Results had to be genuinely useful.

Leadership did not describe an algorithm. It described the gap.

PageRank emerged as the team's answer to that gap.

Notice the order. Problem first, mechanism second, and the mechanism belonged to the people closest to it.

AdWords: Money As A Problem

The second named need was monetization. Search had users but no revenue engine.

Again, leadership framed the question rather than the product.

AdWords was the team's answer.

One pattern, two very different domains. That is the signal that the pattern is about how direction is set, not about search technology.

Why Trust Is The Engine

Naming a hard problem only works if you genuinely hand over the solution.

Trust is not a nice-to-have here. It is the mechanism.

If leadership keeps second-guessing the approach, the team is really just executing a hidden spec.

The problem statement stays fixed. The path to it stays open.

Spotting It In Your Work

Read your last project brief.

If it names a build, you assigned a solution. If it names a gap nobody has closed, you framed a problem.

Explaining this to a colleague is simple: leadership owns the problem, the team owns the answer.

The test is whether the team could return with something leadership never imagined, and that would count as success.

When a need is significant and genuinely unresolved, should leadership normally name the need rather than prescribe the solution?

• Yes
• No

Answer: Yes

Yes. Problem-framing is useful when no good answer exists yet, so the team can discover an approach leadership did not specify.

For Google's two examples, PageRank addressed _____, while AdWords addressed _____.

Answer: For Google's two examples, PageRank addressed search relevance, while AdWords addressed monetization.

PageRank was Google's answer to making search results useful and relevant. AdWords was the team's answer to the need for search revenue.

A company knows customers struggle to complete a task, but leadership has no proven way to fix it. Which brief best follows the problem-framing approach?

• Build a three-step workflow with email reminders.
• Reduce customer difficulty completing the task.
• Copy the competitor's task-completion feature.
• Implement a mobile dashboard for the task.

Answer: Reduce customer difficulty completing the task.

The second brief names a significant unmet need without dictating the mechanism. That preserves the team's opportunity to find the answer.