Tag Archives: command and control

The Burgundy Ribbon Rule

BurgundyRibbonsCalPERS

Another rule, and for the time being, at least, I am happy* with the wording here: an abuse of asking almost always presents an abuse of power.

Take the case of burgundy affair at the public pension fund CalPERS, as documented by Yves Smith over at Naked Capitalism.

This past fall, documents obtained by Smith show, CalPERS CEO Marcie Frost “asked the CalPERS senior leadership team to wear burgundy to show their support for her” as she faced questions about representations she had made regarding her educational background before and after she was hired. Burgundy ribbons were set out in break rooms with messages urging the “Team” to wear one in a show of support. “No pressure and no problem if you do not want to do this,” the message reads, “it is completely voluntary.” Completely.

“This is obviously inappropriate,” writes Smith,

since a request made by a CEO is effectively an order. CalPERS executives and employees are civil servants, not Frost’s personal retainers. As an expert on managerial and political conduct reacted:

I don’t even know what category to put this in. A scandal-plagued boss orchestrating support by inventing gang colors and pressuring employees to wear them? What happens to the employees who don’t perform this ritual of fealty? Should they be polishing their resumés and practicing their swimming skills?

These incidents smack of underlying panic. Frost is working overtime to shore up her position as CEO in the face of fully deserved questions regarding her long history of misrepresentations about her background, which include committing perjury in Washington on a gubernatorial questionnaire. Not only is Frost pushing her subordinates far too hard to back her up, since they can only do so much for her and coercing them will diminish their good will, she is also showing a lack of a sense of professional boundaries….

Frost’s burgundy campaign may well have crossed the line into creating a hostile work environment. One senior staff member who came to the office and saw the “dress burgundy” request too late to comply issued a written apology. Similarly, when “asked” to wear burgundy to an offsite, one [employee] who wears only black and white felt compelled to buy a burgundy outfit to comply…

…word clearly got around quickly, including the notion that non-compliance was risky.

I am still fussing over the word “presents,” and I’ve considered “masks” and variations in that direction, as well as “declares,” “represents” or “signals.” That one abuse (presenting an order as a request) almost always carries the other with it — almost always, because I don’t want to get caught up right now in handling exceptions — is the essential thing.

You can read my other posts about asking here.

*Postscript: On reflection, I might prefer this much more straightforward and concrete formulation: when someone presents an order as a request, look for an abuse of power. That way, we don’t have to worry too much about motives, or figure out whether the person doing the asking is trying to get away with something. It falls to the person being asked to watch for abuse, and conduct herself accordingly. (Being asked for something, or to do something, turns the ethical spotlight on you, or at least requires you to share it with the person doing the asking. This is your moment.) In a case like the present one, and in most superior-subordinate relationships, calling out abuse may be impractical. Subordinates will bury grievances, reluctantly comply, or pretend not to have been aware of the request. The subordinate’s dilemma in this case registers a failure of governance; a failure of governance at the highest reaches makes itself manifest at even the lowest levels and in the most trivial matters (the wearing of a ribbon). More immediately, presenting orders as requests hijacks power, creates distrust (after all, we can’t help but wonder about motives), and makes people prone to dissemble. All this thwarts collaboration, or the power to do things (to act) together.

Serious Conversations, 7

In these notes on serious conversations, I keep circling back, it seems, to two ideas: first, that what makes a conversation serious is not its subject matter or tone, but the stance of its participants toward each other; and, second, that the conversational stance requires that we confer a certain authority on our interlocutors, or (to put it another way) recognize that they have standing to address us.

While other kinds of authority — title, rank, role — are of secondary importance, and can sometimes even get in the way, this moral authority or standing is fundamental. It does not have to be earned, proven or ratified by reference to some person, written instrument or record of accomplishment outside the conversation or by institutional set up. It is constituted and realized in the relationship you and I have — or, if that is just too clunky, let’s say it is the relationship you and I have; and it is sufficient authority for a serious conversation because it makes us mutually accountable to each other.

