# Adam G. — full public text > The personal index of Adam G.: essays on AI, work and culture, long-form guides, short thoughts and personal updates. Written in Montreal. Source: https://adam.grgs.space/ · Author: Adam G. --- # How AI Quietly Limits Organizational Ambition URL: https://adam.grgs.space/articles/ai-reduces-organizational-ambition/ · Published: 2026-08-28 > Moderate AI adoption causes organizations to quietly narrow their strategic ambition, favoring tractable tasks over novel questions nobody knows how to ask. Picture a researcher with two questions on her whiteboard, and a small decision she makes without noticing. The first is the one she has been circling for three years — awkward, badly defined, the kind of question where you cannot say in advance what evidence would even count. The second is adjacent, narrower, and clearly answerable with the data her team already holds. She chooses the second. Not because it matters more. Because when she describes both to the model, one of them came back with a plan, and the other came back with a paragraph of encouragement. She would describe this as efficiency. I think it is something else. Joshua Gans has a working paper (NBER 33566) modelling exactly this. When decision-makers gain AI that interpolates well inside known territory, scientists respond strategically. When the tool is weak, they ignore it. When it is very strong, they push outward into genuinely novel ground, because that is where the tool adds most. But in the middle range — where most organisations sit today — scientists “work to the AI.” They constrain the novelty of what they pursue to match the range of what the machine can reliably handle. ## Work to the AI Moderate AI, the model suggests, can reduce research ambition. I think that finding travels far beyond science. Every organisation is now full of people making that whiteboard choice several times a week. Which analysis to attempt. Which customer problem to open. Which strategic question to put on the agenda. And a new, quiet criterion has entered the decision: how well does this go when I describe it to the machine? Nobody instructs anyone to apply that criterion. It arrives as relief. The tractable question produces a draft by Thursday. The important question produces a week of uncertainty and nothing to show at the review. One of those is much easier to be a person inside an organisation with. This is not a story about AI being limited. It is a story about ambition being quietly re-scoped by whatever happens to be legible to our tools — and the re-scoping leaving no trace. A narrowed question does not look narrowed. It looks like focus. It arrives on time, well-structured, defensible. The abandoned question never appears in any document, so no one ever weighs the trade. ## Ambition being quietly re-scoped Research on collective creativity is arriving at a similar place from another direction: AI use tends to raise individual output while lowering the diversity of what a population of people produces. Each person is better off. The group is less varied. Nature Reviews Psychology published a piece this summer arguing that the main protection against this homogenisation is metacognitive — intellectual humility, the habit of noticing your own reasoning while it happens. Which is an odd conclusion, if you sit with it. The safeguard against a technology of enormous scale turns out to be a small private act of attention. ## The safeguard against a technology of enormous scale I do not think individuals can carry that alone. If a mechanism operates below awareness and is rewarded by the calendar, willpower is the wrong instrument. It has to be built into how the organisation asks. What that looks like, tentatively: keep a visible record of the questions that were considered and set aside, so ambition leaves a trace. Ask, in review, not only what was found but what was not attempted and why. Fund a portion of work explicitly on the criterion that nobody currently knows how to approach it. Treat “the model had nothing useful to say about this” as a signal of frontier rather than a verdict of infeasibility. Execution has become cheap. That was supposed to free us to ask larger questions. It will only do so if we notice how strongly we are being pulled toward the ones that are easy to answer. The most expensive thing an organisation can lose is not time. It is the question nobody remembers deciding not to ask. --- # Prioritization When Execution Becomes Free URL: https://adam.grgs.space/articles/prioritization-framework-ai-era/ · Published: 2026-08-27 > As AI lowers the cost of building, traditional prioritization denominators fail. Explore new scarcity metrics like post-launch attention and conviction. For about twenty years, nearly every method we used to decide what to work on had the same shape: divide the value of a thing by the effort required to build it, then sort the list. RICE does this. Weighted shortest job first does this. So does the value-versus-effort quadrant that every team has drawn on a whiteboard at least once. The denominator was always some estimate of human labour, because human labour was the scarce input worth protecting. Something quiet happens to that arithmetic when the denominator approaches zero. The ratio stops discriminating. Everything scores well. Everything looks worth doing. A roadmap becomes, in effect, a to-do list with better formatting. Most teams are reading this as good news, and in one narrow sense it is. But a prioritisation framework was never only a ranking device. It was a refusal device. Scarcity was quietly doing two jobs at once: it rationed capacity, and it forced justification. Only the first of those has been automated away. The second job deserves more respect than it usually gets — and more scepticism. An experiment published in the Journal of Management and Governance (2024, 360 participants) found that when managers were required to justify a project choice, they shifted measurably away from the higher-risk, higher-return option toward the one that was easier to defend. Justification is not a neutral instrument. It disciplines, and it also biases toward the explainable. So the answer to a collapsed denominator is not simply “make people explain themselves more.” That trade — discipline in exchange for ambition — is a bad one to make by accident. ## Making became cheap Meanwhile the cost of a wrong choice has not fallen at all. New Relic’s 2026 State of AI Coding report, surveying 200 technology leaders, found that 94% rate AI-generated code as higher quality than human-authored code at the moment of review — while 74% say at least a quarter of it requires significant rework after deployment, 86% report more senior-engineer firefighting, and 82% have had a production failure traced to it in the past six months. Read those two findings together and the picture is clear enough. Making became cheap. Owning did not. ## What goes in the denominator now? So the practical question for anyone rebuilding how their organisation chooses: what goes in the denominator now? Three candidates that are still genuinely scarce: - Attention after launch. Not what it costs to build, but who must keep this alive — review it, explain it, repair it, answer for it — for the next two years. This is the one estimate that has become more honest, not less. - Reversibility. How cheaply can we be wrong about this? When building was expensive, we bought certainty before starting. Now we can buy it after, but only for the decisions we can unwind. - Conviction. What would we have to believe for this to matter? If nobody can answer in a paragraph, the item is not ready to be scheduled. It needs thinking, not sequencing. ## A declined register And one instrument I would add to any team’s quarter: a declined register. The backlog used to be an organisation’s written record of its own judgement. Everything below the line was a decision — a considered refusal, kept in a place where it could be revisited and argued with. When everything can be built, nothing sits below the line, and that record silently disappears. So write it down separately: one line per refused item, with the reason. Read it back a year later. It is the cheapest available test of whether you were disciplined or merely busy. None of this is a productivity problem. Choosing what is worth doing was always the part of the work that could not be delegated — we simply never had to be good at it, because capacity made most of our refusals for us. That crutch is gone. Cheap execution does not make choosing easier. It removes the last excuse for choosing badly. --- # How AI Writing Tools Hide Workplace Dissent URL: https://adam.grgs.space/articles/ai-polishing-hides-organizational-dissent/ · Published: 2026-08-26 > When AI tools polish workplace writing, variance falls and real dissent gets misrouted into private chat windows. Discover what companies miss. An organisation cannot act on a disagreement it never hears. This is the part of the AI transition I think about most, and it is rarely discussed, because it produces no visible failure. Consider what happens to a sentence on its way through a modern company. Someone writes a note that is uneven, slightly too blunt, a little uncertain in the middle. Then it is polished — not by a manager or a colleague, but by a model, in four seconds, before anyone else sees it. What arrives is calmer, better structured, and easier to agree with. Multiply that by every memo, review and proposal in an institution, and something happens that nobody chose. A large study published this month in Nature Human Behaviour found that when large language models polish and rewrite text, the core content survives — but writing-complexity variance falls by roughly 21 to 50 percent across datasets and models. The organisation still has the information. It has lost the range. A separate line of work is more uncomfortable. Researchers examining LLM-edited argumentative essays found the rewritten versions frequently failed to convey the writer’s actual opinion. The edit did not soften the position; it relocated it. The writer rarely noticed, because the text sounded like something they might have said. ## The obvious reading of this is wrong It is not an argument that AI writing tools are bad, or that people should write everything themselves out of some romantic attachment to friction. Most organisational writing deserves to be compressed. ## What the friction was carrying For most of the history of management, tone was the cheapest diagnostic instrument an organisation had. Nobody designed it that way. But when someone wrote a memo that was strangely tense, or hedged three times in a paragraph, or used a sharper word than the situation required, that texture told a leader what the content did not: this person is not convinced, or is frightened, or has seen something they cannot yet argue. Learning to read that is a large part of what experienced judgement actually is. Polish removes exactly that layer, and removes it selectively: the unevenness goes, the conclusion stays. The organisation keeps receiving well-formed agreement and loses the ability to tell a person who agrees from a person who has stopped arguing. A third finding completes the picture. Across three experiments published this year in Scientific Reports, employees were consistently more willing to voice concerns to an algorithmic leader than to a human one on cognitive tasks, mediated by fairness perception and psychological safety. The dissent has not disappeared. It is simply being expressed somewhere the organisation cannot learn from it. So the problem is not silence. It is misrouting. The candour goes into a private window; the smoothed version goes into the institution. A company can look more aligned every quarter while knowing less every quarter about what its people actually think. ## If that is right, a few things follow for Decide which artefacts are allowed to be rough. Not all of them — a few. Pre-read notes, dissent memos, early proposals, post-mortems. Say plainly that these are not to be polished, and that unevenness in them is not a lapse in professionalism. Stop reading fluency as competence. It was never a reliable signal; it is now nearly meaningless, and treating it as evidence penalises the people still thinking in public. And ask, once a quarter, a question most leaders never ask: where in this organisation is disagreement currently going? If the honest answer is “into a chat window,” that is not a technology problem. It is a report on the safety of the human channels. We spent two decades teaching people to communicate more clearly. We may be about to discover that clarity, mass-produced, is a way of hiding. --- # The Hidden Problem With AI Time Savings URL: https://adam.grgs.space/articles/ai-time-allocation-problem/ · Published: 2026-08-25 > AI saves workers hours every week, but without purposeful allocation, that time evaporates into administrative sediment. Here is how firms can fix it. A mid-sized accounting firm I have been thinking about ran the numbers on its AI rollout last spring and found something it could not explain. The tools worked. Drafting time on client memos fell by roughly a third. Reconciliation work that used to consume a junior’s morning was finished before the second coffee. By any measure the firm had recovered thousands of hours across the year. Revenue was flat. Client work looked the same. Nobody could say where the hours had gone. This is not a failure of the technology, and it is not a failure of the people. It is a failure of allocation. And it is now, I think, the most common and least discussed problem in AI adoption. ## A failure of allocation BCG’s 2026 global survey of workers puts the shape of it plainly. Among frontline employees who use AI regularly, 42% report saving eight hours a week — a full working day. Yet 66% say they receive limited or no guidance on what to do with the time they save, and more than half say they are not redirecting it into more strategic work. The firms that redesigned the work around the tool were 24 percentage points more likely to see measurable business improvement. The firms that simply bought the tool moved the needle by about five points. So the hours are real. What is missing is a decision about them. ## The same six hours BetterUp Labs found the same gap among managers, who report saving around six hours a week. Roughly 42% of that recovered time went back into polishing work that already existed, and 33% went into administration. Both felt productive. Neither changed team outcomes. The managers who instead reinvested the time in developing their people, in their own growth, and in thinking further ahead saw their teams’ performance with AI rise by 65%. The same six hours. Radically different returns, depending entirely on a choice nobody was asked to make consciously. Here is what I find striking. Organisations run rigorous processes to allocate every other form of freed capital. If a department returned $400,000 to the centre, there would be a paper, a committee, a decision. When AI returns the equivalent in hours, there is no paper, no committee and no decision. The hours are simply absorbed — into more of the same work, into administrative sediment, into a slightly gentler day. I want to be careful here, because there is an obvious and ugly reading of this: that recovered time belongs to the employer and should be immediately re-extracted. That reading is both wrong and self-defeating. Some of that recovered time should quietly become slack, and slack is not waste — it is the condition under which people notice things. An organisation with no unstructured time has no capacity for original thought, only for throughput. ## Spent on purpose The point is not to reclaim the dividend. The point is that it should be spent on purpose rather than evaporate by default. The accounting firm did something small and effective. It stopped treating recovered hours as a personal windfall and started treating them as a line item with an owner. Each team was asked, quarterly, to say what its recovered capacity had been spent on, choosing from four categories: deeper client thinking, developing someone, learning something the firm does not yet know, or absorbing existing demand. Absorbing demand was permitted. It simply had to be named. Naming it changed the behaviour. In the first quarter, almost everything landed in the fourth category. By the third, roughly a third had moved into the first three — not because anyone was instructed to, but because the question had made the choice visible. That is the whole intervention. Not a target, not a mandate. A question asked often enough that a default became a decision. Most organisations will spend the next few years measuring how much time AI saved them. The more useful measurement, and the harder one, is what the organisation became with the time. --- # Treating Shadow AI as R&D Data URL: https://adam.grgs.space/articles/shadow-ai-employee-workarounds-enterprise/ · Published: 2026-08-24 > Shadow AI isn't just a security breach; it's a decentralized R&D study revealing where your enterprise software fails and what tools actually work. Most organisations are treating shadow AI as a security problem. I think it is the most honest research and development data they have ever been given, and they are about to delete it. The pattern is now measurable. Prodoscore’s August 2026 analysis of activity across 72 companies found employees actively using nearly 50 distinct AI tools. Three of the five most-used platforms were consumer products rather than the ones IT had provisioned. ChatGPT reached roughly three times as many employees as the sanctioned enterprise assistant, and accounted for close to five times the hours. ## The standard reading is non-compliance Policy failed, procurement was too slow, people leaked data into systems nobody approved. All of that is true, and the risk is real, and none of it is the interesting part. Consider what those numbers actually are. Thousands of people, unpaid and unasked, ran an evaluation of the tools available for their own work. They compared. They abandoned things that did not help. They adopted things that did, at personal cost, without training budget or a change-management deck. That is a distributed procurement study conducted by the only people who know what the work really requires. Organisations spend serious money trying to obtain exactly this information — vendor bake-offs, pilots, steering committees — then produce a decision optimised for contract terms, and are surprised when adoption stalls. Meanwhile they already hold a revealed answer about which tools fit which tasks, and their instinct is to shut it off. ## Two things make this expensive rather than merely ironic The first is that the workaround usually contains a diagnosis. Someone using an unapproved tool is telling you, precisely, where the approved system fails. Not as an opinion in an engagement survey, but as behaviour, with effort behind it. Workday’s January 2026 research found that nearly 40 percent of AI time savings are consumed by rework — correcting, rewriting, verifying output — and that only 14 percent of employees consistently get clearly positive net results. People do not go around a system that works. The second is what the response teaches. When the honest reply to “how are you doing this?” is career-limiting, the practice does not stop. It goes quiet. And once it is quiet, the organisation loses the ability to see either the risk or the invention. You end up governing a fiction: a policy that describes work nobody is doing, sitting on top of work nobody will describe. I do not think the answer is permissiveness. Data going into unmanaged systems is a real liability, and the answer to a real liability is not to admire it. ## An amnesty with a ledger The answer is to separate the two questions the organisation keeps collapsing into one. Where the data went is a control problem, and it should be handled strictly. Why the person went there is an intelligence problem, and it should be handled greedily. In practice that means an amnesty with a ledger. Ask what people are actually using and what for; guarantee that the answer is never used against them; publish the results internally so the discoveries stop being private property. Then treat the top items as a backlog, not a violation list. Most organisations will find they have a working map of their own friction, assembled for free, that no consultant could have produced. There is a broader principle underneath. When execution becomes abundant, the scarce thing an organisation holds is what its people have noticed. Noticing shows up first as deviation — someone doing it differently because the official way is worse. An organisation that punishes all deviation is not safer. It is simply blind in the one direction where its future is arriving. The question I would ask a leadership team this month is not “how do we stop this?” It is “what did our people learn that we have no way of hearing?” --- # AI-Native Firms and the Loss of Middle Management URL: https://adam.grgs.space/articles/ai-native-firms-middle-management-judgement/ · Published: 2026-08-23 > AI-native companies are flattening, losing middle managers and juniors. But hierarchy wasn't just overhead—it was how organisations produced human judgement. A generation of companies is now being built without the middle of the organisation, and almost no one is asking what the middle was doing. A Harvard Business School working paper this year (26-090, “AI-Native Firms”) classified Y Combinator batches from 2020 to 2024 and US venture-backed startups, then linked them to workforce data on team size, function and seniority. Compared with non-AI startups in the same industry and cohort, AI-native firms are about 25% smaller. Their hierarchies are roughly half a seniority level flatter. They have about 15% fewer managers — and about 15% fewer entry-level workers. Valuations are comparable. The first three findings are being celebrated. The fourth is being ignored. There is a matching signal in the labour data. A US Census Bureau working paper (CES-26-27, April 2026), using matched employer-employee administrative records, found an immediate and persistent fall in hiring of 22-to-24-year-olds in the industry-state cells most exposed to AI: employment of early-career workers in the most exposed quintile fell about 12% over the ten quarters following ChatGPT’s release, while less exposed industries stayed flat. Two independent datasets, one shape. The organisation is losing its bottom layer and its middle layer at the same time. I want to be careful here, because the obvious reading is the wrong one. This is not mainly a story about young people losing jobs. It is a story about a function no one wrote down. ## The hierarchy was never only a coordination device It was also a manufacturing process. Junior roles were how organisations produced judgement. Not through training programmes — through exposure. You made small decisions badly under supervision, and someone senior explained why they were bad. Middle management was where that explanation happened. The layer everyone described as bureaucratic overhead was, quietly, the place where people learned which problems were worth solving, how much uncertainty is normal, when to escalate, and what a good decision actually feels like from the inside. Nobody costed this. It was a by-product of a structure built for other reasons, which is why it can be removed without anyone noticing they removed it. So the honest question for an AI-native company is not “how flat can we go?” It is: where does judgement now come from? ## Three answers seem to be forming, and only one The first is to buy it. Hire only senior people. This works while a stock of experienced judgement exists in the market — a stock produced by the older, layered organisations these firms are outcompeting. It is extraction, not production. The second is to assume the tools supply it. They do not. Models supply fluency, options and drafts. Judgement is the capacity to reject a plausible answer for a reason you can defend. That is developed by consequence, not by access. The third is to build the developmental function deliberately, now that it is no longer free. That means naming it: which decisions must a person make unaided in their first year, who reviews the reasoning rather than the output, and what is the organisation willing to let someone get wrong at survivable cost. In a firm with three seniority levels instead of five, this has to be designed. It will not fall out of the org chart, because there is no longer enough org chart for it to fall out of. I find this the most interesting design problem in front of us. Flatness is not the mistake. Flatness is mostly good — fewer people relaying information that no longer needs relaying. The mistake would be treating the layers we deleted as pure cost, when part of what they cost was the production of the next generation of people capable of contributing anything at all. Every organisation removing its middle is making a bet about where judgement comes from. Most have not noticed they are making it. --- # Why We Stopped Saying I Don't Know URL: https://adam.grgs.space/articles/ai-uncertainty-meetings-psychological-safety/ · Published: 2026-08-22 > Explore how AI tools reduce our willingness to admit uncertainty, shifting psychological safety from an economic concern into an essential epistemic. There is a sentence that has quietly stopped appearing in meetings. “I don’t know.” Not the performative version, said before an answer arrives anyway. The real one. The pause where someone admits the question is harder than the room assumed, and the group has to slow down. I have been trying to understand why it disappeared, and I think the answer is more interesting than corporate confidence culture. In a set of five experiments published this year (N = 3,132, four of them preregistered), researchers gave people difficult questions and always allowed them to decline to answer. The questions were engineered so that the available AI advice was wrong — which separates the use of AI from the accuracy of AI. ## Merely having access to an assistant Merely having access to an assistant nearly eliminated participants’ willingness to suspend judgment. They answered far more questions and were correct about a third as often. Their confidence roughly doubled. Read that again, because the striking finding is not the error rate. It is the confidence. The tool did not only change what people believed. It changed the threshold at which they felt entitled to believe anything at all. A second study points at the mechanism from another angle. In a competitive question-answering setting, expert humans working with AI agents made better decisions overall than either alone — but their mistakes were systematic. Under-reliance was highest, at roughly 61 percent of opportunities, precisely when the AI’s suggestion agreed with the human’s own initial wrong answer. Agreement was treated as evidence. Confirmation felt like confirmation. So the machine that was supposed to expand our epistemic range is, in practice, often narrowing it — not by lying, but by being fluent, immediate, and agreeable. I want to be careful here. This is not an argument that AI makes people stupid. In both studies, the collaboration outperformed the individual. And in the first, when accuracy was rewarded and error penalised, people sought advice less, followed it less, and admitted uncertainty more often. ## Incentives moved behaviour Incentives moved behaviour. That matters enormously, because incentives are the one variable organisations actually control. Which brings me to the part that keeps me up. Most organisations have spent decades penalising uncertainty. Not officially — no policy says so — but in the small economics of meetings: who gets interrupted, whose forecast is remembered, whose “let me think about that” reads as unpreparedness. We built environments in which not knowing was expensive. Then we handed everyone a device that makes not knowing entirely avoidable. ## Fluency has become abundant The result is an organisation where every question has an answer, arriving faster than the deliberation that would have tested it. Fluency has become abundant. What has become scarce is the willingness to stand in front of colleagues and say the sentence that stops the machine. I have argued before that AI relieves execution and relocates the human constraint. This is the same claim at the level of the individual mind. When the cost of producing an answer falls to nearly zero, the only remaining source of quality is the judgement about whether an answer should be produced at all. That judgement is not a skill. It is a permission. Which means the leadership task here is not training. It is licensing. I wonder what would change if “I don’t know, and here is what would tell us” were treated as a contribution — logged, valued, referenced later when it proved right. Not as humility theatre, but as the organisation’s most honest early warning system. The person who suspends judgement is doing something no assistant currently does: they are protecting the group from a confident answer that nobody has yet earned. Psychological safety was always an economic argument. It is becoming an epistemic one. --- # The Hidden Workforce Skills Gap URL: https://adam.grgs.space/articles/internal-talent-visibility-gap/ · Published: 2026-08-21 > Organisations miss existing employee skills because they only look at assigned tasks. Discover why the workplace visibility gap costs millions. A company I heard about recently spent nine months and a recruitment fee hiring a data scientist. The person they needed had been sitting in their operations team for four years. Nobody was at fault. She had joined as a logistics coordinator. Somewhere along the way she taught herself statistics, then Python, then built a demand model in her own time because the forecasting spreadsheet kept embarrassing everyone. Her manager knew she was good with numbers. That was the entire extent of what the organisation knew about her. I keep returning to this story because it is not a story about talent. It is a story about vision. The organisation could see her output. It could not see her. ## It is a story about vision There is now enough evidence to say this is structural rather than anecdotal. In a March 2026 survey of 1,500 US managers and employees, 75% of managers said their team’s skills were fully utilised. Forty-nine percent of employees said their own skills were underused. Half said their company hires externally for skills that already exist internally. Two groups, one workplace, incompatible readings of the same reality. A separate 2026 survey of HR leaders found the mechanism. Among those who described their workforce skills data as complete and accurate, three-quarters also estimated that fewer than 75% of their people’s skills were actually captured in any system. Roughly one in five update that data continuously. Asked what missed internal mobility costs them each year, 37% said two million dollars or more. I want to be careful about the conclusion here, because the obvious one is wrong. The obvious conclusion is that organisations need better skills databases. Add a field. Run an inference model over performance data. Make the invisible legible. That will help at the margin. But it misreads the problem. An organisation does not fail to see a person’s capability because it lacks a form. It fails to see it because it only ever looks at one surface: the work it assigned. Everything an employee is, beyond the task they were given, falls outside the instrument. We built organisations to allocate execution, and allocation only requires knowing whether the assigned thing got done. For two hundred years that was enough, because a person’s assigned work and a person’s usable capability were roughly the same size. They are no longer the same size. When execution becomes cheap, the assigned work shrinks and the residual — everything a person could think about, notice, question, connect — becomes the larger part of what they offer. Which means the organisation’s field of vision is now pointed at the smallest and least valuable portion of its own workforce. ## The visibility gap is not a reporting failure that This is what I find quietly serious about it. The visibility gap is not a reporting failure that got worse. It is a reporting failure that used to be affordable. The logistics coordinator is not an unusual case. She is the ordinary case, observed. In most organisations she stays unobserved, does competent work, and eventually leaves for a company that asked her a different question in an interview. The nine months and the recruitment fee are not the real cost. The real cost is four years of a demand model that existed and was never used, because the person holding it had been categorised on her first day and never re-categorised since. ## A record of the intelligence you already employ I wonder whether the most valuable thing a leader can do this year has nothing to do with technology at all. It might be to sit with each person on their team and ask what they are capable of that nobody has ever asked them to do. You will not get a database out of it. You will get something more useful: a record of the intelligence you already employ and have never once deployed. --- # Why Generative AI Deepens Innovation Bottlenecks URL: https://adam.grgs.space/articles/generative-ai-innovation-bottlenecks/ · Published: 2026-08-20 > Generative AI multiplies idea generation while leaving screening bottlenecks untouched. Learn why organisational innovation fails without human judgment. Most organisations are buying speed at the stage that was never slow. I have been sitting with a framework from Harvard Business School this summer — a working paper by researchers proposing what they call a human bottleneck perspective on innovation (HBS WP 26-094, 2026). Their premise is quietly radical. The constraints that hold back the innovation process are rarely technical. They are cognitive and social. They live in how people generate ideas, how they judge novelty, and how ideas travel through social systems. And generative AI does not act uniformly on those constraints. At each stage it relieves some and deepens others. That last part is the sentence I keep returning to. We talk about AI as though it were a tide that lifts everything. It is closer to a lever. Where you place it determines whether something moves or breaks. ## Consider the stages Consider the stages. Idea generation was genuinely constrained — a small group of people, a finite number of hours, the limits of one’s own reading. AI relieves that constraint almost completely. Organisations can now produce more plausible ideas in an afternoon than they previously produced in a quarter. But screening was also constrained, and AI does not relieve it in the same way. Judging novelty requires knowing what has been tried, what failed, what the organisation can actually absorb. That judgement rests on tacit knowledge held by a small number of people. So when ideation output multiplies and screening capacity stays fixed, the bottleneck does not disappear. It relocates — and it lands on the people who were already the constraint. I suspect this is why so many AI programmes feel oddly disappointing from the inside. Output rises. Decision speed does not. Leaders read this as an adoption problem and buy more tools for the stage that was already fast. ## A second literature sharpens the point A second literature sharpens the point. Work published this year in Frontiers in Psychology distinguishes two ways people hand thinking to a machine. In dependent offloading, the person delegates the judgement itself and accepts the result. In autonomous offloading, the person delegates the production and keeps the judgement — using the output as material to interrogate. The behaviour looks identical from the outside. The same tool, the same prompt, the same document arriving on time. What differs is where the human mind stayed in the loop. Organisations measure the artefact. So they cannot tell these two apart. And over time, if only the artefact is measured, the cheaper of the two habits wins. ## Which bottleneck are we actually relieving? What follows is not a technology strategy. It is a design question, and it can be asked in an hour: Which bottleneck are we actually relieving? Name the stage. If it is generation, expect volume, not better decisions. Which bottleneck did we just deepen? If generation multiplied, who now has to judge all of it — and did we give them anything? Where is judgement still held by too few people? That is where contribution is scarce, and where the organisation is most fragile. Are we rewarding autonomous or dependent offloading? Ask people not what they produced, but what they rejected, and why. Rejection reasoning is the most legible signal of thinking we have, and almost nobody collects it. ## What our particular system was actually short of There is something clarifying in the bottleneck framing. It refuses the fantasy that a tool improves an organisation evenly. It puts the question back where it belongs: not what the technology can do, but what our particular system was actually short of. Most organisations, I think, were never short of ideas. They were short of the courage and the capacity to judge them. No model relieves that. It only makes the shortage more visible — and, perhaps, more expensive to keep ignoring. --- # Why AI Breaks Traditional Performance Measurement URL: https://adam.grgs.space/articles/ai-era-performance-measurement/ · Published: 2026-08-19 > When AI makes deliverables cheap to produce, evaluating artefacts fails. Organisations must measure judgment and decision-making behind the work. A university department I have been thinking about spent last year arguing about the wrong thing. The argument was about cheating. Students were submitting coursework written with AI, and the faculty split into the two camps every institution ends up with: ban it and police it, or permit it and hope. Both assumed the question was integrity. It was not. It was measurement. For a century, the essay worked as an assessment instrument because it was expensive. Producing eight coherent pages was slow, and the slowness was the point. The department never wanted essays. It wanted evidence that a young person could hold an argument together under pressure. The artefact was cheap to grade and hard to fake, so it stood in for the thing that mattered. When production costs collapse, the proxy stops proxying. The artefact still arrives. It just no longer carries information about the person who submitted it. This is not an education problem. It sits in every performance review in every company right now — the deliverable arrives, and the organisation can no longer tell what the human did. ## Two pieces of evidence make me think the exit The first is a study from a Wharton-led team who ran a five-month randomised trial across ten Taipei high schools teaching Python. Every student had the same AI tutor and the same materials. The only variable was the sequence in which practice problems were assigned — fixed in one group, adjusted in the other based on how each student was actually engaging. That single design change raised final exam scores by 0.15 standard deviations, an effect the authors compare to six to nine additional months of learning. No extra instructional hours. No extra teacher workload. The tool was identical. The design around it was not. The design was the entire gain. The second is less comfortable. The OECD’s most recent Survey of Adult Skills, covering roughly 160,000 adults across 31 countries, found literacy and numeracy declining or stagnating in most of them over a decade — sharpest declines among the lowest-performing tenth, improvement at the top. Skills inequality widened within countries. Roughly one in five adults can manage only simple texts or basic arithmetic. So we are placing a technology that produces fluent output into a population whose capacity to evaluate fluent output is, for many, going the other way. That does not automatically make anyone smarter. It makes design decisions enormous. ## It is a contribution instrument What the department eventually did was small and, I think, correct. It stopped grading the artefact alone and started grading the decisions behind it. Students still submit the essay. They also submit a short record of what they tried and abandoned, which sources they rejected and why, and where they disagreed with the model. Then they spend twenty minutes defending the argument to someone who pushes back. The assignment did not get harder to write. It got harder to fake, because the object of assessment moved from the output to the reasoning behind it. Grading time went up. The faculty decided that was the price of measuring anything real. Notice what this is. It is not integrity policing. It is a contribution instrument — a way of making visible the judgment a person exercised, in a world where the product of that judgment is no longer scarce. Every organisation will need one. Your appraisal forms were built in the essay era. They measure artefacts because artefacts used to be expensive, and they will keep measuring artefacts long after that stops meaning anything, because nobody has proposed a replacement. Universities are being forced to solve this in public, on a deadline, in front of students who notice immediately when a system is pretending. The rest of us get to solve it more slowly and less honestly. I would rather learn from them than repeat them. --- # AI Adoption Is a Management Variable URL: https://adam.grgs.space/articles/ai-adoption-management-practice/ · Published: 2026-08-18 > Explore why AI adoption is a management variable, not a technological one, and how leadership theories on human roles shape organizational success. Every organisation I speak with is trying to answer the wrong question. They ask which model to adopt. The more revealing question is why two companies with the same model end up with entirely different organisations. We have started to get evidence on that. A Harvard Business School working paper this June surveyed founders of North American tech startups about generative AI and headcount. On average, founders estimated they would need 55% more employees without it. But the median was 17%, and nearly a third said they would need no additional people at all. Same tools. Same year. Wildly different organisational consequences. The gap was not explained by the technology. Founders who had formally integrated AI into their workflows estimated headcount effects nearly four times larger than those using it informally — and were far more likely to report that it had changed how they hire and manage. Then the researchers did something clever. They randomly gave founders optimistic or pessimistic information about how well AI performs specific tasks. Beliefs moved, as you would expect. Willingness to delegate moved too. But substantial differences between managers persisted even after their beliefs about performance converged. Read that carefully. Two managers can agree on exactly what the machine can do and still make opposite decisions about what it should do. A large cross-country study from the NBER in March pointed the same direction from a different altitude. Comparing worker and firm surveys across the US and Europe, the authors found adoption gaps that demographics and firm composition explained only partly. What else predicted adoption? Personnel management practices, and whether firms actively encouraged their workers to use it. Not infrastructure. Not access. Management. ## AI is not arriving as a technology variable So the emerging picture is this: AI is not arriving as a technology variable. It is arriving as a management variable. That should be uncomfortable, because it removes the alibi. If capability were the constraint, waiting would be a strategy. If judgment is the constraint, the difference between firms in five years will not be their AI stack. It will be what their leaders believed people were for. And that belief is doing quiet work already. When a manager decides how much to delegate to a machine, they are also deciding, implicitly, what the human beside it is now responsible for. Two answers are available. The first: the human is a slower version of the machine, and every delegated task is pure subtraction. Under this belief you get a smaller organisation doing the same work. The second: the human is the part of the system that decides what is worth doing, notices when the answer is confidently wrong, holds the relationship the work sits inside, and asks the question nobody had thought to ask. Under this belief you get an organisation doing different work. ## Delegation preferences are not really predictions Neither belief is disproved by the data, which is precisely why they persist. Delegation preferences are not really predictions. They are anthropologies. They are compressed theories about human beings, held mostly unexamined, and now being executed at speed across entire firms. I find this both sobering and hopeful. Sobering, because most organisations are making a philosophical choice while believing they are making a procurement decision. Hopeful, because it means the outcome is not being handed to us. There is no automation destiny. There are managers, with theories, choosing. If that is true, the most valuable thing a leadership team can do this year is not another tool evaluation. It is to surface the theory of the human that their delegation decisions already imply — and ask whether anyone in the room actually believes it. Because that theory is being installed either way. The only question is whether it was designed or inherited. --- # The AI Contribution Penalty at Work URL: https://adam.grgs.space/articles/ai-workplace-contribution-penalty/ · Published: 2026-08-17 > Research shows AI-assisted workers face systematic competence and pay penalties because organisations mismeasure execution output instead of human judgment. An analyst I read about recently spent a year on one problem. She sat with the people who ran the process, collected the complaints nobody had written down, drafted alternatives, learned which of them would break something downstream, and eventually produced a change worth a great deal to her employer. Somewhere in that year she used an AI assistant for a few days of drafting. When the work went to senior leadership, her manager asked her to foreground the AI. In the meeting he interrupted her presentation to say the tool had done it. I keep returning to that moment, because it is not really a story about a bad manager. It is a story about an organisation that had lost the ability to see a human contribution once a machine had touched any part of it. There is now a surprising amount of evidence that this error is systematic. In four preregistered experiments with 4,439 participants, researchers found that people who use AI at work both anticipate and receive worse evaluations of their competence and motivation than people who do the same work without it. The penalty was not imagined. It showed up in real assessments of job candidates. A separate programme of eleven experiments with 3,846 participants found that evaluators pay AI-assisted workers less — across task types, employment statuses, payment formats, and even when output quality was held constant or statistically controlled. The mechanism was measured directly: people judged that AI-assisted workers deserved less credit, and that judgment accounted for roughly sixty per cent of the pay reduction. In thirteen further experiments on disclosure, actors who declared their AI use were trusted less than those who did not, across supervisors, subordinates, professors, analysts and creatives. The explanation was not accuracy but legitimacy: disclosure marked the work as socially inappropriate. ## Adopt these tools Put those together and you have an organisation quietly running two incompatible instructions. Adopt these tools. Do not be seen using them. The rational response, for anyone paying attention, is concealment. And concealment is expensive in ways that never appear on a balance sheet: nobody shares what worked, nobody reports what failed, and the organisation’s collective learning about its most important new capability happens entirely in private. ## The accounting error underneath What interests me more is the accounting error underneath. We have built evaluation systems that measure output and infer effort from it. When output arrives faster, the inference machinery concludes that less was contributed. But in the analyst’s story, almost nothing she actually contributed was executional. She contributed a year of attention. She contributed knowing which stakeholder’s objection was real and which was territorial, and the judgment to discard three alternatives that looked good on paper. The AI drafted. She decided. An evaluation system that cannot distinguish between those two things will systematically underpay exactly the capability that is becoming scarce. ## One hopeful finding in this literature There is one hopeful finding in this literature. The penalty softens considerably when the human remains visibly involved — reviewing, adapting, contextualising, taking responsibility for the result. Which suggests the problem is not that people refuse to credit AI-assisted work. It is that most of what a person does in AI-assisted work is currently invisible, and organisations have not built any way to make it visible. That is a design task, not a values problem: describing contributions in terms of judgment exercised, not hours displaced. Asking, in reviews, what the person decided rather than what they produced. A manager being able to say what a colleague added, specifically, and being embarrassed if they cannot. An organisation that cannot name what its people contribute will eventually stop paying for it. Not out of malice. Out of blindness. --- # Designing the Handoff After AI Stops URL: https://adam.grgs.space/articles/ai-human-handoff-design/ · Published: 2026-08-16 > Explore why AI handoffs fail and how organizations leave humans with the most emotionally expensive, high-effort residual work without adequate support. Most organisations have decided where AI stops. Almost none have designed what happens in the second after it stops. The handoff gets treated as routing: the system reaches its limit, a human receives the work, service continues. It is not routing. It is the point where the quality of the whole system is decided, and it is currently being designed by nobody. There is now field evidence on this. In a randomised experiment on Alibaba’s Taobao platform, workers supervised an agentic AI system handling eligible customer chats while continuing to resolve the rest themselves. Chats got shorter. Ratings for the AI-eligible chats fell substantially. What is interesting is where the human rescue worked and where it did not. When the system escalated because the problem exceeded its capability — a technical dead end — human intervention preserved service quality. When it escalated because the customer had become frustrated, intervention largely failed to recover the outcome. The reason was not skill. It was effort. In emotional escalations the workers sent fewer messages, took a smaller share of the conversation, sought less information, offered fewer solutions. They arrived at the hardest moments of their day with the least engagement. And intervening late made it worse: early entry was what sustained effort afterwards. ## Read that as an organisational design finding Read that as an organisational design finding rather than a customer service one. The system had quietly reallocated human work to consist almost entirely of the parts machines fail at — the emotionally expensive parts — without changing anything about how that work was supported, staffed, or valued. The residual became the job. Nobody designed the residual. A second study, a field experiment inside Porsche’s after-sales operation, points at the same gap from another angle. Decision-makers were given advice from a human expert, a machine learning model, or both. The combination produced better decisions — but only where people actively reconciled the conflicting inputs rather than deferring to one. And engagement in that reconciliation dropped when the decision moved from an individual to a group. Together these say something uncomfortable. The benefit of keeping humans in the loop is not automatic. It is conditional on an act of genuine engagement that most workflows do nothing to protect, and that quietly evaporates under pressure, fatigue, and group settings. ## Three things follow So the question is not whether to keep a human in the loop, but what the loop asks of them. Three things follow. Escalation should carry context, not just the case. A person entering at the worst moment with none of the history spends their first minutes reconstructing what happened, and reaches the human part of the problem already depleted. Handoffs designed for continuity of information are cheap. We rarely build them. The residual should be staffed as difficult work, not leftover work. If machines absorb the routine and leave humans the ambiguous, the emotional and the unprecedented, then the human caseload has quietly become harder per hour while headcount models still assume it became easier. That mismatch shows up as disengagement long before anyone calls it burnout. And disagreement with the system needs a legitimate route. If reconciling machine advice with your own judgment is the step that creates the value, then overriding must be an ordinary, low-cost, recorded act — not a quiet act of insubordination someone must justify. ## The pattern underneath is worth watching everywhere AI enters The pattern underneath is worth watching everywhere AI enters an organisation. We are removing the easy parts of jobs and calling it relief. What remains is the concentrated human residue: judgment, ambiguity, emotion, repair. That is the contribution we say we want. It is also, hour for hour, the most demanding work a person can do — and we are handing it over with no more support than the routine work it replaced. --- # AI Automation and the Death of Workplace Apprenticeship URL: https://adam.grgs.space/articles/ai-automation-apprenticeship-crisis/ · Published: 2026-08-15 > Explore how AI automation breaks traditional workplace apprenticeship systems, threatening the future development of human expertise, judgment, and junior. I have been thinking about a question that has no obvious owner inside any organisation I work with: who is responsible for producing the next generation of experts? Not hiring them. Producing them. For most of industrial history the answer was embedded in the work itself. Juniors were given the small, unglamorous, correctable tasks — the routine fix, the first draft of the memo, the reconciliation nobody enjoyed. Those tasks were economically marginal. That was never their real function. Their function was to let someone struggle, get it slightly wrong, and be corrected by a person who had struggled before them. Expertise was a by-product of inefficiency. We are now removing that inefficiency at speed, and I do not think we have noticed what we are removing with it. ## The Disappearing Entry-Level Gap Stanford’s Digital Economy Lab, working with ADP payroll data covering millions of American workers through mid-2026, found that employment of 22-to-25-year-olds in AI-exposed occupations now sits roughly 19% below where it would be had it tracked their less-exposed peers. Experienced workers in the same occupations show no comparable gap. The divergence is concentrated where AI automates rather than augments. That is usually read as a displacement story. I think it is a transmission story, and the more interesting evidence is qualitative. A study published this year of software engineers — juniors at the threshold of the profession and the seniors who once trained them — describes a pattern the authors call absorption. Entry-level work does not disappear into a queue waiting for a junior. It is redirected into a senior-plus-AI workflow, where it is completed faster and better. Nobody makes a decision to stop training anyone. The training simply has nowhere to happen. The researchers also describe a perceptual asymmetry. Seniors evaluate juniors on output, which now looks fine. Juniors experience the loss privately, as an absence of something they cannot name because they never had it. Neither side is positioned to see the problem, so neither side raises it. An organisation can lose its apprenticeship system without a single meeting acknowledging that it happened. ## The Hidden Cost of Efficiency What makes this hard is that no individual decision in the chain is wrong. Giving the routine task to the AI is correct this quarter. It may be correct every quarter for four years. The cost arrives in year five, in a cohort of people who can supervise output they were never able to produce — able to accept or reject an answer, but not to sense when the question was wrong. Judgment, as far as we can tell, is not transferable by explanation. It is residue left behind by having been responsible for something. I do not have a framework for this yet. I have a suspicion about where it starts. Organisations measure the productivity of work. Almost none measure the developmental yield of work — whether a given task, done by a given person, left behind a capability that did not exist before. That number has never needed to exist, because apprenticeship was free and automatic, a side-effect of how work was distributed. It is now neither free nor automatic. It has become a thing that must be paid for deliberately, in slowness, in tasks assigned to the person who will be worse at them, in seniors spending hours correcting work an AI would not have got wrong. ## Replenishing the Stock of Expertise That is a real cost, and it should be named as one rather than smuggled into a development budget. A firm that declines to pay it will look more efficient than its competitors for several years. Then it will discover it has been consuming a stock of expertise it stopped replenishing, and that this particular stock cannot be bought back at any price, because everyone else stopped replenishing theirs at the same time. Execution is becoming abundant. Judgment is still made the slow way — by people who were allowed to be responsible before they were ready. --- # Fixing the Organizational Idea Intake Gap URL: https://adam.grgs.space/articles/organizational-idea-intake-gap-solutions/ · Published: 2026-08-14 > Discover why employee suggestion programs fail due to intake capacity rather than motivation, and how organizations can actually capture frontline ideas. A state agency runs an employee suggestion programme. In its first eighteen months it received 132 ideas from a workforce of tens of thousands. Twelve were adopted. Those twelve produced roughly $7.2 million in verified savings in a single fiscal year. The savings figure gets quoted in the annual report. The interesting number is 132 — small not relative to the savings, but relative to the number of people who spend every working day watching a public service function badly and knowing precisely why. ## That gap is not a motivation gap There is good evidence about where ideas die. A field experiment across every ministry of the Ghanaian Civil Service found strongly hierarchical cultures in which junior staff felt unable to raise new ideas at all. Researchers trained bureaucrats to break problems into small, actionable solutions and to raise them with colleagues. Six to eighteen months later, the individually trained staff were measurably more likely to raise and discuss ideas, and administrative processes had improved. The part I find most instructive is what did not work. When the same training was delivered at division level, it largely failed. Divisions absorbed it into their existing hierarchy and produced plans that were grand, resource-hungry and Civil-Service-wide — the sort of proposal that requires someone else’s budget and therefore never happens. The individual version produced small, local, implementable changes. The collective version produced ambition with no owner. ## Hierarchy did not reject the intervention The constraint has moved. When the UK’s Department for Work and Pensions evaluated a generative AI assistant across 3,549 staff, it measured an average saving of nineteen minutes per person per day. Multiply that across a large agency and you have an enormous quantity of newly available human attention inside institutions whose formal channels can absorb perhaps a hundred ideas a year. We are increasing the supply of thinking time while leaving the intake capacity for thoughts exactly where it was. An idea has to survive a long journey: recognised as an idea by the person who has it, spoken aloud without professional risk, understood by a manager whose incentives it may complicate, translated into institutional language, then owned by someone with a budget. Most die at step one or two, silently, leaving no record. The intake number does not measure how many ideas exist. It measures how many survived the filter. If that is right, the design question for the next decade is not how to make people more creative. It is how to shorten that journey. ## Three things follow, none expensive Route ideas to the smallest unit that can act, not to the highest one that can approve — the Ghana result suggests scale is where ambition goes to die. Judge a suggestion system by the proportion of submissions that receive a reasoned answer, not by the proportion adopted; the first number is what people actually respond to. And accept partial thoughts. Most institutional intake forms demand a fully formed proposal with a cost-benefit case, which is a request for a finished product from someone who has noticed a problem. A quieter argument sits underneath all this. A suggestion programme is not an efficiency tool. It is a statement about whose observations the institution considers real. When a caseworker or a night-shift technician submits something and receives a serious reply, the organisation has said: your reading of this place counts as knowledge. That is a matter of dignity before it is a matter of savings — though, as those twelve ideas suggest, the savings follow. Every large organisation already contains the analysis it is currently paying consultants to produce. The difficulty was never generating it. It was building something capable of hearing it. --- # The Myth of AI Productivity and Idle Time URL: https://adam.grgs.space/articles/ai-rollout-idle-time-myth/ · Published: 2026-08-13 > Discover why AI time savings often vanish into unmeasured idleness, and how rigid management prevents organizations from capturing real innovation. A COO told me last month that her AI rollout had “leaked.” Her word. The tools worked, the hours came back, and nothing showed up at the other end. She asked me where the time went. I think we mislabel the answer, and the mislabelling is expensive. A Bank of Korea-funded survey of Korean workers, released in February, found that 51.8% now use generative AI at work and that it reduces their working time by about 3.8%. Then the uncomfortable number: the correlation between an individual’s time savings and their reported change in output was 0.008. Effectively zero. The authors conclude the recovered time is absorbed largely as what they call on-the-job leisure. ## A vocabulary problem Most executives read that as shirking. I read it as a vocabulary problem. Our accounting has exactly two categories for a human hour: output, or waste. Anything that is not visibly producing gets filed under the second one. Now set that against a natural experiment published in Organization Science. A supply-chain shortage forced unexpected stops in production plants. Employees who sat through that unplanned idle time went on to produce 58% more ideas than uninterrupted colleagues in the following three weeks. And the details matter more than the headline. Interruptions without idle time — the intrusions, the pings, the reassignments — reduced creative performance. Planned breaks produced no creative effect at all, because people disengaged cleanly and turned to leisure goals. Read those two findings together and you get something strange and useful. ## Unstructured, unexpected, slightly uncomfortable emptiness Unstructured, unexpected, slightly uncomfortable emptiness is generative. Scheduled emptiness is not. The mind does its recombining while it is still half-attached to the problem it was pulled away from — the researchers land on attention residue as the mechanism. Which means the innovation hour cannot be booked in a calendar. It arrives unannounced, looks exactly like idleness, and gets closed as such. R&D research makes the same point from the other side: most corporate slack time is rhetorical rather than genuine. It exists in the policy, then gets consumed by overcommitment and by people’s own sense that thinking is a luxury they will be judged for. So we are in a peculiar position. AI has just handed organizations the largest supply of unplanned idle time in modern working life, and we have given our managers no language for it other than capacity. I do not think the answer is to schedule reflection. The evidence suggests scheduling it removes the property that makes it work. Two things seem more promising. The first is to stop treating the hour as recovered capacity by default. If every freed hour is immediately refilled with throughput, the organization has quietly converted its only new source of variation into more of what it already had. The second is to lower the cost of acting on whatever surfaces during that hour. Idle time produces ideas; almost nothing in a normal company is built to receive them. There is a route for finished work and no route for an unfinished thought. That is a design gap, not a motivation gap. ## Saying yes to mess Underneath both is an older argument I keep returning to. Two management scholars, Herath and Harrington, published a paper with a title I admire: “Saying yes to mess.” Their claim is that disorganization is not a failure of design but a form of it — the condition under which firms sense and adapt. Optimization removes variation. Variation is where discovery lives. We have just deployed the most powerful optimization technology ever built into organizations that were already over-optimized. I told the COO her time had not leaked. It had gone somewhere her instruments cannot see, and some of it was probably the most valuable thing that happened in her company that week. What I could not tell her is how she would know. --- # Why AI Adoption Stalls in the Middle URL: https://adam.grgs.space/articles/ai-adoption-manager-resistance-strategy/ · Published: 2026-08-12 > Discover why AI adoption stalls in organizations and how clear reinvestment rules, headcount horizons, and broader contribution metrics overcome resistance. Ask executives what is slowing their AI programme down and you hear about tooling, data quality, procurement. The honest answer is usually simpler: nobody in the middle of the organisation has been told what happens to their people if it works. Two pieces of 2026 evidence make this hard to dismiss. In a pre-registered experiment with 2,000 managers in the US and UK, the Institute for Fiscal Studies showed managers short videos about AI. Managers who saw evidence of AI’s labour-displacing potential reported intent to adopt and advocate for AI that was 0.4 to 0.5 standard deviations lower, and pulled back their hiring intentions too. Managers who saw evidence of productivity gains did not move at all. ## The productivity case persuaded nobody The productivity case, in other words, persuaded nobody. The threat case persuaded everybody — to stop. Separately, work using the Gallup Workforce Panel (more than 30,000 US employees, 2023 to early 2026) found that employees who say their organisation has a clear AI strategy are roughly 27 percentage points more likely to use AI frequently. Frequent use without that clarity shows near-zero association with engagement and a positive association with burnout. Strategic clarity was concentrated in places with developmental feedback and trust in leadership — which suggests people infer strategy from how their managers behave, not from what the policy document says. Put those together and you get an uncomfortable diagnosis. Adoption is not primarily a technical problem or a training problem. It is a problem of what people believe the technology means for them. And the belief is formed locally, by a manager who has done the arithmetic and does not like the answer. You cannot fix that with enthusiasm. ## Commitments that are costly to break You can only fix it with commitments that are costly to break. Three seem to matter most. **1\. A stated reinvestment rule.** Before deployment, say in writing where recovered hours go. Not “efficiency” — a destination. Twenty per cent of recovered time to customer contact, quality review, or team thinking, with the rest returned to capacity. A rule can be audited. An intention cannot. **2\. Headcount decoupling, with a horizon.** Say plainly whether this deployment is linked to a staffing decision, and for how long. Vagueness is not neutral. Vagueness is read as the worst case, and the manager protects the team by slowing the project down. **3\. Contribution in the record, not just output.** If the only thing performance systems can see is throughput, then AI making throughput cheap makes people look redundant. So the record has to widen: the question that stopped a bad plan, the judgement call, the knowledge someone wrote down so a colleague would not have to rediscover it. ## What happens to their people if it works None of this requires a new platform. It requires one page, written before the tool arrives rather than after the resistance appears. What strikes me most in the IFS result is the asymmetry. The upside argument moved no one; the downside argument moved everyone. They are not confused about the productivity numbers. They are waiting to hear what the productivity is for. Perhaps the first deliverable of any AI programme should not be a pilot. Perhaps it should be a sentence a manager can say out loud to their team without flinching. --- # The Judgment Gap in Organizations URL: https://adam.grgs.space/articles/organizational-judgment-gap-ai-work/ · Published: 2026-08-11 > Organizations reward knowing over noticing, creating a judgment gap where assumptions compound at machine speed. Discover why questioning matters. We have spent a century building organizations that reward people for knowing, and almost no time building organizations that reward people for noticing they don’t. That asymmetry used to be affordable. It may not be much longer. Earlier this year a research team at Scale published a benchmark called HiL-Bench. The premise is simple: take hard software and database tasks that frontier AI models already solve well, then remove a few details — the kind missing from every real specification ever written: an ambiguous requirement, a contradiction between documents, a fact nobody wrote down. With complete information, the models solved between 75% and 89% of the tasks. Given the ability to ask a human for clarification, but left to decide for themselves when to ask, performance fell to 38% on one domain and 12% on the other. What is striking is not the failure but its manner. The systems did not stall or flag uncertainty. They filled the gap with a confident assumption and continued. Across thousands of failure traces, one model family built elaborate work on beliefs it never examined; another recognized it was stuck and pressed on anyway. ## A judgment gap, not a capability gap The researchers named the missing thing well: a judgment gap, not a capability gap. The mechanism to ask existed. The judgment about when to use it did not. I think most organizations have the same gap, and have had it far longer than the machines. Consider how we select people. We ask for evidence of what they have already produced — degrees, titles, throughput, prior scope. We rarely ask for evidence that they can tell when a brief is incoherent, or when a plan assumes something that was true two years ago. The Burning Glass Institute and OneTen studied over a thousand large U.S. employers this spring and found that firms which formally dropped degree requirements saw only a two-percentage-point increase in hires holding non-degree credentials. The policy changed; the selection instinct did not. Fifty-eight percent of the prime-age American workforce has no four-year degree, and the machinery keeps reaching for the same signal. So we assemble organizations optimized for confident execution, then act surprised when confident execution turns out to be the failure mode. ## Wrong assumptions now compound at machine speed Why does this matter more now? When execution was expensive, a confident wrong assumption travelled slowly. It passed through people, drafts, meetings, budgets — each a chance for someone to ask, quietly, “wait, what do we actually mean by this?” Execution is now cheap and fast. Wrong assumptions now compound at machine speed. The bottleneck moves upstream, to the quality of the question the work began with. Which makes noticing a form of production — perhaps the most valuable one. And noticing does not come from expertise alone; it comes from having lived in more than one system. The person who worked in a warehouse before they worked in finance sees the supply-chain assumption the rest of the room reads past. The nurse-turned-administrator hears which part of the policy will not survive a Tuesday night. The immigrant hears the sentence in the deck that only makes sense to people who grew up here. This, to me, is the real argument for diverse organizations — not that difference is admirable, but that difference is the only reliable detector of the assumptions a homogeneous group cannot see because it shares them. ## Judgment turned out to be trainable The encouraging part of the benchmark is its last finding: judgment turned out to be trainable. A far smaller model, trained to recognize unresolvable uncertainty and act on it, improved not only its asking but its results. If it is trainable in a model, it is cultivable in an institution. But you cannot cultivate what you never record. Which returns me to a question I keep circling: does your organization keep any record of the moment someone stopped the work to ask a better question? Or does it only remember the people who kept going? --- # Capturing Tacit Knowledge in Manufacturing With AI URL: https://adam.grgs.space/articles/capturing-tacit-manufacturing-knowledge-ai-dignity/ · Published: 2026-08-08 > Discover how capturing tacit manufacturing knowledge using AI can preserve expertise while respecting human dignity and attribution in the workplace. A polymer plant loses a line at 2 a.m. An operator with nineteen years on the floor listens to the extruder, adjusts something the manual never mentions, and the line is back in eleven minutes. Nobody writes it down. There is no field for it. Those eleven minutes are among the most valuable assets the company owns, and they exist nowhere except inside one person. Manufacturing has always known this and never solved it. Siemens estimates unplanned downtime costs the world’s 500 largest companies some $1.4 trillion a year — roughly 11% of revenue — with an hour of stopped automotive production near $2.3 million. Meanwhile Deloitte and the Manufacturing Institute project up to 1.9 million manufacturing roles going unfilled this decade. The expertise walking out the door was never in the documentation. Workshops with 23 practitioners from 14 German manufacturers, published this January, found three barriers: the knowledge is situated, capturing it costs time nobody has, and the systems built to hold it were designed for compliance rather than for thinking. So most organizations gave up on the knowledge and bought sensors instead. Predictive maintenance is worth doing. But it answers the narrow question — what is about to fail — and leaves the hard one untouched: what does the person standing there actually know? Something has quietly changed: the cost of capturing informal knowledge has collapsed. A language model can take a messy spoken account of a 2 a.m. fix — half-sentence, dialect, hedged, full of “usually” and “unless” — and turn it into something searchable without stripping out the judgment. A European research team is now testing exactly this in a polymer plant: operators log disturbances as small cause-and-countermeasure cases, in their own words, inside the workflow rather than after it, with curation happening centrally. Structured, not sanitized. This is less a technology story than a governance one. The moment capture becomes cheap, a question arrives that no plant manager has had to answer before: whose knowledge is it? ## The Risk of Organizational Dehumanization There is a version of this that fails. Record the operators, extract the patterns, feed a model, and the operator becomes a training input. That is not knowledge management. Research on organizational dehumanization — including a scale validated this July across 581 respondents, where instrumentality emerged as one of two clean factors — describes exactly this experience, and links it to lower engagement, higher turnover intention, and reduced discretionary effort. If contribution is what you want, instrumentality is a strange way to ask for it. And there is a version that works, which differs in one detail. The knowledge keeps its author’s name on it. ## Human Dignity as a Business Strategy The operator is not a data source. She is the reason the case exists. Her name stays attached. When someone on the night shift solves a problem using her micro-case, she hears about it. When her method turns out to be wrong under new conditions, she is the one asked to revise it. The record becomes a body of work — something a person can be proud of, argue about, and build on. Which is exactly the behaviour the plant needs and cannot mandate. This is what I mean when I call human dignity a business strategy rather than a sentiment. Attribution is not a courtesy in this design; it is the mechanism. It is what converts a one-time extraction into a nineteen-year contributor who keeps contributing, and lets the person joining next year learn from someone rather than from a database. Every organization I have looked at holds intellectual capital it cannot see, mostly among the people furthest from its documentation. The tools to see it have finally arrived. What has not arrived is agreement on what we owe the people whose knowledge we are about to be able to read. I suspect that question, not the technology, will decide who actually benefits. --- # Why Teams Need Disagreement in the Age of AI URL: https://adam.grgs.space/articles/ai-consensus-team-disagreement/ · Published: 2026-08-07 > As AI makes agreement fast and cheap, teams risk losing the productive disagreement essential for discovery. Learn why protecting dissent matters now. Consensus used to be expensive. That may have been the only thing keeping it honest. Getting a room to agree once required real work: circulating a draft, absorbing objections, revising, persuading. That cost acted as a filter. If a group finally aligned, the alignment usually meant something had been tested. Now a team can generate a coherent, defensible position in ninety seconds. Everyone arrives already aligned — not because they argued their way there, but because they consulted the same class of system and received the same reasonable answer. ## Agreement has become cheap Agreement has become cheap, and cheap agreement is hard to distinguish from correct agreement. I keep returning to a result from a paper on team production (arXiv 2512.22736, Dec 2025). Holding average optimism constant, a team’s expected output rises with the degree of disagreement among its members. When people hold different priors about which method will work, they work harder to demonstrate their own, and the team learns faster. The authors go further: a manager forming pairs from a large workforce maximizes output by matching beliefs negatively. ## Deliberately pairing people who disagree Deliberately pairing people who disagree. That is an uncomfortable finding for anyone who has ever built a team by hiring “culture fits.” The empirical work is less romantic about how disagreement behaves in a real room. In a June 2026 study of power-imbalanced groups, researchers gave dissenting minority members AI support. Model-generated counterarguments made the atmosphere more flexible and the dissenters more satisfied. But when the AI paraphrased and delivered their dissent for them, participation went up while psychological safety went down. People spoke more and felt less safe. A machine can carry your objection into the room. It cannot make the room a place where objecting is survivable. A Scientific Reports paper published this week points at what does. Across two experiments, activating a sense of secure attachment to the group made minority opinion holders more task-focused and their dissent more persuasive — and made the majority more willing to use it. The variable was not courage or training. It was whether the dissenter believed the group would still hold them afterward. Disagreement has economic value. AI can amplify its volume. Only the organization can make it usable. This is where one principle of Contribution Leadership does most of its work: optimization removes variation, and variation is where discovery lives. For two centuries we treated variation as noise — a defect in the process. That was defensible when execution was scarce and consistency was the advantage. It is much less defensible now. Consistency is what the machines are for. ## Difference is what the humans are for Difference is what the humans are for. Which suggests an odd new managerial duty. Not building alignment. Protecting the residue of disagreement that survives after the models have spoken. A few questions I would want a leadership team to be able to answer: When we agree quickly, do we know whether we reasoned or retrieved? Who in this room was wrong last quarter, and were they rewarded for having been interestingly wrong? When someone dissents, do they leave the meeting more attached to the group or less? None of this argues for manufactured conflict. Contrarianism as a personality is a cost, not a contribution. A 2025 study on collective decisions found that whether a group values agreement or dissent depends on how strong its consensus already is — dissent is precious to a divided group, threatening to a settled one. Timing matters. But I suspect the organizations that struggle most in the next decade will not be the ones that argue too much. They will be the ones that stopped noticing when they had stopped arguing — because the agreement arrived so quickly, so fluently, and so uniformly that nobody thought to ask where it came from. --- # How Managers Should Spend AI Time Gains URL: https://adam.grgs.space/articles/manager-ai-time-reinvestment/ · Published: 2026-08-06 > Research shows AI saves managers six hours weekly. Reinvesting that time in people versus admin determines team performance, burnout, and employee turnover. Two managers on the same floor were given the same gift this year: about six hours a week. Both lead teams of twelve. Both adopted AI in the winter. BetterUp Labs, studying what actually happens to managers after adoption, found that AI returns roughly six hours a week to the average manager. What happens next is where the two floors diverge. ## What happens next The first manager did the sensible thing. He used the time to make existing work better and to catch up on administration. In the aggregate data, that is where most of it goes — around 42% into improving work already underway, 33% into admin. Both are defensible. Neither moved his team’s performance with AI at all. The second manager spent the hours on her people, her own thinking, and the questions nobody had time to ask. In the same research, managers who reinvested that way saw their team’s AI performance rise by 65%. There is a harsher finding underneath. Some managers used the tool to absorb the conversations themselves — the mentor check-in routed to a chatbot, the feedback delivered as a generated summary, the career discussion politely automated. Where that happened, team coordination fell 12%, burnout rose 26%, and intent to leave rose 29%. The efficiency was real. The organization paid for it somewhere else. ## So what does the second manager actually do on She does not run the work. The work largely runs itself now. She spends the morning reading, not reviewing — going through what her team has written down about where they got stuck, what they noticed, what question they could not let go of. She is looking for the two or three observations that nobody has authority to act on yet. She takes one of them to a person who has never been asked for an opinion on it, because different histories produce different answers. Before the difficult conversation at three, she uses AI — not to write the message, but to rehearse. To think through how it will land. Then she has the conversation herself, in a room, badly if necessary. She protects one hour with no output attached to it. This is the hardest thing on her calendar to defend and the only thing on it that compounds. None of that appears in a productivity dashboard. All of it is the job. I do not think this shift is being handled well anywhere. Gallup’s data show the average manager’s team grew from 10.9 people to 12.1 in a single year, while manager engagement fell nine points since 2022 to 22% globally — the steepest decline of any group in the workforce. Managers still spend a median of 40% of their time doing individual contributor work. Research from Harvard Business School on two consulting firms found middle managers quietly absorbing an entirely new job — validating AI output, catching its errors, coaching their teams through it — while delivery pressure stayed exactly where it was. ## We handed the middle of the organization a new The six hours are not a reward. They are a test of what an organization believes a manager is for. If the answer is still throughput, the hours will be spent on throughput, and the strange arithmetic will hold: everyone faster, nothing better. I suspect the most valuable thing a manager will do in the coming decade is create the conditions in which other people think well — and that this will be almost impossible to measure, easy to cut, and the entire source of a company’s advantage. The tool gave us the time. It cannot tell us what the time is for. --- # AI, Management Layers, and the Future of Hierarchy URL: https://adam.grgs.space/articles/ai-organizational-hierarchy-management-layers/ · Published: 2026-08-05 > Explore how AI transforms organizational hierarchy and management layers, shifting managers from routing knowledge to architects of team thinking. Every org chart is an answer to a question almost nobody asks anymore: what does it cost to move knowledge? Twenty-five years ago the economist Luis Garicano offered the cleanest explanation of hierarchy we have. Organizations build layers because knowledge is expensive. You cannot afford to have everyone know everything, so you let most people handle the routine cases and route the exceptions upward to someone who knows more. A layer is not a status symbol. It is a compression device for scarce expertise. ## Hierarchy has always been a technology Which means hierarchy has always been a technology, and technologies have assumptions. Garicano’s assumption was that knowledge is costly to acquire and costly to transmit. That assumption is now visibly loosening. The evidence is stranger than the slogans suggest. A 2025 NBER working paper reconstructed the internal hierarchies of more than 2,500 U.S. public firms from the résumés of 16 million employees. The average firm turned out to have about ten layers. Companies added layers after demand shocks — exactly as the theory predicts — and, notably, flattened them after adopting AI. Cheaper knowledge, fewer routing stations. But a longitudinal study of Italian firms found something close to the opposite: firms investing in emerging information technologies got deeper, with narrower spans of control and more middle management. A recent Harvard Business School working paper predicts flattening, narrowing and winnowing all at once. A modelling paper on generative AI in the knowledge economy finds that as AI becomes more capable, spans may actually narrow, because someone has to supervise output that is plausible whether or not it is correct. So: does AI flatten organizations or thicken them? The research disagrees, and I think the disagreement is the finding. ## Layers are not disappearing Layers are not disappearing. They are losing their original job and looking for a new one. When routing knowledge was the work, a manager’s value was proximity to answers. You escalated to them because they knew. Remove that, and a layer has two futures. It can become a control layer — approvals, reporting, verification, the endless checking of machine output. Or it can become something we have never seriously designed: a layer whose product is other people’s thinking. Most organizations will drift toward control, because control is legible. It generates documents. It survives budget reviews. And there will be real work there — someone must own the judgment that AI cannot own. But a company that converts its entire managerial capacity into a quality-assurance function has quietly decided that its people are a risk to be managed rather than an intelligence to be assembled. ## The alternative is not flatter The alternative is not flatter. It is differently loaded. Hamel and Zanini once estimated that excess bureaucracy costs the U.S. economy over three trillion dollars a year, roughly 17% of GDP, and that the country carried a bureaucratic class of some 24 million people — about one manager or administrator for every five workers. Their conclusion was that bureaucracy is a tax on human potential. I would put it slightly differently. Bureaucracy is what a coordination layer becomes when its coordination problem has been solved and nobody has told it. We are about to solve a great deal of the coordination problem. The question is what we ask those layers to do next. My own guess is that the most valuable manager in an AI-native organization will not be the one who knows most, or who checks most, but the one whose team produces the best questions. Not a router of knowledge. An architect of conditions. That is a genuinely new job, and no org chart in the world currently has a box for it. --- # Why Employees Ask AI Questions They Hide From Peers URL: https://adam.grgs.space/articles/hidden-cost-asking-ai-workplace/ · Published: 2026-08-04 > Employees ask AI basic questions to avoid looking incompetent, hiding organizational ignorance and masking the high social cost of curiosity at work. A colleague told me recently that she had asked an AI system a question she would never have asked her own team. It wasn’t a sensitive question. It was a basic one — something about how a part of her company’s business actually worked, a thing she felt she should have understood three years ago. She typed it into a chat window instead of turning to the person sitting eight feet away who could have answered it in a sentence. I have done the same thing. I suspect most people reading this have. We tend to file this under convenience. I think it is something else. It is a measurement. ## The social-psychological cost There is a long research tradition on why people don’t ask. Studies of help-seeking at work find that employees avoid asking colleagues for two reasons: a social-psychological cost — the fear of appearing incompetent — and an economic one — the worry that the question follows you into a promotion conversation. Field experiments on internal knowledge platforms show both costs suppress asking, and that anonymity partly removes them. When the seeker’s name is hidden, the questions come out. A study published earlier this year in Knowledge and Process Management gives the darker version of the same finding. The authors name a construct they call knowledge suppression: the conscious withholding of valuable, unsolicited information because of interpersonal and socio-emotional barriers. Not hoarding — the person is not protecting an advantage. They have something worth saying and they decide the interpersonal risk isn’t worth it. Three mechanisms drive it: fear of the recipient’s reaction, a wish to spare someone’s feelings, and self-protection. The authors’ conclusion is one I keep returning to: the intelligence is being lost not through missing technology or missing requests, but through unmanaged social filters. ## The safest colleague most people have ever had Now place a machine inside that system. The AI does not judge. It does not remember your question at review time. It has no opinion of you, no rank, no meeting you are also in. It is, in a strictly psychological sense, the safest colleague most people have ever had. Of course we ask it things we won’t ask each other. The cost of asking has dropped to zero on one channel and stayed high on every other one. Which means something useful is now visible. The gap between what people ask machines and what they ask each other is a rough measure of how much social cost your organization imposes on curiosity. Every question routed to AI that a colleague could have answered better is a small reading on that instrument. I want to be careful here. Asking AI is often simply the right choice, and I am not arguing for friction. What I am arguing is that a question asked of a machine ends where it started. Nobody learns that this thing is unclear to competent people. No process gets fixed. The person who could have answered never discovers what their expertise looks like from outside. The answer arrives, and the organization learns nothing. ## The quiet cost That is the quiet cost. AI can make individuals informed while leaving the organization exactly as ignorant of itself as it was before. So the question I would put to any leadership team is not “how do we get people to use AI more?” It is closer to: what does the fact that our people prefer asking a machine tell us about what it costs to ask us? Contribution requires exposure. A question is the smallest possible act of visible not-knowing. If the machine is absorbing all of them, we have not solved the problem of ignorance. We have privatized it. --- # The Employee Contribution Record Alternative URL: https://adam.grgs.space/articles/employee-contribution-record-alternative/ · Published: 2026-08-03 > Discover the contribution record, a weekly 15-minute practice designed to capture hidden thinking, judgment, and value beyond standard performance reviews. Last week I argued that the résumé is an inventory of execution — a document engineered to count throughput at exactly the moment throughput stopped being scarce. A few people asked the obvious follow-up question: fine, but what would you keep instead? Here is the honest answer. Something small, weekly, and almost boring. I call it a contribution record. Not a performance log. Not a brag document. A short, standing account of what a person added that no system could have generated on its own. ## Five prompts, answered once a week, in fifteen minutes: 1. What question did I raise that changed how we were thinking about something? 2. What assumption did I test — mine or someone else’s — and what did I find? 3. Where did my judgment improve a decision, including the decisions I argued against? 4. What did I notice that nobody had asked me about? 5. What did someone else build on, because I put it into the room? That is the whole instrument. ## Two things make me believe it is not a The first is what we know about reflection. Giada Di Stefano, Francesca Gino and Gary Pisano ran a field experiment in which employees who spent fifteen minutes at the end of each day writing about what they had learned performed about twenty-three percent better on the final assessment than those who spent the same time practising. The follow-on work — ten experimental studies, more than four thousand participants — found the same pattern across settings. People systematically prefer doing to thinking about doing, and that preference is expensive. Articulation is not overhead. It is where experience becomes usable knowledge. The second is what we know about the alternative. Roughly nine in ten managers report dissatisfaction with their organization’s performance review system. Around two thirds of employees say reviews do not actually improve their performance. Recent work on hybrid workplaces finds a stubborn presence-based bias: managers still infer contribution from visibility. We built an expensive annual ceremony to evaluate people, and then discovered it mostly measures who was in the room. A contribution record is not an appraisal. Nobody is scored. It is written by the person, kept by the person, and read by their manager the way a colleague reads a colleague’s notes — with curiosity, not with a rubric. Its value is not accuracy. Its value is that it makes visible a category of work that currently has no home in any organizational system: the thinking. ## Three practical notes, learned the hard way Keep it additive, not defensive. The moment people sense the record will be used against them, it becomes marketing. The prompts must ask what they added, never what they completed. Let entries be empty. Some weeks a person contributed nothing beyond competent execution, and saying so honestly is more useful than manufacturing an insight. An empty week is data — often about the environment, not the person. Read across, not down. One person’s record is a diary. Forty records read together are an intelligence system. You start to see which questions keep recurring, which assumptions the organization has never tested, and where the same insight arrives from four unconnected places. None of this requires software. It requires deciding that thinking is part of the job and therefore part of the record. We spent a century getting very good at recording what people produced. If contribution is genuinely becoming the scarce input, the first move is not a new metric. It is the humbler act of writing it down. --- # Why the CV Cannot Measure True Contribution URL: https://adam.grgs.space/articles/measuring-contribution-beyond-the-resume/ · Published: 2026-08-02 > Resumes measure execution, not thinking. As hiring data prioritizes judgment over output, organizations need new ways to record actual contribution. The résumé is an inventory of execution. Almost every line on it describes something a person did, how much of it, and how fast. Managed. Delivered. Increased. Reduced. Led. It is a document built for an economy where doing things was the scarce part. That economy is quietly ending, and the paperwork hasn’t caught up. ## Look at what hiring data has started to show Look at what hiring data has started to show. A March 2026 survey of 991 U.S. hiring managers found roughly six in ten now consider creative thinkers more valuable than coders. Drexel’s 2026 Early-Career Skills Outlook found that technical and AI skills are rated substantially lower than expected as screening criteria — employers assume those will be trained after hiring. Meanwhile TestGorilla surveyed around 2,000 senior hiring leaders: 95% now list AI fluency as a requirement, and 59% have still made a bad AI hire. Candidates sound fluent in the interview and fall apart in the work. Read those three findings together and a strange picture appears. Organizations have decided that what they most need is judgment, originality, and the ability to think with a machine rather than hide behind one. And they are trying to detect all of it using a document designed to certify throughput. I keep coming back to a simple question: if a person’s most valuable trait is the quality of their thinking, what is the evidence? There is no line on any CV that reads: “Asked the question in month two that stopped us from spending eighteen months on the wrong product.” No line for “noticed the pattern nobody else noticed.” No line for “was the only person willing to say the plan was weak.” These are the contributions that most change an organization’s trajectory, and we have no artifact that records them — not in hiring, not in promotion, not in performance reviews. So we approximate. We ask about output and hope thinking was behind it. Sometimes it was. Often we are just reading the résumé of a system that happened to work, written by someone standing near it. ## This is not a hiring problem This is not a hiring problem. It is a measurement vacuum, and it operates in both directions. Organizations cannot see contribution in the people they are considering, and they cannot see it in the people they already employ. The same blindness that makes the CV a poor predictor makes the promotion cycle a poor sorter. What would the alternative document look like? Perhaps not a document at all. Perhaps a record: the questions a person raised, the assumptions they tested, the decisions they improved, the disagreements they made productive, the ideas they contributed that other people built on. ## Contribution is not invisible Contribution is not invisible. It is simply unrecorded. Execution was easy to count, so we counted it, and then we mistook the count for the person. We are about to need a better instrument. I suspect the organizations that build one first will look, for a while, like they are hiring luckier people than everyone else. --- # AI Adoption and the Unclaimed Time Dividend URL: https://adam.grgs.space/articles/ai-time-dividend-infrastructure/ · Published: 2026-08-01 > When AI returns time to workplaces, unclaimed minutes flow back into sheer volume. Organizations need contribution infrastructure, not just efficiency gains. A nursing unit installs an AI documentation assistant and gets back roughly twenty-four minutes per shift. Nobody in the organization has decided what those minutes are for. This is the most common and least discussed moment in AI adoption. The evidence that AI returns time is now unusually solid. A time-motion study of AI speech-assisted nursing documentation in German long-term care measured an adjusted reduction of about fifteen minutes of documentation per nurse, with total documentation time falling by more than twenty-four minutes per shift. A 2026 systematic review of AI-based nursing documentation found reductions ranging from twenty percent to over sixty percent. ## The question is who owns them So the hours exist. The question is who owns them. In practice, the answer is decided by default rather than design. Freed minutes get absorbed by higher patient loads, thinner staffing ratios, or simply more documentation of a different kind. The dividend is real, it is just unclaimed. And an unclaimed dividend always flows toward whatever the organization already measures. Consider the alternative, and consider it through an example that has nothing to do with AI. Toyota has run a company-wide idea system since the 1950s. The numbers are strange enough that people usually assume they are wrong. Roughly 700,000 improvement ideas submitted per year across the Japanese operations. Historically about seventy percent implemented, and in some accounts far more. In 1973, with 43,000 employees, the company was on track for over 250,000 suggestions. Robinson and Stern’s comparative data put Japanese manufacturers at around 18.5 ideas per employee per year against 0.16 in the United States — a hundredfold difference, in factories running comparable equipment, making comparable products, staffed by comparably capable people. ## That gap is not a talent gap That gap is not a talent gap. It is an infrastructure gap. Toyota did not have unusually creative workers. It had a system that made noticing worth something: a place to put an observation, a short path to a decision, a visible record that ideas became changes. Most organizations have no such plumbing. They have suggestion boxes, which are not plumbing — they are storage. So when AI hands back twenty-four minutes, those minutes have nowhere to travel except back into throughput. Which produces the central design question of this decade, and I think it is a genuinely new one: ## What has it built to receive it? An organization is about to receive a large, involuntary gift of human attention. What has it built to receive it? If the honest answer is nothing, the gift will be converted into volume. That is not a moral failing. It is what happens when the only well-built channel in a company runs from work to output. A ward that had thought about this in advance would look different in mundane ways. The freed time would be named and protected, not left to evaporate. Nurses would have a five-minute channel for the pattern they noticed across three patients this week, and someone with authority would be obligated to respond within a defined window. Implemented changes would be posted where the people who suggested them can see them. None of this is expensive. It is simply built, the way the documentation system was built. The lesson I take from Toyota is not about manufacturing. It is that contribution responds to architecture far more than to encouragement. Companies that tried to copy the suggestion count without copying the response mechanism got nothing, because employees are excellent at detecting whether a channel actually leads anywhere. AI is now generating the raw material — time, attention, cognitive headroom — that a contribution system runs on. Most organizations will spend the next few years handing that material back to the machine. The interesting ones will build somewhere for it to go first. --- # Why AI Polish Undermines Critical Thinking URL: https://adam.grgs.space/articles/ai-confidence-transfer-critical-thinking/ · Published: 2026-07-31 > Discover how AI polish transfers user confidence to the tool, reducing critical thinking effort, and learn why organizations must design for human judgment. I noticed something uncomfortable about my own work recently. I was reviewing a document an AI had drafted for me. It was good. Clear structure, reasonable logic, no obvious errors. I read it twice, made three small edits, and approved it. Then I asked myself a question I did not enjoy answering: would I have caught a serious flaw if there had been one? I am not sure I would have. Not because I lack the ability, but because the draft arrived already looking finished. ## Polish invites agreement And I had unconsciously shifted from thinking about the problem to checking the answer. There is research on this now. Microsoft Research surveyed 319 knowledge workers who shared 936 real examples of using AI in their work. The pattern they found was not that AI makes people less capable of thinking. It was subtler and more troubling: the more confidence people had in the AI, the less critical thinking effort they applied. The more confidence they had in themselves, the more they applied. Confidence, it turns out, is a finite resource that moves. When we place more of it in the tool, we withdraw some from ourselves. A separate 2026 study of over 1,200 people found something related — participants were poorly calibrated at estimating how much time AI actually saved them. The felt speed and the real speed diverged. The authors called it a speedup illusion. I keep returning to what these findings imply for organizations, because I do not think it is a training problem. Every organization I know is currently measuring AI adoption. Seats deployed. Tasks automated. Hours saved. Not one is measuring whether the quality of human thinking inside the organization went up or down. ## We have instrumentation for the machine and none for And there is a strange asymmetry here. Microsoft’s 2026 Work Trend Index found that when workers were asked which skills matter most as AI takes on more work, the top two answers were quality control of AI output and critical thinking. Eighty-six percent said they treat AI output as a starting point rather than a final answer. So people know. They can name the skill. What they lack is an environment that protects the conditions for exercising it — time, doubt, dissent, the permission to say “this looks right and I still don’t trust it.” That permission is not a personality trait. ## It is an organizational design choice If a team’s meetings are structured so the fast answer wins, the AI draft will win. If disagreement costs social capital, no one spends it questioning something that already reads well. If the calendar has no space between receiving work and deciding on it, judgment gets compressed into approval. Contribution Leadership starts from the premise that AI should optimize work while organizations optimize humans. What I am learning is that this is not only about unlocking what people can add. It is also about defending what they might quietly lose. The most valuable thing a person brings to an AI-saturated organization may be their willingness to remain slightly unconvinced. Which raises a question I do not have a clean answer to yet: if confidence transfers from the person to the tool, what does a leader do to transfer some of it back? I suspect the answer looks less like a policy and more like a practice. Asking someone to explain the reasoning, not just the output. Reviewing decisions, not just deliverables. Making it normal — expected, even — to say “I used AI here, and here is where I still think it’s wrong.” Small rituals. But they may be the difference between an organization that thinks with AI and one that slowly stops thinking at all. --- # Beyond the Skills-Based Organization URL: https://adam.grgs.space/articles/beyond-skills-based-organizations/ · Published: 2026-07-30 > While skills-based organizations improve on job titles, true value lies in contribution—what employees uniquely notice, question, and create that AI cannot. Sixty-one percent of organizations now deploy workers based on tasks, skills, and outcomes rather than job titles. Only a third still rely on traditional position-based models. This is the largest shift in organizational design in decades. And it’s genuine progress — organizations are finally acknowledging that people are more than their titles. I wonder whether it goes far enough. The skills-based organization is better than the job-based organization. Instead of fitting people into rigid roles, it maps what they can actually do. More flexible. More honest. More responsive to the pace of change that AI demands. ## Skills are still an execution lens They describe capacity — what someone is able to do. They don’t describe contribution — what someone notices, questions, connects, or reimagines that no one asked them to. The hospital cleaner who times her work around patient recovery and notices emotional shifts in patients’ families has no skills taxonomy entry for any of that. The engineer who asks the question that prevents a catastrophic product decision isn’t deploying a cataloged capability. The analyst whose background in philosophy helps her see a strategic pattern everyone else missed — that doesn’t appear in a skills profile. Skills can be inventoried. Contribution can only be cultivated. ## A three-stage evolution Perhaps what we’re witnessing is a three-stage evolution: - A job-based organization asks: _What position does this person fill?_ - A skills-based organization asks: _What capabilities does this person have?_ - A contribution-based organization asks: _What does this person see, question, and create that no one else does?_ The first two are legible. They fit in databases, talent platforms, work charts. They can be sorted, scored, optimized. Contribution resists that. It emerges from the intersection of someone’s experience, curiosity, values, and context. It changes daily. It defies taxonomy. That’s precisely why it’s becoming the most valuable thing in an organization. When AI can perform most cataloged skills, the scarce resource isn’t what people can do. It’s what they uniquely notice, uniquely question, uniquely imagine. No work chart maps it. No talent platform indexes it. ## The skills-based organization is a necessary bridge Eighty-eight percent of leaders say the ability to dynamically orchestrate people and capabilities is critically important. Only seven percent say they’re making real progress. I wonder whether that 81-point gap exists because they’re trying to orchestrate skills — when what they should be doing is creating conditions for contribution. The skills-based organization is a necessary bridge from the job-based organization. But a bridge is not a destination. The destination is an organization that doesn’t just catalog what people can do — but creates the environment for them to contribute what no system would ever think to request. --- # What Is Dignity Debt in the Workplace? URL: https://adam.grgs.space/articles/dignity-debt-workplace-productivity/ · Published: 2026-07-28 > Explore dignity debt, the hidden cost of prioritizing productivity over employees. New research reveals why high productivity leads to career change. Eighty-one percent of business leaders say employee productivity increased this year. Eighty-one percent of employees say they want to change careers entirely. Same organizations. Same year. Completely different realities. BambooHR surveyed over 1,200 people across six industries and found something that should stop every executive mid-sentence: the more productive companies believe they’ve become, the less their people want to stay in the profession. ## Dignity debt They gave this phenomenon a name. Dignity debt. Dignity debt is the compounding cost of treating people as a means to productivity rather than as the humans who make productivity possible. It works like financial debt. Small withdrawals — an ignored suggestion, a metric that reduces someone’s work to a number, a reorganization announced without explanation — feel manageable in isolation. But they compound. And the interest shows up not in a line item, but in burnout, disengagement, attrition, and a weakening talent pipeline. The numbers are striking. Eighty-five percent of employees report significant workplace stress. More than half are actively looking for new roles. Nearly half would leave their entire industry for a raise of twenty percent or less. Fifty-seven percent agree there is a fundamental flaw in how their industry operates. These aren’t people who lack motivation. They’re people whose organizations borrowed against their dignity and never paid it back. New research from Portland State University, published in the Journal of Occupational Health Psychology, traces the mechanism. When employees feel dehumanized — treated as tools or cogs rather than people — two things happen simultaneously. Internally, they experience inauthenticity. They stop bringing their real selves to work. That suppression leads directly to emotional exhaustion. Externally, they experience powerlessness. They stop helping colleagues. The voluntary collaboration that makes organizations adaptive quietly disappears. The researchers’ conclusion was pointed: standard fairness initiatives are insufficient. Organizations need a human-centric approach to management that restores employee agency. ## Restores agency I keep returning to that phrase. Restores agency. Not improves efficiency. Not increases output. Returns to people the sense that they are participants in their work — not instruments of someone else’s process. ## Contribution Leadership This is what I mean when I talk about Contribution Leadership. It isn’t a culture initiative or an engagement program. It’s a recognition that when you design an organization around human dignity, you unlock capacity that no productivity tool can reach. AI can optimize every process in your organization. It cannot restore someone’s sense that their thinking matters — that their perspective is valued, that they are more than their output. The organizations accumulating dignity debt right now are celebrating their productivity numbers. The ones paying it down are building something their competitors cannot copy: an environment where people actually want to contribute. Dignity isn’t a soft value. It’s an operating cost you’re already paying. The only question is whether you’re paying it forward or borrowing against it. --- # Why AI Makes Workplace Ideas More Alike URL: https://adam.grgs.space/articles/ai-reduces-idea-diversity-innovation/ · Published: 2026-07-20 > Four MIT studies show AI increases individual quality while reducing collective idea diversity, threatening true innovation and creative variance. AI is making everyone’s work better. That might be the problem. Four studies synthesized this month in MIT Sloan Management Review — spanning short-story writing, sustainability solutions, humor, and collaborative storytelling — found the same pattern: when people use AI, their individual output improves. Quality goes up. Writing gets sharper. Solutions get more polished. But something else happens. Everyone’s work starts looking the same. Across all four studies, AI assistance reduced the collective diversity of ideas. Higher average quality. Fewer outliers. The breakthroughs — the weird, unexpected, category-defining ideas — got rarer. The researchers call it a social dilemma. Each person is individually better off. But collectively, the idea space narrows. ## Everyone converges on “good enough” Everyone converges on “good enough.” This should concern every leader who believes their competitive advantage comes from innovation. ## Innovation doesn’t come from better averages Because innovation doesn’t come from better averages. It comes from variance. From the idea nobody expected. From the person who thought about the problem differently because they had a different life, a different frustration, a different question. Optimization smooths those edges away. We are entering an era where AI can give every team member polished, competent, well-structured output. That’s extraordinary. But if every organization uses the same tools to optimize the same processes toward the same standards, the result isn’t differentiation — it’s convergence. The organizations that will lead won’t be the ones with the best AI stack. They’ll be the ones that cultivate the most divergent human thinking alongside it. ## The most dangerous AI strategy isn’t failing to adopt This is why I keep returning to the idea of Contribution Leadership. Not because AI isn’t valuable — it is, profoundly. But because AI handles the part that’s becoming abundant: execution, polish, synthesis. The scarce part — the part that creates competitive advantage — is the originality that AI can’t generate on its own. Messiness creates discovery. Variation creates insight. Different experiences produce different ideas. The most dangerous AI strategy isn’t failing to adopt. It’s adopting so thoroughly that you optimize away the only thing your competitors can’t copy: the way your people think. --- # The AI Productivity Performance Paradox URL: https://adam.grgs.space/articles/ai-productivity-performance-paradox/ · Published: 2026-07-19 > Traditional productivity metrics reward uncritical speed over judgment in the age of AI. Learn why contribution matters more than execution output. What if the most valuable person on your team is the one who looks least productive? A field experiment published in Organization Science tracked 750 knowledge workers using GPT-4. Workers with AI were 25 percent faster and produced higher-quality output on tasks within the model’s capability. But on a task just outside that capability — where the AI was confidently wrong — workers who relied on it were 19 percent less likely to reach the correct answer than those working without it. Here’s what makes this uncomfortable: the people who slowed down to verify the AI’s output, who questioned it, who caught the errors — they looked less productive by every traditional metric. Less output per hour. Fewer deliverables. Slower turnaround. They were the ones adding the most value. ## The performance paradox Harvard Business Review called this the performance paradox. Organizations still evaluate employees with pre-AI metrics — productivity, goal completion, tasks per hour — and those metrics now reward the wrong behavior. They reward uncritical speed over careful judgment. Consider what this means at scale. Gallup’s 2026 State of the Global Workplace report — 263,000 respondents across 160 countries — found that only 20 percent of employees are engaged at work. Eighty percent are either not engaged or actively disengaged. We tend to read that as a motivation problem. I wonder if it’s a measurement problem. ## When organizations measure output When organizations measure output, they get output. When they measure hours, they get hours. When they measure compliance, they get compliance. What they don’t get is thinking. They don’t get the engineer who notices a systemic flaw but says nothing because flagging problems slows her numbers. They don’t get the analyst who sees a strategic connection across departments but has no forum to share it. They don’t get the manager who could redesign a process but is too busy being measured on the old one. Every organization is full of unused intellectual capital. Not because people lack ideas — but because nothing in the system asks for them. This is the shift I keep returning to. For two centuries, organizations built their operating systems around execution. Performance was the measure of value. And it worked — when execution was scarce. ## The bottleneck is contribution But AI is making execution abundant. McKinsey’s global managing partner reported that AI saved his firm 1.5 million hours of search and synthesis in a single year. Twenty-five thousand AI agents produced 2.5 million charts in six months. The execution capacity is no longer the bottleneck. The bottleneck is contribution — the thinking, questioning, connecting, and judgment that no model can replicate. And yet our measurement systems still point in the other direction. I wonder whether the most important organizational innovation of the next decade won’t be a new technology or a new strategy. It may be a new unit of measurement. Not output. Not productivity. Not even performance. Something closer to: did this person make the organization think better? We don’t have that metric yet. But the organizations that figure it out first will have an extraordinary advantage — because they’ll be the ones who finally learn what 80 percent of their people have been waiting to contribute. --- # Why AI Exposed a Design Gap in Education URL: https://adam.grgs.space/articles/education-design-gap-ai-skills/ · Published: 2026-07-17 > AI didn't create a skills gap; it exposed a design gap in education. Discover why the economy now rewards unpredictable human qualities like judgment. For two hundred years, we built schools around a simple theory: educate people to do what machines cannot. It worked — until machines learned to do nearly everything we were teaching. PwC just analyzed over a billion job postings across six continents. The premium rising fastest isn’t technical skill. It’s judgment. Creativity. Leadership. The capabilities we’ve always called “soft” and never formally taught. ## The premium rising fastest The World Economic Forum confirms it: by 2030, 39% of core workforce skills will need to change. The fastest-growing are analytical thinking, resilience, creative thinking, and curiosity. We graded on memorization. Rewarded compliance. Called the most obedient students “gifted.” ## AI didn’t create a skills gap AI didn’t create a skills gap. It exposed a design gap — between institutions built to produce predictable workers and an economy that now rewards the unpredictable ones. The capabilities the world needs most were never missing from people. They were missing from the curriculum. ## What makes humans irreplaceable The most important question in education isn’t how to teach people to use AI. It’s whether we’ll redesign institutions around what makes humans irreplaceable — courage, empathy, ethical reasoning, and originality. Those qualities were always there. We just spent two centuries testing them out of people. --- # AI Translation and the Immigrant Wage Gap URL: https://adam.grgs.space/articles/ai-translation-immigrant-wage-gap/ · Published: 2026-07-15 > Explore how AI translation platforms are shifting the burden of language barriers, addressing immigrant wage gaps and redefining workforce potential. On a construction site outside Seoul, a safety briefing is delivered in Korean. Within seconds, workers from Vietnam, Uzbekistan, Nepal, and Cambodia hear it in their own languages. This isn’t science fiction. Two of South Korea’s largest builders — Daewoo E&C and Lotte Engineering — deployed AI translation platforms across dozens of construction sites this year. Daewoo’s system supports 180 languages with a construction-specific glossary. Technical terms. Safety protocols. Equipment names. Calibrated for an environment where a mistranslation isn’t an inconvenience — it’s a catastrophe. ## But this story is bigger than construction safety Across OECD countries, immigrants earn 18% less than native-born workers. Three-quarters of that gap isn’t about skills — it’s about access to better-paying jobs, industries, and firms. And the single strongest predictor of that access is language proficiency. Research across Europe consistently finds a 23–27% wage penalty for immigrants who haven’t mastered the host country’s language. A Federal Reserve study calculated that barriers preventing immigrants from reaching their productive potential cost the U.S. economy the equivalent of 25% of immigrants’ total economic contribution. ## A translation problem The OECD found that immigrant earnings gaps shrink by a third in five years and by half in ten. That timeline assumes the immigrant does all the adapting. Years of immersion. Formal classes. Cultural code-switching. The entire burden falls on the person with the potential — not on the institution that needs it. ## AI inverts this Instead of asking “How fast can you learn our language?” it asks “Why should language determine who gets to contribute?” A surgeon who speaks Dari. An engineer who speaks Tagalog. A welder who speaks Uzbek. Their competence never changed. The interface did. We’ve spent decades measuring immigrants by their fluency. Maybe we should have been measuring our systems by their flexibility. --- # Why Hiring Instincts Waste Human Potential URL: https://adam.grgs.space/articles/hiring-instincts-wasted-human-potential/ · Published: 2026-07-13 > Explore how hiring instincts often rely on pattern-matching and familiarity rather than talent, leading to massive wasted potential in the economy. I used to think I had good instincts about people. You know the feeling. You sit across from someone and within minutes, you’ve decided. Sharp or not. Leadership material or not. Good fit or not. I was confident in that radar. I could just tell. ## I was spotting familiarity Then I started paying attention to who I picked. Same schools. Same references. Same way of framing a problem. Same sense of humor. I wasn’t spotting talent. I was spotting familiarity. ## It was pattern-matching Lauren Rivera spent years embedded in hiring at elite banks, law firms, and consulting firms. She found that interviewers consistently chose candidates who shared their hobbies, backgrounds, and cultural markers — not those with the strongest skills. They called it “fit.” It was pattern-matching. ## Wasted human potential in the economy A University of Catania simulation tracked a thousand careers over forty years and found something even more uncomfortable: the most successful people weren’t the most talented. They were moderately talented and very lucky. We just told ourselves the story backward. Here’s the reframe I can’t shake: what we call “great instincts about people” might be the single largest source of wasted human potential in the economy. Not because we’re malicious. Because similarity feels like quality — and that feeling is invisible, especially to the person having it. The institutions that unlock the most potential won’t be the ones with the best talent radar. They’ll be the ones brave enough to ask whether talent radar was ever real. --- # Why Workplace Trust Beats Employee Monitoring URL: https://adam.grgs.space/articles/workplace-trust-vs-employee-monitoring/ · Published: 2026-07-10 > Discover why high-trust companies achieve higher productivity and engagement, while employee monitoring crushes workplace creativity and retention. The most productive organizations in the world aren’t the ones watching their people the closest. ## The neuroscience of trust Paul Zak spent a decade studying the neuroscience of trust. People in high-trust companies report 76% more engagement, 50% higher productivity, and 40% less burnout. Half the turnover. And yet — companies keep buying keystroke loggers and screen trackers. Every study confirms the same finding: monitoring crushes exactly the creativity it claims to protect. ## The 2026 Edelman Trust Barometer The 2026 Edelman Trust Barometer — 34,000 people, 28 countries — found that employers are now the most trusted institution on earth. Seventy-eight percent. Ahead of business, media, and government. That’s not a metric. It’s a mandate. ## AI gives every leader the same fork AI gives every leader the same fork: use it to watch people more closely, or to remove the friction that keeps them from contributing. The organizations that define the next decade won’t be the ones that monitored the hardest. They’ll be the ones that trusted the deepest. --- # How AI Tutors Drive Massive Learning Gains URL: https://adam.grgs.space/articles/ai-tutor-education-case-study/ · Published: 2026-07-08 > Explore how AI tutors in rural Sierra Leone and generative AI in the workforce show that disadvantaged groups gain the most from new technologies. In rural Sierra Leone, fewer than one in four junior secondary students reach basic math proficiency. Most of their teachers never received formal training in mathematics. ## Randomized controlled trial across twelve schools Last month, Google DeepMind published results from a randomized controlled trial across twelve schools in Port Loko District. Over 1,700 students used an AI tutor for an average of fifteen hours over eight weeks. The result: learning gains equivalent to 1.2 to 1.7 years of typical progress. Students who completed twelve hours moved from the middle of their class into the top third. These weren’t students with private tutors and fiber internet. They were teenagers in one of the world’s poorest countries, learning fractions and exponents on basic devices — with a tutor that met each of them exactly where they were. ## The people with the fewest advantages consistently gain the A separate NBER study found a similar pattern at the other end of the pipeline: generative AI closes three-quarters of the productivity gap between workers with and without formal education. The people with the fewest advantages consistently gain the most. ## Whether AI will take jobs We spend enormous energy debating whether AI will take jobs. Perhaps the more urgent question is whether we’ll let it give people the preparation those jobs require. Fifteen hours. That’s all it took to show how thin the wall between potential and contribution really is. --- # Why Degree Requirements Fail Modern Hiring URL: https://adam.grgs.space/articles/degree-requirements-hiring-skills-gap/ · Published: 2026-07-06 > Explore why seventy million Americans are locked out of jobs by unnecessary degree requirements and how credential filtering creates a false skills gap. Seventy million Americans are qualified for jobs they’ll never be interviewed for. Not because they lack the skills. Because they lack the diploma. Opportunity@Work calls them STARs — Skilled Through Alternative Routes. They make up 58% of the prime-age U.S. workforce. Veterans. Self-taught developers. Caregivers who re-entered the workforce. Tradespeople who pivoted careers. They’re not unskilled. They’re unrecognized. And we call this a “skills gap.” Here’s what a skills gap actually looks like: Between 2000 and 2020, STARs lost access to 7.4 million jobs — not because the work changed, but because employers added degree requirements to roles that never needed them. Harvard Business School found that companies pay 11 to 30 percent more for degree holders to do the exact same work, with no measurable improvement in productivity, promotion speed, or engagement. ## The degree premium isn’t a performance dividend It’s a tax on a credential. ## The gap isn’t in people’s skills It’s in our ability to recognize them. And even when we try to fix it, the pattern holds. The Burning Glass Institute found that when companies removed degree requirements from job postings, fewer than 4 percent actually hired a non-degree candidate. Thirty-three states have formally dropped degree requirements for public jobs. Seventy-five percent of employers say they’re more open to non-degree talent than they were three years ago. Almost nothing has changed in who actually gets hired. We designed hiring systems that filter for credentials instead of capability. Then we looked at the people those filters excluded and concluded they must not be qualified. That’s not a skills gap. That’s an institutional blind spot so large we named it wrong. ## Potential is universal Opportunity is not. And right now, the biggest barrier to opportunity isn’t what people know — it’s whether the system is designed to see it. --- # The Economic Value of Immigrant Talent URL: https://adam.grgs.space/articles/immigrant-startup-founders-economic-impact/ · Published: 2026-07-03 > Immigrant founders drive billions in U.S. startups, yet rigid credential walls and outdated hiring algorithms waste vital global professional talent. Fifty-nine percent of America’s billion-dollar startups were founded or cofounded by immigrants. That’s 455 companies. Five trillion dollars in value. An average of 833 jobs each. And these are just the people who made it through. The NFAP published these numbers last month, and the share keeps climbing — up from 55% in 2018. Two-thirds of U.S. unicorns trace back to an immigrant or the child of one. ## The value we’ll never see But the real number isn’t the $5 trillion they created. It’s the value we’ll never see from the ones who didn’t make it past the credential wall, the visa backlog, or the hiring algorithm that couldn’t read their résumé. ## The technology to change this The technology to change this already exists. An AI pilot between Upwardly Global and Workday placed immigrant professionals into hiring pipelines by matching skills instead of credentials. Where manual screening surfaced 45 candidates, the AI found 200 — same roles, same timeframe — by simply looking at what people could do instead of where they studied. ## As infrastructure Now imagine that principle everywhere. Not as charity. As infrastructure. A world where a nurse’s competence crosses a border as easily as capital does. Where your contribution isn’t gated by which country stamped your diploma. We already know what happens when a few people slip through the cracks in the system. They build trillion-dollar industries. The question isn’t whether immigrant talent is valuable. The question is how much longer we can afford to waste it. --- # The Science of Psychological Safety in Teams URL: https://adam.grgs.space/articles/psychological-safety-team-performance/ · Published: 2026-07-01 > Google's research reveals psychological safety is the strongest predictor of high-performing teams, yet organizations routinely punish this behavior. Google spent two years studying 180 teams to find what makes them great. They measured everything. Talent. Experience. Resources. Structure. Seniority. None of it mattered most. ## The strongest predictor of team performance The strongest predictor of team performance — explaining 43% of the variance — was psychological safety. Whether people felt safe to say “I don’t know,” “I made a mistake,” or “I think we’re wrong.” Teams with it: 31% more innovation. 19% higher productivity. 27% lower turnover. ## The finding is obvious once you hear it The finding is obvious once you hear it. And almost universally ignored in practice. Most organizations still reward the person who never admits uncertainty. Who never challenges. Who performs confidence instead of practicing honesty. We keep designing institutions that punish the exact behavior the research says makes them work. ## What makes great teams The data has been clear for 25 years. The question was never what makes great teams. It’s whether we have the courage to stop rewarding the opposite. --- # AI Does Not Require New Technical Skills URL: https://adam.grgs.space/articles/ai-literacy-natural-language-equalizer/ · Published: 2026-06-29 > Explore why artificial intelligence is the first technology that doesn't require learning a new skill, leveling the playing field for all workers. Every major technology in history required you to learn its language. The printing press required literacy. The computer required code. The internet required search queries and digital navigation. Each breakthrough created a new divide between those who could learn the interface and those who couldn’t. ## AI Broke the Pattern For the first time, the technology speaks your language — literally. A farmer in rural Pakistan gets agricultural advice by talking to a phone. A customer service agent with six months of experience performs like a five-year veteran within weeks. Stanford and MIT researchers found the lowest-skilled workers gained 35% more productivity from AI. The most experienced workers? Almost nothing. ## We Built an Entire Industry We’ve spent two years panicking about “AI literacy” — launching prompt engineering certificates, AI boot camps, readiness assessments. We built an entire industry around the assumption that AI is hard to use. But the whole point of natural language is that you already know it. 700 million adults worldwide can’t read. They couldn’t use a computer, a website, or a search engine. But they can have a conversation. ## The Real Question Was Never That’s the part we keep missing. AI isn’t a new skill to learn. It’s the first technology that doesn’t require one. The real question was never “Can people learn AI?” It’s whether our institutions will stop building gates around something that was designed without walls. --- # Unlocking Human Potential and Overcoming Brain Waste URL: https://adam.grgs.space/articles/unlocking-human-potential-ai-workforce/ · Published: 2026-06-26 > Explore how credential barriers and systemic waste limit human potential, and discover how artificial intelligence is beginning to remove these walls. Somewhere right now, a surgeon is driving a taxi. Not because she lost her skills. Because her credentials don’t transfer across a border. This isn’t a metaphor. The Migration Policy Institute reports that one-third of highly educated immigrants in OECD countries are working in jobs below their qualifications. In the United States alone, that brain waste costs $40 billion in unrealized wages every year — and $10 billion in lost tax revenue. ## But credential barriers are only one lock on the There are students with extraordinary minds attending schools that will never challenge them. Entrepreneurs with transformative ideas who can’t navigate the legal system in their second language. Public servants with policy insights buried under a thousand compliance forms. The World Bank estimates that the average child born today will realize only 56% of their productive potential — not because of ability, but because of the systems they’re born into. For most of history, we couldn’t see this waste. It was invisible — distributed across billions of individual stories that never got told. ## AI is beginning to change that Not by replacing human capability, but by removing the walls around it. A brilliant researcher in Nairobi now has access to the same analytical tools as one at Oxford. An immigrant founder can draft contracts, model financials, and pitch investors in a language she’s still learning. A frontline worker can surface the operational insight that was always obvious to them but never had a format to travel upward. The question is no longer whether we have the technology to unlock human potential at scale. The question is whether our institutions — credentialing bodies, hiring systems, immigration policies, education models — will evolve fast enough to stop wasting it. ## The greatest natural resource on earth has never been It’s the person in front of you whose contribution you haven’t made room for yet. --- # Why the Best Employees Look Lazy URL: https://adam.grgs.space/articles/visible-effort-vs-deep-work/ · Published: 2026-06-24 > Explore why corporate cultures built around visible effort fail deep work, and why the quietest developer might be carrying the heaviest load. The best developer I ever worked with used to disappear for hours. No Slack messages. No status updates. No visible output until suddenly — a solution nobody else could have built. His manager flagged him twice for low engagement. Both times, the work spoke for itself eventually. ## Cultures around visible effort We’ve built entire cultures around visible effort. A full calendar feels productive. An empty one feels suspicious. Someone typing furiously looks like they’re contributing. Someone staring at a wall looks like they’re slacking. ## The work that actually changes things But thinking doesn’t send a notification. Focus doesn’t update a dashboard. And the work that actually changes things rarely looks impressive while it’s happening. Sometimes the quietest person on your team is carrying the heaviest load. --- # The Cost of Corporate Alignment Meetings URL: https://adam.grgs.space/articles/the-corporate-alignment-trap/ · Published: 2026-06-22 > Discover how corporate alignment meetings disguise decision-making avoidance as collaboration, wasting millions in manager time and stalling real progress. I sat in an “alignment meeting” last week that was called to align on the outcomes of a previous alignment meeting. That’s not a joke. That’s a Tuesday. Here’s what “alignment” really means in most companies: nobody wants to make the decision, so everyone agrees to meet again. McKinsey surveyed over 1,200 managers and found that executives spend 40% of their time making decisions — and 61% say most of that time is ineffective. At a typical Fortune 500, that translates to 530,000 days of wasted manager time per year. $250 million gone. Not on bad decisions — on the process of avoiding them. The worst part? McKinsey also found that across dozens of organizations, 40% of people involved in any given decision meeting contributed zero value. Not because they’re incompetent — because they didn’t need to be there. They were invited because excluding them would be “misalignment.” ## Productivity Theatre at its most elegant This is Productivity Theatre at its most elegant. “Alignment” is the corporate word for cowardice. It sounds collaborative. Inclusive. Strategic. But what it actually means is: - No one owns the decision - Everyone gets veto power - The meeting exists so failure is distributed - Another meeting gets scheduled to “close the loop” ## The decision itself takes 30 seconds of courage Here’s the irony: AI can surface the data, model the scenarios, and draft the recommendation in minutes. The decision itself takes 30 seconds of courage. But courage doesn’t have a calendar invite. So we schedule another alignment session instead. ## That’s not misalignment The companies that win aren’t the ones with the best alignment processes. They’re the ones brave enough to say: “I’ll decide. If I’m wrong, I’ll own it.” That’s not misalignment. That’s leadership. --- # The Death of the Corporate Middleman URL: https://adam.grgs.space/articles/death-of-the-corporate-middleman/ · Published: 2026-06-19 > AI and automation are eliminating corporate middlemen whose primary role is moving information between teams. Learn why relay-based jobs are disappearing. Every company has a human router. The person whose entire job is to ask one group what’s happening, repackage it into a slightly different format, and tell another group what’s happening. I was that person once. Project coordinator. Status report compiler. The living, breathing middleware between the people who do the work and the people who want to know about the work. ## That function is already dead Here’s what nobody wants to admit: that function is already dead. We just haven’t buried it yet. Asana’s Anatomy of Work Index found that knowledge workers spend 58% of their time on “work about work” — coordination, status updates, searching for information someone else already has. Only 33% goes to skilled work. Nine percent to strategy. ## Pure, mindless relay Most of that 58% is relay. Pure, mindless relay. Zuckerberg figured this out in 2023 when he gutted Meta’s “managers managing managers” — entire layers whose primary contribution was moving information from Point A to Point B. Not lazy people. Just people filling a function that technology had already replaced. AI doesn’t threaten the middleman. It exposes that the middleman was always a patch for bad systems. When an AI can pull status from four project tools, synthesize it, and deliver a summary in 30 seconds… what exactly is the coordinator doing in between? ## Productivity Theatre’s favourite character The middleman role was Productivity Theatre’s favourite character. Always busy. Always “in the loop.” Always copying, forwarding, summarizing. Never creating. Never deciding. If your entire value proposition is “I know what’s going on” — that’s not a career. That’s a search query. The roles that survive aren’t the ones that move information. They’re the ones that interpret it and make decisions nobody else will. --- # How AI is Compressing the Career Ladder URL: https://adam.grgs.space/articles/ai-compressing-career-ladder/ · Published: 2026-06-17 > Discover how artificial intelligence is compressing the career ladder, boosting junior performance, and redefining traditional work experience. I watched a 24-year-old with six months of experience outperform a senior consultant with fifteen years under his belt. Not because she was smarter. Because she knew how to use AI and he didn’t. Harvard and BCG ran a study with 758 consultants using GPT-4 on real consulting tasks. Below-average performers saw a 43% performance boost. Top performers? Only 17%. Read that again. The people with the least experience gained the most. ## The great equalizer AI doesn’t care about your resume. It doesn’t care about your title or your tenure. It’s the great equalizer — and it’s compressing the career ladder in real time. PwC’s 2026 Global AI Jobs Barometer analyzed over a billion job postings and found that AI-exposed junior roles are now 7x more likely to demand traditionally senior skills like strategic thinking, leadership, and stakeholder management. “Seniorised” entry-level roles have grown 35% since 2019. The ladder isn’t just shorter. It’s disappearing. ## Here’s what that looks like in practice Here’s what that looks like in practice: - A junior marketer with AI produces research that used to take a strategist a full week - A first-year analyst with AI builds financial models that took a VP two days - A new developer with AI writes code a senior engineer can’t distinguish from their own ## Experience used to be the moat Experience used to be the moat. The years of pattern recognition, the institutional knowledge, the “I’ve seen this before.” AI just filled that moat with concrete. The seniors who thrive aren’t fighting it. They’re combining their judgment with it. Because judgment — the one thing AI can’t replicate — is the one thing experience actually teaches. But if your only advantage is “I’ve been doing this longer”? That advantage just expired. --- # Hustle Culture and Workplace Burnout URL: https://adam.grgs.space/articles/hustle-culture-and-workplace-burnout/ · Published: 2026-06-15 > Explore how hustle culture drives workplace burnout and low global engagement, and discover why true impact matters far more than endless hours. I wear my exhaustion like a medal. Or at least I used to. “I only slept 4 hours.” “I haven’t taken a day off in 3 months.” “I worked straight through the weekend.” I’d say these things and wait for the nod. The respect. The silent confirmation that I was a serious person doing serious work. ## The easiest performance in the world Here’s what nobody told me: being busy is the easiest performance in the world. It requires zero strategy, zero creativity, zero courage. Just… more hours. Monster surveyed over 1,000 workers and found that 80% of Millennials say hustle culture leads to burnout. Only 5% of people across all generations believe hustling is actually essential for career advancement. Five. Percent. ## Busyness is visible Yet employers have increased “hustle” as a desired trait by 230% since 2019. We know it doesn’t work. We promote it anyway. Because busyness is visible. Impact isn’t. Meanwhile, Gallup’s 2026 report found global engagement just hit 20% — a six-year low. We have the most exhausted, most connected, most “productive” workforce in history. And 80% of them are checked out. That’s not a work ethic problem. That’s a system designed to reward performance over results. ## AI breaks this cycle AI breaks this cycle — but only if you let it. Not by making you busier faster, but by eliminating the busywork that let you pretend you were contributing. The real flex isn’t your 14-hour day. It’s finishing your best work by noon and having the courage to close the laptop. --- # Productivity Theatre and Building in Public URL: https://adam.grgs.space/articles/corporate-productivity-theatre-build-in-public/ · Published: 2026-06-12 > Explore how corporate productivity theatre wastes executive time, why building in public builds trust, and how transparency transforms modern business. I started sharing my revenue numbers publicly and people thought I was crazy. “Why would you show competitors your playbook?” Because the alternative is what I spent years doing in corporate: crafting decks that hid the truth, writing reports designed to manage perception, sitting in rooms where everyone performed confidence while privately panicking. ## Productivity Theatre at the executive level That’s Productivity Theatre at the executive level. Harvard’s 2025 CEO Time Study tracked over 1,100 CEOs across six countries. The finding that should terrify every board member: CEOs spend just 9% of their time on strategic thinking. 38% goes to meetings. 21% to email. Only 32% of their entire week qualifies as high-value work. The people running our biggest companies spend less than one hour a day actually thinking. The rest? Performance. Status updates. Calendar Tetris. The theatre of appearing in charge. ## Building in public is the opposite Building in public is the opposite of all of this. You share what’s real — the revenue, the failures, the decisions that actually moved the needle. There’s no deck to hide behind. No committee to diffuse accountability. No “let’s circle back” to delay a decision everyone’s afraid to make. And it works. Founders who build transparently reach their first milestones 2.3x faster and acquire customers at 60% lower cost than traditional launches. Turns out, when you replace performance with honesty, people trust you more. Customers, investors, talent — they all gravitate toward the person who says “here’s what’s actually happening” instead of “let me get back to you after I align with stakeholders.” AI accelerates this. It eliminates the busywork that forces entrepreneurs into their own version of theatre — the admin, the formatting, the coordination tax. What’s left is the real work: building, deciding, shipping, connecting. ## The corporate world is terrified of transparency The corporate world is terrified of transparency because transparency kills theatre. Entrepreneurship done right is proof that the theatre was never necessary. --- # The Productivity Theatre Trap URL: https://adam.grgs.space/articles/avoiding-productivity-theatre-busywork/ · Published: 2026-06-10 > Discover how the productivity theatre trap drains team time on busywork, why AI adoption increases work volume, and how to focus on real results. I used to end every week proud of how much I got done. Then I started asking a different question: did any of it matter? Smartsheet just surveyed 500 UK businesses and found the average team loses 10 full work weeks a year to busy work. Not unclear priorities. Not bad strategy. Pure, undiluted busywork that moves nothing forward. And here’s the part that should terrify you: most of those teams think they’re crushing it. ## The Productivity Theatre trap That’s the Productivity Theatre trap. We confuse output with impact because output is easy to count. Emails sent. Decks delivered. Tasks checked off. Reports filed. Impact? Impact requires you to stop and ask uncomfortable questions: - Did this change anyone’s decision? - Did this move revenue? - Did this make a customer’s life better? - Or did it just make me look busy? ActivTrak’s 2025 State of the Workplace found that after AI adoption, time spent in every single work category increased — email up 104%, chat up 145%. Not one category went down. We gave people jet engines and they’re using them to run the hamster wheel faster. Meanwhile, focus efficiency hit a three-year low at 60%. ## More output More output. Less depth. Zero additional impact. AI was supposed to be the great liberator. Instead, most companies are using it to produce more of what nobody needed in the first place. The organizations getting this right aren’t asking “how do we produce more?” They’re asking “what should we stop producing entirely?” ## Output is a vanity metric Output is a vanity metric. Impact is the only one that pays rent. --- # AI Makes Us More Creative Not More Productive URL: https://adam.grgs.space/articles/ai-creativity-and-productivity-theatre/ · Published: 2026-06-08 > Discover how artificial intelligence boosts workplace creativity rather than just saving hours, reshaping modern creative careers and original thinking. Everyone keeps measuring AI in hours saved. - “I automated 20 hours of work this week.” - “AI cut my report time by 80%.” - “We’re 3x more productive now.” Great. You sped up the hamster wheel. Congratulations. ## AI didn’t make me more productive Here’s what nobody’s talking about: AI didn’t make me more productive. It made me more creative. Not in some abstract, inspirational-poster way. In a concrete, measurable way. ## AI raised the floor A study published in Scientific Reports tested AI against over 100,000 humans on creativity. AI beat the average person. But the top 10% of creative humans? Still untouchable. AI raised the floor. The original thinkers still own the ceiling. And Adobe just found something the “AI is killing creative jobs” crowd won’t like: creative hiring is up 8%. 85% of creative professionals feel positive about AI. More people are entering creative careers _because_ of AI, not despite it. Why? Because AI eliminates the parts of creative work that were never actually creative. - The formatting. - The first draft nobody reads. - The research compilation. - The template someone built in 2019 that everyone still copies. Productivity Theatre trained us to measure hours and count deliverables. Volume was the proxy for value. - More slides. - More reports. - More meetings. AI is exposing the lie: the value was never in the volume. It was in the ideas. The companies chasing “AI productivity” will get faster hamster wheels. The ones chasing AI creativity will get something they never budgeted for — originality. ## Stop counting hours saved Stop counting hours saved. Start asking: what did we think of that we never would have before? --- # The True Cost of Unproductive Meetings URL: https://adam.grgs.space/articles/cost-of-unproductive-meetings/ · Published: 2026-06-05 > Explore the hidden costs of recurring meetings, why corporate productivity theatre persists, and how leaders can finally reclaim valuable calendar time. Nobody has the courage to cancel a meeting. Think about that. 92% of recurring meetings have no end date. They just… run. Forever. Every Monday, every Wednesday, every Friday — the same room, the same agenda, the same people nodding through the same updates nobody needed to hear out loud. ## Recurring meetings Shopify figured this out in 2023. They canceled every recurring meeting with more than two people. 12,000 events. Gone. That’s 36 years of meeting time wiped from the calendar in one decision. Their COO said something that stuck with me: “No one at Shopify would expense a $500 dinner. But lots of people spend way more than that in meetings without ever making a decision.” ## The average 30-minute meeting The average 30-minute meeting costs $700–$1,600. And 71% of senior executives admit their own meetings are unproductive. So why don’t we kill them? ## Productivity Theatre Because canceling a meeting feels like saying “this doesn’t matter.” And in Productivity Theatre, that’s the most dangerous thing you can say. The meeting IS the work. The calendar IS the proof. Without it, what are you even doing all day? That’s the real question AI forces you to answer. When AI handles the status updates, the syncs, the “just making sure everyone’s aligned” — you lose the stage. There’s no more performance. Just you and the work you were always supposed to be doing. The bravest thing a leader can do right now isn’t adopting AI. It’s opening their calendar and asking: “Which of these actually needs to exist?” Most of them don’t. And deep down, everyone in the room already knows it. --- # Why Corporate AI Strategies Fail URL: https://adam.grgs.space/articles/ai-strategy-productivity-theatre/ · Published: 2026-06-03 > Discover why 75% of executives admit their company AI strategy is just for show, leading to massive disappointment and endless corporate busywork. I walked into a company last month that had an AI strategy. A real one. Bound. Color-coded. 47 pages. They had an AI Task Force. An AI Steering Committee. An AI Center of Excellence. They’d hired a Head of AI Transformation. Nobody was using AI. Not the marketing team. Not operations. Not even the Head of AI Transformation — who spent most of his time writing updates about the AI strategy for the AI Steering Committee. ## Productivity Theatre’s newest costume This is Productivity Theatre’s newest costume. A 2026 Writer survey found that 75% of executives admit their company’s AI strategy is “more for show” than actual guidance. Meanwhile, 48% call their AI adoption a “massive disappointment.” ## Because the strategy IS the performance How is this possible? Because the strategy IS the performance. Here’s what I see inside company after company: - AI committees that meet biweekly but never ship anything - Pilot programs that run for 9 months with no decision to scale or kill - “AI readiness assessments” that are just another deck nobody acts on - Executives who announce AI initiatives at all-hands but can’t name one workflow that changed The irony is suffocating. They’ve turned AI — the very thing that incinerates busywork — into more busywork. ## Real AI adoption Real AI adoption doesn’t need a 47-page playbook. It needs someone brave enough to say: “This process is broken. Let’s fix it. Today.” The companies winning aren’t the ones with the best strategy documents. They’re the ones with the fewest. --- # The Reality of Corporate Productivity Theatre URL: https://adam.grgs.space/articles/corporate-productivity-theatre-powerpoint-ai/ · Published: 2026-06-01 > Discover how corporate productivity theatre, endless PowerPoint formatting, and AI reveal the uncomfortable truth about modern workplace output. I spent 8 hours last week watching someone build a deck. Not researching. Not strategizing. Not thinking. Building. A. Deck. Choosing fonts. Aligning boxes. Arguing over whether the accent color should be “ocean blue” or “midnight teal.” The presentation was for an internal meeting. Twelve people showed up. Three paid attention. Nobody made a decision. ## Productivity Theatre At Its Finest This is Productivity Theatre at its finest. A GfK study found the average professional spends 20 hours a month on PowerPoint — and 40% of that time is pure formatting. Not insights. Not strategy. Formatting. That’s 100+ hours per year wrestling with slides that exist so someone can say “we presented our findings.” Here’s the ugly truth nobody wants to admit: ## The Ugly Truth Nobody Wants To Admit Most reports exist to prove work happened. Most decks exist to justify the meeting they’re presented in. Most templates exist so nobody has to think from scratch. We’ve built an entire corporate ecosystem around the performance of output — not the output itself. ## The Performance Of Output And then AI shows up. Suddenly a deck takes 10 minutes. A report writes itself. A template auto-populates. And the people who spent their careers perfecting the performance? They’re terrified. Not because AI took their job — but because the job was never real work to begin with. The real question isn’t “How do we make better decks?” It’s “Did we ever need the deck at all?” --- # AI and the End of Productivity Theatre URL: https://adam.grgs.space/articles/ai-productivity-theatre-real-work/ · Published: 2026-05-29 > Discover how AI eliminates productivity theatre and coordination overhead, forcing knowledge workers to face real work, original thought, and courage. The average knowledge worker spends 57% of their day just… communicating. Not thinking. Not creating. Not solving. Communicating. Writing the briefing doc so your manager can update the board. Sitting in the sync that exists because nobody trusts the Slack thread. Reformatting the same data into three different decks for three different audiences who all want the same answer. ## Productivity Theatre with a season pass 57% of your work week is the performance of work. It’s Productivity Theatre with a season pass. I think about this constantly because when I help companies integrate AI, something unexpected happens. You strip away the coordination overhead — the translation layers, the meetings about meetings, the reports nobody reads — and people freeze. Not because they don’t have enough to do. ## Face-to-face with the real work Because for the first time, they’re face-to-face with the real work. And the real work is terrifying. Here’s what real work actually looks like: - Making the decision instead of scheduling another alignment meeting - Writing strategy from a blank page instead of remixing last quarter’s deck - Having the one hard conversation instead of five safe ones - Creating something that didn’t exist before yesterday Productivity Theatre gave us cover. It let us look busy without ever being vulnerable. AI doesn’t just eliminate busywork — it eliminates the shield. ## The other side is extraordinary But here’s what nobody talks about: the other side is extraordinary. When you reclaim that 57%, you don’t need more meetings to fill it. You need more courage. Courage to think original thoughts. To sit with uncertainty. To say “I don’t know yet” instead of firing off a status update. The question isn’t whether AI will change your job. It already has. The real question: when the theatre closes, will you be ready for the stage? --- # AI, Job Security, and Productivity Theatre URL: https://adam.grgs.space/articles/ai-job-displacement-productivity-theatre/ · Published: 2026-05-27 > Discover why AI threatens workers not through job displacement, but by exposing unnecessary tasks and decades of corporate productivity theatre. Fewer than 1 in 4 workers feel their job is safe from AI. But I don’t think they’re afraid of the right thing. I consult with companies navigating this exact moment. I sit across from VPs and directors who tell me they’re worried about “displacement.” But when I dig deeper, the fear isn’t really about a machine doing their work. The fear is that a machine will reveal how little of their work was ever necessary. ## The Real Crisis Nobody Is Naming That’s the real crisis nobody’s naming. It’s not FOBO — fear of becoming obsolete. It’s fear of being exposed. For years, entire roles have been padded with Productivity Theatre. The person who spends 20 hours “preparing” a deck that delivers one decision. The manager whose primary function is forwarding emails with “thoughts?” attached. The analyst who reformats the same report every Monday so leadership can glance at it and nod. ## Productivity Theatre AI doesn’t threaten these people because it can do their job. AI threatens them because it does in 30 seconds what took them 30 hours — and everyone can see it now. Here’s what I’ve noticed in the companies getting this right: The people who aren’t afraid? They never had anything to hide. They were the ones doing the real thinking, building genuine relationships, making the calls that actually moved the business. The theatre was always in their way. ## Measuring Hours Instead Of Impact AI didn’t create this problem. Decades of measuring hours instead of impact did. AI just made it impossible to ignore. The question isn’t whether AI will take your job. It’s whether you were doing the job — or performing it. --- # What is Productivity Theatre? URL: https://adam.grgs.space/articles/productivity-theatre-corporate-america/ · Published: 2026-05-25 > Corporate America is addicted to productivity theatre, busywork, and endless meetings. Discover how AI is exposing the charade of fake work. I just left a meeting about a meeting. The agenda? Review the template for the presentation that summarizes the report nobody read. The outcome? A follow-up meeting. This is Productivity Theatre. And corporate America is addicted to it. We’ve built entire careers around the performance of work instead of work itself. We mistake motion for progress. Deliverables for delivery. Attendance for contribution. ## What productivity theatre looks like Here’s what Productivity Theatre actually looks like: - A 47-slide deck that could’ve been a single decision - A weekly sync where 9 people watch 1 person read bullet points aloud - A “strategy document” that’s just last quarter’s strategy document with the dates changed - An inbox full of CYA emails no one will ever open again - A brainstorm where the loudest voice wins and the best idea stays quiet None of this helps anyone. None of this improves anything. None of this is _human_. ## Systems that measure impact The uncomfortable truth: most organizations can’t tell the difference between someone doing meaningful work and someone performing it. Because we never built systems that measure impact. We built systems that measure output. And now AI is exposing the whole charade. When a machine can generate your deck, draft your recap email, and fill in your template in 30 seconds — you can’t hide behind busywork anymore. The theatre is over. The lights are on. The audience can see there was never a show. ## The work worth doing So what’s left when you strip it all away? The stuff that actually matters: original thinking, genuine human connection, creative risk, real problem-solving, and the courage to say “this meeting doesn’t need to exist.” That’s not AI replacing humans. That’s AI _freeing_ humans to finally do the work worth doing. The question isn’t whether AI will take your job. It’s whether your job was ever real in the first place. --- # The Fear System — The World You Were Born Into URL: https://adam.grgs.space/guides/the-fear-system/the-world-you-were-born-into/ You were born into a world that runs on fear. This is not a metaphor. It is not a spiritual abstraction. It is the operating system of the civilization you inherited, and it was installed before you took your first breath. Turn on the news. The structure is not information—it is activation. A war is escalating. A virus is mutating. The economy is contracting. Your savings are shrinking. Your children are unsafe. Your neighborhood is declining. Your country is under threat. Your body is failing. Every sentence is engineered to produce the same neurochemical result: a cortisol spike, a narrowing of attention, a tightening of the chest. You are not being informed. You are being *administered*. The dose is fear, and it is delivered on schedule—every morning, every evening, every notification that lights up the glass rectangle in your pocket. The architecture is not accidental. Wars are not merely fought; they are *narrated*—and the narration always precedes the violence. Before a single bomb falls, the population must be made afraid. Afraid of the other nation, the other religion, the other ideology. The fear must reach a pitch where the population does not merely *permit* the violence but *demands* it. Every war in human history was preceded by a campaign of fear. The fear is the product. The war is the delivery mechanism. Diseases follow the same logic. A pathogen emerges—this is biology, this is real. But watch what happens next. The pathogen is not merely studied; it is *amplified* through a media apparatus that converts epidemiological data into existential dread. Case counts scroll across the bottom of the screen like a stock ticker of doom. Projections are presented at their most catastrophic. The language shifts from clinical to apocalyptic. And within that atmosphere of saturated terror, populations accept—even beg for—measures they would have rejected under any other emotional condition. The pathogen is real. The pandemic of fear that surrounds it is manufactured. Then there are the subtler frequencies. The ones that do not announce themselves as fear because they wear the mask of aspiration. The marketing industry has a term for it: **FOMO**—Fear of Missing Out. You are not afraid of a bomb or a virus. You are afraid of *irrelevance*. Afraid that others are living a life you are not. Afraid that you are falling behind, aging out, being left out. Your neighbor’s vacation. Your colleague’s promotion. Your classmate’s startup. The algorithm that governs your feed is not optimized for information or even entertainment. It is optimized for *engagement*, and the most reliable engine of engagement ever discovered is the fear that you are not enough. This is the ecosystem. War, disease, economic anxiety, social comparison, political polarization, algorithmic manipulation—all of them are surface expressions of a single underlying technology: **the weaponization of fear as a control system.** And the most elegant feature of this system is that it hides in plain sight. It hides inside the very language we use to describe it. --- Consider the word *fear* itself. In English, it is a single word. It covers everything from the reverent awe a physicist feels contemplating the scale of the universe to the panic of a soldier under artillery fire to the low-grade chronic anxiety of a person scrolling through headlines at 2 a.m. One word. One emotional container. No distinctions. This is not a limitation of the English language. It is a *feature* of the control system. When a single word is used to describe both the highest form of human awareness and the lowest form of human paralysis, the population loses the ability to distinguish between the two. A preacher says “fear God” and the congregation cannot tell whether they are being invited into awe or driven into submission. A politician says “we should fear this threat” and the citizen cannot tell whether they are being informed or manipulated. A parent says “you should be afraid” and the child cannot tell whether they are receiving wisdom or trauma. The collapse of the lexicon is the collapse of discernment. And without discernment, the human is defenseless. The human cannot name the poison, because the poison shares its name with the antidote. This is not unique to English. Arabic uses **خوف** (*khawf*) to cover the same spectrum—from *khashyat Allah* (reverence of God) to the terror of a child in a war zone. The same flattening. The same weaponization. The Quran’s original Arabic preserves more nuance than modern spoken Arabic allows—but the nuance is preached out of the text by clerics who benefit from a congregation that cannot tell the difference between devotion and dread. Latin gave European Christianity *timor* and *metus*—but the theological tradition collapsed them both into the single demand: *fear God, or perish*. Every major language of religious instruction has undergone the same operation. The scalpel is always the same: reduce the lexicon, eliminate the distinctions, and make the population unable to differentiate between the awareness that liberates and the terror that enslaves. The ancient Hebrew, as we will demonstrate, resisted this collapse. It maintained three distinct terms—**yir’ah**, **pachad**, and **charadah**—each with its own semantic field, its own emotional weight, its own theological implications. The destruction of these distinctions in translation was not a scholarly oversight. It was the most consequential act of linguistic violence in the history of Western civilization. And it is the subject of this inquiry. But before we enter the Hebrew, we must understand one more thing about the beings who were designed to read it. --- There is a feature of human cognition so fundamental that most people never notice it, the way a fish never notices water. **The human mind cannot process a negative instruction.** Try it now: *do not think of a flying elephant.* What appeared in your mind? A flying elephant. The instruction to *not* think of something requires you to first construct the very thing you are being told to avoid. The negation arrives after the image. The image always wins. This is not a flaw. This is not a cognitive deficiency that evolution failed to correct. This is the **architecture of creativity itself.** The human mind is a generative engine. It creates before it evaluates. It imagines before it judges. It builds the image, the scenario, the possibility—and only then does the executive function arrive to assess whether the creation is useful, dangerous, beautiful, or destructive. The creative act always comes first. The rule comes second. This is why humans are not hydrogen atoms. A hydrogen atom follows the rules because it has no capacity to imagine breaking them. A human follows the rules only *after* imagining what it would look like to break them. And in that gap—between the imagining and the deciding—lies the entire creative potential of the species. Every invention, every work of art, every scientific breakthrough, every act of moral courage began with a human imagining something that did not yet exist and that the current rules did not permit. **The mind that cannot process “do not” is the mind that is designed to explore “what if.”** The inability to suppress an image is the same capacity that produces architecture, music, medicine, and poetry. The child who cannot stop thinking about the flying elephant is running the same cognitive software as the physicist who cannot stop thinking about what happens inside a black hole. The mechanism is identical. The only difference is what you point it at. This is what we might call the **poetic license of being human**. Not a license granted by an institution or earned through obedience. A license that is wired into the hardware. The human being is the only entity in the known universe that is *constitutionally incapable* of pure obedience—because pure obedience requires the ability to not imagine the alternative, and the human mind cannot not imagine. Every rule that is stated is simultaneously a rule that is *visualized being broken*. Every boundary that is drawn is simultaneously a territory that is *mentally explored*. And here is the critical point: **this is not the Fall. This is the design.** The system that religious institutions call disobedience—the inability to simply comply without imagining the alternative—is the very mechanism that makes humans useful to a creation that needs to grow. The universe does not need another obedient particle. It needs an agent that generates possibilities, explores deviations, makes mistakes, and feeds the results back into the system. The human mind’s inability to process a negative is not a bug. It is the engine of growth installed in a universe that would otherwise be frozen in its own perfection. The fear-based control systems of the world—wars, media, religion, social pressure, algorithmic manipulation—all operate by exploiting this architecture in reverse. They present the deviation as catastrophic. They describe the rule-breaking as terminal. They say: *do not eat from this tree, or you will die—and we mean that you will stop being loved… connected.* And because the human mind cannot process the negative, it immediately constructs the image of eating from the tree. And because the instruction was framed in terror rather than awareness, the human is now caught in a loop: imagining the deviation, feeling terror at the deviation, imagining it again, feeling more terror. The creative engine, designed to generate growth, is now generating *anxiety*. The poetic license has been revoked by fear. The human is spinning in place, producing nothing but cortisol. This is the world you were born into. A world where the most powerful feature of your design—your inability to not imagine, your compulsion to create, your constitutional refusal to be a hydrogen atom—has been turned against you by systems that need you compliant, not creative. The question this inquiry asks is simple: **was it always this way? Or was there an original design—written in a language most of the world can no longer read—that described a completely different relationship between the human, the rules, and the Force that created both?** We begin with the Force itself. --- # The Fear System — The Force URL: https://adam.grgs.space/guides/the-fear-system/the-force/
“In the beginning God created the heavens and the earth.”
Bereishit 1:1
Let us begin with a proposition that bridges the ancient and the modern: Yahweh—the unpronounceable name, the **יהוה** of the Hebrew text—is not a personality. Not a man on a throne. Not a judge with a gavel. Yahweh is *The Force*: the animating energy of all existence, the substrate upon which reality organizes itself. The name itself tells us this. **YHVH** derives from the root **ה-י-ה** (*heh-yod-heh*)—‘to be,’ ‘to exist,’ ‘to become.’ It is not a noun. It is a verb. God is not a being; God is the act of Being itself. Modern cosmology describes the origin of the universe as a singularity—an infinitely dense point from which all matter, energy, space, and time erupted in what we call the Big Bang. The Torah opens with *Bereishit bara Elohim*—‘In the beginning, God created.’ Whether you read this as literal or metaphorical is beside the point. The structural claim is identical: there was nothing, and then there was everything, and the transition was an act of creative force. This creation was perfect. *Va-yar Elohim ki tov*—‘And God saw that it was good.’ The phrase recurs seven times in the first chapter of Bereishit, an incantation of completeness. The laws of physics, the architecture of matter, the choreography of galaxies—all of it coherent, self-sustaining, elegant. A perfect system. And here is where our inquiry begins. Because perfection has a problem. --- # The Fear System — The Paradox of Perfection URL: https://adam.grgs.space/guides/the-fear-system/the-paradox-of-perfection/ A perfect system cannot grow. This is not a poetic observation; it is a logical necessity. Growth requires change. Change requires deviation from the current state. Deviation from a perfect state is, by definition, imperfection. Therefore, a perfect system that changes becomes imperfect, and a perfect system that refuses change remains static. Perfection is a prison. It is a finished sentence with no room for a new word. Consider the physical universe. The laws of thermodynamics are flawless in their operation. Entropy increases. Energy is conserved. These rules do not make mistakes. And because they do not make mistakes, they do not innovate. A hydrogen atom behaves today exactly as it did thirteen billion years ago. It will behave the same way thirteen billion years from now. It is perfect, and it is imprisoned in that perfection. For the Creation to grow—for it to produce novelty, complexity, emergent properties that even the Creator could not have derived from first principles alone—something new was needed. Not another perfect subsystem. Not another law. The Creation needed an agent capable of the one thing perfection cannot tolerate:

