World Icon

Updated September 2026: in 2020 my uncle bought AirPods Pro at full price and asked me to set them up across his devices, which convinced me to buy a pair. I have rewritten it into a guide to setting up AirPods Pro for a family member, including features worth switching on for them.

I had wanted AirPods Pro for a long time, especially after spatial audio was announced, but held back waiting for a discount. My uncle simply bought them. When he asked me to set them up and connect them across his devices, I heard the sound quality for myself and saw how smoothly they connected. That settled it for me.

How do you set up AirPods Pro with an iPhone?

Unlock the iPhone, open the AirPods case next to it, and follow the prompt on screen. The AirPods are then linked to the Apple Account on that iPhone and appear automatically on the person's other Apple devices signed in to the same account.

Which settings help a family member most?

• Ear tip fit test: in the AirPods settings on the iPhone; the right size improves comfort and sound.
• Noise control: show them how to switch between noise cancellation and transparency by pressing and holding the stem.
• Find My: make sure it is on, so lost AirPods can be located.
• Automatic switching: turn it off if they are confused by audio jumping between devices.
• Headphone safety: set a volume limit if appropriate.

Can AirPods be used with Android or Windows?

Yes, as ordinary Bluetooth earbuds. Hold the button on the back of the case to enter pairing mode. Many features, such as automatic switching and some settings, are unavailable without Apple devices.

Should they be set up on your account?

No. Set them up on the owner's own device and Apple Account. Otherwise they will appear on your devices and can connect unexpectedly, and Find My will show them to you instead of the owner.

Is it worth paying full price?

Discounts appear regularly during sales, so waiting usually saves money. But as my uncle's pair showed, the experience is good enough that many people are happy they did not wait.

Keep reading

• Reasons why I hate or don’t like AirPods Pro
• iPhone 14's Missing Features: What Apple Added Since
• Dialogue Enhancement Fixes One Thing, Not Three

Updated September 2026: in June 2020, after leadership rejected my manager's approach, he promised the updated version by the next day, which was a weekend, without asking me. I logged off as soon as the call ended. I have rewritten it into advice on responding when someone commits you to weekend work.

The client's requirements turned out opposite to the delivery team's assumptions. Leadership then asked for information from other accounts, and my manager gathered details they did not want. When leadership dismissed his suggestions and asked for simple insights, I stayed silent. At the end, my manager committed to sending the updated version the next day, a Saturday. I logged off immediately after the call.

Is it fair for a manager to commit you without asking?

It happens, especially under pressure from leadership, but it is not good practice. Commitments should reflect who will do the work and when. Being volunteered for a weekend without a conversation damages trust even when the work itself is reasonable.

How should you respond?

• Do not ignore it. Logging off without a word leaves the commitment standing.
• Talk to your manager the same evening: ask what exactly was promised and what is the minimum that would satisfy leadership.
• Offer a realistic option, such as a short version on Saturday afternoon, or the full version first thing Monday.

What if the deadline genuinely cannot move?

Agree a limited scope and a fixed window, and ask for the time back as comp-off. Share the work if others can help. A focused two-hour task on Saturday is manageable; an open-ended weekend is not.

How do you stop it becoming a pattern?

After the weekend, raise it calmly: "Next time, can we check timing together before committing to leadership?" Suggest that commitments on dates are confirmed after the call rather than on it. Most managers accept this once they see its effect.

Should you speak up on the call itself?

Sometimes a brief, neutral line helps: "I can have a first version by Monday morning." It is not contradicting your manager, just offering a realistic date before the promise sets.

Keep reading

• When a Client Team Asks for You by Name
• Validate the Brief Before Building the Deck
• How Client Appreciation Emails Help Your Rating

Updated September 2026: in June 2020 my manager gave me a brief for a short-turnaround opportunity; I built slides and a storyline around it, then presented them on a call with onsite and offshore teams, where the day's work was set aside. I have rewritten it into advice on validating a brief before investing a day in it.

Back from leave, I was assigned an opportunity with a familiar account team and a short deadline. My manager shared some snippets and asked me to collate slides with a storyline. I trusted his input, built the deck, and he asked me to set up a call with onsite and offshore teams. I opened the call with my deck in presentation mode, confident. The day's work did not survive it.

Why do second-hand briefs go wrong?

Because they are summaries of conversations you were not in. Details get lost, and the manager's own interpretation fills the gaps. When the people closest to the client hear the result, they often find it does not match what they asked for.

How do you validate a brief quickly?

• Write the brief back in five lines: the client's need, the deliverable, the storyline, the deadline and the approver.
• Send it to the onsite lead as well as your manager, and ask for a quick yes or corrections.
• Hold the kickoff call first, then build, not the other way round.

Should you present a full deck at a first call?

Usually not. At a first call, share a one-page outline and ask questions. Presenting a finished deck invites people to react to the slides rather than tell you what they need. An outline invites correction when correction is cheap.

How do you recover when a day's work is dropped?

Take notes on what the team actually wants, confirm it in writing, and reuse whatever still fits. Then tell your manager what changed, factually. Most of the time some structure survives, even if the storyline changes.

What should you ask your manager in future?

"Has the onsite team seen this direction?" If the answer is no, suggest a fifteen-minute call before building. That single question saves the most rework.

Keep reading

