All AI techniques for the Deliver phase of Will's "AI-Assisted UX Workflow". The real goal of this phase is not to hand off specs to developers, but to distill the project into a presentable portfolio page plus interview talking points. Therefore, all AI techniques center on two things: "rearranging information into a story-telling visual/layout" and "clearly explaining the human-AI collaboration process". Coverage includes: ① Generating multiple layout options (1:1 text extraction from old layout → content direction exploration → direction selection → final image output) ② Optimizing layouts / migrating visual styles (style transfer from reference images, only changing the skin without altering the bones) ③ Layout-to-code & Figma mockup (single-page image → restoration prompt → HTML → reverse-engineer editable source file via Figma Make) ④ Infographic semantic extraction + visual redraw (strip visuals to retain only logic → 5 styling directions → wireframe → apply style) ⑤ Metric-driven design review using the will-ux-metric-teardown skill (reverse-engineer business model/North Star metric, identify issues by Tier 1-3 priority) ⑥ Showcasing AI capabilities and value in projects (for each UX phase, output "what AI did / interview talking points / what evidence to put in PPT"). Each section provides reusable prompt skeletons + Why reasoning + counterexamples. Interpersonal collaboration rules for design review meetings (roles / receiving feedback / turning feedback into actions) are covered in [[google-ux-testing-iteration]]; this article focuses specifically on prompts and workflows for using AI to run layout generation/code conversion/metric review/value articulation.
17 curated articles from Nielsen Norman Group’s “Organization and Design Process” collection, covering “what actions you take and what you produce during the design process.” Five major themes: ① Discovery Phase — Discovery Mindset (focus on problems rather than solutions, counter Anchoring effect + Confirmation Bias, 3 tactics: Reframe the Goal/Highlight Unknowns and Assumptions/Icebox Favorite Ideas), 7 tips for successful discovery (secure buy-in first/clarify roles and norms/write a problem statement that does not imply solutions/cluster and vote on unknown priorities/timebox to counter planning fallacy, 7-week sample plan: weeks 1–2 framing + weeks 2–4 research + weeks 3–5 analysis + weeks 6–7 opportunities and ideation/all team members participate in research/collaborative analysis and synthesis with How-Might-We), CSD Matrix (Certainties “We know”/Suppositions “We believe” testable/Doubts to be researched, rows grouped by user·business·technology·people·process·status·priority, goal = convert doubts and suppositions into certainties), 4 steps to kick off a new UX project (enter kickoff with a question list/expose information gaps through verbal discussion/schedule based on gaps/pave the way for the future, adapted for Agile + Waterfall); ② Wireframes and Collaborative Sketching — 4 steps to draw wireframes (set aspect ratio 1024x768/1920x1080·navigation and search·largest elements: headings in thick lines, body text in thin lines, images marked with crosses·details: dropdowns, radio buttons, buttons), magic formula to get stakeholders to sketch (thick Sharpie markers + small 8-grid paper + time limit of 5 minutes per sketch + intentionally ugly examples = relaxed sketchers), Promptframes (wireframes + generative AI prompts, replacing lorem ipsum placeholder text, 6 steps: define context, role, organization, goal, tone + write recording prompts + run + collaborate to test and optimize + iterate + manual refinement, 2–3 variants, for internal use only, not for senior leadership); ③ Prototype Fidelity — 7 decision questions for low-fidelity vs. high-fidelity, clickable vs. static prototypes (can all responses be predefined/can it be trialed multiple times/can all issues be fixed/is the design stable/is someone acting as the computer/is page flow the focus/do dynamic changes need to be observed), why test prototypes (save cost/avoid risk/iterate); ④ Design Specs and Deliverables — Dual design spec package (Figma design file: interaction flows·visuals·layout grids·components·real content·accessibility tab order and alt text; Linear development task ticket: goal·scope including inclusions and exclusions·assumptions·success metrics·Figma link·notes) + 4 tips for alignment with developers (invite developers early/leave time for comments/prepare tradeoffs/record and sync updates), 50+ deliverable glossary terms (affinity diagram/antipersona/archetype/CSD matrix/empathy map/experience map/Kano model/MoSCoW/RICE/RACI/service blueprint/persona including proto/qualitative/statistical/prototype/paper prototype/promptframe/sketch test...), most commonly used deliverables (survey of 86 practitioners: static wireframes/interactive prototypes 67%/flowcharts/site maps/usability reports; select by audience: management views interactive prototypes + usability reports + journey maps·clients view interactive prototypes 67% + high-fidelity mockups 47% + competitive analysis 34%·developers view interactive prototypes 63% + flowcharts 55% + style guides 51%); ⑤ Expert Review/Workshops/Storyboards/Surveys — Expert Review (three types: heuristic evaluation/independent design critique/expert review, external perspective is more objective + uncovers blind spots, 5 components: strengths list·issues list·severity high/medium/low·improvement suggestions·best practices, complementary to usability testing, conduct regular reviews every 2–5 years), Workshop Facilitation (4 goals: full and equal participation Diverge-Converge/promote mutual understanding/inclusive collaborative decision-making/shared responsibility, 6 principles: listen·inclusive space·welcome improvisation·authentic and transparent·do not give advice·embrace constructive conflict, toolkit = materials + activities post-up/affinity diagram/forced ranking/role-play/Playback + techniques silence/balancing/connecting), Storyboard (three elements: scenario + visuals + captions, differences from journey maps, 6 steps, low-fidelity sticky notes can be rearranged), In-Process Surveys (4 stages of the design cycle: discover/explore/test/listen, corresponding types for each stage: discovery phase qualitative surveys + stakeholder surveys + diary studies/exploration phase statistical persona surveys + competitor customer surveys/testing phase post-task SEQ single ease question + post-test SUS System Usability Scale 10 items/listening phase NPS 0–10·CSAT 1–5·CES, counterexample = mistakenly thinking surveys are fast and simple). Audience = non-technical product managers, terms explained in-line, decision-oriented (when to use/how to choose/counterexamples), all numbers retained.
