--- title: "Knowing Isn't Enough | SPMS Insights" description: "Paul Smith explains why understanding project problems is not enough, and why effective leadership depends on consistent action, behavior, and execution habits." lang: en json-ld: | [ { "@context": "https://schema.org", "@type": "ProfessionalService", "name": "Smith Project Management Services, LLC", "description": "Independent advisory led by Paul Smith, advising leadership on complex project recovery, risk identification, organizational effectiveness, and contract and project execution oversight.", "url": "https://www.smithprojectmanagement.com", "telephone": "+1-941-812-7035", "address": { "@type": "PostalAddress", "addressRegion": "FL", "addressCountry": "US" }, "areaServed": "United States", "priceRange": "$$$$", "founder": { "@type": "Person", "name": "Paul Smith", "jobTitle": "Founder & Principal Consultant" }, "knowsAbout": [ "Project Recovery", "Independent Project Oversight", "Risk Identification", "Organizational Effectiveness", "Contract and Scope Oversight", "Nuclear Decommissioning Oversight", "Construction Project Leadership" ], "hasCredential": [ { "@type": "EducationalOccupationalCredential", "credentialCategory": "Professional Certification", "name": "Construction Health and Safety Technician (CHST)" }, { "@type": "EducationalOccupationalCredential", "credentialCategory": "Professional Certification", "name": "Safety Trained Supervisor-Construction (STS-C)" } ] }, { "@context": "https://schema.org", "@type": "Article", "headline": "Knowing Isn't Enough", "description": "Paul Smith explains why understanding project problems is not enough, and why effective leadership depends on consistent action, behavior, and execution habits.", "articleSection": "Insights & Perspectives", "author": { "@type": "Person", "name": "Paul Smith" }, "publisher": { "@type": "Organization", "name": "Smith Project Management Services, LLC" }, "mainEntityOfPage": "https://www.smithprojectmanagement.com/insights/knowing-isnt-enough", "url": "https://www.smithprojectmanagement.com/insights/knowing-isnt-enough" }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.smithprojectmanagement.com/" }, { "@type": "ListItem", "position": 2, "name": "Insights", "item": "https://www.smithprojectmanagement.com/insights" }, { "@type": "ListItem", "position": 3, "name": "Knowing Isn't Enough", "item": "https://www.smithprojectmanagement.com/insights/knowing-isnt-enough" } ] } ] --- [![Smith Project Management Services, LLC](/assets/spms-logo-Cm2mE7fh.png)](/) [About](/#about)[Services](/#services)[Experience](/#experience)[Credentials](/#credentials)[Insights](/insights)[Contact](/#contact)[Get In Touch](/#contact) [Home](/)[Insights](/insights)Article No. 016 ![Smith Project Management Services, LLC](/assets/spms-logo-Cm2mE7fh.png) Smith Project Management Services, LLC Insights & Perspectives Series • Article No. 016 Knowing Isn't Enough [Back to Insights](/insights) # Knowing Isn't Enough Over the past fifteen articles, I've written extensively about why projects succeed, why they fail, and the patterns that consistently separate the two. We've explored alignment, oversight, organizational culture, institutional knowledge, emerging risk, normalization of deviance, respect for the process, communication, and decision making. If there's one conclusion I've reached after writing those articles, it's this: Understanding the problem doesn't solve the problem, and recognizing the warning signs doesn't automatically change the outcome. Knowledge is valuable - Action is transformational. Throughout my career, I've worked with organizations that clearly understood what good project execution looked like. They had; - • Experienced people. - • Well-written procedures. - • Detailed schedules. - • Lessons learned. - • Risk registers. - • Dashboards. - • Metrics. The knowledge was there, yet many of those same organizations continued to struggle with the same recurring issues. Why? Because understanding what should happen isn't the same as consistently doing it, and knowing the right answer has never guaranteed the right decision. I've also worked with organizations that weren't necessarily more experienced or more technically capable. What made them different wasn't what they knew, it was how they behaved. They; - • Consistently demonstrated habits that strengthened execution. - • Asked better questions. - • Challenged assumptions. - • Encouraged difficult conversations. - • Clarified expectations. - • Listened to the people performing the work. - • Respected proven processes. - • Recognized emerging problems while they were still manageable. None of those behaviors were dramatic, and most weren't complicated. But they were intentional, and they happened consistently. Looking back, I don't think successful organizations possess some secret knowledge that struggling organizations lack. I think they consistently apply principles that others understand but fail to practice. That realization has changed the way I think about leadership. Leadership isn't simply making decisions. It's creating an environment where good decisions become more likely, and creating conditions where people understand the work, communicate openly, challenge assumptions respectfully, and solve problems before they become crises. In other words... Leadership isn't about controlling execution, it's about influencing the behaviors that determine execution. That's why I've intentionally spent the first fifteen articles focusing on observation rather than instruction. Before discussing solutions, I believed it was important to first understand the recurring patterns. - • Why projects drift. - • Why communication breaks down. - • Why organizations normalize small deviations. - • Why institutional knowledge matters. - • Why oversight is often misunderstood. Those observations created the foundation. Now it's time to build on it. Beginning with my next article, I'm going to shift from observation to application. Instead of asking, "Why do projects struggle?" I'll begin answering a different question: "What do effective leaders consistently do that helps projects succeed?" These aren't theories, and they're not management concepts borrowed from a textbook. They're practical principles I've relied on throughout my career—first as a craftsman, then as a supervisor, construction manager, and oversight professional. They've been shaped by successful projects, refined by difficult ones, and occasionally learned the hard way. …I simply call them my Rules of Engagement, and I hope you enjoy learning about them. [Back to Insights](/insights) [Previous Article The Pattern Behind Every Successful Project ](/insights/the-pattern-behind-every-successful-project)[Next Article Rule #1: Understand Craft Needs ](/insights/rule-1-understand-craft-needs) ## Related Consulting Capabilities Explore consulting capabilities related to the project and organizational issues discussed in this article. [Leadership Assessment ](/#services)[Project Oversight ](/#services)[Project Recovery ](/#services)[Safety Program Development ](/#services)[Schedule Analysis & Review ](/#services)[Contract & Scope Development ](/#services) For more insights from Paul Smith, connect with him on LinkedIn. [Connect on LinkedIn](https://www.linkedin.com/in/paul-smith-chst-sts-c-1514b414) ## Need an Experienced Perspective on a Complex Project? Smith Project Management Services advises leadership on project risk, organizational effectiveness, contract oversight, and recovery before issues become failures. [Start a Conversation](/#contact) Smith Project Management Services, LLC Project Oversight, Recovery, and Organizational Effectiveness Paul Smith | Principal Consultant CHST · STS-C · OSHA Authorized Construction Trainer © 2026 All rights reserved. Powered by [Periscope Promotions](https://www.periscopepromotions.net)