• When a Client Team Asks for You by Name
• When Your Lead Rejects a Slide the Client Team Accepted
• Running a Query Log With Answer Deadlines

Updated September 2026: in March 2020, pulled back into an old request after vacation, I spent the first day drafting a plan: the offshore lead would list every open query for the onsite team, with deadlines, after which we would proceed on assumptions. Before I could send it, the onsite team proposed daily morning status calls. I have rewritten it into a guide to running a query log with deadlines.

The work was back on my desk with people I had struggled with. I spent the day planning: milestones for each day, sign-off from each owner, and a request to the offshore lead to list every question needing onsite input, each with a deadline. If answers did not come by then, we would go ahead on stated assumptions. As I drafted the email, the onsite team wrote suggesting daily morning status calls.

What is a query log?

A single list of open questions, each with an owner, a date raised, a deadline for the answer, and the assumption the team will use if no answer arrives. It turns scattered emails into one place everyone can check.

Why set deadlines on questions?

Because unanswered questions are the most common cause of late proposals. A deadline plus a default assumption means work never stops waiting. It also makes clear who is responsible when an assumption turns out wrong: the person who did not answer in time, not the team that proceeded.

What should each entry contain?

• The question, written so it can be answered in one or two lines.
• Who it is for, and who raised it.
• The answer deadline.
• The assumption if unanswered.
• The status: open, answered or assumed.

Do daily status calls help or hurt?

Short daily calls can work well alongside a query log: fifteen minutes to walk the open questions and confirm the day's milestones. They hurt when they become long reviews of slides. Suggest using the log as the call's agenda, which keeps it short.

How do you get sign-off from each owner?

Name one approver per section and give each a date. Send the section with a clear request: "Please approve by Thursday 5 pm, or send changes." Record approvals in the log, so the final document has a clear trail.

Keep reading

• Client Hasn't Answered the Questionnaire? Keep Moving
• Validate the Brief Before Building the Deck
• When a Client Team Asks for You by Name

Updated September 2026: in February 2020 a new delivery team told me I had only a limited role for two weeks, and just as I relaxed, an old team asked for justification slides within two days. I have rewritten it into advice on juggling a standby role and a returning old request.

The new delivery team said my role would be small and I could be on standby for two weeks. Before I could enjoy the quiet, my previous team, which I had found difficult, came back wanting a few justification slides in two days. If the new work had been as heavy as predicted, the two would have collided. I told the old delivery person, informally, that I had a new assignment but, luckily for them, it was light for now.

What does being on standby mean?

It means you are allocated to a project but not yet fully needed. You should be reachable and ready, but you have spare capacity. That capacity is visible to others, which is why old requests tend to find you during standby periods.

Should you accept the old request?

If it is small and time-limited, usually yes; it builds goodwill. But tell your manager, so the allocation is recorded, and tell the new team, so they know you may be busy for two days. Informal arrangements are where overload starts.

How do you avoid the two colliding?

• Ask the new team when they expect to need you properly.
• Give the old request a clear finish date before that.
• Agree which takes priority if both become urgent at once.

How do you keep the old request small?

Confirm exactly which slides and what "justification" means: evidence, figures or narrative. Reuse existing material where possible. Send a draft early and ask for one round of comments. Justification requests can grow if you let them.

What should you tell your manager?

That you are on standby for the new project and supporting the old team for two days, with the end date. Managers dislike discovering this later, and knowing it lets them protect you if both teams ask at once.

Keep reading

• When a Client Team Asks for You by Name
• Quiet Days and Colleagues Leaving: What to Do
• Validate the Brief Before Building the Deck

Updated September 2026: in January 2020 an onsite team I had worked with came back with a new request addressed directly to me, so my manager and I had to take it on. I have rewritten it into advice on handling requests when a client team asks for you by name.

After finishing a tough opportunity with my manager, I hoped the next one would be calmer. On Monday, the same onsite team returned with a new request, addressed straight to me. Neither my manager nor I felt we could decline. I set up a call with onsite and offshore teams to align, and a delivery person I had worked with before joined.

Is being requested by name a good sign?

Yes. It means the team trusts your work and finds you easy to work with. It is also a sign of your value to the account, worth noting at appraisal time. The downside is that it can bypass normal allocation and pile work on you.

How should you respond to a direct request?

• Acknowledge it quickly and thank them for thinking of you.
• Copy your manager and let them confirm the allocation.
• Ask for scope and dates before committing to a timeline.

How do you avoid becoming the default for everything?

Share credit and knowledge. Introduce a colleague on the call, and let them handle part of the work. Over time the team trusts more than one person, which protects your capacity and helps your colleague grow.

What should the first alignment call cover?

The client's need, the deliverable, who approves it, the timeline, and anything learned from the last opportunity with the same team. If the last one had repeated changes, agree a change process now. A familiar team makes the start faster, but it can also bring back old habits.

Should you worry about working with the same team again?

Only if the previous work was painful for reasons that still apply. If so, raise them at the start, politely: "Last time the requirements changed late; can we agree a checkpoint with the client this time?" Direct requests give you some leverage to set better terms.

Keep reading

• When Your Lead Rejects a Slide the Client Team Accepted
• On Standby for One Project, Pulled Back to Another
• Validate the Brief Before Building the Deck