Where this equal human stature (or dignity) is respected (and appreciated), it can be a source of power: not just the power of one over another, but the power to make claims or demands of each other, or to ask and answer, and this power of asking is essential if we are going to deliberate in earnest about our situation or collaborate on something new.

The conversational stance allows for genuine co-creation, because it’s not founded on subordination or one person ordering the other about. And the capacity for co-creation, the creative power that we share, only increases as we include more people in the circle of the conversation. (Of course there are limits: the research on group size and social complexity Dunbar summarizes suggests the circle probably should not widen beyond 150 people.)

I’ve tried to capture this thought in a simple rule: the power of asking will always be greater than the power of command.

That’s the basic position.

Another way to put the same thought might be in terms of the mechanics of ordering versus asking: whereas in the former we have one person directing the will of another, as we might address a short-order cook, in the latter we direct each other’s wills, so that we are, to stick with the metaphor, chefs in our own kitchen.

Of course the usual caveat applies about too many cooks spoiling the broth, I guess, but let’s also remember that people have different talents, training and competencies, and we can worry about how to order and organize ourselves once it comes to the actual cooking. Right now we’re just having a conversation.

Let’s also acknowledge, while we’re at it, that short-order cooks are models of industrial-era efficiency (but no longer efficient enough for the post-industrial fast food kitchen); gains in co-creativity can and probably will translate to losses in short-term efficiency.

Some concessions on one side or the other will probably have to be made, but too often the proponents of efficiency win without any argument, and people start giving orders or setting out plans for what’s to be done before the conversation even has a chance to get started. That’s when all the real power goes out of the room.

A Fourth Note on the First CEO: The Postwar Provenance

A reader of my posts about the acronym CEO suggests I have a look at the organizational chart for the Manhattan Project to gain a better appreciation for the “American and military” provenance of the term. “I believe during a period of intense collaboration between the military and private sector after WWII,” he writes, “it somehow permeated to corporate use.”

I have wondered about that “somehow,” and wondered, too, if I could be a little more specific about the course this permeation took. Is the acronym CEO — and the idea of the CEO — an outgrowth of the military industrial complex? Does the rise of the CEO to a position of cultural celebrity in the 1970s and 1980s tell us something (we don’t already know) about how the postwar environment shaped American ideas of command, power and leadership, in the private sector and in the public sector?

These are questions worth asking, I think, though I’m not sure the organizational chart for the Manhattan Project is the best place to start. Or at least that chart doesn’t include the term “CEO.” There is an “OCE” — an Office of the Chief of Engineers; the role of “Executive Officer” was assigned to J.B. Lampert. That title was also used in the appointment of Leslie R. Groves (of Now It Can Be Told fame), who in the org chart has the title of Commanding General.

The larger point here still merits consideration: just follow the careers of the engineers and military commanders identified in the Manhattan Project org chart, consider the military industrial development of the 1950s and the American business environment in which COs and XOs and members of the OCE worked closely with the private sector, and in many cases left the military to join the private sector: it’s easy to see how a new vocabulary of command might have emerged during that period, and eventually found its way into ordinary usage.

Still, I want specifics and cases I can point to. To that end, I’ve written to the company historian at General Electric, to ask whether the term CEO was in general use before the era of Jack Welch (who for a variety of reasons — not least for his cultural celebrity — probably deserves the title “The First CEO”). I’m looking for some examples of usage from the days of Ralph J. Cordiner (Chief Executive Officer from 1950-1963), Fred J. Borch (Chief Executive Officer 1963-1972) or Reginald H. Jones, who served from 1972-1981.

ReaganProgressGE seems like an obvious place to start looking. The company that brought us both Jack Welch and Ronald Reagan was, during the war and then in the postwar period, at the very center of military-industrial development; and big American companies like General Electric were never just manufacturing products — or even “progress,” which Reagan used to tout on TV as GE’s “most important product.” They were also designing models of power that persist to this day.

