User Experience

Back in 2007, Nobel Prize-winning psychologist Daniel Kahneman taught a private master class to tech founders including Larry Page and Jeff Bezos. The following year, Elon Musk joined. Among the topics: priming, where subtle cues shape our decisions without us realizing it. In that room, Musk pressed on subliminal versus explicit persuasion: “Does the hidden beat the obvious?” Kahneman's answer: "There are many situations in which subliminal effects are stronger than superliminal effects." Translation: Hidden influences shape behavior more than obvious ones. You can't resist what you don't notice. Later after that session, Bezos connected the dots: “You can choose your choice architect.” You either design the decision environment, or it designs you. Amazon designed theirs. One-click purchasing removes the pause where doubt lives. Every additional step is an exit ramp. They chose zero exits. Google designed theirs. That empty white homepage isn't minimal by accident. No portals, no distractions. Just one thought: search. Most companies let chaos choose. Cluttered onboarding. Buried CTAs. Friction everywhere. They're not architects. They're accidents. So how do you become the architect instead of the accident? 1. Choose your pricing architect: Sell your core product for $99/month. Then offer a bundle with two add-ons for $119. The bundle makes the core feel essential. 2. Choose your onboarding architect: When users first sign up, make their first action create immediate value - a report generated, first customer added, dashboard live. Success in 30 seconds primes confidence in everything that follows. In contrast, when you make the frame obvious, you lose it. Slap "Most Popular!" on everything and watch trust erode. The moment users detect manipulation, they create their own frame - one where you're untrustworthy. Kahneman warned Musk about this directly. Covert cues work precisely because they're not noticed. Priming is architecture, not decoration. By the time logic kicks in, the frame has already decided. Because you’re already an architect. The only question is whether you know what you're building.

Invisible UX is coming 🔥 And it’s going to change how we design products, forever. For decades, UX design has been about guiding users through an experience. We’ve done that with visible interfaces: Menus. Buttons. Cards. Sliders. We’ve obsessed over layouts, states, and transitions. But with AI, a new kind of interface is emerging: One that’s invisible. One that’s driven by intent, not interaction. Think about it: You used to: → Open Spotify → Scroll through genres → Click into “Focus” → Pick a playlist Now you just say: “Play deep focus music.” No menus. No tapping. No UI. Just intent → output. You used to: → Search on Airbnb → Pick dates, guests, filters → Scroll through 50+ listings Now we’re entering a world where you guide with words: “Find me a cabin near Oslo with a sauna, available next weekend.” So the best UX becomes barely visible. Why does this matter? Because traditional UX gives users options. AI-native UX gives users outcomes. Old UX: “Here are 12 ways to get what you want.” New UX: “Just tell me what you want & we’ll handle the rest.” And this goes way beyond voice or chat. It’s about reducing friction. Designing systems that understand intent. Respond instantly. And get out of the way. The UI isn’t disappearing. It’s mainly dissolving into the background. So what should designers do? Rethink your role. Going forward you’ll not just lay out screens. You’ll design interactions without interfaces. That means: → Understanding how people express goals → Guiding model behavior through prompt architecture → Creating invisible guardrails for trust, speed, and clarity You are basically designing for understanding. The future of UX won’t be seen. It will be felt. Welcome to the age of invisible UX. Ready for it?

