Help Desk Blogger

Updated September 2026: in November 2020 I wrote an angry note about a weekend spent on a document my manager replaced minutes before the client call. I have rewritten it into practical advice on last-minute rework, which is what I needed at the time.

One weekend in November 2020, my manager and I worked on a proposal document with almost no input from the account team. I rebuilt it from past material, took his suggestions, and argued with him when they felt pointless. A few minutes before the call he shared a new set of documents, and the deck I had spent the weekend on was not used. I joined that call having lost all interest in the opportunity.

Most people in project work have a version of this story. Here is what reduces how often it happens.

Why does work get replaced at the last minute?

Usually because information reached your manager late and nobody went back to tell you. The account team shared something with him directly, a client conversation changed the direction, or he had his own version in mind from the start and did not say so. It feels personal. It is more often a communication failure than a judgement on your work.

How do you confirm direction before you start?

• Ask at the outset what the final output is for, who will present it and what they already have.
• Send a one-paragraph outline before building the full document and ask for a yes or changes.
• Agree a checkpoint halfway: "I will share a draft by Saturday 3 pm." Any new material should reach you then, not at the call.

These add perhaps twenty minutes. They save weekends.

What do you do when it happens anyway?

Do not argue about it before the call. Join, listen and take notes, because the discussion tells you what the client actually wanted. Afterwards, ask your manager for five minutes and keep it factual: which inputs arrived late, how much time the replaced work took, and what would help next time. Proposing a checkpoint for the next document is far more likely to change behaviour than complaining about the last one.

When does it become a pattern worth raising?

If your work is replaced repeatedly with no explanation, keep a short record: date, task, hours spent, and what happened to it. After three or four entries, you have something concrete to bring to your manager, or, if nothing changes, to a skip-level conversation. Wasted effort that is recorded can be discussed. Wasted effort that is only resented tends to show up in your own motivation instead.

What I would do differently

An outline sign-off and a Saturday checkpoint would not have guaranteed the document survived. But asking what my manager was working towards, instead of getting angry at each new change, would have surfaced the new material on Saturday morning rather than a few minutes before the call.

Keep reading

• Working Under a Micromanager: A Practical Guide
• When Your Only Teammate Leaves: Handover and Workload
• Keeping a Work Journal in IT: Why and How to Restart

Updated September 2026: in 2020 I listed the features Apple Pages needed to catch up with Microsoft Word, grammar checking first. Both apps have changed a lot since, so I have rewritten this around where the gap stands now and who should use which.

I have used Pages on a MacBook Pro for years alongside Microsoft Word for office work. In 2020 my complaint was simple: Word caught grammar mistakes Pages missed, and Pages hid its formatting options in ways that slowed me down. I suggested Apple should buy or build a proper grammar tool. Some of that has happened.

Has Pages closed the grammar gap?

Partly. On Macs that support Apple Intelligence, Pages gets Apple's Writing Tools, which can proofread, rewrite and summarise selected text. That is a real step up from the basic spell check I was comparing against in 2020. Word, meanwhile, has Microsoft Editor built in, and Microsoft 365 subscribers get Copilot inside Word for drafting and rewriting. For careful grammar and style suggestions on long documents, Word still gives more control. Writing Tools also depends on your Mac and language settings, so check it is available on yours.

Is Pages still harder to format in?

It is different rather than harder. Pages puts formatting in the sidebar Format panel, organised around paragraph and character styles. Once you work with styles instead of formatting text by hand, it becomes quick. Word's ribbon exposes more options at once, which suits people who move between many documents with different templates. My 2020 frustration was mostly about habit, and the fix is learning Pages styles.

Which features still favour Word?

• Working with others on Windows: Word files round-trip reliably; Pages can export to .docx, but complex layouts, comments and tracked changes can shift on the way.
• Long structured documents: references, cross-references and heavy review cycles are more mature in Word.
• Company templates: most offices build templates in Word, and they rarely convert cleanly.

When is Pages the better choice?

• Personal and design-led documents: newsletters, flyers and reports with images are faster to lay out in Pages.
• Cost: Pages is free on every Mac, iPhone and iPad; Word needs a Microsoft 365 subscription for full editing.
• Apple devices: documents sync through iCloud and open on iPhone and iPad without a subscription.

How do you move a document between them safely?

Export from Pages with File, Export To, Word, and open the result in Word before you send it, rather than trusting that it converted cleanly. Check headers, footers, tables and any images placed inline with text, which are the elements that move most often. Going the other way, Pages opens .docx files directly, but keep the original Word file as the master copy if a colleague will edit it again.

So should you switch?

Use both, for different jobs, which is what I have always done. Anything that will be edited by a Windows-using colleague or client belongs in Word. Anything personal, visual or Apple-only is quicker in Pages. The grammar gap I wrote about in 2020 is narrower now; the compatibility gap is the one that still decides it.