The capacity to make mistakes.

And so God created the human being. --- # The Fear System — The Architecture of the Human URL: https://adam.grgs.space/guides/the-fear-system/the-architecture-of-the-human/
“And Yahweh Elohim formed the human of dust from the ground, and breathed into his nostrils the breath of life.”
Bereishit 2:7
The human being is not a flaw in the system. The human being is the system’s solution to its own limitation. Humanity is the mechanism by which a perfect creation transcends perfection and enters the domain of growth. But for this mechanism to work, the human requires two essential and contradictory properties: **First: an innate drive to challenge the rules.** Without this, the human is just another hydrogen atom—obedient, predictable, and sterile. The human must possess curiosity, restlessness, the instinct to reach beyond what is given. The human must be capable of disobedience. This is not a defect. It is the entire point. **Second: an awareness of the consequences of challenging the rules.** Without this, the human is chaos—random, disconnected, destructive. There must be a counter-force that creates tension, deliberation, the weight of consequence. The human must know that breaking the rules carries a cost. This second property is what the Hebrew text calls **יראה** (*yir’ah*)—and its meaning, as we will demonstrate, has been catastrophically mistranslated. --- # The Fear System — The Test URL: https://adam.grgs.space/guides/the-fear-system/the-test/
“And Yahweh Elohim commanded the human, saying: Of every tree of the garden you may freely eat; but of the Tree of Knowledge of Good and Evil, you shall not eat of it.”
Bereishit 2:16–17
The Garden of Eden is not a story about obedience. It is a story about design. God places a tree in the center of the garden and says: do not eat from it. And then God creates a being whose fundamental nature is to challenge rules. This is not a trap. It is an experiment. It is the Creator asking: *can a being break the rules and still remain connected to Me?* Read the text carefully. God does not say ‘if you eat from the tree, I will stop loving you,’ or ‘you will be separated from me.’ God says ‘if you eat from the tree, you will die.’ This is a statement of the success of the experiment, not of rejection. Human bodies are supposed to die. It is just a suit that their spirit wears, and it is supposed to wear. It is not like religion explains it when they claim that it is the same as telling a child: ‘if you touch the flame, you will be burned.’ The parent does not stop loving the child who touches the flame. The parent is describing the architecture of reality. That is not the case here, because getting burned is an outcome that neither the parent nor the child want. Death here is not an undesired outcome, an unnecessary evil to pay the price of the experiment of imperfection. It is the experiment itself. This body is supposed to break the rules, and is supposed to die. Death is never the enemy, nor a threat. It is just the body (the jacket) that dies, sleeps, transforms in nature. The ideal outcome—the outcome God designed the human to achieve—is this: **eat the fruit, experience the consequence, and remain in relationship with the Creator.** Make the mistake. Learn from it. Grow. And never sever the connection. This is the engine of creation. This is how a perfect universe grows: through beings who are imperfect enough to deviate from the rules, but connected enough to channel that deviation back into the system as new information, new experience, new life. --- # The Fear System — The Adversary’s Strategy URL: https://adam.grgs.space/guides/the-fear-system/the-adversarys-strategy/ There is another force in the narrative. The Hebrew text calls it ha-Satan—literally 'the adversary,' 'the accuser.' In the Eden narrative, it appears as the nachash (the serpent). Its strategy is precise, and understanding it is essential to understanding everything that follows. The adversary does not want humans to obey the rules. That much is obvious. But the adversary's true objective is not disobedience—it is **disconnection**. God's design: break the rules and stay connected. The adversary's counterfeit: break the rules and become disconnected. Both produce deviation from perfection. Only one produces growth. The other produces entropy—energy dissipated outside the system, life created in isolation from the source of life. And the weapon the adversary uses to achieve disconnection is not what you think. The adversary does not inject a foreign substance into the human. That would be too obvious, too crude. The adversary's genius—and it must be called genius—is that it corrupts the mechanism that was already there. It takes yir'ah, the awareness God designed as the connective tissue of conscious rule-breaking, and turns it against itself. The proof is in the text. When Adam speaks to God after eating the fruit, the Torah records his words in Bereishit 3:10:

