I recently watched a documentary about Norman Foster, an architect responsible for designing a wide array of stunning structures such as the Millau Viaduct in France, the Swiss Re Headquarters in London, and the Hearst Tower in New York.
The title of the documentary comes from a question raised by his mentor, Buckminster Fuller, early in Mr. Foster’s career. The question, “How much does your building weigh?” was unexpected but would radically influence Mr. Foster’s future designs.
Initially, this reminded me just how powerful probing questions can be but it also got me thinking about what often happens to our processes over time. They get heavy. Well-intended yet unneeded additions to the way people work slowly erode confidence in the process itself and the velocity with which the organization can deliver.
This is happening with frequent regularity even in organizations seeking greater agility. People begin to add sign-offs, approvals, wasteful documentation, and other governance steps not because it is needed but because it is comfortable. Eventually, this additional “weight” begins to drag an organization to a crawl and frustrate those trying to quickly deliver value.
What would happen if we began asking ourselves “How much does our process weigh?” What if you could visibly see the weight we are putting on the shoulders of our teams?
Here are few thoughts to consider as you add or remove activities in your process:
Jettison weight. Once something has been added it is rarely removed. Identify and remove defensive processes such as those mentioned in the post “Defending Your Position.” Identify and remove unneeded event-based processes such as those mentioned in a previous post, “A Wildly Swinging Pendulum.”
Everything is based on practice. This means the process is not developed by a single person in a cube somewhere but created by communities of practitioners based on real experience. Similar to packing your backpack for a multi-day hike, when you have to carry it yourself you only add weight if it’s really needed or it will save your life.
Everything is tested with pilots. Before implementing process change to your entire organization or department, test it with just a few teams. Get their feedback and remove anything not adding measurable value.
Obviously, depending on your situation or industry, audit, regulatory, or legal requirements must be added to your process regardless of how much they weigh. The value here would be in keeping people out of jail.
References:
Etienne Wenger, Communities of Practice, http://wenger-trayner.com/theory/
6 replies on “How Much Does Your Process Weigh?”
[…] being requested and collectively discover ways to remove and purge. Guide people on a journey to discover new, lightweight ways to accommodate the needs of the original artifacts. As you know, its much easier to add process than […]
[…] process baggage. The volume of complex systems and defensive processes are heavy and burdensome, weighing down the best of intentions for improvement. There seems to be an unwillingness to let go of old […]
[…] have all felt the impact of historical complexity and the burden of process (especially defensive processes). While listening in to a recent town hall, I heard a CEO state, “Customers love our products but […]
[…] your organization is one of those feeling this weight and are searching for a better […]
[…] will rise to the occasion when provided with a compelling vision, a likable, energized team, and a “right-weight” process to get their work […]
[…] Cannot Be Managed, Only Inspired (Part 2) Performance Cannot Be Managed, Only Inspired (Part 1) How Much Does Your Process Weigh? Meeting Resistance The Tester and Conversations About Quality Defending Your Position Shaping Your […]