# Diverge, Converge, Adapt, Deliver Sat, 08 Feb 25 --- ### 1. WHY A DESIGN PROCESS MATTERS - **Definition & Analogy** - A design process is like a _recipe_ for cooking: many recipes exist for the _same dish_, and each person may follow a different approach. - A process makes it easier to navigate complexity. It is most valuable when the project is large or repetitive—like cooking huge quantities daily vs. making a single meal. - **Key Benefit** - _Reduces uncertainty_ and aligns everyone involved (clients, teammates, managers). - Prevents “just vibes” design that can go off track with endless rework. - **Actionable Point** - _Always outline a high-level plan_ when projects involve multiple stakeholders, larger scopes, or repeated tasks. --- ### 2. “MAP IS NOT THE TERRITORY” - **Concept** - A “map” (the process) is _not_ the real project—it’s only a structured guide. - Reality is messy; the path from _problem_ to _solution_ rarely follows a straight line. - **Practical Implication** - _Expect deviations._ Even with a well-defined process, requirements can shift, scope might expand, or client feedback can force major changes. - **Actionable Point** - _Build in checkpoints._ Clearly define milestones or sprints to reevaluate progress and adjust. --- ### 3. DIVERGENCE VS. CONVERGENCE - **Divergence** - Generating a wide range of ideas, possibilities, and exploration. - Commonly used in _brainstorming, moodboarding,_ or early research. - **Convergence** - Narrowing down to a final direction or concrete solution. - Used in _decision-making_ and _finalizing_ deliverables (selecting that _one_ layout, color palette, etc.). - **Actionable Point** - _Identify phases for ‘exploration’ vs. ‘decision-making’_ so your team knows when it’s time to push creativity or, alternatively, lock in the final approach. --- ### 4. DOUBLE DIAMOND FRAMEWORK - **Overview** - A popular way to visualize the _diverge–converge_ cycle _twice_: 1. **Discover** (go wide, research) 2. **Define** (narrow scope, identify exact problem) 3. **Develop** (go wide, explore solutions) 4. **Deliver** (narrow to final solution) - **Reality Check** - The “diamonds” are conceptual. Real projects zig-zag unpredictably, and each “diamond” can repeat or overlap. - **Actionable Point** - In interviews or real projects, _talk through actual steps you took_ rather than just name-dropping “Double Diamond.” Show how you researched, iterated, and decided. --- ### 5. CORE STEPS IN A TYPICAL DESIGN PROCESS _(A “map” you’ll often see in product/website work. Tailor as needed.)_ 1. **Research** - Understand the problem, market, and users. - _Example Action:_ Interview stakeholders, analyze competitor sites. 2. **Information Architecture (IA)** - Determine site structure, content hierarchy, user flows or sitemaps. - _Example Action:_ Sketch out site sections, navigation, content groupings. 3. **Wireframing** - Translate IA into low-fidelity layouts. - _Example Action:_ Draft quick sketches or use Figma to create grayscale wireframes. 4. **Copywriting** - 80–90% of any interface is text. Clarify messaging. - _Example Action:_ Write placeholder copy early; refine as you go. 5. **Visual Design** - Define the look and feel: typography, color, spacing, components. - _Example Action:_ Moodboard references, refine style, create high-fidelity comps. 6. **Prototyping & Feedback** - Build clickable versions to test flow and usability. - _Example Action:_ Conduct quick user tests or design critiques. 7. **Handoff / Implementation** - Collaborate with developers, track final build, and address any dev constraints. - _Example Action:_ Create style guides or design tokens to ensure consistency. - **Actionable Point** - Don’t get stuck forever in one step (like over-researching). _Ensure you deliver._ Keep momentum by deciding how much time you’ll allow per phase. --- ### 6. CASE STUDY: BUILDING “UI SOURCES” - **Project Brief** - A personal side project to collect mobile app flows and screen recordings for design inspiration. - **Steps Undertaken** 1. **Idea & Research** - Bought the domain, checked existing competitors, researched traffic and potential gaps. 2. **Defining the Scope** - Narrowed down from multiple features (freebies, courses, patterns) to a simpler, app-focused library. 3. **Wireframing & Visuals** - Drew rough site layouts, tested different headers, iterated on how to present each app’s screens. 4. **Content Collection** - Manually took screenshots and screen recordings of apps, wrote short captions. 5. **Development & Launch** - Used Webflow to build out pages, integrated a CMS for new app uploads, launched on Product Hunt. 6. **Feedback & Monetization** - Started free, added ads, then pivoted to a subscription model to cover costs and earn revenue. - **Key Takeaway** - The project’s real process jumped back and forth, repeatedly scoping down to something viable. - _Map vs. reality_: Even with a vision, the final shape was decided by time constraints, personal bandwidth, user feedback, and business goals. --- ### 7. COMMUNICATING AND WORKING WITH STAKEHOLDERS - **Why** - Clients, managers, or team leads want to know _timeline, deliverables, progress,_ and _how they can support_ or provide materials. - **Suggested Best Practice** 1. **Discovery Call**: Gather requirements, record everything with a tool or AI transcript. 2. **Written Proposal**: Summarize scope, timeline, pricing, and “what you need from them.” 3. **Regular Checkpoints**: Demo your ongoing work, get feedback, pivot if needed. 4. **“Map” Adjustments**: Show how you handle scope changes or unexpected discoveries. 5. **Clear Termination Clauses**: In case the project must end early, specify ownership of deliverables and non-refundable deposits. --- ### 8. ACTIONABLE TIPS & NEXT STEPS 1. **Pick & Adapt** - No single “correct” recipe. Borrow from frameworks (Double Diamond, Diverge–Converge, etc.), and _adapt_ to each project’s realities. 2. **Prevent Paralysis** - Don’t over-research or over-process. _Deliver incremental work_ that stakeholders can react to. 3. **Use Collaboration & Workshops** - Conduct short brainstorming sessions or workshops with your team or client to get aligned quickly, rather than just sending them a map. 4. **Leverage AI Wisely** - Tools like ChatGPT can _generate ideas or structures_ but _you_ remain in control. 5. **Focus on the Finish** - A process is only as good as its _output._ Ensure you actually ship, launch, or hand off your design.