Startup Lab workshop: How Google sets goals: OKRs

• OKRs ! = PRM directly
• Q based
• Good data points.
• OKRs are public; everyone in the company should be able to see what everyone else is working on (and how they did in the past)
• Objectives are ambitious, and should feel somewhat uncomfortable
• Key Results are measurable; they should be easy to grade with a number (at Google we use a 0 – 1.0 scale to grade each key result at the end of a quarter)
• The “sweet spot” for an OKR grade is .6 – .7; if someone consistently gets 1.0, their OKRs aren’t ambitious enough. Low grades shouldn’t be punished; see them as data to help refine the next quarter’s OKRs.

Posted in Technical excellence, Thinking tools | Leave a comment

Masaaki Imai – Definition of KAIZEN

Posted in Uncategorized | Leave a comment

The art of innovation: Guy Kawasaki at TEDxBerkeley

Posted in Design Thinking, Thinking tools | Leave a comment

Dr. Clayton Christensen delivers 2012 Pullias lecture at USC

Posted in Thinking tools | Leave a comment

Dilbert: Disaster Recovery Plan

Posted in Thinking tools | Leave a comment

9 Myths About Agile

9 Myths About Agile

Setting the record straight on the most common misconceptions about an increasingly popular—and controversial—approach to software development.

Agile has proven a polarizing force since a group of veteran software developers first proposed it in 2001 as a reaction to traditional “Waterfall” development, which they perceived as slow and dysfunctional. Unlike the Waterfall method, Agile encourages rapid and flexible responses to changing business needs and user requirements.

Some in both the IT and business communities are justifiably enthusiastic about achieving desired results more quickly, and welcome the move away from traditional software development approaches. Others are vehemently opposed to Agile for a variety of reasons, including that it requires making disruptive changes to established processes and may place additional burdens on users.¹ The reality of Agile probably lies somewhere in the middle.

Certain myths permeate the often-heated discussions taking place among IT and business leaders considering Agile.

more is available here

Posted in Agile, Kanban, Scrum | 2 Comments

Functional fixedness

“A mental block against using
an object in a new way that is
required to solve a problem.”

More here

Posted in Thinking tools | Leave a comment

Dave Snowden | How not to manage complexity

Posted in Agile, Creativity, Kanban, Lean, Scrum, Thinking tools | Leave a comment

Don Reinertsen @ The Lean Startup Conference 2013

Posted in Lean | 1 Comment

Red Queen Hypothesis

Red Queen Hypothesis brings interesting view point to modern industry / enterprise as well.

Posted in Lean, Thinking tools | Leave a comment