> Term

Problem Statement

A clear, concise description of the specific issue or pain point that needs to be solved, stripped of proposed solutions.

Detailed Explanation

A problem statement is the anchor of any technical initiative. It forces teams to articulate exactly what is broken or missing before rushing into architecture design or coding. A good problem statement defines the current state, the desired state, and the gap between them, ensuring that the engineering effort actually addresses a real user or business need rather than just satisfying a desire to use new technology.

Why It Matters

Jumping straight to solutions without a well-defined problem statement usually results in building the wrong thing perfectly.

Common Failure Mode

Baking the desired solution into the problem statement (e.g., 'The problem is we don't have Kafka' instead of 'The problem is data sync takes 24 hours').

Practical Example

Before migrating to a new cloud provider, the architect insists on a problem statement detailing exactly how the current provider is failing to meet uptime and cost requirements.

Production Manifestation

A massively over-engineered distributed cache built to solve a 'performance issue' that was actually just a missing database index.

Frequently Asked Questions

What is Problem Statement in short?

A clear, concise description of the specific issue or pain point that needs to be solved, stripped of proposed solutions.

What is the most common failure mode?

Baking the desired solution into the problem statement (e.g., 'The problem is we don't have Kafka' instead of 'The problem is data sync takes 24 hours').

AI Summary

A clear, concise description of the specific issue or pain point that needs to be solved, stripped of proposed solutions. Jumping straight to solutions without a well-defined problem statement usually results in building the wrong thing perfectly.