Overview
The article discusses LinkedIn's Hack Week, a dedicated time for engineers to innovate and build projects outside their regular work. It highlights the structure, outcomes, and lessons learned from this initiative, emphasizing the importance of creativity and collaboration in engineering.
What You'll Learn
1
How to organize a successful Hack Week for engineering teams
2
Why structured brainstorming sessions enhance project feasibility
3
How to measure the success of innovation initiatives through Net Promoter Score
Key Questions Answered
What is the purpose of Hack Week at LinkedIn?
Hack Week at LinkedIn serves to encourage engineers to innovate and collaborate on projects outside their usual work. It allows team members to explore new technologies and solve problems creatively, fostering a culture of experimentation and ownership.
What were the winning projects from Hack Week?
The winning projects from Hack Week included AirDnD, a platform for LinkedIn employees to find available desks in different offices, and an automatic meeting scheduling tool that simplifies the process of coordinating meetings across time zones and locations.
What lessons were learned from running Hack Week?
Key lessons from Hack Week included the importance of choosing the right timing for the event, providing structure to encourage leadership opportunities, and ensuring that participants can focus without interruptions. These insights will help improve future iterations of Hack Week.
Key Statistics & Figures
Net Promoter Score for Hack Week participation
80
This score indicates that 80% of participants would recommend Hack Week to a peer, reflecting high satisfaction with the initiative.
Percentage of engineers who volunteered as project leaders
15
Around 15 percent of engineers took on leadership roles during Hack Week, showcasing a strong willingness to engage in innovative projects.
Technologies & Tools
Communication
Bluejeans
Used for remote participation in brainstorming sessions during Hack Week.
Key Actionable Insights
1Encourage engineers to take ownership of their projects by allowing them to lead their teams during Hack Week.This approach not only fosters leadership skills but also increases engagement and investment in the projects, leading to more innovative outcomes.
2Conduct Hack Week at a time that minimizes conflicts with regular work responsibilities.Scheduling Hack Week during less critical periods allows engineers to fully immerse themselves in their projects, enhancing creativity and productivity.
3Utilize feedback mechanisms like surveys to assess the success of innovation initiatives.Measuring participation satisfaction through metrics like Net Promoter Score can provide valuable insights into the effectiveness of events like Hack Week and guide future improvements.
Common Pitfalls
1
Running Hack Week at a critical time can lead to distractions and reduced focus.
This can hinder creativity and productivity, as engineers may be pulled away to address urgent work tasks. It's essential to choose a period that allows for uninterrupted time.
2
Lack of structured planning can leave project leaders unprepared.
Without requiring leaders to develop a project plan in advance, some may struggle with execution, which can impact the overall success of their projects.
Related Concepts
Innovation In Engineering Teams
Team Collaboration Techniques
Project Management In Tech Environments