You will be able to decide what to do with a task in each box of the matrix.
It's Monday morning and Priya, a marketing executive at a consumer brand's office in Paya Lebar, opens her laptop to 43 unread emails, a Teams message from her manager asking for "a quick look" at a deck, and a reminder that the campaign brief for the year-end sale is due on Friday. She also promised herself she would finally finish the online analytics course she started in July. By ten, she has answered eleven emails and has not touched the brief.
In lesson 1.1 you sorted yesterday's work into the four boxes of the Eisenhower matrix. Sorting is only half the method. Each box comes with its own action, and once you know the action, a long list stops being one undifferentiated pile. This lesson goes through the four boxes one at a time.
These are the real fires. A client cannot log in to the system your team runs. A payment has to go out today or a supplier stops delivery. Your manager needs figures for a meeting that starts in an hour. You do these straight away, because waiting makes them worse.
The useful habit comes after the fire is out. Ask one question: could better planning have stopped this from becoming urgent? Many fires are important tasks that sat in the second box until someone started shouting. The deck Priya's manager wants by noon may be a deck that was mentioned three weeks ago. If the same kind of fire keeps coming back, the fix belongs in the important but not urgent box: a checklist, an earlier reminder, a conversation about deadlines.
This is the box that decides how your year goes, and it is the one that loses every day. Priya's campaign brief is due Friday, so on Monday it feels like it can wait. Her analytics course has no deadline at all, so it can wait forever.
A list does not protect this work. A list says "someday". A calendar entry says "Tuesday, 9 to 11am, in the small meeting room with notifications off". The rule for this box is simple: give the task a time, not just a place on a list. If it is large, give it several times. If someone tries to book over that slot, treat it the way you would treat a meeting with a client and offer another time.
Priya blocks Tuesday and Wednesday mornings for the brief and puts the course on Thursday evening from 8 to 9pm. The work is exactly the same size as before, but now it has somewhere to happen.
This box is where most of a busy day goes. It's the work that arrives loudly but does not move your own goals much: many meeting invites, requests that someone else could answer, a "quick look" that is really a favour, forms and approvals.
You have four moves here, and they work best in this order.
Batch it: collect similar small requests and handle them together, for example all approvals at 4pm, instead of one at a time as they land. Shorten it: reply in two lines rather than ten, join the part of the meeting where you are needed, send a voice note instead of scheduling a call. Delegate it: if a colleague or a team member is the better person, pass it on with what they need to finish it. Push back on it: ask about the deadline. "Is end of day okay, or do you need it before lunch?" is a fair question, and the answer is often end of day.
Pushing back is the hardest one if you are new to a role or work in a team where saying no to a senior person feels risky. You do not need to say no. You need to ask a question that lets the other person tell you how urgent it really is. If you want help with the wording, lesson 4.3 of Communicate at work: writing, speaking and meetings, Clarify the task before you start, covers how to ask about deadlines and priority without sounding difficult.
The last box holds the work that feels like work but is not. Refreshing your inbox to see if anything new has come in. Scrolling LinkedIn "for research". Reading every message in a 200-person company channel. Reformatting a document nobody will see. Keeping a report going that nobody has opened since the person who asked for it left.
Drop it. Some of it you can stop on your own today. Some of it, such as a weekly report that may still be read, needs a quick check with your manager first. Ask, and if nobody misses it for a month, it was in this box.
Notice how much of this box is checking: feeds, messages, whether someone has replied yet. Each check feels small, but it often pulls you out of something that mattered. Module 5 deals with notifications and chat in detail. For now, just notice the pattern.
You will not have time to think hard about every task, and you don't need to. With practice, the decision takes a second or two: is this a fire, something that needs a slot, something to batch or pass on, or something to stop? When you are unsure whether a task is important, ask whether it connects to one of the few outcomes your role is judged on. Lesson 1.3 helps you find those outcomes, and once you know them, the important question gets much easier to answer.
Priya ends her Monday with the brief blocked in, the deck reviewed in a twenty-minute slot after lunch, three approvals batched for the afternoon, and her company-wide channel muted. The list is as long as it was at nine, but every item on it now has a next move attached.
Now take the list you made for lesson 1.1. Choose five tasks from it, ideally from different boxes, and decide what you will actually do with each one.
Pick five tasks from yesterday's list and write the action you will take on each: do, schedule, delegate or drop.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).