𝟔𝟔% 𝐨𝐟 𝐀𝐈 𝐮𝐬𝐞𝐫𝐬 𝐬𝐚𝐲 𝐝𝐚𝐭𝐚 𝐩𝐫𝐢𝐯𝐚𝐜𝐲 𝐢𝐬 𝐭𝐡𝐞𝐢𝐫 𝐭𝐨𝐩 𝐜𝐨𝐧𝐜𝐞𝐫𝐧. What does that tell us? Trust isn’t just a feature - it’s the foundation of AI’s future. When breaches happen, the cost isn’t measured in fines or headlines alone - it’s measured in lost trust. I recently spoke with a healthcare executive who shared a haunting story: after a data breach, patients stopped using their app - not because they didn’t need the service, but because they no longer felt safe. 𝐓𝐡𝐢𝐬 𝐢𝐬𝐧’𝐭 𝐣𝐮𝐬𝐭 𝐚𝐛𝐨𝐮𝐭 𝐝𝐚𝐭𝐚. 𝐈𝐭’𝐬 𝐚𝐛𝐨𝐮𝐭 𝐩𝐞𝐨𝐩𝐥𝐞’𝐬 𝐥𝐢𝐯𝐞𝐬 - 𝐭𝐫𝐮𝐬𝐭 𝐛𝐫𝐨𝐤𝐞𝐧, 𝐜𝐨𝐧𝐟𝐢𝐝𝐞𝐧𝐜𝐞 𝐬𝐡𝐚𝐭𝐭𝐞𝐫𝐞𝐝. Consider the October 2023 incident at 23andMe: unauthorized access exposed the genetic and personal information of 6.9 million users. Imagine seeing your most private data compromised. At Deloitte, we’ve helped organizations turn privacy challenges into opportunities by embedding trust into their AI strategies. For example, we recently partnered with a global financial institution to design a privacy-by-design framework that not only met regulatory requirements but also restored customer confidence. The result? A 15% increase in customer engagement within six months. 𝐇𝐨𝐰 𝐜𝐚𝐧 𝐥𝐞𝐚𝐝𝐞𝐫𝐬 𝐫𝐞𝐛𝐮𝐢𝐥𝐝 𝐭𝐫𝐮𝐬𝐭 𝐰𝐡𝐞𝐧 𝐢𝐭’𝐬 𝐥𝐨𝐬𝐭? ✔️ 𝐓𝐮𝐫𝐧 𝐏𝐫𝐢𝐯𝐚𝐜𝐲 𝐢𝐧𝐭𝐨 𝐄𝐦𝐩𝐨𝐰𝐞𝐫𝐦𝐞𝐧𝐭: Privacy isn’t just about compliance. It’s about empowering customers to own their data. When people feel in control, they trust more. ✔️ 𝐏𝐫𝐨𝐚𝐜𝐭𝐢𝐯𝐞𝐥𝐲 𝐏𝐫𝐨𝐭𝐞𝐜𝐭 𝐏𝐫𝐢𝐯𝐚𝐜𝐲: AI can do more than process data, it can safeguard it. Predictive privacy models can spot risks before they become problems, demonstrating your commitment to trust and innovation. ✔️ 𝐋𝐞𝐚𝐝 𝐰𝐢𝐭𝐡 𝐄𝐭𝐡𝐢𝐜𝐬, 𝐍𝐨𝐭 𝐉𝐮𝐬𝐭 𝐂𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞: Collaborate with peers, regulators, and even competitors to set new privacy standards. Customers notice when you lead the charge for their protection. ✔️ 𝐃𝐞𝐬𝐢𝐠𝐧 𝐟𝐨𝐫 𝐀𝐧𝐨𝐧𝐲𝐦𝐢𝐭𝐲: Techniques like differential privacy ensure sensitive data remains safe while enabling innovation. Your customers shouldn’t have to trade their privacy for progress. Trust is fragile, but it’s also resilient when leaders take responsibility. AI without trust isn’t just limited - it’s destined to fail. 𝐇𝐨𝐰 𝐰𝐨𝐮𝐥𝐝 𝐲𝐨𝐮 𝐫𝐞𝐠𝐚𝐢𝐧 𝐭𝐫𝐮𝐬𝐭 𝐢𝐧 𝐭𝐡𝐢𝐬 𝐬𝐢𝐭𝐮𝐚𝐭𝐢𝐨𝐧? 𝐋𝐞𝐭’𝐬 𝐬𝐡𝐚𝐫𝐞 𝐚𝐧𝐝 𝐢𝐧𝐬𝐩𝐢𝐫𝐞 𝐞𝐚𝐜𝐡 𝐨𝐭𝐡𝐞𝐫 👇 #AI #DataPrivacy #Leadership #CustomerTrust #Ethics

