24分
Listener Questions / AMA REWORK
-
- マネージメント
In this episode of Rework, Jason Fried and David Heinemeier Hansson, co-founders of 37signals, join host Kimberly Rhodes to answer questions posed by Rework listeners.
Listen in as they share their insights and experiences in running a successful software company by answering questions from podcast listeners on topics such as 37signals' approach to design, decision-making processes, product management, and balancing managerial roles and responsibilities.
Tune in to hear their unique perspectives on these key aspects of building a successful software company.
Show Notes:
[00:23] - Noel asks David and Jason about their philosophy on design systems and using components instead of reinventing the wheel every time.
[01:01] - Jason explains that 37signals' website is a collection of ideas. The product itself is their design system.
[03:07] - As with Basecamp and Hey, design consistency can emerge naturally.
[03:30] - David shares that large organizations typically use design systems to standardize processes.
[05:34] - Why it makes sense for individual designers to have ownership over the design process for small teams like 37signals.
[06:52] - Listener Paul asks how David and Jason resolve conflicts and make difficult decisions.
[07:02] - Jason explains conflicts are rare among the team and shares how they handle the things they don't agree on (without keeping score).
[08:18] - Why it's important to remember most decisions are temporary.
[08:59] - Jason shares an example of the rare occurrences when they might battle. [09:49] - Setting the standards for a smooth workflow.
[11:30] - David's philosophy: "A willingness to try anything as long as there's an expiration on the experiment and a way to tell whether it went one way or the other."
[12:55] - Jason explains why they don't need to consult each other for every decision—even the BIG ones, like leaving the cloud.
[14:28] - Prioritizing independence, competency, and TRUST.
[16:50] - Podcast listener Tim asks Jason and David to discuss 37signals' approach to product management and some of their methods over the years.
[17:20] - David shares how using software to gather and distribute information, allowing teams to make decisions, leads to everyone rowing in the same boat.
[20:19] - Jason adds that with two-person teams, there is a direct relationship between the programmer and designer, and management would get in the way.
[22:21] - Fighting hard against traditional managerial responsibilities because having managers invent work for other people can wreck a good thing (David and Jason only wear the hats of CTO and CEO occasionally).
[23:25] - 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 email.
Links and Resources:
Sign up for a 30-day free trial at Basecamp.com
HEY World | HEY
Leaving the Cloud | REWORK
Leaving the Cloud Part 2 | REWORK
Dev.37signals
37signals on YouTube
The REWORK podcast
The 37signals Dev Blog
@reworkpodcast on Twitter
@37signals on Twitter
In this episode of Rework, Jason Fried and David Heinemeier Hansson, co-founders of 37signals, join host Kimberly Rhodes to answer questions posed by Rework listeners.
Listen in as they share their insights and experiences in running a successful software company by answering questions from podcast listeners on topics such as 37signals' approach to design, decision-making processes, product management, and balancing managerial roles and responsibilities.
Tune in to hear their unique perspectives on these key aspects of building a successful software company.
Show Notes:
[00:23] - Noel asks David and Jason about their philosophy on design systems and using components instead of reinventing the wheel every time.
[01:01] - Jason explains that 37signals' website is a collection of ideas. The product itself is their design system.
[03:07] - As with Basecamp and Hey, design consistency can emerge naturally.
[03:30] - David shares that large organizations typically use design systems to standardize processes.
[05:34] - Why it makes sense for individual designers to have ownership over the design process for small teams like 37signals.
[06:52] - Listener Paul asks how David and Jason resolve conflicts and make difficult decisions.
[07:02] - Jason explains conflicts are rare among the team and shares how they handle the things they don't agree on (without keeping score).
[08:18] - Why it's important to remember most decisions are temporary.
[08:59] - Jason shares an example of the rare occurrences when they might battle. [09:49] - Setting the standards for a smooth workflow.
[11:30] - David's philosophy: "A willingness to try anything as long as there's an expiration on the experiment and a way to tell whether it went one way or the other."
[12:55] - Jason explains why they don't need to consult each other for every decision—even the BIG ones, like leaving the cloud.
[14:28] - Prioritizing independence, competency, and TRUST.
[16:50] - Podcast listener Tim asks Jason and David to discuss 37signals' approach to product management and some of their methods over the years.
[17:20] - David shares how using software to gather and distribute information, allowing teams to make decisions, leads to everyone rowing in the same boat.
[20:19] - Jason adds that with two-person teams, there is a direct relationship between the programmer and designer, and management would get in the way.
[22:21] - Fighting hard against traditional managerial responsibilities because having managers invent work for other people can wreck a good thing (David and Jason only wear the hats of CTO and CEO occasionally).
[23:25] - 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 email.
Links and Resources:
Sign up for a 30-day free trial at Basecamp.com
HEY World | HEY
Leaving the Cloud | REWORK
Leaving the Cloud Part 2 | REWORK
Dev.37signals
37signals on YouTube
The REWORK podcast
The 37signals Dev Blog
@reworkpodcast on Twitter
@37signals on Twitter
24分