From Prompting to System Design: A 10-Stage Model of LLM Users

Phase 1: Message Control Stage This stage focuses on refining the content and format of a question to obtain better answers. 1 → 2 (Reactive → Request-Oriented) Required capability: Awareness of output format Transition condition: Moving beyond simply asking questions and beginning to specify the desired output format, such as tables, summaries, or comparisons. 2 → 3 (Request-Oriented → Constraint-Oriented) Required capability: Parameter control and constraint design Transition condition: Defining length, level, restrictions, and scope to constrain the response. Note: Early stages (1–3) often overlap in practice. A single prompt may include elements from multiple stages simultaneously. 3 → 4 (Constraint-Oriented → Structured) Required capability: Question decomposition (Modular Input) Transition condition: Breaking the question into structured components such as [Goal / Scope / Constraints / Output]. Phase 2: Reasoning Management Stage This stage treats the model as a reasoning engine, managing errors and injecting structured thinking patterns. 4 → 5 (Structured → Verification-Oriented) Required capability: Critical validation and hallucination control Transition condition: No longer fully trusting the model and requiring separation of facts, assumptions, and uncertainty. 5 → 6 (Verification-Oriented → Framing) Required capability: Application of analytical frameworks Transition condition: Instead of asking isolated questions, applying a structured framework to guide how the problem is analyzed. Examples: “Analyze this in terms of cause / effect / impact” “Organize by advantages / risks / trade-offs” “Break this down into structure / flow / importance” 6 → 7 (Framing → Loop Design) Required capability: Iterative process and feedback design Transition condition: Moving beyond one-off prompts to building repeatable workflows: Input → Process → Validation → Feedback → Iteration Phase 3: System and Governance Stage This stage moves beyond individual usage toward system design and operational principles. 7 → 8 (Loop Design → Meta Design) Required capability: System architecture thinking Transition condition: Moving beyond writing prompts to designing external layers that coordinate the model’s reasoning process. 8 → 9 (Meta Design → Engine Orchestration) Required capability: Quantitative system operation and optimization Transition condition: Treating the model not as a conversational partner, but as a reasoning engine that generates, compares, and selects among multiple outputs. Operating a structured system: Candidate generation → Evaluation → Optimal selection Note: This transition occurs when the goal shifts from producing better answers to designing systems that consistently produce good outcomes. 9 → 10 (Orchestration → Interaction and Collaboration Design) Required capability: Interaction design and collaborative system definition Transition condition: Moving beyond obtaining better answers to designing how humans and AI collaborate, including role distribution and continuously improving workflows for problem-solving.