In this episode, host Clark Davis sits down with pediatric sleep and developmental specialist and kinesiologist Kelly Routkevitch to explore common infant and toddler sleep challenges.

If you've been looking for toddler sleep solutions, including night wakings, early morning wake-ups, co-sleeping transitions, and independent sleep struggles, this pediatric sleep consultant answers top community questions!

Welcome to the very first episode of the Space to Grow Together Podcast.

In this opening conversation, Sprout founder Clark Davis and Head of Marketing Danica Faber reflect on the experiences that shape growth. From stepping into new roles to learning through hands-on challenges, they share how discomfort often becomes the starting point for something meaningful.

Together, they explore what it means to create space for growth, both in business and at home, and within ourselves.
This episode sets the foundation for the podcast: honest conversations, a behind-the-scenes look at how things are made, and a goal of building a community that can grow together.

This episode of Space to Grow Together dives into the first phase of the ARCS framework: Awareness and Acknowledgement (the "A"). This step is foundational to successful improvement, aligning with the Visibility (V) step of the host's VCI (Visibility, Consistency, Improvement) framework.

The host emphasizes that the natural human inclination is to "work through" an issue or "brush past" an anomaly, often seen as heroic behavior. To implement ARCS, the organizational culture must shift to view the true heroic behavior as intentionally highlighting a failing—a gap between the expected outcome (mental model/hypothesis) and reality. This intentional stop and acknowledge process is key to learning from anomalies.

The philosophy is echoed in Lean thinking, which views problems as "jewels" and asserts that "no problem is a problem" (i.e., not escalating issues is the real problem). The primary role of management is simply to make problems clearly visible, as humans are inherently hardwired to solve visible problems.

To institutionalize this first step, organizations must build "red flag mechanisms" that make it easy for people to say, "I need your attention." Examples include:

• Andon: A signal (like a light, sound, or physical cord in a factory) that immediately brings attention to a problem.1 The host notes that the act of stopping the process (or "stopping the line") is a powerful mindset shift.

  
  

• Incidents: Logging every customer issue as an incident in customer service work.

• Feedback Systems: Customer and internal surveys, though the host hopes the Andon system catches issues earlier than a formal grievance process.

• Dedicated Ticket Streams: In their system, this is a dedicated "Andon" stream tied to immediate notifications for key personnel (like engineers or line leads).

The host, as a leader, makes it a priority to respond quickly to these signals, getting directly involved to ensure the team has a viable path forward for root cause analysis.

Bringing an out-of-standard condition into the light provides several critical benefits:

1. Shifts Mindset from Dread to Action ("Name It to Tame It"): Issues that live in the "underground" or "subconscious" create dread. Naming and acknowledging them shifts the issue from something to fear into a problem that can be dealt with via a clear course of action.

2. Allows a Change in Success Metrics:

   • The act of signaling an Andon shifts the work from Brown Work (value-adding, efficiency-focused, day-to-day tasks) to Red Work (problem-solving, issue resolution).

   • Success in Brown Work is efficiency; success in Red Work is gaining understanding and improving the system.

   • Acknowledgeing the shift is vital because it stops the clock on efficiency metrics for that task, allowing people to focus on solving the problem without being penalized for taking time to stop and fix the process.

3. Brings Needed Resources: The "red flag" acts like the biological response to seeing blood—it instantly focuses attention and resources on the area of distress (the failing system).

The host stresses that culture is the biggest barrier to implementing this first step. The natural human tendency is to hide or work through issues. Developing a successful "A" step requires:

• Core Values: Reinforcing values like transparency and reflection that value people bringing up issues.

• Moving Beyond "Get 'er Done": The powerful urge to just "pound through" issues has short-term benefits but wears people down and causes long-term issues to be hidden.

• Understanding the Investment: Acknowledging an issue is an investment; it almost never pays off immediately but yields greater long-term efficiency and improvement.

The most crucial element for sustaining the "A" step is the response: The value of the response (the R step) must consistently outweigh the effort or discomfort it takes for people to signal the problem.

This episode of Space to Grow Together, the workplace edition, introduces the ARCS framework, a foundational four-phase process used at Sprout to handle the inevitable issues that arise from new innovations and turn "deep chaos" into sustainable order.

