Comparing by fit
Two ways of thinking, side by side. There is no winner here — read across each row and choose the one that fits your situation.
Decision Making
Strip a problem back to what must be true, then rebuild — instead of copying what exists.
By 6days
Operations
Separate urgent from important, and notice how much of your week serves neither.
By 6days
When to use — First-Principles Thinking
Use it when an industry's costs or practices have been stable for a long time without obvious justification, when you are entering a field as an outsider and lack the incumbents' assumptions, or when repeated incremental attempts have all failed and the problem may be framed wrongly.
When to use — Eisenhower Matrix
Use it when you are busy but not progressing, when a team is permanently reactive, or during a periodic review of where a role's time actually goes. It works well as a recurring habit rather than a one-off, and it is a useful device for a manager and report to look at a workload together without it becoming personal.
When not to use — First-Principles Thinking
Avoid it for routine decisions — it is slow, effortful, and analogy is right most of the time. It is also a common vehicle for arrogance: reasoning from first principles while lacking domain knowledge tends to rediscover why the convention exists, expensively. If experts cannot explain why a practice exists, that is worth investigating; if they can, listen.
When not to use — Eisenhower Matrix
Avoid it where you have little real autonomy — telling someone to delegate work they cannot delegate is just a way of blaming them for their constraints. It handles individual tasks better than long collaborative efforts, and it has nothing to say about work that is important to someone else and not to you, which is most of what makes a job hard. It also assumes you can tell importance from urgency, which is exactly the skill people struggling with this tend to lack.
Most reasoning is analogy: we do it this way because that is how it is done, because the incumbent does it, because we did it last time. Analogy is efficient and usually right, which is exactly why it is dangerous — it carries forward constraints that were real once and quietly expired. Whole industries hold assumptions nobody has tested in decades, because testing them was never anyone's job.
Urgency is loud and importance is quiet. Work that matters — the strategy, the fix that prevents next quarter's incident, the conversation with the struggling team member — has no deadline, so it loses every day to whatever is shouting. Weeks pass full of activity and empty of progress, and the diagnosis is always 'no time', when the truth is that the important work never once won a scheduling contest against the merely urgent.
First-principles thinking decomposes a problem to the things that must be true — physics, arithmetic, contract terms, hard constraints — and reasons upward from there, deliberately ignoring how the problem is currently solved. The hard part is not the rebuilding; it is telling a real constraint from an inherited convention. 'Water boils at 100°C at sea level' is a principle. 'Enterprise software is sold through channel partners' is a convention wearing a principle's clothing. The method is expensive and usually unnecessary — its value is concentrated in the rare cases where a load-bearing assumption is simply wrong.
The matrix sorts work on two independent axes: important (contributes to outcomes you care about) and urgent (demands attention now). The four quadrants get different treatment. Important and urgent: do it, but treat its existence as a signal, since most crises are the residue of neglected important work. Important, not urgent: schedule it, because this is where nearly all real progress lives and it will never demand attention on its own. Urgent, not important: delegate it, or resist it — it is usually someone else's priority wearing your calendar. Neither: stop. The insight is that urgent and important are genuinely independent, and most people's calendars silently assume they are the same axis.
Write the problem so that no current approach is embedded in the wording. 'How do we make our call centre more efficient' has assumed a call centre. 'How do customers get their question answered' has not, and the two questions have very different answer sets.
Write down everything you believe about the problem, especially what feels too obvious to state. The load-bearing assumptions are always the ones nobody thought worth writing down, because obviousness is what protects them from scrutiny.
For each, ask what would happen if it were false, and demand evidence for why it holds. Laws of physics, arithmetic, and binding contracts survive. Industry practice, precedent, and 'the customer expects it' usually turn out to be conventions that someone chose, under conditions that may no longer apply.
Construct a solution using nothing but the constraints that survived. Do not check it against the existing approach yet — the comparison will pull you back toward the familiar before the new idea has finished forming.
Not specified
A two-by-two matrix. The horizontal axis runs from Urgent on the left to Not urgent on the right; the vertical axis runs from Important at the top to Not important at the bottom. Top-left: Do now — Crises and hard deadlines, Pressing problems you must handle. Top-right: Schedule — Planning and strategy, Relationships and prevention. Bottom-left: Delegate — Interruptions and some meetings, Requests that are someone else's priority. Bottom-right: Delete — Busywork and time-wasters, Habitual activities that add nothing.
Worked example — First-Principles Thinking
A team is quoted £40,000 for a piece of lab equipment and treats it as fixed. Decomposed: what is it actually made of? A precision stage, a camera, a light source, a controller, an enclosure, and software. Priced as components, roughly £6,000. The remaining £34,000 is not physics — it is certification, low production volume, support, and margin, all of which are real costs but not laws. For a regulated clinical setting the £40,000 is justified and the analysis ends there. For an internal research rig that needs no certification, most of that gap is avoidable, and the team builds it for £9,000.
Worked example — Eisenhower Matrix
An engineering manager audits a week. Urgent and important: a production incident, four hours. Urgent, not important: eleven meetings where they were informed rather than needed, nine hours. Important, not urgent: hiring, the architecture decision blocking two teams, and a struggling report's development conversation — zero hours, as every week. Neither: two standing meetings inherited from a reorganisation eighteen months ago that nobody has cancelled. Declining six meetings and booking two protected blocks moves nine hours into the quadrant that was empty. The incident, it later turns out, was caused by the architecture decision that never got made.
The idea is ancient: Aristotle described reasoning from first principles, and the method underpins mathematics and physics as disciplines. Its modern circulation in business owes much to engineering culture and to founders who have publicly credited it for cost-structure decisions. It is common intellectual heritage rather than anyone's proprietary framework.
The urgent-versus-important distinction is popularly attributed to Dwight D. Eisenhower, who quoted a formulation of it in a 1954 address and credited it to an unnamed university president. It was later developed into a four-quadrant tool by Stephen Covey and others in the time-management literature of the 1980s and 1990s. Eisenhower did not devise the matrix that bears his name.
Set the rebuilt solution against the status quo. Often the status quo wins, which is a real and useful result: you now know why it is right rather than merely inheriting it. Occasionally the gap is enormous, and that is what the whole exercise was for.
List the actual demands — tasks, meetings, requests, the recurring things you have never questioned. Work from your real calendar and inbox rather than from memory, which reliably omits the routine items that consume the most hours.
Importance is meaningless in the abstract, so name the outcomes you are accountable for and judge each item against them. Anything that contributes to none of them is not important, however comfortable or familiar it is.
Ask what genuinely happens, and to whom, if this waits a week. Most 'urgent' items have a soft consequence and a loud sender. Rating this independently of importance is the whole mechanism; collapsing the two axes reproduces the problem you came to solve.
Do the important-and-urgent, delegate or decline the urgent-but-not-important, delete the rest — and then actually put the important-not-urgent work in the calendar as a booked commitment. If it stays on a list it will lose again next week, exactly as it lost last week.