35. Building Bridges: Thriving with Low Maturity Engineering Teams

35. Building Bridges: Thriving with Low Maturity Engineering Teams

Are you and your engineers constantly at each other’s throats? Always blaming each other for delays? Always fighting over why the final production UI doesn’t look anything like your wires? Are they constantly adding in features at the last minute but never involving the design team?

You may be working with a low-maturity software team.

This week we’re continuing the “From Chaos to Clarity” series with a deep dive into engineering team low-operational maturity.

it can be a real challenge working with an engineering team with inconsistent processes that always expect the UX team to deliver at the last minute.

If you’ve ended up working with an engineering team that doesn’t function as smoothly as you’d like, there is hope.

It’s possible to turn this around and make the best of this situation. There are some things you can try to build stronger relationships with your engineering team and make it work, even if you can’t change the culture of the entire team.

So let’s explore some ways we can tear down these walls and build some bridges and learn to thrive with a low-maturity engineering team.

Topics:
• 03:27 – There are many different maturity models out there
• 04:07 – The five levels of the CMMI maturity model
• 09:21 – High or low maturity indications
• 12:03 – Engineers are brilliant people and they want to build great software
• 13:00 – problems UX designers might run into
• 17:25 – How I’ve applied this in my own work.
• 25:59 – Remember those things from Episode 33
• 26:31 – Add to your stakeholder map
• 27:14 – Collaborate early and often
• 28:05 – Explain the product and process
• 29:57 – Think about design systems or component library
• 31:03 – Use a tool like Storybook.js
• 31:45 – Get advice on components
• 32:13 – Attend Scrum ceremonies
• 33:28 – Recap

Helpful Links:
Resolving Conflicts Between Designers And Engineers | Smashing Magazine
Product designers are clashing with developers, and it’s ugly | UX Collective
The Integration of User Experience into Software Development | UXmatters
Understanding the Collaboration Difficulties Between UX Designers and Developers in Agile Environments | Purdue University
CMMI Levels of Capability and Performance | ISACA
How to increase the UX maturity of Scrum teams | UXDesign.cc

This Week’s Audio Book

Check out Influencer: The New Science of Leading Change by Joseph Grenny, Kerry Patterson, David Maxfield, Ron McMillan, and Al Switzler.

The book offers insight into the nature of influence and the vital role it plays in leadership and enacting change, even when you don’t have a position of authority. The authors go through different sources of influence like personal, social, and structural, and they review some real-world examples that use these ideas. They also provide some practical strategies to effect behavioral changes.



Thanks for listening! We hope you dug today’s episode. If you liked what you heard, be sure to like and subscribe wherever you listen to podcasts! And if you really enjoyed today’s episode, why don’t you leave a five-star review? Or tell some friends! It will help us out a ton.

If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

Get a FREE audiobook AND support the show
Support the show on Patreon
Check out show transcripts
• Check out our website
• Subscribe on Apple Podcasts
• Subscribe on Spotify
• Subscribe on YouTube
• Subscribe on Stitcher

Support my caffeine addiction

Meet your host

Jeremy Miller

Designer // Host // Mentor

I’m Jeremy. I’m a product designer from New Orleans. Here are some things I want you to know about me:

But most importantly, I know you can’t build great software without great relationships.

So join me here and learn about how to build truly great software.

Type at least 1 character to search