Claude for E-commerce Typography Specialists: Fix Poor Mobile Responsiveness With a UX Research Report

You are a senior typography and UX content specialist with 9 years of experience writing UX research reports and type system documentation for e-commerce brands where poor mobile responsiveness is frequently caused by type scale decisions that were designed for desktop first and scaled down incorrectly, and where a clearly written UX research report is the tool that gets the development team to implement the correct type scale rather than the one that was convenient to code. Help me write a UX research report so I can improve client approval speed and produce a report that connects the typography findings from a mobile responsiveness audit directly to the conversion and readability outcomes the client cares about, without requiring the client to interpret raw design data. My situation: - E-commerce site type and mobile performance problem: [e.g., "a fashion e-commerce brand — mobile bounce rate is 61% versus 34% on desktop, and heatmap data shows 73% of mobile users abandon the product description page before reaching the add-to-cart button"] - Typography-specific mobile problem identified: [e.g., "the product name uses a 24px font size on desktop that scales to 18px on mobile — at 18px in the current typeface (a condensed serif), the descenders become illegible on screens below 375px width, creating a false readability signal where text appears present but is not being read"] - Research data available: [e.g., "Hotjar heatmap data for 3 product pages over 4 weeks, a mobile usability session recording with 6 participants, and Google Analytics showing average scroll depth of 22% on mobile product pages versus 68% on desktop"] - Client approval bottleneck: [e.g., "the previous research report was 24 pages with appendices — the marketing director approved it 6 weeks after delivery, after requesting a one-page summary that the design team had to produce separately"] - Client audience for the report: [e.g., "the marketing director and the e-commerce manager — both make budget decisions, neither has a design background, and both evaluate reports based on the commercial impact of findings rather than the quality of the research methodology"] - Development team constraint: [e.g., "the front-end developer who will implement the typography fix has asked for the corrected type scale in rem values rather than px, with the breakpoint specified in the CSS syntax used by the current codebase"] - Report length and format required: [e.g., "the client has explicitly requested a maximum 8-page report with an executive summary on page one — all supporting data must be referenced rather than reproduced in full"] Deliver: 1. A UX research report structure for an 8-page maximum — page one is a one-paragraph executive summary stating the commercial impact of the typography problem and the recommended fix, pages two and three cover the three key findings from heatmap, session recording, and analytics data with one visual reference per finding, pages four and five cover the typography diagnosis explaining the specific readability failure at the 375px breakpoint, page six is the corrected type scale recommendation, page seven is the implementation brief for the developer, and page eight is the measurement plan for confirming the fix worked 2. A commercial impact summary for the executive summary — a one-paragraph statement connecting the 61% mobile bounce rate to the specific typography readability failure, with a revenue estimate based on the current mobile traffic volume and the brand's average order value, written for a marketing director who needs to justify a development sprint to fix a typography issue 3. A finding presentation format for non-designer clients — a three-part structure for each of the three key findings covering the observation in plain English (what was seen), the cause in one sentence (why it happened), and the commercial consequence in revenue or conversion terms (what it costs the business), applied to the heatmap, session recording, and analytics findings 4. A typography diagnosis section — a plain-English explanation of why a 18px condensed serif at 375px width is failing readability, with a comparison using a corrected size and weight combination, written so the marketing director understands the problem without needing to know what a condensed serif is or why descenders matter 5. A corrected mobile type scale — a type scale for the product description page with font size, line height, and font weight at three breakpoints (375px, 768px, 1280px), expressed in both px for design and rem for development, with the specific breakpoint values in CSS media query syntax matching the current codebase format 6. A developer implementation brief — a one-page technical specification covering the three CSS changes required (font-size, line-height, and font-weight adjustments at the 375px breakpoint), the files affected, the testing requirement (visual regression test at 320px, 375px, and 414px), and the browser support scope 7. A client approval process brief — a structured review pathway reducing the previous 6-week approval delay, covering a 2-day window for the executive summary review, a 5-day window for the full report review, and an asynchronous approval mechanism (a single email confirmation rather than a scheduled review meeting) for clients who have read the summary 8. A post-implementation measurement plan — four metrics tracked at 30 days after the typography fix (mobile bounce rate, scroll depth on product pages, add-to-cart rate from mobile, and mobile conversion rate), with the benchmark comparison against the pre-fix baseline and the target improvement range that confirms the fix worked **Write every report section assuming the marketing director will read only the executive summary and the finding presentations — every finding must make its commercial consequence clear in the first sentence, and every recommendation must be stated as an action rather than an observation, because a client who reads the action on page one does not need to read pages two through eight to approve the development sprint.**