디자인 포트폴리오 구성·첨삭

# Story Architecture## Contents1. Portfolio-level structure2. Single-project arc3. Multi-project selection4. Page budgeting5. Planning tables## Portfolio-level structureUse this default sequence for a full portfolio:1. Identity and thesis2. Selected work index3. Flagship case study4. Contrasting case study5. Short supporting project or process appendix6. Capabilities, role clarity, contactThe first project should prove the capability most relevant to the audience, not simply be the newest project.## Single-project arcUse an evidence-driven arc rather than a chronological diary:1. **Hook** — final tension, product promise, or meaningful constraint.2. **Brief** — user, context, objective, role, timeline, constraints.3. **Evidence** — observations, research, benchmarks, or existing-product failures.4. **Insight** — the design implication distilled from evidence.5. **Divergence** — meaningfully different concepts, not cosmetic variants.6. **Decision** — selection criteria, trade-offs, and chosen direction.7. **Development** — form, CMF, ergonomics, architecture, interaction.8. **Reality check** — prototype, test, manufacturing, cost, safety, or maintenance.9. **Iteration** — what changed and why.10. **Resolution** — final experience, product views, specification intent.11. **Reflection** — outcome, limits, next validation step, personal learning.Do not force every project through all eleven beats. Omit unsupported sections and explain gaps honestly.## Multi-project selectionBuild a capability matrix before choosing projects:| Capability | Project A | Project B | Project C ||---|---:|---:|---:|| Research and insight | Strong | Medium | Low || Form and CMF | Strong | Strong | Medium || Engineering collaboration | Medium | Strong | Low || Prototyping and testing | Strong | Medium | Strong || Manufacturing awareness | Medium | Strong | Low || Storytelling and leadership | Strong | Medium | Medium |Keep the smallest set that covers the desired role. Flagship projects need depth; supporting projects may use 3-6 pages.## Page budgeting| Format | Typical pages | Guidance ||---|---:|---|| Interview cut | 8-15 | One flagship project, fast proof || Single case | 12-18 | Full decision chain || Student application | 20-32 | 2-4 projects plus process range || Senior job portfolio | 18-30 | Role clarity, impact, collaboration || Client capability deck | 12-24 | Outcomes, process, risk control |Reduce pages by removing repetition, not evidence.## Planning tables### Evidence map| Claim | Artifact | Level | Source | Gap/action ||---|---|---|---|---|| Grip was uncomfortable | Test notes + photo | E2 | Applicant | Add participant count |### Story table| Page | Question answered | Message | Evidence ||---:|---|---|---|| 05 | Why this direction? | Access required one-handed operation | Observation photos |### Layout plan| Page | Layout | Theme | Slot | Reason ||---:|---|---|---|---|| 05 | ID03 | Light | 3:2 evidence grid | Compare observations |