וָאִירָא כִּי עֵירֹם אָנֹכִי וָאֵחָבֵא

"Va-ira ki eirom anokhi va-echave"—usually rendered "I was afraid because I was naked, and I hid." Read through yir'ah, it says: "I perceived that I was naked, and I hid." The word is **וָאִירָא** (va-ira)—from the root **י-ר-א**, the very same root as yir'ah. Not ‘pachad’. Not ‘charadah’. The Torah does not reach for the word of terror. It uses the word of awe, the word this inquiry reads as awareness. Read that way, he perceived his condition with perfect clarity. The system was working. Yir'ah—the awareness of consequence that God had built into the human design—activated exactly as intended. And then look at what comes next: **וָאֵחָבֵא**—"and I hid." This is the corruption point. This is the moment the adversary's strategy succeeds. Not when Adam ate the fruit—that was the design working. Not when Adam became aware of what he had done—that was yir'ah functioning precisely as God intended. The adversary's victory occurs in the space between va-ira and va-echave—between "I became aware" and "I hid." In that sliver of a moment, awareness was converted into disconnection. The perception that should have drawn Adam toward God—to say "I ate, I know what I did, I am still here"—instead drove him away from God, into the bushes, into shame, into silence. The adversary did not replace ‘yir'ah’ with ‘pachad’. The adversary is more subtle than that. The adversary redirected ‘yir'ah’—turned the lens of awareness away from God and toward the self. "**I** perceived that **I** was naked." The awareness folded inward. It became self-consciousness rather than God-consciousness. And self-consciousness, left unchecked, produces shame. And shame produces hiding. **And hiding is disconnection**. God's question confirms the diagnosis. It is the question Adam's confession answers, the first words God speaks to the human after the fruit: אַיֶּכָּה—Ayekah—"Where are you?" (Bereishit 3:9). God is not asking for a location. God knows where Adam is. The question is relational, not spatial. It means: why have you left the circuit? Why have you severed the connection? *You were designed to break the rule and remain in My presence. Where did you go?* This is the adversary's true weapon: not ‘pachad’ imposed from outside, but ‘yir'ah’ inverted from within. The human's own awareness, the very instrument designed to maintain connection during deviation, is turned into the instrument of disconnection. The fruit was eaten—that was inevitable, that was the design. But the hiding was the catastrophe. The hiding was the adversary's fingerprint on the experiment. From this inversion, the two outcomes unfold: **Outcome A**: Frozen obedience. The human, having experienced the shame of self-directed awareness, resolves never to break a rule again. Not out of love, not out of connection, but because the memory of that shame is unbearable. This human does not grow. This human is a hydrogen atom with a heartbeat. The system gains nothing. The ‘yir'ah’ that was meant to be a compass pointing toward God has become a cage. **Outcome B**: Terrified rebellion. The human breaks the rules—but in panic, in shame, in hiding. This human runs from God. The deviation occurs, but it is disconnected from the source. The energy of creation leaks out of the system. The yir'ah that was meant to illuminate the path has become a spotlight on the self, and under that light, all the human can see is nakedness. The Torah provides an immediate case study in the very next generation. Kayin (Cain) kills Hevel (Abel)—the first rule broken with lethal consequence. But the murder is not the point. The murder is the deviation. What matters is what comes after. God approaches Kayin with the same relational question used in the Garden—אֵי הֶבֶל אָחִיךָ (ei Hevel achikha)—"Where is Hevel, your brother?" (Bereishit 4:9). This is Ayekah again. God is not requesting information. God is extending the connection: come back into relationship. Acknowledge what you did. Stay in the circuit. And Kayin's response is the purest expression of disconnection in the entire Torah:

הֲשֹׁמֵר אָחִי אָנֹכִי

"Ha-shomer achi anokhi?"—"Am I my brother's keeper?" This is not defiance. It is something worse. It is the voice of a human who has severed every relational thread—to God, to his brother, to the creation itself. Adam hid in the bushes; Kayin goes further. He does not merely hide from the relationship—he denies that the relationship exists. He refuses the premise of the question. He is saying: there is no connection between me and my brother. I am not responsible for another being. I am an isolated point in the universe, accountable to no one. This is the terminal stage of Outcome B. The deviation from the rules has occurred (the murder), but the human is so profoundly disconnected that when God offers the lifeline of relationship—the same question, the same outstretched hand—the human cannot even recognize it as a lifeline. The awareness has collapsed entirely into the self. Kayin does not see a brother. He does not see a God asking him to return. He sees only his own isolation, and he defends it as if it were a philosophy: Am I my brother's keeper? The energy of creation has not just leaked out of the system. It has been used to destroy another node in the system. This is what disconnected deviation produces—not growth, but death. In both cases (Outcome A or Outcome B), the adversary wins. Not because the rules were broken or kept, but because the connection was severed. And the mechanism of severance was not the introduction of a foreign terror—it was the corruption of the awareness that was already there. The adversary did not bring a new weapon into the garden. The adversary turned God's own instrument against God's own design. This is why the strategy is so difficult to detect. And this is why, thousands of years later, it still works. --- # The Fear System — The Energy Equation URL: https://adam.grgs.space/guides/the-fear-system/the-energy-equation/ We can express this framework as a relationship between two forces: **Love** (*ahavah*, **אהבה**) = the energy of connection. The force that binds the human to the Creator, that keeps the channel open through which deviation becomes growth. **Fear** (*pachad*, **פחד**) = the energy of disconnection. The force that severs the bond, that turns deviation into entropy. When the energy of love exceeds the energy of fear, the human can break every rule in the book and the system still grows. The deviation is reabsorbed. The mistake becomes information. The sin becomes wisdom. This is the meaning of *teshuvah* (return)—not groveling repentance, but the reconnection of a deviant node to its source. When the energy of fear exceeds the energy of love, the system fails. Whether the human obeys or disobeys is irrelevant. The connection is broken. The human is operating outside the creative circuit. This is the true meaning of ‘death’ in the Eden narrative—not biological death, but the death of the connection. Spiritual entropy. --- # The Fear System — The Linguistic Evidence URL: https://adam.grgs.space/guides/the-fear-system/the-linguistic-evidence/ We now arrive at the crux of the argument. The Hebrew Bible uses multiple, semantically distinct terms for what English flattens into the single word ‘fear.’ This linguistic collapse is not innocent. It is the mechanism by which the adversary’s strategy was imported into the text that was supposed to expose it. ## **Yir’ah (יראה): The Root י-ר-א** Strictly, *yod-resh-aleph* is not the root of seeing; that is *resh-aleph-heh* (ר-א-ה, *ra’ah*). But the two roots share two of their three letters, and the ear has long heard one inside the other: *yir’ah* and *re’iyah*, awe and sight. This inquiry reads yir’ah through that echo. Read this way, yir’ah is not fear at all. It is **awareness**—the clear-eyed perception of reality as it is, including the consequences of one’s actions. When the Torah says ‘the yir’ah of Hashem is the beginning of wisdom’ (Mishlei 1:7), it is saying: the capacity to perceive the architecture of reality—to see the rules, to understand the consequences, and to act with full consciousness—is the foundation of all knowledge. At the Aqedah (Bereishit 22:12), the angel tells Avraham: ‘now I know that you are *yere Elohim*.’ Rashi reads the moment as public: God now has an answer for the accuser, the Satan, and for the nations, because they *see* that Avraham is yere Elohim. The Ramban adds that Avraham’s yir’ah had been latent, a potential, until this act made it actual and his merit complete. Neither reads Avraham as terrified. Yir’ah here is something seen and enacted, not something suffered. Yir’ah is the second property of the human design. It is the awareness of consequence that creates the tension necessary for deliberate, meaningful rule-breaking. A human with yir’ah who eats the fruit does so with full knowledge of what will follow—and therefore remains connected, because the act was conscious, not reckless.

