- Set your own salary
- Vote your leaders in/out
- Come and go when you please
- Take vacation whenever you want
- If you finish your work by Wednesday, go to the beach and come back on Monday
- If you have to give back, you’ve taken too much
- Ask “why” three times and then stop
- Design for wisdom
A brilliant and emotionally moving talk from my favorite CEO of all time, Mr. Ricardo Semler.
Please, please, watch it. I guarantee that some, if not all, parts of the talk will fill your heart with joy! Well, maybe it will. If you’re an average, run-of-the-mill, anointed, business leader, it will either piss you off or strike fear into your bones.
If you want some more seminal Semler to whet your appetite, check out these two MIT-sponsored videos:
Make no mistake about it, Mr. Semler’s radical ideas are not a mess of pie-in-the-sky, Utopian psychobabblings. They’re the real deal, and they’ve been in play… in the real world… for over 20+ years at Semco.
In the pic below, I prefer taking the low road over the high road.
So, now that you and your accomplices have labored long and hard to transform your standard org into a high performing org, you’re happy as a clam. Whoo Hoo!
But wait! What happens when you inevitably team up to do business with a standard org? D’oh! I hate when that happens.
Note1: This bogus post was inspired by Bertrand Meyer’s book: “Agile!“. Specifically, the juice is squeezed from chapter 2: “Deconstructing Agile Texts“.
Business gurus love to fabricate crises and instill fear in their deep-pocketed C-level executive clients so they can pitch their latest idea (at $2000/day plus expenses) to “reinvent management!”
Steve Denning is a big-league business management guru, ala Gary Hamel, Tom Peters, Ken Blanchard, Bob Sutton, etc. Even though Mr. Denning has no software background, he somehow got into Jeff Sutherland’s refrigerator and managed to drink a whole pitcher of “agile” koolaid with nary a burp.
In a brilliant marketing move to distance himself from his peers, Steve has jumped on the “agile” bandwagon. He’s been busy advocating the migration of Scrum out of the software development trenches; up the ladder and into the corner office we go. I can visualize it: CEO as Certified Product Owner, COO as Certified Scrum Master, and the rest of the C-suite as second-class, uncertified, “developers“. (Why is there no certification program for developers?)
In closing out this post, I’d like to share with you this brief twitter exchange between Mr. Denning and the lowly BD00 :
Here’s your miserable predicament:
Here’s what Scrum can give you:
All ya gotta do to transform your 20th century horse and buggy into a 21st century Ferrari is hire a gaggle of agile coaches, agile scalers, and agile adoption experts to facilitate the much-heralded transformation:
So, what’s in da magic box? Shhhhhhh! BD00 knows. That scoundrel signed an NDA and successfully bribed some well-known, high profile, agile transformers into disclosing their 5 process secrets. Four of them consist of the following parallel micro-transformations:
The fifth transformation process component is the most important and well-guarded secret of the lot. BD00 had to pay an extra premium before it was disclosed. It is hoodwinking the eager sponsor into believing that the transformation was an astounding success:
After all was said and done, more was said than done.
A long time friend of BD00’s, Mr. William L. Livingston IV, asked me to post the following provocative product sheet on this blog:
Breakthrough October 2014
Everyone knows breakthroughs come in various kinds and sizes. The breakthrough announced here is in social system productivity. The noteworthy dimension of this breakthrough is the huge size of its available collective impact.
The math of its extravagant benefit is simple. This breakthrough applies to the productivity of any social system producing goods or services. The typical boost in social system productivity in application experience is 20%. The 2014 productivity of all the social systems around the globe, measured by the value of goods and services produced, the World Gross National Product, is $40 Trillion. By multiplication, the economic value of the benefit of this breakthrough to the world GNP is $8 Trillion/annum.
- The cost of the program is trivial. Its ROI computes in the many hundreds.
- No changes in facilities or personnel is necessary. Nothing is required of management.
- The attained positive transformation is fast. Program success is established and obvious in a couple of days. Tangible, measurable benefits start appearing in a couple of weeks.
- The program is transparent, natural law based, incontrovertible. Nothing is hidden. It has the characteristics necessary for universal, unconditional application.
- The need for this program cannot diminish. Its market opportunity is continuously replenished by business as usual.
- While the benefits to the participants sustain indefinitely after the program ends, eventually, with turnover, productivity maintenance will be necessary.
- There are various collateral benefits beyond the base economic 20%. Transformation brings a tide that raises all boats. There are many beneficiaries.
- Applications of the breakthrough can be demonstrated in your shop in a day and/or you can visit an application in process. One day of first-hand experience will do it.
To express interest in auditing an application, contact firstname.lastname@example.org
Since I enjoyed reading Tom DeMarco’s “Slack: Getting Past Burnout, Busywork and the Myth of Total Efficiency” years ago, this diagram in Jamshid Gharajedaghi’s “Systems Thinking: Managing Chaos and Complexity” brought back some fond memories of that book:
The diagram shows the slow, insidious erosion in flexibility that occurs in a complex system when efficiency and optimization initiatives are relentlessly applied to the system by its uninformed stewards. As the “slack” is stretched out of the system due to increasing internal pressure, it: 1) loses its robustness to external stressors, 2) the tension between connected nodes increases, and 3) the inter-node couplings harden. At the system breaking point, one or more of the connections crack open, the nodes fly apart, and the conglomeration ceases to function as a whole – a system. I hate when that happens!