Posts Tagged ‘government’
“Do not remove a fence until you know why it was put up in the first place”*…
The last U. S. election was fueled, in some large measure, by dissatisfaction with government bureaucracies. Indeed, public trust in government has been low– among Democrats and Republicans alike– for decades; there is a wide-spread constituency for reform.
The pending answer at the federal level is an Elon Musk and Vivek Ramaswamy-led effort, DOGE, which their comments suggest will be an accelerationist application of “business principles” and slash-and-burn reduction.
But as Kevin Hawickhorst reminds us, there is another way, one that the U.S. has successfully pursued before– one that doesn’t throw the baby out with the bath water…
For the federal bureaucracy, the 1940s through the 1960s are a nostalgic time. The era saw one spectacular achievement after another: from winning World War II, to building the interstate highway system, to landing on the moon. At its high point, trust in the federal government reached almost 80% in the 1950’s, as opposed to only 20% today.
Trust in the federal government has plummeted alongside the federal government’s ability to accomplish anything – which is no coincidence. Although government competence has changed for many reasons, there is one forgotten reason: after the second World War, the government was competent because it taught its managers to be competent.
During World War II, the poor management in the federal government was keenly felt. Although federal management had never been especially good, it reached a boiling point when it began noticeably impeding the war effort. The Bureau of the Budget (now OMB) responded by creating a new management unit tasked with training federal managers.
They termed their newly-developed management approach work simplification, which held that implementation and policy went hand-in-hand, and therefore managers had to be trained to streamline procedure in order to achieve policy goals. Moreover, the Bureau of the Budget felt that this viewpoint could be systematically taught to federal managers of average competence, and developed a training program to do so.
During the war, the civilian agencies were incredibly short staffed due to the draft, so any procedural red tape or poor distribution of work created instant bottlenecks. Many of these bottlenecks directly impacted the war effort, as (for example) with slow approvals for important construction projects. The Bureau of the Budget therefore began an initiative to improve management around 1942.
They conducted user research with several agencies and eventually felt they had a management system that could scale, which they termed Work Simplification. They taught managers Work Simplification at training seminars, and also created guides and pamphlets to distribute across the government. I quote from one of their guides1 that sets out the problem, the audience, and their goal:
Thinking of this sort has been going on in the United States Bureau of the Budget for some time. It has culminated in the decision to make a concerted drive to capture the best available means for exposing and disposing of common management problems, set it forth in clear, simple language, and put it in the hands of those who can use it to best advantage. And who are they? They are the operating managers of government: middle management people and first line supervisors. […]
From the standpoint of the Bureau of the Budget, Work Simplification is a method of attacking the procedural problems of large organizations by equipping first line supervisors with the skill to analyze and improve procedures. It provides a way of tapping the great reservoir of unused practical knowledge represented by this group.
… Their management agenda developed a training program for the managers closest to the ground, rather than (as is common today) focusing on top leadership…
… Although Work Simplification was developed during World War II, it was still the common approach for training federal managers into the 1960s. These were the stodgy managers of the Eisenhower era who oversaw the building of the interstate highway system, or the administration of the GI bill.
This is not how the federal government approaches management today. It would be, obviously, unreasonable to claim that earlier success was entirely due to training managers differently. But it clearly contributed – their methods explicitly aimed to solve issues that today’s processes aggravate.
In particular, the Bureau of the Budget’s work almost remarkably anticipated current conversations on government efficiency. Reformers note that the bureaucracy piles up layers of procedure without ever rethinking them – process charting taught managers to reduce procedural burden. Reformers note that government IT piles up layers of software from different eras, with nobody understanding how it fits together – process charting taught managers the start-to-finish viewpoint. Reformers note that bureaucrats rarely consider what it’s like to actually apply for benefits – once again, a failure that process charting aimed to correct.
Process charting is clearly not a perfect solution to any of these issues. But it is proof that the government can train bureaucrats to tackle these issues head-on!
The overall lessons of Work Simplification are even more important. Work Simplification’s success did not last forever, but it did last for several decades. And it achieved its success because the Bureau of the Budget created free training for low-level managers, while nobody else particularly cared.
So would-be bureaucratic streamliners today – proponents of product management thinking, agile IT development, or what have you – might imitate Eisenhower’s bureaucrats. Above all, they should prove that their proposals are a rational method that can be systematically taught to low-level managers, in order to put their “great reservoir of unused practical knowledge” to use…
How the federal government taught its managers to cut red tape: “Eisenhower’s Bureaucrats,” from @KHawickhorst.
Via Jennifer Pahlka, whose own Recoding America (and her continuing work) are powerful contributions to this critically-important dialogue.
By way of context, a piece from Venkatesh Rao explicitly about “self-help” but very useful in this broader/more systemic context: “How to Fall Off of the Wagon.” (Per the diagram below, from that post, the approach suggested above is “clockwise”; the Musk/Ramaswamy m.o., “counterclockwise”… which will make clarifying sense after you’ve read the short essay. While I can’t attribute the significance that I draw from it [for the issue of reengineering the government bureaucracies that are not serving Americans as they should] to Rao, I’d note that the clockwise direction is green; the counterclockwise, red.)
* G. K. Chesterton, The Thing
###
As we fix it instead of throwing it away, we might recall that it was on this date in 1957 that President Dwight D. Eisenhower gave his sixth State of the Union Address to the joint houses of Congress. Eisenhower focused on three themes: a vigilant regard for human liberty, a wise concern for human welfare, and a ceaseless effort for human progress. His speech addressed the threats posed by the Soviet Union (and communism more generally around the world); urged efficient, effective government (as the government’s duty to citizens); and raised the issue of civil rights, calling for the enactment of what later became the Civil Rights Act of 1957.
Senate Majority Leader Lyndon B. Johnson called Eisenhower’s speech “a comprehensive and thoughtful analysis of the problems which confront our people.”
“Only in our dreams are we free. The rest of the time we need wages.”*…
The Economist is repurposing one of its famous indices…
Since 1986 The Economist has produced the Big Mac index as a light-hearted gauge of whether currencies are at their “correct” level. The famous burger is a good test of currency valuations because of its global uniformity and ubiquity. The same properties make it a useful way of comparing international salaries: how many Big Macs, in principle, can a typical worker afford with their wages?
The more conventional way of comparing incomes is to convert wages in different countries into a common currency. But that is misleading because exchange rates are volatile. Moreover, one American dollar goes a lot farther in, say, the Philippines than it does in America itself. The Big Mac helps to solve this problem as a ready-made illustration of purchasing power: it represents a bundle of goods (or, rather, a bun of goods) that is identical everywhere, and so it serves as a yardstick of the real cost of things from country to country.
For the Big Mac wage analysis (the MacWage, for short), we started with full-time, pre-tax earnings in 2023 as reported by the OECD, a club of 38 mostly rich countries. We then made a simple adjustment, dividing wages by the price of a Big Mac—all in local currencies. That gave us the number of burgers that the average full-time worker can buy annually.
The results? Americans can perhaps be forgiven for having somewhat expansive waistlines. Although fast-food prices have rocketed since the pandemic, Americans still earn more greasy calories than any others in our analysis [chart below]. The average American worker takes home the equivalent of 14,000 Big Macs in wages for a year of full-time work. At 590 calories a pop, they could buy enough burgers to keep ten adults fed for a year. The Swiss and Danes come, respectively, second and third in MacWages. At the bottom are Mexican workers, who can afford to buy about 2,500 Big Macs with their average annual wages.
A standard objection to any measure of higher incomes in America is that its workers generally get less time off. To factor this in, we looked at average hours worked, based on data from the OECD and the Conference Board, a business-research group. This yields slightly different results (see chart 2). Americans still get more than enough Big Macs—pulling in the equivalent of about 7.4 per hour on the job—but they drop to third in the ranking. The burger champions are the Danes, who earn 8.1 per hour, followed by the Swiss. Looked at another way, the average Dane works for just seven minutes to make enough money to buy a Big Mac. In Mexico—still at the bottom of the rankings after this hourly adjustment—workers must toil for about 57 minutes.
The MacWage is, of course, far from perfect. Danes may celebrate their top performance, but our measure misses how income taxes (which can surpass 50% in Denmark) eat into their burger budgets. Much else of what goes into the cost of living, from housing to transportation, is also barely reflected in the price of burgers. In a developing country like Mexico, where housing is relatively cheap and American fast-food indulgences relatively expensive, a burger-based wage calculation understates how much stuff an average worker can actually afford. Still, as a quick method for comparing incomes around the world, the MacWage is easily digestible…
The purchasing power of average earners across the OECD: “An alternative use for The Economist’s Big Mac index” from @ECONdailycharts in @TheEconomist.
* Terry Pratchett
###
As we supersize that, we might recall that it was on this date in 1979 that the U.S. government agreed to a bailout of the Chrysler Corporation. The smallest of the “Big Three” automakers, but still the 10th largest company in America, Chrysler suffering from a combination a bad management decisions and increased competition from Japanese and German automakers. Facing a $500 million loss for the year (and probably bankruptcy), newly-installed CEO Lee Iacocca asked the government for a guarantee on a $1.5 Billion loan package. In return for detailed plans from Chrysler detailing both how the company would right its ship and how other constituents (employees, suppliers, lenders) would make concessions, the Carter Administration (which feared that a Chrysler failure could lead to a “depression”– and depression-level unemployment– in the auto industry) agreed. In return for its guarantee, the government received stock warrants in the company.
Chrysler did turn itself around: it proceeded to introduce the “K-Car” line, then mini-vans, then the earliest generation of SUVs. The company repaid the government-guaranteed debt ahead of schedule; the Treasury made about $500 million on its warrants.
But of course, nearly thirty years later, in 2008, Chrysler received billions in a new bailout from the U.S. government in the aftermath of the financial crisis that decimated automotive sales over the following few years. Chrysler filed for Chapter 11 bankruptcy in April 2009, before being acquired in total by Fiat in 2014.

