Dom Spallino

Most documentation problems don’t start with bad writing. They start with no shared rules. Style guides turn scattered docs into a system: → clearer instructions → consistent terminology → documentation that actually scales Our latest blogpost breaks down the essential technical writing style manuals, when to use each, and why they’re still the backbone of great docs—even in an AI-assisted world. 👉 Read more — link in comments

1

1 Comment

V28 isn’t just a coding update. It’s a shift in how clinical logic, documentation defensibility, and audit risk actually work. Many organizations are treating V28 like past model changes. Same workflows. Same reviews. Same assumptions. That’s the problem. V28 introduces tighter condition logic, higher evidence thresholds, and less tolerance for ambiguity. What used to “pass” quietly now fails loudly and at scale. ▪️ Manual review alone can’t reliably keep up ▪️ Retrospective fixes arrive too late ▪️ Clinicians are absorbing more cognitive load, not less This is why AI has to shoulder the complexity. Not as an add-on. As infrastructure. We break down what V28 really changes, where teams are getting exposed, and why human-only processes won’t hold in 2025 and beyond 👉 https://hubs.ly/Q03ZyNKK0 ⬇️ Curious how others are adapting: Where is V28 creating the most friction for your organization right now? #RiskAdjustment #V28 #HealthcareAI #ValueBasedCare #MedicareAdvantage #Inferscience

1

Turn your screen time into a paycheck. 💸 📱 QA testing is one of the best ways to build tech skills while earning extra cash, but you need a plan. My latest article covers: ✅ How to prioritize high-payout bugs ✅ Managing your "Test Lab" on a budget ✅ Balancing uTest with your 9-to-5 Check the link in my bio to read the full guide!https://link.utest.com/5p6 #QA #QualityAssurance #uTest #SideHustle #TechLife #FreelanceLife

51

5 Comments

Here's the problem with most QA programs: they're obsessed with measuring what happened, but they completely miss the why. Your agent had a low satisfaction score? That's the what. But was it because of poor system training, unclear processes, or something else entirely? Without understanding the root cause, you're just playing quality assurance whack-a-mole. QEval® goes deeper than surface metrics. Our conversation pattern analysis uncovers the real drivers behind negative outcomes - the insights that actually drive meaningful change. Stop playing whack-a-mole with symptoms. Start solving problems at the source. See root cause insights in action: https://lnkd.in/d3M-WPr4 #RootCauseAnalysis #QEval #ContactCenter #ConversationIntelligence 

4

Would your Section 508 review pass a second opinion?    True compliance isn’t when one tester says, “it’s good.” It’s when two independent testers reach the same conclusion, with 98% accuracy or better.    When you check “compliant,” you’re not just ticking a box. You’re signing your name to say you understand the criterion, verified it yourself, and stand by it. That’s a professional promise.    And if two testers disagree? That’s not a problem – that’s progress. It’s how we uncover gaps in interpretation, strengthen consistency, and build a culture of accountability. Measure twice, cut once.    How does your team handle peer review differences? 👇    #Section508 #DigitalAccessibility #TrustedTester #ADA

7

Documentation works best when it answers questions before they’re asked. When it doesn’t, those questions show up later, when timelines are tighter and stakes feel higher. At that point, even simple clarifications take more effort than they should. Early clarity usually pays off downstream.

2

1 Comment