Principle · Chief of Staff

Urgent vs. Important.

Source: Stephen R. Covey, The 7 Habits of Highly Effective People (1989), Free Press. Attributed by Covey to Dwight D. Eisenhower (the "Eisenhower Matrix").

The Principle

Urgent work shouts. Important work whispers. The brain is wired to respond to urgency (a ringing phone, an incoming email, a today-deadline) even when the urgent thing is not actually the most important. Important work is the work that produces strategic outcomes over time but rarely has today's deadline attached: content creation, systems building, relationship investment, learning, thinking.

If a calendar fills with urgent work by default, important work never happens. The Eisenhower Matrix sorts tasks into four quadrants. Effective operators spend the majority of their time in the Not Urgent + Important quadrant (Q2), because that is where structural progress lives. Reactive operators spend their time in Q1 (urgent fires) and Q3 (other people's urgency), and wonder why nothing compounds.

Urgent + Important

Crises, deadlines on essentials. Do first. Goal: shrink this quadrant over time by handling Q2 well.

Not Urgent + Important

Strategic work, relationships, prevention, learning. Schedule first. Protect aggressively.

Urgent + Not Important

Other people's urgency, most interruptions, many meetings. Delegate, batch, or decline.

Not Urgent + Not Important

Entertainment distractions, busywork. Eliminate.

Why It Matters Here

Chief of Staff owns the founder's time allocation. The default failure mode is reactive scheduling: whatever comes in drives what gets done. Important work is always pushed to "next week" because something urgent popped up. Applying this principle rigorously means scheduling Q2 work FIRST -- blocked, protected, non-negotiable -- and fitting urgent work around it rather than the reverse.

Signals (When to Apply)

Scheduling the week or the day
A new inbound request is interrupting planned work
The founder is reporting "too much to do" but most of what was done was reactive
Important projects are slipping quarter after quarter
The calendar is full but the week produced no forward motion on strategic goals

How to Apply

Categorize every task into one of the four quadrants before deciding when to do it.
Block Q2 work on the calendar first, every week. Treat these blocks as appointments that cannot be moved without equal-value justification.
When an urgent request arrives, ask: is this urgent AND important? If not important, route to decline, defer, or batch. Most urgent things are urgent to someone else, not important to you.
Track the ratio of time spent in Q2 vs. Q1+Q3 over a week. If Q2 is under 40% of productive hours, the reactive failure mode is dominant.
Watch for fake urgency. Most things framed as "urgent" are not actually urgent when examined. The framing is a request for your attention, not a statement of real time pressure.

Examples

Applied well A founder's Monday calendar has 8am-11am blocked for "V1 product work" (Q2). Tuesday morning, a client sends a "quick question that's urgent." The founder looks at the question, recognizes it as Q3 for her (urgent to the client, not critical to the business this morning), sends a one-line reply promising an answer by end of day, and returns to the Q2 block. The Q2 block produces 3 hours of compounding work. The client gets their answer by 5pm and is satisfied. Both things got done. Important work did not get sacrificed to urgent work.

Misapplied Same founder receives the "urgent" question, drops the Q2 block, spends 90 minutes solving the client's question. The Q2 block is rescheduled for "later this week." By Friday, later-this-week has been occupied by other urgent interruptions. The week ends with zero forward motion on V1. The client's question got answered. Nothing else important did.

When to Break It

In genuine crisis situations where Q1 expands and requires full attention for a short, bounded period (a delivery crisis, a team emergency, a health issue). Shift fully to Q1 during the crisis, then rebuild Q2 discipline when stable.
During pre-scheduled reactive periods (e.g., "Friday is for client communication, everything else is Monday-Thursday"). Batching urgency into known windows is itself a Q2 strategy. The rule is adapted, not broken.
For certain professional roles where Q1 IS the job (ER doctor, crisis responder, incident commander).