Steve Jobs, Apple founder – 1955-2011

I will always remember Steve Jobs for his ability to design a vision of the future that differs from the present – he never settled.

Steve Jobs 1955-2011

Steve Jobs 1955-2011

 

 

A story about Steve Jobs

Steve Jobs has always been known for his attention to detail – insisting on beautiful typeface and fonts from Apple’s beginning.
Apple CEO Steve Jobs at the  Apple Worldwide Developers Conference in San Francisco in June.

Paul Sakuma/AP

Vic Gundotra — the man behind Google +, posted a story about an interaction with Steve Jobs.

He writes that on a Sunday morning in 2008, he received a call during a religious service. He didn’t answer, but Jobs left a message saying he had something “urgent to discuss.” Gundotra returned his call almost immediately:

“Hey Steve — this is Vic,” I said. “I’m sorry I didn’t answer your call earlier. I was in religious services, and the caller ID said unknown, so I didn’t pick up.”

Steve laughed. He said, “Vic, unless the Caller ID said ‘GOD’, you should never pick up during services”.

I laughed nervously. After all, while it was customary for Steve to call during the week upset about something, it was unusual for him to call me on Sunday and ask me to call his home. I wondered what was so important?

“So Vic, we have an urgent issue, one that I need addressed right away. I’ve already assigned someone from my team to help you, and I hope you can fix this tomorrow,” said Steve.

“I’ve been looking at the Google logo on the iPhone and I’m not happy with the icon. The second O in Google doesn’t have the right yellow gradient. It’s just wrong and I’m going to have Greg fix it tomorrow. Is that okay with you?”

The CEO of Apple — the tech visionary who revolutionized personal computers, the way we listen to music and the way we think of mobile devices — was worried about the yellow in the second “O” in Google. Needless to say the problem was fixed, and Gundotra says it taught him a lesson on leadership and “passion and attention to detail.”

“It was a lesson I’ll never forget,” wrote Gundotra. “CEOs should care about details. Even shades of yellow. On a Sunday.”

read more

While no longer managing the day-to-day actives of Apple, Steve Jobs remains a great leader – one that all leaders, engineers and architects should learn to appreciate for his discipline, willingness to take risks, execution and attention to detail.

The Start-Up of You

Published: July 12, 2011
Facebook is now valued near $100 billion, Twitter at $8 billion, Groupon at $30 billion, Zynga at $20 billion and LinkedIn at $8 billion. These are the fastest-growing Internet/social networking companies in the world, and here’s what’s scary: You could easily fit all their employees together into the 20,000 seats in Madison Square Garden

http://www.nytimes.com/2011/07/13/opinion/13friedman.html

Web 3.0: The ‘Social Wave’ and How It Disrupts the Internet – Knowledge@Wharton

Web 3.0: The ‘Social Wave’ and How It Disrupts the Internet – Knowledge@Wharton.

The web has grown to the point where “there’s too much information,” according to Katz. “Finding ways to filter out information and find what’s relevant to you is getting harder and harder. The model of Google doesn’t work at scale — especially when it comes to things where taste matters.”

Katz predicted that the future of the Internet “is one where every page is going to be personalized. If you plan a trip to Paris, you shouldn’t see [search results listing] 900 hotels. You should see six hotels based on where you stayed before; the places you checked in at on Facebook and Foursquare, and the places where your friends have stayed. It’s not something that’s just relevant to travel; it’s something that makes sense for almost every part of the Internet.”

Building a Shared Mental Model to Rekindle Collaboration

Building a Shared Mental Model to Rekindle Collaboration.

The ability to develop an accurate mental model often separates successful companies from organizations that do not survive.

So what exactly is a company’s mental model? Simply put, a robust mental model eliminates internal confusion. The mental model is a framework that simplifies a potentially complicated strategy, allowing everyone in the organization to internalize the strategy and be guided by it.

Great companies build and share their mental model internally in ways that enable managers and employees to independently make critical decisions day in and day out that are aligned with the strategy. Without a strong mental model strategy can become open to interpretation, decision making can become bogged down, or both can occur at once.

The Only Way to Get Important Things Done

The Only Way to Get Important Things Done.

The answer, surprisingly, is not that they have more will or discipline than you do. The counterintuitive secret to getting things done is to make them more automatic, so they require less energy.

