Let the employee choose the conversation
An employee-led agenda can include obstacles, feedback, and development alongside current work. The Asana one-on-one template includes previous follow-ups and employee-led topics. Use the structure to prepare a conversation, rather than filling the entire meeting with project reporting.
This original illustrative agenda uses fictional work requests with no private performance information. Request A is a client guide due Friday; Request B is an internal walkthrough also due Friday. The employee estimates eight remaining work hours before Friday and six hours for each request. Those estimates are discussion inputs, not a real employee's productivity record.
Employee's chosen topic: “Which request should I prioritize, and who will communicate the revised expectation for the other one?”
Previous commitment: The manager would confirm who approves the client guide. Current status: [NOT YET CONFIRMED]. The agenda does not mark the commitment complete merely because it appeared in last week's notes.
A 30-minute agenda
| Minutes | Conversation | Preparation or outcome |
|---|---|---|
| 0-3 | Employee opening: what needs attention today? | Confirm or revise the chosen topic. |
| 3-7 | Review the prior approval-owner commitment. | Record actual status or the next check. |
| 7-20 | Discuss the conflicting requests and support needed. | Clarify priority, scope, or timing with the manager. |
| 20-25 | Employee-selected feedback or development question, if time permits. | Identify an example to discuss or carry forward. |
| 25-30 | Read back each person's follow-up and next check. | Distinct manager/employee responsibilities. |
The blocks total 30 minutes. The main concern receives 13 minutes. If it needs more time, agree which remaining topic moves to the next conversation; do not rush a support decision to complete every row.
Ask for a decision, with enough context
Bring the requesters, expected outputs, deadlines, remaining effort estimates, and any commitments already made. In the illustrative example, demand is 12 hours against eight available, a four-hour gap. Confirm that these estimates cover the same period and account for other work before treating the gap as settled.
Use a support request such as: “Please help confirm the priority with both requesters, or agree which scope or deadline can change.” The manager may need another person's authority. In that case, record the person to consult and the time to return with an answer, instead of describing an unresolved discussion as a decision.
Avoid converting the capacity conflict into an unsupported judgment about the employee. The agenda contains work constraints; it does not establish motivation or performance.
Write two follow-ups, not one vague action
Before the meeting, the follow-up fields are proposed and open:
- Manager: [CONFIRM priority and revised expectation with requesters]; due [TO AGREE].
- Employee: [UPDATE the work sequence after priority is confirmed]; due [TO AGREE].
- Next check: [WHEN to verify that the answer reached both requesters].
After the conversation, write the actual agreement. If no priority was settled, retain “pending” and name the next authority check. Do not quietly choose a request while writing the recap.
Copy a preparation prompt
Help me prepare an employee-led one-on-one agenda in US English.
Meeting length and next meeting date: [inputs]
My most important discussion question: [question]
Relevant work requests, deadlines, effort estimates, and available time: [inputs]
Previous commitment and actual current status: [inputs or unknown]
Manager support I want to request: [request]
Feedback/development topic I choose to include: [topic or blank]
Our approved private record location/format: [format only]
Give a short timed agenda that prioritizes my concern, reviews the previous commitment, and reserves time to agree follow-ups. Separate a routine update from a question requiring support or authority. Show a capacity conflict only when estimates use the same period and unit. Keep manager action, employee action, due date, and next check distinct. Mark all proposed follow-ups as proposed until agreed.
Do not invent manager decisions, employee motives, performance ratings, completed commitments, or private histories. Use [NEEDED: input] for gaps. Retain unknown status and conflicting inputs. Do not infer a priority from urgency alone. Avoid personal identifiers and confidential content in any sample. Check minutes and return notes for our approved private system.
Keep the actual conversation and agreed follow-ups in the private record you and your manager use. At the next meeting, start with whether the promised support happened and what changed for the work. That gives the conversation continuity beyond a list of updates.
Optional: inspect a sanitized agenda structure in NOS
For a template review or manager-training discussion, an HTML copy with fictional requests can be saved and rendered in NOS. Use it to inspect the separation between the employee's concern and each person's follow-up. Keep actual confidential one-on-one notes in your approved private system.