Knowing when you're in over your head and recognizing when a project has gone off the rails are crucial aspects of successful project management. But what are the red flags to watch for to prevent project derailment and how can you tell if a project is doomed to fail—even before you start? This week, Jason Fried and David Heinemeier Hansson, the co-founders of 37signals, sit down with host Kimberly Rhodes to discuss the challenges of project management and share valuable insights on how to stay focused, recognize red flags early on, and foster creative problem-solving in order to see a project through to completion. Listen in as they reveal the importance of finishing tasks before adding new ones, the pitfalls of multitasking, and the magic of setting clear endpoints. Plus they share Basecamp's tool for facilitating project monitoring without time-consuming meetings or derailing check-ins.Tune in for practical solutions for rescuing a project before it's too late! Check out the full video episode on YouTubeShow Notes: [00:00] - Kimberly opens the show and the topic of how to rescue a project when it’s gone off of the rails.[00:34] - Adding too much without finishing anything causes chaos. Jason shares the story behind his HEY World piece, Rescuing a project in progress, and shares the advice he gave his friend and how that applies to software development too.[02:49] - David shares the reasons behind the “Shape Up” approach at 37signals. [03:44] - You can’t do two things at once, every time you do you lose a little bit…[04:33] - Clearing the decks, wiping the slate clean, AND deciding what you are going to do with 100% of your time and how it helps you avoid shiny object syndrome.[05:20] - Why it's crucial for successful project management to avoid adding new tasks until all the existing unfinished ones are completed. [06:11] - How the magic of deciding when you’re done helps lower the risk of multitasking.[08:53] - In software development how can you tell things are going off the rails before it’s way too late?[09:17] - Jason shares why you need to be tuned into those feelings of being in over your head. [10:43] - David shares the major red flag moment for him that lets him know you’ve already failed before you even get started.  [12:28] - “The longer, the more complicated the project, the more deceivingly specific people believe they can be when the opposite should actually be true.”[13:17] - Why you should never give yourself too much time for a project. [14:13] - The work-in-progress unified system in Denmark for tax assessments of properties that will never be finished (it’s already eight years overdue, and a billion dollars in).[15:53] - The easiest time to stay on track for a project. [16:29] - The other problem with long projects is that you get more time to not fix the problem.[17:17] - The curse of too much time and the sweet spot of creative problem-solving for any endeavor. [18:06] - X is the epicenter of the problem, start there and THEN see how much of Y and Z you get to before your (set in stone) ship deadline. [19:37] - Kimberly shares some people’s approach to rescuing projects and the difference at 37signals. [20:02] - Jason talks about the false sense of security that comes from knowing everything that’s going on.  [21:12] - David shares how “sawing at the wheel” just makes you go slower. [21:57] - Are we done yet? Are we done? How constant interruptions slow projects down. [22:42] - How Basecamp’s

If you've been following along with the podcast, you've heard the mention of two-person teams and how 37signals makes the most of its software features and productivity with just two people working together—one programmer and one designer. In this episode of the Rework podcast, 37signals co-founders Jason Fried and David Heinemeier Hansson sit down with Kimberly Rhodes to dive deeper into the concept of two-person teams and share valuable insights on the benefits, challenges, and strategies behind their unique approach.Listen in as Jason and David share the importance of short-term cycles, the significance of building their own tools for maximum efficiency, and how these principles shape their company's operations. They also discuss the expansion of two-person teams into other areas of the organization and the limitations of working as a team of one. Tune in to discover how the power of two can revolutionize teamwork and productivity.Show Notes:  [00:00] - Today, Jason Fried and David Heinemeier Hansson are here to discuss the concept of smaller teams and how two-person teams are effective at 37signals. [00:48] - Jason shares that initially, teams at 37signals had three people, including two programmers and one designer, and why they changed to two people on each six-week cycle project. [01:33] - The constraint of having two people is not a resource issue but rather an opportunity to tighten project scopes and prioritize ideas. Direct communication between the programmer and designer eliminates translation layers and allows for efficient progress.[02:14] - How the direct collaboration of two-person teams sharing the same workspace enables rapid progress.[02:53] - David shares how working with web technologies improves two-person teams' efficiency and helps avoid delays caused by platform approvals or updates.[03:49] - The significant advantage for 37signals is that it eliminates the need for conversions.[04:44] - Enhancing the bandwidth between the two team members by removing obstacles and maximizing direct communication—how 37signals realized that having five programmers for Basecamp was too many.[05:40] - Blowing the minds of startups who think they need an army of programmers—the secrets of 37signals' productivity. [06:31] - New members easily integrate into the productive system, proving that anyone can embrace this approach.[06:45] - Two-person team pairings at 37signals are flexible—some stay together, some don't. [09:06] - Embracing the freedom of the two-person team approach by setting aside daily stand-ups and rigid check-ins in favor of a balance of oversight and support without unnecessary bureaucracy.[10:19] - The secret behind 37signals' unique management approach—how management, driven by processes rather than people, creates a more efficient work environment.[11:10] - How a simple set of questions and a six-week feature cycle can provide clarity while evaluating progress and fostering trust within the team.[12:48] - A drop of product management is all you need to drive success.[14:31] - How traditional software development approaches and large teams lead to excessive long-term planning, misguided processes, and massive hirings and firings.[16:02] - Challenging the status quo with smaller, nimble projects for greater success.[17:07] - Unlike industry giants, 37signals is focused on speed and efficiency.[19:05] - David shares the difference between producing something final instead of “a long conveyor belt of partial feature implementations that get put behind feature flags, and you have the proliferation of half-done work that has never moved off the plate.”[21:07] - Jason shares one of the biggest mistakes in business—what promises really get you (hint: it’s not to your t