🌎 Designing Cross-Cultural And Multi-Lingual UX. Guidelines on how to stress test our designs, how to define a localization strategy and how to deal with currencies, dates, word order, pluralization, colors and gender pronouns. ⦿ Translation: “We adapt our message to resonate in other markets”. ⦿ Localization: “We adapt user experience to local expectations”. ⦿ Internationalization: “We adapt our codebase to work in other markets”. ✅ English-language users make up about 26% of users. ✅ Top written languages: Chinese, Spanish, Arabic, Portuguese. ✅ Most users prefer content in their native language(s). ✅ French texts are on average 20% longer than English ones. ✅ Japanese texts are on average 30–60% shorter. 🚫 Flags aren’t languages: avoid them for language selection. 🚫 Language direction ≠ design direction (“F” vs. Zig-Zag pattern). 🚫 Not everybody has first/middle names: “Full name” is better. ✅ Always reserve at least 30% room for longer translations. ✅ Stress test your UI for translation with pseudolocalization. ✅ Plan for line wrap, truncation, very short and very long labels. ✅ Adjust numbers, dates, times, formats, units, addresses. ✅ Adjust currency, spelling, input masks, placeholders. ✅ Always conduct UX research with local users. When localizing an interface, we need to work beyond translation. We need to be respectful of cultural differences. E.g. in Arabic we would often need to increase the spacing between lines. For Chinese market, we need to increase the density of information. German sites require a vast amount of detail to communicate that a topic is well-thought-out. Stress test your design. Avoid assumptions. Work with local content designers. Spend time in the country to better understand the market. Have local help on the ground. And test repeatedly with local users as an ongoing part of the design process. You’ll be surprised by some findings, but you’ll also learn to adapt and scale to be effective — whatever market is going to come up next. Useful resources: UX Design Across Different Cultures, by Jenny Shen https://lnkd.in/eNiyVqiH UX Localization Handbook, by Phrase https://lnkd.in/eKN7usSA A Complete Guide To UX Localization, by Michal Kessel Shitrit 🎗️ https://lnkd.in/eaQJt-bU Designing Multi-Lingual UX, by yours truly https://lnkd.in/eR3GnwXQ Flags Are Not Languages, by James Offer https://lnkd.in/eaySNFGa IBM Globalization Checklists https://lnkd.in/ewNzysqv Books: ⦿ Cross-Cultural Design (https://lnkd.in/e8KswErf) by Senongo Akpem ⦿ The Culture Map (https://lnkd.in/edfyMqhN) by Erin Meyer ⦿ UX Writing & Microcopy (https://lnkd.in/e_ZFu374) by Kinneret Yifrah

Data is everything in product design. Without data, we open ourselves up to: - Biases - Opinions - Confusion - Misalignment When we are data-informed and that data is accurate, we can truly make educated product decisions. I like to think of data in two layers: a) What’s happening and b) Why it’s happening. Let’s break it down. What’s happening: - Business data tells us how the business is doing - Marketing/sales data tells us where our customers come from - Retention data tells us when and why customers are leaving us - Engagement data tells us how customers are using our product Why it’s happening: - User research gives us rich insight into why something is happening - Voice of the customer data shows us how customers talk about our product - Usability scores show us how people perceive our product or feature experience in a measurable way - Product market fit & satisfaction scores give us a simple and actionable metric to track and improve over time In terms of accessing that data, methodologies vary, but generally speaking, I always advise the following: 1. Get access to growth and retention data through business dashboards. 2. Get access to product data through your product analytics tool. 3. Set up a cadence to gather customer reviews & comments, either manually or via automated tools. 4. Set up a cadence to speak to your users continuously to answer the why. 5. Set up a recurring survey to track satisfaction and usability. If you don’t have the data structure for any of the above, speak to your product and data team to see if you can change that. If not, rely on the data that you can actually get. PS: The list of metrics is indicative: Actual metrics will differ greatly from one company to another and largely depend on the industry, niche, as well as your data infrastructure and setup. — If you found this useful, consider reposting ♻️ How are you collecting and using data in your design process? What else are you tracking?

