Rework 37signals

In our recent episodes, we've been talking about the principles of Shape Up – the cornerstone of 37signals' product development philosophy. We've explored the art of crafting a pitch and the decision-making process that takes place at the betting table. 

Shape Up acknowledges that there's always more work than time allows, and on today’s episode, we’re zeroing in on a critical aspect of the Shape Up philosophy—when to stop tinkering and take the leap and ship.

Join Kimberly Rhodes and 37signals co-founders Jason Fried and David Heinemeier Hansson as they share their wisdom on the ever-present dilemma of shipping on time versus shipping perfect, and the fine balance between must-haves and nice-to-haves in product development. Plus, the value of Hill Charts in Basecamp to keep you tethered to the reality of where your project truly stands.

Listen in as Jason and David provide practical strategies to master the art of timely product delivery that doesn't sacrifice quality to ensure your team stays on the path to success.

Check out the full video episode on YouTube

Show Notes: 

[00:00] - There's always more work than there is time, and at some point, you must stop and ship and that's the topic of our conversation today. 
[00:44] - Jason talks about the importance of shipping on time without sacrificing quality.
[02:29] - David uses a racing analogy to explain how viewing work through a budgeted timeframe helps you prioritize (and shed excess scope). 
[03:21] - The effectiveness of constraints in achieving better results.
[04:18] - How embracing constraints leads to better software.
[05:23] - How the two-person teams decide on "must haves" vs. "nice to haves." 
[07:51] - Constraints allow for reevaluation of the problem statement, highlighting that even the "epicenter" of a feature can be redefined, leading to scope reduction.
[10:08] - How timelines keep you honest and keep you from chasing bad money. 
[11:47] - The value of "Hill Charts" in Basecamp
 and why complex issues on the other side of the hill pose a greater challenge.
[12:44] - Jason explains that in the Shape Up methodology, if something isn't completed within the timeframe, it isn't automatically reintroduced—it has to fight for its relevance.
[14:08] - How to avoid the "too big to fail."
[14:21] - David explains how to use the "penalty box" concept to keep yourself honest in product development.
[15:08] - The importance of guidelines and guardrails in getting you where you want to go. 
[19:08] - When should a project transition to a more formalized approach like Shape Up using the example of HEY.
[20:45] - Why you should allow for experimentation in the initial exploration phase of new product development.
[21:50] - You can read more about Shape Up, 37signals philosophy around product development in the book Shape Up. A free copy is available here. Rework is a production of 37signals. You can find show notes and transcripts on our website. Full video episodes are available on YouTube and Twitter (also known as X). If you have a question for Jason or David about a better way to work and run your business, leave us a voicemail at 708-628-7850 or send us an email. 

Links and Resources:

Writing a Pitch | REWORK 
Shape Up Principle: The Betting Table | REWORK 
Books by 37signals
Shape Up
Sign up for a 30-day free trial at Basecamp.com
HEY World | HEY 
The REWORK podcast
The 37signals Dev Blog
37signals on YouTube
@37signals on Twitter 
37signals on LinkedIn 

Recently 37signals co-founders David Heinemeier Hansson and Jason Fried found themselves at the center of an unexpected internet storm. It all began when David made a significant announcement: Turbo 8 would no longer be using TypeScript. 
What followed was a whirlwind of controversy and social media fireworks.  

In today's discussion, Kimberly Rhodes sits down with Jason and David to unpack the impact of social media on these types of discussions and the broader implications of these online controversies on open source contributions. 

Check out the full video episode on YouTube

