[2425.AP] Ministries and Offices

Here’s a thought I had: what if we had a flexible system of executive offices, in addition to ministries, to handle persistent long-term responsibilities? For instance, one way this could work might be:

  • Similar to ministries, the Prime Minister can create offices to focus on particular policy concerns.
  • Unlike ministries, creating or shutting down offices is subject to Assembly approval.
  • Similar to ministries, each office is led by a director, appointed by the Prime Minister and confirmed by the Assembly.
  • Similar to ministries, each director serves until the end of the Prime Minister’s term.
  • Unlike ministries, each office continues to exist indefinitely until shut down by the Prime Minister (with Assembly approval).

Like most ideas I float here, I’m not necessarily sold on this myself, but I’d be interested to see how people feel about it.

In my experience, executive responsibilities can be broadly divided into two categories:

  • ministerial portfolios, focused on particular policy areas or term-long projects, and driven by specific agendas each term; and
  • recurring institutional responsibilities, focused on particular infrastructure maintainence, and driven by specific desires for ‘things’ we want to have.

For example, consider a hypothetical cards program. Launching the cards program could fall into the first category, where the agenda consists of getting the program off the ground. Maintaining the cards program could fall into the second category, where the focus is more on maintaining a steady stream of cards (which requires continual upkeep in the form of card farming) as a sort of ‘infrastructure’ for other parts of the government that want to use those cards as rewards.

Because we haven’t sought to differentiate these two categories, we’ve sometimes strayed into bureaucratic bloat without a clear solution to clean it up. For example, with the Ministry of Engagement and the staffer system, we ended up with an expansive staff roster despite having few individuals actively participating; but in the process of trimming things down, we ended up in a situation where just a handful of individuals — Viet, myself, and maybe anjo — are in essence responsible for our dispatches, outside of any executive structure. The pathway from noticing an error in our dispatches to getting it fixed should not be posting about it on Discord, hoping Viet sees the message and pings me, and waiting for me to just fix it myself, without any involvement from the executive. It also should not be sending private messages to people without knowing who can actually edit the dispatch or who’s supposed to sign off on that change. I’m speaking from experience here!

Separating this work out into its own office ‘isolates’ the bureaucracy. An office doesn’t have to do a whole lot, but it allows us to identify the kinds of work that actually need continual upkeep and separate it from the ministerial portfolios of people who want to pursue their agenda, not manage the bureaucracy. For instance, a Minister of Integration could focus on launching their new mentorship program without worrying about how to do dispatch maintenance, and an office could focus on gradually making that dispatch maintenance more approachable without worrying about churn every three months where the Ministry of Integration might not even exist.

We already have one office, the Office of World Assembly Legislation. Arguably, we could just create more offices. But I think we don’t have a culture of doing so, in part because OWL was not created to be a permanent executive institution in contrast to transitive ministries. It was created as a compromise between a full-fledged WA ministry, back when our ministries were fixed, and no ministry at all. It’s just happened to be grandfathered in as a permanent fixture of the executive, and it kind of works because a lot of what OWL does or has done is opening voting threads — the kind of recurring work that I’d argue better fits an office than a ministry.

9 Likes

I think this is an interesting idea that warrants more careful consideration. Governments ministers in TSP don’t really last that long in their positions, so it does make sense for there to be existing bodies to maintain infrastructure in the long-term.

Perhaps one consideration on how to make offices actually distinguishable in practice from ministries is to basically copy the OWL model, which is to legislate the role of the office and establish parameters that effectively mandates any incoming PM to appoint someone to that particular role. For instance, to continue from your Cards example, a “Cards Act” could legislate that the “Director of the Office of Card Farming” is in charge of farming cards, is not allowed to transfer cards away from TSP-owned nations created for the sole purpose of farming cards, etc. (not saying that this is ideal or that I’d endorse a “Cards Act”, this is just by way of example.)

On the other hand, it is fair to think about whether there really needs to be this artificial distinction. A PM (or some other elected minister if we do end up transitioning back to elected ministers) could just as easily appoint a “(Junior) Minister of Cards” to preserve the previous Cabinet’s wildly-successful Cards project. Perhaps the more important issue is that there needs to be mechanisms by which projects from previous administrations are preserved properly. This includes expertise and know-how as well. It is not enough that we create an “Office of Dispatch Infrastructure”, if future PMs only appoint people who haven’t a clue on how to maintain the existing infrastructure.

1 Like

