Posts about Creativity

Children are Amazingly Creative At Solving Problems

This story at NPR reminded my of Russell Ackoff talking about the creativity kids show in solving problems* – and how school often stifles that creativity.

Preschoolers Outsmart College Students In Figuring Out Gadgets

Children try a variety of novel ideas and unusual strategies to get the gadget to go. For example, Gopnik says, “If the child sees that a square block and a round block independently turn the music on, then they’ll take a square and take a circle and put them both on the machine together to make it go, even though they never actually saw the experimenters do that.”

This is flexible, fluid thinking — children exploring an unlikely hypothesis. Exploratory learning comes naturally to young children, says Gopnik. Adults, on the other hand, jump on the first, most obvious solution and doggedly stick to it, even if it’s not working. That’s inflexible, narrow thinking. “We think the moral of the study is that maybe children are better at solving problems when the solution is an unexpected one,” says Gopnik.

And that flexibility may disappear earlier than we think. Gopnik’s lab has also compared toddlers and kindergartners in doing these tests of abstract thinking, and found that the diaper set are actually better at focusing on the relationship between the objects, rather than on the things.

To those, like me, that use Deming’s ideas to help understand and improve management it is apparent these findings relate directly to two areas of Deming’s management system: psychology and theory of knowledge (how we know what we know).

Understanding how our psychology limits are effectiveness can be used to counter those tendencies.

And as Daniel Boorstin said:

“The greatest obstacle to discovery is not ignorance – it is the illusion of knowledge.”

Understanding the limits of our knowledge and our tendency to become rigid in our thinking can help us avoid blinding ourselves to options. Our brains overrule options without us consciously even knowing that is happening; it takes effort to overcome this tendency.

Continue reading

Deming and Software Development

I am sometimes asked about how use Deming’s ideas on management in a software development context. My belief is Deming’s ideas work extremely well in a software development context. The main issue is often unlearning some assumptions that people might have about what the Deming management system is.

It really is surprising to me how many “knowledge workers” respect Deming ideas but then say his attempts to treat factory workers as thoughtful people who should be respected and involved in improving their processes doesn’t make sense for them because they are “knowledge workers.”

There are many good things being done to improving the software development process. I think many of them are very Deming-like in their approaches (but to me miss out on aspects of the Deming management system that would be helpful). I think Dr. Deming’s approach to software development would focuses on the system of profound knowledge (the 4 inter-related areas below):

  • Understanding variation – software development has quite a bit of variation, some probably innate [unique work] and some due to not having good procedures, batching work, not fixing problems right when they are seen, quick fixes that leave the system venerable in the long term (when you make one simple change to the code it has an unanticipated consequence due to poor practices that could have been eliminated), etc.. Many good coding practices are effective strategies to deal with this issue. And building an understanding of variation for managers (and business process owners/product owners) is very helpful to the software development process. The ideas in agile and kanban of focusing on smaller delivery units of work (one piece flow, just in time, cycle time…), customer value, maintainable code, sustainable work conditions, etc. are directly found in a Deming management system.
  • Appreciation for the system of software development. Don’t just complain about bugs. Examine the process of development and then put in place mistake proofing efforts (don’t duplicate code, use integrated regression tests, don’t put artificial constraints on that result in system distortions – unrealistic targets…). Use things like kanban, limited work in progress, delivering value to customers quickly, think of success in terms of getting working software to customers (not meeting internal delivery goals), etc. that take into account our experience with systemic software development problems over the decades.
  • Theory of knowledge – how do we know what we know? Are estimates reliable? Lets look at what users do, not just what they say (A/B testing…). Software developers often appreciate the value of usability testing, even though they rarely work for organizations willing to invest in usability testing. In my experience when software developers object to usability testing it is normally really an objection to overwork, and the usability testing is just going to give them more work or criticize things they were not allowed to spend the time they needed to do great work. That won’t always be the reason but it is the main one in my experience (I suppose their is also fear and just the psychology of not wanting to hear anything negative about what has been created – even if the usability testing shows tons of great results people will often focus on the negative).
  • psychology and respect for people – This pretty much seems like it is the same for software development as everywhere else.