The host presents ARCS as an approachable sequence that synthesizes key principles from Lean methodology, including root cause analysis, PDCA (Plan-Do-Check-Act), SDCA (Standardize-Do-Check-Act), standard work, and countermeasures. The framework's core purpose is to achieve daily management or consistency after a major innovation (Hoshin), preventing the gains from being lost and creating a stable system (VCI: Visibility, Consistency, Innovation).

ARCS is designed for situations where simple solutions aren't quickly apparent and an unexpected problem requires deep analysis and resolution. It's presented not just as a process, but as a repertoire of skills, behaviors, and reflexes for turning chaos into order and learning from it.

The ARCS framework is an acronym for four phases:

1. A - Awareness and Acknowledge (Goal: Visibility):

   • Focus: Bringing visibility to an issue and openly acknowledging it. This requires a cultural shift to embrace problems as "jewels" and opportunities to learn, moving away from the natural human inclination to hide issues or immediately blame others.

   • Pitfall to Avoid: Blaming individuals; the focus must be on the process.

   • Lean Principle: Andon (a system to signal a problem).1

     
     

2. R - Response and Root Cause (Goal: Scientific Method):

   • Focus: A quick response team must affirm the person escalating the issue, and then assist in finding the root cause. Responders must be capable of guiding the team through scientific inquiry (like the 5 Whys).

   • Pitfalls to Avoid:

     • Assuming the cause is known (e.g., mistaking the same symptoms for the same cause).

     • Only scraping the surface-level cause and failing to find the ultimate, deeper cause.

3. C - Countermeasure and Confirm (Goal: Validation):

   • Focus: Implementing countermeasures (viewed as possible solutions, not final solutions) and confirming their effectiveness.

   • Confirmation requires observing two things:

     1. The countermeasure does what was intended.

     2. It does not introduce unintended consequences.

   • Key Distinction: The host notes a growing appreciation for the value of short-term countermeasures alongside long-term ones, provided their use is fully understood and not abused.

4. S - Standardize and Share (Goal: Sustained Gains):

   • Focus: Turning confirmed countermeasures into structure, systems, and processes with a long half-life. This prevents organizational amnesia (returning to the same problem later).

   • Process: Incorporating the fix into documentation, training, and overall processes so it is wholly adopted. Sharing the learning is a high-yield, low-effort part of this step.

   • Result: Standardization sets the foundation for the next wave of innovation, as it resolves current issues and frees the team to see the "next hill crest" or challenge.

The host cautions that while ARCS is presented as a linear process, it's intended to be deeply iterative and fractal. Ultimately, the goal is for ARCS to become an instinct—a set of internalized principles and habits that shift from a structured process into an art for creating immense value in response to chaos.

Clark dives into how we use the value stick to understand value and design. This episode includes a discussion of:

• What is Customer Utility
• How we see resources consume
• Value as Surplus Utility
• Design as the processes of innovating new solutions to customer needs that provider greater utility or lower resource consumption for increased value. Synergy is a major component
• A look at the entire system and sharing surplus value

In this episode we explore the layered motivations for creating a structure for standardization and innovation, ultimately leading to greater individual growth.

Clark also overviews topics we will cover in future episodes.

In this first episode, explain a few (probably not all) of the reasons for creating this podcast, and what to expect (as far as I can see now, which is certain to change).

• To just get started. The host admits he doesn't have a clear plan for the format and believes the best way to figure it out is to begin the process.

• To create a format for personal reflection. The host explains that writing and journaling are too slow for his thought process, possibly due to dyslexia. He hopes that the audio format will allow him to "strike while the iron is hot" and better process his thoughts and creative ideas.

• To facilitate meaningful conversations. The host expresses a desire for long-form dialogue and believes social media and short-form content lack the nuance needed for genuine connection. He hopes the podcast will encourage listeners to engage in deeper conversations.

• To serve as an internal training tool. The host plans to use the podcast to share discussions and ideas with his employees. He finds that written training materials can be difficult for some people to access and videos are often inconvenient to watch. He believes an audio format will make this content more accessible for his team, especially during tasks like driving or production work.

• To process a wide range of topics. The host acknowledges that this may be a "bad practice" for podcasts but states that he will cover various topics in one show, rather than creating multiple podcasts. He plans to cover a mixed bag of content for employees, customers, and friends, and he will title the episodes clearly so listeners can choose which ones to tune in for.