Chapter 3 — The Person Who Keeps the Spreadsheet

The Person Who Keeps the Spreadsheet

The spreadsheet was supposed to be temporary.

It began during a meeting about revising the university’s undergraduate curriculum. The department had spent months discussing larger questions: what students should know before graduating, which courses had become outdated, whether the program still reflected the field it claimed to teach. Faculty members arrived with annotated proposals and competing philosophies. Some wanted more theory. Others wanted more practical work. Several believed the curriculum already asked too much of students. Nearly everyone agreed that the existing requirements had accumulated rather than been designed.

Then someone asked which proposed courses would satisfy the accreditation standards. The room became quiet. The answer existed, but not in one place.

A requirement appeared in an accreditation document last updated three years earlier. Another depended on how the registrar classified laboratory hours. One proposed course could replace an existing requirement only if the department preserved a particular learning outcome somewhere else. Two adjunct instructors had contracts tied to classes that might disappear. A laboratory needed a new safety review before enrollment could increase. The university catalog deadline was closer than anyone remembered.

An associate professor opened a laptop and began making columns. Course number. Current requirement. Proposed requirement. Accreditation language. Instructor. Contract status. Laboratory approval. Registrar deadline. At first, the spreadsheet was only a way to get through the meeting. Someone said, “Can you send that around afterward?” She did.

Over the next week, people added comments. The department chair asked her to include enrollment history. The registrar’s office corrected several course codes. A colleague forwarded an email about an upcoming accreditation review and asked whether she could add the new criteria. Someone else realized that the proposed sequence would leave transfer students unable to complete the major in two years.

The spreadsheet grew.

It acquired colors whose meanings were understood by people who had never agreed on them. Yellow meant unresolved, except in one section where it meant awaiting confirmation. Red meant impossible, unless the impossibility depended on funding, in which case it meant unlikely. Green meant approved, though sometimes only by the department and not by the college.

The associate professor learned to read the colors because she had created them one problem at a time. Soon, questions began arriving directly.

“Sorry to bother you—quick question.”

“Do you remember whether we decided to keep the old prerequisite?”

“Which version should I be looking at?”

“Did anyone ever hear back from the lab coordinator?”

“Is the catalog deadline the same as the registrar deadline?”

“Can you remind me why this course cannot move to spring?”

Each question was small. Together, they turned one person into the department’s memory. This happens in many collaborations.

A group begins with work everyone can see: the plan, the product, the event, the policy, the patient, the publication. Around that visible work, another kind of work slowly gathers. Someone remembers what was decided. Someone notices when two people are using the same word differently. Someone knows which promise was made to whom, which exception was granted last year, and which apparent shortcut will reopen an argument everyone else has forgotten.

The group may not formally assign this work. It simply begins asking the person who knows.

That person answers because the answer is available. They were in the meeting. They kept the notes. They know whom to call. They remember why the rule exists. They can explain the history in five minutes, while reconstructing it would take everyone else an afternoon.

Each answer saves time. The savings accumulate for the group and as work for the person. This is one of collaboration’s quiet bargains: efficiency often appears because one person absorbs the complexity others no longer have to carry.

From the outside, the arrangement can look natural. Some people are organized. Some people have good memories. Some are generous with context. Some are simply better at seeing how pieces connect.

The department may even say so out loud. She is just like that. She has always kept track. The explanation feels kind, and it ends the inquiry. Natural ability does not explain why the same person keeps receiving the questions. A gift for noticing does not, by itself, create a queue of “quick questions.” Once someone becomes known as the person who remembers, the group begins organizing itself around that fact. People take fewer notes because she took notes. They enter meetings less prepared because she can reconstruct what happened. New members are directed toward her instead of toward documentation that does not yet exist. Decisions remain informal because everyone knows who can explain them later.

The person becomes helpful in ways that make the group more dependent on her helpfulness. This dependence rarely appears on a roadmap.

The curriculum project still has visible tasks. Faculty members draft course descriptions. Committees approve changes. Administrators update catalogs. Those activities produce artifacts that can be counted and presented.

The associate professor’s work appears differently.

She answers the email that prevents two colleagues from proposing incompatible changes. She notices that an accreditation phrase has shifted between versions. She reminds the chair that the department promised an adjunct instructor a course before the schedule is finalized. She explains to a new committee member why an apparently irrational requirement was created after a student could not graduate on time.

