The Soft Sag of Shared Responsibility

The Soft Sag of Shared Responsibility

When everyone owns the risk, the project owns you. Navigating the paralysis of modern corporate collaboration.

The cursor on the Smartsheet is blinking at 12:03 AM, a rhythmic, taunting pulse that feels less like a software feature and more like a migraine in the making. I am staring at a cell labeled “Final Approval” that has remained uncolored for 13 days, while the song ‘Everybody Wants to Rule the World’ loops in my head for the 43rd time today. It is a peculiar kind of torture. The bassline is driving, but the lyrics about nothing ever lasting forever feel like a personal attack on this project timeline. Somewhere in the digital ether, 3 separate teams are convinced that one of the other 2 has already checked the load-bearing capacity of the new spring assembly.

I am Marcus S.-J., and for the last 13 years, I have made a living by lying down. I am a mattress firmness tester. It sounds like a joke you would hear at a sticktail party, but the physics of foam density and the precise indentation load deflection of a latex core are matters of high-stakes engineering. If I misjudge the ‘push-back’ of a hybrid pillow-top, 103 people might wake up with lumbar stiffness that ruins their week. But tonight, the stiffness isn’t in a mattress; it is in the process.

We have entered the era of the ‘Venn diagram of despair.’

This is a corporate state where cross-functional collaboration has been weaponized into a sophisticated method for manufacturing ambiguity.

We are told that shared ownership is the gold standard of modern management. It sounds generous. It sounds democratic. It sounds like a way to ensure no stone is left unturned. In reality, shared ownership is often just a fancy way of saying that 33 stakeholders are currently watching a ball roll toward a cliff, each assuming that someone else has the specialized gloves required to catch it.

The Distribution of Assumed Work

Team A (Approval)

80% Assumed

Team B (Materials)

35% Assumed

Team C (Logistics)

10% Assumed

I remember a specific mistake I made back when I was still learning the nuances of memory foam recovery times. We were launching the ‘Zenith-13’ line. I saw the testing data for the fire-retardant layer and assumed the Materials Team had validated the breathability. The Materials Team saw my signature on the firmness profile and assumed I had cross-referenced the airflow metrics. The Logistics Team saw both our names in the ‘Updated’ column and moved the 43 prototypes to the showroom.

When everyone owns the risk, the risk owns the project.

It turned out the mattresses were essentially heat-trapping blocks of cured resin. They felt like sleeping on a heated sidewalk in the middle of a July afternoon in Phoenix. We lost $733 in shipping costs alone before we realized that ‘shared ownership’ had actually meant ‘shared blindness.’ It is a classic case of the bystander effect, scaled up to the size of a corporate quarterly report. When you are standing in a crowd and see someone in trouble, you are statistically less likely to help because you assume someone more qualified will step in. In business, this translates to 13 people on a CC chain all assuming that the person in the ‘To’ field is the one doing the actual work.

๐Ÿ›‘

Singular Expert

Clarity: Blame is centralized.

VERSUS

๐Ÿ”„

Dashboard Loop

Ambiguity: Blame is diluted.

This fetish for collective ownership has become a way of avoiding the simpler, older, and admittedly scarier discipline of naming responsibility out loud. We have traded the ‘Buck Stops Here’ desk plaque for a collaborative dashboard where the buck just circles around in a holding pattern until it eventually runs out of fuel and crashes into the sea of forgotten tasks. I find myself missing the days of the singular, grumpy expert. The person who said, “This is mine, and if it breaks, you can come to my office and yell at me.” There is a profound comfort in knowing exactly who to blame. It creates a clarity that no ‘Alignment Sync’ can ever replicate.

The Cost of Safety: Momentum Loss

I’ve spent 53 hours this month in meetings where the primary goal was to ‘socialize’ a decision. Socializing a decision is corporate speak for diluting the blame in case the decision turns out to be a disaster. If 233 people agree that a blue logo is better than a red one, and the blue logo causes sales to plummet by 13 percent, nobody has to pack their bags. We all agreed! We had a workshop! We used post-it notes!

But the cost of this safety is a total loss of momentum. It takes 63 days to decide on a typeface because the brand team, the legal team, and the ‘Customer Happiness’ team all need to weigh in on whether the letter ‘g’ looks too aggressive. This is why small, nimble companies eventually turn into slow-moving glaciers. They stop being driven by individuals with a vision and start being steered by committees with a fear of being singled out.

Mapping Invisible Authority