Keep reading

• How latest iWork update impacts old Mac users
• Comet Browser Assistant vs Chrome: Where Google Falls Behind
• Microsoft 365 Family vs Google One for Photo Backup

Updated September 2026: this post began as my March 2020 diary of waiting for my manager to allow work from home as Covid-19 spread. Remote work is now a normal, negotiated arrangement, so I have rewritten it as a guide to asking for work from home well, with what that period taught me.

In early 2020 the coronavirus was spreading city by city. Traffic on my commute thinned, colleagues were quietly asking their onsite counterparts about working from home, and when I asked my manager, he said he would wait and decide. Within weeks the question was settled for everyone by lockdowns.

Six years on, work from home is rarely an emergency request. It is a negotiation over days, roles and trust. The lessons from that spring still apply.

Why did so many managers hesitate in 2020?

Mostly uncertainty. Few had managed a fully remote team, client contracts sometimes specified where work could be done, and nobody knew how productivity would hold up. The hesitation was less about distrust of individuals than fear of being the manager who got it wrong. Understanding that helps, because the same worries sit behind most refusals today.

How should you ask for work from home now?

• Know the policy first. Most large IT companies publish a hybrid policy with a minimum number of office days. Ask for something inside it, or explain clearly why you need an exception.
• Lead with the work. Say which tasks you do better remotely, such as focused documentation or late calls with overseas teams, and which you will still do in person.
• Offer a trial. Four to six weeks with a review at the end is easy for a manager to agree to and easy to extend.
• Put it in writing. A short email after the conversation avoids "I never agreed to that" later.

What should you avoid?

Asking in a crisis, when the manager is already stretched. Comparing yourself to a colleague who got approval, which makes it about fairness rather than work. And disappearing once approved. Being reachable during agreed hours is what keeps an arrangement alive.

What if the answer is no?

Ask what would change it. Sometimes the answer is a client requirement you cannot influence; sometimes it is a concern about a specific task that you can address. If you have a genuine need, such as caring for a family member, say so plainly and ask HR what formal options exist. A written refusal with a reason is more useful than a vague "not now", because it tells you whether to wait, adjust, or look elsewhere.

Looking back at March 2020

My manager's "let's wait and see" was frustrating then. What would have helped was a concrete proposal on my side: which work, which days, how I would stay reachable. It is the same proposal that gets a remote arrangement approved today.

Keep reading

• What a Fair Hybrid Work Policy Should Include
• Work Arriving Just Before Your Leave: What to Do
• Why Employees Resist the Return to Office

Updated September 2026: this March 2020 post described old work landing on my desk days before a long vacation. I have rewritten it into a guide to protecting planned leave when last-minute work arrives, which is the situation most readers are in when they search for it.

In March 2020 I had a long vacation booked and, for once, a light desk. Then an email arrived on an old service request thread, asking for my support "for the next few days". The days overlapped with my leave. I spent the evening torn between being glad of the work and worried it would eat into my holiday.

This happens to almost everyone in project work. Here is how to handle it without either refusing outright or giving up your break.

Should you accept work just before your leave?

Accept the work, not the timeline. The request is usually legitimate; the problem is only that nobody checked your calendar. Reply the same day, confirm you can help, and state your leave dates plainly in the same message. That one line changes the conversation from whether you will do it to how it gets done around your absence.

How do you agree what can be done before you go?

Break the request into pieces and say which ones you can finish before your last day. Offer a specific handover point for the rest: "I will have the first draft and the data sheet ready by Thursday evening; after that Priya can take it forward." Requesters are generally relieved to get a clear plan instead of an open-ended yes.

Confirm the plan with your manager at the same time. Leave that was approved should be protected by the person who approved it, but they can only do that if they know about the clash.

What if they insist you stay available?

Agree a narrow window rather than open availability. Thirty minutes on a fixed day, or phone contact for a named emergency, is reasonable for a critical item. "Just keep an eye on email" is not, because it never ends. If the pressure continues, it is fair to ask your manager whether the leave should be moved; putting the choice to them usually settles it in favour of your break.

How do you hand over cleanly?

• A short note listing what is done, what is pending and who owns each pending item.
• Links to every file, with access already granted to your cover.
• The requester's expectations in their own words, copied from the email thread.
• An out-of-office reply that names your cover, not just your return date.

What I learned from March 2020

That leave clashes are usually a planning gap, not bad faith. Stating your dates in the first reply and handing over properly lets most requesters work around them. Most of the anxiety comes from saying nothing and hoping it will sort itself out.

Keep reading

• How to Plan Leave in IT and Return to a Clear Desk
• How to Ask Your Manager for Work From Home
• When Your Only Teammate Leaves: Handover and Workload

