This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
A Product Framework from Concept to Delivery: Part 1 Why “FE²AR” As a technology executive, I have seen my share of successful and not-as-successful products. The best products fail nowadays due to a lack of consideration of Ecosystems, an example that I will walk through in Part 2 of this article. How frustrating would that be?
Much of this is largely due to the fact that internal politics exist in almost all companies. Yet, despite the fact that this disastrous situation was caused by a broad spectrum of factors, some of the most apparent problems were attributed to communication, leadership, and relationship management.
In the early 90s, the technological landscape was a very different place. And the idea of a home filled with technology that could wirelessly communicate not only with you but other pieces of technology was, for most, as out of reach as something on the Jetsons. Internet access wasn’t available in the average household.
Research shows that most 20th-century products followed this adoption behavior: Source: The Atlantic “ The 100-Year March of Technology in 1 Graph “ Let’s now take a look at the different stages of the Product Adoption Curve. They’re technology enthusiasts and are usually quite technical. There’s just one catch.
The requirements of these parts should also coincide with a review of any compliance or regulatory requirements that your product will need to meet for its market, whether this is driven by certifications, safety standards or your competition. Water repellency, for example, requires much development work and has high manufacturing costs.
In this webinar, Steven Haines, founder and CEO of Sequent Learning Networks and author of The Product Manager’s Survival Guide , draws on extensive product leadership experience to show how to develop customer empathy, develop great customer insights, and transform them into better value propositions. That’s my voice, but nobody’s listening.
In this webinar, Steven Haines, founder and CEO of Sequent Learning Networks and author of The Product Manager’s Survival Guide , draws on extensive product leadership experience to show how to develop customer empathy, develop great customer insights, and transform them into better value propositions. It’s not damning anyone.
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content