The Whole Foods Language Police: Keystone Cops or Company Thugs?

Whole Foods now denies that Lupe Gonzales and Bryan Baldizan were suspended for speaking Spanish on the job. While the company does, in fact, have a written policy requiring employees to speak English while “on the clock” — in order to maintain what one Whole Foods manager calls “a uniform form of communication” — the employees, Whole Foods now says, were fired for being “disrespectful.”

The proof? A letter Gonzales and Baldizan wrote, asking why workers in the Albuquerque, New Mexico store could be dressed in Mexican bandito costumes (“sarapes and sombreros with fake mustaches”) on Cinco de Mayo, but are “forbidden” to speak Spanish on the job.

Nothing says respect like grotesque parodies of Mexican culture. As for the actual, living culture of New Mexico (where, by the way, not just Spanish but Ladino is spoken) — just keep it off the clock and preferably outside the store.

Ralph Arellanes, New Mexico director with the League of United Latin American Citizens, said he “almost fell off [his] chair” when he first got wind of this; now the League is threatening a nationwide boycott if Whole Foods does not drop the policy. The company says the English-only policy is necessary for “safety” and — incredible though it may seem — inclusion: if workers speak Spanish, “team leaders” and customers may feel “excluded.” How is a leader expected to lead, or customer able to shop, or feel that they belong at Whole Foods, or in Albuquerque, New Mexico, for goodness sake, with all that Spanish being spoken around them?

It’s tempting to write this off as yet another example of the folly of top-down corporate policy-making: policies imposed from above usually hit the floor with a thud; hilarity or disaster ensues. There’s also a cautionary tale here about policing language, which hasn’t worked since the days of Babel. The language police usually turn out to be Keystone cops.

keystone-cops-granger
Or, worse, they end up offending people, and the policy-makers look historically ignorant, culturally arrogant and out of touch.

I wonder, however, if there’s something else at work here. People who speak the same language — a language “team leaders” don’t speak — are able start their own conversations about work and other topics. They can talk about their lives and their families. They can form new bonds and build networks within and beyond officially recognized teams.

Those informal bonds can pay off. It’s been repeatedly shown that unofficial, loose, self-directed, peer-to-peer social bonds help people learn from one another and develop new approaches to their work: people who share a language can share practices that have proven effective, find new ways to do things, or create unwritten rules and new combinations that will help them collaborate.

On the other hand, of course, workers can use a language they share to talk about the realities of their jobs, the possibilities they see for themselves within the organization, the conditions under which they work as well as the barriers to their advancement. And they can talk about their Anglophone leaders, too. I suspect those are conversations Whole Foods — “a staunchly anti-union enterprise” run by a man who sees himself as the benevolent father of his workers — probably wants to nip in the bud.

Creativity or Command?

John Hagel and John Seely-Brown have a new piece on CNN Money called “Welcome to the Hardware Revolution” that nicely highlights an issue I touched on yesterday: the limits that institutionalized power — or the ways we institutionalize power — can place on learning and innovation.

I suggested, in passing, that business organizations rely on hierarchical models of command-obedience in order to achieve efficiency; but that doesn’t always work to their advantage (and the performance advantage to be gained from scalable efficiency, Hagel and Seely-Brown have argued elsewhere, isn’t anywhere near what it used to be). What these companies may gain in efficiency they lose in creativity, learning and innovation.

Here is what Hagel and Seely-Brown have to say in their “Hardware Revolution” piece:

many of the executives we speak with list talent development and innovation as top priorities, but for all they push, progress remains a struggle. Part of the problem is that most businesses’ institutional structures, hierarchies, and cultures actually limit the connecting, exploration, tinkering, and improvisation that make learning and innovation possible.

