Sejal Mehra

This final week focused on compiling all my entries together in this UX Toolkit, which will serve as my personal reference built from every method, framework, and insight gathered throughout this course. The goal was to create something practical, adaptable, and personally meaningful rather than polished or decorative. It’s about curating what’s useful for real-world design practice and building a framework I can continue evolving as my career progresses. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Building a toolkit reinforces the value of process. It transforms scattered notes and artifacts into a coherent system, one that can be reused, adapted, and shared. The act of organizing also deepens understanding; deciding what to keep reveals what I truly learned. It’s a way of designing for myself as the “user,” ensuring future projects start grounded in proven methods rather than reinventing each time. I’m excited to continue this process in my future classes and outside too! 𝙃𝙊𝙒 𝙄’𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • Keep the toolkit modular with Tinyfolio so it’s something that evolves as I learn new methods or technologies • Use it as a quick-start reference when I need extra help or when I randomly remember course content while designing or developing • Incorporate visual guides and checklists to make it accessible under time pressure • Align toolkit sections with stages of real projects for easy recall 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How might I digitize my toolkit into an interactive or AI-assisted version? • What methods are missing that would better support future generative AI or data-driven design work? • How can toolkits become collaborative? Besides sharing the link to my toolkit, is there a way to bring this to the workplace?

This week centered on translating experience goals into measurable outcomes. Instead of treating metrics as an afterthought, we explored how UX-KPIs can clarify what “success” truly looks like for both users and the product. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 This week deepened my understanding of how metrics shape experience design, not as vanity numbers, but as indicators of whether users are actually succeeding. In Designing Experiences, Rossman & Duerden emphasize that meaningful experiences are intentional and measurable, and KPIs help make that intention visible. For CommonGround, success isn’t “time spent in the app,” but whether users feel a sense of belonging. Mapping KPIs to moments of truth ensures that each interaction supports connection, community, and emotional resonance. Good design becomes accountable, not just intuitive. 𝙃𝙊𝙒 𝙄’𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 I’d integrate UX-KPIs early in any project by mapping them directly to the core experience goals and journey moments. That starts with identifying what success should feel like for the user, then translating that into measurable behavioral and sentiment-based indicators. For example: • Activation Metrics: How quickly users understand value and complete key onboarding tasks • Engagement Metrics: Frequency and depth of interactions with the product’s primary features • Retention Metrics: Patterns that show whether the experience is sustaining long-term value • Emotional/Sentiment Metrics: Lightweight check-ins that capture trust, confidence, or satisfaction Embedding these into research plans, prototypes, and testing cycles helps validate concepts earlier and ensures design decisions ladder up to clear, accountable outcomes. It also turns metrics into a design tool, not just another reporting tool or dashboard, so teams can iterate with intention and evidence. 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How do I balance quantitative and qualitative KPIs effectively? • How can we as designers quantify feelings of connection or emotion without overburdening the user with surveys or friction points? • Explore how to visualize KPIs in a dashboard that reflects both engagement data and sentiment, keeping user success visible and actionable for the entire team.

This week focused on refining all previous artifacts, such as personas, stories, touchpoints, and ecosystems, and turning them into a cohesive experience journey map. The goal was to visualize the end-to-end user experience and capture how people interact with a product or service across channels, motivations, and emotional states. This map connects our earlier “zoomed out” work (like ecosystem mapping) with detailed, moment-by-moment understanding. It’s not just about steps but about empathy, flow, and recognizing where value is created or lost. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Journey mapping unites everything we’ve explored in design so far (people, context, emotion, and action). It also reveals the “why” behind every touchpoint and helps identify pain points, opportunities, and “moments of truth.” As Kalbach describes, maps bring coherence to complexity by showing how context and motivation evolve over time. This process also mirrors the principles in Designing Experiences by Rossman & Duerden, where every interaction contributes to a broader narrative of engagement and meaning. For our CommonGround project, this step was about connecting the story of local belonging to the tangible moments that make it real. 𝙃𝙊𝙒 𝙄’𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • Synthesizing artifacts: Combining personas, concept story, and touchpoints into one visual framework • Map across layers: Including user actions, emotional states, channels, and opportunities • Designing for emotion: Using visual cues (icons, colors, emojis) to show shifts in motivation • Iterating with stakeholders: Treating the map as a living document to test assumptions and refine moments that matter most 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How can journey maps evolve into live tools that connect directly to data or analytics? • What is the best balance between detail and clarity? How do you know when the map has enough information? • How might AI tools eventually automate parts of journey mapping while keeping the human empathy intact?

