The career question product managers keep asking me after the promotion lands is whether the new title actually expands what they can decide without approval, and it is a career question no raise answers on its own. The answer is no, not unless the scope of their circle of competence has also moved outward in concrete ways.
Most keep measuring progress by the old markers—headcount, budget line, and the size of the roadmap they inherit. Those markers no longer track real ownership once AI tools compress the time between idea and shipped feature.
The Career Question When Compensation and Scope Drift Apart
The promotion conversation usually ends with a number and a new business card. What it rarely surfaces is whether the person now owns decisions that used to sit two layers above them. In practice the gap shows up six months later when an AI-generated prototype lands on their desk and they realize they still need three sign-offs before they can run it with real users.
This mismatch is not unique to faith-tech, but it appears faster here because the user base is smaller and the success metrics are softer. A children’s ministry volunteer who prints a lesson on Tuesday does not file a support ticket when the experience feels off—she simply stops coming back. The PM who cannot change the print layout without another round of reviews never learns what that volunteer actually needed.
Gallup’s research on what actually drives engagement at work reframes this career question well. Charlie Munger’s circle of competence is useful here because it forces the question away from title and toward boundary. Munger described the circle as the area where you can make decisions with high accuracy because you have seen the patterns before. Outside that circle, even smart people produce expensive errors. The promotion does not enlarge the circle; deliberate work does.
Circle of Competence Applied to AI Product Roles
In AI-era product work the boundary matters more because models now generate options faster than teams can evaluate them. A PM whose competence stops at writing requirements will green-light features that look good in a demo and fail with the smallest churches. The PM who has spent time watching volunteers navigate the same workflow on paper knows which generated option will actually survive contact with a seven-minute prep window.
Expanding the circle requires choosing a narrow slice and owning the outcome end to end. At one ministry tool I watched a PM take responsibility for the entire flow from volunteer signup to lesson completion. She removed three internal review steps and measured only whether the printed page reached the classroom. Usage rose because she had narrowed her circle to something she could actually judge without waiting for data that never arrived in time.
The same pattern holds for larger platforms. When the team at a high-traffic Bible site decided to test an AI-assisted reading plan, the PM who succeeded was the one who had previously owned the print PDF version used by small groups. She already knew which formatting constraints mattered. The model suggestions were filtered against that lived constraint rather than against abstract engagement metrics.
The Career Question the Old Faith-Tech Playbook Cannot Answer
The inherited playbook says move up by managing larger teams and bigger roadmaps. In ministry tools that path often leads to more meetings and less contact with the actual user. The volunteer who prepares a lesson in a church basement does not care about the PM’s headcount; she cares whether the material fits on one page and survives a spilled coffee cup.
AI accelerates the break because it removes the old friction of building. A feature that once took a quarter can now ship in a week. The limiting factor becomes judgment about whether the feature should ship at all. That judgment only improves inside a competence circle that includes direct observation of the user under real constraints.
Teams that keep promoting on the old signals end up with leaders who can describe strategy but cannot tell whether a generated outline will work for a volunteer with no formal training. The organizations that notice the drift are the ones that start asking different questions in promotion reviews: what specific decision boundary has this person moved in the last twelve months, and what evidence shows the boundary is now reliable.
Your Turn: Apply This Today
- List every current project and mark the single decision on each that you cannot make without another person’s approval; choose one to own fully this quarter.
- Shadow one user completing their actual task with the current product for at least ninety minutes and record the exact moment they adapt or abandon the flow.
- Write a one-paragraph definition of the competence boundary you claim today and share it with your manager before the next role conversation.
- Run one AI-generated option through your existing user constraint set and reject it on paper before any build work begins.
- Identify the last three features that shipped under your name and note whether you personally observed the user outcome or relied on secondhand reports.
- Schedule a thirty-minute review with a peer PM who works on a different product line and compare where each of you can act without escalation.
The CPO Who Captured What the Spreadsheet Missed and The CPO Who Started Asking What Kept Her Volunteers Up both trace the same pattern: real ownership grows only after someone redraws their own competence boundary.
I consult with mid-career product leaders on mapping competence boundaries, AI-era role decisions, and ownership growth in mission-driven tools. Let’s talk.