Bugs are an inevitable part of complex software and aiming for complete bug-free perfection is not only unrealistic, but it hinders progress and product delivery.In this episode of Rework, host Kimberly Rhodes sits down with 37signals founders, Jason Fried and David Heinemeier Hansson to discuss why you need to be realistic about bugs in software development. Listen in as David and Jason offer a behind-the-scenes look at the two-tiered approach to handling bugs in their software at 37signals and their triage plan for determining which should be fixed, when, and by whom.Tune in to uncover strategies to manage your customers' expectations while dealing with bugs WITHOUT deviating from your product roadmap Check out the full video episode on YouTubeShow Notes: [00:00] - Kimberly opens the show and shares the topic for discussion, that bugs in software are normal. [00:27] - David shares why you need to be realistic about bugs in software development.[01:18] - Bugs, a natural side effect of software. [02:08] - What makes users abandon a piece of software (hint: it’s usually not a few bugs)?[05:26] - The two-tiered (non-emotional) approach to handling the vast spectrum of bugs in complicated pieces of software.  [06:13] - When is a “bug” not a “bug”? [07:00] - Handling customer expectations without screwing up your product roadmap.  [07:52] - You need a filter: the double-edged sword of founders operating in customer support.  [08:32] - David shares a behind-the-scenes look triage at 37signals.  [09:31] - The novel QA approach of the Toyota production line that 37signals tries to emulate. [11:37] - Jason shares the difference between the software and auto industries when fixing production problems. [12:37] - Yes, quality matters, but perfect never gets shipped. [14:30] - So how do we build useful, meaningful software? [15:21] - Breaking out of bad bug thought patterns so you can keep making software of value. [16:47] - Who oversees fixing the bugs at 37signals—the methods they use to determine what gets fixed, when, and by who. [20:08] - Cleaning up the tech debt: the vital importance of a measured, mature way of scheduling things. [21:09] - Don't create ****** software—it can’t be fixed. [23:55] – Jason discusses the idea an organization might be a bigger problem than just a bug in the software.[24:44] - Why you should never become "too big" to listen to your customers. [26:28] – For more, check out our Dev.37signals blog, where the 37signals developers write about some of their processes.[26:45] - Rework is a production of 37signals. You can find show notes and transcripts on our website. Full video episodes are also available on Twitter and YouTube. If you have questions for David and Jason about a better way to work and run your business, we’d love to answer them. Leave your voicemails at 708-628-7850 or send an email. Links and Resources:From David’s HEY World: Software has bugs. This is normal. Dev.37signalsIt Doesn’t Have to Be Crazy at Work  Sign up for a 30

In today's fast-paced information-saturated world, advice is abundant, but it can be difficult to determine which sources are truly reliable.This week, Jason Fried and David Heinemeier Hansson, the co-founders of 37signals, join host Kimberly Rhodes to discuss the challenges of navigating the ever-growing sea of advice and how to choose the right guidance for your journey.Listen in as they share their thoughts on the expiration date of advice, the dangers of following someone else's prescribed path, and the value of trusting your own instincts.Watch the Full Episode on VideoShow Notes: [00:00] - Kimberly opens the show and introduces listeners to the topic of finding reliable business advice in today’s digital age. [00:40] - Jason shares why he wrote Advice Expires and why he and David are the wrong people to ask for advice about starting a business. [02:14] - David shares how the Internet's craving for content leads to conflicting advice and the value of trusting your own instincts.[04:16] - Ignore more advice than you take: turning the tide on the trend of collecting mentors and seeking advice from multiple sources.[05:04] - The value of being outside the Silicon Valley bubble.[05:44] - The importance of cultivating originality. [06:15] - The danger of following everyone else's formula for success. [07:38] - How the "Pinterestization" of our culture is diluting originality in favor of popularity.  [09:48] - The mystery behind success—Jason shares why you must be mindful of blindly emulating successful companies or individuals.  [10:52] - David discusses the “Halo Effect” and how success in one aspect doesn't necessarily mean excellence in all areas. [11:41] - The “awesomeness tradeoff”: how the book “Blue Ocean Strategy” puts a method to the idea that you can't be awesome at all the things all the time. [13:12] - Kimberly raises the issue of self-proclaimed experts on the Internet.[14:13] - Why "Rework" was so successful. [14:50] - The importance of a select set of core ideas or key values for more effective decision-making in a sea of options. [16:13] -Trusting your gut and the pitfalls of seeking too much advice.[17:13] - Kimberly asks Jason and David about their approach to seeking advice and executing decisions. [17:35] - Jason shares his approach to seeking advice and what his method depends upon.  [19:04] - David shares his preference for seeking guidance from "dead people." [20:03] - Reality as a mentor: the importance of contextualizing advice and learning through experimentation.[21:44] - The role of criticality when seeking advice.[22:08] - David shares why he continues to give advice and what people are really looking for.[22:34] - How the book "Maverick" by Ricardo Semler influenced the unconventional ideas and served as a benchmark for determining the level of "bat-shitness" in Jason and David’s decisions when they were starting out. [23:48] - Do you have qu

"Getting out of estimates and getting into appetites and budgets is the single most important thing that we have instituted," - David Heinemeier Hansson  Today, Jason Fried and David Heinemeier Hansson, the co-founders of 37signals, discuss their chapter in Rework on why estimating is not the road to completing projects and what has helped them get things done in their business for over twenty years. Show Notes:  [00:42] - David shares why it's time to accept that we're awful at estimating.[03:27] - Why estimating is 'an amazing example of the human optimism to overcome its own fundamental flaws in a way that's just wholesomely unrealistic.'[04:48] - What 37signals does instead of estimating as relayed in Shape Up.[05:49] - Jason asks how much you are willing to spend (or lose) in gambling (and software development projects).[08:13] - The worst situation to be in for rational decision-making.[09:00] - Why it's vital to stick to your limits.[10:29] - "Getting out of estimates and getting into appetites and budgets is the single most important thing that we have instituted as a barrier for our software development process over all these years."[12:47] - In software development, no one—from the owner of the company to the end user—gets everything they want; staying within your parameters is about trading concessions. [14:15] - You need to keep the engine moving because software development is like baking bread on an industrial scale.  [16:19] - You produce what you practice. [16:57] - You don't cut corners or quality, you cut scope, and if you can't, you scrap the project. [18:15] - Losing the right things prevents you from missing out on other opportunities. [19:48] - Forecasting the next ten years, six weeks at a time. [20:33] - Shortening planning cycles improves your ability to determine your next steps with more accurate information. [21:15] - 'We're making a ton of progress with a small team with a product that's been around for 18 years - so it works!'[23:21] - Why keep doing things that don't work? Links and Resources:Rework Shape UpDev.37signalsSign Up for 30-day FREE trial at Basecamp.com37signals on YouTubeThe REWORK podcastThe 37signals Dev Blog@reworkpodcast on Twitter@37signals on Twitter

