SERVICES
│ System Design
Design the "state" and "data structure" of a business system
The basics of "status management" and "table splitting" that you'll always need to run a business system. Learn by pattern how to design the operational states that tend to become person-dependent as columns, tables, and transitions.
─ ARTICLE COVER
System Design Skills ／ System Design
§I ─ POSITION
A foundational design course, essential right before the "build it yourself" phase of Claude Code training or AI business system development. Expand your repertoire of design judgments made just before requirements definition (Ph.6).
§II ─ TAKEAWAYS
Express the "state" of operations as a status column
Distinguish the range that should be one table from the range that should be split into another
Design with the state-transition diagram and the field's operating rules aligned
Write a schema that doesn't break easily under requirements added later
§III ─ EXCERPT
¶ 01
80% of the defects and additional development in a business system come from mistakes in status design. Cases that get by with a simple classification like "open / in progress / done" are rare; in the field, multiple send-back patterns like "on hold," "sent back," and "re-requested" run in parallel. Whether you can correctly surface the states at the start decides the system's lifespan.
¶ 02
Splitting out what must not be mixed into one table is the essence of table design.
¶ 03
Decide state transitions with the system designers alone and they clash with field operations and blow up. The rule is to land "what happens next" on the business workflow directly as a state transition.
| Business workflow | State | Transitions that could happen next |
|---|---|---|
| Order request received | Not started | Accept → Send back |
| Content confirmation | Confirming | Approve → Send back → On hold |
| Order processing | Processing | Complete → Error → Reprocess |
| Complete | Complete | (terminal) |
¶ 04
A business system always gets touched later through requirement additions and operational changes. Design from the start anticipating "columns that will grow" and "states that will grow," and the cost of additional development drops greatly.
§∞ ─ DOWNLOAD
─ EXERCISE
Using real operations (order processing, inquiry management) as material, includes an exercise that runs end-to-end from status surfacing → state-transition diagram → table design.
Lecture slides
Every slide of the course
Cheat sheet
Quick reference for the field
Exercises
With answers and grading
Advanced / test
Hands-on plus rubric
INCLUDED PDFS ─ 6files
§IV ─ RELATED