<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Marcin Treder — Blog</title>
    <link>https://treder.design/blog</link>
    <atom:link href="https://treder.design/rss.xml" rel="self" type="application/rss+xml" />
    <description>Marcin Treder — Director of UX, Product &amp; Strategy at Google Play, founding CEO of UXPin, and author of The AI Handbook for Product Design.</description>
    <language>en-us</language>
    <copyright>Copyright 2026 Marcin Treder</copyright>
    <managingEditor>Marcin Treder</managingEditor>
    <lastBuildDate>Sun, 02 Aug 2026 22:21:40 GMT</lastBuildDate>
    <item>
      <title>Five Chapters In!</title>
      <link>https://treder.design/blog/five-chapters-in</link>
      <guid isPermaLink="true">https://treder.design/blog/five-chapters-in</guid>
      <pubDate>Sun, 02 Aug 2026 22:21:40 GMT</pubDate>
      <category>Book note</category>
      <description>Last week I sent the first five chapters of my book Apress. The working title: The AI Handbook for Product Design; I don&apos;t love it yet... but we shall see – I may change my mind, or come up with a better title.</description>
      <content:encoded><![CDATA[<p>Last week I sent the first five chapters of my book Apress. The working title: The AI Handbook for Product Design; I don&#39;t love it yet... but we shall see – I may change my mind, or come up with a better title. My contract asked for three chapters by July 24, but I wrote five. While exploring the depths of AI theory and history, I concluded that Part 1 only holds together as a complete arc, and stopping in the middle of it would have handed my editor a story without an ending. Also... I was just too excited to stop, and to afraid that without the complete narrative it&#39;s hard to see where I am going. So here we are. 5 chapters are done. </p>
<p>What is my book about? It is a guide for designers, product managers, and technologists who want to build the next generation of AI-powered software. Part 1 is about how intelligence became computable in the first place. I wanted the foundation to feel complete, interesting, and intellectually challenging. </p>
<p>Chapter 1 asks what intelligence actually is, and takes the question seriously enough to go back to Aristotle, then to the long argument between Descartes and Locke about where knowledge comes from, then to Kant, Piaget, and Friston. It took me back to my roots in Philosophy and Psychology – I happen to have degrees in both. The chapter ends on a working definition that carries the rest of the book: intelligence is the ability to compress experience into models that predict well enough to support effective action in a changing world.</p>
<p>The next four chapters follow that idea as it turns into machinery. Chapter 2 covers classical machine learning, from Rosenblatt&#39;s perceptron through the first AI winter to the algorithms that quietly powered the first generation of intelligent products. Chapter 3 is about deep learning and the moment machines stopped needing humans to tell them what to look at. Chapter 4 covers transformers and language models, including the property I consider the most important and most dangerous thing a designer can know about them, which is that a model is exactly as articulate when it is wrong as when it is right. Chapter 5 is about diffusion models and the shift from recognition to creation.</p>
<p>The content in each chapter is written from a very particular angle – I want designers, researchers and product managers to really understand the underlying concepts and being able to apply them in practice. This led me to two writing rules. </p>
<p>The first is that every technical concept has to earn a design implication. If I explain attention or latent space or the bias-variance tradeoff and cannot tell you what it changes about the interface you are building on Monday, the section does not belong in the book. Each chapter now mints a small number of named design principles, and they accumulate across Part 1 into a set you can carry into Part 2.</p>
<p>The second is that I refused to skip the math. Yep, it may be the first UX and product book that is filled with math. I&#39;m taking some risks here. You do not necessarily have to have a deep understanding of linear algebra, and calculus to read the book, but you&#39;ll see the mathematical foundation of AI, and hopefully, grasp how all the concepts fit together. </p>
<p>Part 2 is next, and it moves from how AI works to how you design with it: retrieval, reasoning, multimodal interfaces, and agents. I will keep writing about it here as I go.</p>
]]></content:encoded>
    <item>
      <title>Augmented Intelligence</title>
      <link>https://treder.design/blog/augmented-intelligence</link>
      <guid isPermaLink="true">https://treder.design/blog/augmented-intelligence</guid>
      <pubDate>Sun, 26 Jul 2026 17:10:28 GMT</pubDate>
      <category>Essay</category>
      <content:encoded><![CDATA[<h2>From a Website Redesign to AI Displacement</h2>
<p>Back in 2019, I worked on a complete redesign of my personal website. Coming up with the design language and my personal brand was a lot of fun. Coding it, however, was a mixed bag. There were great moments (I have always loved writing React), but also tedious chores like wrangling build configurations to deploy to Netlify. All in all, it took a few weeks of after-hours work.</p>
<p>Fast forward to last weekend: I decided to refresh the site, refactor the codebase, add a newsletter, launch a blog with a custom admin panel, and build a dedicated landing page for my upcoming book. The entire process took less than two hours. Between visual changes steered via Claude Design, and execution and deployment handled by Claude Code, it felt effortless. I was freed up to focus entirely on quality, direction, and steering the features I needed.</p>
<p>Weeks of work compressed into hours. It felt incredible, and a little unnerving. </p>
<p>Like many of us in tech, I occasionally worry about AI displacing human labor. After all, tasks I used to perform manually are now executed by a machine in seconds. But that perspective misses the point. My entire job was not replaced; specific tasks were automated. In reality, I became augmented by the machine. That realization pushed me to look past the hype and dig into the history of human-computer interaction, as well as the current data on AI job displacement.</p>
<h2>A Time Study from 1957</h2>
<p>In the spring and summer of 1957, <a href="https://worrydream.com/refs/Licklider_1960_-_Man-Computer_Symbiosis.pdf">J.C.R. Licklider</a> kept a meticulous log of his own workday. As a psychoacoustician managing research at Bolt Beranek and Newman, he wanted to see where his intellectual energy actually went. Lacking a better subject, he chose himself. </p>
<p>To his surprise, roughly 85 percent of what he considered thinking time was spent simply getting into a position to think: tracking down references, plotting graphs, explaining to assistants how to plot them, or spending hours reconciling experiments measured on different scales. Once the numbers were standardized, arriving at the actual insight took seconds.</p>
<p>His most striking observation is one I keep returning to. Licklider admitted that his choices about which scientific problems to pursue were shaped to an embarrassing degree by what was clerically feasible, rather than what he was intellectually capable of solving.</p>
<p>Something similar happened to me over the weekend. The work went faster, but more importantly, I built things I would not have attempted in 2019. Back then, a custom admin panel and a bespoke blog engine sat on the far side of an invisible line, a line where a good idea ceases to be worth the evenings it costs to build. Figuring out Netlify build configurations was my modern equivalent of plotting graphs by hand. The hours it consumed mattered less than the ambitious ideas it quietly disqualified.</p>
<p>Licklider published his findings in his landmark 1960 paper, <a href="https://worrydream.com/refs/Licklider_1960_-_Man-Computer_Symbiosis.pdf"><em>&quot;Man-Computer Symbiosis,&quot;</em></a> proposing machines that would take on clerical preparation so humans could spend their days on the parts that require human cognition. Two years later, <a href="https://dougengelbart.org/content/view/138/">Douglas Engelbart</a> formalized this into a research agenda titled <em>&quot;Augmenting Human Intellect&quot;</em>, an effort that gave us the computer mouse, bitmapped displays, and hypertext. Making humans more capable was one of the two founding ambitions of computer science, alongside building autonomous intelligence.</p>
<p>I heard Nvidia CEO Jensen Huang reach for this exact intuition in <a href="https://youtu.be/fr1IQspixmM?si=dbIMan31jYb_HZii">a recent interview</a> while describing how his engineers work. He called it &quot;augmented development,&quot; grabbing the ordinary phrase that best described what he observed across his company&#39;s desks. I found the term accurate and delicate. Instead of chasing pure automation, his organization focuses on human augmentation. </p>
<p>Is this emphasis on symbiosis representative of how the broader tech industry views generative AI, or is it an outlier? I turned to economic data to find out.</p>
<h2>The Reality &quot;Right Here, Right Now&quot;</h2>
<p>In a working paper for the Stanford Digital Economy Lab, <a href="https://digitaleconomy.stanford.edu/publications/canaries-in-the-coal-mine">Erik Brynjolfsson, Bharat Chandar, and Ruyu Chen</a> analyzed ADP payroll records covering millions of American workers. They found that early-career workers aged 22 to 25 in the most AI-exposed occupations experienced a <strong>16 percent relative decline in employment</strong> following the widespread adoption of generative AI. Crucially, this adjustment occurred not through active layoffs, but through reduced hiring. Entry-level roles are simply being left unfilled.</p>
<p>If you work in a high-exposure knowledge sector, the ladder is missing its bottom rungs.</p>
<p>Is this shift driving clear business gains? Are companies cutting entry-level roles because AI has made their operations drastically more productive? The data does not support that assumption. Research by <a href="https://fion.ac/jellyfish.pdf">Fiona Chen and James Stratton at Harvard</a> examined roughly 200 million work events across 500 engineering organizations. They observed an <strong>8.5 percent increase in coding activity</strong> and an <strong>8.7 percent faster task completion time</strong> among engineers using tools like GitHub Copilot and Cursor. However, they found <strong>no statistically significant impact on total business output or revenue</strong>.</p>
<p>Individual tasks get completed faster, but overall organizational output remains flat. </p>
<p>We are currently navigating the fog of war in the early days of an AI-driven economic transition. Business leaders are reacting to a narrative rather than reality. Influenced by headlines predicting full autonomy, companies are cutting entry-level headcount before seeing true productivity breakthroughs. In turn, product teams build tools designed for total task delegation rather than human augmentation. It threatens to become a self-fulfilling prophecy.</p>
<h2>The Shape of Interaction is a Design Choice</h2>
<p>In mid-2026, Anthropic published a comparison from their <a href="https://www.anthropic.com/research/economic-index-june-2026-report">Economic Index report</a> that I have not stopped thinking about. Looking at how users completed similar writing tasks across two different surfaces powered by the same underlying model, they found a stark contrast:</p>
<ul>
<li>The median <strong>chat session</strong> producing a blog post involved <strong>13 back-and-forth turns</strong> between human and model.</li>
<li>The median <strong>agentic environment</strong> (Claude Code) producing a text artifact contained a <strong>single initial prompt</strong>.</li>
</ul>
<p>The underlying model was identical; the interaction surface determined the nature of the work.</p>
<p>When I refactored my website, I used an automated agentic surface, yet I experienced it as an augmented dialogue. I constantly intervened, steered, rejected outputs, and treated every generated draft as a starting point rather than a final product. The software leaned toward total automation, but I leaned back toward human oversight.</p>
<p>We cannot rely on users to fight their tools. Interfaces set default behaviors. A system that delivers a finished artifact encourages passive acceptance. A system that presents malleable, inspectable work invites critique and iteration. The distance between those two experiences is not determined by breakthroughs in machine learning. It is determined by UX designers and Product Managers deciding how the interface tilts the floor.</p>
<h2>Designing for Symbiosis</h2>
<p>As product leaders, designers, and engineers we really should <strong>stop building interfaces that treat human beings as passive consumers of AI output, and start building products engineered for true human-machine symbiosis.</strong></p>
<p>If we default to building tools that turn humans into button-pushers who blindly accept generated outputs, we will erode domain expertise, degrade work quality, and shrink human agency. If we build for symbiosis, we remove the clerical drag on human creativity, unlocking problems we previously lacked the bandwidth to attempt.</p>
<p>To build products that elevate human capability rather than replace it, we can anchor our work on four core design principles:</p>
<h3>1. Design for Steering, Not Just Prompting</h3>
<p>Prompting is an instruction given at the start. Steering is continuous control applied throughout the process. Symbiotic products provide real-time controls, inline branch points, and mid-flight interventions that allow users to shape the outcome as it forms.</p>
<h3>2. Expose the Scaffolding of Thought</h3>
<p>Never present complex AI outputs as an unexplainable fait accompli. Make the underlying reasoning, sources, assumptions, and trade-offs visible and editable. When users can see how a machine arrived at a proposal, they can critique, refine, and learn from it.</p>
<h3>3. Keep the Feedback Loop Frictionless</h3>
<p>The moment an interface makes it difficult to challenge, adjust, or tweak an AI output, users default to passive approval. Treat every generated output as a draft. Provide lightweight micro-interactions, such as single-click alternatives, granular inline edits, or targeted re-prompts, to make iteration effortless.</p>
<h3>4. Protect the Thinking Time</h3>
<p>Automation should eliminate clerical setup (the modern equivalent of plotting graphs by hand) so humans can focus on evaluation, strategy, and domain judgment. Measure your product&#39;s success not by how long it operates without human involvement, but by how effectively it equips the user to make high-leverage decisions.</p>
<p><strong>There&#39;s lots of work for us left to do</strong> to make AI perform well in the symbiotic relationship with people. </p>
<p>ps. Premium subscribers to my Substack Newsleter: <a href="https://marcintreder.substack.com/"><strong>Augmentation: UX, Product, AI</strong></a> will receive a full prompt by prompt history of my website redesign. You&#39;ll be able to see how I steered Claude towards the right results.</p>
<hr>
<h3>References</h3>
<p>Autor, D. H. (2015). Why are there still so many jobs? The history and future of workplace automation. <em>Journal of Economic Perspectives, 29</em>(3), 3–30. <a href="https://doi.org/10.1257/jep.29.3.3">https://doi.org/10.1257/jep.29.3.3</a></p>
<p>Brynjolfsson, E., Chandar, B., &amp; Chen, R. (2025). <em>Canaries in the coal mine? Six facts about the recent employment effects of artificial intelligence</em> (revised 13 November 2025). Stanford Digital Economy Lab. <a href="https://digitaleconomy.stanford.edu/publications/canaries-in-the-coal-mine">https://digitaleconomy.stanford.edu/publications/canaries-in-the-coal-mine</a></p>
<p>Chen, F., &amp; Stratton, J. (2026). <em>Artificial Intelligence in the Firm</em>. Harvard University. <a href="https://fion.ac/jellyfish.pdf">https://fion.ac/jellyfish.pdf</a></p>
<p>Engelbart, D. C. (1962). <em>Augmenting human intellect: A conceptual framework</em> (Summary Report AFOSR-3233, SRI Project 3578). Stanford Research Institute. <a href="https://dougengelbart.org/content/view/138/">https://dougengelbart.org/content/view/138/</a></p>
<p>Licklider, J. C. R. (1960). Man-computer symbiosis. <em>IRE Transactions on Human Factors in Electronics, HFE-1</em>, 4–11. <a href="https://worrydream.com/refs/Licklider_1960_-_Man-Computer_Symbiosis.pdf">https://worrydream.com/refs/Licklider_1960_-_Man-Computer_Symbiosis.pdf</a></p>
<p>Massenkoff, M., Lyubich, E., Sacher, S., Hitzig, Z., Zhang, S., Heller, R., &amp; McCrory, P. (2026). <em>Anthropic Economic Index report: Cadences</em>. Anthropic. <a href="https://www.anthropic.com/research/economic-index-june-2026-report">https://www.anthropic.com/research/economic-index-june-2026-report</a></p>
<p>U.S. Bureau of Labor Statistics. (2025). <em>Occupational outlook handbook: Tellers</em>. <a href="https://www.bls.gov/ooh/office-and-administrative-support/tellers.htm">https://www.bls.gov/ooh/office-and-administrative-support/tellers.htm</a></p>
]]></content:encoded>
  </channel>
</rss>
