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...

Social CRM: Putting Customers First

Last night I attended Social CRM: Putting Customers First , hosted by the San Francisco chapter of the Social Media Club .  It was a great event, and I'll briefly recap some of the discussion and my observations. The panelists were first asked why Social CRM (SCRM) was relevant.  Their answers were as follows: Vendors need to know who their customers are out there on the social web. Vendors need to be able to identify customer pain points from conversations on the social web.  Vendors need to know what to do with these conversations on the social web.  These discussions are the center of business today; their importance cannot be understated. The social web grows too fast for vendor solutions to keep up.  Therefore, vendor solutions must embrace the social web, and learn how to crowdsource.  There is no way that you can scale communities and community managers that fast. Customers don't care about your organization structure, they just want answers a...

A Change In Perspective on Mobile Content Creation

Over the past few years, I've championed the idea that smartphones are by-and-large consumption devices; not creation devices. Someone asked me recently: Do you send email from your smartphone? Isn't that creation? I suppose that it is. But I typically send bite-sized emails, SMS, and Tweets; not long-form content. But when you also share photos and videos and links and likes and plus-1s, smartphones are clearly creation devices. This reflection challenged my previous perspective from thinking of content exclusively as robust documents to include rapid-fire info-blurbs. Where now is the dividing line between smartphone content creation expectations and those of laptops and desktops? This question prompted me to try the previously unthinkable; to write a blog post on my mobile phone. This is clearly long-form, but still distinct from the rich authoring experience I enjoy on my full-fledged computers. Perhaps then the discussion ought not be about content creation, but...