Skip to main content

Reflecting on Steve Jobs


Today we lost a luminary. Steve Jobs died this afternoon, leaving a hole in the beating heart of Silicon Valley, and a virtually unparalleled legacy in high-tech history.

Steve will be remembered for many things. What I will remember him for is perhaps something...different. He didn't design all these lauded products we covet. He didn't invent all the great technology Apple is known for. What he did do, however, is transform Apple into a product-based company and instill his philosophy of quality and simplicity in the teams that he assembled.

Apple is a great company because they have great internal processes for product development, they exhibit outstanding execution with regard to production and delivery, and they have one of the best marketing teams in the world. Steve Jobs didn't architect or design all of these components, but he recognized the business value of them, hired the right people to get the job done, and invested the required time and effort to get things done right.

Steve Jobs exercised professional discipline. Other business leaders would do well to note that, and not chalk up Apple's success to fortunate sparks of creative genius. Doing so only shows that they don't understand Steve Jobs, his role, or the business principles that make Apple great.

Thank you Steve.

Comments

Popular posts from this blog

Building Better Products Using Quantitative & Qualitative Data

Disclosure: This was an internal post I wrote and shared with my colleagues back in 2015. While cleaning out my Confluence space, I came across it and thought that I'd share it with everyone. There is a much more recent and polished post by my good friend Glenn Block on Mind the Product that you can read here:  https://www.mindtheproduct.com/2018/01/need-quantitative-qualitative-data/ What Data Is/Not Data cannot  compensate for bad design or replace good design, but it can inform designers. Data cannot compensate for listening to actual users, but it can inform the kind of user research we conduct. Data cannot tell us what to build, but it can inform what we should investigate. Example If you can visualize a funnel report where visitors are leaving a buying process during various stages of the journey, quantitative data can give you information about where you may have a problem. In the above example, the quantitative data ( QT ) informs you that 36 pe...

Improving Win Rates

Still here at the Gartner Local Briefing. In a session with Richard Fouts about customer win rates. Sharing Win/Loss Data Sales teams tend to advertise their wins, yet contain their losses. Why is this so? Q:  How many global IT companies conduct win/loss on an enterprise scale? Less than 5%? About 10%? About 20%? A: Less than 5% Why? CEOs and Sales people say "I know why we win/lose".  Some politics are touchy; people don't want you to expose what they did well/not (especially in competitive environments).  "I clicked the won/loss checkbox in Salesforce.com" One company evaluated their win/loss data. They looked at 140 wins, and 55 losses. Looking at this data, they noticed a correlation between the wins and the fact that they beat their competition to market with compelling announcements in over a third of the scenarios. An IT services firm attempted to sell a more sophisticated solution. Upon evaluation of the win/loss data, they fo...

Product Parenthood

It has been a long time since I've been able to sit down and write a lucid blog post.  This one will not be one of them. I've come to realize that my full-time job as a Product Manager, my other full-time job as a husband, and my newest (and most demanding) full-time job as a parent (to a delightful son) consume roughly 100% of my time; leaving precious few moments in the day in which to gather and synthesize my thoughts.  Thus, I've been using Twitter more often and blogging less. " Blogging less?  What?  You only have 3 prior entries! " I used to blog quite a bit under a different moniker.  However, as a parent, I have come to the realization that composing longer, thoughtful essays are a luxury that I generally cannot afford. With that, I've added my Twitter feed to the left, and will make an effort to write "larger-than-micro" blogs here on at least a weekly basis, if not more frequently. And now it's back to full-time job #1, follo...