↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

I do whatever I want at work and I haven’t been fired yet

The author explains how new projects and other decisions are “green lit” at Basecamp through a simple rule: if a decision doesn’t seem likely to get you fired, you should go ahead and make it. Basecamp avoids formal decision-making structures like budgeting processes, program reviews, and long-term detailed plans, relying instead on a shared vision and strong trust in employees to move the company and product in the right direction.

Decision authority is largely implicit and varies by role and tenure, but the guiding rule is that if you don’t fear a disastrous outcome, you can decide. The author outlines three typical outcomes: most decisions help the company, some are “wrong” but harmless and informative, and a few cause problems that are still manageable because the company rarely faces single decisions that could destroy it. This setup depends on mutual trust between leadership and staff and aligns with David Marquet’s “Intent-Based Leadership,” where people state their intent instead of asking permission.

Over nearly seven years at Basecamp, the author has asked Jason and David for explicit permission only a handful of times, mostly for input on large or unusual moves, such as initial paid advertising experiments, a major infrastructure hardware spend, starting an internship program, and hiring a teammate. What was often sought was advice rather than formal approval. In contrast, most actions, including committing to substantial recurring cloud costs, long-running projects, internal systems, and product features, were undertaken without prior permission, sometimes preceded by a shared plan or followed by an announcement.

The author argues that companies that tightly restrict decision authority spend energy on who may decide instead of on doing the work, and they risk losing strong employees. An anecdote about a designer needing five levels of approval to buy a mouse at a previous job illustrates this contrast. The author notes that this trust-based, autonomy-focused approach has worked personally so far, including the choice to publish the post without asking for permission.

Reading notes
#

  • Basecamp recently discussed how decisions to start new projects are made, leading to a simple rule: if a decision does not seem like it will get you fired, you should proceed with it.
  • The company operates with minimal formal decision-making processes: there is no budgeting process, no program reviews, and no long-term detailed planning.
  • Instead of formal processes, there is a high-level vision for the company and product and strong trust that people will direct their time and energy toward that vision.
  • The absence of formal structures means individuals must decide how to act on their ideas on their own.
  • The level of implicit decision authority varies among people based on role, tenure, and similar factors, but the same basic rule of acting unless disaster seems likely applies to everyone.
  • Decisions are grouped into three broad outcomes: right decisions that benefit the company, wrong decisions that cause no harm but offer learning, and wrong decisions that cause problems.
  • The author says most decisions at Basecamp fall into the beneficial category, attributing this to hiring intelligent people who make those decisions.
  • Even “wrong” decisions without negative impact are seen as acceptable when they provide useful experience or lessons.
  • When a wrong decision does cause harm, the company can still recover because its scale makes truly catastrophic, company-ending decisions rare.
  • Basecamp’s approach to decision authority relies on trust: leadership trusts employees to be smart, capable, and aligned with the interests of the company, coworkers, and customers.
  • In return, employees trust that if they act in good faith, they will be safe even when some decisions turn out poorly.
  • Over nearly seven years at Basecamp, the author recalls only a few times when permission from Jason or David was explicitly requested.
  • The first request for permission involved starting paid advertising experiments shortly after joining the company.
  • Another request involved spending a few hundred thousand dollars on hardware to upgrade the data infrastructure in 2014.
  • The author also sought permission to start an internship program in late 2015 but did not repeat this step when continuing the program the following year.
  • A further example was asking permission to hire Justin as a full-time team member in 2016.
  • In these permission-seeking cases, the underlying need was often advice: checking whether the problem framing and proposed course of action seemed sound and likely to succeed.
  • By contrast, the list of actions taken without permission is described as much longer and covering more of the author’s work.
  • Without asking in advance, the author committed Basecamp to tens of thousands of dollars per month in recurring cloud infrastructure costs.
  • The author also invested months of personal effort into projects believed to be in Basecamp’s long-term interest without formal approval.
  • Additional autonomous actions included launching new internal systems and adding features to customer-facing applications.
  • The author also persuaded other teams to invest significant time into projects that originated from the author’s own ideas, again without prior permission.
  • The author estimates that about 99% of their work at Basecamp followed this pattern of acting without seeking permission.
  • For these autonomous decisions, sometimes a written plan was shared ahead of time, while other times the author simply announced what had been done after completion.
  • The author connects this approach to David Marquet’s concept of “Intent-Based Leadership” described in the book “Turn the Ship Around.”
  • Under intent-based leadership, people state what they intend to do and allow others to raise concerns instead of formally asking for approval.
  • The expectation in this model is that most of the time no one objects because the person acting is considered competent and likely to choose well.
  • After years of working this way, the author finds it hard to imagine working in an environment that requires permission on an hourly, weekly, monthly, or even quarterly basis.
  • The author contends that organizations that tightly control decision authority harm themselves by focusing on permission structures rather than execution.
  • Such control-heavy environments can also cause them to lose their best people, who do not want to work under heavy approval layers.
  • A designer at Basecamp previously worked somewhere that required five levels of approval to order a new mouse, an experience contrasted with Basecamp’s culture.
  • The designer from that story now works at Basecamp instead of the previous company with the rigid approval process.
  • As of the time of writing, the author reports that working under this high-autonomy rule at Basecamp has been successful and has not resulted in being fired.
  • The author notes that this particular blog post was written and published without asking for permission and expresses confidence that this will be acceptable.

Related notes#