--- title: "Leadership Rule #9: Stay in Your Role | SPMS Insights" description: "Paul Smith explains why role discipline matters on high-performing projects and how clear authority, accountability, and ownership improve execution." 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": "Leadership Rule #9: Stay in Your Role", "alternativeHeadline": "Why Role Discipline Matters on High-Performing Projects", "description": "Paul Smith explains why role discipline matters on high-performing projects and how clear authority, accountability, and ownership improve execution.", "articleSection": "Insights & Perspectives", "author": { "@type": "Person", "name": "Paul Smith" }, "publisher": { "@type": "Organization", "name": "Smith Project Management Services, LLC" }, "mainEntityOfPage": "https://www.smithprojectmanagement.com/insights/leadership-rule-9-stay-in-your-role", "url": "https://www.smithprojectmanagement.com/insights/leadership-rule-9-stay-in-your-role" }, { "@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": "Leadership Rule #9: Stay in Your Role", "item": "https://www.smithprojectmanagement.com/insights/leadership-rule-9-stay-in-your-role" } ] } ] --- [![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. 025 ![Smith Project Management Services, LLC](/assets/spms-logo-Cm2mE7fh.png) Smith Project Management Services, LLC Insights & Perspectives Series • Article No. 025 Leadership Rule #9: Stay in Your Role Why Role Discipline Matters on High-Performing Projects [Back to Insights](/insights) # Leadership Rule #9: Stay in Your Role ## Why Role Discipline Matters on High-Performing Projects Every successful project depends on people understanding two things clearly: what they are responsible for—and what they are not. That sounds simple, but in practice, it can be one of the most difficult disciplines for a project team to maintain. Projects bring together people with different backgrounds, expertise, personalities, levels of authority, and experiences. Good people want to help. Experienced people have opinions. Leaders want problems solved, and when schedules tighten or problems arise, the natural tendency is for people to step in. Sometimes that’s exactly what a project needs, but there’s a significant difference between being engaged and taking over someone else's role. Over the years, I've seen plenty of examples: - • Project managers trying to be engineers. - • Engineers trying to direct construction. - • Safety professionals trying to run the project. - • Craft personnel making design decisions. - • Executives bypassing the chain of command to solve field issues. In most cases, the intentions weren't bad. People believed they were helping, but the results often said otherwise. ## Roles Exist for a Reason Defined roles aren't bureaucratic boxes on an organization chart. They establish something every successful project needs: Accountability. Someone must ultimately; - • Own the decision. - • Be responsible for the engineering. - • Own construction execution. - • Establish and enforce safety requirements. - • Manage cost and schedule. - • Decide whether the work meets the project's requirements. When those responsibilities become blurred, accountability becomes blurred with them. And when everybody owns a decision, quite often nobody really owns it. That's when projects begin experiencing conflicting direction, duplicated effort, delayed decisions, frustrated team members, and the inevitable question after something goes wrong: "Who authorized this?" If the answer requires a twenty-minute explanation, the project probably had a role-discipline problem long before the event occurred. ## Collaboration Doesn't Mean Taking Ownership Staying in your role does not mean staying in your lane with your head down. High-performing teams don't operate in silos, they; - • Communicate. - • Challenge assumptions. - • Identify risks. - • Offer alternatives. - • Ask difficult questions. - • …And when they see something that doesn't look right, they speak up. The distinction is what happens next. An experienced construction manager should absolutely challenge an engineering decision that appears difficult or impossible to build. That doesn't make the construction manager the engineer. An engineer should absolutely raise concerns about how work is being performed in the field. That doesn't make the engineer the superintendent. Everyone – NOT just the safety professional - should stop work when an unsafe condition exists and ensure the appropriate requirements are followed. And senior leadership should absolutely remain informed about important field issues. That doesn't mean executives should bypass the project organization and begin directing individual work activities. Expertise gives you a voice. It doesn't automatically give you ownership. ## Authority and Accountability Must Stay Connected One of the most damaging situations on a project occurs when responsibility sits with one person while someone else exercises the authority. - • If a project manager is going to be held accountable for the project's outcome, that project manager must have reasonable authority to manage it. - • If an engineer is responsible for the technical adequacy of a design, technical decisions shouldn't be casually overridden by people who don't own that responsibility. - • If a construction manager is accountable for field execution, multiple people shouldn't be independently directing the workforce. Separating authority from accountability creates an impossible situation: One person makes the decision. Someone else gets held responsible for it. That isn't accountability - It's organizational dysfunction. Strong leaders recognize this and resist the temptation to solve every problem personally. They make sure the right person owns the problem, provide that person with the resources and support needed to solve it, and then hold them accountable for the result. ## When You See a Problem Seeing something outside your area of responsibility doesn't mean ignoring it. Quite the opposite. When you identify a problem: - • Involve the right people. - • Bring the issue to the individual who owns it. - • Offer your perspective. - • Experience from another discipline can expose risks the responsible person hasn't considered. - • Ask questions. - o A good question can be more valuable than an unsolicited solution. - • Raise concerns when necessary. - o Professional disagreement is healthy. Silence in the presence of a known risk isn't. - • Escalate when appropriate. - o If an issue presents a serious safety, quality, regulatory, cost, or schedule risk and isn't being addressed appropriately, escalation may be necessary. But throughout that process, remember the distinction, and don't confuse being engaged with taking over. ## Role Discipline Is a Leadership Behavior This becomes especially important as people move higher in an organization. The more senior the position, the easier it becomes to unintentionally override the people below it. A comment from a senior executive may be interpreted as direction. A suggestion may suddenly become a requirement. A question asked in the field may result in someone changing work simply because of who asked it. Good leaders understand the weight their position carries. They don't demonstrate leadership by inserting themselves into every decision. They demonstrate it by creating an organization capable of making good decisions without requiring them to personally make every one. That means establishing clear ownership, respecting decision rights, demanding collaboration, and intervening when necessary—without becoming the unofficial project manager, engineer, superintendent, or foreman. ## High-Performing Teams Know Who Owns the Decision The best project teams I've worked with weren't teams where everyone agreed. They were teams where people could disagree openly, challenge assumptions, contribute expertise, and raise concerns without creating confusion about who ultimately owned the decision. Everyone had a voice. But not everyone had the same role. That distinction matters, because role discipline isn't about protecting one’s turf, it's about preserving accountability. It's about making sure decisions are made by the people best positioned—and authorized—to make them. And it's about creating a project organization where people can contribute everything they know without undermining the responsibilities of the people around them. Know your role. Respect everyone else's. Support the team. That's how accountability—and great projects—are built. [Back to Insights](/insights) [Previous Article Leadership Rule #8: Adhere to the Schedule...or Change the Schedule ](/insights/leadership-rule-8-adhere-to-the-schedule-or-change-the-schedule)[Next Article Leadership Rule #10: Speak Positively About the Team and the Team Members ](/insights/leadership-rule-10-speak-positively-about-the-team-and-the-team-members) ## 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)[Schedule Analysis & Review ](/#services)[Contract & Scope Development ](/#services)[Safety Program 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 experienced guidance for a complex project? SPMS helps organizations strengthen oversight, safety, leadership, and project performance. [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)