Continue reading

Taking Risks Based on Evidence

My opinion has long been that football teams are too scared to take an action that is smart but opens the coach to criticism. So instead of attempting to make it on 4th down (if you don’t understand American football, just skip this post) they punt because that is the decision that is accepted as reasonable.

So instead of doing what is wise they do what avoids criticism. Fear drives them to take the less advantageous action. Now I have never looked hard at the numbers, but my impression is that it is well worth the risk to go for it on 4th down often. In a quick search I don’t see a paper by a Harvard professor (this article refers to it also – Fourth down: To punt or to go?) on going for it on 4th down but I found on by a University of California, Berkeley economist (David Romer wrote called “Do Firms Maximize? Evidence from Professional Football.”).

On the 1,604 fourth downs in the sample for which the analysis implies that teams are on average better off kicking, they went for it only nine times. But on the 1,068 fourth downs for which the analysis implies that teams are on average better off going for it, they kicked 959 times.

My guess is that the advantages to going for it on 4th down are greater for high school than college which is greater than the advantage for the pros (but I may be wrong). My guess is this difference is greater the more yardage is needed. Basically my feeling is the variation in high school is very high in high school and decreases with greater skill, experience and preparation. Also the kicking ability (punting and field goals) impacts the choices of going for it on 4th down and that dramatically increases in college. So if I am correct, I think pro coaches should be more aggressive on 4th down, but likely less aggressive than high school coaches should be.

But in any event the data should be explored and strategies should be tested.

Continue reading

What is the Explanation Going to be if This Attempt Fails?

Occasionally during my career I have been surprised by new insights. One of the things I found remarkable was how quickly I thought up a new explanation for what could have caused a problem when the previously expressed explanation was proven wrong. After awhile I stopped finding it remarkable and found it remarkable how long it took me to figure out that this happened.

I discovered this as I programmed software applications. You constantly have code fail to run as you expect and so get plenty of instances to learn the behavior I described above. While I probably added to my opportunities to learn by being a less than stellar coder I also learned that even stellar coders constantly have to iterate through the process of creating code and seeing if it works, figuring out why it didn’t and trying again.

The remarkable thing is how easily I could come up with an new explanation. Often nearly immediately upon what I expected to work failing to do so. And one of the wonderful things about software code is often you can then make the change in 10 minutes and a few minutes later see if it worked (I am guessing my brain kept puzzling over the ideas involved and was ready with a new idea when I was surprised by failure).

When I struggled a bit to find an initial explanation I found myself thinking, “this has to be it” often because of two self reinforcing factors.

First, I couldn’t think of anything else that would explain it. Sometimes you will think right away of 4 possible issues that could cause this problem. But, when I struggled to find any and then finally came up with an idea it feels like if there was another possibility I should have thought of it while struggling to figure out what I finally settled on.

Second, the idea often seems to explain exactly what happened, and it often feels like “of course it didn’t work, what was I thinking I need to do x.” This often turns out to be true, doing x solves the problem and you move on. But a remarkable percentage of the time, say even just 10%, it doesn’t. And then I would find myself almost immediately thinking, of course I need to do y. Even when 10 seconds ago I was convinced there was no other possibility.

Continue reading

Quality Processes in Unexpected Places

This month Paul Borawski asked ASQ’s Influential Voices to explore the use of quality tools in unexpected places.

The most surprising example of this practice that I recall is the Madison, Wisconsin police department surveying those they arrested to get customer feedback. It is obvious that such “customers” are going to be biased. Still the police department was able to get actionable information by seeking the voice of the customer.

photo of a red berry and leaves

Unrelated photo from Singapore Botanical Garden by John Hunter.

Certain of the police department’s aims are not going to match well with those they arrest (most obviously those arrested wish the police department didn’t arrest them). The police department sought the voice of the customer from all those they interacted with (which included those they arrested, but also included those reporting crimes, victims, relatives of those they arrested etc.).

