Skip to content
Linear Horizon Training

Example · 3 days

AI for product and programme managers

Use AI for requirements, plans, reporting and meetings, connect it to your delivery tools, then learn to scope, run and measure AI projects and features.

For product, programme and project managers.

  1. Day 1

    • What generative AI is, and is not

      Quarter day · AI foundations · Foundation

      • Language, image, speech and code models, and what each is good for.
      • Where generative AI fits next to search, analytics and conventional software.
      • Chat assistants, copilots, APIs and agents: the same models behind different products.
      • Common claims, and how to tell a demonstration from a dependable capability.
    • LLM fundamentals

      Quarter day · AI foundations · Foundation

      • How an LLM actually produces text, at a practical level.
      • Tokens, context windows, and what the model can and cannot see.
      • Prompting, system instructions and structured outputs.
      • Hallucination and reliability: why it happens and what reduces it.
      • Known limits: arithmetic, recency, long documents and confident errors.
    • A working method for AI at work

      Quarter day · AI foundations · Foundation

      • Choosing a tool your organisation allows for the task in hand.
      • Give context, ask, check, refine: a loop that produces work you can sign off.
      • Projects, saved instructions and reusable prompts.
      • Exercise: a real task from your role, start to finish.
    • Checking AI output, and when not to use it

      Quarter day · AI foundations · Foundation

      • Spotting fabricated facts, references and figures.
      • Proportionate checking: how much review a task deserves.
      • Personal and confidential data: what can go into which tool.
      • Tasks where AI is the wrong choice.
  2. Day 2

    • Requirements, user stories and acceptance criteria with AI

      Quarter day · AI for product and delivery · Foundation

      • Turning interviews, notes and tickets into requirements.
      • User stories and acceptance criteria a team can build and test against.
      • Finding gaps, contradictions and edge cases.
      • Exercise: draft and challenge the stories for a real feature.
    • Planning, estimation and scheduling with AI

      Quarter day · AI for product and delivery · Foundation

      • Breaking work down into plans and work packages.
      • Estimates with ranges and stated assumptions.
      • Dependencies, critical paths and what-if scenarios.
      • Exercise: plan a real piece of work and check the AI’s reasoning.
    • Status reports, RAID logs and stakeholder updates with AI

      Quarter day · AI for product and delivery · Foundation

      • Status reports drafted from tickets, notes and plans.
      • Risks, assumptions, issues and dependencies kept current.
      • One set of facts, written for different audiences.
      • Exercise: produce a week’s reporting from raw project data.
    • Meetings, minutes and actions with AI

      Quarter day · AI for product and delivery · Foundation

      • Agendas and pre-reads.
      • Transcripts, minutes and decision logs.
      • Actions with owners and dates, followed up.
      • Privacy and consent when meetings are recorded.
  3. Day 3

    • Connecting Jira, Confluence and other tools to AI

      Quarter day · AI for product and delivery · Intermediate

      • Connectors and MCP: letting an assistant read and update your tools.
      • Automations: triage, summaries and ticket updates.
      • Permissions and what an assistant should never change on its own.
      • Exercise: design one automation for your team’s workflow.
    • AI-native programme management with Claude

      Quarter day · AI for product and delivery · Intermediate

      • From AI-assisted to AI-native programme management.
      • Claude as a work platform: projects, connectors and skills.
      • Custom connectors with MCP for your own systems.
      • High-value programme workflows: status, risks, RAID logs and reporting.
      • Permissions, cost and keeping people accountable for decisions.
    • Running an AI project

      Quarter day · AI for product and delivery · Intermediate

      • Why AI projects are less predictable than ordinary software.
      • Milestones built around evaluation results, not features.
      • Data, security and legal dependencies to plan for early.
      • Go, no-go and when to stop.
    • AI risk and policy in an organisation

      Quarter day · AI foundations · Foundation

      • Data protection, confidentiality and what providers retain.
      • Accuracy, bias and accountability for AI-assisted decisions.
      • Approved tools, acceptable use and a policy people will follow.
      • Regulation in outline, including the EU AI Act.
Contact