Show Notes: 
[00:00] - Kimberly opens up the discussion, sharing the recent announcement made by David, that Turbo 8 would no longer utilize TypeScript and the resulting online controversy.
[00:33] - Jason shares his reaction to the drama unfolding and offers kudos to David for handling the storm with grace.
[01:34] - David shares how it all began with eternal debate: dynamic vs. static languages, strong vs. weak typing, and 37signals is firmly in the dynamic, free-spirited camp.
[02:23] - What led to the BIG decision to pull the TypeScript plug?
[03:19] - Dynamic vs. static, it's like arguing about your favorite pizza topping. 
[04:13] - TypeScript was removed in record time (freeing the code!).
[04:59] - This debate is like a merry-go-round of arguments (and we're not here to convert anyone). 
[05:48] - David shares: "People have preconceived notions about my opinions, and when we go against the flow, it's bound to stir the pot," (remember the cloud exit?).
[07:32] - Programmers can turn small details into raging infernos and social media is like a dry brush waiting for a spark. 
[08:45] - Compared to fighting Apple for HEY.com or navigating the minefield of workplace politics, this is just a minor skirmish. 
[10:38] - Humans naturally tend to form tribes and defend their beliefs, but internet drama usually loses its fervor in 24-36 hours.
[11:38] - Jason shares the binary nature of most debates such as air-cooled vs. water-cooled Porsches or car collectors' preferences.
[12:25] - Kimberly comments on the polarized nature of the comments.
[12:38] - There is value in discussing ideas so long as the debates don’t devolve into personal attacks.
[14:39] - How personal attacks gain traction.
[15:44] - The importance of embracing diversity in programming languages and techniques for a more vibrant tech world.
[17:24] - David shares insight from his recent trip to Japan and the beauty of appreciating different cultures without feeling the need for uniformity. 
[18:42] - David reveals whether this unexpected negativity has changed his view of open source and sharing. 
[20:40] - David will continue to contribute to open source BUT…
[21:26] - Please don’t spoil open source contributions for everyone else. 
[23:16] - David shares a surprising recurring theme in the Rework podcast and why it’s important to speak out about your beliefs—especially those you are hesitant to voice publicly. 
[24:01] - David discusses whether this kerfuffle has had any effect on the 37signals team. 
[25:19] - Rework is a production 37signals. You can find show notes and transcripts on our website. Full video episodes are available on Twitter and YouTube. If you have a specific question for Jason or David about a better way to work and run your business, leave your voicemails at 708-628-7850 or send an email. 

Links and Resources:

From David’s HEY World: Turbo 8 is Dropping TypeScript
From David's HEY World: Open Source Hooliganism and the TypeScript Meltdown
DHH's post about Turbo 8 dropping TypeScript on X (formerly Twitter)
Books by 37signals
Sign up for a 30-day free trial at Basecamp.com
HEY World | HEY 
The REWORK podcast
The 37signals Dev Blog
37signals on YouTube
37signals on X 
37signals on LinkedIn 

Picture this: a dimly lit room where velvet-robed figures gather in secret to make decisions of paramount importance as the fate of the pitches for the next product development cycle hangs in the balance. 

The "betting table” – where the formalized pitches for each six-week work cycle are selected – might seem mysterious but we're about to unravel its secrets. 
Listen in as host Kimberly Rhodes sits down with 37signals co-founders Jason Fried and David Heinemeier Hansson to explore the unique inner workings of the "betting table" and how this process shapes each product development cycle.

Tune in to discover 37signals' approach to selecting and refining projects at the "betting table."

Check out the full video episode on YouTube

Show Notes: 
[00:00] - Today on the podcast, the discussion focuses on the betting table and how the decisions are made about which pitches are selected and which projects to schedule.
[00:42] - Jason shares what the betting table is. 
[02:26] - The betting table process: refining pitches into a kickoff document.
[03:17] - David shares the background behind the betting table and how it has evolved. 
[05:51] - The betting table: passionately advocating for different views, with one person ultimately making the decision.
[06:51] - Ensuring that resource allocation decisions are made efficiently while avoiding committee-driven decision-making.
[08:56] - Decisions made at the betting table can sometimes be passed to others who are more passionate or informed about a particular project.
[10:04] - It's all about timing—unselected pitches don't automatically get another chance in the next cycle, but if they are relevant, they might.  [10:51] - Jason shares his biggest issue with backlogs. 
[11:33] - David shares why Shape Up is such a powerful way of working and how the betting table process provides multiple opportunities to influence product direction.
[14:38] - Jason shares how the assignment of team members works during the betting table to ensure that the available resources match the selected projects.
[15:49] - David shares the background behind aligning pitch budgets with available resources and calendars during the betting table.
[19:55] - Why so much of the betting table process is asynchronous and done via written communication,
[22:54] - When calls might need to happen during the betting table process. 
[23:57] - For more background on how 37signals manages product development, get your free copy of the book Shape Up. It is available here.
[24:13] - Don't forget you can still enter #TheUnderdogChallenge by sharing the story of your scrappy team on the 37signals LinkedIn post here for a chance to be featured on a future episode of Rework. The deadline to enter is September 15. Rework is a production of 37signals. You can find show notes and transcripts on our website. Full video episodes are available on Twitter and YouTube. If you have a specific question for Jason or David about a better way to work and run your business, leave your voicemails at 708-628-7850.

Links and Resources:

Enter #TheUnderdogChallenge on LinkedIn 
Writing a Pitch | REWORK 
Books by 37signals
Shape Up
Sign up for a 30-day free trial at Basecamp.com
HEY World | HEY 
The REWORK podcast
The 37signals Dev Blog
37signals on YouTube
@37signals on Twitter 
37signals on LinkedIn 

If you've been following the Rework podcast, you're undoubtedly acquainted with the concept of Shape Up, a cornerstone of 37signals' approach to product development.
In this episode, we delve into a core component of Shape Up: the delicate art of crafting a pitch.

Join Rework host Kimberly Rhodes as she sits down with 37signals founders, Jason Fried and David Heinemeier Hansson for a conversation encompassing everything from the essence and purpose of a pitch to the step-by-step process of constructing a finely tuned pitch.
Listen in as Jason and David  walk listeners through Shape Up's five-point compass for an effective pitch: problem, appetite, solution, rabbit holes, and no-gos, plus insight on how to use “tracer bullets” to manage the balance between scope and execution while avoiding the pitfalls along the way.
Check out the full video episode on YouTube

Show Notes:
[00:00] - Kimberly introduces listeners to Shape Up, and the topic of the day: "writing a pitch" for product development.
[00:34] - Jason shares what a pitch is and its purpose in product development. 
[02:16] - David emphasizes a crucial counterpoint to common practices at most organizations, highlighting the two common pitfalls. [03:12] - Striking a balance: providing boundaries without stifling creativity.
[04:05] - The key innovation of a Shape Up and the importance of avoiding extremes of over-specification or vague one-liners in your pitch.
[05:44] - Jason shares who can write a pitch, and the distinction between throwing out ideas and formalized pitches. 
[07:47] - David introduces listeners to the concept of "framing" before pitching.
[09:28] - Why it’s vital to distinguish between identifying a problem and crafting a pitch.[10:25] - Effective pitch creation requires contextual awareness to devise realistic solutions.
[11:46] - Pitched solutions are more about direction than detailed execution—the true execution and implementation are the responsibility of the assigned team. 
[13:06] - Pitching is a powerful tool for attracting and nurturing independent decision-makers.
[14:54] - The magic of deferring decisions until the implementation stage.[15:46] - Pitching projects is a blend of autonomy, mastery, and purpose, aligning with Daniel Pink's principles of employee satisfaction.
[17:21] - Shape Up's five key details for making a pitch: problem, appetite, solution, rabbit holes, and no-gos. 
[18:23] - Rabbit holes: tempting yet treacherous distractions that offer the illusion of progress. Why unveiling these traps early is essential. 
[20:08] - David shares an example of a recent project using a time zone auto completer. 
[21:15] - A "science project" - the macro version of a rabbit hole.
[22:41] - How a "tracer bullet" or "traceable" helps the 37signals team understand a project's feasibility and complexity leading through a small investment of information gathering. 
[24:29] - Why a "tracer bullet is crucial for prioritizing projects, using an example of using a tracer to explore billing in other currencies and how it provided clarity on the project scope and timeline.
[25:40] - Next week's episode of Rework will focus on the "Betting Table" and how the decision-making process unfolds to choose which pitches to work on. In the meantime, don’t forget you can still enter #TheUnderdogChallenge by the sharing the story of your scrappy team on the 37signals LinkedIn post here for a chance to be featured on a future episode of Rework. Look for show notes and transcripts on our website with full video episodes available on Twitter and YouTube. If you have a specific question for Jason or David about Shape Up leave your voicemails at 708-628-7850 and we just might answer it in a future episode. 
Links and Resources:
Enter #TheUnderdogChallenge on LinkedIn 
Books by 37signalsShape Up
Drive: The Surprising Truth About What Motivates Us by Daniel H. Pink Sign up for a 30-day free trial at Basecamp.com
HEY World | HEY 
The REWORK p

In this episode of Rework, host Kimberly Rhodes sits down with 37signals founders Jason Fried and David Heinemeier Hansson to hear about the company's fondness for underdogs – small businesses that are scrappy, do more with less, and use creativity over big budgets. 
If this sounds like you, we'd love to hear from you and just might have you on an episode of Rework to share your story. Plus, the lucky winner will get one year of Basecamp Pro Unlimited on us! Here's what you need to know:

How to Enter

To participate, share your underdog story by commenting on the official contest post on LinkedIn or Twitter (X).
Your entry should include a single photo of your team in action and a description of your underdog story, with a maximum of 500 words.
To complete your entry, you must either:
Share your story on your own LinkedIn or Twitter profile using the hashtag #UnderdogChallenge and tag the official @37signals account in your post, or
Fill out the form on Basecamp’s official “Underdog Challenge” contest page at basecamp.com/underdogchallenge.


See the official contest rules for more details.
Other Links:Basecamp's Old vs. New Campaign, focused on the underdogFrom Jason's HEY World: We Stand with the Underdogs

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 YouTube

Show 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.37signals
It Doesn’t Have to Be Crazy at Work  
Sign up for a 30-day free trial at Basecamp.com
HEY World | HEY 
37signals on YouTube
The REWORK podcast
The 37signals Dev Blog
@37signals on Twitter