Dummi

Your QA’s are testing too late You can save up to 30X the cost of fixing bugs Nearly every software team will bring in the testers towards the end of the development cycle. This traditional approach appears easy, but can add a big cost to your business. An often referenced study by the IBM Systems Sciences Institute reports that the cost to fix issues increases dramatically the later in the process it is found. That’s where Shift Left Testing comes in. By involving the QA team as far forward as possible, we catch issues sooner, reduce costs, and create a more collaborative environment between dev and QA teams. It is not without its challenges, it requires a different mindset from your team, which can take time to settle. Curious about how to get started? 📢 Check out our latest podcast with a QA expert who dives into practical tips on integrating Shift Left Testing into your workflow: https://lnkd.in/e869j6N3 #SoftwareTesting #ShiftLeft #QA #QualityAssurance #DevOps #SoftwareQuality #LinkedInNetwork

💡 Want to know our secret weapon for project planning? 💡 A poorly planned software project can completely derail your development team (trust us, we have been there!). After years of project planning, we have experienced what works and what does not, and refined a project plan that avoids common pitfalls. This template has allowed us to: ✅ Save time and ship faster ✅ Work more efficiently with our remote teammates ✅ Have better quality software for our customers So how do we do it? We separate the plan into five chapters. Each chapter is designed to avoid common pitfalls and set up projects for smooth sailing: 1️⃣ Purpose and Validation – Understand exactly what problem you are solving and DO NOT jump to a solution before you define the problem 2️⃣ Research and Proposal – The fun part, explore different possible outcomes 3️⃣ Use Cases and Testing – Converting your solution into tasks, and checking your blind spots 4️⃣ Technical Specification – Define architecture, stack, and all tech requirements 5️⃣ Release – Plan a seamless launch and ensure everything’s in place for ongoing support and adoption This template isn’t just theory—it’s practical, tested, and proven to streamline your product development. 👉 WANT ACCESS TO OUR FULL TEMPLATE? Drop a “PLAN” in the comments, and we will send it to you directly! Let’s set your next project up for success. #SoftwareDevelopment #ProjectPlanning #TechSuccess #AgileTeams

🚀 We’re excited to announce “Product Tales” – our brand-new newsletter, packed with hands-on insights for product builders like you! When we launched Dummi, we set out to make product-building clear, collaborative, and impactful. “Product Tales” takes that further, bringing you straight into the core of our process with real stories and strategies that you can apply in your own projects. Our first issue is live, and we’d love for you to join us – subscribe and follow along as we grow together! Read our first issue here: https://lnkd.in/gj5cZGnV In this issue, you’ll meet the product pros: an AI builder (Billy Lam) avoiding tech hype traps, developers transforming bug chaos into calm, and a team leader breaking down barriers in hybrid workplaces (Farran Jonker). #Product #ProductTales #Newsletter #ProductDevelopment #ProductManagement #TeamCollaboration #Dummi #AI

The latest episode of the Product Tales podcast by Dummi is out! Check it out to hear the chat our founder Giulia Dressler had with QA expert Yaroslav Donchuk

Respect is key to building effective international teams. 🌍 In this clip from the Product Tales Podcast, Farran Jonker talks about the importance of embracing cultural differences to create stronger, more unified teams. It’s not just about hiring talent—it’s about making everyone feel valued, no matter where they’re located. Watch the full episode here: https://lnkd.in/eshUA7Zp #RemoteTeams #Leadership #TeamCulture #ProductManagement #GlobalWorkforce

Honesty builds trust. 🗣️ In this clip from the Product Tales Podcast ,Farran Jonker shares how being upfront with users, even when it means saying 'no,' leads to stronger relationships and more trust. It’s all about setting the right expectations from the start. Watch the full episode here: https://lnkd.in/eshUA7Zp #ProductManagement #SaaS #CustomerSuccess #Leadership #RemoteTeams

🔍 The Hidden Cost of Fixing Bugs Nobody Talks About (and How We Fixed It) If you’ve ever managed a software team, you know that bugs can eat up a huge chunk of your time. But here’s the thing: the real problem isn’t always the bugs themselves—it’s the messy communication around them. 🙃 Let me explain. A while ago, we spoke with a senior dev team member at Trail CRM. Their bug reporting process used to be a nightmare — think post-it notes, half-filled bug spreadsheets, and a lot of Slack pings. They were overwhelmed with context-switching and wasting hours trying to reproduce user issues. But when they started focusing on creating a standardized process and optimizing communication between support and dev teams, things shifted: 🔥 They reduced the bug resolution time by 40%. 🔥 Developers finally had clear, reproducible steps and technical info to work with. 🔥 And—most importantly—users saw faster turnarounds for fixes. Here’s what worked for them, and how you can do that too: 1️⃣ Set a Standard for Bug Reports. Avoid the chaos of incomplete reports and random messages. Have a template that captures not just what happened, but who, when, and under what conditions. A solid template saves countless hours. 2️⃣ Create “Shared Language” Between Teams. Support and devs speak two different languages. Use session recordings and screen captures so both teams are literally seeing the same issue. This alignment is key! 3️⃣ Prioritize Clarity Over Speed. Sometimes it’s better to delay a fix by 2 days if it means devs have everything they need. Consistency and clarity beats speed every time when it comes to avoiding future bugs. 💡 Trail CRM’s trick to get these steps implemented in seconds? They started using a tool like Dummi for their bug reporting. ❓What’s the biggest challenge your team faces in handling bugs? Drop your thoughts below 👇! #bugfixing #softwaredevelopment #productmanagement #agile #engineering #teamwork #leadership #bugtracking #productdesign #teamcollaboration #growthmindset

How do you balance user feedback with the vision for your product? 🎯 In this clip from Product Tales Podcast, Farran Jonker, Product Manager at Trail, discusses the fine line between taking user feedback seriously and ensuring it aligns with your product’s long-term goals. Watch the full episode here: https://lnkd.in/eshUA7Zp #ProductManagement #SaaS #RemoteLeadership #UserFeedback #TeamCulture

Building high-performing remote teams across time zones isn’t easy—but it’s possible with the right approach 👀 In this episode of Product Tales Podcast, hosted by our very own Giulia Dressler, we sit down with Farran Jonker, Product Manager at Trail, to explore how culture-first leadership can create strong, cohesive product teams—even when working across borders. Farran shares his experience managing remote teams in Vietnam and New Zealand, and offers valuable insights on fostering trust and alignment across different cultures. 🎧 Listen to the full episode now and discover how to lead remote teams that thrive globally! Spotify: https://lnkd.in/dhgP-5WH Youtube: https://lnkd.in/eshUA7Zp #RemoteTeams #ProductManagement #Leadership #CompanyCulture #Podcast #Dummi

Love AI but not sure how to start incorporating it into your existing product? Tune in to our latest episode of the Product Tales Podcast to hear from Billy Lam, AI expert at Education Perfect, as he shares tips and best practices for building with AI. Listen to it in full here: https://lnkd.in/eeeH5qt6 #AI #Podcast #Product