ºÝºÝߣshows by User: AaronKovalcsik / http://www.slideshare.net/images/logo.gif ºÝºÝߣshows by User: AaronKovalcsik / Thu, 14 Jun 2018 13:40:43 GMT ºÝºÝߣShare feed for ºÝºÝߣshows by User: AaronKovalcsik Using a Google Design Sprint as a product superpower /slideshow/using-a-google-design-sprint-as-a-product-superpower/102451701 scotlandv2-180614134043
At the beginning of the year, our senior leadership team was going product by product and deciding which ones were worth funding and which ones should have their talent re-assigned. The product I work on from within the Indeed Tokyo tech office rivaled some of the biggest competitors in the market and leveraged a team smaller than most start-ups. Obviously we thought our product was safe from such a massive culling and thought the value of our team was well known within the company. Unfortunately, that was not the case - and our product was now on the chopping block. The senior leadership team asked us to answer 3 questions: prove that there was a user need for this, prove there was a business need, and prove that there is a roadmap and vision worth investing in. With our jobs on the line and a product we believed in, we decided to prove that our product was worth continued investment. There were many tools that we could have chosen to do this, but we decided to use a Google Design Sprint as the cornerstone to our strategy for answering these core questions. Our team undertook coordinating 2 back-to-back sprints that incorporated remote and local participants from marketing, product, customer service, sales, engineering, QA, and UX teams in a truly global effort. In true Indeed fashion, we modified the Google Design Sprint script slightly to fit Indeed's work culture and accommodate local and remote experts. With this session I will identify where we differed from the sprint book, the effort we undertook to coordinate a global sprint, and the lessons we learned about proving value in a product and defining a long-term vision. The session itself follows a dramatic story arc detailing how our jobs were on the line, the challenges our team faced coordinating 2 back-to-back global sprints, and the eventual outcome that paves the way for continued investment in our product and a vision. However, the core concept is that regardless of the outcome of the sprint, we were building a cohesive and cross-functional team that could carry out a product launch from across the org chart successfully. We weren’t just building a product in 5 days - we were building a global team capable of working together to drive a successful product launch.]]>
At the beginning of the year, our senior leadership team was going product by product and deciding which ones were worth funding and which ones should have their talent re-assigned. The product I work on from within the Indeed Tokyo tech office rivaled some of the biggest competitors in the market and leveraged a team smaller than most start-ups. Obviously we thought our product was safe from such a massive culling and thought the value of our team was well known within the company. Unfortunately, that was not the case - and our product was now on the chopping block. The senior leadership team asked us to answer 3 questions: prove that there was a user need for this, prove there was a business need, and prove that there is a roadmap and vision worth investing in. With our jobs on the line and a product we believed in, we decided to prove that our product was worth continued investment. There were many tools that we could have chosen to do this, but we decided to use a Google Design Sprint as the cornerstone to our strategy for answering these core questions. Our team undertook coordinating 2 back-to-back sprints that incorporated remote and local participants from marketing, product, customer service, sales, engineering, QA, and UX teams in a truly global effort. In true Indeed fashion, we modified the Google Design Sprint script slightly to fit Indeed's work culture and accommodate local and remote experts. With this session I will identify where we differed from the sprint book, the effort we undertook to coordinate a global sprint, and the lessons we learned about proving value in a product and defining a long-term vision. The session itself follows a dramatic story arc detailing how our jobs were on the line, the challenges our team faced coordinating 2 back-to-back global sprints, and the eventual outcome that paves the way for continued investment in our product and a vision. However, the core concept is that regardless of the outcome of the sprint, we were building a cohesive and cross-functional team that could carry out a product launch from across the org chart successfully. We weren’t just building a product in 5 days - we were building a global team capable of working together to drive a successful product launch.]]> Thu, 14 Jun 2018 13:40:43 GMT /slideshow/using-a-google-design-sprint-as-a-product-superpower/102451701 AaronKovalcsik@slideshare.net(AaronKovalcsik) Using a Google Design Sprint as a product superpower AaronKovalcsik At the beginning of the year, our senior leadership team was going product by product and deciding which ones were worth funding and which ones should have their talent re-assigned. The product I work on from within the Indeed Tokyo tech office rivaled some of the biggest competitors in the market and leveraged a team smaller than most start-ups. Obviously we thought our product was safe from such a massive culling and thought the value of our team was well known within the company. Unfortunately, that was not the case - and our product was now on the chopping block. The senior leadership team asked us to answer 3 questions: prove that there was a user need for this, prove there was a business need, and prove that there is a roadmap and vision worth investing in. With our jobs on the line and a product we believed in, we decided to prove that our product was worth continued investment. There were many tools that we could have chosen to do this, but we decided to use a Google Design Sprint as the cornerstone to our strategy for answering these core questions. Our team undertook coordinating 2 back-to-back sprints that incorporated remote and local participants from marketing, product, customer service, sales, engineering, QA, and UX teams in a truly global effort. In true Indeed fashion, we modified the Google Design Sprint script slightly to fit Indeed's work culture and accommodate local and remote experts. With this session I will identify where we differed from the sprint book, the effort we undertook to coordinate a global sprint, and the lessons we learned about proving value in a product and defining a long-term vision. The session itself follows a dramatic story arc detailing how our jobs were on the line, the challenges our team faced coordinating 2 back-to-back global sprints, and the eventual outcome that paves the way for continued investment in our product and a vision. However, the core concept is that regardless of the outcome of the sprint, we were building a cohesive and cross-functional team that could carry out a product launch from across the org chart successfully. We weren’t just building a product in 5 days - we were building a global team capable of working together to drive a successful product launch. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/scotlandv2-180614134043-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> At the beginning of the year, our senior leadership team was going product by product and deciding which ones were worth funding and which ones should have their talent re-assigned. The product I work on from within the Indeed Tokyo tech office rivaled some of the biggest competitors in the market and leveraged a team smaller than most start-ups. Obviously we thought our product was safe from such a massive culling and thought the value of our team was well known within the company. Unfortunately, that was not the case - and our product was now on the chopping block. The senior leadership team asked us to answer 3 questions: prove that there was a user need for this, prove there was a business need, and prove that there is a roadmap and vision worth investing in. With our jobs on the line and a product we believed in, we decided to prove that our product was worth continued investment. There were many tools that we could have chosen to do this, but we decided to use a Google Design Sprint as the cornerstone to our strategy for answering these core questions. Our team undertook coordinating 2 back-to-back sprints that incorporated remote and local participants from marketing, product, customer service, sales, engineering, QA, and UX teams in a truly global effort. In true Indeed fashion, we modified the Google Design Sprint script slightly to fit Indeed&#39;s work culture and accommodate local and remote experts. With this session I will identify where we differed from the sprint book, the effort we undertook to coordinate a global sprint, and the lessons we learned about proving value in a product and defining a long-term vision. The session itself follows a dramatic story arc detailing how our jobs were on the line, the challenges our team faced coordinating 2 back-to-back global sprints, and the eventual outcome that paves the way for continued investment in our product and a vision. However, the core concept is that regardless of the outcome of the sprint, we were building a cohesive and cross-functional team that could carry out a product launch from across the org chart successfully. We weren’t just building a product in 5 days - we were building a global team capable of working together to drive a successful product launch.
Using a Google Design Sprint as a product superpower from Aaron Kovalcsik
]]> 1340 8 https://cdn.slidesharecdn.com/ss_thumbnails/scotlandv2-180614134043-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-AaronKovalcsik-48x48.jpg?cb=1528983643 http://instagram.com/tokyoux.aaron