“For every complex problem, there’s a solution that is simple, neat, and wrong”*…
Last year, in explaining the Biden Administration’s emerging new economic policy, National Security Advisor Jake Sullivan talked of a “small yard, high fence” approach to its trade with China. The idea: to place strict restrictions on a small number of technologies with significant military potential while maintaining normal economic exchange in other areas.
The estimable Henry Farrell argues that this approach to technology and China is working poorly (though, he suggests, it will work much worse if Trump wins and takes office in January). Self-reinforcing political feedback loops and self-reinforcing expectations are leading to breakdown.
The fundamental problem of managing geopolitics through manipulating technological trajectories is not readily solvable given existing means, Farrell suggests. We live in a much more complex world than existing state institutions are capable of handling. Therefore, he argues, we need to remake the state…
… Making the right choices in a complex policy environment requires an approach that is a world away from the application of brute force at scale. Your maps of the environment are going to be all wrong when you go in, and brute force is likely to have unexpected consequences. It isn’t just that you are going to make mistakes (you are), but your map of the actual problem you are trying to solve is likely to be utterly out of whack. As you try to catch up with China on EV, you discover that you don’t understand the market right. As you try to impose controls on military use of semiconductors, you find out that you don’t have the information you need to really actually understand how the semiconductor market works.
The problem – as Jen Pahlka’s book Recoding America explains at length – is that addressing such complex problems does not fit well with the way that the U.S. government works. When you are trying to impose order a vast sprawling bureaucracy, which is its own mid-sized global economy, and when your people don’t trust government much, you rely on rigid contracting systems, which define the problem in advance down to its finest details, even if that definition is out of whack with reality. You don’t build connections between the bureaucracy and outside actors, unless they run through cumbersome and rigidly pre-defined channels because it takes months or years to get approval for such connections. And you certainly don’t try to remake policy in realtime as your understanding of the situation changes. Pahlka’s book is cunningly disguised as an account of US software outsourcing practices. If it mentions either ‘national security’ or ‘economic security’ once, I don’t remember it. But it is arguably (along with Dan Davies’ similarly motivated The Unaccountability Machine) the most important book on these topics of the last twenty years. [Your correspondent heartily agrees.]…
… what do you do – is this. You start to think… about how to build economic security institutions that are designed from the ground up to manage complexity. If you want to take ‘small yard, high fence’ seriously as a policy approach, you need to build the apparatus to discover what lies inside, what lies outside, and what the barriers ought be. That apparatus – and its prescriptions – need to change over time both to match a better understanding of the policy environment, and changes in the environment itself.
And we don’t have the apparatus to actually implement small yard, high fence properly. Nor do we have it for pretty well every other plausible economic security policy you might imagine, short of a brute force decoupling of the U.S. and Chinese economies. And if you did that, you would need enormous capacity to manage the horrifically complex aftermath, if that aftermath could even be managed at all.
Clearly, it is far easier to make these arguments in the general than the particular. Saying that you need reforms is straightforward, but figuring out what they ought to be, let alone how to implement them in current political circumstances, is an altogether more difficult challenge. But it is where the debate needs to be going – and there is a role for technology in it. We are in a situation that rhymes in weird ways with the situation discovered by Vannevar Bush after World War II – recognizing that the needs of government had changed, that vastly better information and feedback systems were required to meet those needs, and that even if we didn’t exactly know what those systems were, we needed to start figuring them out, and quickly. That world had its pathologies. This one does too. But to prevent them becoming worse, we need better ways to manage them, and to ensure that the solutions are better than the problems that they are supposed to mitigate.
This is – obviously – a radical set of claims. But it’s one that is entailed by the diagnosis of the problem that I’ve presented. If we need to manage complex challenges – of which the U.S. China relationship is only one – we need a state that is capable of managing complexities. We don’t have one. And that remains a first order problem, regardless of however hawkish or dovish you are…
We need a new kind of state for the new geopolitics: “‘Small Yard, High Fence’: these four words conceal a mess,” from @himself.bsky.social (and @pahlkadot.bsky.social). Eminently worth reading in full.
* H.L. Mencken
###
As we ruminate on restructuring, we might recall that it was on this date in 1954 (7 years after the transistor was developed at Bell Labs) that Texas Instruments introduced the Regency TR-1, the first commercially-manufactured transistor radio. Its performance was mediocre, but its small size and portability drove sales of over 150,000 units.
Further to Farrell’s and Pahlka’s points, it’s instructive to ponder what became of the transistor radio as a product category (and of the competitors in it) over the next few decades– and the altogether-unanticipated plethora of small, convenient, hand-held product categories it spawned: calculators, mobile phones, tablets… and whatever comes next…












You must be logged in to post a comment.