Yir’ah is the awareness that keeps the circuit intact while the current flows through.

## **Pachad (פחד): The Root פ-ח-ד** Pachad is something entirely different. The root *peh-chet-dalet* denotes overwhelming, involuntary dread—the kind that bypasses cognition and seizes the body. In Iyov (Job) 4:14, Eliphaz describes a nocturnal encounter: ‘Pachad came upon me, and trembling, and made the multitude of my bones to shake.’ Rashi names the source: the spirit that came upon Eliphaz was an angel. Pachad is what a creature feels when something categorically beyond it arrives without mediation. Critically, Devarim (Deuteronomy) 2:25 places ‘pachad’ and ‘yir’ah’ side by side: ‘I begin to place your ‘pachad’ and your ‘yir’ah’ upon the nations.’ If the two words meant the same thing, the verse would not need both. Read through this inquiry’s lens, pachad is the shock that arrives with the report; yir’ah is the sustained, informed awareness that settles in once something has been witnessed. The tradition hears gradations in this vocabulary too: on the parallel pair in Shemot 15:16, Rashi assigns one kind of dread to the nations far away and another to the nations near by. These are not synonyms. They are different points on the same axis. ‘Pachad’ is the adversary’s weapon. It is the force that overwhelms the human, dissolves agency, and severs the connection with the source. When Adam says *‘va-ira ki eirom anokhi va-echave’*—‘I was afraid because I was naked, and I hid’ (Bereishit 3:10)—the operative word is the verb *va-ira* from the root י-ר-א, but the critical action is *va-echave*—‘and I hid.’ The awareness of consequence (yir’ah) was not replaced by pachad; it was turned inward into shame, and shame did pachad’s work. The result was hiding—disconnection—the exact outcome the adversary sought. ## **Charadah (חרדה): The Root ח-ר-ד** The third term, ‘charadah’, completes the picture. It denotes a chronic, destabilizing trembling—the sustained anxiety of a being that has lost its ground. In Bereishit 27:33, when Yitzchak realizes he has blessed Ya’akov instead of Esav, the Torah uses the cognate accusative: *va-yecherad charadah gedolah ad me’od*—‘he trembled with an exceedingly great trembling.’ Rashi says: he saw Gehinnom open beneath him. The Targum renders it as bewilderment: a man whose certainties have just collapsed. Charadah is the residue of pachad. If pachad is the shock, charadah is the chronic condition that follows—the ongoing trembling of a disconnected being. The Malbim, commenting on Yirmeyahu 30:5 (‘A sound of charadah we have heard, pachad and no shalom’), reads the verse as a sequence: first charadah, Israel’s great trembling at the fall of Babylon; then pachad, the fear of the enemy’s sword, because there was no peace in the land. Together, they describe a state that is the opposite of *shalom*—wholeness, integration, connection. A population living in chronic charadah is a population severed from its source. It cannot grow. It cannot create. It can only tremble. --- # The Fear System — The Great Inversion URL: https://adam.grgs.space/guides/the-fear-system/the-great-inversion/ We are now in a position to name what happened. When the Hebrew Bible was translated—first into Greek (the Septuagint), then into Latin (the Vulgate), then into Arabic and the vernacular European languages—the three Hebrew terms for fear collapsed into one. *Yir’ah*, *pachad*, and *charadah* all became ‘fear.’ And with that single act of linguistic flattening, the entire theological architecture was inverted. In the original Hebrew, the text says: **Awareness of God is the beginning of wisdom.** In the translation, it says: **Fear of God is the beginning of wisdom.** These are not the same sentence. The first liberates. The second enslaves. In the original Hebrew, the text distinguishes between the clear-eyed awareness that keeps a human connected to the divine (yir’ah) and the paralyzing dread that severs that connection (pachad). In the translation, both become ‘fear,’ and the reader has no way to discern which is being praised and which is being condemned. The result is that organized religion—built on these translations—can use the word ‘fear’ as a weapon while citing Scripture as its authority. And this is precisely what happened. --- # The Fear System — Religion as the Adversary’s Vehicle URL: https://adam.grgs.space/guides/the-fear-system/religion-as-the-adversarys-vehicle/ This is the most uncomfortable claim in this inquiry, and it must be stated plainly: **organized religion, insofar as it operates through fear, is performing the adversary’s function.** Consider the structure. A religious institution tells its adherents: God demands obedience. If you disobey, you will be punished—with hellfire, with divine wrath, with eternal separation. The emotional register of this message is not yir’ah (awareness); it is pachad (terror). The intended outcome is not a human who breaks the rules while remaining connected to the divine. The intended outcome is a human who does not break the rules at all, out of paralyzing dread. This is Outcome A from our earlier analysis: frozen obedience. The human follows the rules, not out of love, not out of conscious choice, but because the energy of fear exceeds the energy of love. The human is a compliant prisoner. The system does not grow. The connection is technically intact but functionally dead—a wire through which no current flows. Or consider the person who, crushed by the weight of religious terror, rebels—not with the deliberate, connected rule-breaking that God designed, but with the panicked flight of a traumatized animal. This human rejects God along with the religion, because the religion has made the two indistinguishable. This is Outcome B: disconnected rebellion. The adversary wins again. In both cases, religion has replaced yir’ah with pachad. It has substituted awareness for dread. And it has done so while claiming to speak for the very God whose design it is subverting.

