About The Program Manager

The Program Manager is a web application for coordinating programs that span several projects and tools. It keeps one graph of programs, milestones, cross-project dependencies, blockers, decisions and approvals, built from the projects your teams already run in Jira and Asana.

It is MCP-first: you ask about your portfolio in Claude or ChatGPT through the Model Context Protocol, and you use the web app to see what is happening, what connects to what, and what still needs your approval. Its tagline sums up the job: know what will slip before your next status meeting.

In a program that spans many projects, the risk sits between the trackers: a Jira issue in one team blocks an Asana launch task in another, and nobody sees the milestone move until the status meeting. The Program Manager makes those links explicit and shows their effect:

• Cross-program dependency graph: hard, soft and informational links between work items across Jira and Asana, verified or flagged as suggested.
• Milestone risk monitoring: baseline versus forecast for every milestone, with a deterministic impact preview when an upstream item slips.
• Blockers and escalations: an eight-state blocker workflow with owners, due dates and the milestones each blocker holds.
• Decision log: options, rationale, approver and follow-up deadline for each decision, linked to the milestones it affects.
• Weekly program review: progress, milestone movement, blockers, decisions and asks, assembled from live data for each program.

The Program Manager is built for program managers, PMOs and cross-functional delivery leads who coordinate multiple Jira and Asana projects toward shared milestones and launches. It is an independent product, not an all-in-one suite, and it works alongside the tools your teams already use instead of replacing them.

1. Map your launch. Connect Jira and Asana with an API token and pick the projects that make up each program.
2. Detect the slip. Dependencies and milestone forecasts update on every sync. Stale sources are labeled, never shown as green.
3. Escalate with precision. See which blocker holds which milestone, who owns it, and draft the escalation to Slack.
4. Review and decide. Run the weekly review, log decisions with rationale and approve agent proposals.

For AI agents, The Program Manager exposes ten domain-level MCP tools, such as get_dependency_graph, analyze_milestone_impact, list_critical_blockers and get_weekly_program_brief. Agents can propose dependency links and escalations with propose_dependency_link and propose_escalation; nothing is written until a person approves the exact payload, and only then does execute_approved_action perform it.

Integrations available today: Jira Cloud (issues, epics, status transitions and cross-project links), Asana (projects, tasks, sections and task dependencies) and Slack (program updates, escalation alerts and status broadcasts). Planned: Linear, GitHub Projects, Azure DevOps, Microsoft Teams, Confluence, ClickUp, Microsoft Planner and Google Workspace. Planned connectors are never shown as connected until they are live.

Clear limits keep the product focused. The Program Manager is not:

• a task manager or a replacement for Jira or Asana,
• a generic project editor or a second place to edit tasks,
• a resource or HR system, or a timesheet tool,
• a chat app that copies your AI assistant,
• a portfolio finance suite,
• a prediction engine that invents probabilities or dates.

• Human in the loop. Agents propose, people approve. Every external write follows propose, approve, execute, verify, record, and single-use approvals expire.
• Explainable, not opaque. Milestone impact comes from deterministic date logic with visible assumptions, not from model-generated dates.
• Security by default. Row-level security isolates every organization in the database, provider credentials stay server side, and consequential actions are recorded in an audit trail.
• Privacy. No analytics or advertising trackers, self-hosted fonts, and provider data treated as untrusted input that never runs as instructions. Details are in the Privacy Policy.
• Fail closed. Stale sources show timestamps and unverified risk. Never a false green status.

The Program Manager is built and operated by Max Benz, founder, as a sole proprietor based in Dresden, Germany. Max studied Economics (Bachelor) and Business Administration (Master) at TU Dresden and wrote his master thesis on the business models of successful SaaS companies. He is co-founder and CEO of LBC Finance UG and LBC Beteiligungs GmbH and runs several content and SaaS products.

Find Max on LinkedIn and X.

Email team@theprogrammanager.com for questions about the product, access codes, data processing agreements or privacy.

More: Blog · Imprint · Privacy Policy · Sign up with an access code