New! We’ve published a new set of automated evaluations and benchmarks for RAG - a critical component of Gen AI used by most successful customers today. Sweet. Retrieval-Augmented Generation lets you take general-purpose foundation models - like those from Anthropic, Meta, and Mistral - and “ground” their responses in specific target areas or domains using information which the models haven’t seen before (maybe confidential, private info, new or real-time data, etc). This lets gen AI apps generate responses which are targeted to that domain with better accuracy, context, reasoning, and depth of knowledge than the model provides off the shelf. In this new paper, we describe a way to evaluate task-specific RAG approaches such that they can be benchmarked and compared against real-world uses, automatically. It’s an entirely novel approach, and one we think will help customers tune and improve their AI apps much more quickly, and efficiently. Driving up accuracy, while driving down the time it takes to build a reliable, coherent system. 🔎 The evaluation is tailored to a particular knowledge domain or subject area. For example, the paper describes tasks related to DevOps troubleshooting, scientific research (ArXiv abstracts), technical Q&A (StackExchange), and financial reporting (SEC filings). 📝 Each task is defined by a specific corpus of documents relevant to that domain. The evaluation questions are generated from and grounded in this corpus. 📊 The evaluation assesses the RAG system's ability to perform specific functions within that domain, such as answering questions, solving problems, or providing relevant information based on the given corpus. 🌎 The tasks are designed to mirror real-world scenarios and questions that might be encountered when using a RAG system in practical applications within that domain. 🔬 Unlike general language model benchmarks, these task-specific evaluations focus on the RAG system's performance in retrieving and applying information from the given corpus to answer domain-specific questions. ✍️ The approach allows for creating evaluations for any task that can be defined by a corpus of relevant documents, making it adaptable to a wide range of specific use cases and industries. Really interesting work from the Amazon science team, and a new totem of evaluation for customers choosing and tuning their RAG systems. Very cool. Paper linked below.

I can’t stop thinking about this. If you invest in your people from day 1, they’ll invest their talents in your company tenfold. It sounds obvious, but I’ve seen firsthand how often this gets missed. I joined companies and startups with zero training: - no documentation - unclear processes - no real onboarding I was expected to figure it out as I went, and honestly, it was brutal 😭 So here’s what *actually* sets people up for success: —— 1️⃣ What does a new hire need to know but feels awkward asking? Think back to your first 30 days. ↳ How do things actually work here? ↳ Where do I go for answers? ↳ What mistakes should I avoid early on? If the answers live only in someone’s head, that’s the gap. ✅ Document anything you explain more than once. —— 2️⃣ Where are people guessing instead of being guided? When training doesn’t exist, people improvise. ↳ Clicking the wrong thing ↳ Following outdated steps ↳ Copying work that isn’t quite right That’s how errors and rework happen. Tools like Tango make this easy by turning workflows into step-by-step guides. ✅ Record one common task this week and turn it into a reusable guide. —— 3️⃣ What tribal knowledge needs to be documented? You know it’s a systems problem when there are: ↳ Constant pings ↳ Repeating the same answers ↳ Little time for deep work ✅ Have your strongest team member document one core process they own. —— 4️⃣ Are you onboarding people or overwhelming them? More information doesn’t mean better onboarding. People need: ↳ Clear priorities ↳ Time to practice ↳ Space to build confidence ✅ Use a simple 30-60-90 day framework for all new hires —— 5️⃣ Are expectations clear or just assumed? When expectations are vague: ↳ People second-guess themselves ↳ Feedback comes too late ↳ Performance feels personal instead of fixable ✅ Check in early and often and schedule 20-minute check-ins with your manager or onboarding buddy in the first 8 weeks. —— When you give people the right tools, training, and support, you get: → Faster onboarding → More consistent processes → Fewer mistakes and support tickets → Happier, more confident employees 💙 You can’t expect people to thrive without setting them up properly. Set people up to win and they will 🫶 Do you agree? #TangoPartner