Updated September 2026: the original February 2020 post was a diary entry about a client call that went unexpectedly well, leaving me with no work for a while. I have rewritten it into advice on using a quiet stretch at work well, which is the useful part.

In February 2020 I sat through an end-of-day call expecting the onsite team to change the requirements again, as they usually did. Instead, they accepted my slides as they were and took the deck forward themselves. For the first time in months I had nothing assigned.

That sounds like a gift. In an IT services company it often feels like a threat, because unallocated time is visible and people worry about being seen as spare. Here is how I would handle it now.

Is a quiet week a bad sign?

Not by itself. Work in services arrives in waves: an opportunity closes, the next one has not started, and there is a gap. It becomes a concern when the gap stretches into weeks and nobody is looking for your next assignment. The difference is whether you are managing the gap or waiting in it.

What should you do on the first day with no work?

Tell your manager, briefly and in writing, that your current item has closed and you are available. People often stay quiet hoping to enjoy the break, then get handed whatever unpleasant task is lying around. Saying it first lets you suggest what you would like to pick up next.

Then close the loop on the finished work. Save the final deck, note what the client accepted and why, and file any appreciation that came with it. That record matters at appraisal time.

How can you use the time well?

• Build something reusable: a template, a checklist or a reference deck your team keeps rebuilding from scratch. It is visible and it saves others time.
• Learn one thing with a certificate at the end: a cloud, security or product certification relevant to your accounts is easy to justify and easy to show.
• Fix your own tools: clean up your notes, your file structure and your email filters. It sounds small; it pays back every busy week after.
• Talk to people on other accounts: the next opportunity often comes from someone who knows you are free and competent.

How long is too long?

If you have been unallocated for more than a few weeks and your manager has no plan, ask directly what the plan is and when you will hear. Many companies have formal bench policies with time limits, and it is better to know yours than to be surprised by it. Keep your CV current during any long quiet stretch. That is not disloyalty; it is ordinary caution.

Quiet weeks end, usually sooner than expected. The point is to use the gap deliberately rather than spend it wondering what will land next.

Keep reading

• Keeping a Work Journal in IT: Why and How to Restart
• Working Under a Micromanager: A Practical Guide
• Preparing for Your Appraisal and Hike in Indian IT

Updated September 2026: in January 2020 I wrote a nervous note while waiting for my appraisal letter, and never followed it up here. I have rewritten it into what I wish I had done in the months before that letter.

In early January 2020 I was a day or two away from my annual hike and promotion letter, refreshing my inbox and wondering whether another year of work would be recognised. What bothered me most was that I had more years of experience than some people graded above me, and I had never raised it properly.

Waiting anxiously for a letter is the least useful part of appraisal season. By the time it arrives, the decision was made weeks earlier. The useful work happens before that.

When is your hike actually decided?

In most large Indian IT companies, ratings are calibrated by managers and their managers in a session you are not part of, usually weeks before letters go out. Budgets for hikes and promotions are set at company level first and then divided down. Your manager walks into that session with whatever they remember about your year, which is why the preparation has to happen well before it.

What should you prepare before the review?

• A one-page summary of your year: the work you delivered, with numbers where you have them, and the escalations you resolved.
• Evidence of scope above your grade: if you led work that someone at the next grade would normally lead, say so with examples.
• Feedback you received: client or onsite appreciation emails, saved in one folder through the year.
• Your ask: promotion, a specific kind of work, or a correction to your grade. Decide it in advance.

Hand the summary to your manager before calibration, not after the letter. Managers are grateful for it, because it makes their own case easier to argue.

How do you raise a grade that lags your experience?

Calmly and with facts. "I have eleven years of experience and I am graded below colleagues with seven" is a reasonable thing to say, but it lands better with evidence that your work is already at the higher level. Ask your manager what specifically stands between you and the next grade, and ask for it in writing. A vague "next cycle" answer repeated twice is information in itself.

What if the letter disappoints?

Do not reply the same day. Read it, sleep on it, then ask for a meeting to understand the rating. Go in asking what the gap was, not arguing that the decision was wrong. Most companies have a formal route to contest a rating, but it rarely changes the outcome in the current cycle. What it does is put your concern on record for the next one.

And be honest with yourself. If the market pays your experience noticeably more than your company does, a switch will usually move your salary further than any appraisal. Many people in Indian IT have found that the fastest raise comes from a new offer, not an old employer.

What I would tell myself in January 2020

Stop refreshing the inbox. The letter was already written. The time to influence it had been months earlier, with a one-page summary and a direct question about my grade, rather than two days of worrying about a decision that rested on someone else's memory.

Keep reading

• Keeping a Work Journal in IT: Why and How to Restart
• No Work Assigned in IT? How to Use a Quiet Week Well
• How to Ask Your Manager for Work From Home