None of these actions looks like the project. They are what keep the project from repeatedly forgetting itself.

Every collaboration produces this surrounding work: the work that keeps the visible work possible.¹ A community theater needs actors and lights—and someone who knows that a volunteer’s child must be picked up by nine, that one costume cannot go through the washing machine, and that the landlord complained the last time equipment blocked the rear exit. The same surrounding work appears wherever visible tasks depend on unassigned memory: a software team remembering why an odd safeguard exists, a family tracking which sibling has already been called and what the doctor actually said.

The surrounding work is not separate from collaboration. It is collaboration becoming livable.

Yet it remains difficult to recognize because it often leaves no finished object behind. The person doing it may have no deliverable beyond the absence of confusion.

A question gets answered before it becomes a delay. A conflict is softened before it becomes a rupture. A risk is noticed before it becomes an incident. A newcomer is oriented before they accidentally reopen an old wound. Nothing happens. The meeting proceeds. The deadline holds. The group calls itself efficient. Some of the most important work inside a collaboration is visible only through the failures that do not occur. This creates a problem of recognition.

Organizations tend to reward the work they can point to. A report was published. A feature launched. A grant was secured. A course was created. Someone stood at the front of the room and presented the result.

Maintenance appears less impressive because its evidence is continuity. The schedule still makes sense. The relationship still works. The system still runs. The group still remembers why it made the decision. Continuity rarely announces itself as an achievement. It becomes noticeable only when it disappears. When the associate professor takes leave for a week, the questions do not stop. They scatter.

One colleague asks the department chair, who forwards the email to the registrar. The registrar replies that the answer depends on the version of the proposal. Someone searches the shared drive and finds four spreadsheets with similar names. Another person makes a new copy to avoid altering the wrong one.

By the time the professor returns, the department has created two conflicting schedules and promised the same classroom to different courses. Everyone is relieved to see her. The relief feels like appreciation. It is also evidence of dependency. Groups often learn what someone was carrying only when that person puts it down.

This can happen suddenly, through resignation, illness, retirement, or transfer. More often it happens gradually. The person keeps attending but contributes less. They stop volunteering context that nobody requested. They answer only the question asked, not the question they can see forming behind it. They allow others to discover the consequence of a forgotten decision.

Seen from elsewhere, they appear less engaged. They may be described as tired, territorial, resistant, or no longer collaborative. But withdrawal is sometimes what happens after a person realizes that their reliability has become a resource everyone else consumes without seeing. The group experiences the withdrawal as a change in attitude. The person experiences it as the first boundary anyone has respected. This is especially difficult because the work of remembering is often mixed with care.²

The person who maintains the spreadsheet does not only preserve information. She considers how decisions will land on people who are not in the room. She notices that a change described as minor will eliminate an adjunct instructor’s expected income. She knows which colleague is caring for a sick parent and will struggle with an additional evening course. She understands that transfer students do not experience the curriculum as an elegant sequence but as a maze they are trying to cross before financial aid runs out.

The spreadsheet becomes a map of human consequences disguised as administrative detail.

This is why the person holding context can appear overly cautious. Others see a row, a date, or a dependency. She sees the conversation that created it and the person who will absorb the cost if it is ignored.

She says, “It is more complicated than that.”

The room hears resistance. She is slowing the decision. She is attached to the old way. She cannot let a simple change remain simple. She may also remember more of the complication: the adjunct contract tied to the cell, the transfer student who will lose a year if the sequence shifts, the accreditation phrase that already failed once. The row looks administrative from a distance. Up close it is a map of people who are not in the room. What sounds like obstruction may be the sound of those people becoming briefly visible.

Knowledge of history changes the emotional weight of proposals.

A new leader sees an inefficient process and asks why it cannot be simplified. The person with institutional memory recalls the failure that produced each step. A team proposes consolidating two systems. Someone remembers the clients stranded during the last migration. A volunteer board wants to remove a cumbersome approval. One member remembers that the approval began after money was spent without consent.

The person who remembers can become the defender of things they do not necessarily like. They may want the system replaced. They may have complained about it for years. But because they know what the current structure is preventing, they cannot participate in the fantasy that removing it removes only inconvenience. Memory makes change look slower. For people who do not carry the memory, the caution can feel like attachment to the past. For the person who does, forgetting can feel like making the same people pay twice.