This week, Jason Fried and David Heinemeier Hansson, co-founders of 37signals, join host Kimberly Rhodes to answer listener questions from the recent episode about Two-Person Teams. They tackle topics ranging from two-person team collaboration techniques to their innovative approach to team cooldown periods and the benefits for individuals and the overall project workflow. Listen in as they discuss their journey in refining the on-call process and the power of "spring cleaning" to address unresolved issues. Tune in to this episode for valuable advice based on questions asked by listeners like you.Show Notes: [00:00] - Kimberly dives into today’s episode with more listener questions sourced from various platforms beginning with Kenneth from LinkedIn and his question about how a two-person team can be resilient to vacation, sickness, and turnover.  [00:42] - Jason shares how having multiple two-person teams and time-boxed cycles allows for handling absences. [02:52] - "Scope is this magical flexible bubble of energy that you can squeeze into different size containers."[04:24] - A viewer on YouTube responds to David's remarks about trust in teams by asking if there are any prerequisites for trustworthy individuals. [04:51] - The critical foundation of a long-term collaboration: David shares why trusting employees is a worthwhile investment and how to establish the right boundaries within your organization to build trust.[08:30] - How the concept of the "trust battery" (introduced by Toby from Shopify) helps in understanding the dynamics of trust and its impact on relationships and perceptions.[10:02] - Trust is a gradual process that allows individuals to gain confidence and demonstrate their readiness for higher levels of responsibility.[11:23] - The next question comes from a voicemail inquiring about how Quality Assurance (QA) and testing are handled at 37signals and the interaction between QA and the six-week cycles of the Shape Up paradigm.[12:16] - David reveals the priorities of 37signal's recently revamped QA approach with two QA team members and no more reliance on external vendors.[13:12] - The importance of customer data using the example of the launch of a card table feature in Basecamp.[16:27] - You are responsible for your own work; the QA team is there to find the edge cases, not the other way around.[17:18] - QA (like many things) is everyone's job: how the 37signals model helps individuals level up more quickly AND ensures that the quality is right when things ship. [18:26] - Justice, a fan of Jason and David's books and products, emailed a question about how 37signals handles bugs, smaller tasks, and standalone features that vary in time requirements.[19:10] - Clearing up the confusion about the 6-week rule. The distinction between proactive and reactive work and ensuring efficient project handling.[21:49] - The 37signals "spring cleaning" approach to tackling non-critical but lingering issues, allowing for dedicated time for focused resolution while preventing constant interruptions in delivering ambitious goals.[24:11] - Cleaning up your own s***! An explanation of 37signals two-tier code system for handling issues [25:41] - How the on-call rotation works at 37signals.[25:51] - The on-call rhythm: a chance to stretch problem-solving muscles for a period. [27:37] - The vital role of the cooldown at 37signals: empowering developers and designers to recharge and fostering a balance between ambition and reflection.[31:41] - Do you have questions for David and Jason about a better way to work and run your business? Leave your voicemails at 708-628-7850 or send an email. Remember, you can find show notes and transcripts on our website. Links

David Heinemeier Hansson, an expert on the 'Post-SaaS era', joins the podcast to discuss the shift from SaaS to product businesses, the evolving landscape of remote work, navigating internal culture struggles at Basecamp, and the potential for small startups to compete and disrupt larger companies. They also touch on the changing cost structure for startups, the impact of remote work on business models and costs, the benefits of living under constraints, and the power of AI in learning.

