DriftLead’s Post

Successfully clear the test

Here’s the #1 craziest hack to get more CRO results. Test faster and test more. That’s it really. There aren’t any hacks that will immediately guarantee more results. But we have proven that more tests, and faster execution are two levers that are true for every business. It’s simple math. No one can predict which tests will win, but the more experiments we launch, the more we stack our odds to find winning tests. Here’s how you can do it: - Automate and streamline the communication workflow - Present new test plans in weekly batches - Appoint one leader to approve test plans for velocity - The next variation is ready as soon as you pause - Do a single review round after design stage - Stay between low to mid level of effort - Launch more tests - More variations per hypothesis Just follow the process. And then improve it. A higher velocity means more wins and faster wins, assuming you maintain your current win rate. That is, only if the quality of the work stays the same. Follow the process. Test faster.

𝗧𝗵𝗲 𝗣𝗼𝘄𝗲𝗿 𝗼𝗳 𝗖𝗹𝗲𝗮𝗿 𝗧𝗲𝘀𝘁 𝗜𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗶𝗼𝗻𝘀: 𝗟𝗲𝘀𝘀𝗼𝗻𝘀 𝗳𝗿𝗼𝗺 𝗮 𝗛𝘂𝗺𝗼𝗿𝗼𝘂𝘀 𝗩𝗶𝗱𝗲𝗼 In the world of software testing, clear and precise instructions are paramount. A recent video I came across brilliantly illustrates this point through a humorous and engaging example. This video serves as a light-hearted reminder of the importance of clear instructions in testing. By emphasizing precision, communication, and thorough documentation, we can enhance the quality and reliability of our software testing processes. Understanding the end-user perspective helps design tests that align with real-world scenarios and user expectations. #SoftwareTesting #QualityAssurance #TestingBestPractices #AgileTesting #UserCentricTesting 𝘄𝗮𝘁𝗰𝗵 𝘁𝗵𝗲 𝘃𝗶𝗱𝗲𝗼 𝗵𝗲𝗿𝗲:

Making your policy deliver accurate results in practice can be challenging. We share five tactics that are easy to test, likely to boost accuracy, and fast to implement. 1️⃣ Build a moderation flowchart with Typeform or GPT 2️⃣ Write your policy guidelines as sequential steps 3️⃣ Get your policy to fit on one screen 4️⃣ Hackathon your policy guidelines with product and engineering colleagues 5️⃣ Get everyone, yes everyone, to do some real moderation Bonus tip: Optimize your guidelines with Unitary's help! Read the full article linked in the comments✨

How do you get students involved in team testing? Check out this video to find out!

🚀 Here's an incredible session by Ellie Hughes from Experiment Nation’s Conference! Watch this and learn: 1️⃣ Don’t get paralyzed by prioritization - be open to pivoting based on new evidence. 2️⃣ Always check your statistics and tagging - you don’t want to dilute your experiment results. 3️⃣ Optimize for value vs. velocity - focus on impactful experiments, not just the number of experiments per month. Ellie’s insights on A/B testing fallacies and practical tips are so valuable. If you’re looking to level up your experimentation program, I highly recommend watching the full video here: https://lnkd.in/gB68_SqX If you'd like to support our modest CRO / Experimentation community, consider subscribing to our YouTube channel. Every bit helps! #Experimentation #ABTesting #MarketingStrategy

Figuring out how to get accurate moderation results starts with the policy. Here are some handy tips we've put together to help people get the best out of their policies. 🤓

It only makes sense to write a test if we first see it fail. The test must fail for a valid reason. If we don't know why the test fails, our approach is wrong. Once we see the test fail, we work on making it pass. When it passes, it should never fail again. If it does, roll back.

Tell the truth! Tell the truth to yourself: If you're not solving that one problem, figure out why you're not shipping that today. ☕️ Use the set of truths as unit tests. Write down which truths don't exist yet, and keep running your truth unit tests every single day.