{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://tommymagee.com/#person",
  "name": "Tommy Magee",
  "alternateName": "Thomas Magee",
  "url": "https://tommymagee.com/about",
  "description": "Tommy Magee leads Strategy & Applied AI for capital projects and corporate real estate at Rivian. He built the systems, analytics, and executive reporting the capital program runs on, and leads the team that puts AI to work on top of that foundation. Earlier he was an embedded capital programs consultant at Turner & Townsend. He is also the founder of VibeLaunch.",
  "email": "tcmagee@gmail.com",
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "Speaking, professional opportunities and collaboration",
    "email": "tcmagee@gmail.com",
    "url": "https://tommymagee.com/contact"
  },
  "image": "https://tommymagee.com/images/tommy-studio-2026.jpg",
  "sameAs": [
    "https://www.linkedin.com/in/tcmagee/"
  ],
  "jobTitle": "Sr. Manager, Strategy & Applied AI, Capital Projects & CRE",
  "worksFor": {
    "@type": "Organization",
    "name": "Rivian"
  },
  "knowsAbout": [
    "Capital programs",
    "Program management office (PMO)",
    "Stage gates and project controls",
    "Portfolio analytics and executive reporting",
    "Cost management",
    "Technology vendor management",
    "Corporate real estate",
    "AI enablement",
    "AI training and enablement",
    "AI champions programs",
    "Information flow mapping",
    "Domain learning for technical teams",
    "AI for knowledge work",
    "AI-enabled organization design",
    "Enterprise AI implementation",
    "Systems thinking",
    "Change management",
    "Product strategy",
    "Capital program technology",
    "AI agent evaluation",
    "AI ROI assessment",
    "Agentic operating models",
    "AI team leadership",
    "Applied AI",
    "AI agents",
    "Construction technology",
    "Real estate",
    "Enterprise AI adoption",
    "Workflow design",
    "Capital projects",
    "Corporate real estate technology",
    "Product development",
    "Model Context Protocol"
  ],
  "contactUrl": "https://tommymagee.com/contact",
  "opportunities": [
    {
      "type": "Speaking",
      "description": "Enterprise AI implementation and adoption, agentic ways of working, and technology in construction and corporate real estate.",
      "url": "https://tommymagee.com/speaking",
      "contact": "tcmagee@gmail.com"
    },
    {
      "type": "Leadership roles",
      "description": "Leadership roles where program operations and AI sit together, from PMO and capital program operations in real estate to applied AI strategy: operating model and governance, systems and reporting, enterprise enablement, and the organizational change that makes AI useful.",
      "url": "https://tommymagee.com/about",
      "contact": "tcmagee@gmail.com"
    },
    {
      "type": "Co-founder and advisory conversations",
      "description": "Co-founder, advisory, and board conversations around useful AI products. Particular interests include construction, capital projects, real estate, and making technology easier for everyday people to use.",
      "url": "https://tommymagee.com/about/vibelaunch",
      "contact": "tcmagee@gmail.com"
    }
  ],
  "speaking": {
    "url": "https://tommymagee.com/speaking",
    "shortBio": "Tommy Magee leads Strategy & Applied AI for capital projects and corporate real estate at Rivian. His work connects business systems, agents, and the teams who use them. He speaks about AI implementation, adoption, and how work changes.",
    "bio": "Tommy Magee leads Strategy & Applied AI for capital projects and corporate real estate at Rivian. His work connects business systems, agents, and the people who use them. He created AI councils and a champions program to help teams build their own tools and has trained hundreds of people at Rivian, most personally. His perspective comes from capital programs, construction, corporate real estate, and informal, free AI sessions with industry peers. Earlier, through Turner & Townsend, he worked with clients including Google, Meta, Apple, Uber, and Chevron. He is also the founder of VibeLaunch. Tommy speaks about AI implementation, adoption, and how work changes.",
    "topics": [
      {
        "title": "The workshop is the easy part.",
        "description": "People leave excited. Then Monday happens. We’ll work through how to find your team’s AI champions, help them build something useful, and decide who looks after it once others depend on it.",
        "audience": "Teams moving from AI experiments into everyday work.",
        "format": "Talk, fireside conversation, or team session",
        "resource": {
          "label": "See the enablement plan",
          "href": "https://tommymagee.com/resources/enablement-plan"
        }
      },
      {
        "title": "Show me the work that goes away.",
        "description": "A great demo can still give everyone more work. We’ll look at checking, corrections, and upkeep alongside time saved, so you can decide whether a workflow is worth expanding.",
        "audience": "Leaders deciding where AI is worth the investment.",
        "format": "Talk or practical workshop",
        "resource": {
          "label": "Try the evaluation worksheet",
          "href": "https://tommymagee.com/resources/agent-workflow-field-test"
        }
      },
      {
        "title": "Your business is an information factory.",
        "description": "Some of my best AI lessons come from moms on YouTube and lean manufacturing. I’ll show you how to follow a piece of information through a business and spot the handoffs worth changing.",
        "audience": "Operations teams across industries, including construction and real estate.",
        "format": "Talk, panel discussion, or workflow mapping session",
        "resource": {
          "label": "Explore the information factory framework",
          "href": "https://tommymagee.com/resources/information-factory-map"
        }
      }
    ]
  },
  "independentWork": {
    "name": "VibeLaunch",
    "role": "Founder",
    "url": "https://tommymagee.com/about/vibelaunch"
  },
  "experienceOverview": {
    "eyebrow": "Capital programs · Systems · Applied AI",
    "title": "I build the systems, teams, and AI a business runs on.",
    "intro": "I lead Strategy & Applied AI for capital projects and corporate real estate at Rivian. The AI work sits on top of what came before it - the stage gates, systems, cost controls, and executive reporting a capital program runs on, and the team that keeps them running. I’ve done this from both sides of the table, first as an embedded consultant to owners like Google and Uber, and for the last six years on the owner side."
  },
  "experienceNarrative": [
    {
      "id": "rivian",
      "eyebrow": "Capital Projects & CRE · 2020 to present",
      "title": "Rivian",
      "intro": "When I joined in 2020, capital projects and corporate real estate at Rivian was a small, early portfolio of five distinct programs. Over six years I’ve helped turn it into what it is today. Most of my work has been on the technology side, but the strategy came with it the whole way. I started as a product manager and now lead the team behind its portfolio analytics, enterprise platforms, design technology, and applied AI.",
      "parts": [
        {
          "id": "rivian-strategy",
          "title": "Strategy, organization, and change",
          "paragraphs": [
            "Strategy ran alongside the technology from the start, architecting and structuring how the department should operate, from yearly priorities to the quarterly portfolio reviews and leadership updates that keep it on track. In 2024 I brought product and strategy, data and insights, and design technology into one team. Right now I’m working with our VP to rework how the program office runs, getting Finance, Legal, IT, and Operations onto the same stage gates, approval requirements, and data definitions so leaders can compare budgets and forecasts across projects. So much of technology and strategy is really about people and change - processes, ownership, agency, and retiring the old, sticky ways of working. Ultimately it’s about getting people to buy in, then iterating so the new way doesn’t go stale itself."
          ]
        },
        {
          "id": "rivian-systems",
          "title": "Systems, data, and process",
          "paragraphs": [
            "The AI gets the attention, but the systems of record came first. I designed and built the in-house platform the capital program runs on, took it through rollout to real adoption, and still own its roadmap. Every project now moves through the same stage gates from request to delivery, with a clear owner at each one. I led the rollout of Autodesk and our other construction and design platforms the same way. The payoff is in the reporting. Executives and Finance decide from one view of budget, forecast, and risk, and can compare projects on the same definitions in business reviews we run on a set cadence. It also meant we knew what to remove or simplify before we automated anything. I own the technology budget and our vendor relationships too, so build versus buy gets decided against one roadmap."
          ]
        },
        {
          "id": "rivian-ai",
          "title": "Applied AI",
          "paragraphs": [
            "We started testing generative AI when ChatGPT launched, and today it runs in production, taking manual work out of cost management, contract review, and finance. Some we built ourselves, some we bought, and all of it plugs into the systems the department already runs on. Work that used to go to outside firms, like lease administration and pay application review, now gets done in-house. The people who know the work build and look after their own agents. Now we’re building our own internal harness from everything we’ve learned, because what’s specific to how we work is where our advantage comes from."
          ],
          "link": {
            "href": "/library/when-everyone-starts-building-agents",
            "label": "Read the implementation story"
          }
        }
      ],
      "points": [],
      "link": {
        "href": "https://tommymagee.com/library/when-everyone-starts-building-agents",
        "label": "Read the implementation story"
      }
    },
    {
      "id": "silicon-valley",
      "eyebrow": "Systems & strategy consulting · 2017 to 2020",
      "title": "Turner & Townsend",
      "intro": "Before Rivian I sat on the other side of the table, as an embedded capital programs consultant at Turner & Townsend, working inside the teams that run some of Silicon Valley’s largest capital programs.",
      "paragraphs": [
        "When I got to Uber’s workplace team, a roughly $500M program was being managed off one spreadsheet. Working directly with their Finance directors, I moved it into a full system built in Salesforce, with rules, permissions, approval workflows, automations, and dashboards. The team went from updating a shared file to planning, approving, and forecasting capital in one place.",
        "Most of my time, though, was on Google’s data center program, a multibillion-dollar build-out across North America, EMEA, and APAC. A lot of that work was streamlining how the program contracted with its general contractors and architects, along with the vendor strategy and cost controls around it. We got the process and the strategy right first, then turned them into digital systems, so contracts and invoices ran through the same workflow and actual costs were captured for estimators to benchmark future work against.",
        "Around that I supported Meta’s data centers and Google’s workplace program, did similar planning and forecasting work for Chevron’s infrastructure program, and built custom chatbots for Apple’s retail real estate team, well before ChatGPT."
      ],
      "points": [],
      "link": {
        "href": "https://tommymagee.com/about/capital-systems",
        "label": "More on the capital-program work"
      }
    }
  ],
  "aiEnablement": {
    "title": "AI training & enablement",
    "paragraphs": [
      "None of this works unless people can use it. I built AI councils and a champions program to spread adoption and find the people who could take their teams further, many of them from non-technical roles. The bigger shift is in the roles themselves, with knowledge workers learning to partner with AI and create something more powerful together."
    ],
    "context": "I’ve trained hundreds of people at Rivian, most of them personally, and run informal, free sessions with industry peers."
  },
  "independentProjects": [
    {
      "id": "vibelaunch",
      "name": "VibeLaunch",
      "role": "Founder",
      "period": "May 2026 to present",
      "description": "A product for publishing, sharing, and managing what people create with AI, so it doesn’t take an engineer to put an idea in front of someone.",
      "lesson": "I own the product, the build, and operations.",
      "url": "https://www.vibelaunch.live/",
      "story": {
        "href": "https://tommymagee.com/about/vibelaunch",
        "label": "The thinking behind VibeLaunch"
      }
    },
    {
      "id": "skotero",
      "name": "Skotero",
      "role": "Co-founder · Electric scooter startup",
      "period": "2015 to 2017",
      "description": "An early attempt at solving last-mile transportation. I led product strategy, operations, and go-to-market. We closed the business in 2017.",
      "lesson": ""
    }
  ],
  "metrics": [],
  "experience": [
    {
      "role": "Sr. Manager, Strategy & Applied AI",
      "organization": "Rivian",
      "period": "2025 – NOW",
      "description": "Capital Projects & CRE. Leads the team behind portfolio analytics, enterprise platforms, design technology, and applied AI. Owns the department’s technology budget and vendor relationships, runs the executive reporting behind capital planning, and leads AI implementation and enablement, including bringing outsourced work in-house."
    },
    {
      "role": "Manager, Tech & Strategy",
      "organization": "Rivian",
      "period": "2024 – 2025",
      "description": "Capital Projects & CRE. Brought product, data, and technology into one operating group and translated executive priorities into plans through quarterly portfolio reviews."
    },
    {
      "role": "Lead Product Manager, Tech & Strategy",
      "organization": "Rivian",
      "period": "2020 – 2024",
      "description": "Capital Projects & CRE. Built and rolled out the in-house platform the capital program runs on, with its stage gates and approval workflows, and led adoption of Autodesk and other construction and design platforms. Founded the analytics and BI team and set the reporting cadence for Finance and leadership across a multibillion-dollar portfolio."
    },
    {
      "role": "Consultant to Senior Consultant",
      "organization": "Turner & Townsend",
      "period": "2017 – 2020",
      "description": "Systems & Strategy. Embedded capital programs consultant to owners including Google, Meta, Apple, Uber, and Chevron. Streamlined contracting, vendor strategy, and cost controls on Google’s data center program, and moved Uber’s workplace capital program from one spreadsheet to a full planning and approval system."
    },
    {
      "role": "Technology advisory & implementation",
      "organization": "IT managed services",
      "period": "2013 – 2017",
      "description": "Gamwell Technologies and Novatech Systems · El Paso. Helped small and medium-sized businesses choose and implement technology, from cloud services to day-to-day systems, around what the business needed to do."
    }
  ],
  "resources": [
    {
      "title": "Execution and enablement",
      "url": "https://tommymagee.com/resources/execution-and-enablement",
      "description": "Two jobs every AI program has to do, measured in different ways: getting the organization started, and delivering real returns."
    },
    {
      "title": "Centralize the data first",
      "url": "https://tommymagee.com/resources/centralize-data-first",
      "description": "Step one, before agents or apps: find where the information lives, rank it, connect it, give it an owner, and open it to people and agents with the right permissions."
    },
    {
      "title": "The information factory",
      "url": "https://tommymagee.com/resources/information-factory-map",
      "description": "Follow one piece of information through the business like a part through a plant: who touches it, where it waits, and which handoffs are worth changing."
    },
    {
      "title": "Headless and agentic first",
      "url": "https://tommymagee.com/resources/headless-and-agentic-first",
      "description": "State the need as a capability, expose it behind an API or MCP, let an agent be the interface where people already work, and build a screen only when it is earned."
    },
    {
      "title": "The enablement plan",
      "url": "https://tommymagee.com/resources/enablement-plan",
      "description": "How to level up your subject matter experts: go wide and shallow, give people room to build, grow champions, and add a council as building takes off."
    },
    {
      "title": "Finding champions",
      "url": "https://tommymagee.com/resources/finding-champions",
      "description": "Treat enablement as recruiting: know the signals, give new champions a real first month, and keep them from burning out."
    },
    {
      "title": "Data, process, people",
      "url": "https://tommymagee.com/resources/data-process-people",
      "description": "The execution strategy, in order: get the information right, question every step, then change responsibilities."
    },
    {
      "title": "Build, buy, or remove",
      "url": "https://tommymagee.com/resources/build-versus-buy",
      "description": "There are three options, and the cheapest is often the one nobody proposes: remove the work. If it has to stay, building is cheap now. The real cost is the code plus maintenance, rollout, and change management."
    },
    {
      "title": "The embedded builder",
      "url": "https://tommymagee.com/resources/embedded-builder",
      "description": "Send an AI developer to sit with a team, in the style of a forward deployed engineer: watch the work, build the smallest useful thing in the open, hand it over, and move on."
    },
    {
      "title": "Measuring released capacity",
      "url": "https://tommymagee.com/resources/released-capacity",
      "description": "Time saved, minus time added, equals net capacity. Then check where that capacity went, and don’t count it as cash."
    },
    {
      "title": "Three levels of AI output",
      "url": "https://tommymagee.com/resources/three-levels-of-ai-output",
      "description": "A shared way to read the complexity of anything built with AI, from a personal tool to an enterprise system. It’s also how a council filters what gets built."
    },
    {
      "title": "Personal agents and shared experts",
      "url": "https://tommymagee.com/resources/personal-agents-shared-experts",
      "description": "A model for which AI agents belong to each person and which ones the organization has to manage."
    },
    {
      "title": "The AI business council charter",
      "url": "https://tommymagee.com/resources/council-charter",
      "description": "Who sits on an AI business council, what it decides, how it runs, and the rules that keep it from becoming a gate."
    },
    {
      "title": "The trust ladder",
      "url": "https://tommymagee.com/resources/trust-ladder",
      "description": "Four rungs of authority, from drafting to acting alone, and the evidence that moves an agent up or down."
    },
    {
      "title": "The change path",
      "url": "https://tommymagee.com/resources/change-path",
      "description": "Five outcomes every person has to reach before a change sticks, with a readiness check before you start and an executive driving it the whole way."
    },
    {
      "title": "The change readiness assessment",
      "url": "https://tommymagee.com/resources/change-readiness-assessment",
      "description": "Five checks to run before you plan a rollout, the case, the sponsor, the capacity, the history, and the impact. Don’t launch on red."
    },
    {
      "title": "Executive sponsorship",
      "url": "https://tommymagee.com/resources/executive-sponsorship",
      "description": "The single strongest predictor of whether a change sticks. What an executive sponsor has to do, visibly and repeatedly, beyond signing off."
    },
    {
      "title": "Communicate like a launch",
      "url": "https://tommymagee.com/resources/communicate-like-a-launch",
      "description": "Treat change communication like go-to-market. Know the audience, sharpen the message, use every medium, and overcommunicate well past the point it feels like enough."
    },
    {
      "title": "The burning platform",
      "url": "https://tommymagee.com/resources/burning-platform",
      "description": "Show people the problem they can’t see yet, plainly and with evidence, and point to the way off. Urgency, not fear."
    },
    {
      "title": "Gamified adoption",
      "url": "https://tommymagee.com/resources/gamified-adoption",
      "description": "Tap into reward. Pick one behavior, make progress visible, recognize it fast and often, and refresh the game before it goes stale."
    },
    {
      "title": "Learn by doing",
      "url": "https://tommymagee.com/resources/learn-by-doing",
      "description": "Kickoffs and seminars fade within days. Tutorials, hands-on sessions, and office hours build skill people actually keep."
    },
    {
      "title": "Train the trainer",
      "url": "https://tommymagee.com/resources/train-the-trainer",
      "description": "The tried and true technique for implementation. Train a respected peer in each team deeply, equip them, and let them teach the rest."
    },
    {
      "title": "The leaderboard and the naughty list",
      "url": "https://tommymagee.com/resources/leaderboard-and-naughty-list",
      "description": "Publicly recognize the people who keep adhering, and show who isn’t, lightly and objectively. Neutral reporting does most of the work."
    },
    {
      "title": "Is this agent making the work better?",
      "url": "https://tommymagee.com/resources/agent-workflow-field-test",
      "description": "A field-test worksheet for quality, human effort, operating cost, and the decision to scale."
    },
    {
      "title": "Find the work worth removing",
      "url": "https://tommymagee.com/resources/workflow-prompt",
      "description": "Six questions to ask before reaching for another AI tool."
    }
  ],
  "appearances": [
    {
      "title": "The AI Evolution of Retail",
      "url": "https://tommymagee.com/speaking/ai-evolution-retail",
      "date": "October 2026",
      "venue": "SF Tech Week · Surfaice & JLL"
    },
    {
      "title": "Fireside chat with Google & Rivian",
      "url": "https://tommymagee.com/speaking/autodesk-owners-forum",
      "date": "July 21, 2026",
      "venue": "Autodesk Owners Forum · San Francisco"
    },
    {
      "title": "Cost controls using AI: the future of pre-construction",
      "url": "https://tommymagee.com/speaking/rics-ai-cost-controls",
      "date": "2025",
      "venue": "RICS · San Francisco"
    },
    {
      "title": "How emerging tech is disrupting real estate",
      "url": "https://tommymagee.com/speaking/emerging-tech-real-estate",
      "date": "2018-07-26"
    }
  ],
  "library": [
    {
      "title": "Your company will issue you an AI agent",
      "type": "Writing",
      "description": "Personal agents that know how you work, shared experts the organization manages, and what that means for the software we build.",
      "url": "https://tommymagee.com/library/company-issued-ai-agent",
      "markdownUrl": "https://tommymagee.com/library/company-issued-ai-agent.md",
      "tags": [
        "AI agents",
        "Organizational change",
        "SaaS"
      ],
      "body": [
        "Your company will issue you an AI agent like it issued you a laptop. Except this one will learn how you think and start taking work off your plate.",
        "The cliché is Jarvis from Iron Man, but honestly, more like Donna from Suits. Part chief of staff, part minion. And yes, they literally tried making a digital Donna in the show.",
        "The part that interests me is how well Donna understands the person she works with. She knows what matters, sees what’s coming, and handles things without needing the whole situation explained every time. That’s a pretty useful starting point for thinking about a personal agent.",
        "As my team builds toward a more AI-native org, I keep coming back to two types of agents: personal agents and shared experts. I think the relationship between them will shape a lot of knowledge work beyond developers.",
        "## Your agent will learn the job with you",
        "Your personal agent will know how you think, what you’re working on, and how to get things done for you. It’ll learn which details you care about, who you work with, and when you need to be pulled into a decision.",
        "It could help you onboard by walking you through real work in context. As you settle in, it could prepare responses, follow up on things you’ve delegated, and work in systems on your behalf. Eventually, you might realize you haven’t personally logged into half of them since last year. It might even cover a meeting for you, if the job is to gather information and bring it back.",
        "Imagine asking it to get a vendor proposal ready for a decision. It already knows why you need the vendor, what you’ve discussed, and what’s still missing. It gathers the current information, gets help reviewing the terms and costs, and comes back with the questions you actually need to settle. Once you decide, it handles the follow-through within the authority you’ve given it.",
        "You’d still be involved. But you wouldn’t need to personally move every piece of information between every system and person along the way.",
        "## Shared experts are an organizational responsibility",
        "Your personal agent shouldn’t have to become the company’s best contract reviewer just because you need a contract reviewed.",
        "That’s where shared expert agents come in. Legal, finance, design, engineering. Digital employees the organization manages, with deep company context and internal experts responsible for testing and continuously improving them. Your personal agent would call on them like you would.",
        "In that vendor example, your agent could ask the shared contract expert to review the terms against the company’s current guidance. A finance expert could check the commercial assumptions. Your agent brings the results together in the context of your decision, including anything that still needs a person’s judgment.",
        "Calling something a legal expert doesn’t give it authority to approve a contract. The organization still has to decide what it can do, what needs review, and who owns the result. The same is true when a human employee joins a team. A job title is the beginning of that conversation.",
        "## Consistency is why this matters",
        "Give everyone the same data and tools, and you still get wildly different results. Everyone builds differently. Someone writes a great prompt. Someone else connects the wrong folder. Another person makes something useful for themselves that falls apart when anyone else tries it.",
        "Some setups expose information, confidently get things wrong, or feed slop back into company knowledge. Then the next agent retrieves that slop and treats it as context. Pretty quickly, it gets hard to tell where the original information ended and someone’s generated interpretation began.",
        "Shared experts give the organization a standard it can actually manage. The people responsible for the work can test the same kinds of requests, inspect failures, and improve the expert everyone relies on. When company guidance changes, there’s a clear place to update the behavior and check whether it still holds up.",
        "That concentrates responsibility too. A shared expert that gets something wrong can spread that mistake much further. Someone needs to own it, know what good looks like, and be willing to pull it back when it stops meeting that standard. We should expect ongoing work here.",
        "There’s still room for people to build and experiment. I want that. But a useful personal setup and something the whole company depends on need different levels of care.",
        "## Most people shouldn’t have to become AI hobbyists",
        "I don’t think most knowledge workers will need to know about context windows, token spend, prompt engineering, or which model to pick. They’ll work with their agent like a reliable remote coworker. Explain what they need, give feedback, and get on with the job.",
        "People will still need to learn how to delegate, check work, and recognize when something needs their attention. Those are familiar skills. We already expect them from people working with other people.",
        "The technical decisions still matter. Somebody has to make them. I just don’t think that somebody needs to be every employee, every time they want help getting through the day.",
        "Trust will have to build through use. An agent that drafts a message well hasn’t automatically earned permission to send it. One that can explain a budget hasn’t earned permission to change it. Responsibility should expand as the work holds up and the person delegating it gets comfortable.",
        "## If you build SaaS, think about who will use it",
        "A lot of your interface exists so humans can move information around. Find the record, check another screen, copy something over, update a status, tell somebody it’s done. Agents won’t need all those screens.",
        "People will still need ways to understand what happened, make decisions, and correct mistakes. But I think a lot more of the routine work will happen through personal agents and shared experts calling on the capabilities underneath the interface.",
        "For a founder, I’d think hard about where the product fits. A personal agent might want broad access to a system so it can carry a task through. A shared expert might need one very specific capability that your product does exceptionally well. Either way, it needs to get the work done and return something the agent can use, including a clear failure when it can’t.",
        "That’s what I see us building toward: a personal agent that understands you, shared experts the organization can stand behind, and products useful enough for both to call on.",
        "Go wide or go deep. Just be really useful to at least one instead of bad at both."
      ]
    },
    {
      "title": "Changing the work, not just the tools",
      "type": "Writing",
      "description": "A firsthand account of enterprise AI implementation: workflow redesign, agents managed by subject matter experts, and the ownership that lets teams build.",
      "url": "https://tommymagee.com/library/when-everyone-starts-building-agents",
      "markdownUrl": "https://tommymagee.com/library/when-everyone-starts-building-agents.md",
      "tags": [
        "Enterprise AI",
        "Organizational change",
        "Capital programs",
        "AI implementation"
      ],
      "body": [
        "The most useful AI work I’ve led started with a question about the business: how should the work change now that AI can do some of it? At Rivian, my team and I helped business teams rethink how they plan, coordinate, and make decisions across capital programs and corporate real estate.",
        "I connected the process, people, and data framework with implementation: shaping the agent platform, mentoring teams building their own solutions, and establishing ownership for what they built. The work was shared. Keeping those pieces connected was a central part of my job.",
        "## Start with the information",
        "We mapped how information moved between people and systems: what came in, what needed to come out, and where it went next. Doing that with the people responsible for the work helped us question the steps themselves.",
        "We used three lenses:\n\n- **Process:** Which steps still need to exist?\n- **People:** What can this team change, and what crosses into someone else’s responsibilities?\n- **Data:** What information does the job need, and can people and agents use it?",
        "Some processes could go away. Some work belonged with an outside provider. Other workflows needed a change in responsibilities before better software would help. Being able to automate a task wasn’t enough reason to keep doing it.",
        "## Put control close to the work",
        "We built a platform of custom agents that subject matter experts could tune and manage themselves. They understood the job. Depending on developers for every adjustment would have limited what they could do with it.",
        "The work reached across cost and portfolio management, site selection, leasing, cash modeling, forecasting, and workplace operations. We connected systems through custom APIs and Model Context Protocol (MCP), with Slack as a place people could work across them. Making the underlying data readable by AI and accessible to people building tools was a major engineering priority.",
        "## Give teams room to build",
        "I created AI councils and a champions program to find people who combined subject matter expertise with an aptitude for AI. My team and I mentored them, developed building kits, and created a tool registry to make ownership visible.",
        "Contract review support was one of the workflows champions worked on. Other tools supported finance and accounting, meeting records, and dashboards that reduced coordination between groups. The people who knew the work could build with help from my team.",
        "A personal tool, a shared team solution, and an enterprise initiative need different support. As others began relying on what teams built, we had to decide where to invest, where effort was being duplicated, and who would look after it. That became part of enablement, not something to sort out later.",
        "## What changed, and what is still ahead",
        "We eliminated unnecessary processes, simplified the technology stack, and reduced tooling and licensing spend. Redesigned workflows and automation also freed capacity and helped teams absorb work without new hires. Lower spending is a saving; released time gives people room to take on other work.",
        "Our planning points to more capacity for a growing capital program. The next test is how this way of working holds up as that work arrives.",
        "## What I would carry into another business",
        "Finance, contracts, forecasting, and coordination are familiar problems well beyond construction and real estate. The useful starting point is the same: follow one piece of work, understand who needs what, and decide which responsibilities should change.",
        "I evaluate the whole job, including the checking, correction, and support an agent adds. I’ve turned those questions into an [evaluation worksheet](/resources/agent-workflow-field-test) you can adapt.",
        "The frameworks and change management are the part I’m proudest of. They gave us a way to improve shared systems while helping teams solve problems for themselves."
      ]
    },
    {
      "title": "The best interface might be no interface",
      "type": "Writing",
      "description": "If AI is supposed to remove work, why are we creating another place for humans to work?",
      "url": "https://tommymagee.com/library/less-interface",
      "markdownUrl": "https://tommymagee.com/library/less-interface.md",
      "sourceUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7502513748235096064/",
      "tags": [
        "AI & work",
        "Applied AI"
      ],
      "body": [
        "SaaS founders, a request: build products my team and I don’t have to log into.",
        "I actively solicit demos and get pitched new tools. Lately, I keep coming back to the same question. Do we really need another interface? A product can solve a narrow problem and still give the organization more work overall.",
        "Another tool means another workflow to learn. Someone has to train the team, manage access, keep the information current, and support it when something changes. Eventually, someone has to replace it. Those costs rarely fit into the demo.",
        "## Start with what needs to happen",
        "When I see a promising solution, I increasingly ask whether it can do the work for us as a service, or make its capabilities available to our agents. I’m interested in the outcome. The screen is one possible way to get there.",
        "Take a hypothetical project update. If the information already exists across the systems a team uses, asking everyone to enter it into one more dashboard adds a coordination job. A more useful product might assemble the current picture, show its sources, and flag the few things that need a person’s attention.",
        "That still requires an interface somewhere. People need to check the answer, understand what changed, and correct mistakes. But there’s a difference between giving someone control and making them operate every step.",
        "## There’s no maintenance-free option",
        "Internally built agents have maintenance costs too. So does vibe coding. Someone needs to own the connections, permissions, quality, and behavior when the system fails. Building it yourself doesn’t make that responsibility disappear.",
        "The comparison I care about is the total work involved. What does this remove? What does it add? Who ends up looking after it? A smaller interface is useful only if the complexity hasn’t just moved somewhere harder to see.",
        "For teams buying software, I’d put those questions into the evaluation early. For founders, I think there’s an opportunity to make the product useful wherever the customer already works, including through an agent.",
        "If AI is supposed to remove work, a new place for people to manage it is a pretty incomplete proposition. Show me the work that goes away. That’s where it gets interesting."
      ],
      "originalPostDate": "2026-09-06"
    },
    {
      "title": "What lean manufacturing gets right about AI",
      "type": "Writing",
      "description": "Some of my best AI lessons came from moms on YouTube.",
      "url": "https://tommymagee.com/library/information-factory",
      "markdownUrl": "https://tommymagee.com/library/information-factory.md",
      "sourceUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7490994059873001472/",
      "tags": [
        "Systems thinking",
        "Applied AI"
      ],
      "body": [
        "A surprising amount of my AI philosophy comes from moms on YouTube and Japanese lean manufacturing.",
        "The first one is legit. People running households are constantly coordinating information, juggling constraints, delegating, and dealing with exceptions. Some of the clearest AI tutorials I’ve seen come from people trying to make real life a little easier. They know what the job is. The tool has to earn its place.",
        "That’s a useful starting point for a company too. Before asking which agent platform to buy, understand the work people are already trying to get through.",
        "## Watch the work",
        "One lean principle I keep coming back to is Gemba: understand the work where it happens. A process diagram tells you what’s supposed to happen. Watching someone do the job tells you where they wait, re-enter information, chase a decision, or work around the system.",
        "For a construction or real estate team, that could mean following a single decision from the person who spots a problem to the person who can resolve it. Where does the context get lost? Why does it need another meeting? Is there actually a decision to make, or is somebody just looking for information?",
        "Those are useful questions whether the answer involves AI or not.",
        "## Keep responsibility visible",
        "I also think about Jidoka, which I translate into my AI work as automating while keeping people responsible for quality. An agent finishing a task doesn’t tell us whether it did the right thing.",
        "We need to decide what a good result looks like, who can check it, and when the system should stop and ask. That doesn’t mean reviewing every small action forever. It means being deliberate about which decisions we’re comfortable delegating and what evidence would change that judgment.",
        "Then there’s Yokoten: spread what works. Once a team finds a useful approach, share the reasoning and the conditions that made it work. Copying a prompt without the surrounding context is a pretty thin form of knowledge transfer.",
        "## Think about the whole system",
        "Japanese manufacturers didn’t simply add technology to an unchanged factory. They rethought how the work moved. I see a similar opportunity for organizations that move information and decisions all day.",
        "The phrase I use is information factories, with both human and digital workers. The interesting part is how they work together: who has the context, who owns the decision, and how the next person knows it’s their turn.",
        "I’d start with one real workflow, learn from the people doing it, and make the smallest change that improves it. The tools will keep changing. Understanding the work is still the part that matters."
      ],
      "originalPostDate": "2026-08-05"
    },
    {
      "title": "Your AI is only as good as its context",
      "type": "Writing",
      "description": "Clean, connected, trusted data is the work behind the impressive demo.",
      "url": "https://tommymagee.com/library/data-first",
      "markdownUrl": "https://tommymagee.com/library/data-first.md",
      "sourceUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7480368579847106561/",
      "tags": [
        "Applied AI"
      ],
      "body": [
        "Show me a company’s data quality and structure, and I’ll have a much better idea of what its AI can actually do.",
        "My rough rule: enterprise AI is probably 80% data and 20% AI. We spend a lot of attention on models and agents. The less visible constraint is whether they have useful context.",
        "An organization can have years of documents and still struggle to answer a basic question reliably. Having information somewhere is different from knowing which information to trust.",
        "## Context has a job to do",
        "Consider a hypothetical capital project. There’s a schedule in one system, a cost forecast in another, and a decision recorded in an email. An agent can retrieve all three and still get the answer wrong if the schedule is stale, the forecast uses a different project identifier, or the decision has been superseded.",
        "A bigger model doesn’t settle those disagreements for us. Someone has to establish the relationships and decide which source owns which fact.",
        "Before adding another AI tool, I want to understand a few practical things. Where does the information come from? How current is it? What does it refer to? Who owns it? And does the person asking the question have permission to see it?",
        "Those questions sound ordinary because they are. They’re also the difference between a convincing answer and an answer a team can safely use.",
        "## Start with a bounded problem",
        "I wouldn’t wait for every piece of company data to be perfect. That can turn into a program with no useful stopping point. Pick a workflow and identify the context it actually needs. Clean up that slice, connect it, and see whether the result holds up in real use.",
        "For example, an assistant answering questions about a project should be able to point back to the record behind its answer. If the record is missing or outdated, that should be visible. The gap is useful information, even when it means the agent can’t finish the task.",
        "As the workflow grows, the data responsibilities need to grow with it. Access, ownership, and updates are ongoing work. They aren’t a one-time cleanup before the interesting AI part starts.",
        "I think there’s a lot of value in the companies and teams that make this foundation easier to build and maintain. The impressive demo gets attention. Clean, connected, trusted context is what gives it a chance of becoming useful every day."
      ],
      "originalPostDate": "2026-07-07"
    },
    {
      "title": "Do we need to heat the whole house for this?",
      "type": "Writing",
      "description": "Choosing an AI model is starting to feel a lot like becoming your dad with the thermostat.",
      "url": "https://tommymagee.com/library/thermostat",
      "markdownUrl": "https://tommymagee.com/library/thermostat.md",
      "sourceUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7495932739339046912/",
      "tags": [
        "In practice",
        "Applied AI"
      ],
      "body": [
        "Choosing a model is starting to feel like adjusting the thermostat. Does this task need the most powerful setting, or is a smaller one enough?",
        "Matching the model to the work can reduce cost and resource use. The goal is to use the capability the task actually needs, with enough attention to quality to know the difference.",
        "I’m interested in keeping quality high without using more capability than the work needs."
      ],
      "originalPostDate": "August 2026"
    }
  ]
}
