Dustin Moskovitz – Eliminating Work About Work – [Founder’s Field Guide, EP. 19]
What this covers
This Founder's Field Guide episode has Patrick interviewing Dustin Moskovitz, co-founder and CEO of Asana, who started the company four years after co-founding Facebook. It opens on how to tell hard, purposeful work from the kind that leads to burnout, then covers Asana's origins and how a founder's job grows more abstract with scale, until at the top it is nearly all work about work. It also covers what Moskovitz carried over from Facebook, chiefly leverage: stack-ranking the roadmap by effort against customer value.
The middle of the conversation is practical. Moskovitz says sprints can last three or four weeks but must be repaid with a week or two of lower productivity. He says Asana's no-weekends norm works because senior leaders model restraint. He argues that culture should be defined in a company's first weeks, or it becomes path dependent. He also describes the Pyramid of Clarity, from mission down to tasks, and why Asana began at the bottom. Other topics include the container model versus the work graph, Asana's merge-sorted customer-feedback leaderboard, and treating disagreements as differences in assumptions. His account of where Asana's AI is headed is a navigation system over the work graph, and ultimately a Spotify-style queue of tasks.
The last third turns to philanthropy. Moskovitz describes how he and his wife approached giving like an investment portfolio, found GiveWell and effective altruism, and funded pandemic preparedness about four years before COVID. The contested turns include factory-farm welfare, even at heavily discounted moral weight, and his view that AI misuse by autocratic governments is a nearer danger than runaway machines.
Moskovitz argues that hours worked yield diminishing and then negative returns, so companies should maximize output by eliminating 'work about work' through shared clarity and a work-graph data model rather than siloed container-based task tools.
- Beyond roughly 50-60 hours per week, added hours can reduce total output, and burnout degrades teamwork.
- About 60% of knowledge worker time goes to 'work about work' (communication about work), per Asana's 13,000-person survey.
- Shared clarity from the top of the mission down to tasks, plus a work graph where tasks live in many contexts, removes the status drift that creates coordination overhead.
This asset isn't compiled yet
You're seeing its claims, ranked. Compile it to build the argument threads, weight them, and check each claim against your library — the full view.
Stating goals and metrics upfront creates falsifiable claims, and A/B tests help teams avoid ex post rationalization where a project is justified by vague benefits after failing its original metric, though tests can produce false positives and negatives.
“you end up with a set of falsifiable claims, especially if you have a strong testing framework”
Even if farm animals like chickens and cows have only a tiny fraction, such as one ten-thousandth or one millionth, of human moral worth, the marginal opportunities in factory-farm welfare, such as cage-free egg sourcing and dairy standards, are so cost-effective that the area is an important target for philanthropy.
“if you think they're even worth a very small fraction, one-ten-thousandth or one-one millionth even, the opportunities on the margin are so effective”
High-leverage philanthropy targets causes that are important, neglected, and cost-effective on the margin, because the marginal dollar in an underfunded area yields the highest return.
“So they're looking for things that are important and they're neglected and then they're cost-effective”
Moskovitz and his wife began philanthropy cause-agnostic, treating giving like an investment portfolio to maximize ROI, and found effective altruism via GiveWell's approach of choosing causes that are important, neglected, and cost-effective at the margin.
“they're looking for things that are important and they're neglected and then they're cost-effective”
Open Philanthropy began funding pandemics and biosecurity about four years before COVID, because COVID-19 was among the easiest disasters to predict and the area was neglected, and earlier investment in at-home rapid diagnostics would have been transformative.
“we actually started four years ago working on pandemics and biosecurity. I wish that we had started even earlier”
According to Asana's 13,000-person yearly Anatomy of Work survey, knowledge workers report spending about 60% of their time on 'work about work', such as long email threads, status meetings, and communicating about work rather than creating output.
“knowledge workers say they're spending 60% of their time on what we call 'work about work'”
Past roughly 50 or 60 hours per week, productivity gains diminish and can turn negative quickly, so that extra hours make all hours less productive and the total output falls below what less work would have produced.
“not only do you get diminishing returns as you go beyond, call it 50 or 60 hours per week, you can actually get to negative returns quite quickly”
The nearer-term AI danger is misuse by actors such as autocratic governments, using AI for surveillance, speech suppression, and autonomous weapons, rather than accidents like runaway paperclip machines or Skynet, which Moskovitz thinks matter less.
“it's less what concerns me, and more the misuse, especially in the near term, because you don't actually need Skynet level intelligence to do very bad things”
Because philanthropic dollars are concentrated domestically in the US while the need for global poverty and health is much greater abroad, moving a dollar out of the US makes it immediately more leveraged.
“As soon as you take one of those dollars and you move it out of the U.S., it's immediately more leveraged because the need is so much greater outside of the U.S.”
Asana's pyramid of clarity runs from mission down through strategy, objectives, portfolios, projects, and tasks; Asana started building at the bottom because most work about work is exchanging status information, which projects and tasks address first.
“So we really started at the bottom there with projects and tasks, because I think that most of that 'work about work' is really exchanging status information”
As a company grows, a founder's role becomes more abstract, focused on clarity about why and what through talking to employees, customers, and investors, so that at the top the job becomes nearly all work about work, which is leveraged only if it reduces others' coordination load.
“the higher you go up the corporate ladder at Asana, the more your work actually is just the 'work about work'”
Most work management tools use a container model in which each task lives in exactly one project, causing copies and drift in status; Asana's work graph lets a task exist in many contexts from one source of truth, which removes the drift that creates work about work.
“every task lives in exactly one project. Asana tries to free you from that container model. So the tasks exist and they can be put in as many contexts as it makes sense”
Companies should define values and culture architecture in the first weeks alongside product and technical architecture, since waiting until product-market fit leaves culture path-dependent and merely documented after the fact.
“don't put this off. I think the conventional approach is, focus on product market fit, see if you're actually still going to exist a few years later”
Asana's Voice of the Customer process has support, sales, customer success, and user research each rank the top 100 product opportunities, then merges the rankings with a merge sort into one unified leaderboard for product prioritization.
“they each express their view on the top 100 opportunities, and give them their own ranking, and then we do a merge sort to get this unified Leaderboard”
Asana's strong norm against late-night and weekend work is set by senior leaders modeling restraint, for example by drafting tasks to deliver on Monday, which reduces perceived urgency from bosses and lets others unplug.
“I think that's very much because people like me and the other senior leaders are just mindful about that”
Sprinting can work for a limited period, roughly three or four weeks, but it must be repaid afterward with a week or two of degraded productivity, so sprints should be used carefully rather than as constant pressure.
“maybe three or four weeks of sprinting, but you'll basically have to pay for that after, in the form of a week or two of degraded productivity”
When colleagues disagree, it usually reflects a difference in underlying assumptions; the productive response is to decompose the problem and identify those assumptions, which removes emotion and makes the disagreement factual rather than personal.
“when we disagree, it probably just means we have a difference of assumption somewhere”
A core Facebook value Moskovitz brought to Asana is leverage: stack-ranking the roadmap by time and effort against customer value and doing the highest-ROI work first, which many companies fail to do.
“Literally try and stack-rank the roadmap in terms of time and effort to customer value, do the things that have the best ROI at the top”
Asana's AI will act as a navigation system over the work graph, identifying bottlenecks and reassigning work, starting with simple heuristics for resource management and progressing toward systems that auto-assign tasks, schedule meetings, and generate dependency-aware plans.
“graphs are very useful but something that makes them even more useful is having a navigation system that helps you find the best paths through that map to reach your goals”
The ultimate AI vision for Asana is a Spotify-playlist-like system that knows every assigned task, its deadlines and blockers, and tees up one task at a time, schedules meetings, and generates the dependency-aware Gantt chart for team leaders before tasks are even assigned.
“Holy grail version of this is what we think of as almost Spotify playlist-like experience for individuals”
Work-life balance is about clear separation between focused work time and focused rest time, not merely hours per week; constant email checks and push notifications keep half the mind in work, and ensuring this separation is the top priority.
“You're not constantly checking your email and getting push notifications, and keeping half of your mind in the work context. That's the number one”
Moskovitz and co-founder Justin built an internal task system at Facebook for engineering, then other teams (IT, sales, recruiting) pulled it out of their hands, revealing unmet cross-functional demand that the market was not meeting.
“Really, this is a cross-functional need, and it's not being met by the market, and we have people pulling your internal tools out of your hands”
When people list and update their own work in a shared project tool, status changes are immediately visible to everyone, so daily stand-up status meetings become unnecessary and can be reused for problem-solving or team bonding.
“There's no reason to do this daily, because as people change the metadata, or complete things, that's just immediately reflected, everyone can see it”
Asana's mission should not change, its strategy is refreshed only every three or four years, and OKR objectives keep the same structure with updated targets and initiatives each year, though exceptional events can force change.
“In fact, I usually say the mission, that shouldn't change”
When people do not understand why a task matters or how it fits the larger goals, they duplicate others' work and see their assignments as an indistinguishable soup of tasks, so connecting tasks upward to objectives restores priority and motivation.
“they all look the same to you. They're just like a soup of tasks, and you don't know which is more important”
New employees should use beginner's mind to notice what veterans miss, but should write down practices and ask why they exist before proposing change, because Asana's processes often have good reasons and sometimes none.
“they can see things that we've lost perspective on. It's just like water to us”
Asana's divergence from typical software companies is embracing complexity and nuance, using multiple balancing metrics rather than a single simple axiom, which he sees as rejecting false tradeoffs.
“In Asana, we embrace complexity and nuance a little more.”
Asana presents ARR alongside quality and sustainability regulators, specifically net retention (quality of revenue) and operating margin (sustainability), arguing all three legs are needed rather than one simple metric.
“we typically present it to the company balanced with things that I think of as quality regulators, or sustainability regulators, the net retention statistic is a quality of revenue metric, operating margin is a sustainability metric”
Asana's first custom web architecture, Luna, delivered a rich single-page experience but was too slow as customers scaled, so around 2014 to 2015 the company faced a pivot-or-persevere decision and split engineering to rebuild, causing a long, demoralizing slog.
“our first run at it was just not very efficient, and it did create the rich client side experience”
Asana could reach 10x its ARR mainly by penetrating its existing market: about 1.25 billion knowledge workers form the TAM, and existing customers are only about 3 percent penetrated into their employee bases, so expanding current deployments is enough.
“If you think of the TAM, it's about 1.25 billion knowledge workers. Right now, us and all of our competitors combined, still only reach a very small fraction of that”
Press coverage of entrepreneurship shows only the easiest, most successful stories in polished form, hiding the messiness and failures, which is survivorship bias and makes founding a company seem easier than it is.
“a lot of what you read about entrepreneurship in the press is survivor bias”
When people are burnt out they are worse teammates: more prone to conflict and less able to work through disagreement and make productive progress with the team.
“When you're in a burnt out state, you're just not as good of a teammate, it's easier to get into conflict, it's harder to work through disagreement”
Society is organized around the status quo, so radically inclusive norms must be actively fought for rather than emerging naturally, which explains why the mindset transmits slowly from settings like Burning Man.
“society is currently organized to not be radically inclusive, and so you actually have to fight that”
AI misuse rises to civilization-level existential risk, either by enabling outcomes like global nuclear war or by creating a perfectly controlling autocratic dystopia in which resistance is impossible.
“it definitely rises to the level of being a civilization existential risk”
Open Philanthropy was started alongside GiveWell to find high-impact opportunities outside global poverty and health, applying the same three filters of importance, neglectedness, and cost-effectiveness to other causes.
“we decided to start this additional organization, Open Philanthropy Project, with the goal of looking for opportunities outside of global poverty and health”
Burning Man embodies radical inclusiveness, where roughly 95 percent of attendees who show up are welcomed and encouraged to participate regardless of age, background, or identity, and Moskovitz aspires to bring that to Asana.
“95% of it, just whoever shows up is totally welcome and embraced and included and encouraged to participate”
Indoctrinating a value into a small group of about 10 people makes it far more likely to persist as the company grows to 1,000 or 10,000, which is why intentional early culture matters.
“You can be a lot more successful if you successfully indoctrinate a certain value in 10 people, you're much more likely to have it when you get to 1,000 or 10,000”
Early productivity software copied physical flat formats like spreadsheets and word processors, and the next wave breaks from that by building around relational databases, which unlocks new value.
“emails are just digital faxes”
Because Asana had a formalized objectives system, it was able to reconfigure its plan quickly after COVID hit six weeks after finalizing objectives, cancelling 300 in-person customer events and revising financial targets and operating envelopes.
“we were able to reconfigure pretty quickly”
Promising early-career people in Moskovitz's network quit or retired early when burnt out rather than taking a vacation, and he concluded there should be a way to make work time feel more sustainable so they can have longer careers.
“instead of taking a vacation when people got burnt out, they would quit. They just needed a really long reset”
If knowledge work drives technological progress and 60% of it is work about work, then automating coordination through AI like a Spotify-playlist for work becomes a force multiplier on productivity growth.
“then all of a sudden this Spotify playlist genius idea is not a trivial thing. You're talking about a force magnifier on productivity growth”
The goal for a team is to maximize output over the long run, not the number of hours people work.
“the goal is not to maximize your hours, it's to maximize your output, and in particular, over the long run”
No Meeting Wednesday was introduced at Facebook around the time Paul Graham published his Maker's Schedule, Manager's Schedule essay, and Asana adopted it.
“Facebook introduced it around the time that Paul Graham published that really famous; Maker's Schedule, Manager's Schedule”
Asana's resource management feature already uses simple non-AI heuristics to show which people are overloaded and suggest reassigning work to people with more capacity.
“we have a resource management feature in Asana right now, and just with simple heuristics, it's not AI, we can show you these people are overloaded”
Facebook's internal transparency about goals and decisions was a practice Asana adopted, and the product itself makes history searchable so new employees can trace how any decision was reached, including its data.
“you can literally go back through the entire history of the company and find almost any decision, and see the conversation about how we got to that decision”
Founders pursuing a big mission should expect many years of ups and downs and need a motivation strong enough to sustain them through a long career, since the role changes continuously.
“if you're going after a really big mission, it's just often going to take a lot of years, you better be really committed to that”
Asana should be easy to adopt by starting users with a lightweight personal task list that feels like a blank sheet of paper, then letting them grow into enterprise-wide, flexible use as needed, with customer success helping those who adopt best.
“meet those people early in their lifecycle, where they are just starting with a single task or a single project”
Almost all the fastest-growing tech companies of the 2000s had engineering teams build their own internal task management systems because they shared the coordination problem and were empowered to fix it.
“Almost all of the fastest growing tech companies in the 2000s had some internal task management system their engineering teams built”
Beyond recovering the roughly 60% of time spent on work about work, clarity about priorities, strategy, and goals can make the remaining 40% of knowledge work far more leveraged and effective.
“we can not only, hopefully give back all of that 60%, but we can also make the 40% more leveraged and effective”
Facebook's No Meeting Wednesday practice, adopted by Asana, protects focus time; Moskovitz's view is that meetings are valuable but fragment calendars, so the practice keeps both benefits.
“No Meeting Wednesdays is a way to have your cake and eat it too”
The best reason to start a company is being extremely motivated to bring something new into the world that does not currently exist and that the founder is uniquely suited to create, because it will not happen without them, rather than lifestyle goals.
“the thing that works best is just being extremely motivated by bringing something new into the world that doesn't currently exist”
As a 20-year-old first-time manager, Moskovitz found biweekly one-on-ones gave only a month-old picture of the organization, which led him to build structured, collaboratively updated databases instead of tracking everything himself.
“That was not good enough, and I was a software engineer, so I started designing some database systems where I could keep track of the state of the world”
Asana uses internal projects and in-product likes for employees to suggest features and cultural changes, letting ideas rise by pseudo-voting and leaderboards so the best ones surface.
“So it's very easy for people to pseudo vote on them, we can easily see what rises to the top there”
As a young leader, Moskovitz treated disagreement as proof that colleagues were wrong and bad, which damaged relationships until a mentor showed that disagreement does not require hatred.
“when I disagreed with somebody, they were not only wrong, but they were bad, they were an enemy”
Radical inclusiveness means countering the status quo of community, personality, or identity-driven judgments about who is allowed in and to participate, and Burning Man embodies it by welcoming whoever shows up.
“95% of it, just whoever shows up is totally welcome and embraced and included and encouraged to participate.”
When Moskovitz began building his tool around 2005 to 2006, Jira had just started and alternatives existed but were nascent and did not solve the problem the way he wanted.
“Jira started way back in 2005, so there were a couple alternatives out there, but they were very nascent”
Teams should not be dogmatic about metrics, because some good things are valuable but hard to measure, so they should be balanced against measurable goals.
“I would just balance it with don't be dogmatic, because sometimes things are good, but they're hard to measure”
Asana's long-tenured leadership and employees, some over 10 years, show that the company's sustainable day-to-day work pace allows people to stay for long careers.
“some of them more than 10 years as well, and I attribute that to them being able to have a sustainable work-life day in, day out”
Preparing an earnings call requires many teams (leadership, investor relations, legal, marketing) to work from the same source of truth with shared process status, which the work graph enables by letting each team contextualize the same task in its own queue.
“they all want to be working off the same source of truth. So of course the actual script, the content”
Moskovitz's instinct to hug the Winklevoss twins on first meeting, as a Burning Man-style gesture, was cited as a funny illustration of cultural openness.
“when you encountered the Winklevoss twins for the first time, your instinct was to hug them”