Plan and develop survey methods

Plan and develop survey methods — real work, not an imagined feature: named inside 11 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

11career tasks name it
3prompt heights

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Improve — make it easier to accept

+
Before I hand this protocol to field managers, make the instrument easier to implement: list the…
Before I hand this protocol to field managers, make the instrument easier to implement: list the top three respondent burdens at the top, reorder questions so sensitive items are later in the interview, flag routing logic that could confuse supervisors, and add a short interviewer instruction sheet as the first page.

Decide — diagnose the stuck moment

+
The pilot showed a sharp drop during household income questions and supervisors reported…

We pretested the questionnaire and response rates fell during sensitive modules.

The pilot showed a sharp drop during household income questions and supervisors reported inconsistent routing logic. I worry that continuing as-is will bias nonresponse and ruin the survey. Should I shorten or rearrange sensitive modules, or change consent wording to reassure respondents? Which fix will best recover response rates without compromising measurement of income?

Become — change the pattern

+
In three consecutive surveys we run into routing errors and interviewer confusion during field…

We keep losing time fixing questionnaire routing during field deployment.

In three consecutive surveys we run into routing errors and interviewer confusion during field deployment, forcing mid-field edits that damage timelines and data quality. What habit should we change for instrument development and testing, and what concrete checklist or role assignment will prevent routing and instruction problems from reaching field teams?

Where the evidence lives

Who was seen doing this, and what people really ask.

Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.