11 minutes
Power, privilege and the weight of a routine decision Public authority is rarely exercised as a dramatic decision. It sits in a definition, a deadline, a required channel and an agenda — and its effect is often different from its intent.
What you’ll be able to do Identify the authority carried by a routine decision in your own work and describe its likely effect separately from its intent. Compare the responses to this question and explain your choice: Which response best uses the authority the team actually holds? Document a next step for Power, privilege and the weight of a routine decision: Name one decision on your desk this month and write down who is in the room when it is made, and who is not. Where the authority actually sits Ask most staff in a state division whether they hold power and the honest answer is no. The commissioner holds power. The legislature holds power. A program consultant writing a field guidance note, a contract manager choosing a submission method, a supervisor setting a response standard — those feel like ordinary work. They are ordinary work, and they are also the points where public authority meets a person's life.
Authority in this setting is quiet and cumulative. It shows up as the definition that decides who is included in a category, the deadline that decides whose week is long enough, the required channel that decides who can reach you, and the agenda that decides which questions get air. None of these announce themselves. All of them travel outward, through counties, providers, contracts and notices, to people who cannot see where the decision was made and have no practical way to ask about it.
Privilege, in this work, is not an accusation and it is not about anyone's character. It is the simple fact that a process feels normal to the people it was built around. If the phone line's hours have never been a problem for you, the hours are invisible. If you have never needed an interpreter for a formal meeting, the scheduling rule for interpreters is invisible. This is why intent and effect have to be held apart: a decision made carefully, by people acting in good faith, can still land as a closed door — and the effect is the only part the person on the other side experiences. Naming the effect is not an accusation about the intent, and a colleague who hears it as one deserves the clarification rather than the argument.
Four kinds of authority staff carry without noticing Definition Timing Channel Agenda
The power to decide what a word means in practice: who counts as a caregiver, what counts as a documented need, when a household is one household. Definitions travel further than any memo and are rarely revisited once they are in a form.
The power to set the window: how long someone has to respond, how much notice a meeting gets, how quickly a decision closes. Timing decides who is able to participate more often than eligibility rules do.
The power to decide how someone must reach us: an online portal, a mailed form, a phone line with set hours, a signature in person. Each channel is easy for someone and closed to someone else, and a single required channel is the most common quiet exclusion in public work.
The power to decide which questions are discussed, in what order, and who speaks. A workgroup that hears from the people affected in the final ten minutes has already made its decisions, whatever the meeting record says.
Signs a routine decision is carrying more weight than it looks It will be copied. Field guidance, templates and standard language get reused for years by people who never see the original reasoning.
It sets a default rather than a maximum. Most people will take the default, so the default is the policy.
It decides who has to ask. Any step that works only when a person requests an exception will reach only the people who know exceptions exist.
It is easiest for people whose work and week look like the team's. That is a signal worth checking, not evidence of bad faith.
Nobody in the room will personally meet the process from the outside. That is the moment to bring someone in, with their time paid for.
Separate the requirement from the habit What you can change You control whether your team can say, for each step, where the requirement is written. That single question separates law and policy from things we have simply always done.
What to watch for Do not defend an inherited step as though it were a legal obligation. It costs the team credibility, and it protects a practice nobody chose.
Your next step Take one process your team owns, list its steps, and mark each one as required by law or policy, required by a system we use, or inherited. Start the next conversation with the inherited ones.
Private reflection, for you alone — nothing here is collected and nobody will ask you to share it. How might my role, authority, language or assumptions shape the decision in front of me? Who could be helped, burdened, excluded or misunderstood by this process? Whose expertise is missing from the room, and what would it take to bring it in earlier?
Carry this forward Staff in a state division hold four kinds of everyday authority: the power to define, to set timing, to require a channel, and to set an agenda. None of them feels like power while you are using it.
Privilege, in this work, is simply the ability not to notice. A process feels normal to the people it was built around, and the people it was not built around are the only ones who can see it clearly.
Intent and effect are separate questions. A decision made carefully and in good faith can still exclude, and only the effect reaches the person on the other side.
Calling in means naming the effect, keeping the colleague, and asking what the process will do differently — rather than assigning a motive to anyone.
A scenario about a contract requirement set without the organizations it binds, a look at four kinds of routine authority, and a knowledge check on separating intent from effect.
Name one decision on your desk this month and write down who is in the room when it is made, and who is not.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
