Step-by-Step Guide to Applying Kidlin's Law at Work

Kidlin's Law states that writing a problem clearly reduces it by half, as it uncovers root causes and actionable paths. This guide turns that principle into a repeatable process for tackling work challenges like project delays or team conflicts.​

Step 1: Capture the Raw Problem

Start with the vague frustration you're feeling — jot it down without editing, even if it's emotional like "This launch is a disaster." Give yourself 2-3 minutes to brain-dump symptoms, frustrations, and context on paper or a doc. This externalizes mental clutter so you stop spinning.

Step 2: Rewrite for Clarity

Transform the raw notes into one precise sentence: Who, what, when, where, why (as you know it), and impact. Example: "The Q1 feature launch is delayed by two weeks because API integration testing lacks clear ownership, risking customer churn." Aim for specificity — no jargon or assumptions.​

Step 3: Break It into Components

List the problem's elements: causes (e.g., unclear roles), effects (e.g., missed deadlines), constraints (e.g., team bandwidth), and unknowns (e.g., dependencies). Use bullets or a table for structure. This reveals what's solvable now versus what needs more data.​

Step 4: Identify Quick Wins and Next Actions

From the clarified breakdown, spot immediate fixes (e.g., "Assign API testing owner today") and bigger steps (e.g., "Schedule cross-team sync"). Prioritize by impact and effort — often, 50% of the problem dissolves here.​

Step 5: Test, Iterate, and Track

Act on the top actions, then revisit the written problem in 48 hours to update or close it. If it persists, rewrite Step 2 with new info. Tools like Linear, Notion, or a simple notebook amplify this for PMs.

‍