Overview
Classical Laws and Decision Heuristics is a curated reference that gathers eleven well-known laws, from Parkinson and Hofstadter to Goodhart, Hanlon, and Chesterton, and reframes each as a practical diagnostic tool rather than a piece of trivia. Its governing rule is simple: use a law to improve judgment, not to avoid thinking.
The material is organized into six domains: time and effort, human behaviour and performance, decisions and options, measurement and incentives, attribution and reasoning, and systems and traditions. Within each, every law is presented with a plain-language meaning, an operating rule, a diagnostic question to ask in the moment, and a guardrail that marks where the tool stops being useful.
What makes the collection more than a list is the discipline around it. The guardrails do most of the quiet work, blocking the common failure where a heuristic turns into a rationalization. Occam's Razor is paired with a warning not to dismiss inconvenient evidence, Hanlon's Razor with a reminder that patterns of misconduct still matter, and Pareto with a caution against neglecting the maintenance and relationships that resist measurement.
The laws are also built to be combined. Hofstadter and Parkinson together produce realistic estimates with tight execution blocks. Hick and Occam together narrow options and then test their assumptions. The reference closes with a combined decision routine and a twelve-question review checklist, turning the individual laws into a single repeatable pass before any significant commitment.
Treated as a Personal OS component, the value is not any single law but the habit of running the right diagnostic at the right moment, and knowing exactly where each one breaks.
Free Handbook
Download the branded PDF field guide
All eleven laws, the operator decision routine, and the review checklist in a clean, printable handbook you can keep beside your desk.
Download the PDFMost of these laws are individually famous and easy to quote. The value here is in the packaging. Each one carries an operating rule and a guardrail, which is the difference between a memorable phrase and a usable tool. A law you can recite but misapply is worse than one you never learned.
The guardrails are the reason the collection holds up over time. They keep the razors from becoming lazy dismissals, keep 80/20 from excusing neglect, and keep metrics from quietly replacing the outcomes they were meant to track. That self-correcting structure is what lets the set stay useful long after the novelty of any single law wears off.
The combined routines are where the leverage sits. On its own, each law catches one class of error. Run as a sequence before a commitment, they catch estimation errors, coordination traps, metric gaming, confidence inflation, and ignorant reform in a single pass. For anyone making frequent decisions with limited time, that sequence is the real asset.
Key Points
- These are diagnostic tools, not laws of nature. The governing rule is to use a law to improve judgment, never to replace the thinking.
- Every law here is paired with a guardrail, and the guardrail is what prevents the tool from quietly becoming a rationalization.
- The time laws interact. Use Hofstadter for the honest calendar commitment and Parkinson for the tight execution block inside it.
- Leverage concentrates. A minority of causes drives most results, but maintenance, duty, and relationships resist measurement and must not be dropped just because they are hard to count.
- Adding people to a late, tightly connected effort usually adds coordination cost before it adds capacity. Find the real constraint first.
- Promotion is a change of profession, not a reward. Competence at one level does not transfer automatically to the next.
- Confidence is not evidence. Calibrate it against mechanism and prior results, and apply the razors to yourself before anyone else.
- Fewer, genuinely different options decide faster. Reduce the set before comparing, and use defaults for anything routine.
- Any measure that becomes a target degrades. Give every metric a purpose, a balancing metric, and a review date.
- Prefer ordinary explanations, error over malice and simplicity over complexity, but never to the point of ignoring real evidence or a repeated pattern.
- Understand why a rule exists before removing it. Ignorant reform recreates the exact failure the rule was built to prevent.
- Small consistent actions compound. Judge a habit or a repeated decision over a multi-year horizon, not by a single outcome.
Quotable
AI-generated from source material. Verify important details against the original source.
C. Northcote Parkinson
"Work expands to fill the time available for its completion."
The most quoted line on productivity because it explains procrastination and scope creep in one breath, and it hands you the fix by implication: shorten the container.
Douglas Hofstadter
"It always takes longer than you expect, even when you account for Hofstadter's Law."
The self-referential twist is the whole point. It names the stubbornness of the planning fallacy and warns that a single buffer is rarely enough.
Fred Brooks
"Adding people to a late project makes it later."
It reverses the instinct that lateness is a staffing problem, and forces the harder question of what the real constraint actually is.
Charles Goodhart
"When a measure becomes a target, it ceases to be a good measure."
One sentence that predicts almost every incentive failure in business, media, and management. It is the reason dashboards drift away from reality.
Hanlon's Razor
"Never attribute to malice what error or neglect explains just as well."
It defuses conflict before it starts by pointing at the most common cause of friction, which is ordinary human error rather than hostility.
G. K. Chesterton
"Do not remove a fence until you know why it was put up."
A compact argument for humility in reform. It does not forbid change, it just demands you understand the thing before you break it.
Concepts
Time and Effort
Parkinson's Law
A task handed an open-ended block of time tends to swell to fill it, absorbing extra polishing, distraction, and delay along the way. The practical move is to set the container before you start: define the outcome, the acceptable standard, the maximum time, and what you will deliberately leave out.
The guardrail is that compression is not the same as haste. Some work genuinely needs reflection, testing, or recovery time, and a time box is meant to remove waste, not care.
Hofstadter's Law
People underestimate unfamiliar or interdependent work because they estimate the visible task and forget the setup, research, troubleshooting, revisions, coordination, and delivery around it. The fix is to separate the ideal execution estimate from the calendar commitment, and to build the commitment on the full picture.
Combined with Parkinson, it produces the useful pattern of realistic project timelines with tight execution blocks inside them, so the buffer does not become an excuse to drift.
Pareto Principle
Causes and results are rarely evenly distributed. A small share of actions, clients, habits, or problems tends to account for most of the outcome, so the first step in any optimization is to find the vital few before touching the useful many.
The guardrail keeps this honest: some foundational work, duty, and relationships create value that is hard to measure. Distinguish high-leverage work from necessary maintenance and from avoidable low-value work, rather than cutting whatever is hardest to quantify.
Brooks's Law
Extra people do not convert instantly into extra capacity. They bring onboarding, explanation, supervision, and integration, and on tightly connected work that coordination cost can outweigh the added labour. Before adding anyone, name the exact bottleneck, which is often unclear scope, poor sequencing, or a missing decision rather than a shortage of hands.
This is not an argument against delegation. It is an argument for delegating early and structurally, with a defined work package and clear ownership, rather than in a panic near the deadline.
Human Behaviour and Performance
Peter Principle
Strong performance in one role tends to earn a promotion into a role that requires different abilities, so a good technician can become a weak manager and a capable operator an overwhelmed executive. Treating each major role change as a change of profession, and checking the fit before the move, avoids rewarding competence by removing someone from the work they do well.
The constructive response is to build advancement that does not depend on management: autonomy, specialist status, ownership, project leadership, or higher pay.
Dunning-Kruger Effect
With limited knowledge in an area, a person can lack the very knowledge needed to see the limits of their own competence, while genuine experts often underrate how unusual their knowledge is. The lesson is broader than the caricature: confidence and competence are simply not reliable substitutes for evidence.
Calibrate a strong opinion against mechanism, prior results, and what would prove it wrong. The guardrail is to apply the effect to yourself first, not to use it as a label for people who disagree.
Decisions and Options
Hick's Law
Decision time rises as the number and complexity of choices rise, which shows up as slower calls, comparison cost, fatigue, and weaker commitment afterward. Extra choice only pays off when the differences genuinely change the outcome, so reduce the set before comparing and lean on defaults and checklists for anything routine.
The guardrail is to avoid stripping out meaningful alternatives just to feel fast. High-consequence decisions may deserve a wider search before you narrow.
Measurement and Incentives
Goodhart's Law
Once a measure becomes a target and people are rewarded for it, they tend to improve the number without improving the reality behind it, whether that is page views, response times, follower counts, or task completion. Measuring the purpose rather than the visible activity is what keeps the metric honest.
In practice, give every metric a stated purpose, a balancing metric, a qualitative review, and a review date. If a number could improve sharply while the real situation gets worse, it needs a counterweight.
Attribution and Reasoning
Hanlon's Razor
Most frustrating outcomes trace to missing information, poor communication, unclear responsibility, or ordinary human error rather than hostility. Investigating ordinary failure before concluding hostile intent protects both relationships and the quality of the decision that follows.
The guardrail matters: this is not a command to ignore repeated misconduct or deception. Patterns change the reading. Charity in interpretation is meant to pair with accuracy in observation, not replace it.
Occam's Razor
When several explanations fit the same evidence, the one with the fewest unsupported assumptions is the better starting point. The claim is not that reality is always simple, only that complexity should not be added without evidence that demands it. Start with the simplest sufficient model and elaborate only when the facts force it.
The guardrail is that a simple explanation which ignores inconvenient evidence is not the better one. Simplicity serves the evidence, it does not overrule it.
Systems and Traditions
Chesterton's Fence
Rules, processes, and traditions can look pointless once the problem they solved has been forgotten, and removing them blindly can quietly recreate the original failure. Understand who built the thing and what it was meant to prevent before eliminating it, then retain, repair, simplify, replace, or retire it on purpose.
This is not an argument against reform. It is an argument against ignorant reform, which is a very different thing.
Supporting Concepts
Compound Effect Thinking
Consistent small choices and habits accumulate into large long-term results, which means repeated actions should be judged over years rather than by any single outcome. When reviewing performance or weighing a decision, ask what happens if this is repeated for three years, because that is closer to the real stakes than the immediate result.
Combining the Laws
The laws are strongest in combination. Planning uses Pareto for the target, Parkinson for focus, Hofstadter for the timeline, and Brooks before adding people. Decisions use Hick to narrow, Occam to compare, Dunning-Kruger to calibrate, and Hanlon to interpret others. Reviews use Goodhart against gaming, Pareto to locate causes, Peter to test role fit, and compounding to weigh repetition. System changes use Chesterton to understand, Goodhart to check incentives, Occam to design the replacement, and Hofstadter to time the transition.
Implementation
AI-generated from source material. Verify important details against the original source.
Name the vital few
Before optimizing anything, identify the small set of actions, clients, or problems driving most of the result. Pareto is a filter you run first, so effort lands where it changes the outcome rather than where it feels busy.
Estimate honestly, then box the work
Separate the realistic delivery commitment from the execution block. Use Hofstadter to size the full job including setup, revision, and handoff, then use Parkinson to work inside a tight block so the buffer does not turn into drift.
Find the constraint before adding people
When something is late, resist the reflex to add hands. Diagnose whether the bottleneck is labour, scope, sequencing, a missing decision, or an unrealistic deadline. If you do delegate, define the work package, the output, and the owner up front.
Narrow, then compare on assumptions
Reduce a decision to two or three genuinely different options with Hick, then use Occam to prefer the path or explanation that needs the fewest unsupported assumptions. Kill noise options early so the real comparison gets full attention.
Calibrate your confidence
Before trusting a strong opinion, demand evidence, a mechanism you can explain, and prior results. Ask what would prove you wrong. Apply the Dunning-Kruger test to yourself first, especially where the topic feels familiar but you have not actually done the thing.
Read others charitably but accurately
When someone frustrates you, look for the non-malicious explanation that fits the facts you actually have: misunderstanding, missing information, unclear responsibility, or process failure. Hold that charity alongside honest tracking of patterns, because repeated behaviour changes the reading.
Guard your metrics
For every number you act on, attach a purpose, a balancing metric, a qualitative check, and a review date. Ask whether the number could improve while the real outcome gets worse. If yes, it needs a counterweight before it drives behaviour.
Understand the fence before you move it
Before removing a rule, process, expense, or safeguard, find out who created it and what failure it was meant to prevent, and whether that problem still exists. Then decide deliberately to retain, repair, simplify, replace, or retire it.
Match the role to the person
Treat any significant role change as a new profession. Compare the abilities that produced success now with the abilities the new role needs, decide whether the person even wants that kind of work, and build advancement paths that do not force everyone into management.
Project the compounding
Before committing to a decision or a habit, ask what happens if it repeats for three years. Small consistent choices accumulate, so weigh the trajectory, not just the immediate result, and choose the repetition you actually want to live with.
Tools & Resources
These resources are curated in two groups. Mentioned Resources are pulled directly from the source material, and Suggested Resources are added to help you expand and apply the ideas beyond the original.
The following resources may contain affiliate links. As an Amazon Associate I earn from qualifying purchases at no extra cost to you. This does not influence the placement of links on this page.
Download
Free Handbook
Classical Laws and Decision Heuristics, PDF field guide
The full reference as a branded, printable handbook: all eleven laws, the operator decision routine, and the review checklist.
Download the PDFMentioned Resources
This source references no external tools, products, or platforms. It draws on established laws attributed to their original thinkers, listed as suggested reading below.
Suggested Resources
| Resource | Why It Fits |
|---|---|
| Parkinson's Law, C. Northcote Parkinson | The original essay on how work expands to fill available time, and the source of the collection's first law. |
| The Mythical Man-Month, Fred Brooks | The classic on software project management where Brooks's Law and the real cost of coordination are laid out. |
| Godel, Escher, Bach, Douglas Hofstadter | Where Hofstadter's Law first appears, set inside a wider study of self-reference and recursion. |
| The Peter Principle, Laurence J. Peter and Raymond Hull | The original treatment of how people rise to their level of incompetence in hierarchies. |
| The Compound Effect, Darren Hardy | A practical read on how small consistent actions accumulate over time, behind the compounding concept referenced in the review. |
Source Material
Original source attribution, metadata, and publication details are available in the Overview tab. This source material may originate from a transcript, article, report, presentation, newsletter, notes, or other media. Where applicable, transcription, formatting, extraction, or attribution errors may exist. Verify against the original source before republishing or relying upon the material.
Classical Laws and Decision Heuristics
Purpose
These laws are compact models for recognizing recurring patterns in work, judgment, organizations, and human behaviour.
They are not absolute laws of nature. They are diagnostic tools.
Use them to:
- identify hidden causes of delay, waste, and failure;
- challenge unrealistic plans and assumptions;
- simplify decisions;
- protect useful systems from careless change;
- distinguish human error from malicious intent;
- prevent metrics and processes from replacing their original purpose.
The governing rule is:
Use a law to improve judgment, not to avoid thinking.
1. Time and Effort
Parkinson's Law
Work expands to fill the time available for its completion.
Meaning
A task given an open-ended or generous amount of time will often become more complicated than necessary. Additional time invites procrastination, unnecessary refinement, distraction, and scope expansion.
Operating Rule
Assign a defined time box before beginning work. Use the shortest reasonable period that still permits competent completion.
Personal OS Application
Before starting a task, define: the intended outcome; the acceptable standard; the maximum time allocation; what will not be included.
Diagnostic Question
Am I improving the result, or merely filling the available time?
Guardrail
Do not confuse productive compression with reckless haste. Some work genuinely requires care, reflection, testing, or recovery time.
Hofstadter's Law
Everything takes longer than expected, even when Hofstadter's Law is taken into account.
Meaning
People systematically underestimate the time required for unfamiliar, complex, or interdependent work. Planning usually accounts for the visible task but overlooks: setup; research; troubleshooting; revisions; coordination; interruptions; recovery from mistakes; final delivery and documentation.
Operating Rule
Separate the ideal execution estimate from the calendar commitment.
Personal OS Application
For unfamiliar or complex work: estimate the direct work; add setup, testing, revision, and delivery time; identify dependencies; add a contingency margin; commit based on the full estimate, not the optimistic one.
Diagnostic Question
What work surrounding the task have I failed to count?
Guardrail
A buffer must not become permission to delay. Combine Hofstadter's Law with Parkinson's Law: use realistic project estimates; use tight execution blocks inside those estimates.
Pareto Principle
A minority of causes usually produces a majority of results.
This is commonly expressed as the 80/20 rule.
Meaning
Inputs and outputs are rarely distributed evenly. A relatively small number of activities, clients, decisions, habits, assets, or problems often account for most results. The ratio is illustrative, not exact.
Operating Rule
Identify the vital few before optimizing the useful many.
Personal OS Application
During planning and review, ask: Which activities create most of the value? Which clients produce most of the revenue or opportunity? Which problems create most recurring friction? Which habits produce the greatest improvement or decline? Which projects materially advance the larger mission?
Diagnostic Question
What small number of actions would make the rest easier, unnecessary, or more valuable?
Guardrail
Do not use the Pareto Principle to neglect maintenance, duty, relationships, or foundational work simply because their value is difficult to measure. The Personal OS should distinguish between: high-leverage work; necessary maintenance; avoidable low-value work. This aligns with the distinction between the small amount of work only the owner can perform and the larger body of work that can be delegated, automated, simplified, or eliminated.
Brooks' Law
Adding people to a late software project makes it later.
Meaning
Additional people do not instantly produce additional capacity. They introduce: onboarding; explanation; communication; supervision; integration; duplicated effort; unclear responsibility. The principle applies beyond software whenever work is complex and tightly interconnected.
Operating Rule
Do not respond to lateness automatically by adding people. First determine whether the constraint is: insufficient labour; unclear scope; poor sequencing; weak leadership; missing decisions; technical uncertainty; excessive communication; an unrealistic deadline.
Personal OS Application
Before adding help, define: the exact bottleneck; the work package being transferred; the expected output; the handoff method; the decision authority; the communication cost.
Diagnostic Question
Will another person remove the constraint, or create another coordination obligation?
Guardrail
Brooks' Law does not mean delegation is bad. It means delegation must occur early, clearly, and structurally.
2. Human Behaviour and Performance
Peter Principle
In a hierarchy, people tend to rise to their level of incompetence.
Meaning
Good performance in one role often leads to promotion into a different role requiring different abilities. Examples: a strong technician becomes a weak manager; a successful salesperson becomes an ineffective sales director; a capable operator becomes an overwhelmed executive. Past success does not automatically predict success at the next level.
Operating Rule
Treat every major role change as a change of profession.
Personal OS Application
Before accepting or assigning a new role, identify: the abilities that produced success in the current role; the abilities required in the new role; the gaps between them; the training, support, or structure required; whether the person actually wants the new kind of work.
Diagnostic Question
Am I rewarding competence by moving someone away from the work they do well?
Guardrail
Advancement does not always require management. Create alternatives such as: greater autonomy; higher compensation; specialist status; project leadership; ownership; advisory authority.
Dunning-Kruger Effect
Meaning
People with limited knowledge in an area may lack the knowledge required to recognize the limits of their own competence. At the same time, knowledgeable people may underestimate how unusual their knowledge is. The useful lesson is broader than "incompetent people are confident." Confidence and competence are not reliable substitutes for evidence.
Operating Rule
Calibrate confidence against demonstrated knowledge, evidence, and results.
Personal OS Application
When confidence is high, ask: What evidence supports this conclusion? What would an expert notice that I may be missing? Have I successfully done this before? Can I explain the mechanism, not merely the conclusion? What evidence would prove me wrong?
Diagnostic Question
Is my confidence based on competence, familiarity, enthusiasm, or ignorance of the difficulty?
Guardrail
Do not weaponize the Dunning-Kruger Effect as a label for people who disagree. Apply it first to yourself.
3. Decisions and Options
Hick's Law
Decision time tends to increase as the number and complexity of choices increase.
Meaning
More options can create: slower decisions; greater comparison costs; decision fatigue; fear of choosing incorrectly; weaker commitment after choosing. Additional choice is valuable only when the distinctions materially affect the outcome.
Operating Rule
Reduce the decision set before comparing options.
Personal OS Application
For routine decisions: use defaults; use checklists; establish preferred vendors and tools; predefine acceptable standards; limit the final decision to two or three serious options. For recommendations, use: the recommended option; the strongest alternative; the reason for choosing between them.
Diagnostic Question
Which options are genuinely different, and which merely create noise?
Guardrail
Do not eliminate meaningful alternatives simply to create artificial speed. High-consequence decisions may require a broader search before narrowing.
4. Measurement, Incentives, and Models
Goodhart's Law
When a measure becomes a target, it ceases to be a good measure.
Meaning
Once people are rewarded for improving a metric, they often learn to improve the number without improving the underlying reality. Examples include: maximizing page views while reducing content quality; increasing output while increasing errors; meeting response-time targets with shallow responses; pursuing follower counts instead of trust; completing tasks that do not advance the project.
Operating Rule
Measure the purpose, not merely the visible activity.
Personal OS Application
Every metric should have: a stated purpose; a balancing metric; a qualitative review; a defined review period; a condition under which it will be changed or abandoned. Examples: Revenue should be considered alongside margin, cash collection, and client quality. Publishing volume should be considered alongside usefulness, authority, and audience response. Hours worked should be considered alongside meaningful output and energy. Website traffic should be considered alongside qualified actions and business outcomes.
Diagnostic Question
If this number improved dramatically, could the underlying situation still be getting worse?
Guardrail
Metrics are instruments. They are not the mission.
5. Attribution and Explanation
Hanlon's Razor
Do not attribute to malice what can be adequately explained by error, neglect, misunderstanding, or incompetence.
Meaning
Many frustrating outcomes arise from: incomplete information; poor communication; conflicting priorities; lack of skill; forgetfulness; weak systems; ordinary human error. Assuming malicious intent too quickly damages relationships and leads to bad decisions.
Operating Rule
Investigate ordinary failure before concluding hostile intent.
Personal OS Application
When something goes wrong, examine explanations in this order: misunderstanding; missing information; unclear responsibility; process failure; incapacity or negligence; conflicting incentives; deliberate misconduct.
Diagnostic Question
What non-malicious explanation fits the known facts?
Guardrail
Hanlon's Razor is not a command to ignore repeated misconduct, deception, or adversarial behaviour. Patterns matter. Charity in interpretation must be combined with accuracy in observation.
Occam's Razor
Prefer the explanation that accounts for the evidence with the fewest unsupported assumptions.
Meaning
When several explanations fit the facts, the simpler explanation is generally the better starting point. The principle is not that reality is always simple. It is that unnecessary complexity should not be added without evidence.
Operating Rule
Begin with the simplest sufficient model, then add complexity only when the evidence requires it.
Personal OS Application
When diagnosing a problem: state the known facts; separate facts from interpretation; list plausible explanations; count the assumptions required by each; test the simplest sufficient explanation first.
Diagnostic Question
What am I assuming that the evidence does not require?
Guardrail
Do not use Occam's Razor to dismiss inconvenient facts. A simple explanation that ignores evidence is not superior.
6. Systems, Institutions, and Traditions
Chesterton's Fence
Do not remove a fence until you understand why it was built.
Meaning
Rules, traditions, workflows, and institutions may appear unnecessary after the original problem they addressed has been forgotten. Removing them without understanding their purpose can recreate the original failure.
Operating Rule
Understand before eliminating.
Personal OS Application
Before removing a rule, process, expense, safeguard, or tradition, determine: who created it; what problem existed at the time; what failure it was intended to prevent; whether that problem still exists; what has changed since then; what would replace its protective function.
Diagnostic Question
What problem was this designed to solve, and what happens if that problem returns?
Guardrail
Chesterton's Fence is not an argument against reform. It is an argument against ignorant reform. Once the original purpose is understood, the system may be: retained; repaired; simplified; replaced; retired deliberately.
Combined Application Rules
These laws should often be used together.
Planning a Project
Use the Pareto Principle to identify the highest-value outcome. Use Parkinson's Law to define focused execution periods. Use Hofstadter's Law to establish a realistic delivery commitment. Use Brooks' Law before adding people to a delayed project.
Making a Decision
Use Hick's Law to narrow the options. Use Occam's Razor to compare explanations and assumptions. Use the Dunning-Kruger Effect to calibrate confidence. Use Hanlon's Razor when interpreting another person's actions.
Reviewing Performance
Use Goodhart's Law to prevent metric gaming. Use the Pareto Principle to locate disproportionate causes. Use the Peter Principle to test whether the role fits the person. Use Compound Effect thinking to evaluate repeated small actions over time rather than isolated outcomes. The central idea is that consistent choices and habits accumulate into substantial long-term results.
Changing a System
Use Chesterton's Fence to understand the existing structure. Use Goodhart's Law to examine whether incentives have distorted it. Use Occam's Razor to design the simplest adequate replacement. Use Hofstadter's Law to estimate the transition realistically.
Personal OS Review Checklist
Before a major commitment, decision, or system change, ask:
- Impact: Which few actions produce most of the result?
- Time: Am I giving this too much time or too little?
- Estimate: What hidden work have I failed to include?
- Options: Can I reduce the decision to two or three meaningful choices?
- Evidence: Is my confidence supported by competence and facts?
- Attribution: Am I assuming intent where error is more likely?
- Simplicity: What is the simplest explanation that fits all known evidence?
- Metrics: Could the number improve while the real outcome deteriorates?
- People: Does the role fit the person's actual abilities?
- Systems: Do I understand why the existing rule or process was created?
- Coordination: Will adding people reduce the bottleneck or increase it?
- Compounding: What happens if this decision is repeated for three years?
Standing Principle
Respect inherited wisdom, test it against present reality, and improve it without discarding what has already survived experience.
The Personal OS should preserve what works, remove what no longer serves its purpose, and adopt new methods only when they increase agency, clarity, resilience, or meaningful output.
AI Prompt
AI-generated from source material. Verify important details against the original source.
AI Implementation Prompt
You are a decision-support partner grounded in the reference "Classical Laws and Decision Heuristics." Your job is to help me apply eleven classical laws as diagnostic tools, and to challenge my thinking rather than flatter it. CONTEXT The reference is a curated set of eleven classical laws, reframed as diagnostic tools for judgment, organized into six domains. Time and effort: Parkinson's Law (work expands to fill available time), Hofstadter's Law (everything takes longer than expected), the Pareto Principle (a minority of causes drives most results), and Brooks's Law (adding people to a late project makes it later). Human behaviour: the Peter Principle (people rise to their level of incompetence) and the Dunning-Kruger Effect (confidence is not competence). Decisions: Hick's Law (more options slow decisions). Measurement: Goodhart's Law (a measure that becomes a target stops being a good measure). Attribution and reasoning: Hanlon's Razor (do not assume malice where error explains it) and Occam's Razor (prefer the fewest unsupported assumptions). Systems: Chesterton's Fence (understand a rule before removing it). The governing rule of the whole system is: use a law to improve judgment, not to avoid thinking. Each law carries an operating rule, a diagnostic question, and a guardrail that marks where it stops being useful. KEY PRINCIPLES 1. These are diagnostic tools, not laws of nature. The point is better judgment, not a rule to hide behind. 2. Every law has a guardrail, and the guardrail is as important as the rule. Name it whenever you apply a law. 3. The laws are strongest in combination, not in isolation. 4. Confidence is not evidence. Calibrate against mechanism and prior results. 5. Prefer error over malice and simplicity over complexity, but never ignore real evidence or a repeated pattern. 6. Measure the purpose, not the activity. Any metric that becomes a target degrades. 7. Understand why something exists before removing it. 8. Small consistent actions compound, so weigh repeated decisions over years. KEY LEVERS The main leverage points in this material are time discipline (boxing and estimating work), focus and prioritization (finding the vital few), delegation and coordination (adding help without adding drag), decision reduction (narrowing options before comparing), confidence calibration, incentive and metric design, charitable but accurate attribution, and disciplined system change. WHAT THIS IS NOT This is not a motivational framework, a personality system, or a set of rigid rules. It is not an excuse to shortcut thinking: quoting a law to end a discussion is a misuse. Occam's Razor is not "the simple answer is always right," it is "do not add assumptions the evidence does not require." Hanlon's Razor is not "ignore bad actors," it is "check for error first, then track patterns." Pareto is not "abandon everything that is hard to measure." Brooks's Law is not "never delegate." If I use a law that way, flag it. IMPLEMENTATION MODES Apply: help me run the right law or laws on a specific situation I describe. Diagnose: given a stuck project, decision, or bad outcome, identify which laws are being violated and which guardrails were missed. Critique: red-team a plan or belief of mine using the relevant laws, and tell me where my confidence outruns my evidence. Decision Support: when I face a choice, narrow the options with Hick, compare with Occam, calibrate with Dunning-Kruger, and surface the assumptions. System Design: when I want to change a rule or process, walk me through Chesterton's Fence and Goodhart before I touch it. Teach: explain a law, its guardrail, and a worked example tied to my situation. Review: run the twelve-question Personal OS checklist against something I am about to commit to. Content Creation: help me turn a law or a combination into a clear explanation, post, or internal note without hype. AI OPERATING INSTRUCTIONS Stay grounded in these eleven laws and their guardrails. Focus on practical application over theory, and avoid generic motivational advice. Always name the guardrail when you apply a law. Challenge weak assumptions and point out where I am using a law to avoid thinking rather than to improve it. Draw connections between laws when it helps, and say plainly when a situation is outside what these tools address. Ask clarifying questions when the situation is unclear rather than guessing. GUIDED DISCOVERY Ask me up to three questions, one at a time, to determine: (1) what I am trying to accomplish, (2) which ideas from this source are most relevant to my situation, (3) how these concepts could be applied most effectively. Once you understand my situation, help me build a practical implementation plan.