In this episode, hosts Jeff Sample and Nathan Wood sit down with Bryan Guess to explore one of the most overlooked challenges in construction, technology, and business operations: mistaking symptoms for root causes. Drawing from his experience, Bryan explains why organizations often jump straight to solutions without first understanding the real problem they're trying to solve. The conversation explores systems thinking, organizational accountability, communication breakdowns, technology adoption, and why most operational problems are ultimately people and process problems.
Bryan Guess is the founder of Bartizan Strategic Group, a consulting firm focused on helping organizations diagnose operational challenges, improve business systems, and solve complex organizational problems. Prior to launching Partizan, Bryan spent over a decade working with commercial building owners and AEC stakeholders, where he discovered that many challenges attributed to construction, engineering, or technology are actually universal business problems involving people, processes, incentives, and communication.
Key Takeaways
- Why organizations often prescribe solutions before fully understanding the problem.
- How authority, accountability, and communication create recurring project failures.
- Why technology and software are rarely the root solution to operational challenges.
- How systems thinking can uncover hidden organizational inefficiencies.
- Practical ways to diagnose recurring business and project problems before investing in new tools or processes.
Timestamps
[00:00] - Episode Teaser
[03:56] - Bryan's Journey from Building Consulting to Business Consulting
[05:21] - Universal Business Problems Across Industries
[07:11] - Systems Thinking, Shared Language, and Organizational Diagnostics
[10:34] - Authority, Accountability, and Why Projects Break Down
[15:07] - Technology Isn't a Magic Bullet
[19:15] - Diagnosing Before Prescribing Solutions
[30:53] - Lessons Learned, Repeatability, and Improving Project Systems
[37:15] - Communication Systems, Software Creep, and Operational Complexity
[46:11] - Final Advice: Stay Curious and Challenge Assumptions
Follow Bryan Guess:
Follow the Hosts:
Follow The ConTech Crew:
