5 Minute UX

5mUX
  • 0.0 (0)
  • Kurse
  • Täglich

5mUX is practitioner-grade UX training in five-minute lessons, structured around how adults actually learn. Every lesson teaches one concept or skill you can apply immediately, available as text, audio, or video. Pick the modality that fits your moment; the rigor stays the same.

  1. vor 3 Std.

    URL Problems That Hurt Search Ranking

    Apply a diagnostic framework to identify URL duplication risks in CMS output. Distinguish between structural cloning and legitimate content variation to ensure search engines index single, stable paths.

  2. vor 4 Std.

    Making the Case for Content Strategy

    Learn to position content strategy as a core project pillar rather than an afterthought. You will apply a decision framework to ensure content creation, curation, management, and measurement align with business goals and brand strategy from the start.

  3. vor 2 Tagen

    Writing a Design Proposal to Protect Both Sides

    Learners will structure a formal agreement that secures payment terms and defines client obligations for resource access. This capability allows designers to mitigate risks of scope creep and non-payment by establishing a clear paper trail before work begins. Learning Objective: By the end of this lesson, learners will be able to draft a UX design proposal that explicitly defines scope, payment schedules, and client resource obligations to protect both parties. Transcript Core Functions of the Design Agreement The design agreement does three distinct things before any actual work begins. First, it acts as a paper trail that backs up the designer if misunderstandings arise later. Second, the signature itself creates a formal agreement on who handles specific aspects of the project, what is included in the scope, and the estimated price. Third, and most importantly, it defines the terms that protect both the designer and the client in the event that project conditions change. This protection is about operational stability as much as legal liability. When a client signs, they are explicitly accepting responsibility for providing timely access to their resources, which prevents the designer's timeline from slipping due to missing information. It also establishes financial security, ensuring the designer gets paid for completed work even if the client loses funding and kills the project. Without these defined terms, the relationship relies on goodwill, which tends to evaporate the moment a deadline is missed or a budget gets cut. The primary function of this document is to remove ambiguity from the start. It transforms a handshake into a shared understanding of expectations, roles, and financial commitments. By locking in these definitions, both parties can move forward with the confidence that their interests are secured. This clarity sets the stage for the specific content elements that need to be included next. Key Points: The proposal serves as a paper trail to back up the designer in the event of misunderstandings Signing formally agrees to who handles specific aspects, what is included in scope, and the estimated price The primary function is to define terms that protect both the designer and the client if project conditions change Mandatory Content Elements Five things belong in the agreement, and each one closes a specific gap. First, the terms of the relationship between the client and the vendor. Second, the payment schedule, which dictates when and how funds move. Third, a clear identification of who is handling what aspects of the project, so responsibility sits with a named party rather than between two people who each assumed the other had it. Fourth, the specific aspects of the project included within the proposal. This is where your UX work gets its boundary, separating it from development, content, and whatever else a client might reasonably assume is coming. Fifth, the price estimated for that included work. Those five turn a conversation into a document both sides can hold each other to. The designer gets a defence against scope creep, because anything outside the listed aspects is visibly outside. The client gets a defence against a surprise invoice, because the estimate attaches to a named body of work. Both protections hold on their own terms, which is what makes them worth writing down. Key Points: Terms of the relationship between the client and the vendor The payment schedule for the client Clear identification of who is handling what aspects of the project Specific aspects of the project included within the proposal and the price estimated for that work Risk Mitigation and Client Obligations The moment a client accepts the project, the proposal must make them aware of their obligations to the project’s success. You specifically address the risk that if the client does not provide timely access to their resources, the designer’s timeline will slip. This clause forces the client to commit to the workflow, ensuring that delays are not treated as the designer's fault. Next, you protect against the risk of non-payment if a client loses funding and kills the project. Without a formal agreement, the designer runs the risk of not getting paid for work already completed. The proposal ensures the designer is paid for work already completed even if the project is terminated. This financial security is non-negotiable for your business stability. These protections are the specific mechanisms that define the terms of the relationship between the client and the vendor. By defining who handles what, you create a clear boundary. This clarity prevents the most uncomfortable situations in project history, keeping the working relationship professional and predictable. Key Points: Address the risk that if the client does not provide timely access to their resources, the designer’s timeline may slip Protect against the risk of non-payment if a client loses funding and kills the project Ensure the designer is paid for work already completed even if the project is terminated Scope Definition Template When you sit down to draft the scope of work, you need a specific template to anchor the boundary. Start by stating the engagement in one sentence: the client's company name, then the phrase "to provide all services required to build", then the project type. That sentence establishes the overall context and the client's specific goal, telling them exactly what the final deliverable is supposed to be. Next, state your limitation in the same shape: your company name, then "will focus solely on", then the specific user experience aspects, then the client's website. The word "solely" is critical here because it draws a hard line around your expertise. It clearly separates your user experience design work from other components like development or content strategy, so the client knows which parts of the build are yours. By using this two-part structure, you apply the scope-of-work template to delineate the specific UX design aspects included in the project. It protects you from scope creep and protects the client from over-promising. Once this boundary is set, you can move to the next step of the drafting sequence. Key Points: Use the structure: 'We were approached by [Client Company name] to provide all services required to build [Project Type]' Specify the limitation: '[Your Company name] will focus solely on the [user experience design Aspect(s)] of the [Client Company name]’s website' This template clarifies the boundary between the designer's UX focus and other potential project components Drafting Sequence and Execution The moment the handshake happens, you begin drafting. This is the window where momentum is highest, and the agreement deserves the right amount of time rather than the bare minimum. The urgency is practical. The sooner the proposal is approved and signed, the sooner work can begin, and there is a direct link between the ink drying and the clock starting. Wait, and the delay compounds into a later launch date. Signing is also the prerequisite for getting paid. Until there is a signature you are working on a handshake, which is the most unstable foundation in business. So the decision in front of you is whether to start drafting today, or wait until the scope feels perfectly clear. Clarity arrives through the drafting rather than before it, so the waiting buys nothing. Your job is to apply the scope-of-work template and delineate the specific user experience design aspects included in the project. You have defined the scope, identified the risks, and set the terms. Now you execute. Draft it now. Key Points: Begin drafting immediately after the handshake or acceptance to maintain momentum Recognize that the sooner the proposal is approved and signed, the sooner work can begin Treat signing the proposal as the prerequisite for beginning to get paid for the work

  4. vor 2 Tagen

    Time-Aware Research: Catching Users Mid-Task

    You will define time-aware research as the practice of intercepting users while they are actively performing a natural task. You will distinguish this just-in-time approach from in-person methods that require users to recreate needs in unfamiliar spaces. Learning Objective: By the end of this lesson, learners will be able to define time-aware research and describe how it captures real-time user context compared to in-person methods. Transcript Intercepting Users in Their Natural Context Time-aware research intercepts users while they are actively performing a natural task. This approach captures the context of the user's need in real-time, preserving the specific details that often vanish in traditional settings. In-person methods typically require users to leave their typical context, such as their home or work, and recreate their needs in an unfamiliar space. This separation creates a gap between the original intent and the observed behavior. When a user has to think of a task scenario on demand, the data becomes less reliable. Time-aware research makes it easier for users to describe the specific need that brought them to the site. The context is already present, so the description feels natural rather than forced. This immediacy is the core advantage of the method. By catching users mid-task, you get a clearer picture of their actual journey. The user does not have to reconstruct their experience from memory. Instead, they simply explain what they are doing right now. This direct access to current intent is what distinguishes this approach from standard in-person interviews. The next step is understanding how tools like Ethnio manage this interception process. Key Points: Time-aware research intercepts users while they are actively performing a natural task This approach captures the context of the user's need in real-time In-person methods typically require users to leave their typical context and recreate their needs in an unfamiliar space Time-aware research makes it easier for users to describe the specific need that brought them to the site The Interception Mechanism and Recruitment Flow Ethnio intercepts users who have arrived at a website for their own natural reasons. The tool immediately asks the user if they are interested in participating in research. This initial query respects the user's time and intent. Next, the system runs an active screening process to determine if the visitor qualifies. Only those who meet the specific criteria move forward in the flow. Unqualified users are released back to their tasks without further interruption. Finally, qualified users are directed to a facilitator. The facilitator then asks the user to participate in an interview or usability test. This three-step sequence ensures that only the right people engage in deeper conversation. The mechanism relies on catching the user mid-task, preserving the context that brought them to the site. This direct path from interception to facilitation keeps the research process tight and relevant. Key Points: Tools such as Ethnio intercept users who have come to a website for their own natural reasons Step 1: The tool asks the user if they are interested in participating in research Step 2: Users who qualify based on active screening are directed to a facilitator Step 3: The facilitator asks the user to participate in an interview or usability test Logistical Advantages of Remote Interception Remote research removes the biggest friction points of in-person scheduling. You eliminate travel time entirely, which means no more missed appointments or scheduling snafus that derail a day. It’s a lower-commitment way to reach a large number of participants, because they don’t have to clear a calendar or drive across town. This method is particularly useful for target users in other countries or those with frenetic schedules, encouraging higher participation rates. In contrast, scheduling in-person research requires more time and logistics management for both the facilitator and the participant. By keeping the process remote, you capture users mid-task without the logistical overhead that often causes drop-off. Key Points: Remote research eliminates travel time and avoids scheduling snafus and missed appointments It is a lower-commitment way to reach a large number of participants This method is particularly useful for target users in other countries or those with frenetic schedules Scheduling in-person research requires more time and logistics management for both the facilitator and the participant Planning Constraints and Analysis Ratios Planning this kind of study requires you to map out the entire operational footprint before the first session begins. You need to decide on the specific tools, define your budget and timeline, and identify where the highest risks lie if you proceed without user insights. This also means setting clear goals, determining how you will recruit and screen participants, and securing the necessary space, equipment, and software. Furthermore, you must define the primary content topics and choose a capture method that accounts for the number of people involved and their specific tools. The most critical constraint in your planning is the time required to process what you gather. The data volume from these sessions can be daunting, so a common guideline for analysis time is a one-to-three ratio. This means that for every hour of research conducted, you should plan for three hours to get through the analysis and write up your findings. This dedicated time allocation provides the space you need to find actionable findings and create an appropriate report to deliver to the customer. By applying this one-to-three time ratio guideline to estimate your analysis and reporting effort, you ensure your team has the bandwidth to transform raw observations into clear, usable insights that drive the next phase of the project. Key Points: Planning must address tools, budget, timeline, risk, goals, participants, resources, content, and capture method A common guideline for analysis time is a 1:3 ratio For every hour of research conducted, plan for three hours to get through the analysis and write up findings This time allocation provides space to find actionable findings and create an appropriate report Team Involvement and Stakeholder Advocacy Invite your team and the customer to observe the live session. Each session requires full attention, interest, and care to observe behaviors and capture conversations, so having stakeholders watch in real time ensures no detail slips through the cracks. The best user research sessions are inclusive of other team members and the customer as observers, turning a solitary analysis task into a shared discovery. When the results are delivered, those same observers often become the biggest advocates, because they witnessed the user struggle firsthand rather than reading about it in a report. You can also run these sessions in parallel with your recruitment efforts, since schedules are tricky and communication is rarely as fast as desired. This keeps the momentum going while you still fill the remaining slots. So when you sit down to plan that first intercept, remember that the people watching the screen are just as important as the person on the other end of it. You caught them mid-task, and now you’re handing the whole team the same live view that made the insight stick. Key Points: Each session requires full attention, interest, and care to observe behaviors and capture conversations The best user research sessions are inclusive of other team members and the customer as observers Team members and customers who participate as observers sometimes become the biggest advocates when results are delivered It is possible to host research sessions in parallel to recruitment efforts

  5. vor 2 Tagen

    The Meeting Justification Test

    Apply the five-question verification framework to determine if a meeting is the most efficient channel for obtaining approvals. Distinguish between necessary face-to-face interactions and tasks solvable via email or phone to reduce project friction. Learning Objective: By the end of this lesson, learners will be able to apply the five-question verification framework to justify or reject scheduling a meeting. Transcript The Efficiency Threshold for Scheduling A meeting is only valid if the necessary information or approvals cannot be obtained through more efficient channels. Before you schedule anything, you must verify that those specific results cannot be achieved by picking up the phone, sending emails, or using instant messages. This step is critical because the approach chosen must be the most efficient and effective way to get the required results. If a simple call gets the approval, a full meeting is a failure of process. There is a specific trap to avoid here. Do not use email as a crutch to avoid face-to-face or asynchronous one-to-one meetings when genuine interaction is required. The channel must match the complexity of the decision. If you need nuanced feedback or real-time debate, a text message won't cut it. But if the goal is just a yes or no, stop and send the email. This efficiency threshold is the foundation for the five-question verification framework we will use next. Key Points: A meeting is only valid if necessary information or approvals cannot be obtained through more efficient channels Verify that results cannot be achieved by picking up the phone, sending emails, or using instant messages before scheduling Avoid using email as a crutch to avoid face-to-face or asynchronous one-to-one meetings when interaction is required The Five Verification Questions Diane Brewster-Norman, who created the Franklin-Covey Meeting Advantage workshops, frames the decision around five specific verification questions. You ask them to determine if a meeting is truly necessary before you commit anyone’s time. The first question is whether the total cost of the meeting justifies the advantages of holding it. This forces you to weigh the expense against the specific outcome you need. Next, you check if the people who can make decisions are available to attend, which is really about whether the timing is right. If key decision-makers are absent, the meeting often stalls. Then you ask if the purpose of the meeting is clear. You can’t move forward without a defined goal for the conversation. The fourth question asks if the necessary information is already available. If the data is sitting in an inbox, a meeting is redundant. Finally, you must ask if alternatives to holding a meeting have been considered. This ensures you’re not defaulting to a calendar invite when a quick email or phone call would solve the problem. Answering yes to these questions confirms that a meeting is the right channel. This verification process sets the stage for choosing the most efficient way to get the approval you need. Key Points: Does the total cost of the meeting justify the advantages of holding it? Are the people who can make decisions available to attend (is the timing right)? Is the purpose of the meeting clear? Is the necessary information available? Have alternatives to holding a meeting been considered? Decision Framework for Channel Selection Once you have answered the five verification questions with a yes, you have established a clear need for a meeting. This confirmation is the trigger for the next phase: selecting the right channel and timing. When you know your attendees are in the office, prioritize early time slots for the session. This strategic choice maximizes the likelihood of full participation, which directly supports the cost-justification argument you built earlier. However, the definition of a meeting is broader than a scheduled block on a calendar. Any discussion about a project, whether conducted via technology with distant teams or in person, constitutes a meeting. This means even a quick sync requires preparation, such as drafting a punch list of questions or a brief agenda. By treating every project discussion as a formal meeting, you ensure that the necessary information is always available and the purpose remains clear. This discipline prevents the drift that often turns casual chats into inefficient, unstructured interactions. You are now ready to apply this framework to specific approval scenarios. Key Points: If the answer to the five questions is yes, there is a need for a meeting Prioritize early time slots when it is known that attendees are in the office Treat any discussion about a project, whether via technology or in person, as a meeting requiring preparation Scenario-Based Justification Practice Say you need a stakeholder to sign off on a design change. Before you schedule a full team meeting, run the verification questions through that specific request. Can you get that approval by picking up the phone or sending an email? If the answer is yes, the meeting fails the efficiency threshold. If the approval requires a nuanced discussion that a text-based channel can't handle, consider a "minimeeting" instead of a full team session. This format involves only a couple of people discussing a limited number of issues, which minimizes the signal-to-noise ratio. You are applying the justification test to a scenario requiring project approvals by choosing the most efficient channel that still delivers the necessary result. That choice between a phone call, a minimeeting, and a full session is where the real work of justification happens, and it reveals the specific errors people make when they assume a meeting is the default. Key Points: Apply the test to a scenario where a stakeholder needs approval for a design change Determine if a phone call or email suffices for the approval request Evaluate if the 'minimeeting' format (limited people, limited issues) is more efficient than a full team meeting Common Justification Errors The most common failure is skipping the check to see if the necessary information is already available. You schedule the call because it feels urgent, but you never verify if a quick email or phone call would have gotten the same approval. This ignores the core principle that a meeting only holds if efficient channels fail. Another trap is ignoring the timing of decision-makers. You book the slot, but the person with authority is in another time zone or out of the office. The cost justification question gets skipped because the meeting feels routine. You assume it's free because it's just a chat, but you are burning hours on a conversation that could have been a text. Strong execution looks like pausing before you click send. You ask yourself if the people who can make decisions are actually there. You confirm that you have considered alternatives to holding a meeting. You treat the cost of their time as real, not abstract. Weak execution looks like a calendar full of slots where no decisions were made. You end up with unscheduled interactions that lack a punch list of questions. You miss the chance to use a minimeeting format with limited people and limited issues. The reason this matters is that your calendar reflects your judgment. When you apply the verification framework, you protect your team's focus. You stop treating meetings as a default and start treating them as a specific, justified choice. The moment you next see an open slot, you'll know the difference between a necessary conversation and a costly habit. Key Points: Scheduling a meeting without verifying if the necessary information is already available Failing to consider if decision-makers are available at the proposed time Ignoring the cost justification question by assuming the meeting is 'free' or 'routine'

  6. vor 3 Tagen

    Planning Survey Logistics

    Define stopping conditions using participant counts or deadlines to control data collection scope. Select distribution methods and analysis tools that match your target audience's behavior. Account for manual data entry time to ensure accurate reporting of confidence metrics. Learning Objective: By the end of this lesson, learners will be able to plan survey logistics by defining endpoints, selecting distribution methods, and estimating data entry time. Transcript Defining Survey Endpoints Before you launch a survey, you must determine the stopping condition for data collection. This is the first concrete move in planning logistics. You need to choose between two specific metrics that define when the process ends. The first option is Participant Count, where you run the survey until a specific number of participants is reached. The second option is a Deadline, where you run the survey until a specific date or time is reached. As the practitioner, you choose which metric takes priority based on your project constraints. This decision shapes how you manage the collection phase. If your goal is to hit a precise sample size, participant count is your anchor. If your timeline is rigid, the deadline becomes your hard stop. This choice defines the boundary of your data collection. Once that endpoint is set, you can move to the next logistical decision. That next step involves deciding how to measure the confidence in the data you gather. Key Points: Determine the stopping condition for data collection before launching the survey Choose between Participant Count (run until specific number reached) or Deadline (run until specific date/time reached) Practitioner chooses which metric takes priority based on project constraints Reporting Confidence Metrics When you report your survey results, include two specific metrics to establish the degree of confidence the team should place in the data. First, list the overall number of people you contacted. Second, list the number of actual respondents who completed the survey. This ratio is critical because it reveals your response rate. A high number of contacts with few respondents signals low engagement. Conversely, a balanced ratio suggests strong participation. These figures allow stakeholders to evaluate the reliability of your findings. Without them, the data lacks context for decision-making. You need this baseline before analyzing trends. It grounds your conclusions in reality. Key Points: Include the overall number of people contacted in results reporting Include the number of respondents in results reporting These two metrics establish the degree of confidence the team should place in the data Selecting Collection and Analysis Tools Selecting the right data collection and analysis tool is driven entirely by your chosen distribution method. This decision determines whether your workflow remains seamless or requires significant manual intervention later. If you are running online surveys, the platform you use to collect data often includes built-in options for viewing and analyzing results. This integration means the data flows directly from the participant’s submission to your analysis dashboard without a break in the process. You avoid the friction of moving information between separate systems, which keeps the entire workflow efficient and error-free. Paper surveys operate differently. Because a physical form lacks digital processing capabilities, the collection tool itself does not provide analysis options. This creates a gap where a separate method is required to enter the data into your chosen analysis tool. You must manually transcribe every response, which adds a distinct layer of effort to your project timeline. The core principle is to match your tool selection to the distribution method you have already decided upon. You choose the tool for collecting and analyzing data based on how you will reach your participants. This alignment ensures that your analysis process starts on the same day as your data collection, rather than waiting for manual entry to finish. Key Points: Online Surveys: Tool used to collect data may have built-in options for viewing and analyzing results Non-Online/Paper Surveys: If collection tool lacks analysis options, a separate method is required to enter data into the chosen analysis tool Select the tool for collecting and analyzing data based on the distribution method Planning Data Entry Time Paper-based surveys introduce a specific logistical hurdle that online methods avoid. Every response requires significant manual data entry, a step that is easy to overlook until the first stack of paper lands on your desk. Because this work happens after collection ends, the planning phase must explicitly account for the time required to enter this data. You cannot rely on the tool to do it for you, so the estimate has to be a line item in your project timeline, not an afterthought. In contrast, online surveys are typically the easiest method to gather and analyze. The data lands directly in the analysis tool, eliminating the transcription gap entirely. This difference dictates how you structure your team’s workload, because the manual entry cost is a fixed variable you must budget for upfront. When you map your project schedule, you are deciding where that human effort sits. If you choose paper, you are committing to a period of focused data entry that delays analysis. If you choose online, you are buying speed and reducing the risk that the data sits untouched in a drawer. This time investment is the bridge between collecting responses and actually seeing the results, which leads directly into how you choose the distribution method that will determine whether you face that manual entry at all. Key Points: Paper-Based Surveys require significant manual data entry The planning phase must explicitly account for the time required to enter this data Online Surveys are typically the easiest method to gather and analyze Choosing Distribution Methods So you need to decide how to reach your users. If your target group congregates in a specific physical location, set up a table onsite for them to fill out a paper survey. This method often yields more results for that particular group, though it may skew toward people comfortable talking to strangers. For online surveys, this is your best choice if your users are active internet users and you need a large number of participants. It also keeps your data entry time low, which we discussed earlier. If you have a list of current customers, a phone survey lets you reach that user group directly. Alternatively, if you are studying a specific feature of an existing product, build a very short survey with one or two questions into the product itself. Ask this immediately after the user performs a relevant step. Think about where your users actually are right now. That location dictates your method, and your method dictates your data entry plan. Key Points: Intercept/Paper Surveys: Set up a table onsite if user groups congregate in a particular location Online Surveys: Best choice if user groups are active internet users and a large number of participants is needed Phone Surveys: Use a list of current customers to reach the user group In-Product Surveys: Build a very short survey (one or two questions) into the product to ask immediately after a relevant step

  7. vor 4 Tagen

    Planning for Mobile and Responsive Design

    Prioritize mobile audiences during initial project planning to leverage unique device capabilities like GPS and gestures. Select the appropriate delivery approach—responsive, web app, or native—based on constraint-driven focus rather than treating mobile as a post-launch optimization. Learning Objective: By the end of this lesson, learners will be able to apply the mobile-first planning framework to prioritize device capabilities and select the optimal design approach for a digital product. Transcript Mobile-First Core Principle When project planning starts with a desktop solution, unique device capabilities are often ignored or under-utilized during the subsequent mobile optimization process. This happens because the initial architecture is already fixed around a screen size that doesn't exist on a phone. The core principle of mobile-first planning requires prioritizing mobile audiences from the start to leverage specific hardware and software features. These features include location-based services, input methods, and motion sensing, which are absent or less prominent on desktops. By making mobile the starting point, you prevent the optimization phase from becoming an afterthought. Instead of retrofitting a desktop experience to fit a smaller screen, you design for the constraints that force a focus on essential data and actions. This approach ensures that the unique capabilities of the device are integrated into the product's core structure, not bolted on later. The reason this matters is that mobile users interact with their devices through gestures, accelerometers, and GPS in ways that desktop users simply don't. If you wait until the end of the project to address these interactions, you miss the opportunity to build them into the user's workflow. Mobile-first planning turns these technical features into functional advantages from day one. Key Points: Project planning must prioritize mobile audiences from the start to leverage unique device capabilities. Starting with desktop solutions leads to ignored or under-utilized mobile capabilities during subsequent optimization. Mobile-first planning prevents the 'mobile optimization' process from being an afterthought. Leveraging Unique Mobile Capabilities The mobile-first approach only works if you leverage the hardware features that desktops simply lack. These capabilities define what makes a mobile product distinct from a responsive website. First, you have location-based services, which use GPS to determine precise user locations. This allows your application to respond to where the person actually is, rather than just where they are browsing from. Next, consider the input methods, specifically multi-touch and gestural interfaces. These replace the cursor and click, letting users interact through swipes and pinches that feel natural on a small screen. Then there is motion sensing, driven by accelerometer features that track device orientation. This lets you monitor user movements, a capability particularly useful in healthcare applications where physical context matters. Finally, ecosystem integration ties your product into the user's digital life. It connects common tasks with communication tools like phones and text messages, or scheduling tools, creating a seamless workflow. Key Points: Location-based services: Precise locations determined from GPS. Input methods: Multi-touch and gestural interfaces. Motion sensing: Accelerometer features sensitive to device orientation for tracking user movements. Ecosystem integration: Deep integration with the user’s digital ecosystem, tying together tasks with communication and scheduling tools. Strategic Decision Points for Delivery So, when you’re planning a digital product for both desktop and smartphone, you face a critical fork in the road. You have to choose among three primary approaches. First, there’s responsive design. This means building one single website that looks good on multiple devices. It’s the most common starting point because it keeps your codebase unified. Second, you might build a mobile web app. This is a unique mobile web app, created in addition to, or instead of, your desktop site. It’s tailored specifically for the mobile browser experience. Third, you can build a native mobile app. This is a dedicated app for specific platforms like iOS or Android. It lives on the device and integrates deeply with its operating system. Your choice depends on your specific constraints and goals. But you must make this decision early. Waiting until the end usually leads to a patchwork solution. This choice dictates your entire development path. It determines how you leverage those mobile capabilities we discussed. Key Points: Responsive Design: Build one website that looks good on multiple devices. Mobile Web App: Build a unique mobile web app, in addition to or instead of a desktop site. Native Mobile App: Build a native mobile app for specific platforms like iOS or Android. Teams must decide among these three primary approaches when planning for both desktop and smartphone. Rationale and Costs of Responsive Design You’ve chosen responsive design, so the cost model shifts immediately. The rationale is simple. Mobile user bases are growing explosively, and time spent on these platforms now often exceeds desktop usage. This volume makes mobile the primary interface for many users. However, that choice carries a specific constraint-driven focus. By starting with the smallest screen, the team is forced to prioritize essential data and actions. This limitation strips away clutter, ensuring the core functionality remains clear and accessible on any device. Yet, the work isn’t done once the code is written. You must engage in viewport design for every screen size. This means creating distinct sketches and wireframes for desktops, tablets, and phones. Each layout requires individual attention because the spatial constraints change dramatically between them. Then comes the testing overhead. Every unique view you build needs validation with real users. This adds significant time and effort to the project timeline. You are not just building one site; you are managing a suite of distinct experiences that must all perform reliably. Weigh these costs against the growth data. If your users are predominantly on mobile, the extra design work is a necessary investment. Key Points: Explosive Growth: Mobile user base and time spent on mobile platforms is growing rapidly, often exceeding desktop. Constraint-Driven Focus: Starting with mobile design forces the team to focus on essential data and actions. Viewport Design: Must design for various viewports (desktop, tablets, phones) requiring sketching and wireframe work for each. Testing Overhead: Any view or display created needs to be tested with users, adding time and effort. Contextual Integration and Stakeholder Complexity Mobile and responsive planning must be integrated into the project’s broader ecosystem, which means looking beyond the screen itself. You have to consider the environment, specifically the company culture, because a rigid corporate structure often clashes with the rapid iteration that mobile development requires. Next, you must account for the general type of work, meaning the specific type of product being designed. A utility app demands different stakeholder alignment than a creative portfolio, so the planning process shifts accordingly. This leads directly to stakeholder complexity, a significant cost in responsive design projects. Clients often underestimate the effort required to test across various viewports, from desktops to tablets to phones. They may not fully understand the implications of maintaining a single codebase that adapts to so many devices. So, your job is to translate those technical constraints into business risks early on. When you face this moment in real work, you are negotiating a shared understanding of scope, and the layout follows from it. Recognizing this complexity allows you to manage expectations before the wireframes are even drawn. It connects back to the core insight that mobile-first is a strategic stance that shapes the whole approach, ensuring your plan survives the reality of organizational constraints. Key Points: Mobile and responsive planning must be integrated into the project’s broader ecosystem. Consider the environment (company culture) in planning decisions. Account for the general type of work (type of product being designed). Address stakeholder complexity, particularly when clients may not fully understand the implications of responsive design costs.

  8. vor 4 Tagen

    What's Included in Your Design Fee

    You will learn to explicitly define whether stock photography and font licensing are included in the design fee or billed separately. This capability prevents client misunderstandings by establishing clear boundaries around external resource costs before project kickoff. Learning Objective: By the end of this lesson, learners will be able to formulate explicit fee inclusion statements for external resources like stock photography and fonts to prevent client cost misunderstandings. Transcript The Cost Ambiguity of Third-Party Assets Stock photography and font licensing sit outside the core design labor, yet they often blur into the same line item on a client invoice. This ambiguity creates a specific cost gap where clients assume these external resources are already covered by the base fee. When the final bill includes separate charges for licensing, it triggers confusion about total project costs that should have been clarified upfront. The reason this happens is that fee structures rarely distinguish between creative effort and third-party asset acquisition. Clients perceive the design fee as a comprehensive package, so any unlisted expense feels like an unexpected surprise rather than a standard line item. To prevent these billing disputes, you must explicitly state the inclusion status of every external resource before work begins. This explicit definition is required to establish a clear boundary between what the fee covers and what it does not. By identifying stock photography and font licensing as distinct categories, you remove the guesswork that leads to client misunderstandings. The next step is defining exactly which deliverables fall under that fee umbrella. Key Points: Stock photography and font licensing are external resources distinct from core design labor Ambiguity in fee structure leads to client misunderstandings regarding total project costs Explicit statement of inclusion status is required to avoid billing disputes Defining the Scope of Design Fees Defining the scope of design fees requires a clear boundary between your labor and external resource costs. Your fee covers the deliverables you create, like wireframes and visual designs, but it does not inherently cover the licenses for the assets you use to build them. Specifically, you must distinguish between included design deliverables and separately billed resource licenses to maintain clarity. You need to identify specific external assets, such as stock photography, font licensing, and other third-party resources, that sit outside the core creative work. These are distinct line items with their own pricing structures, and treating them as part of your hourly rate creates immediate financial confusion. The reason this distinction is critical is that fee components must be explicitly defined to prevent scope creep. When you leave these boundaries vague, clients often assume that every visual element in the final product is covered under the initial quote. This ambiguity forces you to either absorb the cost of third-party assets or face difficult conversations about unexpected expenses later. By explicitly stating whether these resources are included or billed separately, you protect your margin and set accurate expectations from the start. Key Points: Distinguish between included design deliverables and separately billed resource licenses Identify specific external assets: stock photography, font licensing, and other third-party resources Recognize that fee components must be explicitly defined to prevent scope creep Choosing Between Bundled and Separate Billing When you bundle stock photography and font licensing into your design fee, the client sees one simple number. That simplicity works until you need ten custom illustrations or a full brand font suite. Your margin erodes because you absorbed costs that were never part of the core labor. Separate billing gives you transparency, but it demands clear communication of additional costs. If you don’t explain why a specific typeface costs extra, the client assumes it’s standard practice. They’ll wonder why their design fee feels like a hidden subscription model. To choose the right approach, apply a decision framework based on client budget expectations and asset usage volume. If the project requires only a few standard assets, bundling keeps the relationship smooth. If the scope involves high-end photography or exclusive licensing, bill those separately. This protects your profit while keeping the core design value distinct. You need to decide where the line falls before the contract is signed. The specific items you list as included versus excluded become the foundation for how you draft explicit fee inclusion statements later. Key Points: Evaluate tradeoffs: bundling simplifies client perception but risks margin erosion Separate billing provides transparency but requires clear communication of additional costs Decision framework: assess client budget expectations and asset usage volume Drafting Explicit Fee Inclusion Statements So, when you write that fee inclusion statement, you need to be explicit about stock photography. Don't just say "assets included." State clearly whether that specific stock image is part of the design fee or if it's billed separately. This removes the ambiguity that usually triggers billing disputes later in the process. Next, you have to specify the font licensing terms. Is the license included in your fee, or is the client providing the font files? This distinction matters because licensing costs vary wildly depending on the vendor and the scope of usage, so you need to assign that responsibility clearly in writing. Finally, you need a catch-all clause for any additional external resources not explicitly listed. This protects you if a new asset type comes up during the project. If it isn't on the list, it isn't included in the base fee. This framework ensures you have a clear decision point for every third-party item. By defining these three areas, you prevent the common misunderstanding that clients often expect all visual assets to be included in the design fee. Key Points: Use language that explicitly states whether stock photography is included or billed separately Specify font licensing terms: included in fee or client-provided Include a clause addressing any additional external resources not explicitly listed Avoiding Common Client Misunderstandings The most frequent error in this space is assuming clients intuitively understand that third-party assets carry separate costs. In practice, clients often expect all visual assets to be included in the design fee. This expectation creates a significant gap when you propose additional charges for stock photography or font licensing. Strong execution looks like a client who clearly distinguishes between your labor and the external resources you source. They see the fee breakdown as a logical extension of the scope, not a surprise. Weak execution appears when a client feels blindsided by a line item they believed was standard. They interpret the ambiguity as a lack of transparency, which erodes trust before the project even begins. To avoid this, you must explicitly state the status of every external resource. This means applying the explicit statement approach to all external resource types in future projects. Whether it is a specific font license or a batch of stock images, the fee structure must leave no room for assumption. The lesson here is that clarity is the only defense against cost misunderstandings. You have now walked through the definition, the billing choice, and the statement drafting. The final step is applying that same explicit clarity to every new project you take on. Key Points: Common mistake: assuming clients understand that third-party assets cost extra Feedback: clients often expect all visual assets to be included in the design fee Transfer: apply this explicit statement approach to all external resource types in future projects

Alle anzeigen (382)

Info

5mUX is practitioner-grade UX training in five-minute lessons, structured around how adults actually learn. Every lesson teaches one concept or skill you can apply immediately, available as text, audio, or video. Pick the modality that fits your moment; the rigor stays the same.

Informationen

  • Erstellt von
    5mUX
  • Jahre aktiv
    2026
  • Folgen
    382
  • Bewertung
    Unbedenklich
  • Sendungswebsite
    5 Minute UX