There are two separate rollout types for Hacker's Mind: Peer Scheduling and Predefined Lead. This article will help you determine which rollout is best for you.
- What are your goals?
- Potential cons of each session type
- Peer Scheduling Case Studies
- Predefined Lead Case Studies
What are your goals?
If your goals are:
- To give employees the choice to pick the time that works for them to complete their Hacker's Mind session.
- To have sessions of Hacker's Mind include members of different teams. This spurs a broader range of discussions and helps your employees learn more about the roles and responsibilities of different teams. It is also a great way to build bridges outside of your silo.
- To reduce the level of effort for your security team in rolling out Hacker's Mind.
- To have more than 200 employees participating in Hacker's Mind.
Then we recommend the Peer Scheduling rollout.
If your goals are:
- To have a manager or a security team member to be in every session. We do not believe this is a requirement, and employees learn and have productive conversations without a security team member present.
- To have close control of each session.
Then we recommend the Predefined Lead rollout.
When in doubt, we recommend a Peer Scheduling rollout.
What are the potential cons of each session type?
For Peer Scheduling, you will want to consider:
- You will need to book all the rooms and assign a video-conference for each session. This is upfront work and requires a partnership with your facilities team.
For Predefined Lead, you will want to consider:
- Employees will not have an option for when they complete the session; they will be told by their session leader when and where to show up.
- You will require a manager, security champion, or security team member to lead each session.
- The session leader will be required to send emails outside of our product, based on campaign email templates, and book their own rooms.
Multinational rollout | 1500+ employees
- This customer rolled out to 16 different offices around the globe, ranging in size from 15 - 500 employees, and 100+ remote employees as their mandatory annual security training.
- They grouped their employees based on location and set up campaigns for each office and for groupings of time zones where remote employees were based.
- They rolled out over the course of 4 months, launching new office campaigns every few weeks.
Phased rollout by team | 400+ employees
- This customer rolled out first with their customer and service teams and then followed on with finance, sales, and marketing teams.
- They set up a campaign for their customer team first with sessions in multiple locations over the course of six weeks.
- After a successful first campaign, they expanded to other teams using a similar rollout strategy.
Manager led rollout | 200 employees
- This customer did a top-down manager rollout of Hacker's Mind as their annual training requirement. They started with a C-Suite Hacker's Mind session and then had each member of their leadership team facilitate a session with their direct reports.
- They continued this top-down rollout until all employees had participated in Hacker's Mind.
- This rollout took six weeks and required managers to play twice, once with their peers and once with their team.
Security team led rollout | 100 employees
- This customer had a security team member lead every session of Hacker's Mind, which they were using as their annual training requirement.
- They divided the company up and hosted sessions over a period of 2 months.
- They then held new hire sessions each month to catch up those who had just joined the company.
If you have additional questions about which option is best for you and your specific needs, please reach out to your customer success manager.