First-time manager

You may have the same deadlines as before, plus several employees who now need decisions and support. Start by naming that combined load with your manager: which individual outputs remain yours, which move to the team and what management work needs protected time? CCL's transition guidance puts responsibility on the organization to support a new manager. If you can finish a task faster yourself, also ask whether taking it over will teach anything or create the same dependency next time. A deliberate hands-on assignment can be appropriate; an unspoken expectation that you do both jobs indefinitely needs clarification.

A one-to-one is a recurring private work conversation between you and an employee. It can cover an unclear priority, a blocked decision, support or development; it need not duplicate a written status report. Google's manager guidance includes coaching and communication, but it does not establish one universally best meeting frequency. Ask what the employee needs to discuss before filling the time with your updates. For example, they may need you to resolve two competing requests rather than review tasks already completed. Agree who will do what next and when you will return to it.

Suppose a report lists several options but gives the reader no recommendation. Describe that gap and the decision the report needed to support, then ask what instruction or context the author received. The point is to help with the next attempt, rather than declare the employee careless. Kluger and DeNisi's feedback research shows why delivering criticism is not itself proof of improvement. Choose a setting and time that allow a real exchange while the example is still clear. The research provides no universal two-day deadline; urgent risk and routine development may require different timing.

An employee says the promised deadline depends on data another team has not supplied. Thank them for making the dependency visible, ask what is known and decide what needs investigation or escalation. Psychological safety means people expect to be able to take interpersonal risks, such as admitting uncertainty or asking for help. Edmondson's manufacturing-team study linked it with learning behavior. That supports taking early questions seriously, alongside clear standards. If you punish the messenger or make a promise and disappear, a later invitation to speak may carry little weight. Explain the next action, including when you cannot grant the request.

CCL's delegation guidance defines delegation as assigning responsibilities with the authority, resources, direction and support needed to deliver. Make the agreement concrete. For an invented internal-report assignment, explain who will use the report, which decision it must inform, the quality needed and the deadline. Identify the available material and what the employee can decide independently: they might choose the structure but need approval before committing money. Ask them to describe their proposed approach and identify missing access or knowledge before investing the whole week. This applies professional guidance rather than a tested universal script. A task name and due date alone leave these decisions unresolved.

At a check-in, the draft answers the right question but uses an unsuitable comparison. The manager explains one example, asks the employee to revise the remaining comparisons, and agrees when to review them. Taking back the entire report might meet today's deadline while preserving tomorrow's dependence. Leaving the employee with no explanation would not develop judgment either. The example shows how support and ownership can coexist; the amount of supervision must still fit the actual risk and experience.

Review should help an employee succeed while leaving meaningful ownership with them. A new task with a consequential commitment may need an early review of the approach; familiar routine work may need only a result check. Agree when the employee should raise an obstacle instead of waiting until the deadline. This is a practical interpretation of delegation support and CCL's situational roles, rather than a research-derived meeting interval. If review reveals a gap, explain the standard and decide what help is needed. Do not silently convert every checkpoint into approval of every small movement.

Sometimes the clearest way to teach is to work through one example together. Name what you are demonstrating, explain the judgment behind it and let the employee do the next attempt. Compare the result with the agreed standard. If an immediate incident requires you to take over, distinguish that exception from the normal arrangement and revisit the learning afterward. Google's empowerment behavior and CCL's coach/player distinction support this direction. Repeated rescue without explanation can make today's output look successful while leaving the person unable to carry tomorrow's work.

The handoff arrived after the agreed time is an observation. You do not care is a judgment about intent that the observation alone cannot establish. Describe the example, the expected work and its effect, then ask for context. Perhaps the deadline changed or an access request was never approved. That does not remove responsibility; it helps identify what needs to change. The task-focus lesson comes from feedback-intervention research. The sample distinction is an application of it, not proof that every employee will respond well to the same phrasing.

Feedback can also explain what to continue: for example, a clear recommendation made a report easier to use for a decision. Kim Scott's care-and-challenge framework explicitly includes specific praise and clear criticism, making it a possible practice aid. Its provider guidance is not a trial validating all of its claims. Ask whether your message gave the employee information they can use, rather than whether you performed a branded technique correctly. Being respectful and clear can include disagreement, and listening does not require withdrawing a sound work standard.

Agree what the employee will try, what support you will provide and when an observable result can be reviewed. For the report example, the next draft might state the recommendation and the reasons for it. If it still misses the purpose, reconsider the explanation, available resources and shared standard. Anseel and Sherf's 2025 review warns that feedback research rests on divergent assumptions and does not yield a single simple rule for organizational life. Your local follow-up supplies information about this attempt; it is not a controlled experiment or a promised performance gain.

Ask what risk, uncertainty or dependency your plan may be missing. Let the person finish, check that you understood and say what will be examined. If you retain the original decision, explain the reason and what new information would warrant reconsideration. Google describes psychological safety alongside dependability and clarity, so accepting questions and expecting quality work belong together. A calm invitation by itself does not establish safety. Employees also observe whose concerns receive attention, whether bad news brings humiliation and whether promised follow-up happens.

If you interrupted or dismissed an employee's concern, acknowledge the specific response and return to the issue. You might explain that you answered before understanding the dependency and ask to examine it together. Sutton's professional writing emphasizes attention to the effects of a boss's behavior and protection of employees' time and dignity. Research on leaders sharing feedback adds a reason to make learning visible. One acknowledgment does not prove trust has been restored. What employees can evaluate is whether later interactions give them a dependable opportunity to contribute.

When a new urgent request arrives, identify what it displaces, who owns it and which decision needs approval. For example, moving a deadline may affect another team's handoff even if your employee agrees to it. Reconfirm relevant authority and support rather than assume the old agreement still fits. This is an application of CCL's delegation guidance. Check the outcome and the support you supplied together; the person cannot responsibly own a decision they were never allowed to make.

Agree a workable rhythm for one-to-ones and a separate way to flag something that cannot wait. Invite the employee's questions about both work and development. If you must move a meeting, rebook it and address urgent decisions. This applies professional coaching guidance rather than claiming a proven optimum frequency. A reliable response matters more than a rigid promise that an appointment will never change, and recurring unresolved obstacles tell you something the calendar cannot.

Retain the relevant work example and the next action in a form that follows your organization's information policies. Check the next result rather than assuming that delivering the message completed the job. If the standard was unclear, clarify it; if the employee lacked necessary access, address that constraint. This applies the feedback literature's attention to context and the limits of simple rules. Keep sensitive employee information out of public tools and use authorized systems.

A promotion can change your access to information and authority even when friendships continue. CCL identifies moving from friend to boss as a transition challenge. Explain how assignments, expectations and decisions will be handled; avoid letting informal closeness determine access to opportunities or exceptions. You can remain warm without discussing another employee's private situation. If a decision belongs to a formal organizational process, use it and seek appropriate support. Being liked is pleasant, but fair and understandable work decisions are part of the responsibility you accepted.

Write down a question the role needs answered: perhaps how your manager measures team success, who can resolve a dependency or how to coach an unfamiliar task. Seek feedback from people positioned to observe that work. Hill emphasizes developmental relationships; Watkins organizes learning and stakeholder alignment; Ibarra adds purposeful experimentation. Use these frameworks to review an actual attempt and decide what to adjust. A mentor helps interpret experience, while your own manager still needs to clarify priorities, authority and organizational support.