[{"data":1,"prerenderedAt":517},["ShallowReactive",2],{"/en-us/the-source/platform/building-a-communication-strategy-for-platform-engineering-teams":3,"footer-en-us":50,"the-source-banner-en-us":384,"the-source-navigation-en-us":390,"article-site-categories-en-us":413,"the-source-newsletter-en-us":415,"building-a-communication-strategy-for-platform-engineering-teams-article-hero-category-en-us":422,"building-a-communication-strategy-for-platform-engineering-teams-the-source-source-cta-en-us":447,"building-a-communication-strategy-for-platform-engineering-teams-article-hero-author-en-us":457,"building-a-communication-strategy-for-platform-engineering-teams-category-en-us":482,"building-a-communication-strategy-for-platform-engineering-teams-the-source-resources-en-us":495},{"id":4,"title":5,"body":6,"category":7,"config":8,"content":14,"description":6,"extension":41,"meta":42,"navigation":12,"path":43,"seo":44,"slug":46,"stem":47,"type":48,"__hash__":49},"theSource/en-us/the-source/platform/building-a-communication-strategy-for-platform-engineering-teams.yml","Building A Communication Strategy For Platform Engineering Teams",null,"platform",{"layout":9,"template":10,"author":11,"featured":12,"sourceCTA":13},"the-source","TheSourceArticle","bryan-ross",true,"source-lp-measuring-success-in-software-development-a-guide-for-leaders",{"title":15,"date":16,"description":17,"timeToRead":18,"heroImage":19,"keyTakeaways":20,"articleBody":24,"faq":25},"Building a communication strategy for platform engineering teams","2025-06-17","Discover how to create a communication framework for platform engineering that increases adoption, builds trust, and shows value.","6 min read","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463500/aw80z4omecn1zduruwhi.png",[21,22,23],"Effective communication is foundational to platform engineering success, directly impacting user adoption, satisfaction, and leadership support.","A multi-channel approach using product websites, blogs, health dashboards, documentation, emails, and chat platforms creates a comprehensive communication ecosystem.","Communication must be tailored to different audiences — from technical users needing implementation details to executives requiring value demonstrations.","Picture this: Your [platform engineering team](https://about.gitlab.com/the-source/platform/platform-engineering-its-about-culture-not-tools/) has spent months perfecting an internal solution that dramatically reduces deployment times and eliminates configuration errors. Yet three months after launch, adoption remains disappointingly low. The culprit? Not technical shortcomings but communication gaps.\n\nEven the most powerful internal developer platform will fail without effective communication. I consistently see technically sound platforms struggling with adoption because potential users don’t understand their value or how to use them.\n\nYour platform’s technical excellence means nothing if engineers don’t adopt it or leadership doesn’t fund its continuous improvement. Strategic communication bridges the gap between platform capability and business impact, transforming your technical innovation into measurable value that resonates with developers and executives.\n\n## Crafting effective rollout communications\nBefore diving into ongoing communication channels, we must address a crucial moment: your platform’s initial launch. Whether you’re communicating through email, Slack, or a real-time presentation, how you introduce your platform sets the foundation for adoption and engagement.\n\n**Start with the “why” behind your platform**. Engineers are naturally skeptical of new tools that appear to add complexity. Your communications should clearly explain how the platform reduces cognitive load, minimizes context switching, improves documentation access, and enables faster development cycles. Frame benefits as concrete improvements to daily workflows rather than abstract concepts. For example, highlight how automating environment setup can save each developer 5-7 hours weekly instead of simply claiming “increased productivity.”\n\n**Anticipate and address resistance points proactively**. Engineers often worry about how new platforms integrate with their preferred tools or disrupt established workflows. Your communications should acknowledge these concerns directly and explain integration capabilities, migration paths, and support options. Consider creating an FAQ document that addresses common objections before they arise. Being transparent about current limitations while sharing your roadmap builds credibility and sets appropriate expectations.\n\n**Recruit platform champions to amplify your message**. Identify respected technical colleagues who contributed to the platform’s development or successfully used early versions. Their authentic endorsements carry significantly more weight than official communications alone. Create opportunities for these champions to demonstrate the platform’s capabilities through lightning talks, recorded demos, or pair programming sessions. These peer-to-peer interactions allow potential users to see practical applications and ask candid questions in a low-pressure environment.\n\nOnce you’ve launched the platform, you’ll need to keep the communication with your users open. Let’s explore the five critical communication channels that should be part of every platform engineering team’s ongoing strategy.\n\n## The essential communication channels\n### Documentation\nGreat documentation - ideally in an editable wiki or intranet that everyone can contribute to - is transformative for platform adoption. It dramatically reduces support overhead and [accelerates user onboarding](https://about.gitlab.com/the-source/platform/transform-your-platform-onboarding-for-higher-adoption-rates/). Intentionally recording your knowledge is one of the most selfless and positive changes you can make in a team.\n\nYour documentation needs to answer three questions concisely: What problem does your platform solve, what benefits can developers expect, and where can they find more information?\n\nEffective documentation puts users first, organizing information around their journey rather than system architecture. It should also include:\n- Straightforward \"Getting Started\" guides showing how easily basic use cases can be implemented\n- A comprehensive knowledge base for more complex scenarios\n- Clear examples and code snippets that users can adapt\n- Regular updates that keep pace with platform changes\n\nThe best documentation anticipates user questions rather than just documenting system capabilities.\n\n### Team blog\nConsider creating an internal blog for your platform engineering team where they can share ideas and solutions with the platform users. A dedicated blog space enables your team to share deeper context about your platform that wouldn’t fit in brief communications. Blog posts allow you to:\n- Provide technical deep dives with diagrams or videos\n- Give users insights into how your platform operates\n- Cultivate knowledgeable platform advocates\n- Build trust through transparency\n- Give team members practice with technical communication\n- Share success stories or interesting use cases for the platform\n\nBlog content helps users understand how to use your platform and why certain design decisions were made, making them more effective users and potential advocates.\n\n### Health dashboard\nWhen users encounter platform issues, nothing frustrates them more than silence. A health dashboard provides immediate visibility into known issues and their resolution status.\n\nAn effective dashboard serves multiple purposes in your communication strategy. First, it builds trust by acknowledging problems quickly rather than leaving users to wonder if issues will be addressed. During widespread outages, a dashboard significantly reduces duplicate support requests by providing a central source of truth about system status. Prospective users often review these dashboards to evaluate how reliably you operate before committing to your platform. Perhaps most importantly, a transparent health dashboard demonstrates your team’s commitment to openness and accountability, qualities that foster long-term trust with your user community.\n\nRemember that dashboards must be accurate to maintain credibility. A dashboard showing all green systems during a known outage will destroy user trust. Similarly, reported problems should always include resolution updates.\n\n### Email updates\nDespite inbox overload, email remains effective for periodic platform updates. Monthly newsletters help maintain awareness of your platform’s ongoing development and improvements.\n\nThese communications serve two purposes:\n- Informing users about new features, improvements, and upcoming changes\n- Demonstrating continuous momentum and investment in the platform\n\nRemember that most recipients will skim emails for just a few seconds. Make key points stand out with clear formatting, concise language, and visual hierarchy. The communication reinforces your team's active presence even if users don’t read every word.\n\n### Real-time messaging\nYour team should maintain a presence wherever your users naturally collaborate - which often means real-time chat platforms like Slack. Chat builds relationships with users through accessibility and responsiveness, creating a community around your platform. Here are a few golden rules teams can follow to ensure they’re building a good relationship with their users:\n\n**Respond to queries promptly**. Chat moves quickly. Teams should aim to respond to user questions within 30-60 minutes during business hours to maintain engagement and show users they’re valued. It’s not ideal if users are chatting in real time about your product and your team is nowhere to be found.\n\n**Present a consistent voice to users**. Think of your organization’s messaging systems as a “public” customer service channel. Maintain a separate “internal” channel where engineers can debate and discuss conflicting viewpoints. A user should never see two engineers debating with one another - they both lose credibility.\n\n**Document solutions publicly**. After resolving an inquiry, ensure that engineers update the channel with the outcome so other users can benefit from the knowledge.\n\n**Open support tickets for users**. Chat is great for quick questions, but more complicated requests should be tracked in issue management software. Instead of directing users to “open a ticket,” ensure your engineers can do this on behalf of the user.\n\n## Bringing it all together\n[Effective platform engineering](https://about.gitlab.com/the-source/platform/driving-business-results-with-platform-engineering/) requires a holistic approach to communication that combines all these channels into a cohesive strategy. Each channel serves distinct purposes and reaches different segments of your audience.\n\nBy implementing this comprehensive framework, your platform team can build trust, demonstrate value, and drive adoption - ultimately ensuring that your technical capabilities translate into business impact.\n\nRemember that in enterprise environments, how you communicate about your platform often matters as much as the platform itself. Invest in communication with the same care you invest in your technical infrastructure.",[26,29,32,35,38],{"header":27,"content":28},"What role does communication play in successful platform engineering?","Communication is foundational to platform engineering success. Even the best technical platforms will fail if users don’t understand their value, know how to use them, or feel supported. Communication drives adoption, builds trust, and helps secure long-term investment.",{"header":30,"content":31},"Why do platform rollouts fail even when the tech is solid?","Rollouts often fail due to poor communication. If developers don’t see clear benefits, or if concerns around workflow disruption and tool integration aren't addressed, adoption stalls. Successful rollouts proactively explain value, anticipate objections, and include trusted advocates to build credibility.",{"header":33,"content":34},"What communication channels should every platform team use?","A strong communication strategy includes five core channels: detailed documentation, a team blog, a live platform health dashboard, periodic email updates, and real-time messaging on platforms like Slack. Each channel supports different user needs and helps ensure ongoing engagement.",{"header":36,"content":37},"How should platform teams communicate with technical vs. executive stakeholders?","Communication should be tailored to each audience. Developers need technical guidance and practical examples. Executives need clear demonstrations of platform impact, such as improved delivery speed or reduced support costs. One message rarely fits both groups.",{"header":39,"content":40},"What’s the benefit of having a health dashboard for your platform?","A transparent health dashboard builds trust by showing users what’s working and what’s not. It reduces support noise during issues, demonstrates accountability, and assures users that problems are known and being resolved.","yml",{},"/en-us/the-source/platform/building-a-communication-strategy-for-platform-engineering-teams",{"title":15,"description":17,"ogImage":19,"config":45},{"ignoreTitleCharLimit":12},"building-a-communication-strategy-for-platform-engineering-teams","en-us/the-source/platform/building-a-communication-strategy-for-platform-engineering-teams","article","uvF_arptQEkRG_XUuVS8dFEh4Msh8EF4BDvAlvXnlog",{"data":51},{"text":52,"source":53,"edit":59,"contribute":64,"config":69,"items":74,"minimal":373},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":54,"config":55},"View page source",{"href":56,"dataGaName":57,"dataGaLocation":58},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":60,"config":61},"Edit this page",{"href":62,"dataGaName":63,"dataGaLocation":58},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":65,"config":66},"Please contribute",{"href":67,"dataGaName":68,"dataGaLocation":58},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":70,"facebook":71,"youtube":72,"linkedin":73},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[75,132,189,248,311],{"title":76,"links":77,"subMenu":93},"Pricing",[78,83,88],{"text":79,"config":80},"View plans",{"href":81,"dataGaName":82,"dataGaLocation":58},"/pricing/","view plans",{"text":84,"config":85},"Why Premium?",{"href":86,"dataGaName":87,"dataGaLocation":58},"/pricing/premium/","why premium",{"text":89,"config":90},"Why Ultimate?",{"href":91,"dataGaName":92,"dataGaLocation":58},"/pricing/ultimate/","why ultimate",[94],{"title":95,"links":96},"Contact Us",[97,102,107,112,117,122,127],{"text":98,"config":99},"Contact sales",{"href":100,"dataGaName":101,"dataGaLocation":58},"/sales/","sales",{"text":103,"config":104},"Support portal",{"href":105,"dataGaName":106,"dataGaLocation":58},"https://support.gitlab.com","support portal",{"text":108,"config":109},"Customer portal",{"href":110,"dataGaName":111,"dataGaLocation":58},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":113,"config":114},"Status",{"href":115,"dataGaName":116,"dataGaLocation":58},"https://status.gitlab.com/","status",{"text":118,"config":119},"Terms of use",{"href":120,"dataGaName":121,"dataGaLocation":58},"/terms/","terms of use",{"text":123,"config":124},"Privacy statement",{"href":125,"dataGaName":126,"dataGaLocation":58},"/privacy/","privacy statement",{"text":128,"config":129},"Cookie preferences",{"dataGaName":130,"dataGaLocation":58,"id":131,"isOneTrustButton":12},"cookie preferences","ot-sdk-btn",{"title":133,"links":134,"subMenu":145},"Product",[135,140],{"text":136,"config":137},"DevSecOps platform",{"href":138,"dataGaName":139,"dataGaLocation":58},"/platform/","devsecops platform",{"text":141,"config":142},"AI-Assisted Development",{"href":143,"dataGaName":144,"dataGaLocation":58},"/gitlab-duo/","ai-assisted development",[146],{"title":147,"links":148},"Topics",[149,154,159,164,169,174,179,184],{"text":150,"config":151},"CICD",{"href":152,"dataGaName":153,"dataGaLocation":58},"/topics/ci-cd/","cicd",{"text":155,"config":156},"GitOps",{"href":157,"dataGaName":158,"dataGaLocation":58},"/topics/gitops/","gitops",{"text":160,"config":161},"DevOps",{"href":162,"dataGaName":163,"dataGaLocation":58},"/topics/devops/","devops",{"text":165,"config":166},"Version Control",{"href":167,"dataGaName":168,"dataGaLocation":58},"/topics/version-control/","version control",{"text":170,"config":171},"DevSecOps",{"href":172,"dataGaName":173,"dataGaLocation":58},"/topics/devsecops/","devsecops",{"text":175,"config":176},"Cloud Native",{"href":177,"dataGaName":178,"dataGaLocation":58},"/topics/cloud-native/","cloud native",{"text":180,"config":181},"AI for Coding",{"href":182,"dataGaName":183,"dataGaLocation":58},"/topics/devops/ai-for-coding/","ai for coding",{"text":185,"config":186},"Agentic AI",{"href":187,"dataGaName":188,"dataGaLocation":58},"/topics/agentic-ai/","agentic ai",{"title":190,"links":191},"Solutions",[192,196,201,206,211,215,220,223,228,233,238,243],{"text":193,"config":194},"Application Security Testing",{"href":195,"dataGaName":193,"dataGaLocation":58},"/solutions/application-security-testing/",{"text":197,"config":198},"Automated software delivery",{"href":199,"dataGaName":200,"dataGaLocation":58},"/solutions/delivery-automation/","automated software delivery",{"text":202,"config":203},"Agile development",{"href":204,"dataGaName":205,"dataGaLocation":58},"/solutions/agile-delivery/","agile delivery",{"text":207,"config":208},"SCM",{"href":209,"dataGaName":210,"dataGaLocation":58},"/solutions/source-code-management/","source code management",{"text":150,"config":212},{"href":213,"dataGaName":214,"dataGaLocation":58},"/solutions/continuous-integration/","continuous integration & delivery",{"text":216,"config":217},"Value stream management",{"href":218,"dataGaName":219,"dataGaLocation":58},"/solutions/value-stream-management/","value stream management",{"text":155,"config":221},{"href":222,"dataGaName":158,"dataGaLocation":58},"/solutions/gitops/",{"text":224,"config":225},"Enterprise",{"href":226,"dataGaName":227,"dataGaLocation":58},"/enterprise/","enterprise",{"text":229,"config":230},"Small business",{"href":231,"dataGaName":232,"dataGaLocation":58},"/small-business/","small business",{"text":234,"config":235},"Public sector",{"href":236,"dataGaName":237,"dataGaLocation":58},"/solutions/public-sector/","public sector",{"text":239,"config":240},"Education",{"href":241,"dataGaName":242,"dataGaLocation":58},"/solutions/education/","education",{"text":244,"config":245},"Financial services",{"href":246,"dataGaName":247,"dataGaLocation":58},"/solutions/finance/","financial services",{"title":249,"links":250},"Resources",[251,256,261,266,271,276,281,286,291,296,301,306],{"text":252,"config":253},"Install",{"href":254,"dataGaName":255,"dataGaLocation":58},"/install/","install",{"text":257,"config":258},"Quick start guides",{"href":259,"dataGaName":260,"dataGaLocation":58},"/get-started/","quick setup checklists",{"text":262,"config":263},"Learn",{"href":264,"dataGaName":265,"dataGaLocation":58},"https://university.gitlab.com/","learn",{"text":267,"config":268},"Product documentation",{"href":269,"dataGaName":270,"dataGaLocation":58},"https://docs.gitlab.com/","docs",{"text":272,"config":273},"Blog",{"href":274,"dataGaName":275,"dataGaLocation":58},"/blog/","blog",{"text":277,"config":278},"Customer success stories",{"href":279,"dataGaName":280,"dataGaLocation":58},"/customers/","customer success stories",{"text":282,"config":283},"Remote",{"href":284,"dataGaName":285,"dataGaLocation":58},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":287,"config":288},"GitLab Services",{"href":289,"dataGaName":290,"dataGaLocation":58},"/services/","services",{"text":292,"config":293},"Community",{"href":294,"dataGaName":295,"dataGaLocation":58},"/community/","community",{"text":297,"config":298},"Forum",{"href":299,"dataGaName":300,"dataGaLocation":58},"https://forum.gitlab.com/","forum",{"text":302,"config":303},"Events",{"href":304,"dataGaName":305,"dataGaLocation":58},"/events/","events",{"text":307,"config":308},"Partners",{"href":309,"dataGaName":310,"dataGaLocation":58},"/partners/","partners",{"title":312,"links":313},"Company",[314,319,324,329,334,339,344,348,353,358,363,368],{"text":315,"config":316},"About",{"href":317,"dataGaName":318,"dataGaLocation":58},"/company/","company",{"text":320,"config":321},"Jobs",{"href":322,"dataGaName":323,"dataGaLocation":58},"/jobs/","jobs",{"text":325,"config":326},"Leadership",{"href":327,"dataGaName":328,"dataGaLocation":58},"/company/team/e-group/","leadership",{"text":330,"config":331},"Team",{"href":332,"dataGaName":333,"dataGaLocation":58},"/company/team/","team",{"text":335,"config":336},"Handbook",{"href":337,"dataGaName":338,"dataGaLocation":58},"https://handbook.gitlab.com/","handbook",{"text":340,"config":341},"Investor relations",{"href":342,"dataGaName":343,"dataGaLocation":58},"https://ir.gitlab.com/","investor relations",{"text":345,"config":346},"Sustainability",{"href":347,"dataGaName":345,"dataGaLocation":58},"/sustainability/",{"text":349,"config":350},"Diversity, inclusion and belonging (DIB)",{"href":351,"dataGaName":352,"dataGaLocation":58},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":354,"config":355},"Trust Center",{"href":356,"dataGaName":357,"dataGaLocation":58},"/security/","trust center",{"text":359,"config":360},"Newsletter",{"href":361,"dataGaName":362,"dataGaLocation":58},"/company/contact/#contact-forms","newsletter",{"text":364,"config":365},"Press",{"href":366,"dataGaName":367,"dataGaLocation":58},"/press/","press",{"text":369,"config":370},"Modern Slavery Transparency Statement",{"href":371,"dataGaName":372,"dataGaLocation":58},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":374},[375,378,381],{"text":376,"config":377},"Terms",{"href":120,"dataGaName":121,"dataGaLocation":58},{"text":379,"config":380},"Cookies",{"dataGaName":130,"dataGaLocation":58,"id":131,"isOneTrustButton":12},{"text":382,"config":383},"Privacy",{"href":125,"dataGaName":126,"dataGaLocation":58},{"visibility":12,"title":385,"button":386},"The Intelligent Software Development Era: How AI is reshaping DevSecOps teams",{"config":387,"text":389},{"href":388},"/developer-survey/","Get the research report",{"logo":391,"subscribeLink":396,"navItems":400},{"altText":392,"config":393},"the source logo",{"src":394,"href":395},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":397,"config":398},"Subscribe",{"href":399},"#subscribe",[401,405,409],{"text":402,"config":403},"Artificial Intelligence",{"href":404},"/the-source/ai/",{"text":406,"config":407},"Security & Compliance",{"href":408},"/the-source/security/",{"text":410,"config":411},"Platform & Infrastructure",{"href":412},"/the-source/platform/",{"categoryNames":414},{"ai":402,"platform":410,"security":406},{"title":416,"description":417,"submitMessage":418,"formData":419},"The Source Newsletter","Stay updated with insights for the future of software development.","You have successfully signed up for The Source’s newsletter.",{"config":420},{"formId":421,"formName":362,"hideRequiredLabel":12},1077,{"id":423,"title":424,"body":6,"category":6,"config":425,"content":426,"description":6,"extension":41,"meta":441,"navigation":12,"path":442,"seo":443,"slug":7,"stem":444,"testContent":6,"type":445,"__hash__":446},"pages/en-us/the-source/platform/index.yml","",{"layout":9},[427,434],{"componentName":428,"type":428,"componentContent":429},"TheSourceCategoryHero",{"title":410,"description":430,"image":431},"Learn how to build a DevSecOps framework that sets your team up for success, from planning to delivery.",{"config":432},{"src":433},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463263/bdz7hmhpbmgwvoybcaud.png",{"componentName":435,"type":435,"componentContent":436},"TheSourceCategoryMainSection",{"config":437},{"sourceCTAs":438},[439,13,440],"source-lp-the-ultimate-playbook-for-high-performing-devsecops-teams","source-lp-building-a-resilient-software-development-practice",{},"/en-us/the-source/platform",{"title":410,"description":430,"ogImage":433},"en-us/the-source/platform/index","category","u9v0Yrf14Lhx-hAKL_t8ViZ-OxgRjEc5QiV6CvI6bJc",{"config":448,"title":449,"description":450,"link":451},{"slug":13},"Measuring success in software development: A guide for leaders","Discover how to measure software delivery performance with key metrics that optimize workflows, enhance team productivity, and drive better decisions.",{"text":452,"config":453},"Download the guide",{"href":454,"dataGaName":455,"dataGaLocation":456},"/the-source/platform/measuring-success-in-software-development-a-guide-for-leaders/","Measuring success in software development","thesource",{"id":458,"title":459,"body":6,"category":6,"config":460,"content":461,"description":6,"extension":41,"meta":476,"navigation":12,"path":477,"seo":478,"slug":11,"stem":479,"testContent":6,"type":480,"__hash__":481},"theSourceAuthors/en-us/the-source/authors/bryan-ross.yml","Bryan Ross",{"layout":9},[462,474],{"componentName":463,"type":463,"componentContent":464},"TheSourceAuthorHero",{"config":465,"name":459,"role":469,"bio":470,"headshot":471},{"gitlabHandle":466,"twitterXProfileUrl":467,"linkedInProfileUrl":468},"bryanrossuk","https://twitter.com/bryanrossuk","https://www.linkedin.com/in/bryanross","Field CTO","With over 15 years of industry experience as a senior IT leader, Bryan helps customers realize business value from IT faster. Equally comfortable speaking with executives and engineers alike, he bridges the gap between technical and business stakeholders through compelling storytelling and real-world examples. With a knack for delivering authentic, impactful messages, he enjoys helping others at the intersection of technology, people and process.",{"altText":459,"config":472},{"src":473},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463324/mvdyvskii4hltdrgqxom.jpg",{"componentName":475,"type":475},"TheSourceArticlesList",{},"/en-us/the-source/authors/bryan-ross",{"title":459},"en-us/the-source/authors/bryan-ross","author","fSon_pjQKF1SoSOt3Vg6MC6j1m9Ej0ODYs8fCB-gyB8",{"id":423,"title":424,"body":6,"category":6,"config":483,"content":484,"description":6,"extension":41,"meta":493,"navigation":12,"path":442,"seo":494,"slug":7,"stem":444,"testContent":6,"type":445,"__hash__":446},{"layout":9},[485,489],{"componentName":428,"type":428,"componentContent":486},{"title":410,"description":430,"image":487},{"config":488},{"src":433},{"componentName":435,"type":435,"componentContent":490},{"config":491},{"sourceCTAs":492},[439,13,440],{},{"title":410,"description":430,"ogImage":433},[496,505,509],{"config":497,"title":498,"description":499,"link":500},{"slug":440},"Building a resilient software development practice","Learn strategies to bolster your team's effectiveness amid shifts in the industry with a standardized approach to software development.",{"text":501,"config":502},"Read the guide",{"href":503,"dataGaName":504,"dataGaLocation":456},"/the-source/platform/building-a-resilient-software-development-practice/","Building a Resilient Software Development Practice",{"config":506,"title":449,"description":450,"link":507},{"slug":13},{"text":452,"config":508},{"href":454,"dataGaName":455,"dataGaLocation":456},{"config":510,"title":511,"description":512,"link":513},{"slug":439},"The ultimate playbook for high-performing DevSecOps teams ","Learn how to tackle issues like deployment slowdowns, lack of collaboration, and developer burnout.",{"text":514,"config":515},"Read the ebook",{"href":516,"dataGaName":511,"dataGaLocation":456},"/the-source/platform/the-ultimate-playbook-for-high-performing-devsecops-teams/",1772652114103]