These are the slides from Roee Kriger's workshop at Product of Things Conference in Tel Aviv on July 2018:
Who this workshop is for: This 90-minute workshop is for those who want to learn how to build their product's roadmap, positioning, partnerships, and channels according to the IoT market characteristics and predictions for next years
After this workshop you will be able to:
- Understand the impact of sales, partnerships and other engagements with your customers, on your product roadmap
- Compare and contrast different product roadmap approaches to creative, technical work (such as your product architecture)
- Ensure your creative, technical process is aligned with the company's business goals
What is covered:
- How different business strategies impact product architecture and technical decisions
- What is the impact of different technical roadmap decisions on product's ability to integrate with other players' products
- How to identify opportunities for creating product ecosystems and follow these opportunities with a valuable product offering that positioning the company for years ahead
In this workshop, Roee will share from his experience leading product management in very technical environments and will guide the audience how to best utilize tech for creating product roadmaps that are relevant for the future of our domain.
Make sure your product doesn’t only follow but also lead tomorrow’s tech with Roee Kriger
1. Workshop by Moriya Kassis
Make sure your product
doesn’t only follow
but also lead tomorrow’s tech
Workshop by Roee Kriger,
Product Management Consultant
2. About me
Roee Kriger
15 years experience in tech RnD & Product
Prime minister office, Trusteer, Redbend.
Founder and CEO of Bazaaro.
You can find me at Roee Kriger 2
3. Agenda
▰ Building a product
▰ GTM for product people
▻ Knowing your customers
▻ Integration and partnerships
▻ Product architecture
▰ Exercise
3
11. “Everything that ensures you build
the right product so that when
you go to market,
it will succeed
& you will keep your job
1111
12. Lets focus
▰ Identify opportunities to increase value for your
customers
▻ Know your customers and their needs
▻ Understand their problems and pains
▻ Understand market trends
▰ Integration and partnerships
▰ Product architecture & release intervals /reaction time12
13.
14. Knowing your customers
▰ Are your customers compete in a fast changing
market environment?
▻ Does your offering reduce the risk for your customers
▻ Can you help your customer prepare for the future
14
15. Knowing your customers
▰ Changing market is a huge opportunity for startups
▻ New needs and pains
▻ Willingness to spend more in order to adapt for the
change
▻ Corporates react slowly to changes
15
17. Knowing your customers
▰ How fragmented is your customers ecosystem
▻ Does each customer use different OS, storage, etc.
(embedded products)
▻ On premise vs cloud
17
18. Knowing your customers
▰ How can I make their decision to choose my
product easier?
▻ Integration and deployment efforts
▻ Partnership
▻ API, Others
18
19.
20. Startups perspective
❖ Bring access to larger deals
❖ Lowering customer acquisition costs
❖ Reputation
❖ Accelerate market penetration
❖ Increase functionality to your core product
Integration and Partnerships
20
Why do startups and corporates need each other?
21. Integration and Partnerships
Corporates perspective
❖ Finding new markets
❖ New form of revenue streams
❖ Add complementary functionality quicker than
internal efforts
21
Why do startups and corporates need each other?
22. Why do collaborations fail
▰ Misunderstandings and misalignment of interests
▻ Make sure you are not competing
▻ Make sure your offering truly benefits your partner and
show him how!
22
23. Why do collaborations fail
▰ Lack of commitment by one of the parties
(find a champion)
▰ Loss of information along the way
▰ Problems to navigate large organization to reach
a consensus and unlock budgets (champion)
23
25. Product architecture
▰ Ability to react according to
market/customer needs should be considered
as part of the GTM Strategy
25
26. Product architecture
▰ Customer/Market fragmentation –
▻ Each customer uses different architecture and has
different integrations
▻ May lead to overhead efforts to meet customer needs
▻ Becomes project oriented vs product
26
29. Background
▰ Industry - Automotive industry
▰ Characteristics –
▻ The industry goes through massive change
▻ Customers have hard time to adapt and understand the needs to cope with the
change
▻ Highly fragmented in terms of demands and platforms
▻ Each customer uses different architecture:
▻ OS
▻ Hardware
▻ Storage
▻ Each customer has different approach of using your product within their
production environment
▻ Demands can change rapidly over time, hence it is hard to plan more than 3
months a head on some use cases and features 29
30. The Product
▻ Your product has two main components:
▻ In vehicle client needed to be install on each computer it
manages
(approx. 180 computers/each)
▻ Web portal for management
▻ In vehicle clients have got to be integrated on each
managed computer
30
31. The Product
▰ Other information
▻ Customers understand the value of your product
▻ Your pricing strategy is based on how many
managed device your customer manages
▻ Integration is a big pain
▻ Your customer is very stubborn and has big
problem reducing features he wants 31
32. Assignment
▰ You are the PM of the company
▰ Write a GTM strategy plan in order to scale your
product
32
33. Assignment
▰ Within the GTM plan include the following:
▻ Write a roadmap for the product
What kind of product, architecture and others would give
you advantage and meet market requirements?
▻ How you scale your product? (what actions inside and
outside of the company would you try to do )
33