This is a guest post by Camilla Velasquez, Justworks' VP of Product.
When youre part of a growing company, its easy to get caught up in the day to day tasks and projects that need to get done. Although thats important for success and growth, its just as important to take a step back and look at the bigger picture.
Our customers are the reason were here to help their businesses run health care, payroll, and compliance smoothly.
Thats why we decided to do a customer-focused, Surprise and Delight hack week this March. So, what did that mean for the Justworks team and customers? For the Product team engineers, product managers, and designers it meant taking a week to focus 100% on coming up with unexpected but delightful projects and executing them. For customers, it meant some new features, which you can see here.
Why Did We Decide on Surprise and Delight Hack Week?
When done right, hack week has the ability to stimulate creative juices, enhance team camaraderie, and allow people to take risks all with fairly low stakes. Its a chance to take some time to focus on the projects we dont always get to do because of our individual domain focus, or top level business priorities.
How Did We Organize Hack Week Ideas?
Overall, we wanted to focus on employees, who are often underserved in HR software the people who regularly use Justworks to enroll in and check their benefits, view the directory and company calendar, and/or review pay stubs. The product works for these users, but rarely delights.
Decreasing meetings during hack week was pivotal for completing projects on time.
So, the week before hack week, we met up and had a comprehensive brainstorming session to get the creative juices flowing and it involved a lot of ideas posted on the wall.
Then, we analyzed those ideas for feasibility. That is, based on how long it would take to execute coupled with the delight it would bring to users. As a fellow teammate Tom put it, It was pretty subjective, but it still offered a loose qualitative metric by which to select hack week projects. Now, we were ready to get started!
Team members got an option to work alone, or tag onto other team members proposed projects if they found them more appealing to work on.
For us, the Surprise and Delight hack week reinforced and introduced some important ways we want to continue working as a cross functional Product team. Here are some major learnings that came out of the experience.
Having the whole team work towards a company-wide awards ceremony for the hack week on Friday encouraged the team to ensure their features were ready to be launched. This really motivated the team and forced the team to think about projects in manageable chunks.
This reinforced that while our Product team has monthly and quarterly goals, weekly deployable milestones allows us to celebrate small wins and reduce risks in our projects.
By hitting more weekly and biweekly milestones, well also have more to demo to our entire company - which means more to celebrate and most importantly, more for other teams (like Sales, Marketing, and CX) to talk about with customers, and sooner. Demoing all the projects for the entire company was a huge morale boost and energized every team across the company. Everyone could not wait to get to their desks to play with the new features.
Transparency is one of our company values and its something we take seriously. As Product pods (what we call our PM-developer-designer groupings by domain area) cross-communicate more about each other's roadmaps, theyll also be more available to help each other and minimize conflicting priorities. During the hack week, as some projects wrapped up, people jumped onto new projects to help them meet the deadline at the end of the week.
Its no secret that too many meetings kill productivity. Removing meetings during the hack week was crucial to increasing the likelihood of projects being finished by the end of the week. If it can be communicated well in an email, well keep choosing that over meetings going forward.
This time around, our theme was Surprise and Delight, which was a nice way to package the projects and keep the brainstorming tight. However, themes can also constrain projects. Its worth considering whether those or open-ended projects are a better direction to take. Going forward, well probably test hack weeks with and without themes.
When we demod in front of the whole company, we voted for our favorites through claps and cheers. Although crowd-based responses are fun, a more organized company voting system will give a better idea of whats bringing the most delight.
Minimizing spillover from hack week is ideal. By shipping as much as possible during the week, well be able to keep up with day to day priorities also.
The design team has weekly critique meetings, but that usually only includes other designers. During the hack week, we included more people who werent on the design team in on the meeting. It helped people to give constructive feedback and seek outside perspectives.
Not only is it fun to include the whole company, but it helps us to continually build product with transparency and helpful feedback from all sides of the business. Next time we might consider a company-wide hack week.
Overall, diving into a customer delight hack week proved both productive and fun, and we cant wait to do it again! Until then, check out all the new product features we shipped by weeks end.
Want to invest in employee incentive programs that work?Get the Guide
This material has been prepared for informational purposes only, and is not intended to provide, and should not be relied on for, legal or tax advice. If you have any legal or tax questions regarding this content or related issues, then you should consult with your professional legal or tax advisor.