This does not mean institutional memory is always wise. Memory can preserve fear long after conditions have changed. Expertise in history can become authority over the future. The spreadsheet itself can become a form of control. Because the associate professor knows the dependencies, every proposal must pass through her interpretation. What began as service can harden into a gate. This is another reason invisible work is difficult to discuss. Naming it should not place the person who performs it beyond question.³ People sometimes become indispensable because they have quietly prevented knowledge from becoming shared.

But dependency does not become healthy merely because the person carrying it is benevolent. A group that relies on one person to remember the whole has not solved its memory problem. It has given the problem a name and an email address.

The challenge is not to eliminate the person’s contribution. It is to stop treating their capacity as an unlimited public utility.

This requires noticing how unevenly collaborative work moves. The language of teamwork suggests that people contribute side by side. In practice, contribution often travels through bottlenecks. One person holds the relationship with another department. One person understands the legacy system. One person can calm a particular stakeholder. One person knows the history of a client account. Work flows toward them because they can move it. Their effectiveness attracts more work. The most reliable person becomes the system.

People ask for their judgment. Leaders praise their ability to connect the dots. But being central and being supported are not the same. The organization may celebrate their reliability while making no attempt to reduce the conditions that require it. Praise becomes a substitute for capacity. “We could not do this without you” sounds like gratitude and functions like a warning: the group has no plan for doing it without them.

The burden is not distributed evenly. The person expected to take notes is often the person whose ideas are taken least seriously once the discussion begins. The person who notices emotional tension may become responsible for resolving it. The colleague perceived as approachable receives the questions people are embarrassed to ask publicly. The person who speaks more than one organizational language becomes the permanent translator between groups that never learn to speak to one another. These patterns emerge from thousands of small choices.

“Could you take notes? You’re so good at it.”

“Would you check in with her? She seems to trust you.”

“Can you explain this to the business team?”

“Could you onboard the new person?”

Each request is reasonable. The distribution formed by the requests may not be. Collaboration can become extractive without anyone deciding to exploit anyone. No single request justifies refusal. The person can answer the quick question, make the introduction, clean up the document, calm the disagreement, remind everyone of the decision, and stay ten minutes after the meeting to explain what the meeting meant. The cost becomes visible only in accumulation. Invisible labor often arrives disguised as an exception—just this once, until the new process is established—and the temporary condition keeps renewing itself. The spreadsheet remains temporary for three years.

Organizations praise steady people. They do not panic. They do not drop handoffs. They absorb changing priorities and continue producing. Steadiness can be character. It can also be load. A person may appear calm because the system has learned to place instability inside them. The group remains stable because one person repeatedly converts disorder into something others can tolerate. This arrangement works until it does not.

Elasticity is useful because it bends. It is dangerous because everyone begins treating bending as proof that the material has no limit.

When the steady person finally refuses, the refusal seems abrupt only to those who never counted the adjustments that came before it. They say, “I cannot take this on.” The group hears a change in behavior. The person hears the first honest description of capacity. One way to see the hidden structure of collaboration is to watch who is permitted to become overwhelmed.

Some people can announce that they are at capacity and have work removed. Others receive help prioritizing how to continue doing all of it. Some can say, “That is not my responsibility.” Others have built careers around solving whatever falls between official responsibilities.

The gaps between roles do not remain empty. They become someone’s job. Because the work is unofficial, it can be difficult to transfer. A formal responsibility can be documented. An informal responsibility is often a web of timing, trust, memory, and judgment.

The associate professor cannot simply hand someone the spreadsheet. The file contains the data. It does not contain her understanding of the data.

It does not explain why one administrator responds better to a phone call than an email. It does not show which approval is technically required and which can be resolved through conversation. It does not reveal that a red cell represents a firm prohibition while another represents a colleague’s guess.

The spreadsheet is not the memory. It is the visible edge of the memory.

This is why organizations often misunderstand documentation. They imagine knowledge as something that can be removed from a person and placed into a file.

Files help. Decision logs help. Clear ownership helps. Shared notes reduce dependency and allow people to inherit the reasoning behind work they did not witness. But documentation does not remove the need for interpretation. Someone still has to know which detail matters now, which decision remains reversible, and which old explanation no longer fits current conditions. The goal is not to make human memory unnecessary. It is to prevent one person from carrying memory alone.

