Enabler 3: Developer Communications Plan

While the first two enablers focus on building the foundational aspects of your secure coding program (by establishing goals and gaining leadership buy-in), Enabler 3 is one of the first steps to implementing your program for teams across your organization.

Your Developer Communications Plan establishes an ongoing strategy designed to keep the developer community excited and engaged with your program.

A successful communications plan maintains an informative communication stream throughout the year, covering events, new assignments, developer recognition, and more. Messages should be clear, concise, and delivered across developers’ preferred channels (email, intranet, Slack, Teams, etc.).

Your Developer Communications Plan establishes an ongoing strategy designed to keep the developer community excited and engaged with your program. 

A successful communications plan maintains an informative communication stream throughout the year, covering events, new assignments, developer recognition, and more. Messages should be clear, concise, and delivered across developers’ preferred channels (email, intranet, Slack, Teams, etc.).

Addressing the Developer Perspective

In addition to logistical information like platform login details and assignment due dates, communications must explicitly address the questions, "What’s in it for me?" and "Why should I care?”. Speaking specifically to the developer perspective shows that you understand the time investment made by developers to participate in your secure coding program, whether it is mandated or not.

Initial program launch communications should clearly link your organization’s secure coding program to critical business outcomes (established in Enabler 1) and to developer benefits. For developers, team leads, and engineering managers, these benefits include:

Reward and recognition

Reducing friction during release cycles

Saving time and frustration resulting from rework

Opportunities for skill development and career advancement

Internal support from Engineering and AppSec leadership

‍

‍Execution and Strategy

A secure coding program cannot rely on a "one-and-done" communication approach. A comprehensive communications plan requires a well distinguished Timeline outlining when launch, follow-up, and reinforcement messages will be sent.

Executive Participation in Program Announcement

Having initial program announcements delivered by executive leadership can help gain developer buy-in. This will help showcase that leaders have visibility into the program and allow them to communicate the why of the program from the start.

When formulating communications, essential elements to consider include content, clarity, consistency, and the credibility of the sender. Also, consider the following:

Tone: The communication tone should be positive and encouraging, prioritizing "More 'carrot' than 'stick'". It is crucial to avoid language that is browbeating or uses finger-pointing, and instead highlights the benefits to gain traction.

Channels: While formal email communications can serve as a backup, more informal channels (such as internal developer communication platforms) should also be utilized. Consider building channels exclusively for program communications, announcements, and developer recognition.

Frequency: It is essential to strike the right frequency for program communications, so that developers stay informed, but not overwhelmed. During the initial rollout and other higher-intensity phases (when training deadlines approach), consider daily communications that count down to your program. However, during routine maintenance periods, veer towards monthly communications. The last thing you want is for developers to check out because there is too much white noise.

Evangelists: Look for credible evangelists within the developer community to help amplify the messaging and promote the program. These champions lead by example and continue to amplify key messages from within the community.

Measuring and Recognizing Success

Developer communications are often the perfect place to showcase rewards and recognition for developer achievements in your program. In addition to celebrating their wins, it is essential  that developers know what targets they are trying to attain as well as their progress on the way to those targets. 

A monthly newsletter or program recap may be the perfect place to showcase:

• Completion Rates - For organizational targets, consider creating team incentives for those who finish fastest!
• Certificates / Badges Earned - Celebrate those who have completed secure code training to promote the achievements to other developers.
• Developers with the Highest Skill - Highlight those developers with special security skills. Not only does it acknowledge their achievements, but it also helps others identify 'go-to' experts for secure coding expertise.
• Competition Winners - Secure coding competitions are not only a great way to engage developers, but also an opportunity to showcase winners and the prizes they’ve won. This can help build a following for annual competitions and to help further motivate the rest of your developer community.
• And More!
  ‍

We’ll dive deeper into Developer Recognition later in the series when we explore Enabler 7.

With our Developer Communications plan now established, our next post will focus on further program implementation, with Enabler 4: Low Barrier to User Access.

Have additional questions?  Customers can reach out to account team members or to support@securecodewarrior.com. Prospective customers can speak to someone on our sales team by contacting us here.