How to prevent blind spots in your SOX program Make sure someone’s holding the flashlight. The Business Process Owner isn’t just running the process. They’re the one holding the flashlight 🔦 —illuminating what others might overlook. Here’s how they bring key COSO principles to life: 🔦 Principle 4 – Competence They make sure the right people are in the right roles—trained, supported, and aligned with process objectives. 🔦 Principle 7 – Risk Identification They identify where the process could break down and ensure those exposures are understood and addressed. 🔦 Principle 9 – Change Management They assess when changes to the business, systems, or team could impact internal control—and take action. 🔦 Principle 10 – Control Design They help ensure the right control activities are in place—and that they actually reduce the likelihood of failure. The control owner executes the control. The business process owner makes sure it works in context. If your SOX program feels reactive or unclear— you don’t need more controls. You need better visibility. What's your experience with the role of Business Process Owner? Lets start the conversation in the comments 👇
Really love the flashlight analogy — great way to describe the role of the Business Process Owner. It’s not just about executing controls, it’s about seeing the bigger picture: risks, changes, and design gaps that others might miss. Great reminder that visibility and ownership are just as important as the controls themselves.
I think many Control Owners want to do the right thing, but juggling their own workload, not having control responsibilities as a top responsibility in their performance evaluation / annual goals, working with faulty or legacy technology, and not having a supportive 2nd or 3rd function helpiing comply with SOX make it difficult to perform controls as expected and needed. Great conversation Ryan Godbey, CPA.