Episode Overview

Podcast: At Work with The Ready
Episode: AUA: How To Design a Startup OS From Scratch?
Hosts: Rodney Evans and Sam Spurlin
Date: January 19, 2026

Theme:
This listener-submitted AUA (Ask Us Anything) episode tackles the foundational question: "How would you design an organizational operating system (OS) from scratch for a brand new company?" Drawing from their extensive experience in helping organizations rethink how they work, Rodney and Sam offer practical advice for intentionally building systems, rhythms, and structures—without overengineering from the outset.

Key Discussion Points & Insights

1. Start Small: Resist Over-Designing Your Org OS

• Both hosts emphasize not to overcomplicate things at the beginning.
• Sam's Principle: "Resist the urge and keep the phrase minimum viable everything in your head." (00:36)
• The team should avoid creating elaborate systems for hypothetical problems; build structures as real tensions or challenges surface.
• Rodney’s Advice: "Wait until it hurts—don't try to do stuff until there is a shared, recognized pain caused by its absence." (01:45)
• Overproduction of frameworks or scaffolding is a common smart-person trap, often creating unnecessary work and confusion.

2. Defaults: One Size Does Not Fit All

• There's a danger in developing universal systems for everyone, as needs differ by team or role.
• Rodney shares a story of a client who built an impressive but overly general strategy framework, which ultimately didn't fit everyone’s needs.
• Rodney: "There is no one size fits all in Org design. There are defaults that you can start from, but they are inevitably going to be adapted based on what the work is to be done." (03:18)

3. Establish A Lightweight Operating Rhythm

• Early focus should be on creating a simple, sustainable cadence for reflection and adaptation.
• Sam: "...get your default operating rhythm up and running immediately. Some sort of cadence: regular strategy conversations, a regular cadence on retros..." (03:54)
• Even solo founders can benefit from self-reflection meetings (e.g., weekly action planning).

4. Non-Negotiables: Kanban, Operating Rhythm, and Experimentation

• Rodney: "The three things that I don't understand how companies live without are some kind of Kanban board... a backlog... and you got to have an operating rhythm." (04:39)
  • Kanban Board: Visualize workflow—absolute must-have for context switching and prioritization at any stage.
  • Backlog: To prevent losing track of tasks and priorities.
  • Experimentation Template: A simple proposal method and a means for team consent help institutionalize safe-to-try experiments.
• Rodney: “Just make one. Also, I can't live without a backlog, you guys. ... Got to have an opera them.” (05:06)

5. Strategy: Sky-Sensing Before Grand Plans

• The hosts distinguish between high-detail planning (usually unnecessary at the start) and “sky-sensing”—the practice of regularly stepping back to observe external trends and environmental context.
• Sam: "It's really important to build the muscle early that we're looking at the sky and that we're talking about it." (07:22)
• Detailed planning is less valuable than cultivating the habit of collectively noticing and discussing the outside world and its possible impacts.
• Rodney: "People want to start with the plan, but actually getting really good at talking about the environment makes the planning a lot, a lot easier." (08:20)

6. Strategy vs. Planning—They're Not the Same

• The hosts caution against conflating "strategy" with detailed operational planning.
• Sam: "Planning and strategy work are two different things and different conversations." (09:11)
• Many teams confuse the two, which undermines both efforts.

Notable Quotes & Memorable Moments

• Sam Spurlin [00:36]:
  "Resist the urge and keep the phrase minimum viable everything in your head."

• Rodney Evans [01:45]:
  "Wait until it hurts—don't try to do stuff until there is a shared recognized pain caused by its absence."

• Rodney Evans [03:18]:
  "There is no one size fits all in org design. There are defaults that you can start from, but they are inevitably going to be adapted based on what the work is to be done."

• Rodney Evans [04:39]:
  "The three things that I don't understand how companies live without are some kind of Kanban board... a backlog... and you got to have an operating rhythm."

• Sam Spurlin [07:22]:
  "It's really important to build the muscle early that we're looking at the sky and that we're talking about it."

• Rodney Evans [08:20]:
  "People want to start with the plan, but actually getting really good at talking about the environment makes the planning a lot, a lot easier."

• Sam Spurlin [09:11]:
  "Planning and strategy work are two different things in different conversations."

Important Segment Timestamps

• 00:20 – Listener question introduction: How to design an org OS from scratch?
• 00:33-01:45 – Sam and Rodney on resisting overdesigning and embracing "minimum viable everything"
• 03:18 – The dangers of universal frameworks and need for adaptation
• 03:49-05:44 – The essential first steps: establishing operating rhythm, Kanban, backlog, and experiment methodology
• 07:04-09:11 – The value of sky-sensing (sensing the environment) and the distinction between strategy and planning
• 09:37 – Rodney on facilitating sky sessions and why they're crucial (with a plug for The Ready's offerings)

Conclusion

Rodney and Sam distill decades of experience into a clear philosophy:

• Don’t overbuild—start with the minimum viable systems.
• Let real, shared pain points drive process and system development.
• Set early habits around rhythm, visual workflow, and scanning the environment.
• Continuously adapt, rather than seeking one-size-fits-all solutions.
  By focusing on these principles, founders can lay solid groundwork without accidentally creating bureaucracy or complexity before their company truly needs it.