The real problem for mid-career product leaders in faith-tech is not a shortage of opportunities. It is the way title signals continue to steer decisions once basic security is in place.
Those signals reward scope expansion and visible ownership even when the actual work no longer matches the leader’s wiring. The result is steady progress on paper and quiet erosion of the judgment that made the earlier work durable.
This misread shows up most clearly when a product leader chooses the next role because it adds “director” or “head of” rather than because it tightens the fit between their strongest pattern of attention and the users who need that pattern most. The pattern repeats across teams that serve pastors, volunteers, and ministry directors. Each move looks like advancement. The underlying product judgment narrows.
John Wesley framed three simple rules for ordering life and work: do no harm, do good, and attend to the ordinances of God. The third rule is the one most product leaders quietly drop once titles become the scorecard. It asks whether daily attention is still ordered toward the practices that keep judgment clear. In product terms, that means checking whether the work still surfaces real user friction faster than internal politics.
Signal chasing crowds out the real user
A product leader who moves for the title often inherits a roadmap already shaped by the last person’s incentives. The new scope feels like progress until the first user interview reveals that the previous team never spoke with the 7-minute volunteer who prints curriculum on Thursday night. The signal was satisfied. The constraint that actually determines retention stayed invisible.
At SermonCentral the teams that stayed longest with children’s ministry directors learned to measure success by whether a volunteer could finish the lesson plan without opening another tab. Leaders who chased platform scope instead spent quarters aligning with marketing calendars that had nothing to do with print-first constraints. User completion rates flattened while title counts grew.
The pattern repeats when a faith-tech PM joins a larger platform to own “strategy” only to discover the real constraint is distribution to churches that still decide tools by whether the children’s director’s inbox can absorb one more weekly email. Title signals do not surface that constraint. Direct observation does.
Wesley’s rule applied to quarterly reviews
Wesley’s first rule, do no harm, translates directly to product reviews. Most mid-career reviews measure output volume and team size. They rarely ask whether the last two quarters of work made it harder for a ministry volunteer to complete the core task. When that question is absent, the review itself rewards scope that crowds out the work the leader is actually good at.
The second rule, do good, requires naming the specific user behavior that improved because of the leader’s attention. In practice this means replacing “shipped three major features” with “reduced time from lesson download to printed page by four minutes for 42 percent of active volunteers.” The second statement forces the leader to stay close to the constraint that actually matters.
The third rule, attend to the ordinances, becomes a personal cadence check. It asks whether the leader still spends time in the environments where the product is used rather than in rooms where titles are discussed. Without that cadence, judgment drifts toward what peers will notice on a résumé instead of what changes a user’s Monday morning.
Replacing scope metrics with personal fit checks
Scope metrics track headcount and budget. Personal fit checks track whether the current work still calls on the leader’s clearest pattern of attention. One practical version is a monthly note that records the single user interaction that most changed the leader’s understanding of the constraint. If those notes thin out, the role has drifted from the work that fits.
Another version is a simple filter before accepting new scope: does this work require the exact combination of technical judgment and ministry context the leader has already proven they can hold? If the answer requires stretching the context rather than sharpening the judgment, the signal is winning.
Teams that adopted this filter at the quarterly planning stage found they declined two expansions that would have added impressive lines to a résumé and kept two smaller bets that later became the clearest sources of ministry retention. The choice was invisible to external signals and decisive for the product.
Your Turn: Apply This Today
- Pick one current title or scope signal you are tracking and write the single user behavior it has not improved in the last six months.
- Schedule one 20-minute conversation this week with the exact user role your product claims to serve and ask only about the last time the tool created extra work instead of removing it.
- Review your last quarterly self-assessment and replace every metric that references team size or feature count with one sentence on a user behavior that changed because of your direct attention.
- Block two hours next week to sit with the actual artifact your users produce (lesson plan, service order, volunteer schedule) and note where your current roadmap would add friction rather than remove it.
- Identify the single meeting on your calendar this month that exists primarily to discuss scope or title adjacency and replace it with a user observation session.
- Write one paragraph describing the work you are best wired for and compare it to the work your current title description actually rewards.
The Tuesday the Children’s Director’s Inbox Became the Real Product Spec showed how distribution constraints surface only when leaders stay close to the actual artifact. The Books Product Teams Ignore Are the Ones That Still Work in Ministry traced how older frameworks still surface constraints that modern scope metrics miss.
I consult with product leaders in faith-tech on replacing scope metrics with personal fit checks and applying durable decision frameworks to roadmap choices. Let’s talk.