Blog

I hit the number on a Tuesday. The offer letter sat in my inbox while the kids argued over cereal, and for about six hours I let myself believe the math would hold. By Friday the same leader who’d fought to close me was already floating the next title, the one that would finally let me shape direction instead of just execute it. The compensation target I had chased for years moved the moment I reached it.

The strange part wasn’t the goalpost moving. It was how quickly my own hunger agreed to follow it, a textbook hedonic treadmill. I started measuring my weeks by whether the new scope felt “strategic” enough, even though the actual work—shipping something useful, keeping the team human—hadn’t changed. The compensation target had moved, so my sense of enough moved with it.

Why the compensation target keeps moving after you hit it

John Wesley’s first rule—do no harm—supplies the lens. It is not a sentiment; it is a constraint that forces an actor to examine whether the next action damages the capacity of the people or systems already in motion. Applied to career design, the rule surfaces how chasing the moving target quietly erodes the conditions required for sustained product judgment.

Designing career signals beyond the compensation target

Title inflation is the clearest case. A product manager who moves from senior to lead because the band opened up often inherits meetings that replace the original user research cadence. The harm is not malicious, but it is measurable in the drop of actual decisions that reach shipped code. In one children’s ministry tool, the decision to expand the PM title ladder coincided with a measurable decline in volunteer completion rates because the new leads spent their cycles on cross-functional alignment rather than print-first UX fixes that had previously driven retention. Wesley’s rule would have required checking whether the title change reduced the team’s ability to protect the seven-minute volunteer workflow.

Flow is the constraint that actually produces durable work once external targets lose their pull. The state is not mystical; it is the condition in which a product person can hold the full problem context long enough to make a single, high-leverage change. When compensation conversations dominate attention, the calendar fills with status updates that fragment that context. The practical result is more features that solve for the next review cycle instead of the recurring user friction that only appears after several iterations of the same surface. Teams that redesign their own signals around flow—protecting two-hour blocks without status reporting, for example—ship fewer but more retained updates, which is the metric that compounds. Once the compensation target loses its pull, flow is what remains.

Values function as the veto that prevents the next visible win from overriding the work already underway. Once base compensation security exists, the remaining decisions are almost entirely value-laden: whether to accept scope that inflates headcount without improving outcomes, or to decline a promotion track that requires relocating decision rights away from the users. Without an explicit veto, the default is to accept the signal because it still registers as forward motion inside most organizations. The teams that treat values as operational rather than aspirational are the ones that can decline the moving target without career penalty, because they have already anchored their internal metric to something the organization cannot revoke.

Your Turn: Apply This Today

• Pick one current compensation signal—title, band, or public metric—and write the exact competence behavior it was originally meant to reward, then measure that behavior directly for the next four weeks instead of the signal.
• Block two contiguous hours on your calendar this week labeled only with the name of the user workflow you are responsible for, and decline every meeting that would break it unless the meeting owner can name the specific decision that requires your presence.
• Identify the last three features or initiatives that were accepted primarily because they aligned with a visible career marker, then list the concrete user harm or delay each one introduced; share that list with your immediate team by Friday.
• Define a single internal metric—volunteer task completion, return session depth, or error recovery time—that you will track weekly for the next month regardless of whether it appears in any performance review.
• Write a one-sentence veto criterion for the next compensation conversation you enter, using Wesley’s first rule as the test: if accepting the change would measurably reduce your capacity to protect the core workflow, decline it in writing.
• Replace one recurring status update meeting this month with a written summary sent the day before, then use the recovered time to complete one small product change that directly improves the metric you defined above.

The Director Who Stopped Performing His Title for LinkedIn shows what happens when the signal is removed before the competence metric is in place. The 1997 Lesson AI Product Teams Keep Missing demonstrates how external markers continue to distort judgment long after the original problem has been solved.

I consult with product leaders and ministry technology teams on redesigning career signals around flow and values, and on applying durable constraints to compensation decisions. Let’s talk.

I watched a volunteer lean over the check-in table, tap once on her phone, and start the countdown. No login. No toggles. Just the numbers dropping while she kept moving toward the craft table. That single tap was the payoff of shipping a narrow feature on its own instead of burying it in the platform.

We had shipped that same timer inside the main platform two years earlier. Everyone on the team could point to the setting. Hardly anyone ever used it.

Then three of them yanked the code out in a single afternoon, shipping a narrow feature that finally fit the table.

Teresa Torres calls this continuous discovery: teams must expose real users to real artifacts on a regular cadence instead of guessing inside a roadmap. The timer team followed her pattern without naming it. They treated the countdown as a product, not a module, and let usage data arrive straight from the people who actually managed Sunday morning logistics.

How shipping a narrow feature exposed actual volunteer friction

The original timer sat behind three admin screens and required a logged-in staff account. Volunteers on Sunday never had that account. They also never saw the timer because the check-in flow ended once a child was marked present. The friction lived in the gap between the designed path and the actual handoff at 9:15 a.m.

Once the standalone app appeared on the kiosk, the first data point arrived within hours. Volunteers needed to start the timer from the same device they used to greet parents. They did not want another login. The stripped version let them tap once. That single change came from watching three people fumble with the old flow during the first service.

The second data point showed up the next week. The countdown needed to reset automatically when the next group of kids arrived. The volunteer running the table did not have time to hit a reset button between services. The team added the auto-reset after seeing it happen live, not after reading a support ticket.

Discovery Loops That Only Appear Once the Tool Ships Standalone

Torres emphasizes that discovery requires repeated contact with users and working software. The timer app created that loop by accident. Every Sunday the same three volunteers used it. They started sending short voice notes on Monday mornings with the exact phrases they wanted on the second screen. One note said, “Put the next service time in big numbers so I can answer parents without looking away.” That request became the next release.

The core platform team had run user tests in a conference room six months earlier. Those tests never surfaced the voice-note pattern because the test setup used staff accounts and printed schedules. The standalone app removed the artificial conditions. Real repetition on real mornings produced the signal.

The same loop exposed a hardware constraint. The kiosk tablet overheated after ninety minutes of continuous countdown display. Volunteers solved it by propping a small fan behind the device. The team later added a low-power mode after seeing the fan trick repeated across three different churches that copied the app.

The Upgrade Path That Emerged Without Paid Acquisition

Within five weeks the timer app had spread to four other churches through volunteer group chats. None of those churches had ever used the parent check-in platform. The narrow tool acted as its own distribution channel because it solved one visible problem in under ten seconds of interaction. Shipping a narrow feature, it turned out, beat any paid acquisition plan.

The original platform team later offered an integration back into the main check-in flow. Adoption came from the volunteers who already trusted the timer. They asked for the connection themselves rather than receiving an announcement from leadership. The upgrade path ran in the opposite direction from the usual roadmap: usage data first, platform attachment second.

The same pattern now appears in two other narrow tools pulled from the same codebase. One handles classroom supply requests. The other prints name tags at the door. Both began as single-workflow experiments and now carry their own weekly usage numbers.

Your Turn: Apply This Today

• Pick one internal tool your team maintains and list every screen a volunteer must pass through before completing the single most common task.
• Remove every screen except the final action, rebuild it as a standalone web page or simple app, and deploy it on the devices the volunteers already carry on Sunday.
• Visit the location where the tool runs within seven days and watch three people use it without offering instructions.
• Write down the first sentence each user says out loud when something does not work and ship the smallest fix for that sentence the same week.
• Share the standalone link in the volunteer group chat instead of the staff newsletter and track how many new users appear without any internal announcement.
• After thirty days of live use, decide whether the narrow tool should connect back to the core platform based only on the requests that come from the volunteers themselves.

The Tuesday the Children’s Director’s Inbox Became the Real Product Spec shows the same principle applied to intake processes. The Fitness App a Pastor’s Kid Shipped Without Writing Code traces how a single workflow became its own distribution engine.

