58% of your team's week is spent on work about work. Here's what's eating it.

Asana's Anatomy of Work Index surveyed 9,615 knowledge workers across 6 countries. The finding that should have broken the internet: 58% of the workday is spent on "work about work." That means searching for information, switching between apps, chasing approvals, updating status, and reconciling conflicting documents.

58%. Most marketers get about 42% of their paid hours back for the actual job they were hired to do.

The number keeps getting worse. Gartner's 2025 knowledge worker survey put the average time spent searching for information at 1.8 hours per day, up from 1.2 hours in 2018. The cause is fragmentation.

Your brand guide lives in Google Docs. Your campaign calendar lives in Airtable. Your voice rules live in a Slack pin.

Your performance data lives in Looker. Your decision history lives in nobody's head.

Every one of those is a separate store of state. When two of them disagree, and they always eventually disagree, you've invented a new task that didn't exist before: reconciliation. Someone has to figure out which version is current.

That's the tax. It never shows up in any budget line, and it eats 10 to 15 hours per week per marketer.

Most teams try to fix this by buying another tool. Notion to "bring it all together." Monday.com to "unify workflows."

Three months in, they have a 7th place where state lives and a new question: is this page current?

Teams that actually solve the problem pick a discipline instead of a tool. Single source of truth. One canonical location per decision.

Everything else points to that location. When something changes, the canonical file changes first and everything downstream updates from it.

Software engineers solved this 20 years ago. They call it version control. You change the file, the change is tracked with a timestamp, an author, and a reason.

Every downstream tool reads from that file. The "is this current" question disappears because there's only one version of current.

Marketing operations teams have the same problem engineers had in 2005. Most of them haven't caught up yet.

Run this in a single 30-minute session with your team leads. The goal is to find every place where state lives in 2+ locations and start consolidating.

Step 1: List recurring decisions (8 min). Go through the operational questions your team asks every week: brand voice rules, approval workflows, target audience definitions, budget thresholds, escalation paths, posting cadence, naming conventions. Aim for 10 to 20 items. If you need examples to prime the pump, start with "what do we do when a lead scores over 80."

Step 2: Map current storage (6 min). For each decision, write down every place the answer currently lives. If you find 2+ locations for a single decision, flag those as conflict zones. Most teams find that 60 to 80% of their decisions have multiple storage locations.

Step 3: Score ambiguity cost (6 min). For each conflict, estimate how often the team hits it per week and how much time it wastes per hit (typically 2 to 15 minutes). Multiply to get a weekly cost. Prioritize anything scoring above 30 minutes per week.

Step 4: Pick a canonical location (5 min). For each priority conflict, pick one place as the canonical source. Every other location becomes a pointer to it: "The rules are in this file. Everywhere else is stale."

Step 5: Make updates one-way (5 min). Commit to a rule that whenever the canonical file changes, the change gets announced to the team and every pointer gets updated the same day. If a pointer gets out of date, it gets deleted instead of corrected.

One media team ran this audit and found 14 hours a week of reconciliation work sitting in 6 conflict zones. Three months later, after collapsing 4 of them into canonical files, they measured the change: 9 hours a week recovered per marketer. The other 2 zones took longer because they involved cross-team ownership disputes.

This week I published the full case for Git as a second brain for solo creators and operators. The post walks through what Git actually does for non-developers (no coding required), tours the Professor Leads repo as a working example with every file and folder accounted for, and lays out a 5-step plan to start your own version-controlled operation in 30 minutes. It also answers the 4 questions every non-developer asks first.

Full breakdown here: professorleads.com/blog/second-brain-on-git

All Shorts this week. Five clips, one theme: why your second brain should run on version control.

"The 60-Second Deploy" shows a rule change hitting the live site in under a minute. "The Decision Log" makes the case for writing down every strategic call on the day you make it.

"The Markdown Briefing" covers how AI agents read the same single file across every session. "The JSON Calendar" walks through the pipeline page that is itself automated. "The Free Tool" lands the argument that developers have been sitting on the solution for 20 years.

The whole pipeline that runs this operation is live and visible: https://professorleads.com/resources/content-pipeline

Asana's Anatomy of Work Index. The study behind the 58% number I opened with. Asana's own press release puts the upside in concrete numbers: knowledge workers estimate that improved processes could save them 4.9 hours a week, which adds up to more than six working weeks a year per person. That's the size of the prize for a team that gets single-source-of-truth discipline right. Worth 15 minutes to skim the executive summary. Read it: https://asana.com/resources/anatomy-of-work

Maggie Appleton on digital gardens. Appleton is a designer and anthropologist who writes about personal knowledge systems for individual operators. Her long-running piece "A Brief History and Ethos of the Digital Garden" contrasts blog-style writing (carefully crafted, edited, revised, published with a timestamp, and then considered done) with garden-style writing (continuously growing, with no final version, always open to revision and expansion). The frame maps almost perfectly onto version-controlled thinking: every note is a commit, every edit is a revision, the garden is the repo. This is the best 15 minutes you'll spend on how to think about your own second brain. Read it: https://maggieappleton.com/garden-history

Gartner on the marketing-tool paradox. Gartner's 2023 Marketing Technology Survey found that marketing teams are using just 33% of their martech stack's capability, down from 42% in 2022 and 58% in 2020. During the same window, martech spending climbed 35% from $15.3 billion to $23.6 billion globally. That's the shape of the problem every VP of Demand Gen is quietly living with: the reconciliation tax between the tools is the real bottleneck, and every new tool adds another line to the tax bill. Read the full breakdown on MarTech.org: https://martech.org/marketers-are-only-using-one-third-of-their-stacks-capability/

GitHub's ReadME Project profile of Caleb Porzio. Porzio left his day job in 2019 to work on open source full-time, and he now earns more than $100K a year through GitHub Sponsors by maintaining two popular JavaScript frameworks (Livewire and Alpine.js). The whole operation lives in Git: code, docs, release notes, sponsor benefits, and changelog, all version controlled, with no CRM or project management tool on top. It's the cleanest example I've seen of what a single-repo operator actually looks like in practice. Read the profile: https://github.com/readme/stories/caleb-porzio

Pick the one decision your team asks you about most often. Brand voice, an objection response, the rule for when a lead gets flagged for sales, a budget threshold, anything. Write the canonical answer in a single file.

Tell the team this file is the only place that answer lives, and everything else is stale until proven otherwise. Takes 20 minutes. The first week in, you'll notice 3 to 5 people pinging the file instead of asking you, and you'll realize how much time that one question was quietly eating.

William DeCourcy
Professor Leads
Forbes Business Development Council contributor