This might be a problem we can solve within an OWL-esque framework, but our WA affairs don’t have a clear separation between term agendas and recurring tasks. The tendency in our current system is to bundle these two separate concerns together into OWL, but I contend that an OWL director who is very good at doing what the law calls for makes for an excellent director, even if they aren’t driven to pursue a political agenda and even if they serve out of a desire to enable others to vote rather than out of their own interest in the World Assembly. Similarly, someone with a passion for resolution writing might make for a fantastic World Assembly minister, but they might not be a great fit for OWL director if they aren’t interested in literally just opening up a bunch of WA voting threads because they want to focus on their vision and agenda rather than repetitive tasks.

This was a problem that fixed ministries overcompensated for to a fault, because our ministries ended up accruing bloat as people didn’t want to cut any projects. The mechanisms have always been there, even in a flexible, appointed Cabinet, but they have not been well exercised, and legislative changes can nudge the executive in the direction of better governance.

Pronoun (or anyone, but since it was Pronoun’s idea originally)–how did you envision this being implemented legislatively? As an entirely new piece of legislation (e.g., a “Civil Service Act” or something similar), as an amendment to the Charter, something else?

I was about to comment that one way to concretize this proposal would be to actually begin drafting some legislative text and see what people think. But then I realized I wasn’t sure exactly where to start with that project. It strikes me that a separate statute would be the cleanest move, perhaps with a cross-referencing amendment to the Executive section of the Charter. But that’s just a preliminary idea. Curious to hear others’ thoughts.

I admit that I’m a little hesitant and I’m worried about whether 1) there would be enough people to head this, since it goes on “indefinitely” and 2) how difficult it would be for the PM to control and manage it.

As for whether or not it is part of the Charter, I honestly don’t know.

As for PM control, I think the PM would be able to remove individuals from offices. So the civil servants might not automatically leave their offices at the end of each term like Cabinet ministers, but a new PM could dismiss them if they wanted someone else in charge / were unsatisfied with the incumbent’s performance. Which is how I believe OWL is currently structured.

Honestly not sure. I think a separate statue cross-referencing Article V of the Charter is fine.

More generally, I think the appointments framework in the Charter is kind of weird. Presumably, it’s not great if the Prime Minister can appoint a minister without Assembly confirmation by just giving them a different title; legally, I’m not sure if tightening that up would require making the ministerial appointments framework the exclusive appointments mechanism. That seems a bit crazy from a policy perspective — the PM can’t get advice from people without making them ministers first? — but I think ideally, other forms of appointments (including OWL director, which a lot of PMs have wanted to include in the Cabinet) shouldn’t feel like ‘bypassing’ the ministerial appointment mechanism. But that’s a bit of a tangent.

I think there are already things we do that are “indefinite” and that not recognizing that reality has detrimental effects. For instance, to use a recent example: if our image hosting has issues, I think it’s kind of inefficient that we have to just, like, post about it on Discord and hope someone with the requisite knowledge sees it? It’s indefinite because it’s nice to know who to ask about where to find our dispatch banner when we need it. It’s not indefinite because they need to be constantly working on new graphics.

Alright. If I get some time (perhaps wishful thinking), I might try to draft something up along those lines.

Agree this is a difficult and interesting question. I’ll have to formulate my thoughts a bit more before responding comprehensively.

I’d like to see this discussion revived, especially in the context of SPROUT making a comeback (perhaps??).

I agree. Perhaps one way to get the ball rolling is to start assembling a list of potential permanent offices. The following have been brought up at various points in this and related discussions:

  • OWL
  • Dispatches
  • Cards
  • SPROUT

Any others?

Should SPROUT also maintain any recruitment API we do?

By that do you mean external recruitment? If so, I would imagine the answer would be yes, given the similar technical skills involved. Although it would make the SPROUT name somewhat less apt.

SWAN? Maybe not.

Good question. @USoVietnam – you maintain both SWAN and the Dispatches currently, correct? Is there a reason those jobs should be kept together, or did you just volunteer for both?

I just volunteer. Dispatch and endorsement program are definitely separate job. Ideally there will be an office/department for each.

That said, if we were to have dedicated offices for these, we may as well as bringing back permanent ministries (with detailed minimum responsbilities defined in laws). A minister may head more than one ministry as PM decides and the PM is free to set up more ministries/offices as needed.

The permanent ministry setup can be as granular as this: Foreign Affairs, Defence, Culture, Roleplay, Information (dispatches, forum posts, public media,…) , Engagement (active recruitment), Card, World Assembly. I do think the Assembly ought to decide the responsibilities of the executive branch more granularly as IRL governments do. The PM has freedom on assgining personnel to run these. One person may run many ministries at once if desired. To this day, I still haven’t seen the benefits of every single cabinet term drawing up new ministry structure from scratch. There should be some sort of bare minimum setup with discretionary additions and personnel assignment.