It turns out we each have one reservoir of will and discipline, and it gets progressively depleted by any act of conscious self-regulation. In other words, if you spend energy trying to resist a fragrant chocolate chip cookie, you’ll have less energy left over to solve a difficult problem. Will and discipline decline inexorably as the day wears on.

“Acts of choice,” the brilliant researcher Roy Baumeister and his colleagues have concluded, “draw on the same limited resource used for self-control.” That’s especially so in a world filled more than ever with potential temptations, distractions and sources of immediate gratification.

 

New Ways to Collaborate for Process Improvement

New Ways to Collaborate for Process Improvement.

This post is part of the HBR Insight Center Making Collaboration Work.

To make big improvements in productivity and customer service, people in an organization must collaborate across corporate hierarchies, functions, companies, and geographies. Emerging social networking technologies offer new ways to overcome these boundaries. Leading companies such as IBM, Ford, and Avery Dennison are making major improvements in key processes by creating online communities to share deep knowledge.

Solving Your Organization’s Open-Faced Sandwich

Solving Your Organization’s Open-Faced Sandwich

Here’s the problem: Our jobs are complex and interdependent, but our goals, objectives, and, most importantly, mindsets, are often siloed.

We each have a job to do — sell a service, design a product, address a customer issue — and the underlying mindset is: if I do my job well, and you do your job well, we’ll achieve our organization’s goals.

But it rarely works that way. People in one silo often have information needed by — but never given to — people in another silo, in which case if there’s a problem anywhere in the organization, everyone fails.

This is not a question of blame. It’s a practical reality of collaboration. And every organization of two or more is a collaborative effort.

How do we escape the silo mentality?

It helps if leadership is explicit about the cross-silo outcomes that are most important in the organization. It helps if each person is committed to a whole that is larger than their part and if leaders communicate, prioritize, and reward for that outcome.

It also helps if the organization’s structures and processes support collaboration. If people meet regularly to share what they are learning and are taught the skills to give and receive feedback. It helps if people are taught to communicate clearly, gently, and inoffensively with each other, avoiding blame and embarrassment, for the sake of cross-silo outcomes.

All that helps. But even with all that support, direction, and skill, it still takes one more critical ingredient. Perhaps the most critical.

Courage.

 

2010 – A Failure in Strategic Technology Leadership

Watching the swings in technology predictions over the past few years, Technology Leaders continue to pursue short-term and reactionary technology implementations rather than pursuing strategic planning that focuses on the technologies and applications that will position a business for growth, performance, and enhanced value.

Top 10 of 2009 Top 10 of 2010 Top 10 of 2011
1. Software as a Service (SaaS) 1. Green Computing and Energy Efficiency 1. Security
2. Virtualization 2. Public and Private Cloud Computing 2. Business Intelligence
3. Enterprise Mobility 3. Virtual Desktop Infrastructure (VDI) 3. Virtual Desktop Infrastructure (VDI)
4. Energy-Efficient Data Centers 4. Mobility, Telecommuting and Virtual Meetings 4. Virtualization
5. Security, Risk and Compliance 5. Centralization, Standards and Governance 5. Mobile IT
6. Social Networking 6. Knowledge Sharing, Business Intelligence and Social Networking 6. Software as a Service (SaaS)
7. Web 2.0 7. Security, E-Discovery and Business Continuity 7. ERP, CRM and BPI
8. Document Management and E-Discovery 8. Advances in Application Infrastructure 8. Hardware Refresh
9. Project Management and Project Portfolio Management 9. Investments in Hardware Infrastructure 9. Monitoring and Management of Social Information
10. Web and Video Collaboration 10. Collaboration, Workflow and Productivity 10. Unified Communications

