Getting Real
The Smarter, Faster, Easier Way to Build a Successful Web Application
byJason Fried, David Heinemeier Hansson, Matthew Linderman
Book Edition Details
Summary
In the fast-paced world of digital innovation, "Getting Real" defies the conventional playbook with its audaciously straightforward philosophy. Crafted by the trailblazers at 37signals, this manifesto isn’t just a collection of ideas—it’s a rebellion against complexity. It whispers secrets of simplicity to entrepreneurs, designers, and tech visionaries daring enough to listen. Learn how seven people, scattered across time zones, birthed groundbreaking tools like Basecamp and Ruby on Rails without the crutch of external funding. This isn’t a technical tome; it’s a rallying cry for those ready to strip away the superfluous and embrace a purer path to success. Are you ready to break the mold and Get Real?
Introduction
In a world where software projects drag on for years and bloated applications overwhelm users with unnecessary features, there exists a revolutionary approach that challenges everything you've been taught about building digital products. What if the secret to creating successful software wasn't about adding more, but about doing less? What if the path to winning wasn't through complex planning documents and lengthy development cycles, but through rapid iteration and ruthless simplification? This methodology transforms how small teams can compete with industry giants, turning constraints into advantages and speed into your greatest weapon. The principles you'll discover here have helped countless entrepreneurs launch products faster, serve customers better, and build sustainable businesses without the traditional overhead that kills innovation and drains resources.
Start Small and Stay Lean
Building great software begins with embracing the power of less. This isn't about cutting corners or delivering inferior products, but about recognizing that constraints breed creativity and focus drives excellence. When you deliberately limit your resources, team size, and feature set, you force yourself to identify what truly matters and eliminate everything that doesn't serve your core mission. Consider the story of 37signals when they decided to build Basecamp. They weren't a venture-backed startup with unlimited resources and a team of dozens. Instead, they were a small design firm with existing client work, spread across different time zones, with no outside funding. Rather than seeing these limitations as obstacles, they transformed them into advantages. The geographical distance forced clearer communication through instant messaging and email, eliminating time-wasting meetings. The small budget prevented feature bloat because every addition had to justify its existence. This approach led them to focus intensely on the core problem: project management is fundamentally about communication, not charts and graphs. By staying small and lean, they could make decisions quickly, pivot when necessary, and maintain the vision that would eventually attract hundreds of thousands of users. Their constraints didn't limit their success; they enabled it. To implement this philosophy, start by deliberately restricting your initial scope. Choose three essential features maximum for your first version. Embrace a small team structure where everyone wears multiple hats and can contribute across disciplines. Set strict budgets and timelines that force prioritization decisions. Most importantly, resist the urge to expand too quickly, as mass creates momentum that becomes increasingly difficult to change direction. Remember that staying lean isn't a temporary phase you'll outgrow, but a permanent mindset that keeps you agile, focused, and connected to what your customers actually need rather than what you think they want.
Build What Matters Most
The foundation of exceptional software lies in solving problems you genuinely understand and care about. This principle goes beyond market research and customer surveys to something more fundamental: building solutions for pain points you've personally experienced and deeply comprehend. The creation of Basecamp perfectly illustrates this approach. The team at 37signals wasn't conducting focus groups or analyzing market opportunities when they identified their core problem. As a design firm, they struggled daily with keeping clients informed about project progress through manually updated client extranets that quickly became stale and abandoned. Every project suffered from poor communication, leaving clients in the dark and team members disorganized. This wasn't a theoretical problem they'd read about in industry reports, it was a daily frustration that affected their actual work and relationships. Rather than accepting this limitation or trying to force-fit existing project management tools that were bloated with unnecessary features like comprehensive billing and strict access controls, they made a bold decision. They would build exactly what they needed, nothing more and nothing less. The solution focused purely on communication: messages, comments, to-do lists, and file sharing, all designed around transparency and collaboration rather than control and restriction. To apply this principle, start by cataloging the genuine problems in your own work or life that existing solutions fail to address adequately. Document specific moments of frustration with current tools or processes. Build for yourself first, ensuring you'll be a passionate, daily user of what you create. This personal investment guarantees you'll understand the nuances that separate good software from great software. When you solve your own problems, you create something you'll naturally want to use and improve continuously, which translates into authentic passion that customers can feel and trust.
Launch Fast and Iterate Smart
Speed to market isn't just about being first, it's about gathering real feedback from actual users as quickly as possible to validate or redirect your assumptions. This approach treats your initial launch not as a final destination, but as the beginning of a conversation with your market that will guide every subsequent decision. The most successful products emerge from this cycle of rapid deployment and continuous refinement. When 37signals launched their various applications, they didn't wait for perfection or try to anticipate every possible user need. Instead, they released functional versions that solved the core problem well, then listened carefully to how people actually used their software. This real-world data proved far more valuable than months of theoretical planning or focus group discussions could ever provide. Ta-da List exemplifies this philosophy in action. Rather than building complex categorization systems, date assignment features, or elaborate notification schemes, they launched with the simplest possible implementation: lists of tasks that you could create, edit, and check off. Users who needed dates simply added them to task descriptions. Those wanting categories created their own conventions using brackets or other markers. The software provided the framework; users developed their own solutions within it. To implement this strategy, identify the absolute minimum viable version of your product that solves the core problem. Build only those essential features that demonstrate your key value proposition. Plan for a launch timeline measured in months, not years, accepting that your first version will feel incomplete compared to your ultimate vision. After launching, establish systems to capture and analyze user feedback, usage patterns, and feature requests. Create regular iteration cycles, perhaps monthly or quarterly, where you add features based on actual user behavior rather than assumptions. Most importantly, maintain the discipline to say no to features that seem logical but don't align with how people actually use your product.
Summary
The path to building exceptional software isn't found in comprehensive planning documents, unlimited resources, or feature-rich applications that try to solve every conceivable problem. Instead, it emerges from the disciplined pursuit of simplicity, the courage to say no to good ideas in service of great ones, and the wisdom to let real user behavior guide your development decisions. As this methodology demonstrates, "Less mass lets you change direction quickly. You can react and evolve. You can focus on the good ideas and drop the bad ones." The most powerful step you can take today is to identify one specific problem you personally experience, write a one-page description of a solution, and begin building the simplest possible version that addresses that core need, committing to launch within 30 days regardless of how incomplete it feels.
Related Books
Download PDF & EPUB
To save this Black List summary for later, download the free PDF and EPUB. You can print it out, or read offline at your convenience.
By Jason Fried
