The Night the New Career Tool Asked the Wrong Job

The cursor blinked on the “add another skill” field while the missions director’s coffee cooled beside her laptop. Slack messages stacked up from the three short-term volunteers waiting on placement answers, each one tagged with a different timezone. The career tool had already cycled through its quarterly goals screen twice, refusing to move forward until she picked from the dropdown.

She typed one entry, then deleted it. The volunteers needed decisions before their flights, yet the screen kept framing the problem as her personal resume growth.

This is the same pattern that breaks jobs-to-be-done work when the team’s real job is keeping a shared state intact across handoffs. Individual outcome questions pull attention away from the coordination constraints that actually determine whether placements survive the next season.

John Wesley’s three simple rules give a different lens. Do no harm. Do good. Stay in love with God. Applied to product interviews, the first rule means the script must not damage the fragile continuity a ministry team already carries. The second means it must actively strengthen that continuity. The third keeps the conversation anchored in the actual relationships rather than abstracted career ladders.

Replace title-chasing prompts with state-preservation questions

Most placement tools open by asking what title or skill set the user wants next quarter. That question assumes the user’s primary task is personal advancement. In the missions director’s case, her primary task was making sure none of the three volunteers arrived without a clear partner on the field.

When the script instead starts with “What state must this team hold steady for the next six months?” the answers surface constraints the tool had ignored. The director listed “one local contact who already knows the language for each arriving volunteer” before she listed any skill of her own. The tool now had to treat that contact as a non-negotiable resource rather than an afterthought.

The shift also changes what counts as progress. Completion is no longer “user filled out five fields.” Completion is “the handoff conditions for the next volunteer are recorded and visible to the people who will act on them.” Metrics move from individual profile completeness to team state continuity.

Interview the handoff, not the person

Traditional interviews treat the missions director as the unit of analysis. They ask about her experience, her goals, her bandwidth. The real unit is the handoff moment when a volunteer steps off a plane and meets the local contact.

Observing that moment in three different regions showed the same pattern. The volunteer who had a named contact waiting with a printed schedule stayed. The volunteer who only had an email address and a general “someone will meet you” message did not. The difference was not the volunteer’s skills but whether the handoff state had been preserved.

A revised interview therefore asks the director to walk through the last successful handoff out loud, step by step, naming every person who touched the volunteer between airport and first assignment. The questions stay on those touch points rather than on the director’s title or aspirations. The resulting data describes the actual coordination surface the tool must support.

Let the oldest volunteer story set the outcome frame

The missions director had one story she told without being asked. A volunteer from eight years earlier still wrote every Christmas because a local pastor had met him at the airport with the exact right bus schedule and a spare key to a spare room. That single preserved state had created eight years of relationship.

When the interview script opens with that story instead of a skills matrix, the outcome frame changes. The director is no longer optimizing for her own next role. She is optimizing for the conditions that let an eight-year relationship begin. The tool must now record and surface the elements that made that handoff durable: the named contact, the printed schedule, the spare key protocol.

This ordering also prevents the tool from treating every placement as a fresh start. It forces the system to inherit the durable states already operating in the field.

Your Turn: Apply This Today

• Open the current placement interview script and move the first three questions to the bottom; replace them with “Name the person who will meet the volunteer at the airport and what they already know about the arrival date.”
• Pick one recent placement that succeeded and one that did not; list every handoff step that differed between them and add those steps as required fields in the next version of the form.
• Schedule a 20-minute call with the oldest volunteer from the last two years and ask only what single action by a local contact made the difference; turn that action into a state-preservation prompt.
• Remove every title or skill dropdown from the first screen and replace it with a single open field: “What must stay the same for the next volunteer after this one?”
• Run the revised script with one missions director this week and count how many coordination constraints appear before any personal career goal is mentioned.
• Update the completion metric in the tool from “profile 80% complete” to “next handoff state recorded and visible to at least two other people.”

The post on prompt replacement shows what happens when tools optimize for the wrong actor. The post on the culture export that actually stuck shows how durable states travel when the handoff is designed first.

I consult with product leaders building placement and assignment tools for mission teams on coordination constraints, state-preservation questions, and handoff interviews. Let’s talk.