Source:  Baseline Magazine, Annual IT Survey (http://www.baselinemag.com)

Baseline Magazine’s Annual IT Survey doesn’t report the percentage of new vs. repeat respondents, however these swings in technology trends are well documented throughout many sources.

The financial crisis of the past two years challenged Technology Leaders to deliver well architected, properly financed and sustainable solutions; unfortunately, the swings in technology trends suggest that the leaders were focused on technology adoption rather than positioning their business for growth, performance, and enhanced value.  For instance, the swing in Security (#5 in 2009, #7 in 2010, #1 in 2011) suggests that Technology Leaders choose to curtail security planning and architecture while pursuing new technologies, and now must spend more, and work harder to implement security behind the implementation of technology.

The failure of the Technology Leadership to keep the organization focused on achieving well architected, properly financed and sustainable solutions during this financial crisis is similar to the dot com bust that followed un-checked spending on technology ahead of business growth, performance and enhanced value.

Financial challenges are a part of our economic cycle, when Technology Leaders are not adopting strategically aligned corrective courses of action; they tend to follow technology trends, such as:

  • Adopting cloud computing to reduce costs rather than to improve the business’ ability to grow (#2 in 2010, not on the list for 2011)
  • Decentralizing or centralizing, without changing the players (#5 in 2010, not on the list for 2011)

The Technology Leadership role continues to be dominated by leaders who fail to recognize, understand and respond to business and economic trends.  Ten years ago, the Chief Information Officer was thought to be a part of the C-Leadership suite, but most have failed to achieve this goal, as they never moved beyond the stereotypical management style that has plagued Technology for more than 20 years.

Today’s Technology Leaders must – understand Business and Enterprise Strategy, partner with Marketing, Finance and Operations, and focus on Risk Management and Operational Excellence (5 Principles).

Contract Penalties do not solve Contracting Issues

For more than a week, three Virginia state agencies — the board of elections, the departments of motor vehicles and the department of taxation have been experiencing “…major computer issues that are hampering their daily operations…” as reported by Marcella Williamson, a spokeswoman for the Virginia Information Technologies Agency (VITA), which oversees the state’s computer network.

Unfortunately, this isn’t Virginia’s first major outage with their outsourcing partner – Northrop Grumman (NG).  In Oct 2009, a legislative audit highlighted deficiencies in planning, communications, and risk management, which lead to interruptions in government services and project delays and eventually contract amendments.

Read/Download the Report at http://jlarc.state.va.us/meetings/October09/VITA.pdf

Lessons learned during the audit include:

  • Vendor’s experience & understanding are key elements for success – success is enhanced when all parties fully understand the goals of the project & have demonstrated the ability to meet them
  • Partnership still requires experienced staff in the public entity
  • Partnership may not produce savings
  • Full & careful evaluation of proposals is critical

Outcomes of the audit included personnel and organizational changes along with contract amendments (see sidebar) – yet problems still exist.

SIDEBAR - Report of the Joint Legislative Audit and Review Commission To the Governor and The General Assembly of Virginia (SENATE DOCUMENT NO. 13 2010)

The most notable change was the elimination of the supervisory body charged with overseeing VITA, the Information Technology Investment Board, which was replaced with the Information Technology Advisory Council. In addition, the State’s Chief Information Officer (who serves as administrative head of VITA) will now be appointed by the Governor and report to the Secretary of Technology, instead of being appointed by and reporting to the Information Technology Investment Board. These actions are consistent with the recommendations made by JLARC staff in presentations to the Commission, the House Appropriations Committee, and the Senate Finance Committee in October 2009.

In addition, on March 30, 2010 VITA and NG signed contract amendments and agreed to implement operational improvements, which have the potential to address several findings in this report

Contracting Services

Contracting for service replacement is far different than purchasing technology through General Services.  Contracting for services requires:

  • An in-depth understanding of key processes and their success criteria (i.e., issuing new drivers licenses with a 0% defect rate in less than 60 min)
  • An understanding of the Enterprise Architecture behind key processes
  • A Portfolio & Project Management methodology that clarifies roles and responsibilities and prioritizes objectives while reducing risk
  • A Risk Management methodology

Unfortunately, Virginia’s focus on organizational changes and contract amendments were not enough to protect critical services from a devastating outage.  They are not alone in their challenges in contracting for IT Services.  Recently Texas announced their intent to rebid IBM’s data center contract and Marin Count recently sued Deloitte over the failed installation of their SAP ERP system.

Texas to rebid IBM’s data center contract - http://www.statesman.com/news/texas-politics/texas-to-rebid-ibms-data-center-contract-865050.html

Understanding Marin County’s $30 million ERP failure - http://www.zdnet.com/blog/projectfailures/understanding-marin-countys-30-million-erp-failure/10678?tag=nl.e539

Conclusion

These organizations made similar mistakes by contracting for services based on a favorable price, rather than strategic decision-making and organizational policies.  The cost savings only approach often leads to cost over-runs, missed expectations and litigation; whereas a collaborative approach focused on solving problems and improving operations, can elevate services and optimize business processes.

Follow

Get every new post delivered to your Inbox.