Why We Need a Rosetta Stone to Interpret Public Service Publications
Remember the BBC programme “Yes Minister”. It was a brilliant satire on the machinations of the English Civil Service. Many of the better bits can be found on YouTube. An example can be found here.
An Australian satire – “Utopia” – about the civil service and its obfuscations was recently available on Netflix. An example can be found here. It was sharp, often not too subtle and very recognizable for any of us who have had to endure dealing with the public service.
Both these programmes could be seen as entertainment. For some they could be viewed as biting satire. For civil servants I have no doubt they were looked upon as documentaries.
One of the things both series highlighted was the curious way in which the bureaucracy speaks and attempts to communicate.
On Thursday 12 November a document was released emanating from the Public Service Commission. It was a review of the performance of the Ministry of Justice and its handling of the employment matter of a Mr. Harrison. The review was entitled “Rapid Performance Improvement.” It occupies 68 pages and has 17 recommendations.
As background it should be remembered that the review arose from the handling of the continued employment of Mr. Harrison who was suspended on full pay after he was arrested on money laundering charges.
The review says the Harrison debacle illustrates wider issues at the Ministry, including leadership’s failure over a five-year period to challenge “flawed” internal advice about Harrison’s employment rights after he was charged.
What is fascinating about the review is not only that those decision makers (or non-decision makers if you prefer) in the Harrison matter have retained their jobs, but also the extraordinary way in which the review couches its recommendations.
This article is a study of the use of language in those recommendations and what that tells us about the Ministry of Justice and indeed the Public Service Commission.
The recommendations expose a bureaucratic culture in which ordinary ideas are buried beneath managerial jargon, abstract language and fashionable terminology. If the language of a public institution reflects the way it thinks, there may be more to worry about than its performance.
George Orwell warned that the corruption of language and the corruption of thought were mutually reinforcing. Bad language encouraged muddled thinking, which in turn produced even worse language. His 1946 essay Politics and the English Language remains a devastating indictment of those who use words not to communicate meaning but to disguise its absence.
Eighty years later, the authors of the Rapid Performance Improvement Review of the Ministry of Justice have provided an almost perfect illustration of Orwell’s concerns.
The 17 recommendations contained in the review address leadership, accountability, court operations, staff management and long-term planning. These are serious matters. Yet the language in which they are expressed is so saturated with managerial jargon, abstract nouns and fashionable bureaucratic expressions that the reader must repeatedly translate the recommendations into ordinary English to discover what is actually being proposed.
Indeed, Christopher Luxon, who in his public persona communicates almost exclusively in managerial jargon would be hard pressed to better this example.
The first recommendation is always a good starting point. It reads as follows:
One of the things both series highlighted was the curious way in which the bureaucracy speaks and attempts to communicate.
On Thursday 12 November a document was released emanating from the Public Service Commission. It was a review of the performance of the Ministry of Justice and its handling of the employment matter of a Mr. Harrison. The review was entitled “Rapid Performance Improvement.” It occupies 68 pages and has 17 recommendations.
As background it should be remembered that the review arose from the handling of the continued employment of Mr. Harrison who was suspended on full pay after he was arrested on money laundering charges.
The review says the Harrison debacle illustrates wider issues at the Ministry, including leadership’s failure over a five-year period to challenge “flawed” internal advice about Harrison’s employment rights after he was charged.
What is fascinating about the review is not only that those decision makers (or non-decision makers if you prefer) in the Harrison matter have retained their jobs, but also the extraordinary way in which the review couches its recommendations.
This article is a study of the use of language in those recommendations and what that tells us about the Ministry of Justice and indeed the Public Service Commission.
The recommendations expose a bureaucratic culture in which ordinary ideas are buried beneath managerial jargon, abstract language and fashionable terminology. If the language of a public institution reflects the way it thinks, there may be more to worry about than its performance.
George Orwell warned that the corruption of language and the corruption of thought were mutually reinforcing. Bad language encouraged muddled thinking, which in turn produced even worse language. His 1946 essay Politics and the English Language remains a devastating indictment of those who use words not to communicate meaning but to disguise its absence.
Eighty years later, the authors of the Rapid Performance Improvement Review of the Ministry of Justice have provided an almost perfect illustration of Orwell’s concerns.
The 17 recommendations contained in the review address leadership, accountability, court operations, staff management and long-term planning. These are serious matters. Yet the language in which they are expressed is so saturated with managerial jargon, abstract nouns and fashionable bureaucratic expressions that the reader must repeatedly translate the recommendations into ordinary English to discover what is actually being proposed.
Indeed, Christopher Luxon, who in his public persona communicates almost exclusively in managerial jargon would be hard pressed to better this example.
The first recommendation is always a good starting point. It reads as follows:
“Working inclusively with staff at all levels, review Ministry values and translate them into specific, observable leadership and staff behaviours. Embed these behavioural expectations in selection, development, performance and recognition processes.”
Behind this forest of words lies a simple proposition - consult employees, agree on appropriate standards of conduct and apply those standards when hiring, training, assessing and rewarding staff.
Why not say so?
Obviously, ordinary simple English lacks the necessary bureaucratic gravitas. Conduct must become “observable behaviours”. Standards become “behavioural expectations”. Hiring and training become “selection and development processes”. And everything must be “embedded”.
This is not precision. It is verbal inflation. And it confounds meaning.
The problem continues throughout the recommendations. The Ministry must “strengthen strategic external and internal communication/stakeholder engagement” to improve the “reach and depth of messaging around strategy and direction”.
Translated, this means explaining its plans more clearly to staff and outsiders.
But that would be far too straightforward. Communication must become “strategic”, people must become “stakeholders”, information must become “messaging”, and explanation must acquire “reach and depth”.
The vocabulary creates an impression of technical sophistication while communicating remarkably little. The use of complex words and phrases does not automatically confer erudition upon the writer, especially when it causes confusion of comprehension on the part of the reader.
Recommendation 13 proposes reviewing “mechanisms for harnessing frontline insights for operational performance improvement” and providing “feedback loops” when staff suggestions are adopted.
In ordinary English - ask frontline employees how things could work better, listen to their suggestions and tell them when their ideas are used.
The word “harnessing” is particularly revealing. Employees’ experience becomes a resource to be captured, like a team of horses, by management. Meanwhile, the simple courtesy of acknowledging a useful suggestion becomes a “feedback loop”.
People disappear into systems. Actions disappear into processes.
Perhaps the most extraordinary recommendation is number 4, which requires the Ministry to “refresh” its vision and strategy into a “plain language artefact” that must then be “cascaded” into business plans and staff performance agreements.
The irony of this use of language is exquisite.
A recommendation demanding plain language uses “artefact” to describe a document and “cascaded” to describe the process of incorporating organisational priorities into departmental plans.
The authors apparently cannot recommend plain English without first translating it into bureaucratic slop.
Elsewhere, the Ministry is told to review its “risk appetite settings”, strengthen its “foresight capability” and reconsider its “governance architecture”.
“Risk appetite settings” presumably means how much risk managers may accept. “Foresight capability” means the ability to plan ahead. “Governance architecture” means the arrangements for making decisions and allocating responsibility.
These are not obscure concepts. They are elementary requirements of competent administration.
Yet the language makes them sound like specialised engineering problems requiring elaborate technical solutions.
Recommendation 10 is particularly instructive. It calls for a review of governance architecture and delegation arrangements to reduce complexity, simplify “line of sight” and drive “tighter accountability”.
What does this actually mean? Make clear who can make decisions, who is responsible and who answers when things go wrong. But that raises uncomfortable questions. If responsibilities are unclear, who made them unclear? If accountability is inadequate, who has escaped it? What consequences have followed?
The recommendations offer no answers. Instead, they propose “reviewing the architecture”.
Accountability becomes something to be “driven” rather than something assigned to identifiable people. In that way the public service perpetuates the suggestion that all problems are systemic, no one is to be held responsible and heads will definitely not roll.
The same fascination with administrative machinery appears in Recommendation 9, which proposes an “implementation framework and lessons learned mechanism to support a 90-day planning and accountability model”.
Three layers of abstraction — a framework, a mechanism and a model — to convey a straightforward instruction which is this - set priorities every three months, check progress and learn from mistakes.
The danger is that the creation of a process becomes confused with the achievement of a result. A framework can be announced. A model can be adopted. A mechanism can be established. None necessarily means that a court hearing takes place sooner, a case is resolved more efficiently or public money is better spent.
The language becomes especially revealing when the recommendations turn to employees.
Recommendation 12 refers to “mapping the future capability” of court staff, investing in “capability uplift”, providing “enhanced pastoral care” and creating “improved career pathways”.
Court staff need adequate resources, training, professional development and appropriate support. Why not say so?
Instead, employees become collections of capabilities requiring uplift. Their careers become pathways. Their welfare becomes pastoral care.
The same recommendation contemplates transferring resources from National Office to “more empowered regional leadership, closely networked to the regional service delivery apparatus of justice system partners”.
Buried beneath this verbal rubble is a potentially important proposal - give regional managers more authority and resources to improve local court services.
It deserves serious consideration, not linguistic camouflage or language that is more opaque than the fog on Barrow-downs.
Recommendation 14 proposes improving the “strategic capability of the PX function” and attention to “strategic people management at the top table”.
Here the language approaches parody. An unexplained abbreviation is combined with fashionable management terminology to say that senior executives should take staff management seriously.
Yet there is a more troubling dimension to all this than mere pomposity.
Language shapes institutional thinking. When responsibility becomes governance architecture, employees become capabilities and accountability becomes a framework, the connection between decisions and their consequences becomes less visible.
There is also a subtle movement from professional responsibility towards behavioural conformity. The recommendations propose translating institutional values into observable behaviours and incorporating them into recruitment, performance assessment and rewards. Senior managers are to demonstrate “collective leadership” and “constructive challenge”.
These expressions sound reassuring. But who decides what constitutes constructive challenge? When does disagreement become insufficiently constructive? Could an employee’s advancement depend upon demonstrating approved organisational attitudes rather than professional competence?
The recommendations do not answer these questions.
This matters in a Ministry serving the justice system, where independence of judgment, candour, intellectual honesty and the courage to question authority should be fundamental professional qualities.
There is nothing objectionable about requiring honesty, competence, courtesy and accountability. There is considerably more objection to question when vaguely defined institutional values become instruments for measuring conformity.
The recommendations’ greatest weakness, however, is their frequent failure to identify precisely who must act, what must change and how improvement will be demonstrated. A detailed implementation plan may properly follow a review, but recommendations advocating clearer accountability should themselves be models of clarity.
Instead, much of their language could be transplanted into a review of almost any government department. Refresh the strategy. Strengthen communication. Embed expectations. Enhance capability. Review the architecture.
The phrases sound purposeful. Their very generality makes them almost meaningless without further explanation.
The Ministry of Justice has responsibilities affecting the liberty, property and rights of New Zealanders. Its work demands precision, clarity and accountability. Those qualities should be reflected in the language used to examine its performance.
Orwell understood that inflated language can conceal weak thinking and protect institutions from uncomfortable scrutiny. The antidote is not another framework, another model or another mechanism.
It is plain speaking.
A performance review should tell us what is wrong, why it is wrong, who is responsible and what must be done to put it right.
The ultimate irony is that the Ministry is being advised to communicate more clearly by reviewers who appear to have considerable difficulty doing so themselves.
Before the Ministry embarks upon another exercise in organisational transformation, perhaps it should begin with something considerably less ambitious. It should learn to speak English.
Five examples from the Ministry of Justice Rapid Performance Improvement Review demonstrate how straightforward ideas become buried beneath layers of managerial jargon.
Recommendation 1 — Managing staff behaviour
Bureaucratese:
“Translate them into specific, observable leadership and staff behaviours. Embed these behavioural expectations in selection, development, performance and recognition processes.”
Plain English:
Decide how managers and staff should behave. Apply those standards when hiring, training, assessing and rewarding employees.
Recommendation 4 — Planning for the future
Bureaucratese:
“Refresh both its vision and medium-term strategy into a plain language artefact based on measurable outcomes.”
Plain English:
Write a clear plan explaining what the Ministry wants to achieve over the next few years and how success will be measured.
Recommendation 9 — Checking progress
Bureaucratese:
“Develop an implementation framework and lessons learned mechanism to support a 90-day planning and accountability model.”
Plain English:
Set goals every three months, check whether they have been achieved and learn from mistakes.
Recommendation 10 — Who is responsible?
Bureaucratese:
“Review the effectiveness of the Ministry’s governance architecture, relevant policies and delegation framework against the objectives of reducing complexity, simplifying line of sight and driving tighter accountability.”
Plain English:
Simplify the rules. Make clear who makes decisions, who is responsible and who answers when things go wrong.
Recommendation 12 — Running regional courts
Bureaucratese:
“More empowered regional leadership, closely networked to the regional service delivery apparatus of justice system partners.”
Plain English:
Give regional managers more authority and resources to run local court services and work with other justice agencies.
Not one of these translations sacrifices the essential meaning. The original language makes elementary management responsibilities sound like complex technical exercises. It creates an impression of expertise without necessarily demonstrating it.
If a recommendation cannot be understood without translation, perhaps the first performance improvement should be in the writing of the recommendation itself.
David Harvey is a former District Court Judge and Mastermind champion, as well as an award winning writer who blogs at the substack site A Halflings View - Where this article was sourced.

No comments:
Post a Comment
Thank you for joining the discussion. Breaking Views welcomes respectful contributions that enrich the debate. Please ensure your comments are not defamatory, derogatory or disruptive. We appreciate your cooperation.