David "DHH" Heinemeier Hansson (@dhh) is the creator of Ruby on Rails, founder and CTO at Basecamp (formerly 37signals), and the best-selling co-author of Rework and Remote: Office Not Required. Oh, and he went from not having a driver's license at 25 to winning, at 34, the 24 Hours of Le Mans race, one of the most prestigious automobile races in the world. It is often called the "Grand Prix of endurance and efficiency." David is one of the most outspoken technologists out there. He is not one to hide his opinions or mince words. In this episode, we cover a lot, including... The power of being outspoken Running a profitable business without venture capital Stoic philosophy Flow space Parallels across disciplines DHH's rules for creating excellence And much, much more... Please enjoy my conversation with DHH! Show notes and links for this episode can be found at www.fourhourworkweek.com/podcast. This podcast is brought to you by Four Sigmatic. I reached out to these Finnish entrepreneurs after a very talented acrobat introduced me to one of their products, which blew my mind (in the best way possible). It is mushroom coffee featuring chaga. It tastes like coffee, but there are only 40 milligrams of caffeine, so it has less than half of what you would find in a regular cup of coffee. I do not get any jitters, acid reflux, or any type of stomach burn. It put me on fire for an entire day, and I only had half of the packet. People are always asking me what I use for cognitive enhancement right now, this is the answer. You can try it right now by going to foursigmatic.com/tim and using the code Tim to get 20 percent off your first order. If you are in the experimental mindset, I do not think you'll be disappointed. This podcast is also brought to you by Wealthfront. Wealthfront is a massively disruptive (in a good way) set-it-and-forget-it investing service led by technologists from places like Apple. It has exploded in popularity in the last two years and now has more than $2.5B under management. Why? Because you can get services previously limited to the ultra-wealthy and only pay pennies on the dollar for them, and it's all through smarter software instead of retail locations and bloated sales teams. Check out wealthfront.com/tim, take their risk assessment quiz, which only takes 2-5 minutes, and they'll show you for free the exact portfolio they'd put you in. If you want to just take their advice and do it yourself, you can. Well worth a few minutes to explore: wealthfront.com/tim. ***If you enjoy the podcast, would you please consider leaving a short review on Apple Podcasts/iTunes? It takes less than 60 seconds, and it really makes a difference in helping to convince hard-to-get guests. I also love reading the reviews!For show notes and past guests, please visit tim.blog/podcast.Sign up for Tim’s email newsletter (“5-Bullet Friday”) at tim.blog/friday.For transcripts of episodes, go to tim.blog/transcripts.Interested in sponsoring the podcast? Visit tim.blog/sponsor and fill out the form.Discover Tim’s books: tim.blog/books.Follow Tim:Twitter: twitter.com/tferriss Instagram: instagram.com/timferrissFacebook: facebook.com/timferriss YouTube: youtube.com/timferrissPast guests on The Tim Ferriss Show include Jerry Seinfeld, Hugh Jackman, Dr. Jane Goodall, LeBron James, Kevin Hart, Doris Kearns Goodwin, Jamie Foxx, Matthew McConaughey, Esther Perel, Elizabeth Gilbert, Terry Crews, Sia, Yuval Noah Harari, Malcolm Gladwell, Madeleine Albright, Cheryl Strayed, Jim Collins, Mary Karr, Maria Popova, Sam Harris, Michael Phelps, Bob Iger, Edward Norton, Arnold Schwarzenegger, Neil Strauss, Ken Burns, Maria Sharapova, Marc Andreessen, Neil Gaiman, Neil de Grasse Tyson, Jocko Willink, Daniel Ek, Kelly Slater, Dr. Peter Attia, Seth Godin, Howard Marks, Dr. Brené Brown, Eric Schmidt, Michael Lewis, Joe Gebbia, Michael Pollan, Dr. Jordan Peterson, Vince Vaughn, Brian Koppelman, Ramit Sethi, Dax Shepard, Tony Robbins, Jim Dethmer, Dan Harris, Ray Dalio, Naval Ravikant, Vitalik Buterin, Elizabeth Lesser, Amanda Palmer, Katie Haun, Sir Richard Branson, Chuck Palahniuk, Arianna Huffington, Reid Hoffman, Bill Burr, Whitney Cummings, Rick Rubin, Dr. Vivek Murthy, Darren Aronofsky, and many more.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this episode, Jason Fried and David Heinemeier Hansson, co-founders of 37signals, discuss the delicate art of crafting a pitch for product development. They walk listeners through Shape Up's five-point compass for an effective pitch, highlighting the importance of avoiding extremes of over-specification or vague one-liners. They also explore the concept of rabbit holes and the significance of identifying and avoiding them. Additionally, they discuss different types of project pitches and approaches and emphasize the importance of dedicating time for exploration and making informed decisions.

"Everyone should manage themselves" has been a core principle at 37signals from day one and has continued to be key as the company has expanded. Today, Jason Fried and David Heinemeier Hansson sit down to discuss why it’s essential to the success of your company to bring on board self-sufficient employees who require minimal supervision in what they refer to as "Managers of One" from their book, Rework. Listen in as they provide tips on identifying such individuals during the hiring process, using Basecamp's features to replace what managers do, and the fundamental characteristics of a great "Manager of One."Show Notes:  [00:42] - "Everyone should manage themselves": A 37signals mantra from day one. [02:12] - Establishing a culture where there is no need for managers.[04:03] - David shares two examples of how using Basecamp's Automated Check-ins helps replace what managers do. [05:12] - Jason shares the behind-the-scenes of using the work to find the employees who are "Managers of One."[07:26] - David shares how "Drive" by Daniel Pink highlights the three drivers of motivation that they look for in an applicant's cover letter. [09:20] - Hiring is not a foolproof process—for anyone—even Google. [10:59] - The "Manager of One" concept applies before and after the hiring process.[13:47] - Self-identifying problems and rushing to solutions are not enough; the interactions must also be great.[14:32] - The ultimate quality of a true "Manager of One."[15:47] - Not to dictate but to support: the hallmarks of a great manager at 37signals.[19:02] - We're getting ready for a "ask me anything" episode. Do you have a question for Jason and David or anyone at 37signals? Leave us a voicemail at 708-628-7850, or send us an email, and we might answer it. Links and Resources:DriveReworkDo you have a question for Jason and David? Leave us a voicemail at 708-628-7850 or email us.HEY World | HEY Dev.37signalsSign Up for 30-day FREE trial at Basecamp.com37signals on YouTubeThe REWORK podcastThe 37signals Dev Blog@reworkpodcast on Twitter@37signals on Twitter