How Can I Collaborate Better with Our Internal Dev Team?

This isn't rare, but it definitely shouldn't be the norm. The persistence of regression bugs suggests there might be deeper issues with how the devs are handling the handoffs or maybe their QA process needs tightening up. You should consider implementing a visual regression testing approach where you use automated tools to catch such errors before they go live. It's crucial that both design and technique are in sync to avoid these recurring problems.

It's great that you have provided such a detailed component library! Make sure you're also emphasizing specifics like font sizes and any measurements in pixels or ems to avoid confusion. If the issues keep resurfacing, it might indicate the developers aren’t taking the feedback seriously or there could be a knowledge gap. Consider discussing your expectations more explicitly with the team to ensure they understand the importance of adhering to the guidelines you've set.

Honestly, it could be a mix of factors here. Regular QA checks should catch these issues, but if they’re not being addressed during development, you may need to reassess the QA process. It could also help to provide clearer documentation around specific design elements, especially with a complex platform like WordPress. Maybe a buddy system where a designer works closely with a developer might improve communication and lead to fewer mistakes!

Sounds like a frustrating situation! It could be that the developers are making changes on their own machines that don’t carry over correctly when moving to production. Sometimes, issues like spacing and font rendering can get overlooked, especially if they’re juggling multiple tasks. It might help to reinforce the importance of following the component library closely. Also, maybe consider scheduling more regular catch-ups during development to keep everyone aligned. Regular communication can often help catch these issues before they become bigger problems in QA.

As a CTO who's dealt with various development teams, I can say that bugs are a common part of the process, especially under tight deadlines. It might be worthwhile to implement a halt on new feature development right before a client onboarding to concentrate on thorough testing. Regularly reviewing the specific bugs that keep coming up together with the dev team could also illuminate whether there’s a larger process issue at play. Setting up a project management tool for clearer visibility on tasks might help keep everyone on track too.