Mark Bonchek describes how organizations can use decision principles to empower employees to take action that is both timely and aligned with the organization's principles.
Healing the Wounds of the Assembly Line with Feedback Loops and Doctrine
Often, the focus on the ideal of the cross-functional, interdisciplinary, extroverted worker results in questions being asked which the average employee is insufficiently skilled to answer. In her book Quiet, Susan Cain cites the example of one of her research technical interviewees' recollection of a 'murder board,' a panel of decision-makers whom engineers had to face in order to get their new ideas considered for funding and other resources. One can imagine a hard-faced panel of besuited men tearing down the brilliant if meek engineer with the smug expressions of a young MBA grad: "What's your marketing plan!," they might shout, "
Autonomy and Acceptable Failures: The Need for Doctrine
Autonomy, especially in and around U.S. businesses, is a tricky concept. Autonomy is valued very highly in our culture, but the challenge of finding a way to hand off acceptable amounts of control takes a lot more work than most leaders or employees realize. Few companies have the patience or budget for mistakes which occur when a more-autonomous goes wrong, so they choose not to grant autonomy in the first place, or revoke it at the first sign of trouble. Understandably, the constant conflict of employees who need autonomy and leaders who need accountability plagues most organizations.
First Steps to Doctrine: the Example of Moore's Cloud Business Principles
For an example of a fluid progression from values to high-level beginnings of doctrine, consider this published set of business principles from Moore's Cloud, a "smart light" startup based in Australia. Their founder, Mark Pesce, explained that the intent of these principles was both internal and external, being used both to inform internal daily decision-making and to filter (attract or repel) investors by explicitly stating the company's commitment to open ecosystems and transparent business practice. By 'downloading' individuals decision-making guides from key leaders in the organization and then 'uploading' them to the business's guiding source code, Moore's Cloud has reduced huge amounts of unnecessary
Doctrine: Downloading Wisdom for Agility and Effective Improvisation
Doctrine sits in between strategy and plans. It is more specific than the strategy, but also more versatile than plans, or rules. Think of it as heuristics, or guidelines: the purpose of doctrine is to enable an individual to know what to do in a situation that's consistent with the strategy and achieves the objectives of a plan, but with flexibility, with autonomy, for the individual, in the circumstance. And the creation of effective business doctrine, I believe is going to be critical for the transition of business in the next century.