My Team Wont Take Our Rules Seriously

The podcast discusses the challenges of leadership, accountability, and process management within a family-owned heating and air conditioning company. The leader struggles to balance grace with accountability, particularly when team members ignore established processes - especially administrative tasks - despite existing documentation. A key issue is that employees often understand processes only in the context of correction, rather than being regularly reminded of their importance. This has contributed to a culture where compliance is reactive rather than proactive, and back-end work is frequently neglected compared to customer-facing responsibilities.

To address these issues, the discussion explores restructuring compensation to better align with desired behaviors. Currently, most pay comes from hourly wages, with job completion bonuses (SPFs) making up a smaller, inconsistent portion. A proposed shift would balance hourly and performance-based pay equally, incentivizing full job completion, including paperwork. This model aims to increase efficiency, improve adherence, and allow employees to earn more by meeting comprehensive job standards - all while staying within budget constraints. Emphasizing the "why" behind processes, clearly communicating expectations, and fostering a performance-driven culture are highlighted as essential steps toward building a sustainable, scalable business where employees are aligned with long-term goals.

• What if you redesigned your solo software project's task completion rewards to mirror a performance-based pay model?

  • Move: Shift from tracking hours or vague progress to defining clear, process-driven milestones (e.g., "deploy with full test coverage", "document API before merge") and tie each to a tangible reward - such as unlocking personal time, a bonus feature development day, or a monetary treat funded by your project revenue.

  • Why Now?: As a solo operator, you're prone to skipping non-customer-facing tasks (like documentation or testing) when under pressure - just like the HVAC team neglects back-end paperwork. With no one enforcing accountability, aligning compensation-like incentives with full-cycle delivery prevents drift and builds sustainable habits before scaling.

  • Expected Upside: You'll reduce technical debt accumulation, increase shipping consistency, and create a replicable model for future hires - all while reinforcing disciplined execution without external oversight.

• What if you conducted weekly solo retrospectives focused only on process adherence, not outcomes?

  • Move: Block 30 minutes weekly to review every skipped or shortcutted process in your workflow (e.g., skipping code reviews, delaying user feedback loops, omitting deployment checklists), and log each with a root cause and adjusted action step - even if the feature shipped fine.

  • Why Now?: Like Josh's team, you may follow customer-facing processes well but ignore internal ones that prevent long-term risk. Without proactive reinforcement, these gaps become systemic. Doing this now builds muscle memory for discipline before complexity increases.

  • Expected Upside: You'll catch compounding inefficiencies early, strengthen system reliability, and develop a culture of accountability in solitude - making future delegation or collaboration far smoother.

• What if you documented the "why" behind every core process in your software business - and revisited it monthly?

  • Move: Create a living document listing key workflows (e.g., release process, bug triage, customer onboarding) and for each, write a short narrative explaining its purpose: how it protects revenue, improves user experience, or reduces rework - then schedule a monthly reminder to reread and revise it.

  • Why Now?: The HVAC team ignored processes because they didn't grasp their importance beyond rule-following. As a solo developer, you risk the same disengagement when motivation dips. Reinforcing meaning sustains compliance during low-energy periods.

  • Expected Upside: You'll make better trade-offs under pressure, avoid cutting corners on high-leverage processes, and build a foundation for onboarding others - because you've already internalized the reasoning behind your systems.

• Review and revise your current compensation structure to tie a larger portion of pay to complete task delivery, not just hours worked, ensuring critical non-customer-facing work (like documentation) is incentivized.

• Document all core business processes with clear explanations of the "why" behind each step, then share these proactively - not during failures - to improve understanding and compliance.

• Run financial simulations in a spreadsheet before implementing new pay models to confirm they stay within labor budget constraints while increasing performance incentives.

• Shift from reactive process enforcement to regular, positive team discussions about procedures, emphasizing their impact on customer experience and business reliability.

• Identify one underperforming back-end process (e.g., paperwork completion), assign measurable outcomes, and pilot a bonus-based reward system to test behavioral change.