Understanding how users move between communication channels and engage with key touchpoints to create cohesive, cross-channel experiences. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Every experience is built on moments called touchpoints, where users interact with a product, service, or community. Orchestrating Experiences (Risdon & Quattlebaum) highlights that while channels often form silos, great design bridges them into a unified flow. Recognizing “moments of truth,” those emotionally charged or high-value interactions, helps ensure users feel consistency and connection at every stage. 𝙃𝙊𝙒 𝙄’𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • Map the full ecosystem of user touchpoints, from app notifications to in-person events • Design for smooth channel transitions (e.g., push notification → event page → physical meetup) • Keep tone, visuals, and emotional intent consistent across every channel • Identify “moments of truth” where small improvements could make a big impact 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How can I balance digital efficiency with real-world warmth across channels? • What makes certain touchpoints more emotionally resonant than others? • How do we measure continuity across hybrid (digital + physical) experiences? • How do we prioritize which touchpoints truly drive long-term engagement?

This week focused on visualizing how users move through a product or service experience. By mapping out touchpoints, emotions, and goals, we can see the full story of how people interact with a design. Experience maps connect empathy mapping, jobs-to-be-done, and ecosystem thinking, showing where value is created and where friction stands in the way of meaningful experiences. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Experience mapping brings all the previous UX layers (personas, empathy maps, and jobs-to-be-done) into a single, holistic view. As Kalbach explains in Mapping Experiences, these maps reveal how people achieve goals through and around your product. It helps us as designers see not just the interface but also the ecosystem of interactions that shape user perception. In Designing Experiences, Rossman & Duerden emphasize the emotional arc within those touchpoints, showing how each moment contributes to participation, engagement, and meaning. Mapping experiences ensures those emotional beats are intentional and human-centered, not accidental. 𝙃𝙊𝙒 𝙄'𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • For CommonGround, mapping a resident’s journey from discovery → onboarding → first event → sustained engagement • Identifying each touchpoint (notifications, event posts, chats, meetups) and the emotional shifts (curiosity → connection → belonging) • Using experience maps to align the design team on which touchpoints deliver the most value and where friction exists • Layering in JTBD insights to ensure each phase addresses a clear user motivation 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How can emotional touchpoints be visualized more effectively in a digital experience map? • What tools best capture evolving experiences, such as users’ behaviors or contexts changing? • How can maps bridge UX research insights and actual implementation in design sprints?

Understanding user stories and storyboarding deepens the connection between design intent and user experience. Together, they bridge the analytical and emotional sides of design: the “what” and the “why.” 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 User stories translate human needs into actionable design requirements, keeping users at the center of product development. Storyboarding complements this by visualizing the user's journey, showing how moments unfold emotionally and contextually. As we saw with Designing Experiences (Rossman & Duerden), experiences are lived narratives, and storyboarding helps us see them. When paired with user stories, it ensures that features serve a purpose within a meaningful journey rather than existing in isolation. 𝙃𝙊𝙒 𝙄'𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • In mobile app design (like our group project of CommonGround), use user stories to guide functional features: “As a neighbor, I want to discover local gatherings so that I can connect with people nearby.” • Use storyboards to visualize emotional context, such as what the user feels before, during, and after using the app • Combine both to align design, development, and storytelling so the experience feels coherent and intentional 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How can storyboards evolve alongside iterative design changes? • What happens when user stories conflict with business goals? How do we reconcile them? • How might visual storytelling be used to communicate experience intent beyond product teams?

Understanding how people, environments, technologies, and relationships interact to shape and evolve an experience. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Ecosystems define the context of an experience. No product, service, or interaction exists in isolation, which is almost always influenced by the larger network around it. As Rossman and Duerden note in Designing Experiences, every experience involves a balance between structure and spontaneity, individual and environment. Knowing the ecosystem helps ensure a design aligns with real-world dynamics rather than idealized assumptions. For me, thinking ecosystemically bridges design and development. It’s about building systems that adapt, connect, and sustain. 𝙃𝙊𝙒 𝙄'𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • Experience mapping: Identify all stakeholders, environments, and tools involved in a user journey • System modeling: Visualize how digital touchpoints interact (e.g., app ↔ community ↔ data platform) • Sustainability thinking: Design for long-term relationships, not just single interactions • Community design (e.g., Common Ground): Map users, local spaces, and communication flows to create an ecosystem that supports authentic connection 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How can ecosystem mapping better inform technical architecture and UX strategy? • What methods best reveal unseen connections like social, emotional, or cultural factors? • How does the ecosystem shift when centering different entities (e.g., user vs. business vs. environment)?