The aim of the police department is not to arrest people. Doing so is necessary but doing so is most similar in the management context to catching an error to remove that bad result. It is better to improve processes so bad results are avoided. How the police interact with the public can improve the process to help steer people’s actions away from those that will require arrests.

The interaction police officers have with the public is a critical gemba for meeting the police department’s aim. Reducing crime and encouraging a peaceful society is aided by knowing the conditions of that gemba and knowing how attempts to improve are being felt at the gemba.

All customer feedback includes bias and personal preferences and potentially desires that are contrary to the aims for the organization (wanting services for free, for example). Understanding this and how important understanding customer/user feedback on the gemba is, it really shouldn’t be surprising that the police would want that data. But I think it may well be that process thinking, evidence based management and such ideas are still not widely practiced as so the Madison police department’s actions are still surprising to many.

Quality Leadership: The First Step Towards Quality Policing by David Couper and Sabine Lobitz

Our business is policing, our customers are the citizens within our jurisdictions, and our product is police service (everything from crime fighting and conflict management to safety and prevention programs.)

If we are to cure this we must start to pay attention to the new ideas and trends in the workplace mentioned earlier that are helping America’s businesses; a commitment to people, how people are treated — employees as well as citizens, the development of a people-oriented workplace, and leadership can and does make a difference.

If we change the way in which we lead the men and women in our police organizations, we can achieve quality in policing. However, wanting to change and changing are worlds apart. The road to change is littered by good intentions and short-term efforts.

This article, from 1987, illustrates the respect for people principle was alive and being practiced 25 years ago; most organizations need to do a great deal more work on applying practices that show respect for people.

Related: Quality Improvement and Government: Ten Hard Lessons From the Madison Experience by David C. Couper, Chief of Police, City of Madison, Wisconsin – SWAT Raids, Failure to Apply System Thinking in Law EnforcementMeasuring What Matters: Developing Measures of What the Police DoThe Public Sector and W. Edwards DemingDoing More with Less in the Public Sector – A Progress Report from Madison, Wisconsin

The Components of Genius

image of poster on what makes up genius

Wonderful poster, by Grant Snider, on the question: what is genius.

Related: Comic About ProgramersYou Have to Find What You Love To DoMarissa Mayer Webcast on Google InnovationInterruptions Can Severely Damage Performance

Using Incentives to Guide Social System Improvements

When confronted with the challenge of managing a social system (or market) I like to find ways to use a few simple rules that will guide the system to find improvements. I favor allowing participants in complex social system to determine how to adapt. So I support, for example, a carbon taxes where the market can decide where it is most effective to invest to reduce carbon use (both to reduce our depletion of the resource and to reduce pollution leading to climate change).

I like to try and keep prescription rules as limited as possible and instead set simple rules that will allow people to make choices. These rules will often allow for people to judge when they need to temper the extremes (in management examples) and in economic situations they often can have costs that escalate as the system is strained (so low pricing if the road is currently not heavily used and increasing the cost to users as congestion increases). The more prescriptive the rules the less ability people have to find creative solutions.

Traffic congestion is a perennial problem with high very costs to society. I very much like congestion pricing. You set a rule that puts increasing costs on those creating an overload on the system (which has costly negative externalities). Then allow people to figure out how to adapt.

The video also provides a very good example of why leadership is important. In Stockholm people were against congestion pricing (70% to 30%). This isn’t surprising they see a new tax that only is a cost. They don’t understand that the system performance is going to improve – the cost will provide a benefit. Leadership is required to push forward when the benefits are not obvious to everyone. Once people saw that congestion was greatly decreased 70% supported congestion pricing.

Jonas Eliasson: “Don’t tell people how to adapt. Nudge them. If you do it correctly – they’ll embrace the change”

Related: The Case for Physically Separated Bike LanesUrban Planning in Northern VirginiaDisregard for People by FedEX and UPS – Systems thinking allowed the engineers to design a solution that wasn’t about enforcing the existing rules more but changing the system so that the causes of the most serious problems are eliminated. – Using Outcome Measures for Prison Management