Increasingly, the sharing of ideas and new developments are taking place outside big companies or officially sanctioned workflows and processes, in what Hagel and Seely-Brown call “creation spaces.” These are spaces — communities, networks and cultures — conducive to what Illich would call conviviality: places real or virtual, open and decentralized, where people congregate to share tools and experiment together, learn from one another, try new things, and be part of a community of people with shared interests.

The article goes on to recommend some basic questions business executives can ask themselves in order to improve their companies and move them toward creativity, or at least get their bearings. But there’s another question looming behind those: the question how (in a large and established organization) you go about institutionalizing the kind of practices you find in creation spaces. Eventually, something’s got to give; and if it comes down to a decision between preserving organizational hierarchies and legacy models of how stuff gets done or opening the doors to creativity — how many will choose the latter?

Maybe the choice is not as stark as my title makes it out to be. Let’s just say there are better ways to spur creativity than to command it.

Everybody’s A Beginner

This passage from Hannah Arendt’s The Human Condition has come up again and again as I think about asking, action and non-coercive power — or what I’m calling the power of asking — so I thought I’d share it. It’s a little dense, but it repays careful reading.

With word and deed we insert ourselves into the human world, and this insertion is like a second birth, in which we confirm and take upon ourselves the naked fact of our original physical appearance. This insertion is not forced upon us by necessity, like labor, and it is not prompted by utility, like work. It may be stimulated by the presence of others whose company we may wish to join, but it is never conditioned by them; its impulse springs from the beginning which came into the world when we were born and to which we respond by beginning something new on our own initiative. To act, in its most general sense, means to take an initiative, to begin (as the Greek word archein, “to begin,” “to lead,” and eventually “to rule,” indicates), to set something into motion (which is the original meaning of the Latin agere). Because they are initium, newcomers and beginners by virtue of birth, men take initiative, are prompted into action. [Initium] ergo ut esset, creatus est homo, ante quem nullus fuit (“that there be a beginning, man was created before whom there was nobody”), said Augustine in his political philosophy. This beginning is not the same as the beginning of the world; it is not the beginning of something but of somebody, who is a beginner himself. With the creation of man, the principle of beginning came into the world itself, which, of course, is only another way of saying that the principle of freedom was created when man was created but not before. (pp. 176-177)

Pay close attention to Arendt’s distinction of action from labor and work in the first few sentences. That’s crucial. For Arendt, action is “never conditioned” by “others.” Unlike labor or work, action isn’t something we undertake because it is “forced” upon us by necessity or “prompted” by utility. It is not prescribed, commanded or ordered, nor are its terms to be set down for us by others in the form of rules or requirements. Its “impulse,” for Arendt, springs from within, or rather from that within us which responds to the fact that we are, each of us, a beginning.

You might get the impression from this passage — which places emphasis on initiative and invokes “the principle of freedom” — that acting is something one does, something one can only do, entirely on one’s own. That would be a misreading. There is a difference between autonomy and isolation, and a difference between being free from constraint or necessity and acting freely with others. We are all self-starters but we are also capable of starting things together.

It takes coordinating, and that’s where asking comes in.

One of the things that interests me about asking is that it can prompt action while recognizing and respecting freedom and autonomy. It can be a way of coordinating our actions with those of others, or of entering into league or “company” (the word is Arendt’s) with others — acting together. The power of asking is that it doesn’t set down rules or requirements, or set up a chain of command. It is a different kind of prompt: more like a cue for improvisation than a script to follow.

Asking doesn’t mean we have to do away entirely with all those rules, protocols and titles that structure human society and human institutions, but we also don’t have to take them so seriously and assume they are the primary condition of our lives. They are, at best, secondary agreements.

Leaders — the first to ask, or the first to act — may be primus inter pares, but in this view a leader is always inter pares, among equals. When we ask and when we act we are all on equal footing, and all of us, by the very fact of our birth, by nature, have the capacity to act, to begin, to set things into motion. We are all beginners.