- From Voices to Results:Voice of Customer Questions,Tools and Analysis
- Robert Coppenhaver
- 383字
- 2021-08-27 18:54:43
Who's responsible?
According to some practitioners of VoC, they will tell you that the entire product development team is responsible for VoC, that it takes a cross-functional team to sustain the integrity of VoC for the duration of the product cycle. They will put the responsibility on a cross-functional core team, tiger team, or VoC steering committee of 5–7 individuals from marketing, engineering, manufacturing, service and repair, and finance to ensure that the VoC is obtained, processed, and included in your new product.
While I applaud their desire to make sure that VoC is everyone's responsibility, what I have found in most organizations is that when something is "everyone's responsibility", no one ends up being "responsible".
I believe the responsibility of VoC falls squarely on whoever is responsible for product management. That could be a product manager, it could be a product marketing manager, or it could be a marketing manager. It could also be the owner of the business, depending on how big the organization is. The point is, when you are responsible for the product, you are responsible for the product research that includes VoC.
But that does not mean that the rest of the organization can ignore VoC, nor does it mean that only the product manager can play a role in the VoC. What it means is that the product manager is the quarterback in ensuring that the VoC is obtained and included into the product. He/she must organize the activities within the organization to ensure that VoC is being collected and incorporated into the product decisions. He/she must be the one to "sell" the validity of the VoC to the senior staff and the engineering team. He/she must also be the one to bring in other people from other disciplines and make them experience the customer input, which will greatly speed the development process, and make it more likely that a successful product is created. I will talk about this more in Chapter 6, The Interview Process – The Interview, but a huge discovery for me was how much better a development team could perform if you made the engineering team participate in each and every one of the interviews in the interview process. Ultimately, the product manager must be the customer "champion" throughout the development!
- 中國國民經濟核算體系修訂問題研究
- Managing IaaS and DBaaS Clouds with Oracle Enterprise Manager Cloud Control 12c
- Magento 2 Cookbook
- 國有企業經濟責任審計實務指南
- Mastering System Center Configuration Manager
- 會計信息化基礎(金蝶版)
- Big Data Visualization
- Business Intelligence with MicroStrategy Cookbook
- EViews10.0的應用與計量分析
- Microsoft Dynamics CRM 2011 Scripting Cookbook
- 大數據搜索與挖掘及可視化管理方案 :Elastic Stack 5:Elasticsearch、Logstash、Kibana、X-Pack、Beats (第3版)
- 振蕩指標MACD:波段操作精解(升級版)
- Tableau:Creating Interactive Data Visualizations
- IBM SPSS Modeler Cookbook
- 企業并購審查中的相關市場界定:理論與案例