A plumb bob is a heavy, pointed brass weight suspended from a string. It is the most honest tool on a construction site. It does not negotiate with the wind, and it does not recognize the authority of a project manager’s timeline. It only recognizes gravity.
When you hang it against a rising wall of brick, the string creates a perfect vertical line-a reference point that dictates whether the structure will stand for a century or collapse under its own weight within a decade. It represents the objective truth of physics, a reality that exists independently of the blueprints rolled out on the foreman’s desk.
The Theology of the Diagram
The reorganization of a company is a theology of the diagram. It is the belief that by rearranging the boxes on a digital canvas, one can optimize the output of the human beings those boxes represent. It is a ritual of geometric displacement.
It assumes that proximity is accidental, that reporting lines are the primary conduits of value, and that the informal “glue” between people is a redundant expense rather than a structural necessity. In most modern businesses, the website is the victim of this theology.
The Trio and the Table
Consider the trio: a designer named Sarah, a developer named Mark, and a copywriter named Jen. For , they sat within of each other. They did not have a “workflow” in the sense that a consultant would define it. They had a conversation.
Sarah: “The button is below the fold.”
Mark: “Tweaked the CSS in three lines.”
Jen: “Heading is four words shorter. Fixed.”
When Sarah noticed that the hero image on the homepage was pushing the call-to-action button below the fold on smaller screens, she didn’t open a ticket. She turned her chair. Mark looked at her screen, tweaked three lines of CSS, and Jen adjusted the headline to be four words shorter so the rhythm of the page remained intact.
This is emergent collaboration. It is the friction between stones that creates a stable wall. It is the reason the site felt like a single, coherent thought rather than a collection of disparate features.
Then came the reorg. The consultants arrived with their charts and their talk of “cross-functional scalability.” Sarah was moved to the Brand Experience squad, reporting to a Director in New York. Mark was moved to Core Engineering, where his performance was measured by “velocity” on a Jira board. Jen was moved to the Content Strategy team under Marketing.
On paper: 27% increase in “Efficiency” metrics.
On paper, the company became more “efficient.” In reality, the website began to die.
I sent an email this morning to a client without the attachment they actually needed. It was a simple mistake, the kind of slip that happens when your brain is trying to solve a puzzle that no longer has all its pieces. I was thinking about Sarah, Mark, and Jen, and how their homepage hasn’t been meaningfully improved in .
The 164-Day Drift
The hero image is still there, but now the headline is too long because Jen’s new manager wants more keywords. The button is still below the fold because Mark’s new manager says a CSS tweak isn’t a “sprint priority.” Sarah sees the mess every day, but she no longer has the authority to turn her chair and fix it. She has to submit a request to a department she no longer belongs to.
It treats the website as a product that can be manufactured in stages, rather than a living system that requires constant, holistic calibration.
Miles M.-C., a historic building mason who has spent the better part of restoring the limestone facades of Philadelphia, once explained the “lime cycle” to me. He told me that you cannot simply slap new mortar into an old wall. If the mortar is harder than the stone, the stone will eventually shatter.
“The wall isn’t held up by the stones. It’s held up by the relationship between the stones. If you change the mortar mix mid-wall because some guy in an office found a cheaper bag of lime, you aren’t saving money. You’re just scheduling a collapse.”
– Miles M.-C., Historic Mason
“The mortar must be ‘sacrificial’-it must be softer, more breathable, and perfectly matched to the specific chemistry of the masonry it holds together,” Miles said, leaning against a stack of reclaimed granite.
Changing the Mortar Mid-Wall
In the digital world, the “mortar” is the informal, unmapped rapport between the people who build the site. When you break that rapport in the name of organizational clarity, you are changing the mortar mix mid-wall. The site starts to crack.
You see it in the of unnecessary latency caused by a bloated tracking script that no one had the heart to argue against. You see it in the “Contact Us” form that hasn’t worked correctly on mobile for because the developer who understands the API is currently stuck in a “alignment meeting” about a different product entirely.
This decay is quiet. It doesn’t happen with a bang; it happens with a slow accumulation of “not my job.”
To achieve this, one must reject the template-driven mindset that views a site as a series of interchangeable blocks. A
is the result of people who understand that the typography must speak to the code, and the code must serve the conversion goal, and the conversion goal must be rooted in the actual psychology of the visitor.
You cannot achieve this when the designer, the developer, and the copywriter are speaking through the muffled glass of three different departments. When the team is scattered, the site becomes a graveyard of good intentions.
The homepage becomes a “stakeholder buffet” where every department head gets to add a banner or a pop-up, because there is no longer a small, empowered group of people to say “no.” Coherence requires a certain level of healthy insubordination-the kind of insubordination that only happens when three people trust each other more than they trust the org chart.
Shadow Architecture & The Grid
We are currently obsessed with the “rational” structure of business. We want everything to be measurable, repeatable, and scalable. But the most valuable things in a creative enterprise-intuition, timing, and the ability to spot a 14-pixel misalignment at a glance-are notoriously difficult to scale.
Rationality is the imposition of a grid on a garden.
The grid makes it easier to count the plants, but it often kills the soil.
A website “managed” by a committee will eventually alienate its audience.
They are the result of the “shadow architecture,” the unofficial network of friendships and shared history that actually gets the work done.
The core frustration of the modern reorg is that it solves for the manager’s comfort rather than the customer’s experience. The manager wants a clean chart. The customer wants a site that doesn’t make them feel like they are being shouted at by twelve different departments at once.
When you dissolve the team that kept the site coherent, you are essentially telling the customer that your internal hierarchy is more important than their journey.
I look at the plumb bob again. It doesn’t care about the reorg. If the wall is leaning, the string will show it. The data on your website’s bounce rate is your plumb bob. If your conversion rate has dropped by since you moved your “web squad” into separate silos, the string is telling you the truth. Your wall is leaning.
You can try to patch the cracks with more meetings. You can hire more project managers to “coordinate” the now-separated Sarah, Mark, and Jen. You can even buy a new AI-driven project management tool that promises to bridge the gap between departments. But you are just adding weight to a structure that is already failing.
The solution is usually to stop trying to be so “efficient” and start being more integrated. It means recognizing that a small, cohesive unit that understands the business model from top to bottom is worth more than a hundred specialized workers who only see their own slice of the pie. It means protecting the “glue.”
The Principle of Integration
717 Design operates on this principle of integration. There is no “hand-off” from a designer to a developer in a way that loses the soul of the project. There is no template that forces the business to fit into a pre-made box.
There is only the realization that for a website to convert, it must be a single, unbroken thought. It must be built by people who are allowed to sit in the same room-physically or metaphorically-and care about the same .
Returning the Chairs
The reorg is a temporary victory for the spreadsheet, but a long-term defeat for the brand. If you want to fix the website, you don’t need a new strategy. You need to give Sarah, Mark, and Jen their chairs back.
You need to let them sit together and ignore the “velocity” metrics for a week while they remind the homepage what it was supposed to be before it was carved into pieces.
I eventually sent the PDF to my client. I apologized for the oversight. They were understanding, but the mistake bothered me because I knew why it happened. I was out of sync. I was working in a way that prioritized the “process” of sending the email over the “outcome” of providing the value.
That is the same trap companies fall into during a reorg. They prioritize the process of the organization over the outcome of the work.
In the end, the plumb bob always wins. Gravity is patient. The market is patient. Eventually, the structures that were built for the chart rather than the truth will come down. The only question is how much you’re willing to lose before you decide to build it right.