Over the last year, I’ve seen many people fall into the same trap: They launch an AI-powered agent (chatbot, assistant, support tool, etc.)… But only track surface-level KPIs — like response time or number of users. That’s not enough. To create AI systems that actually deliver value, we need 𝗵𝗼𝗹𝗶𝘀𝘁𝗶𝗰, 𝗵𝘂𝗺𝗮𝗻-𝗰𝗲𝗻𝘁𝗿𝗶𝗰 𝗺𝗲𝘁𝗿𝗶𝗰𝘀 that reflect: • User trust • Task success • Business impact • Experience quality    This infographic highlights 15 𝘦𝘴𝘴𝘦𝘯𝘵𝘪𝘢𝘭 dimensions to consider: ↳ 𝗥𝗲𝘀𝗽𝗼𝗻𝘀𝗲 𝗔𝗰𝗰𝘂𝗿𝗮𝗰𝘆 — Are your AI answers actually useful and correct? ↳ 𝗧𝗮𝘀𝗸 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗶𝗼𝗻 𝗥𝗮𝘁𝗲 — Can the agent complete full workflows, not just answer trivia? ↳ 𝗟𝗮𝘁𝗲𝗻𝗰𝘆 — Response speed still matters, especially in production. ↳ 𝗨𝘀𝗲𝗿 𝗘𝗻𝗴𝗮𝗴𝗲𝗺𝗲𝗻𝘁 — How often are users returning or interacting meaningfully? ↳ 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗥𝗮𝘁𝗲 — Did the user achieve their goal? This is your north star. ↳ 𝗘𝗿𝗿𝗼𝗿 𝗥𝗮𝘁𝗲 — Irrelevant or wrong responses? That’s friction. ↳ 𝗦𝗲𝘀𝘀𝗶𝗼𝗻 𝗗𝘂𝗿𝗮𝘁𝗶𝗼𝗻 — Longer isn’t always better — it depends on the goal. ↳ 𝗨𝘀𝗲𝗿 𝗥𝗲𝘁𝗲𝗻𝘁𝗶𝗼𝗻 — Are users coming back 𝘢𝘧𝘵𝘦𝘳 the first experience? ↳ 𝗖𝗼𝘀𝘁 𝗽𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝗼𝗻 — Especially critical at scale. Budget-wise agents win. ↳ 𝗖𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝘁𝗵 — Can the agent handle follow-ups and multi-turn dialogue? ↳ 𝗨𝘀𝗲𝗿 𝗦𝗮𝘁𝗶𝘀𝗳𝗮𝗰𝘁𝗶𝗼𝗻 𝗦𝗰𝗼𝗿𝗲 — Feedback from actual users is gold. ↳ 𝗖𝗼𝗻𝘁𝗲𝘅𝘁𝘂𝗮𝗹 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 — Can your AI 𝘳𝘦𝘮𝘦𝘮𝘣𝘦𝘳 𝘢𝘯𝘥 𝘳𝘦𝘧𝘦𝘳 to earlier inputs? ↳ 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 — Can it handle volume 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 degrading performance? ↳ 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗥𝗲𝘁𝗿𝗶𝗲𝘃𝗮𝗹 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝗰𝘆 — This is key for RAG-based agents. ↳ 𝗔𝗱𝗮𝗽𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗦𝗰𝗼𝗿𝗲 — Is your AI learning and improving over time? If you're building or managing AI agents — bookmark this. Whether it's a support bot, GenAI assistant, or a multi-agent system — these are the metrics that will shape real-world success. 𝗗𝗶𝗱 𝗜 𝗺𝗶𝘀𝘀 𝗮𝗻𝘆 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗼𝗻𝗲𝘀 𝘆𝗼𝘂 𝘂𝘀𝗲 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀? Let’s make this list even stronger — drop your thoughts 👇

