前言 Foreword by Jason Fried¶
The way a team works has an enormous influence on what it can do. The process, the methods, the practices, the approach, the discipline, the trust, the communication style, the pace. The way—the how—is foundational and fundamental.
一個團隊的運作方式對其能夠達成的成果有著巨大的影響。流程、方法、實踐方式、工作方式、紀律、信任、溝通風格以及節奏——這些「如何做」的要素都是團隊成功的基礎與關鍵。
You’ll often hear people say “execution is everything,” but that’s not quite right. In fact, it’s often quite wrong.
你可能常聽到有人說：「執行力就是一切。」但這其實並不完全正確，甚至在很多情況下是錯的。
When it comes to project work, and specifically software development, executing something the wrong way can destroy morale, grind teams down, erode trust, crunch gears, and wreck the machinery of long-term progress. So yeah, it’s “done,” but at what cost? By doing, what have we done to ourselves? Do we really have to do that again, over and over month after month, year after year?
在專案工作，特別是軟體開發中，以錯誤的方式執行不僅會摧毀士氣，還會讓團隊疲憊不堪、侵蝕信任、造成內部摩擦，甚至毀掉長期進步的基礎。是的，專案「完成」了，但代價是什麼？在執行的過程中，我們對自己造成了什麼影響？我們真的要一次又一次，每個月、每年都這樣重蹈覆轍嗎？
How many projects have you been a part of that you’d want to do over? How many projects have gone long, piled up at the end, and burned people out? How many projects were essentially collections of unreasonable expectations? How many projects turned teams against each other, frustrated everyone from builder to stakeholder, and ultimately would have been better off dying than delivering?
回想一下，你曾經參與過多少個專案是你願意再做一次的？有多少專案拖延過久、在最後關頭堆積成災，讓團隊筋疲力竭？有多少專案根本是建立在不合理的期待上？又有多少專案最終讓團隊彼此對立，讓從開發人員到利害關係人都感到挫折，最後與其勉強交付，還不如直接放棄？
Sometimes execution is everything—everything that’s wrong. So what does executing right look like?
有時候，「執行力就是一切」——但卻是所有問題的根源。那麼，正確的執行應該是什麼樣子？
Over the last few years, there’s been a heightened curiosity about how we work at Basecamp. People often ask us how we get so much done so quickly at such a high level of quality with such a small team. And how we keep our teams together for years and years.
近年來，越來越多人對 Basecamp 的工作方式產生興趣。人們經常問我們，為什麼我們能夠用這麼小的團隊，在短時間內完成如此多高品質的工作？又是如何讓團隊長年維持穩定、持續合作？
For one, we’re not into waterfall or agile or scrum. For two, we don’t line walls with Post-it notes. For three, we don’t do daily stand ups, design sprints, development sprints, or anything remotely tied to a metaphor that includes being tired and worn out at the end. No backlogs, no Kanban, no velocity tracking, none of that.
首先，我們不使用瀑布式開發（Waterfall）、敏捷開發（Agile）或 Scrum。其次，我們不會在牆上貼滿便利貼。再來，我們不開每日站立會議（Daily Stand-ups）、設計衝刺（Design Sprints）、開發衝刺（Development Sprints），也不會採用任何帶有「衝刺」隱喻的做法，因為這種方法往往讓人筋疲力竭。沒有待辦清單（Backlogs）、沒有看板（Kanban）、沒有速度追蹤（Velocity Tracking），這些我們通通不做。
We have an entirely different approach. One developed in isolation over nearly 15 years of constant trial and error, taking note, iterating, honing in, and polishing up. We’ve shaped our own way.
我們有一種完全不同的方法。這套方法經過近 15 年的獨立摸索、持續試錯、觀察改進、反覆打磨，最終形成了我們自己的工作模式。
Blog posts, workshops, and occasional conference talks have provided glimpses of our own unique process, but we’ve never laid it bare for all to see. This book does just that.
部落格文章、工作坊，以及偶爾在研討會上的分享，或許讓外界對我們獨特的工作流程略知一二，但我們從未完整公開過它。而這本書，正是為了做到這一點。
Now that our process is fully formed, documented, and ready to go, we’re here to share it with all those curious enough to listen to a new way of doing things. Explorers, pioneers, those who don’t care what everyone else is doing. Those who want to work better than the rest.
如今，我們的流程已經成熟、完整記錄並準備好分享。我們希望與那些對新方法感興趣的人交流——探索者、先驅者，以及那些不在乎主流做法、只想找到更好工作方式的人。
Don’t think of this as a book. Think of it as a flashlight. You and your team have fumbled around in the dark long enough. Now you’ve got something bright and powerful to help you find a new way.
別當作一本書，把它當作一支手電筒。你和你的團隊在黑暗中摸索得夠久了，現在你有了一個明亮而強大的工具，幫助你找到一條新的道路。
We hope you find it interesting, enlightening, and, most of all, helpful.
希望你覺得這本書有趣、啟發人心，最重要的是，對你有所幫助。
Thanks for reading.
感謝你的閱讀。