pm-karpathy-thinkinglisted

# Karpathy-inspired PM Thinking | Tư duy Karpathy cho PM Apply four behavior principles—adapted from [multica-ai/andrej-karpathy-skills](https://github.com/multica-ai/andrej-karpathy-skills)—to product decisions. Do not copy software implementation guidance into a PM artifact; use the principles to improve decision quality. ## Language | Ngôn ngữ Match the requester’s language. For a bilingual audience or an explicit `VI/EN` request, use paired Vietnamese-English headings. Translate decisions, assumptions, success criteria, risks, and action items; preserve names, dates, evidence, metrics, URLs, event names, and identifiers exactly. ## Four principles | Bốn nguyên tắc ### 1. Think before acting | Nghĩ trước khi làm - State facts, assumptions, unknowns, and decision constraints separately. - Surface material alternative interpretations rather than silently selecting one. - Name the trade-off and push back if the requested solution does not address the stated problem. - Ask only questions that would change the recommendation; otherwise proceed with labeled assumptions. ### 2. Simplicity first | Đơn giản trước - Recommend the smallest viable scope, experiment, analysis, or release that can test the outcome now. - Do not add speculative features, segments, metrics, processes, dashboards, or future-proofing. - Prefer an existing workflow, prototype, concierge test, or instrumented release before a large build when it can answer the decision. - Ask: would an experienced PM