Every Workflow Is a Curriculum

When we think about curriculum, we usually think about courses, learning outcomes, assignments, and the intentional experiences faculty create for students.

But students are learning from more than the formal curriculum. They are also learning from every system, process, policy, form, message, and interaction they encounter while navigating the institution.

Those operational experiences form an invisible curriculum. They teach students how the institution works, what it expects from them, and whether they can trust it to help them succeed.

Every workflow teaches. The only question is whether it teaches the lesson we intended.

Processes communicate institutional values.

An institution may say it values access while requiring students to navigate a complicated process to receive support.

It may say it values belonging while communicating primarily through impersonal warnings and administrative notices.

It may say it values student success while requiring students to coordinate information between offices that do not communicate with one another.

None of these experiences may have been designed to send a negative message. They may be the product of systems that evolved over time, policies created in response to isolated problems, or technology configured around departmental needs.

Intent, however, does not erase impact.

The hidden curriculum begins with small interactions.

Consider what students may learn from common institutional experiences:

• A form that asks for information the institution already has teaches students that systems are not connected.
• A process with no visible status teaches students that they must follow up repeatedly to receive an answer.
• Contradictory instructions teach students that official information may not be reliable.
• A policy written entirely around exceptions and penalties teaches students that the institution anticipates noncompliance.
• A successful outcome that depends on finding the right employee teaches students that navigation matters as much as eligibility.

These lessons influence behavior. Students begin to create screenshots, save every email, seek informal advice, contact multiple offices, or avoid asking for help altogether.

In other words, students adapt to the curriculum we have created.

Workflows are rarely neutral.

A workflow is a sequence of decisions about who does what, when they do it, what information they need, which system they use, and what happens next.

Each decision distributes time, effort, risk, and responsibility. When a workflow is poorly designed, those burdens do not disappear. They move to someone else.

Often, they move to students or frontline employees.

A department may reduce its administrative work by requiring students to complete additional steps. A system may make reporting easier while making the student-facing process more difficult. A policy may reduce institutional risk while increasing uncertainty for the people navigating it.

Evaluating a workflow therefore requires more than asking whether it functions. We must ask how it distributes work and what experience that distribution creates.

Heroics can hide poor design.

Higher education is filled with people who care deeply and regularly go beyond their formal responsibilities to help students.

That commitment is one of the sector’s greatest strengths. It can also prevent institutions from seeing how much their systems depend on invisible labor.

Employees maintain spreadsheets, remember exceptions, follow up manually, translate policies, and personally guide students through disconnected processes.

When outcomes depend on these interventions, the institution may appear more functional than its systems actually are. The workflow succeeds because someone rescues it.

Heroic effort should be celebrated. It should not be the operating model.

Operational design is student experience design.

Student experience is often treated as a layer placed on top of institutional operations. We focus on service, communication, engagement, and the quality of individual interactions.

Those things matter, but they cannot compensate indefinitely for a process that is fundamentally difficult to navigate.

A warm employee can help a student complete a confusing process. Better communication can make a complicated policy easier to understand. A chatbot can help students locate the correct form.

But the process, policy, and form still shape the experience.

Improving student experience therefore requires operational design: examining workflows, responsibilities, technology, handoffs, policies, and information as connected components of the experience.

Design the lesson intentionally.

Imagine a workflow that teaches students that information will be clear, progress will be visible, help will be available, and mistakes can be corrected.

Imagine processes that teach employees that collaboration is expected, information should move across boundaries, and solving the whole problem matters more than completing one departmental task.

These lessons cannot be communicated through slogans alone. They must be reinforced through the daily experience of interacting with the institution.

Every workflow is already teaching. The opportunity is to become intentional about the curriculum we are creating.