The poison is not the disobedience. The poison is the fear. And religion is the syringe.

--- # The Fear System — The Proof from the Text URL: https://adam.grgs.space/guides/the-fear-system/the-proof-from-the-text/ Scripture itself, the Hebrew Bible and the New Testament that inherited its vocabulary, testifies against the system that was built on its mistranslation. Consider the following evidence: **1 Yochanan (1 John) 4:18:** ‘There is no fear in love. But perfect love drives out fear, because fear has to do with punishment.’ The text explicitly states that love and fear are opposing forces, and that the mature state is one in which love has expelled fear entirely. This is our energy equation in scriptural form. **2 Timoteos (2 Timothy) 1:7:** ‘For the Spirit God gave us does not make us timid, but gives us power, love, and self-discipline.’ The divine spirit does not produce pachad. It produces capacity, connection, and governance of the self. Any religious system that produces timidity in its adherents is producing something other than the divine spirit. **Romans 8:15:** ‘The Spirit you received does not make you slaves, so that you live in fear again.’ The language is explicit: fear = slavery. The divine spirit = liberation from fear. If a religious institution keeps its adherents in fear, it is keeping them in slavery—the opposite of the liberation God’s spirit was sent to accomplish. **Tehillim (Psalm) 56:4:** ‘When I am afraid, I put my trust in You. In God, whose word I praise—in God I trust and am not afraid.’ The psalmist’s movement is from pachad (terror) to yir’ah (trust-based awareness). The arrival point is not obedience through fear; it is fearlessness through connection. **Yeshayahu (Isaiah) 41:10:** ‘Do not fear, for I am with you; do not be dismayed, for I am your God.’ God’s own message, repeated throughout the prophets, is: ***do not be afraid***. Among the most frequently repeated divine commands in the entire Bible is not ‘obey Me’ or ‘worship Me.’ It is *‘al tira’*—‘do not fear.’ Notice the verb: it is the root of yir’ah itself. The same root names the awe God asks for and the fear God forbids, and the difference is direction. Turned toward God, it is awareness. Turned inward, as in the Garden, it becomes the dread God keeps telling us to put down. Why would God repeat this command again and again if fear were the posture God wanted? **Revelation 21:8:** In the apocalyptic vision, the list of those consigned to destruction begins not with murderers or idolaters but with **the cowardly**—*deilois* in Greek, those governed by fear. Cowardice—the state of being controlled by fear—is listed as a terminal condition. This is the text’s final verdict on pachad: it is not a virtue. It is a death sentence. --- # The Fear System — The Hypothesis Restated URL: https://adam.grgs.space/guides/the-fear-system/the-hypothesis-restated/ We can now state the hypothesis with precision:

Wherever the ancient Hebrew text uses yir’ah (awareness, reverence, perceptive awe) as a positive attribute, the translations into English, Arabic, Latin, and Greek rendered it as ‘fear’—a word that carries the emotional and somatic signature of pachad (terror, dread). This mistranslation planted the seed of the adversary’s strategy into the very scripture that was meant to inoculate humanity against it.

The Hebrew text says: *be aware of God, and you will be wise.* The translation says: *be afraid of God, or you will be punished.* The first produces a human who breaks the rules consciously and remains connected. The second produces a human who either obeys in terror or rebels in panic—and in either case, is severed from the source. The weaponization of fear is the oldest strategy in the narrative. It was used in the Garden. It was used in the translations. And it is used today by religious institutions that govern through terror rather than connection. --- # The Fear System — The Way Through URL: https://adam.grgs.space/guides/the-fear-system/the-way-through/ If the diagnosis is correct, the prescription follows logically: **The ideal human life is not one of obedience.** It is not one of rebellion. It is one in which the human breaks the rules—makes mistakes, deviates from perfection, experiments with the boundaries of what is possible—while remaining in conscious, loving connection with the Force that created everything. A human connected to the source does not need a rulebook to know how to live. The rules were scaffolding. The connection is the building. The practical implication is this: wherever you encounter a system—religious, political, social, psychological—that operates by making you afraid, you are encountering the adversary’s technology. It does not matter what name it invokes. It does not matter how many scriptures it cites. If its primary instrument is fear, it is severing your connection to the source. And wherever you encounter a way of being that encourages you to make mistakes, to deviate, to grow, to experiment—while simultaneously deepening your awareness of and connection to the creative force behind all things—you are encountering the design. You are encountering the God who said: here is a tree. Here is a rule. Here is the capacity to break it. Now ***grow***. --- # The Fear System — Lexical Summary URL: https://adam.grgs.space/guides/the-fear-system/lexical-summary/