I consult with product leaders building ministry tools and faith-tech platforms on stripping narrow workflows into standalone products and running continuous discovery with volunteer users. Let’s talk.

The compensation number hit on a Tuesday. I opened the banking app in the parking lot, watched the deposit clear, and felt nothing shift in my chest. Ten minutes later I was back at my desk rewriting the slide deck for a title that would finally let me protect the volunteer tools. That hollow moment was the year external career markers stopped working for me.

I told myself the extra scope would matter. Instead I spent the next year in rooms where we discussed velocity but never opened the product. The seven-minute check-in flow I’d promised the kids’ ministry leads kept getting deprioritized for “strategic alignment.” Completion rates slipped a point every quarter and I kept pretending the next promotion would fix it.

The real problem wasn’t the meetings. It was that I still treated the next of the external career markers as the thing that would finally make the actual work feel worth the cost.

When external career markers lose their pull

External markers work while they are still tied to survival or early-stage credibility. After that point they decouple from the daily decisions that actually move a product forward. I watched this happen on the curriculum platform when we optimized for headcount growth instead of volunteer completion. The title expansion felt good in the moment, yet the product slowed because no one was still measuring the real constraint: how quickly a new volunteer could finish a lesson plan without support.

Munger would call this a failure to update the model. The compensation model had already done its job. Continuing to treat title as the primary variable created incentive drift. Product leaders began protecting scope instead of protecting the time needed for discovery work. The result was predictable: fewer experiments, slower learning, and a gradual erosion of the internal drive that had built the tool in the first place.

Designing Career Choices With Self as Primary User

Treating yourself as the primary user of your own career changes the questions. Instead of asking what title will look credible to peers, the latticework asks which role will still produce daily instances of clear problem-solving flow twelve months from now. That single mental model surfaces trade-offs the external list misses. A smaller scope with deeper ownership often beats a larger scope that fragments attention across coordination.

I applied this lens when deciding whether to expand into broader platform oversight. The compensation model said yes. The flow model said the new work would replace the direct user research loops that had kept the work meaningful. I chose the narrower path and watched the completion-rate metric improve again within two quarters. The decision only became visible once I stopped letting the external marker override the internal one.

The Concrete Trade-offs That Actually Serve the Work

Three recurring trade-offs appear once external signals are set aside. First, depth versus breadth. Breadth usually wins on a résumé; depth wins on the product metrics that matter for mission-driven tools. Second, visibility versus ownership. High-visibility roles often trade away the uninterrupted blocks required to finish hard design work. Third, compensation velocity versus skill velocity. Fast compensation growth can lock someone into coordination work that slows skill growth in the areas that created value initially. Setting external career markers aside is what makes these trade-offs visible.

Munger’s approach requires naming the second- and third-order effects of each option before choosing. In practice this means writing down the expected impact on daily flow, on the quality of user feedback loops, and on the ability to ship something concrete every quarter. The exercise takes twenty minutes and surfaces decisions that the title list never raises.

Your Turn: Apply This Today

• Map your current role against Munger’s latticework by listing the three mental models you are currently ignoring in favor of title or compensation.
• Block two hours this week to write the expected effect of your next career move on daily flow, user feedback loops, and quarterly shipping cadence.
• Identify one external marker you still track even though compensation security is already met, then replace it with an internal metric you can measure weekly.
• Review your last three role decisions and note which one would have changed if internal flow had been weighted equally with scope.
• Schedule a thirty-minute conversation with a peer who left a larger title for narrower ownership and ask what the first quarter revealed about motivation.
• Adjust one upcoming commitment this month that primarily serves an external signal and replace it with a task that directly improves a product metric you care about.

The Director Who Stopped Performing His Title for LinkedIn and The Fitness App a Pastor’s Kid Shipped Without Writing Code both trace similar shifts from external tracking to internal criteria.

I consult with product leaders in mission-driven settings on career design, internal motivation metrics, and trade-off decisions. Let’s talk.