Kefiw

Archived noindex page. Kefiw's public focus is Property decision help.

Archived page

This older Kefiw page is kept for reference, marked noindex, and removed from the primary sitemap. The current Kefiw experience is focused on property decisions: cost, quotes, damage, buying, selling, owning, and packets.

Go to Property

When to Audit Task Switching

Five moments when counting your concurrent contexts changes your week.

Task Switching earns its keep when the hours disappear and you cannot say where.

Task Switching Tax is a diagnostic, not a dashboard metric. It fires when something in your week does not add up — you worked hard, output is thin, and the hours went somewhere. Five specific triggers surface the pattern.

Quick answer

Task Switching earns its keep when the hours disappear and you cannot say where.

What you are trying to do
Five moments when counting your concurrent contexts changes your week.
Limit to remember
Treat this as a practical aid for the task, not a replacement for professional judgment.

Key points

  • The missing-output week. Full calendar, exhausted by Friday, shipped less than expected. Count concurrent contexts; 4+ explains most of the gap.
  • Before accepting new work. Adding a 4th client to your 3-client plate costs ~20% of remaining capacity — not a fixed amount of hours. Run the math before you say yes.
  • Calendar redesigns. Quarterly, look at the last 2 weeks. If n averaged ≥ 4, the calendar is the problem, not the effort.
  • Monday planning. Set n explicitly for the week. If Monday already shows n=5 with no room to drop any, you are pre-committed to the overhead.
  • Tool and channel audits. Each additional Slack workspace, email inbox, or notification source is a concurrent context. Count them like projects.

Examples

  • Missing-output week
    Looked like 40 hours. Tool shows n=5 concurrent projects → 41% retention → 16.4 effective hours. Output matches 16 hours, not 40.
  • Fourth client decision
    Current: 3 clients, n=3, retention 64%. Adding 4th: n=4, retention 51%. Lost ~13% of remaining capacity — ~1 hour/day of previously-working time.
  • Tool audit
    3 projects × 2 tools each (Slack + email) + 1 personal = 7 channels. n=7 → retention 26% → you run the OS, not the app.

When to use which tool

Related

Frequently asked questions

How low should n be? How-to

Depends on the work. Deep-work knowledge jobs want n ≤ 2. Management roles can survive n=3-4. Above 4 for any role means the calendar design is broken, not you.

What about unavoidable contexts — family, health, etc.?

They count. A parent managing school, work, and a medical issue is already at n=3 before adding anything else. Plan professional n around personal n, not independent of it.

How should I use a decision framework in real life? How-to

Use a decision framework to expose the tradeoff, not to outsource the decision. Write down the inputs, compare the output with your constraints, then ask what would change the answer. The strongest use is scenario testing: base case, conservative case, and failure case.

Is this financial, legal, or tax advice? Trust & accuracy

No, this is not legal, financial, tax, medical, or professional advice unless the page explicitly says that use case is supported. It organizes assumptions so you can inspect them. Verify high-stakes choices with qualified people who can review facts, contracts, regulations, and downside risk.

What assumption matters most in a decision model? Edge case

The most important assumption is usually the one you are least certain about and most emotionally attached to. Change that input first. If the recommendation flips after a small change, the decision is fragile and needs more evidence before you treat the model as useful.