That requires more than asking the person to write everything down. Writing is additional labor. When the busiest keeper of context is told to document what everyone else relies on, the solution often becomes another demand on the same person. A healthier group treats memory as a shared practice: notes, decision records, and onboarding stop routing through one permanent guide, and redistribution begins before exhaustion becomes the plan.

Most importantly, the group stops treating invisible work as evidence of personality. Calling someone “naturally organized,” or “the person who knows the old system,” turns work into identity. Once the work becomes who someone is, asking others to share it feels almost unnatural, and refusal starts to sound like character failure. The identity conceals the assignment.

Collaboration becomes fairer when people can remain who they are without being required to provide their strongest capacity without limit. This matters not only for the people carrying the work but for the quality of the work itself. Invisible labor contains information. The repeated question reveals where the process is unclear. The recurring conflict reveals where responsibilities overlap. The exhausted maintainer reveals where the system has concentrated dependency. Every “quick question” is a small piece of system feedback. Why does the answer exist only in one person’s memory? The person keeping the spreadsheet is not only supporting the system. They are showing the group where the system does not support itself. That insight changes what appreciation should mean.

Gratitude is good. Credit matters. Maintenance work should appear in performance reviews, project histories, and stories of success. People deserve recognition for contributions that do not produce dramatic artifacts.

But recognition alone can become another way of preserving the arrangement. The department praises the associate professor’s “exceptional collegial service” and assigns her another committee. The manager thanks the team’s most reliable engineer and adds them to the next troubled project.

The praise can settle the matter before anyone asks what it costs. Someone was seen. The debt was named. Everyone can return to work with a clearer conscience. Appreciation without redistribution is often how dependency apologizes for itself. The sentence that sounds like gratitude—“we could not do this without you”—functions as a warning when no one asks what the person should no longer have to carry.

The deeper form of recognition asks what the person should no longer have to carry.

Near the end of the curriculum revision, the department scheduled a final review.

The spreadsheet was projected on the wall. It had grown wider than the screen, requiring everyone to scroll sideways through categories few remembered requesting. Some cells contained notes longer than the course descriptions they explained.

The chair thanked the associate professor for keeping the project organized. Then he asked whether she could continue maintaining the document during implementation.

The request was reasonable. She knew the history. The work was not finished. Handing it to someone else would create risk.

For a moment, the familiar answer gathered in the room. Of course. Just through the transition. Until everyone understood the new curriculum. She looked at the spreadsheet and said, “I think someone else needs to maintain it now.” The room became quiet in the way rooms do when an invisible arrangement becomes visible.

She did not refuse to help. She proposed that the department assign two people to the implementation, document the unresolved decisions, and hold a monthly review that did not depend on her attendance. She would explain the current structure and answer questions during the handoff. She would not remain the permanent destination for every question the curriculum generated.

The transition took longer than anyone hoped.

The two new maintainers found gaps in the documentation. They disagreed about the colors. Several questions still returned to her because no file could contain every conversation that had shaped the work.

But something changed.

Other people began attending to decisions they had previously allowed her to remember. The department discovered that some procedures were confusing because no one had needed to make them clear while one person could explain them. A recurring registrar problem became a formal checklist. The accreditation criteria were linked directly in the document rather than translated through memory.

The spreadsheet became less elegant for a while. The department became slightly more capable of surviving without its author. Months later, a colleague opened the file and noticed that its original title remained at the top: Temporary Curriculum Planning Tracker. He laughed and asked whether they should rename it. For years, the word temporary had described the spreadsheet. It had also described the department’s willingness to notice the work required to maintain it. The file was renamed. The work was named too.

That did not make it equal. It did not distribute memory perfectly or prevent certain people from carrying more than others. Collaboration rarely becomes fair through one decision.

But a question that had always traveled toward one person now had more than one place to go.

Every successful collaboration asks someone to remember what others forget.

The danger begins when everyone forgets to ask who is doing the remembering.

Footnotes

1. See Susan Leigh Star and Anselm Strauss, "Layers of Silence, Arenas of Voice: The Ecology of Visible and Invisible Work," Social Problems 46, no. 3 (1999): 301–24. ↩

2. See Arlie Russell Hochschild, The Managed Heart: Commercialization of Human Feeling (Berkeley: University of California Press, 1983). ↩

3. See Hochschild, The Managed Heart; Star and Strauss, "Layers of Silence, Arenas of Voice." ↩