Civic Work Atlas

PHOENIX / WORK / EVIDENCE
Municipal work / public evidence

Independent editorial publication. Not affiliated with the City of Phoenix. No login or official employee support.

Working & learning

Use the First Month to Build a Reliable Question Map

Organize early learning by responsibilities, dependencies and confirmation, while letting the employer’s actual onboarding and supervision remain authoritative.

In this guide
  1. Learn the work before optimizing it
  2. Turn a question into a traceable note
  3. Separate observation from permission
  4. Identify the handovers
  5. Review the map, not just the to-do list
  6. Keep a modest learning record
  7. Sources and scope

Organize early learning by responsibilities, dependencies and confirmation, while letting the employer’s actual onboarding and supervision remain authoritative.

Learn the work before optimizing it

A new role can produce more information than someone can confidently use. The first practical goal is to understand the assigned work and the rules for doing it, not to redesign every process immediately. This is a general editorial planning guide, not Phoenix’s onboarding program or a substitute for employer instructions.

Use a question map with three areas: what you are responsible for, what you need from others and what others need from you. Add a fourth area for boundaries: tasks, systems or decisions that require permission or supervision. The map should help you ask better questions without collecting confidential information.

Turn a question into a traceable note

A good note names the task, the uncertainty, the person or source appropriate to ask and the answer once confirmed. Avoid keeping a vague list such as “learn systems.” A narrower note might be “confirm where the current procedure for this assigned task is maintained.” That question can be closed when the correct source is identified.

In a hypothetical administrative role, an employee may need to understand how an incomplete request is handled. The question map records the need for an authorized procedure and contact. It should not contain a resident’s personal details or an invented answer based on a previous employer’s practice.

Separate observation from permission

Watching a colleague perform a task does not necessarily authorize you to do it independently. Completing a general training activity may also leave role-specific permissions unresolved. Keep an explicit distinction between observed, practiced under the appropriate conditions and authorized for assigned work.

That distinction is especially important when work involves records, equipment or public-facing decisions. If instructions are unclear, stop the uncertain step and ask through the employer’s process. This publication cannot grant access, interpret a supervisor’s instruction or supply operational safety procedures.

Identify the handovers

Many early errors come from not knowing what another person needs next. Ask which outputs your work produces, who uses them and what makes them complete enough to hand over. A clear status description can be as important as finishing the immediate task.

A hypothetical example is a shared request that cannot move forward until a missing document arrives. A useful handover identifies the status and next authorized step without claiming the request is complete. The specific workplace process may differ; the general learning question is how completeness and responsibility are communicated.

Review the map, not just the to-do list

At a suitable check-in, review a few questions that have been resolved and a few that remain important. Explain what you understand and invite correction. This makes misunderstandings visible while they are still small. Do not present your personal notes as official policy or circulate them as a replacement for controlled instructions.

If a process changes, update the reference and date rather than leaving old and new instructions blended together. Ask where authoritative updates are maintained. A personal reminder should point toward the current source, not become an accidental second policy manual.

Keep a modest learning record

Record the skills practiced, feedback received and questions clarified, using non-confidential descriptions. This can support later development conversations without creating a private archive of employer records. Follow workplace rules about notes, devices and retention, and avoid storing information you do not need.

The useful outcome of the first month is not a claim of total mastery. It is a clearer understanding of responsibilities, appropriate sources, handovers and the next learning need. Build a Learning Plan around Evidence of Progress helps define that next step, and Keep Personal Work Evidence without Copying Official Records explains how to keep personal evidence distinct from official records.

Related reading: Build a Learning Plan around Evidence of Progress, Keep Personal Work Evidence without Copying Official Records, Read a Municipal Work Schedule across the Whole Cycle.

Have a public source that changes this analysis? Suggest a correction. Please don’t send health records, financial information, employment records or account credentials.

Cookie settings