Below is the step‑by‑step workflow that Mutlu Torun outlines. Think of it as a loop you run repeatedly until the product reaches its target performance thresholds.

| Phase | Goal | Key Activities | Typical Deliverables | |-------|------|----------------|----------------------| | 1️⃣ Discover | Identify real user problems & define measurable goals. | • Stakeholder interviews
• Contextual user research (field studies, surveys)
• Persona creation
• Problem statement & success metrics | • Persona cards
• Problem‑goal matrix
• Success‑Metric Dashboard | | 2️⃣ Ideate | Generate solution concepts that address the discovered problems. | • Co‑creation workshops
• Sketching & storyboarding
• Prioritization matrix (impact vs effort) | • Idea backlog
• Prioritized concept list
• Rough storyboards | | 3️⃣ Prototype | Build low‑fidelity artifacts to test the highest‑priority ideas. | • Paper prototypes, wireframes, or clickable mock‑ups
• “Wizard‑of‑Oz” simulations for complex interactions | • Set of prototypes (often 2‑3 per cycle)
• UD Canvas – hypothesis, metrics, test plan | | 4️⃣ Test | Validate hypotheses with real users and collect quantitative/qualitative data. | • Usability testing (moderated or remote)
• A/B testing if digital
• Metric collection (e.g., task success, error rate, SUS) | • Test reports (observations, raw data)
• Updated UD Canvas with results | | 5️⃣ Iterate | Translate findings into actionable design changes and plan the next cycle. | • Insight synthesis (affinity mapping)
• Decision‑making meeting (what to keep, modify, discard)
• Update backlog & roadmap | • Revised design specifications
• New hypothesis for next cycle
• Updated project timeline |

Tip: The UD Canvas (a single-page visual template) is the glue that holds the cycle together. Keep it visible to the whole team—on a wall or a shared digital board—so that everyone can see the current hypothesis, metrics, and status at a glance.

| Question | Answer | |----------|--------| | Do I need a lot of design tools? | No. The method thrives on speed. Paper, whiteboards, and a simple wireframing tool (Figma, Balsamiq) are enough for the early phases. | | Can I apply UD to an already‑launched product? | Absolutely. Treat the existing product as the “baseline” and run the UD cycle to incrementally improve specific user flows. | | How many cycles are typical? | It varies. For a MVP, 2–3 cycles may be enough. For complex enterprise systems, you might run 5+ cycles, focusing on different modules each time. | | What if the metrics never reach the target? | Re‑examine the hypothesis: maybe the problem statement is wrong, or the target is unrealistic. Pivot if necessary—UD encourages you to change direction based on evidence. |

Aşağıdaki adımlar ile UD Metodu hakkında yasal ve güvenilir bilgiye erişebilirsiniz:

Mutlu Torun, eğitim danışmanlığı ve alternatif öğrenme teknikleri üzerine çalışmalar yapan bir isim olarak bilinir. Kendi geliştirdiği veya uyarladığı UD Metodu’nun uygulayıcılarından biri olduğu düşünülmektedir. Bazı kaynaklara göre Torun, bu metodu özel kurslar ve seminerler aracılığıyla yaygınlaştırmıştır. Ancak, hakkında akademik veya resmi yayınlar sınırlıdır; bu nedenle bilgilerin çoğu forumlar ve kişisel bloglardan derlenmiştir.