I still have the notebook. The 2018 plan sits on page 47, each role written in the same blue pen, connected by straight lines like train stops. No erasures, no extra space.
Two years later an email landed about redesigning how volunteers passed curriculum between sessions. The description didn’t match anything on that page, so I closed it. The person who took the role later told me they had finished the work in six months and were already moving on to the next constraint no one had noticed.
My plan had taught me to wait for the next printed station. It never trained me to see the editable handoff sitting right in front of the tracks.
John Wesley’s three simple rules give a different lens. Do no harm. Do good. Stay in love with God. Wesley used them as daily constraints that anyone in the movement could apply without waiting for permission from the center. The rules did not prescribe outcomes. They kept the next action editable by the people closest to the work.
The plan that locked out the right next captain
I had written the five-year map after a promotion at a curriculum platform. The document assumed I would move from feature owner to group lead to director by a certain date, with specific products attached to each step. When an internal project surfaced that needed someone to hand curriculum ownership to volunteer teams without breaking their weekly rhythm, the map offered no category for it.
The person who stepped in instead treated the role as a temporary container. They set three constraints: the volunteer must finish the handoff in under seven minutes, the output must be printable without further edits, and the next volunteer must be able to change any line without asking permission. Within four months the completion rate for that curriculum doubled. My plan had no room for that kind of container because it measured progress by title sequence, not by whether the actual owners could still edit the work.
How Wesley’s rules expose the hidden constraint in long-horizon PM tracks
Wesley’s first rule, do no harm, translates directly to role design. A five-year plan that cannot be altered by the people who will live with the outcomes does harm by removing their agency before they arrive. The second rule, do good, requires that the next step produce something usable by the current owners rather than something that merely advances the planner. The third rule, stay in love with God, keeps the mission itself from becoming an idol that justifies locking the path.
Most PM career ladders still treat the next title as the measure. They ask for evidence of scope growth, headcount managed, and roadmap ownership. Those signals assume the mission stays the same shape. When AI changes the shape of the work faster than the ladder can update, the signals start rewarding people who protect the old map instead of the people who keep the actual work editable. The three rules surface the constraint because they force every role description to answer whether the next person can still change it without breaking the mission.
What changes when you treat every role as a three-rule loop instead of a title ladder
At one ministry product team the group lead stopped writing annual role charters. Instead each role carried the three constraints written on a single card: the output must remain changeable by the person who runs the session, the change must not increase time for the volunteer, and the mission metric must stay visible without extra reporting. The card could be rewritten by the volunteer owner at any time.
Within a quarter the same team had handed off two senior PM responsibilities to people who had never held the title. One person redesigned the print handoff process. The other built the check that prevented the agent from running a schedule when no one was watching. Neither move appeared on anyone’s five-year map, yet both moves kept the real owners in control of the outcome.
The pattern repeats when the rules stay short. A role becomes a loop that the next captain can still edit rather than a destination that must be defended. The ladder disappears because the measure is whether the constraint set remains small enough for the actual owner to rewrite it.
Your Turn: Apply This Today
- Take your current role description and delete every sentence that names a future title or scope level.
- Replace the deleted lines with exactly three constraints written so the person who will inherit the work can still change any one of them without your approval.
- Send the revised card to the two people who actually run the sessions or own the outcomes this week and ask them to strike or add one line.
- Schedule a thirty-minute review next week where those two people present the updated card and you only record what they changed.
- Apply the same three-constraint rewrite to one open role on your team before the next hiring conversation.
- Archive the original five-year plan document and replace it with a single note that lists only the three constraints active this quarter.
The same pattern shows up in how the agent kept running the schedule while no one was watching and in how the three-person pod still needed a fourth set of eyes to keep the handoff editable. Both cases turned on whether the people closest to the work could still change the constraint set without waiting for the original planner.
I consult with product leaders and ministry PMs on rewriting role constraints for AI speed, keeping handoffs editable by actual owners, and designing three-rule loops instead of title ladders. Let’s talk.
Discover more from Dr. Joshua Read
Subscribe to get the latest posts sent to your email.

