These graphics illustrate how I see my past experience in Product Management as it relates to the role itself.
It's a "hot seat" that interfaces with individuals in every area of the
company and requires ability to take in information from many different sources to
produce a competitive, innovative, and appropriate product / service per market / company requirements.
Product Perspective
These diagrams / pictures illustrate my view of Product Management from the product perspective. The left diagram
illustrates how the intersection of the technical capabilities of an organization (engineering) intersects with known
requirements and expectations of users and/or anticipated expectations of users.
The right is the basis for what the product / service will look like.
Various groups / stakeholders want many things, but the most important ones must be identified as a "need" and prioritized.
Following the above is product / service design philosophy. And the excerpt from the article below sums up how I see this:
May 2014 - Ousted Samsung Design Boss: This Is Why We Make Our Phones Out Of Plastic (Yahoo Finance)
"The video implied that instead of going to consumers first, Apple comes up with a zillion different options on its own and picks the best one. It's the opposite strategy Samsung employs. On one end of the spectrum you have Samsung, which thinks it should go with what users want;
on the other end you have Apple, which thinks it can decide on its own what's best for users."
My "philosophy" -- well, somewhere in between. it depends on the organization,
what kind of research capabilities are available, what information is available in relevant trade
/ consumer magazines, individuals in a development group, what kind of product / service is
being designed, is it an upgrade or new version, and how much time is available to develop the product / service.
