strategic-analysislisted

# Strategic Analysis ## Overview When multiple implementation approaches exist, choosing the wrong one has compounding costs. Strategic analysis forces explicit comparison before commitment, replacing gut decisions with reasoned trade-off evaluation. The goal is not to find the perfect approach. It is to make the trade-offs visible so the decision-maker (the user) can choose with full information. **Depth mandate**: If your options are two flavors of the same approach, you haven't analyzed deeply enough. ## The Iron Law ``` NO IMPLEMENTATION WITHOUT AN APPROVED DECISION ``` Implementation creates momentum — once code is written, the team gravitates toward finishing it rather than reconsidering the approach. Comparing options before coding ensures the chosen approach reflects deliberate evaluation rather than whatever came to mind first. This is especially critical for decisions that are hard to reverse, such as data model choices and integration patterns. Committing to an approach without explicit comparison and user approval compounds wrong choices. Make trade-offs visible before writing code. ## The Process ### Step 1: Identify Options List at least 2 concrete approaches. For each option, provide: - **Name**: A short descriptive label - **Description**: What this approach does in 1-2 sentences - **Example**: A concrete code sketch or structural outline If only one option seems viable, you have not looked hard enough. There is always an alternative — even if it