Building transforms your validated planning decisions into tangible designs and functional solutions. This phase is where you create wireframes, develop prototypes, and provide the documentation development teams need to bring your user-centered vision to life.
Good building puts your research into action, using both quantitative and qualitative data to inform design decisions. Every layout choice, interaction pattern, and visual element should connect back to user needs identified in Discovery and validated during Planning.
Think of building like constructing from a blueprint. Your planning phase created the structure, now you’re creating the detailed specifications and visual representations that development teams can implement.
By focusing on user-centered building, you can:
Usability Consulting and Research
ITS offers UI, web, and app consultations to help Yale departments enhance user experience, accessibility, and meet Yale standards.
The build phase is where UX designers transform abstract planning concepts into concrete design artifacts. You’re not just making things look good. You’re creating detailed specifications that ensure user needs remain central throughout development.
Your role involves translating research data and validated structures into wireframes, prototypes, and documentation. Every design decision should reference the qualitative insights from user interviews and the quantitative patterns from analytics or survey data.
Use your Discovery research and Planning validation to inform every design decision. When choosing how to organize a page, reference card sorting results. When prioritizing features, cite user interview quotes and task analysis data.
Quantitative data shows you what users do (where they click, how long tasks take, which paths they follow). Qualitative data explains why (their motivations, frustrations, and mental models). Combine both types of insights to create designs that work.
Document the research rationale behind design decisions so teams understand it’s not just aesthetic preference. It’s user-centered problem solving backed by evidence.
Wireframes and prototypes communicate your design intent to developers, stakeholders, and other team members. These artifacts need enough detail to preserve user experience decisions while remaining flexible enough for technical constraints.
Low-fidelity wireframes focus on layout, hierarchy, and functionality without visual design details. High-fidelity prototypes include interactions, transitions, and closer-to-final visual design. Choose the right fidelity level based on what you need to communicate or test.
Your specifications become the reference point during development. Clear, detailed design documentation prevents user experience compromises that happen when teams guess at your intent.
UX designers don’t disappear once designs are “done.” You’re actively involved during implementation, answering questions, reviewing builds, and ensuring the final product maintains user-centered design intent.
Development always encounters constraints and tradeoffs. Your job is helping teams find solutions that preserve user experience quality even when original designs need adjustment for technical or resource reasons.
Review implemented features against user needs, not just against design specifications. Sometimes the best solution emerges during development, and your role is ensuring it still serves users effectively.
Design documentation translates your planning and research into detailed specifications that development teams can implement. Create wireframes that show page layouts and content hierarchy based on your validated information architecture. Develop prototypes to demonstrate interactions and test with users before development begins.
Implementation support means staying actively involved as development teams build your designs. Review builds against user needs, provide actionable feedback, and problem-solve when technical constraints require adjustments. Test throughout implementation to catch issues while they’re still easy to fix.
With designed and implemented features taking shape, you’re preparing to launch your solution to real users. But the build phase doesn’t mark the end of UX work. Now it’s time to validate that your design decisions actually work in practice.
Validation is when you finally get to test whether your built solution meets user needs in real-world contexts. This phase confirms whether the assumptions you made during planning and building were correct, or if adjustments are needed.
Your documented designs and research-backed decisions provide the baseline for validation. As you move into this phase, shift focus to measuring how users actually interact with your solution, gathering feedback on what works and what doesn’t, and identifying any gaps between your design intent and user reality.
Testing with real users in authentic scenarios reveals whether your solution truly serves their needs. Validation findings inform whether you can confidently launch, or if iteration is needed to address usability issues before wider release.
