Workplace Communication
Prepare for a One-on-One with Your Manager When You Need More Than a Status Update
A fictional engineer prepares a workload and development conversation, records mutual commitments, and revisits missed feedback and unavailable support without turning requests into promises.
Prepare for a one-on-one by choosing the issue you need your manager’s help to resolve, the evidence they need, and the specific support you want. Move routine progress reporting into a short pre-read so the conversation can address priorities, feedback, obstacles, or development. Finish by distinguishing what each person actually agreed to do from ideas, requests, and decisions that still belong to someone else.
This LandOffer.ai guide includes a completed employee-led agenda and a follow-up record with a missed commitment and an unresolved request. The people, work, estimates, and dialogue are fictional. They show a practical preparation method, not a tested guarantee of promotion, better management, or protected confidentiality. Primary guidance was checked October 27, 2026; your organization’s processes, authority, and document-sharing rules still apply.

Choose a conversation that needs your manager
Choose a topic where your manager’s decision, context, or feedback can help you move forward. You may need a priority decision, clarification of an expectation, feedback on a particular work sample, help reaching another owner, or permission to spend time learning. “Here is everything I did” gives context but does not identify that contribution. “Which of these two commitments should move?” creates a question the manager can answer or route.
FranklinCovey’s employee guide recommends proposing topics, limiting status updates, and agreeing dated next steps. Its guidance supports employee preparation rather than waiting for the manager to notice every concern. You can ask for help before you have a complete solution. Explain what you know, what you tried, and where you need help; do not conceal a serious blocker because you cannot yet solve it.
Start with a running list during the week, then choose the most important discussion for this meeting. Separate matters that can wait from risks that need an immediate channel. A production incident, urgent safety concern, or time-sensitive reporting obligation should not sit on a private agenda until next Tuesday. Use the appropriate process when the issue arises and reserve the one-on-one for support, context, or follow-through where useful.
Bring an observation you can examine together before drawing a conclusion about somebody’s motives. “I received five review requests, including two from another team, while the validation draft was due” is something you can examine together. “Everyone thinks my time is free” is an interpretation. You can describe frustration honestly while leaving room for missing context and a different explanation.
Send enough context without using the whole meeting on updates
An advance agenda gives your manager a chance to inspect evidence and understand the question. Google’s January 2013 practitioner post describes employee-led one-on-ones, a shared running document, and broader career discussion. It is a historical account of a practice, not proof that every current Google team works this way or that a particular meeting frequency is universally best.
For your own pre-read, keep routine status short and link to the existing work record. Include the decision you need, why it matters now, and any preparation you are requesting. For feedback on a brief, point to the decision-consequence paragraph and ask whether its opening makes the choice clear; do not leave the manager to search an entire project archive. Ask whether they can review it in the available time.
Choose an appropriate audience for the document. GitLab’s current public handbook recommends a consistent agenda with contributions from both people and private sharing for performance feedback. That is GitLab’s guidance, not a universal confidentiality promise. Ask how your employer stores one-on-one records and when information may need to be shared. Avoid putting unnecessary personal data, customer secrets, or allegations about third parties into a broadly accessible document.
Leave space for the manager’s context and for a concern that emerges during the conversation. Employee-led does not mean the manager is prohibited from adding a topic. Nor should a minute-by-minute agenda become a way to avoid a difficult answer. Use time estimates to protect the important discussion, and explicitly decide what to carry forward if another issue takes priority.
Completed employee-led agenda: a workload decision and a learning request
Rhea is a data engineer at fictional Harbor Metrics. Her manager is Leo. Their October 20, 2026, one-on-one lasts 30 minutes. Rhea wants a decision about competing work and help practicing concise technical-risk explanations. This is not a promotion conversation, an appeal of a performance rating, or a group project-planning meeting.
Her October 19 pre-read separates asynchronous facts from the discussion:
Routine update: The schema-validation outline is available in the existing project record. The internal support-guide draft has its sections listed but is not ready for review. Five review requests arrived during the prior week: three from our team and two from another team. I have not promised completion dates for the two external requests.
What I need tomorrow: Please help choose a feasible priority order for the 20 focus hours I have identified for the coming work block. My current estimates total 22 hours before adding development preparation. I also want your feedback on explaining a technical risk in a short written brief, without adding an unbounded new project.
Preparation requested: Read the four-line capacity breakdown below. No review of the full support-guide draft is needed for this meeting. Please add any urgent manager topic to the agenda so we can adjust the discussion time together.
The planned work is 12 hours for the schema-validation draft, six hours for the internal support guide, and four hours reserved for reviews: 22 estimated hours against 20 available focus hours. These are fictional planning estimates, not measured task durations or a complete timesheet. Meetings and other obligations have already been excluded from that focus window. Rhea will raise new work rather than quietly treating the estimates as unlimited capacity.
Her finished agenda contains the question, evidence, and requested contribution for each discussion:
| Time | Employee topic and evidence | What Rhea asks Leo to contribute |
|---|---|---|
| 3 minutes | Check-in: fragmented attention from requests arriving outside the planned queue | Ask whether any immediate context changes today’s priorities |
| 12 minutes | Workload: 22 estimated hours against 20 focus hours; two external requests have no accepted deadline | Decide which internally owned scope can move; identify who should negotiate external requests |
| 9 minutes | Development: Rhea’s last risk explanation listed technical details without stating the decision consequence | Give feedback on a two-hour preparation exercise and say whether Leo can review the result |
| 6 minutes | Read back decisions, dates, owners, and unresolved requests | Confirm commitments and the next review point; correct anything Rhea misunderstood |
The development request is specific: “Can I spend two hours writing a one-page risk explanation using the validation work, and can you review whether a non-specialist can identify the decision and consequence?” It does not ask Leo to certify a general communication skill after reading one page. The artifact would supply a narrow sample for feedback; it would not prove a production outcome or confer a new title.
Rhea also asks whether Jo, a specialist on another team, could provide technical input. Leo can ask about that possibility, but neither person can commit Jo’s time. The agenda therefore labels Jo’s help as a request to explore. That small distinction keeps a development idea from turning into an assignment to someone absent from the conversation.
Turn the conversation into an agreement you can read back
During the fictional meeting, Leo confirms that he controls the internal support-guide priority. He agrees to defer four of its six estimated hours from this work block. Rhea retains two hours for that guide, 12 for validation, four for reviews, and adds two for the learning brief. The revised estimate is 20 hours. This is a bounded priority decision, not a promise that the work will finish exactly on estimate.
Leo also agrees to tell the team about the reduced guide scope and to ask the other team’s owner about its review requests. He does not promise that those requests will disappear. Rhea agrees to avoid accepting their dates until the relevant priority discussion happens, while escalating any urgent issue through the normal work channel.
Their end-of-meeting readback is explicit:
Rhea: “I will prepare the validation draft within its current scope, reserve four hours for reviews, limit this block’s guide work to two hours, and use two hours for the risk brief. If new requests or the estimates change, I will bring the trade-off back rather than absorb it silently. I will share the brief with you by October 23.”
Leo: “I agree to the internal guide reduction and will communicate it by October 21. I will ask the other team’s owner about its requests by October 22. I can review your brief by October 26. I can ask Jo whether she has capacity, but I cannot offer her time today.”
Both: “We will recheck the priorities and feedback at the October 27 one-on-one. That review does not depend on Jo accepting the request.”
Each person retains responsibility for the action they accepted. It also records the manager’s actual limit. “I can ask Jo” is an outreach commitment, while Jo’s contribution remains unaccepted. Rhea keeps that distinction when she writes the follow-up rather than summarizing the discussion as “Jo will coach me.”
Completed follow-up: partial progress and a missed commitment
Reopen the agreed actions at the next meeting so preparation leads to a visible follow-up. The following October 27 review is also fictional; it is a completed editorial scenario, not a report about real employee performance. It contains mixed progress instead of manufacturing a clean ending:
| Commitment | Evidence available at the October 27 review | Disposition |
|---|---|---|
| Leo communicates internal guide reduction by October 21 | A team priority note dated October 21 states the reduced scope | Manager action complete; remaining guide work still exists |
| Leo asks the other team’s owner about review requests by October 22 | His October 22 request is recorded; no response accepting new dates is available | Asking complete; cross-team priority outcome remains open |
| Rhea sends risk brief by October 23 | Her one-page brief is available with the decision consequence added to its opening | Preparation complete; usefulness still needs feedback |
| Leo reviews brief by October 26 | Leo acknowledges he has not reviewed it | Missed commitment; he accepts a revised October 29 review date |
| Leo explores Jo’s capacity | Jo replies that she cannot take on the review this month | Specialist support declined; no mentoring agreement exists |
Rhea responds to the missed review with a specific request: “The brief is ready, but I still need your feedback on the decision consequence. Can you review it by October 29? If that is not feasible, let’s choose a smaller question or another reviewer who accepts.” Leo accepts October 29. That revised date is a new commitment, not evidence that feedback has already happened.
They agree that Leo’s review can proceed without Jo. Rhea will bring one question to the next discussion: does the brief explain the consequence before technical detail, or does it still assume the reader knows why the decision matters? No assessment of improvement is recorded yet. The example therefore closes the preparation task and updates the support plan while leaving the learning outcome unproven.

Keep the relationship conversation useful when the plan changes
If the manager repeatedly uses the time for status, propose a small change directly: “I can put progress in the pre-read; could we protect the first discussion for the decision I need?” If the meeting is cancelled, request a replacement or another appropriate channel for a time-sensitive question. Neither employee preparation nor a shared document guarantees the manager’s availability or willingness to help.
Review what is actually working rather than grading the meeting by how many boxes were filled. A useful outcome may be clarified expectations, a candid limit on resources, or agreement that a topic belongs in another process. If the concern needs HR, an accommodation route, a formal performance discussion, or another confidential reporting channel, use that process rather than assuming the one-on-one replaces it.
For your next meeting, identify the support you need, propose a concrete discussion, and ask what follow-up each person can actually accept. Carry forward unresolved commitments with their owner and agreed date, and retire items that have actual evidence of completion. LandOffer.ai publishes this guide; it does not manage your one-on-one records or make decisions for your employer.