There is a specific kind of exhaustion that comes from navigating this ambiguity. It’s not the physical fatigue I feel after testing 33 mattresses in a single afternoon-that’s just muscle soreness. It’s a cognitive drain. You are constantly trying to map the invisible lines of authority. You ask yourself: Does Sarah have the final say on the spring count, or is that a ‘collaborative input’ from the design department? Can I move forward with the foam pour, or do I need a ‘nod’ from the sustainability committee?

The Home Sale Analogy (The Need for SPOF)

I’ve found that this confusion often bleeds into the most stressful moments of our lives outside of the office. Take, for instance, the process of selling a home. It is traditionally a nightmare of shared ownership. You have the agent, the inspector, the buyer’s lawyer, the bank, and the local council, all pointing fingers at each other when the closing date slides for the 13th time.

In those moments, you don’t want a ‘collaborative experience.’ You want a single point of contact who takes the burden off your shoulders entirely. This is why people look for a service like we buy mobile homes when they are tired of the runaround. They want a direct, singular transaction where the responsibility is clear and the action is immediate. They want the ‘SPOF’-the Single Point of Failure-to be a person they can actually talk to, rather than a nebulous group of ‘interested parties.’

[The absence of a clear ‘no’ is not a ‘yes’.]

I once spent 83 minutes explaining to a junior project manager why we couldn’t just ‘crowdsource’ the firmness rating of our orthopedic line. He thought it would be ‘inclusive’ to let the marketing team vote on how a mattress should feel. I had to explain that a marketing manager’s opinion on spinal alignment is about as useful as my opinion on the intricacies of tax law in the Cayman Islands. Inclusion is great for a potluck dinner; it is a catastrophe for technical specifications.

Rediscovering the Beauty of the Boundary

We need to rediscover the beauty of the boundary. A boundary isn’t a wall that prevents collaboration; it’s a fence that tells you where your garden ends and your neighbor’s begins. It allows you to focus. If I know that my only job is to ensure the top 3 inches of foam have a recovery time of exactly 3 seconds, I can do that job with a level of precision that is impossible if I’m also worried about the supply chain for the ticking fabric or the social media strategy for the launch.

Focus vs. Diffusion Metrics

๐ŸŽฏ

Precision

Single Ownership Focus

๐ŸŒช๏ธ

Inertia

Group Consensus Cost

I’ve seen projects where the ‘owner’ was a group of 3 directors. Those projects are the ones that always end up 13 percent over budget and 3 months late. Why? Because when three people are in charge, the amount of time spent on internal communication exceeds the amount of time spent on actual production. They have to have meetings to prepare for the meetings where they will update each other on what they haven’t done yet because they were too busy in meetings. It’s a recursive loop of inactivity.

The 3:33 AM Decision

I remember another time-this was about 93 days into the development of a cooling gel pad-where I decided to just stop waiting. I had been waiting for the ‘Chemical Safety Board’ and the ‘Thermal Dynamics Unit’ to give me the green light on a specific prototype. The song was stuck in my head then, too. ‘Welcome to your life… there’s no turning back…’ I realized that the ambiguity was a choice. I could either wait for a consensus that would never come, or I could take the ‘firmness’ of my job title literally.

I signed the paperwork, took the 43 prototypes to the test floor, and stayed there until 3:33 AM checking the temperature gradients myself. I made a mistake in the calibration of the third unit-I forgot that the ambient room temperature was 3 degrees higher than the lab standard-but at least it was *my* mistake. The relief of taking that responsibility was immense.

Accountability is the only cure for corporate insomnia.

The Choice of Ambiguity

We pretend that ambiguity is a byproduct of complexity, but it’s actually a choice. It’s a defensive crouch. If we can keep the lines of ownership blurry enough, we can never truly be at fault when things go sideways. But we also never get the satisfaction of saying, “I built this, and it works.” We become cogs in a machine that is designed to distribute credit so thinly that it has no flavor and distribute blame so widely that it has no weight.

1%

The Owner’s Contribution

99%

The Consensus Group

As I sit here, finally deciding to hit the ‘Approve’ button on this Smartsheet cell regardless of who else has weighed in, the song in my head finally shifts. The bassline fades, and I’m left with the quiet of the office at 1:03 AM. I am Marcus S.-J., and I am the one who says this mattress is ready. If people wake up with sore backs, they can find me. I’ll be the one sleeping soundly, knowing exactly where my responsibility ends and the rest of the world begins.

Is it better to be part of a safe, anonymous consensus that fails slowly, or a lone voice that risks failing loudly?

In a world obsessed with ‘synergy,’ the most radical thing you can do is stand up and say, “I’ve got this.”

Does anyone actually know who owns the final 3 percent of your most important project right now? Or is everyone just waiting for the cursor to stop blinking?

Reflection on modern process dependency.