My mother, Gloria Murphy, had a heart attack Thursday night and died about 8 feet from where my father had a heart attack a decade ago.
It’s not uncommon for a startup’s offering to evolve from service to system integration to product. Here is an explanation for the reasons and benefits.
The difference between scouting a new market and scouting a promising market is that the former may not exist–or come into existence–while the latter clearly exists because it’s already occupied.
Mark Hanzo, CTO of Hanzo Archives, was interviewed by SimpleWeb as part of a series on validating startup ideas. I found his remarks on very practical and insightful and have added some observations of my own.
Chip Conley shares how he was able to look at AirBNB’s operation with newcomer’s eye when he chose to reconceive bewilderment as curiosity.
A focus on inefficiencies is a good method to find a underserved market where you can bootstrap you way to viability. Here is a list of several others.
How do you answer someone who asks “Should I be an entrepreneur?”
Brent Beshore recently shared an email he had sent to a college seniors that outlined five habits to cultivate for success. In a nutshell they are industry, humility, kindness, learning continually, and taking notes.
Our July 2017 Newsletter focused on key insights for entrepreneurs offered by Robert Pirsig in “Zen and the Art of Motorcycle Maintenance. If you have not had a chance to read it I would encourage you to put it on your summer reading list.
This post applies the moral of James Thurber‘s “The Fairly Intelligent Fly”–that there is “no safety in numbers, or in anything else”–to entrepreneurship.
Max Gunther’s “The Zurich Axioms” is aimed at investors but also offers valuable insights and rules of thumb for entrepreneurs.
A collection of quotes and stories related to fathers and fatherhood for Father’s Day 2017.
Silicon Valley startup culture embraces hard work, but some entrepreneurs fall into the trap of working long hours as an end in itself. With no limits on the workday, Parkinson’s Law warns that work will simply take over your life.
Ogden Lilly passed away suddenly on Sun-May-14-2017. He worked as an accountant for 47 years at a firm that ultimately added his name to the masthead. I have relied on his advice and counsel for more than two decades and feel his loss keenly on a personal and a professional level.
Jeff Allison offers a June-1-2017 briefing on how to blend new capability development and new product development. Innovation requires experimentation that allows for the possibility of failure but the whole point of creating a program commitment process is to avoid failure.
Jeff Allison: How To Blend New Capability and New Product Development
Jeff Allison has worked in high tech industry for over 30 years. During that time he acquired a vast amount experience in product development, change management, new technology adoption, sales and marketing.
Jeff worked at Cisco from 1992 to 2012 at a time of dynamic growth in the company and the networking industry. He joined Cisco as a manager responsible for EDA tools. Then spent the next 20 years at Cisco in various Engineering leadership positions and provided Engineering Design services for all the high-end routing platforms. He was vice president of engineering for the last decade and drove a significant number of cross functional internal and customer facing initiatives. These included a rationalization of best practices across engineering teams from various Cisco acquisitions and quality and customer satisfaction initiatives as Cisco established a leadership position in global service provider markets.
Jeff’s first position was working for Racal-Redac in the Engineering Design Automation (EDA) industry. At Redac he set up an Engineering sales support organization in North America for design entry and simulation tools. During that time, he experienced the rapid growth and consolidation in the EDA industry. Jeff graduated from the University of Wales in ’84 with degree in Engineering.
Experiments vs. Committed Programs: How to Drive Innovation and Meet Commitments
Innovation requires experimentation that allows for the possibility of failure but the whole point of creating a program commitment process is to avoid failure.
How do you as an engineering manager or executive
- leverage a product portfolio to run experiments to minimize risk for future programs?
- sell and deploy new capabilities throughout engineering?
What questions can you as an engineering manager or executive ask to understand the scope of the risk?
Jeff Allison will present lessons learned from working with early adopters in a fast cycle or rapid prototyping approach that anticipates the need for a scalable reliable development process and lays the groundwork for it.
- When: Thu-Jun-1-2017 6pm to 9pm
- Where: AMD Commons Building / AMD Campus, Sunnyvale CA (Intersection of Stewart Drive & Santa Trinita Ave.)
- Cost: $15 (less for IEEE Members)
- Register: https://tems1706.eventbrite.com/
- More info Silicon Valley TEMS Site: Experiments vs. Committed Programs: How to Drive Innovation and Meet Commitments
Related Blog Posts
It’s time to update your goals based on results to date. 2017 is now well underway and some goals you set for Q1 may need to be revisited and perhaps dropped or rescheduled for this quarter. Here is what happened in Q1 and what we have planned for Q2.
It always seems simpler to be able to start with a blank slate, and even better to be given just one project so that you can focus, but the reality is that innovation inside an organization requires balancing priorities.