Early in leadership, I responded to uncertain work by mapping every step. The team learned to wait for me. People brought decisions upward, updates arrived after I asked, and I became the owner of projects I had assigned to someone else.
The pattern changed when I treated accountability as an agreement made before the work begins. That agreement needs five parts:
- an outcome that defines success
- authority to make the required decisions
- constraints, dependencies, and standards
- checkpoints that expose progress and risk
- consequences when commitments repeatedly break
“Own the launch” leaves all five open. A useful agreement names the release criteria, decision rights, dependencies, and the date when risk must be raised. Ask the owner to explain the plan in their own words. Different assumptions will surface before implementation makes them expensive.
Ownership needs room to decide. If five people can reverse the owner’s choices, the role becomes coordination without authority. Define which decisions need consultation, which need approval, and which belong to the owner.
Managers provide product context, technical constraints, and access to people who can remove a block. When someone brings a problem, I ask what happened, which options they considered, and which one they would choose. I also ask what support changes the outcome, when the next update will arrive, and what they will change in the next cycle. The answers reveal judgment and create a clear next commitment.
Feedback needs to arrive while the project can still recover. Use the smallest conversation that can correct the pattern.
Begin with the observation:
The update arrived after the deadline. What happened?
Name the repeated behavior and its effect:
Risk has surfaced late three times. Late warnings force the team to replan.
Set the expectation and consequence:
Raise risk as soon as the date becomes uncertain. Another late warning will change the scope of your role.
Labels such as “be proactive” or “show more ownership” give a person no useful action. “Send the update by Tuesday and list unresolved dependencies” names the action, timing, and expected result.
A missed promise can come from a dependency, weak estimate, unclear priority, personal difficulty, missing skill, or poor follow-through. Find the cause, repair the effect, and define the next owner. A dependency may need escalation. A planning gap may need coaching. Repeated execution failure after clear support may need a role change.
Write down decisions when consequences become material. A shared record helps the person, manager, and team work from the same facts.
When several capable people repeat the same behavior, inspect the environment. People may avoid decisions because earlier decisions were reversed. They may hide risk because every update creates a new priority. They may miss dates because the company calls every project urgent.
Managers own the clarity of direction, quality of feedback, and incentives created by the system. Review those conditions in project retrospectives and one-to-ones. Change a process that keeps producing the same failure.
Accountability grows when people know what they own, when risk should surface, what support is available, and how consequences will follow.