Most teams do not have a work problem. They have a sorting problem. Everything feels urgent. The loudest request wins. The thing that would actually move the week sits untouched until Friday, when someone asks why it slipped.

The Eisenhower method is a way to stop that. You look at each task and ask two questions: is this important, and is this urgent? Then you put it in one of four boxes. That is the whole method. No special vocabulary. No software required — except that a spreadsheet in a private tab is how the method quietly dies on a team.

A team needs the four boxes on a wall everyone can see. That is what a weekly planner for small teams is for.

Important is not the same as loud

Urgent work has a timer on it. A client is waiting. A deploy is broken. Someone pinged you twice. Important work changes the outcome of the week, or the month, even if nobody is tapping their foot. Those are different questions, and mixing them up is how a team spends Tuesday on a thread that will not matter on Thursday.

Two axes give you four kinds of tasks:

• Important and urgent. Do these now. They are both real and due.
• Important and not urgent. Protect these. They are the work that makes next week easier, and they are the first to get stolen.
• Urgent and not important. These feel like work. They often belong to someone else, or they are interruptions dressed up as tasks.
• Not important and not urgent. Park them or drop them. A board that cannot say no is just a list.

If your team only has a single column called "to-do," you are mixing all four. The fire-fighting lives next to the strategy. People pick the fire because it yells. Nobody is being lazy. The board did not give them another way to choose.

Why a personal matrix is not enough

You can run this in a notebook. Plenty of people do. The trouble starts when five people each have a private matrix. Your "important" is my "later." Your fire is a surprise on my Tuesday. Nobody is lying. They just cannot see the same week.

That is the gap a team task board is supposed to close. Not another status meeting. A shared picture of what is on fire, what matters, and what can wait — updated as the week moves. If the picture lives in one person's head, the team is not using a method. They are using a manager.

4square is a lofi task board built as that picture. Four quadrants, one week, everyone looking at the same grid. You can learn it in a couple of minutes because there is almost nothing to learn: put the task in the box it belongs in, then get back to the work.

How the four quadrants map

On the 4square board the axes are impact and urgency. Same method, in words a team will actually say out loud.

• High impact, high urgency. The week's true "do these." If this box is overflowing, you do not have a productivity problem. You have a planning problem from last week.
• High impact, low urgency. The work that makes you better. Design the thing. Write the doc. Talk to the customer before they are angry. This is the box the method is famous for protecting, and it is the box most tools bury under a backlog.
• Low impact, high urgency. The taps on the shoulder. Answer them, hand them off, or shrink them. If this box runs the week, the important work will not.
• Low impact, low urgency. Last. Nice ideas, leftover chores, things that feel like progress. Be honest here.

There is a fifth place: Saved for later. That is not a cop-out. It is how you keep this week's matrix honest. If it is not this week's work, it should not compete with this week's work. Park it, then look at it when you plan the next week.

A prioritized matrix only works if the boxes stay small enough to read in one glance. 4square is designed so you can see the whole week in one glance. If you cannot see it, you cannot argue about it, and if you cannot argue about it, the loudest person wins again.

One week at a time is the point

The method fails in tools that never reset. A backlog that is three months deep is not a matrix. It is a museum. Everything is "important" because nothing ever leaves. People stop trusting the board, and then they stop looking at it.

4square plans one week. Monday, the board is the week you are in. That constraint is the method. You cannot hide fifty important-not-urgent tasks in a someday list and pretend you made a choice. You have to pick the ones that belong in this week, put the rest in later, and live with it.

When the week turns, you do it again. That is how a weekly task planner earns the name. The method is not a poster on the wall. It is a habit with a date on it. A team that re-sorts every Monday is doing the work of Eisenhower without needing to say the word in the meeting.

Make the matrix a team sport

A matrix on one person's laptop is a preference. A matrix on a shared board is a decision.

On a 4square team board, when you drag a task from high impact, low urgency into high impact, high urgency, everyone else sees it. No status round. No "I'll update the tracker later." The picture is the conversation: why did this become a fire? Who is on it? What gets bumped?

You can assign people to a task so "delegate" is not a euphemism for "hope." Urgent-but-not-important work should move to the person who can actually finish it, not bounce around the loudest chat thread. Names on tasks are how a small team turns a quadrant into an agreement.

Comments stay on the task, so the "why is this in this box?" discussion does not live in a side channel the board cannot see. None of this requires a workflow engine. It requires a board that is alive. 4square updates in real time, which sounds like a feature list until you have watched a standup where three people are looking at three different versions of the week.

A Monday you can actually run

You do not need a workshop. You need twenty minutes and a four-quadrant board.

• Dump the week. Everything you think you are doing goes on the board. Do not sort yet. Sorting too early is how important work gets labeled urgent to make it feel safe.
• Sort together. For each task, ask: if we skip this, does the week fail, or does someone just get annoyed? Impact first, then urgency. People will disagree. That disagreement is the meeting.
• Protect the important-not-urgent box. Put real tasks in it, with names on them, not vibes. If that box is empty, you already know how the week will feel on Friday.
• Drain the urgent-not-important box. Assign it, shrink it, or say no. This is the box that steals the week in fifteen-minute slices.
• Be ruthless with last. Move leftovers to Saved for later. A clean last box is a gift to future-you.

Then work the board. When something new shows up — and it will — do not append it to a nameless list. Put it in a quadrant. If it is a fire, it has to bump something. That bump is the method working. A week with no bumps is a week that was not honest on Monday. If the board still looks like Monday on Thursday, something is stuck — usually in the urgent-not-important box.

What this is not

It is not a personality test. It is not a way to feel busy. It is not an excuse to ignore people who need you. Urgent work is still work. The method only asks that you stop pretending every ping has the same weight as the thing that would change the week.

It is a shared language for small teams who are tired of every task arriving with the same volume knob. Urgent versus important is enough language. The rest is whether you can see it, together, before the week gets away from you.

4square will not run the method for you. It will hold the four boxes still long enough for a team to use them. If you want a weekly planner that stays out of the way and still makes the Eisenhower choice visible — impact against urgency, this week, with the people you actually work with — that is the product.

Try it on this week's real work, not a demo dataset. The method only counts when the tasks are yours. Start a board — or come back to the product page if you want the short version first.