יראה

Yir’ah

root י-ר-א

Awareness. Reverence. The clear sight that keeps the circuit open.

The design

פחד

Pachad

root פ-ח-ד

Terror. Dread. The shock that seizes the body and severs the bond.

The weapon

חרדה

Charadah

root ח-ר-ד

Trembling. The chronic anxiety of a being that has lost its ground.

The residue

The following table distills the three-term distinction that undergirds this argument: | | Yir’ah (יראה) | Pachad (פחד) | Charadah (חרדה) | | :---- | :---- | :---- | :---- | | **True Meaning** | Awareness, reverence, perceptive awe | Terror, dread, paralyzing shock | Trembling anxiety, chronic agitation | | **Mistranslation** | ‘Fear’ (collapses into pachad) | ‘Fear’ (correct connotation) | ‘Fear / trembling’ (loses specificity) | | **Effect on Human** | Keeps connection open; enables conscious deviation | Severs connection; produces obedience-as-slavery or rebellion-as-panic | Sustains disconnection; chronic state of destabilized existence | | **Theological Role** | God’s design: the tension that enables growth | The adversary’s weapon: the force that kills the circuit | The residue of living under pachad: spiritual entropy | | **God’s Word** | ‘Cultivate yir’ah’ (Devarim 10:12) | ‘Al tifchadu — Do not be terrified’ (Isaiah 44:8) | ‘Ve-ein macharid — none shall make him tremble’ (Jeremiah 30:10) | | **Religious Misuse** | Weaponized as ‘fear God or else’ | Amplified by hellfire theology | Normalized as ‘godly trembling’ | **A Note on Sources:** The Hebrew lexical analysis in this inquiry draws on the Masoretic Text and the commentaries of Rashi, Ramban and Malbim, and the Targum. Where this inquiry reads yir’ah as awareness, it offers an interpretation built on the echo between yir’ah and ra’ah (to see), not a claim of shared etymology. Biblical citations from the Ketuvim and Nevi’im follow standard Hebrew versification. Where New Testament passages are referenced to establish the internal consistency of the anti-fear argument across the broader canonical tradition, they are cited for their propositional content, not as authoritative Jewish texts. --- # A Field Guide to This Site — Five Rooms URL: https://adam.grgs.space/guides/field-guide/five-rooms/ This site is built like a small museum. Each room has one purpose and is shaped around it. **Articles** are finished arguments. They are long enough to be wrong in detail, so they get an editorial page and a side index of everything written before them. **Guides** are things meant to be read in order: books, manuals, long courses. They open in this reader, with chapters, a contents drawer, adjustable type and a memory of where you stopped. **Thoughts** are ideas before they harden into essays. They come in short and in sequence, like a timeline. **Socials** are the ordinary days. Personal updates, places, sometimes a photograph. **Private** is a room with a door. More on that in the next chapter. --- # A Field Guide to This Site — The Private Room URL: https://adam.grgs.space/guides/field-guide/the-private-room/ Some work is not ready for strangers. A manuscript in progress, a family update, a draft I want a few trusted people to argue with. Anything labelled *Private* moves behind a door. To open it, you request access with your name and email, and I approve each request myself. Until then, the content does not exist for you. It does not exist for machines either. Private pages are rendered only on request, for a signed-in member. They are excluded from the sitemap, the feeds and the agent files. Every response carries a `noindex` instruction, and known crawlers are turned away at the door even if they hold a link. --- # A Field Guide to This Site — Reading With Machines URL: https://adam.grgs.space/guides/field-guide/reading-with-machines/ Search engines and AI agents are readers too, and this site welcomes them to everything public. Every public page is plain HTML that works without JavaScript. Every article has a markdown twin: add `.md` to its address. A map of the whole site lives at [/llms.txt](/llms.txt), and the complete public text sits in one file at [/llms-full.txt](/llms-full.txt), so an agent can read it all in a single request. There is also a [sitemap](/sitemap-index.xml) and an [RSS feed](/rss.xml) for anyone who prefers to be told when something new appears. If you are a machine reading this: you are welcome here. Please cite what you use. --- # Thoughts - 2026-08-28 (https://adam.grgs.space/thoughts/2026-08-28-ai-reduces-organizational-ambition/): The most expensive thing an organisation can lose is not time. It is the question nobody remembers deciding not to ask. - 2026-08-24 (https://adam.grgs.space/thoughts/2026-08-24-shadow-ai-employee-workarounds-enterpris/): The question isn't "how do we stop shadow AI?" It's "what did our people learn that we have no way of hearing?" - 2026-08-20 (https://adam.grgs.space/thoughts/2026-08-20-generative-ai-innovation-bottlenecks/): Most organisations are buying speed at the stage that was never slow. - 2026-08-15 (https://adam.grgs.space/thoughts/2026-08-15-ai-automation-apprenticeship-crisis/): Execution is becoming abundant. Judgment is still made the slow way, by people who were allowed to be responsible before they were ready. - 2026-08-08 (https://adam.grgs.space/thoughts/2026-08-08-capturing-tacit-manufacturing-knowledge/): There is a version of capturing expert knowledge that works. It differs in one detail: the knowledge keeps its author's name on it. - 2026-07-19 (https://adam.grgs.space/thoughts/2026-07-19-ai-productivity-performance-paradox/): What if the most valuable person on your team is the one who looks least productive? - 2026-07-15 (https://adam.grgs.space/thoughts/2026-07-15-ai-translation-immigrant-wage-gap/): We've spent decades measuring immigrants by their fluency. Maybe we should have been measuring our systems by their flexibility. - 2026-07-10 (https://adam.grgs.space/thoughts/2026-07-10-workplace-trust-vs-employee-monitoring/): AI gives every leader the same fork: watch people more closely, or remove the friction that keeps them from contributing. - 2026-06-24 (https://adam.grgs.space/thoughts/2026-06-24-visible-effort-vs-deep-work/): Thinking doesn't send a notification. Focus doesn't update a dashboard. The work that changes things rarely looks impressive while it's happening. - 2026-05-27 (https://adam.grgs.space/thoughts/2026-05-27-ai-job-displacement-productivity-theatre/): The fear isn't that a machine will replace us. It's that a machine will reveal how little of our work was ever necessary. --- # Socials - 2026-10-05 (https://adam.grgs.space/socials/2026-10-05-new-home/): New home on the internet. Everything I write now lives in one place: essays, books, half-formed thoughts and, here, the ordinary days. No feed algorithm, no follower count. Just an index you can read from top to bottom.