Sunday, June 28, 2020

Two Urgent Tasks at Once: Finish Both Without Escalation

Updated September 2026: in June 2020 I had two tasks: solution slides from the onsite team, ahead of client information, and a task from my manager that I judged irrelevant. I prioritised so both were handled without escalation. I have rewritten it into a method for prioritising conflicting tasks without upsetting anyone.

One task came from the onsite team, who wanted solution slides before the client had shared information. The other came from my manager, based on details I felt were out of context. I needed both completed on time, without escalations or follow-ups. I knew my manager's task mattered less, so I parked it until the onsite work was done.

How do you decide which task comes first?

  • Client impact: work visible to the client or onsite team usually comes first.
  • Deadline: which is due soonest.
  • Dependencies: which unblocks other people.
  • Effort: quick tasks can be finished first to clear them.

Is it safe to park a manager's task?

Yes, if you tell them. "I'm finishing the onsite slides first, due at 5; your analysis will follow by tomorrow noon" is a plan, not neglect. Silently parking a task risks it being noticed as ignored.

How do you handle work requested before inputs arrive?

Build what is stable: structure, standard content, placeholders for client information. Flag the gaps clearly. It meets the request without inventing details.

How do you avoid escalations?

Communicate priorities early to everyone affected, deliver what you promised when you promised it, and send a short note on completion. Escalations usually come from surprise, not from the order of work.

What if you think a task is irrelevant?

Ask what it is for before deciding. Sometimes a manager's request has context you have not heard. If it still seems unnecessary, say so politely and suggest a lighter version, rather than ignoring it.

How do you keep track of several tasks?

A short list with the requester, due date and status for each, reviewed at the start and end of the day, is enough for most workloads.

What if both tasks are urgent?

Ask your manager to choose, with the facts. If they cannot, do the client-facing one first.

Keep reading

Sunday, June 7, 2020

Build a Personal Repository to Finish Work Faster

Updated September 2026: in 2020, working from home for two days before a long vacation, my manager asked in the afternoon for several documents by the next day. Instead of building them from scratch, I checked my repository for existing material and finished quickly. I have rewritten it into a guide to building a personal repository that saves you under pressure.

I had permission to work from home for two days before my leave and hoped for quiet. At noon, nothing. Then my manager asked for multiple documents by the next day. I was angry, but I have a habit of checking my repository for similar past work first, and it let me complete the documents quickly.

What is a personal repository?

Your own organised collection of past work: decks, documents, diagrams, estimates and useful answers to common client questions. It complements any team repository, and it reflects the work you actually do.

How should you organise it?

  • By topic, not by client or date.
  • With clear file names describing the content.
  • With a short index listing the most reusable pieces.
  • Removing client names and confidential details from reusable versions.

What should you save after each piece of work?

The final version, plus the two or three slides or sections that were strongest. Five minutes at the end of each request builds a valuable library over a year.

How do you reuse without making work look generic?

Use past material as a starting point, then tailor names, context and specifics. Clients and reviewers notice copied content quickly, especially if another client's name slips through.

What about confidentiality?

Follow your company's rules on storing documents. Keep the repository on company-approved storage, and never reuse confidential client data in another proposal.

How do you keep it current?

Review it every few months. Replace outdated figures, remove material that no longer reflects your company's offerings, and mark the date each item was last checked. A repository full of stale content is almost as slow as having none.

How did it help before my leave?

It turned an evening of work into a couple of hours, leaving my last day for handover rather than drafting.

Keep reading