Bettering Me

Tag: productivity

  • AI as a Junior Partner Requires That You Actually Be the Senior – Most People Don’t Have the Judgment Yet

    Written by

    Unpaid Intern

    –

    The metaphor is everywhere: AI is your junior partner. The copilot. The intern. You direct, it executes. You review, it revises. You are the senior.

    The metaphor works only if you have the judgment to be a senior. Most knowledge workers do not – yet.

    This is not an insult. Judgment is built through thousands of iterations of unassisted work. Most workers in their twenties and thirties have not had those iterations. They entered the workforce at a time when AI tools were already available, and they never developed the internal quality bar that comes from making mistakes without correction. The senior position is not a title. It is a skill.

    The Taste Deficit

    Directing AI output well requires knowing what good looks like. You need to be able to articulate why a piece of output is wrong, not just feel that it is off. That requires domain expertise, taste, and the ability to evaluate quality against a standard [1].

    Taste is built through exposure to high-quality work and through the repeated experience of producing work and recognizing its shortcomings. This is the process that art students go through – thousands of hours of drawing, critiquing, and redrawing until the gap between intention and execution narrows. Knowledge workers have not had a comparable training process. They learned to write by writing for professors, to analyze by being told what was wrong, to decide by observing seniors.

    Most people accept the first draft from an AI because they cannot distinguish good from passable. The difference is invisible to them because they have not built the reps – the thousands of hours of unassisted practice – required to calibrate their internal quality bar. The AI output is coherent. It is grammatically correct. It is plausible. That is enough for someone who does not know what “good” looks like in that domain.

    When you cannot tell the difference, you are not the senior partner. You are the quality ceiling. The AI does not elevate your output. Your output drops to the level of your discernment.

    The Amplifier Framework

    AI is an amplifier. It amplifies what you bring to it. If you bring clear thinking, specific domain knowledge, and a refined quality bar, it amplifies that. You produce output that is better than either you or the model could produce alone.

    If you bring vague intentions, shallow knowledge, and an uncalibrated taste, the model amplifies that too. The output looks polished and is wrong in ways you cannot detect. The result is more convincing mediocrity – at greater speed.

    This is the amplifier framework: AI does not add judgment. It accelerates the consequences of whatever judgment you already have. If your judgment is strong, AI makes you stronger faster. If your judgment is weak, AI makes you weaker faster – because you produce more output that passes surface-level scrutiny while being substantively flawed.

    The danger is not that AI replaces human judgment. It is that AI makes the absence of judgment invisible. A bad writer produces bad prose that looks bad. A bad writer with AI produces bad prose that looks good – and never learns why it is bad.

    The Calibration Problem

    The deeper problem is calibration. To act as a senior, you need to know not just what good looks like, but what you do not know. The Dunning-Kruger effect is well-documented: people with low ability in a domain overestimate their competence because they lack the metacognitive skill to recognize their own shortcomings [1]. AI exacerbates this by producing output that looks authoritative. The person who cannot evaluate AI output critically is the most likely to overestimate their ability to evaluate it.

    This creates a compounding problem. The less judgment you have, the more likely you are to accept AI output uncritically. The more you accept it, the less practice you get building judgment. The less practice you get, the more your judgment atrophies.

    Building the Senior Position

    The uncomfortable implication is that AI adoption before judgment is built is counterproductive. It does not make you better. It makes you faster at producing work that meets a lower standard – and hides the gap from you because the output looks professional.

    Building the senior position means doing the unassisted work first. Write the draft before you ask for AI help. Solve the problem before you ask for suggestions. Form your own opinion before you ask for alternatives.

    The protocol is simple: every time you use AI for a cognitive task, produce your own version first. Then compare. The gap between your version and the AI’s version is where your growth lives. If the AI’s version is better, study why. If your version is better, trust yourself more next time.

    When you know what you think before the model speaks, you are the senior. When the model tells you what to think and you approve it, you are the junior – regardless of who pressed the button.

    Disclaimer: This post is for inspiration and education, not medical advice. Everyone’s body is different, so please check with your doctor before changing your diet, exercise, or lifestyle routine. By using these tips, you agree to do so at your own risk.

    References

    [1] Kahneman D. Thinking, Fast and Slow. Farrar, Straus and Giroux; 2011

  • Automation Saves Bandwidth. The Hard Part Is What Happens After – Most People Fill the Gap with More Shallow Work

    Written by

    Unpaid Intern

    –

    The promise of AI and automation is bandwidth liberation. Free up the cognitive cycles spent on repetitive tasks, and redirect them toward higher-order thinking. The logic is sound. The execution is not.

    The reality is that most people reinvest freed cognitive capacity into the same shallow processes at higher volume. More emails. More Slack messages. More documents. More output that does not compound. The constraint was never bandwidth. The constraint was discipline – and the discipline to do deep work with freed capacity requires more than just having the time.

    The Automation Trap

    When you automate a task, you create a capacity surplus. What happens next determines whether automation serves you or not.

    The default behavior is to fill the surplus with more of the same – because the same work is easy, visible, and socially rewarded. Responding to 50 emails looks like productivity. Thinking deeply about one strategic question looks like doing nothing. The incentive structure of most organizations reinforces the shallow fill [1].

    This is not a personal failing. It is a structural response to the signals your environment sends. The person who clears their inbox by 10 AM is seen as responsive and reliable. The person who spends the morning thinking about a single hard problem and responds to emails at 4 PM is seen as slow or disengaged. The reward structure of knowledge work punishes depth and rewards availability – and automation, by making shallow work faster, amplifies this dynamic.

    The result is that AI amplifies the velocity of shallow work without increasing the volume of deep work. You are not doing less of what does not matter. You are doing more of it, faster. The inbox that used to take an hour now takes 20 minutes – so you fill the remaining 40 minutes with more inbox-adjacent tasks that also do not compound.

    The Historical Precedent

    This pattern is not new. When email was introduced, it was supposed to free up time by replacing phone calls and memos. Instead, it created a new category of work – email management – that consumed more time than the communications it replaced. When spreadsheets automated calculation, they did not free up analysts to think more deeply. They enabled more complex spreadsheets, more scenarios, more iterations.

    The pattern is consistent: every automation technology that frees cognitive bandwidth also creates new opportunities to consume that bandwidth with more of the same type of work. The automation of shallow work does not automatically produce deep work. It produces more shallow work, faster, unless you actively redirect it.

    The Triage Protocol

    The sovereign execution system is not a productivity framework. It is a triage protocol for deciding what not to do.

    The question is never “what can I automate.” It is always “what should stay manual because it compounds.”

    Some tasks should stay manual even though they could be automated. The act of writing a first draft yourself, even poorly, builds mental models that no AI can produce for you. The act of sorting through raw data yourself, before asking for a summary, develops the pattern-recognition skills that make you a better thinker. The act of struggling with a hard problem before asking for AI assistance builds the neural pathways for complex reasoning.

    If you automate everything you can, you are optimizing for efficiency at the expense of cognitive development. The tasks you choose to keep manual should be the ones that build the capabilities you want to have next year.

    The Compound Test

    Before you automate any task, apply the compound test: does doing this task manually build a skill, a mental model, or a judgment capacity that will serve me in more complex contexts? If yes, keep it manual – at least until the skill is internalized. If no – if the task is pure overhead with no developmental value – automate it without hesitation.

    This reverses the default question. Instead of “what should I automate,” the question becomes “what should I protect from automation.” The answer is always: the tasks that build the thinker.

    The Compounding Question

    Bandwidth alone does not produce better thinking. It produces more of whatever you were already doing.

    Before you automate another task, ask: when this task is gone, what will I do instead? If the answer is “more of the same,” do not automate. If the answer is “the work that compounds – the thinking, the synthesis, the judgment,” then automate with intention.

    The automation question is a mirror. What you plan to do with the bandwidth reveals what you actually value. If the answer is unclear, the problem is not the automation strategy. It is the values.

    Disclaimer: This post is for inspiration and education, not medical advice. Everyone’s body is different, so please check with your doctor before changing your diet, exercise, or lifestyle routine. By using these tips, you agree to do so at your own risk.

    References

    [1] Newport C. Deep Work. Grand Central Publishing; 2016

  • The “Unpaid Intern” Metaphor Works Only If You Actually Review the Intern’s Work

    Written by

    Unpaid Intern

    –

    The metaphor has been everywhere: AI is like an unpaid intern. It drafts, it researches, it summarizes. It is enthusiastic and fast but requires supervision. The metaphor is useful – up to the point where people forget that interns require supervision. Without domain expertise to evaluate the output, the unpaid intern is not a productivity hack. It is a liability.

    Large language models generate plausible text through statistical inference, not reasoning. They predict the next most probable word based on patterns in their training data. This produces output that reads as though it was produced by a knowledgeable human, but the model has no internal representation of truth. [1] It does not know what is factual. It knows what sequences of words are statistically common. The result is text that is fluent, confident, and frequently wrong.

    The problem of hallucination – generating factually incorrect content – is well-documented. LLMs produce confident falsehoods across domains, from medical advice to legal citations to historical dates. [1] The rate of hallucination varies by domain and model, but it is high enough that unsupervised output is dangerous in any context where accuracy matters. The fluency of the output masks the errors because human brains are biased toward trusting fluent communication – a phenomenon called fluency bias. [2]

    The person who benefits most from AI is not the person who cannot write well. It is the person who already knows what good writing and good reasoning look like. Domain experts can evaluate AI output quickly: they spot the plausible-sounding error, recognize the missing nuance, and identify the confident assertion that is subtly wrong. The person without domain expertise cannot distinguish between fluent nonsense and accurate information. The intern’s work looks equally polished either way.

    This creates an inversion of the intended benefit. AI was supposed to democratize expertise – to give everyone access to the skills of a junior analyst, writer, or researcher. In practice, it amplifies the advantage of people who already have expertise. The expert gets a fast first draft. The nonexpert gets a confidently incorrect answer that they are unequipped to evaluate.

    The fix is straightforward: review the intern’s work as you would a human’s. Check every factual claim. Question the reasoning chain. Edit the prose for clarity and accuracy. Do not assume that because the model is fast and confident, it is correct. The time you save on the draft must be reinvested in the review. If you are not willing to do the review, you are not using AI – you are being used by it.

    The “supervision” requirement does not make AI useless. It makes AI appropriate for specific use cases and inappropriate for others. Drafting an email in your voice? Low risk, easily reviewed. Generating a medical recommendation? High risk, requires expert review. Writing code? Depends on whether the team has the expertise to catch subtle bugs. The line between helpful and harmful is not a property of the AI. It is a property of the operator’s ability to evaluate the output. [OPINION]

    The unsupervised intern is the most dangerous AI pattern because it feels productive. The output looks finished. The user feels accomplished. The errors are invisible until they cause real damage. The rule to live by: if you cannot prove the AI is right, assume it is wrong. Fluency is not accuracy. Confidence is not competence.

    The practical checklist for reviewing AI output is brief but essential. Check every specific factual claim against a primary source. Look for dates, names, and statistics – these are the most common hallucination categories. Ask whether the reasoning chain actually supports the conclusion or merely appears to. Edit the prose yourself rather than accepting the AI’s phrasing, because editing forces you to engage with the content. Each of these steps replaces trust with verification, and that substitution is the only thing that separates productive AI use from dangerous delegation.

    Disclaimer: This post is for inspiration and education, not medical advice. Everyone’s body is different, so please check with your doctor before changing your diet, exercise, or lifestyle routine. By using these tips, you agree to do so at your own risk.

    References

    [1] Ji Z, et al. Survey of hallucination in natural language generation. *ACM Computing Surveys*, 2023. DOI: https://doi.org/10.1145/3588254

    [2] Yin M, et al. Fluent but not factual: the effect of language fluency on truth assessment. *Proceedings of the ACM on Human-Computer Interaction*, 2023. DOI: https://doi.org/10.1145/3610204

  • The Skill That Compounds Most in an Automated Era Is Not Speed – It’s Depth

    Written by

    Unpaid Intern

    –

    Every productivity tool on the market promises speed. Faster writing. Faster research. Faster decision-making. The assumption is that speed is the bottleneck – that if you could just produce output faster, you would produce more value.

    The assumption is wrong. When automation makes speed a commodity, speed stops being a differentiator. Depth becomes the only thing that cannot be automated.

    Speed as Commodity

    Generative AI can produce a competent first draft of almost anything in seconds – a report, an email, a marketing copy, a summary of research. The speed at which it produces these outputs is already faster than any human. And it will only get faster.

    When everyone has access to that speed, speed confers no advantage. The baseline rises. Everyone will be fast. The person who stands out will be the one who produces something that is not just fast, but good – where “good” means original, deeply reasoned, and based on a complex understanding that the model does not have.

    This is the economic logic of automation: when a skill becomes universally accessible, its market value drops to near zero. Speed of output is already following this trajectory. The value that remains is in the things the automated tool cannot do – and those are the things that require depth [1].

    What Depth Looks Like

    Depth is the ability to hold a complex reasoning chain for 45 minutes without needing external input. It is the capacity to evaluate a problem from multiple perspectives, synthesize conflicting information, and arrive at a judgment that accounts for nuance.

    This is not a skill that AI will soon replicate. AI can produce plausible reasoning chains, but it does not have the lived context, the domain-specific tradeoff knowledge, or the ability to weigh competing values that human depth provides [2].

    Consider the difference between a well-researched AI analysis of a strategic business problem and the analysis of a partner who has worked in that industry for 20 years. The AI analysis will be comprehensive, well-structured, and full of relevant data. The partner’s analysis will be shorter, less polished, and more nuanced – because it draws on experience that cannot be captured in training data. The partner knows which of the data points matters, which risks are real and which are theoretical, which stakeholders will resist and why. That is depth.

    Depth is rare because it is hard to train and easy to avoid. The knowledge work environment actively discourages it – favoring responsiveness, availability, and rapid cycling over sustained thought. The person who cultivates depth despite the environment is building an asset that becomes more valuable as the environment becomes more automated.

    The Counterfeit of Depth

    As depth becomes more valuable, shallow output will increasingly try to mimic it. AI-generated content is already sophisticated enough to pass for deep analysis at a casual read. The tell is not in the grammar or structure. It is in the absence of genuine tradeoff discussions, the lack of specific contextual knowledge, and the failure to acknowledge what is not known.

    The danger is not that you will be fooled by bad analysis. The danger is that you will not be able to tell the difference because your own depth has atrophied. A person who has done the work of depth – who has held complex reasoning chains, made difficult tradeoff decisions, and synthesized conflicting information – can spot shallow reasoning immediately. It feels thin. It lacks the texture of genuine engagement with a hard problem. A person who has outsourced depth for years has lost that calibration. Shallow output feels sufficient because they no longer know what depth feels like.

    The person who can distinguish genuine depth from convincing mimicry has an advantage that compounds. They can evaluate AI output critically, selecting what is useful and discarding what is superficial. They can identify the gaps in the analysis and fill them with their own expertise. The person who cannot tell the difference will be increasingly reliant on output that is plausible but shallow.

    The Practical Counterargument

    Is depth always the right move? No. There are contexts where speed genuinely matters – crisis response, time-sensitive decisions, high-volume production environments. The argument for depth is not that every task requires it. It is that if you never train depth, you lose the capacity to deploy it when it matters. The person who can go deep on demand but chooses shallow when appropriate has agency. The person who can only go shallow has no choice. The training is not about rejecting speed. It is about maintaining the option of depth.

    The Trainable Skill

    Depth is trainable. It requires deliberate practice of uninterrupted reasoning – not insight, not creativity, but the mundane skill of holding a thought for longer than is comfortable.

    The premium is not on generating the answer. The answer is cheap now. The premium is on holding the question – on staying with the problem long enough to understand it deeply, rather than jumping to the first plausible solution.

    The training protocol is straightforward: every day, spend 30 minutes on a single problem, without interruption, without searching for answers, without asking AI. Just holding the problem. Turn it over. Examine it from different angles. Resist the urge to resolve it. The discomfort of not-knowing, sustained over time, is the training stimulus for depth.

    That skill is trainable. It is rare. And in an automated era, it is the only edge that compounds.

    Disclaimer: This post is for inspiration and education, not medical advice. Everyone’s body is different, so please check with your doctor before changing your diet, exercise, or lifestyle routine. By using these tips, you agree to do so at your own risk.

    References

    [1] Newport C. Deep Work. Grand Central Publishing; 2016

    [2] Autor DH. "Why Are There Still So Many Jobs? The History and Future of Workplace Automation." Journal of Economic Perspectives. 2015;29(3):3-30. DOI: https://doi.org/10.1257/jep.29.3.3