Last week, I described four design patterns for AI agentic workflows that I believe will drive significant progress: Reflection, Tool use, Planning and Multi-agent collaboration. Instead of having an LLM generate its final output directly, an agentic workflow prompts the LLM multiple times, giving it opportunities to build step by step to higher-quality output. Here, I'd like to discuss Reflection. It's relatively quick to implement, and I've seen it lead to surprising performance gains. You may have had the experience of prompting ChatGPT/Claude/Gemini, receiving unsatisfactory output, delivering critical feedback to help the LLM improve its response, and then getting a better response. What if you automate the step of delivering critical feedback, so the model automatically criticizes its own output and improves its response? This is the crux of Reflection. Take the task of asking an LLM to write code. We can prompt it to generate the desired code directly to carry out some task X. Then, we can prompt it to reflect on its own output, perhaps as follows: Here’s code intended for task X: [previously generated code] Check the code carefully for correctness, style, and efficiency, and give constructive criticism for how to improve it. Sometimes this causes the LLM to spot problems and come up with constructive suggestions. Next, we can prompt the LLM with context including (i) the previously generated code and (ii) the constructive feedback, and ask it to use the feedback to rewrite the code. This can lead to a better response. Repeating the criticism/rewrite process might yield further improvements. This self-reflection process allows the LLM to spot gaps and improve its output on a variety of tasks including producing code, writing text, and answering questions. And we can go beyond self-reflection by giving the LLM tools that help evaluate its output; for example, running its code through a few unit tests to check whether it generates correct results on test cases or searching the web to double-check text output. Then it can reflect on any errors it found and come up with ideas for improvement. Further, we can implement Reflection using a multi-agent framework. I've found it convenient to create two agents, one prompted to generate good outputs and the other prompted to give constructive criticism of the first agent's output. The resulting discussion between the two agents leads to improved responses. Reflection is a relatively basic type of agentic workflow, but I've been delighted by how much it improved my applications’ results. If you’re interested in learning more about reflection, I recommend: - Self-Refine: Iterative Refinement with Self-Feedback, by Madaan et al. (2023) - Reflexion: Language Agents with Verbal Reinforcement Learning, by Shinn et al. (2023) - CRITIC: Large Language Models Can Self-Correct with Tool-Interactive Critiquing, by Gou et al. (2024) [Original text: https://lnkd.in/g4bTuWtU ]

Most brands spend a lot on media, but treat landing pages as an afterthought If you’re running ads and sending traffic to a homepage or a poorly built landing page, its almost criminal. Specially when gen AI has reduced the cost and time for content creation drastically Here’s how to get landing pages right. Consistently. 1. Match Intent, Not Just Aesthetics The #1 job of a landing page? Continue the conversation you started with your ad •If your ad says “energy efficient fans”, the landing page should show highlight this feature front and center •If your Google ad targets “Mixer Grinders under ₹5000,” don’t show ₹8000 models on the page. Message match > Visual design 2. Keep the Hero Section Clean & Focused Above-the-fold matters. You need to have •Clear headline – Say what the product is and why it’s special. •Key benefits – 3 crisp points max. •Visuals – High-quality product image or demo video. •CTA – One action. Not three. Buy Now,” “Book a Demo,” or “Know More”—but pick ONE 3. Product Benefits, Not Just Features Nobody cares that your mixer uses XYZ motor tech. I mean they do care but only if they care how it helps them They care a lot more that the mixer has a coarse mode which enables silbatta like texture resulting in great taste And that BLDC or intelligent motor tech enables it 4. Solve for Trust People are skeptical by default. Give them reasons to believe •Ratings & Reviews – Show real customer ratings (4.5 stars? Flaunt it). •Media Mentions – “As seen on The Hindu / NDTV” works. •Certifications – BEE 5-Star? BIS approved? Display badges. •Guarantees – Free returns? Warranty? Mention clearly 5. Speed & Mobile Optimization Today at least 80 percent of your traffic is mobile. If your landing page loads in 4 seconds, you’ve lost half. Aim for <2s load time. Avoid fancy animations that slow things down. Test your page on Mobile (3G/4G) and in all browsers Chrome, Safari etc 6. Minimize Distractions A landing page is not your website. •No top nav bars with 7 menu items. •No footer clutter. •No exit doors—except the CTA you want. Keep it focused. Keep them moving toward action 7. Strong CTA (Call to Action) •Make it obvious. One clear button. •Use actionable language: “Get My Free Sample,” “Book a Demo,” “Shop Now.” •Repeat CTA 2-3 times as they scroll, especially after key benefit sections. 8. A/B Test, but with caution: Gen AI makes it very easy to do so. Test •Headlines •CTA text and colors •Images vs Videos •Long-form vs Short-form copy But get the fundamentals of A/B testing right. You need statistically significant sample sizes for each test A good landing page doesn’t sell the product by itself. But It removes friction so the product has a better chance of selling And when done right, your CAC drops, your ROAS climbs, and your ads finally start working to their fullest potential