Build a question map for your first week

Ask about the expected output

Find out the first small task, who will use it and what counts as complete. Do not record your assumption as the team’s expectation. If the answer is missing, keep the question open; filling the note does not resolve the uncertainty.

Separate the people and decision maps

A knowledgeable colleague may not own the decision. Write whom to ask about a particular question rather than collecting names. You do not need personal phone numbers or private contact details in this worksheet.

Learn communication and access methods

Ask which channels the team uses, what context is expected with a question and how access requests are handled. Request an introduction or permission rather than exploring an unfamiliar system experimentally. Do not record passwords or access keys in notes.

Close the week with three lines

Record one expectation you understand, one small output you actually made and one open question. This is not a performance score. Carry forward one genuinely prioritised activity rather than trying to resolve every uncertainty at once.

Turn reading into an output

1. Write three questions about your first small output.
2. Separate a person to consult from a decision owner.
3. Record the relevant communication or access process.
4. Close the week with expectation, output and open question in three lines.