New Deadly Diseases

Management and the economy keep evolving. Many good things happen. In the last decade the best things are probably the increased deep adoption of lean thinking in many organization. and the adoption of lean and Deming methods in software development (agile software development, kanban and lean startup [which I do realize isn't limited to software development]).

Sadly all the deadly diseases Dr. Deming described remain. And, as I said in 2007, I think 2 new diseases have become so widespread and so harmful they have earned their place alongside the 7 deadly diseases (which started as the 5 deadly diseases). The new deadly diseases are:

  • extremely excessive executive pay
  • systemic impediments to innovation

In my view these 2 diseases are more deadly to the overall economy than all but the broken USA health system. The systemic impediments to innovation are directly critical to small percentage (5%?) of organizations. But the huge costs of the blocks to innovation and the huge “taxes” (extorted by those using the current system to do the oposite of what it should be doing) are paid by everyone. The costs come from several areas: huge “taxes” on products (easily much greater than all the taxes that go to fund our governments), the huge waste companies have to go through due to the current system (legal fees, documentation, delayed introduction, cross border issues…) and the denial of the ability to use products and services that would improve our quality of life.

The problems with extremely excessive executive pay are well known. Today, few sensible people see the current executive pay packages as anything but the result of an extremely corrupt process. Though if their personal pocketbook is helped by justifying the current practices, some people find a way to make a case for it. But excluding those with an incentive to be blind, it is accepted as a critical problem.

More people understand the huge problems with our patent and copyright systems everyday, but the understanding is still quite limited. Originally copyright and patents were created to provide a government granted monopoly to a creator in order to reward that creator for contributing to the development of society. Copyrights and patents are government granted interventions in the free market. They are useful. They are wise policy.

Continue reading

Be Thankful for Customer That Are Complaining, They Haven’t Given Up All Hope

I ran across this message and liked it (by wuqi256):

My time spent in a fast food chain (factory worker on weekends and security guard at night, yes really thanks to them, i have great jobs like that) when i was young trying to feed the family and study at the same time was quite useful.

They taught me that “Customers who complain are the best customers, it shows that they have still residual faith and goodwill in the organisation hence we should sift out those frivolous complains from those genuine ones that need our urgent attention” These are people who we can and should do a lot for as a complaining customer still has a very high chance of becoming a “returning” customer.

The customers that we fear for the most are those that either have voiced out or not heard or those who have given up and moved on to another organisation. Those we can no longer do much for as they no longer give us a chance. Discontentment is one thing but find the root cause, remove the straw from the cauldron and the water will stop boiling.

I know I often don’t bother voicing my concerns when I have given up all hope the organization has any interest in customer service. Sadly this is a fairly common situation.

It isn’t easy to do, organizations that are customer focused need but taking advantage of those customers helping you by expressing the frustration (that many of your customers experience, but don’t express). To do so organizations need to develop a culture where everyone is encouraged to improve your processes. The tricky part is not claiming that is what you want, but actually creating and maintaining the systems that bring that about.

Related: The Problem is Likely Not the Person Pointing Out The ProblemCustomer Service is ImportantCustomers Get Dissed and Tell

You’ve Got to Find What You Love

Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven’t found it yet, keep looking. Don’t settle. As with all matters of the heart, you’ll know when you find it. And, like any great relationship, it just gets better and better as the years roll on. So keep looking until you find it. Don’t settle.

- Steve Jobs



Watch this great commencement speech by Steve Jobs at Stanford in 2005.

We lost a great person today, when Steve Jobs died at the age of 56. His words are just as important today: you have got to find what you love to do. Keep looking until you find it. It won’t necessarily be easy to do. But life is too short to waste merely getting by.

My father found what he loved and pursued that throughout his life. He also died young. They both died young, but they both had great lives because they took charge to make the most of their lives. By doing what they loved they made the world a better place for many others, and themselves. Take that message to heart and make your life the best it can be.

Related: Quotes from Steve JobsPeter ScholtesPositivity and Joy in WorkBuild an Environment Where Intrinsic Motivation FlourishesRemembering Bill Hunter

Visual Management with Brown M&Ms

When you hear about rock musicians having a clause in their contract that they must have a bowl of M&Ms in their dressing room with all the brown M&Ms removed you could be excused for thinking: what will these crazy celebrities do next. Well it might just be those crazy celebrities are using visual management (granted I think there could be better methods [a bit more mistake proofing where the real problems would be manifest] but it is an interesting idea). Basically if they didn’t have the bowl of M&Ms, or if the brown M&Ms were not removed, they could distrust the thoroughness of the contractors. And they would check to see what other, actually important, contractual requirements were not followed.

Righting The Wrongs: Van Halen and M&Ms

The staff at venues in large cities were used to technically-complex shows like Van Halen’s. The band played in venues like New York’s Madison Square Garden or Atlanta’s The Omni without incident. But the band kept noticing errors (sometimes significant errors) in the stage setup in smaller cities. The band needed a way to know that their contract had been read fully. And this is where the “no brown M&Ms” came in. The band put a clause smack dab in the middle of the technical jargon of other riders: “Article 126: There will be no brown M&M’s in the backstage area, upon pain of forfeiture of the show, with full compensation”. That way, the band could simply enter the arena and look for a bowl of M&Ms in the backstage area. No brown M&Ms? Someone read the contract fully, so there were probably no major mistakes with the equipment. A bowl of M&Ms with the brown candies? No bowl of M&Ms at all? Stop everyone and check every single thing, because someone didn’t bother to read the contract. Roth himself said:

“So, when I would walk backstage, if I saw a brown M&M in that bowl . . . well, line-check the entire production. Guaranteed you’re going to arrive at a technical error. They didn’t read the contract. Guaranteed you’d run into a problem. Sometimes it would threaten to just destroy the whole show. Something like, literally, life-threatening.”

Related: The Importance of Making Problems VisibleVisual Work InstructionsGood Process Improvement PracticesGreat Visual Instruction Example

Sometimes Micro-managing Works

Sometimes micro-managing works. That doesn’t mean it is a good strategy to replicate. If you benchmark Apple you might decide that you should have a tyrannical obsessive involved CEO who is directly involved in every detail of products and services. After all Apple is now the second most valuable company in the world with a market capitalization of $324 billion (Exxon Mobil is the top at $433 billion) and a huge part of that is Steve Jobs.

Nice quote from How to beat Apple

Apple products & services that Apple does well are the ones that Steve Jobs uses

An interesting point, and really it doesn’t matter if it is completely true it illustrates a point that Steve Jobs is the rare leader that helps by being completely involved in nearly every detail. And at the same time he provides strategic leadership rivaled by very few others. But if you try to benchmark this (simplistically – as most benchmarking is done) you will fail. This works with Steve Jobs and maybe a handful of other people alive today. But with most leaders and organizations it would fail completely.

On another point Jason Kottke makes, I would normally suggest the opposite approach:

Openness and secrecy. Competitors should take a page from Apple’s playbook here and be open about stuff that will give you a competitive advantage and shut the hell up about everything else. Open is not always better.

I think you may well be better off doing the opposite and countering Apple’s secrecy with openness. It would depend on your organization, but, I think you might be better off trying to exploit Apple’s weakness instead of trying to do what they do well. Now things are never this simple but on a cursory level I think that is where I would look.

Google now has a market cap of $171 billion, Apple is almost double that – just 3 years ago Apple first exceeded Google’s value.

Related: Leadership is the act of making others effective in achieving an aimThe CEO is Only One PersonJeff Bezos Spends a Week Working in Amazon’s Kentucky Distribution CenterRespect for PeopleDee Hock on Hiring

Toyota Kata Song – The Times They Are Changing

Very well done song, Toyota Kata – Managing by Means, by Doug Hendren – to the music of “The Times They are A-changing” by Bob Dylan. Doug sounds impressively similar to Dylan and the words are actually wonderful.

Managing by results, it don’t work anymore. Don’t stand in your office, go to the shop floor

to really improve you must iterate, see our problems as treasures before its too late, and eliminate waste, whether little or great. Take baby steps up to your dreams. And gradually reach a more flexible state if we want to manage by means.

Via: Lean Blog

Related: Toyota Kata (book)Learn Lean by Doing LeanThey Will Know We are Christians By Our LoveIf Your Staff Doesn’t Bring You Problems That is a Bad Sign

Innovation in Thinking and the Web

Investing time and effort to attract “the right kind” of contributors to a news site

He thought we needed to make the same shift with our users – instead of seeing having to engage with them digitally as a time-consuming and resource eating problem, we should be seeing our audience as an asset to the brand. Any online organisation that doesn’t include readers in the production chain is inherently inefficient.

I agree. And I think this is a good example of an organization needing to adapt to the changing environment. I thought about what I would do if I ran a news site and how I would try to take advantage of the possibilities to increase engagement using internet technology.

I do think if I was trying to increase engagement I would try to figure out how to highlight thoughtful commenters. I would probably try to look into something like the commenting system on Reddit (with Karma) and also the ability to follow commenters (like you can follow article contributers on Seeking Alpha). I would look at giving value back to good comments (maybe something like commentluv). I would definitely have a pages where you could view more comments by a commenter. I would try to set up categories and then list top commenters on local politics, local sports, health care… I would display in the order of popular comments (like Reddit) not just list in order made. There are lots of ideas I don’t see used (but I haven’t really thought about it until 5 minutes ago – maybe these are already widespread, or maybe I haven’t really though out why they wouldn’t work well).

I just remember a post here previously about a newspaper in Kansas that was taking some sensible actions, and seemed to get the value chain they were serving. I would also take a look at them if I were really going to do this for a news organization.

This blog has a failure miserable, engagement with readers. Hopefully I can work on improving that in the next year. My last post, Customer Focus and Internet Travel Search (is the effort of one of the 4 founders of Reddit).

Related: Joel Spolsky Webcast on Creating Social Web ResourcesJohn Hunter online (Reddit comments…)Delighting CustomersPrice Discrimination in the Internet Age

Customer Focus and Internet Travel Search

The internet should make finding airline flight information easy. Instead it is a huge pain. Hipmunk has taken on the challenge of doing this well, and I think they have done a great job. This video provides an excellent view of both web usability and customer focus. This is a great example of focusing on providing customer value and using technology to make things easy – which is done far to little at most companies.

Related: Innovation Example (Farecast – which seems to have been bought by Microsoft and broken)Making Life Difficult for CustomersConfusing Customer FocusJoel Spolsky Webcast on Creating Social Web ResourcesCEO Flight Attendant

Learn by Seeking Knowledge – Not Just from Mistakes

Being open to new ideas and new knowledge is what is needed to learn. Experimenting, seeking out new knowledge is even better.

You can be successful and see an even better way to do things and learn from it. This seems the best way to learn to me – not to just learn from mistakes. Of course this means your goal has to be improvement not just avoiding more mistakes than before.

Your actions are based on theories (often unconsciously): and learning involves improving those theories. Learning requires updating faulty ideas (or learning new ideas – in which case ignorance rather than a faulty theory may have lead to the mistake). Encouraging people to learn from mistakes is useful when it is about freeing them to make errors and learn from them. But you should be learning all the time – not just when you make mistakes.

You can be also be wrong and not learn (lots of people seem to do this). This is by far the biggest state I see. It isn’t an absence of people making mistakes (including carrying out processes based on faulty theories) that is slowing learning. People are very reluctant to make errors of commission (and errors of commission due to a change is avoided even more). This reluctance obviously makes learning (and improvement) more difficult. And the reluctance is often enhanced by fear created by the management system.

It is best to be open and seek out new knowledge and learn that way as much as possible. Now, you should also not be scared to be wrong. Taking the right risks is important to improving – encouraging creativity and innovation and risk taking is wise.

Experiment and be open to learn from what could be better and improve (PDSA is a great way to try things and evaluate how they work). And the idea is not to be so conservative that every turn of the PDSA cycle has no failures. In order to get significant successes it is likely you will try things that don’t always work.

The desire to improve understanding (and the desire to improve results provides focus to the learning) is what is valuable in learning – not being wrong. Creating a culture where being wrong needs to be avoided harms learning because people avoid risk and seek to distance themselves from failure instead of experimenting and digging into the details when something goes wrong. Instead of learning from mistakes people try to stay as far away from them and hide them from others. That is not helpful. But what is needed is more desire to continually learn – learning from mistakes is wise but hardly the only way to learn.

Related: The Illusion of Knowledgeconfirmation biasManagement is Prediction

Supporting Free and Open Source Software

Gabriel Weinberg (founder of the great Duck Duck Go search engine) proposed starting a FOSS Tithing movement. Many benefit greatly from free and open source software like: Ruby on Rails, Linux (my favorite version Ubuntu), WordPress, Apache, Ruby, Perl, Nginx, Phusion Passenger. As well as other related efforts Electronic Frontier Foundation, creative commons, PLoS.

If we can get people to contribute to this idea that would be great. I have had curiouscat.com give some money to continue the development of the open source software we use, and the related efforts.

The contribution of time is often even more important (and for some people, easier). Those individuals and organizations that are giving back in this way are key to the community benefits. Open source software is a great example of systems thinking and taking a broader view of how to succeed. And for managers interested just in their organization allowing programmers to contribute to open source projects can be very beneficial building their intrinsic motivation by contributing to something they care about them and having them learn through such participation.

My goal is to give back more. But so far that goal has been held back by my failure to better achieve the goal to increase revenue at curiouscat.com. I am going to make a new effort to have curiouscat.com give back more going forward.

I get so much from great open source software like Ruby, Rails, Ubuntu, Apache, MySQL along with lots of less well known software, that it is important to me to contribute to sustaining the environment that will continue to produce such great software.

Related: Open Source Management TermsWhat Managers can Learn From Open Source Project ManagementOpen Source: The Scientific Model Applied to ProgrammingGoogle Summer of Code

Jason Fried: Why work doesn’t happen at work

In this TED talk, Jason Fried, founder of 37 signals, discusses how people get work done. When asked where do you go when you really need to get something done, almost no-one says: the office (unless it is early in the morning or late at night)? This is especially for creative people and knowledge workers. They need long stretches of uninterrupted time to concentrate. “The real problems in the office are the managers and the meetings.”

The main theme is that interruptions can severely damage performance, especially for what Peter Drucker called knowledge workers.

He offers 3 suggestions to make the office a place people can get work done. No talk Thursdays. And if that is too much how starting with 1/2 a day Thursday once a month. Second, replace active distraction (meeting, going and talking to a person) with passive distraction (email and IM) that a person can turn off when they need to focus. I have found this very useful myself. And third, cancel meetings. He closes with: I hope I have given managers reasons “to think about about laying off a little bit and giving people some time to get work done.”

Related: Understanding How to Manage GeeksBetter MeetingsWorkers Allowed Recreational Use of the Internet are More ProductiveManagement By IT Crowd Bosses

Airport Security with Lean Management Principles

The ‘Israelification’ of airports: High security, little bother

We [Israel] said, ‘We’re not going to do this. You’re going to find a way that will take care of security without touching the efficiency of the airport.”

“The whole time, they are looking into your eyes — which is very embarrassing. But this is one of the ways they figure out if you are suspicious or not. It takes 20, 25 seconds,” said Sela. Lines are staggered. People are not allowed to bunch up into inviting targets for a bomber who has gotten this far.

Lean thinking: customer focus, value stream (don’t take actions that destroy the value stream to supposedly meet some other goal), respect for people [this is a much deeper concept than treat employees with respect], evidence based decision making (do what works – “look into your eyes”), invest in your people (Israel’s solution requires people that are good at their job and committed to doing a good job – frankly it requires engaged managers which is another thing missing from our system).

The USA solution if something suspicious is found in bag screening? Evacuate the entire airport terminal. Very poor design (it is hard to over-emphasis how poor this is). It will take time to design fixes into physical space, as it always does in lean thinking. It has been nearly 10 years. Where is the progress?

The Colbert Report Mon – Thurs 11:30pm / 10:30c
Tip/Wag – TSA, Bert & Dogs<a>
www.colbertnation.com
Colbert Report Full Episodes 2010 Election March to Keep Fear Alive
A screener at Ben-Gurion has a pair of better options. First, the screening area is surrounded by contoured, blast-proof glass that can contain the detonation of up to 100 kilos of plastic explosive. Only the few dozen people within the screening area need be removed, and only to a point a few metres away.

Second, all the screening areas contain ‘bomb boxes’. If a screener spots a suspect bag, he/she is trained to pick it up and place it in the box, which is blast proof. A bomb squad arrives shortly and wheels the box away for further investigation.

This is a very small simple example of how we can simply stop a problem that would cripple one of your airports,” Sela said.

Lean thinking: design the workspace to the task at hand. Obviously done in one place and not the other. Also it shows the thought behind designing solutions that do not destroy the value stream unlike the approach taken in the USA. And the better solution puts a design in place that gives primacy to safety: the supposed reason for all the effort.
Continue reading

Why Don’t Football Players Just Thrown the Ball Out of Bounds to Stop the Clock

I have never understood why players don’t lateral the ball out of bounds to stop the clock in pro or college football in the USA. If time is running out and the player is tackled in bounds the clock keeps running and time can expire. You can stop the clock by running out of bounds. Also if the ball goes out of bounds the clock is stopped. I figured maybe there was some rule against just throwing the ball out of bounds to stop the clock. I never hear announcers explain that they can’t just throw the ball out of bounds due to a rule, though.

John Clay, Wisconsin Badgers

I decided to go the the source, on page 73 of the official NCAA football rules it says the clock stops: “With fewer than two minutes remaining in a half a Team A ball carrier, fumble or backward pass is ruled out of bounds.”

However, on page 103 (of 272) it states: “A ball carrier may hand or pass the ball backward at any time, except to throw the ball intentionally out of bounds to conserve time. [The penalty for breaking the rule is] five yards from the spot of the foul; also loss of down.” The clock is started when the ball is ready for play (rule 3-4-3 says the clock restarts on the ready to play signal for “unfair clock tactics” penalties).

From the rule book appendix: “A ball carrier, late in the second period, throws a backward pass out of bounds from behind or beyond the neutral zone to conserve time. RULING: Penalty – Five yards from the spot of the foul and loss of down. The clock starts on the ready-for-play signal.” By the way an illegal forward pass has the same penalty.

Still to me this leaves a very good reason to lateral the ball out of bounds. It should certainly take less time to line up and ground the ball after the ball is marked ready for play than it would if the clock is never stopped. Often you could still have time to run a play or just ground the ball and stop the clock.

The NFL does use a 10-second runoff rule, and with the referee winding the clock on the ready for play, which would likely make an deliberate attempt a bad idea. But as far as I can tell college rules don’t have that time penalty. It seems to me, if you want to have a rule against stopping the clock that way, it probably is wise to have the 10 second penalty.

Even if for some reason taking that penalty doesn’t work if you are in the middle of the filed you could thrown it to someone near the sidelines to let them get out of bounds. Also if you at least make that attempt and then the ball goes out of bounds (based on your lateral attempt) it seems to me you at least have the hope the referees won’t call the penalty that requires your intent to thrown it out of bounds to stop the clock, in order for it to be a penalty.

Related: Randomization in SportsNHL Experiments with the Rules of HockeyPhysicist Swimming Revolution
Continue reading

  • Recent Trackbacks

  • Comments