Why Problem Statements Aren't Enough

(letters.unchartedpathbreakthroughs.com)

7 points | by mooreds 4 days ago

2 comments

  • ericyd 21 minutes ago
    I just can't take tech-adjacent advice from someone who can't properly size an icon in 2026
  • oliculipolicula 2 days ago
    TFA has 2 Qs aimed at building trust-culture:

    >Who has the missing context?

    >If the work succeeds, what changes beyond “the project shipped”?

    As a total rando trying to develop a (possible) nothing-burger I call expert embarrassment, I'd derive 2+2 corresponding what-ifs:

    What if

      1. nobody in the org does?
    
      2. the project ships yet nothing changes?
    
    Excuse my extra what-ifs for being kind of sly takes on the class of "Maserati Problems"

    https://dfccyyqjngn5p3.archive.ph/uWeuT/2f4f3d465f8a85a41e89...

      3. What if we don't market our solution?
    
      4. but it still blows up in our face?
    
    (MPs being defined by the context that makes their technicality _seem_ reasonable only long after you'd have acquired one, but your ability to answer them matters _now_

    Here's a real world instance, related much better than I ever could

    https://www.cringely.com/2026/05/28/the-permission-slip/

    )