Using game design elements such as points, progress bars, levels, and feedback loops to enhance user motivation and create more emotionally resonant experiences. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Gamification bridges motivation psychology and experience design. It’s not just about adding “fun” but designing meaningful engagement loops that make participation feel rewarding. As Designing Experiences (Rossman & Duerden) notes, powerful experiences are co-created, and gamification encourages that by inviting users into active participation and flow. When done well, it has the power to transform everyday interactions into moments of accomplishment, curiosity, and joy. 𝙃𝙊𝙒 𝙄'𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • Learning tools: Use streaks or milestones (like Duolingo) to reinforce consistent engagement • Productivity apps: Layer in goal-tracking and feedback loops to make progress visible • UX research or onboarding: Frame exploration as “leveling up” to help users gain mastery step by step 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How can I ensure rewards feel intrinsically motivating, not manipulative? • Where’s the line between meaningful challenge and cognitive overload? • How might gamification and flow theory work together to sustain long-term engagement and emotional connection?

Collaborative whiteboarding tools like Miro and Mural for brainstorming and mapping ideas. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 These tools let me capture messy ideas visually, structure them in real time with others, and revisit them later. Unlike static notes, digital canvases help me show relationships between ideas, prioritize, and cluster patterns. 𝙃𝙊𝙒 𝙄'𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • For early ideation: sticky-note-style brainstorming with classmates or colleagues • For mapping: organizing research findings into themes or creating quick journey maps • For alignment: bringing technical and non-technical teammates into the same digital space 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • Which tool fits better for long-term documentation (Miro vs. MURAL)? • How can I balance free-form creativity with structured frameworks in these tools? • Are there ways to integrate outputs into dev/design workflows (e.g., export to Jira, Figma)?

This Tinyfolio will be my personal UX Toolkit, a running collection of methods, frameworks, and reflections I’ll build week by week. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Instead of just taking notes, I want a living reference I can use later in my career, something I can return to when I need inspiration, frameworks, or reminders of what worked well. Using Tinyfolio also keeps it lightweight, visual, and shareable. This overall approach aligns with Rossman and Duerden’s view of experience design as a process of intentional orchestration, which allows for building a framework that evolves through reflection, iteration, and shared understanding. And Tinyfolio keeps it lightweight, visual, and shareable. 𝙃𝙊𝙒 𝙄'𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • One entry per week (Modules 2–9) • Consistent structure: What I’m Adding → Why It Matters → How I’d Apply It → Future Learning • Visuals and templates wherever possible (screenshots, diagrams, sketches) • Final submission in Week 10 as a polished but practical resource 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • What format will make this toolkit most useful long-term: portfolio style, internal reference, or public resource? • How can I layer in my own voice and style so it feels authentic, not just academic?

Hello! 👋🏼 A little bit about me is that I’m a software developer-designer who bridges creativity and functionality to craft intuitive, people-first experiences. Based in New York, I approach every project as both a maker and a systems thinker equally interested in how things look, feel, and work. My goal this quarter is to expand my UX toolkit by blending design frameworks with technical implementation and documenting what I learn in a way that’s both practical and personal. 𝙒𝙃𝙔 𝙄𝙏 𝙈𝘼𝙏𝙏𝙀𝙍𝙎 Understanding who I am as a designer and developer shapes how I approach problem-solving. This weekly reflection sets the foundation for how I’ll connect theory to practice and not just study UX methods but also explore how they intersect with development, design systems, and real-world application. 𝙃𝙊𝙒 𝙄'𝘿 𝘼𝙋𝙋𝙇𝙔 𝙄𝙏 • Ground each weekly entry in both creative and technical perspectives • Connect insights from UX readings to real-world tools I use (Figma, React, AI design workflows) • Treat this Tinyfolio as a living document that evolves with my skills and identity 𝙁𝙐𝙏𝙐𝙍𝙀 𝙇𝙀𝘼𝙍𝙉𝙄𝙉𝙂 / 𝙌𝙐𝙀𝙎𝙏𝙄𝙊𝙉𝙎 • How can I best merge technical precision with emotional design? • What patterns define my creative identity, and how do they show up in my work? • How might this toolkit become part of my long-term design–dev portfolio?