AppZen Roadmap Tracker

Loading roadmap data…

Feature ID (system-assigned)

Pillar

Feature / Initiative Name

Category

Product

Select products…

Current Status (synced with this month in Monthly Status & FTE)

💡 Milestones tied to dates: In Design → Design Start · Design Completion → Design Completion Date · In Dev → Dev Start · Deployed in Sandbox → Sandbox Date · Prod Released → Prod Release Date · GA → GA Date. If you pick one of these without the matching date filled, the app will ask you for the date — or a reason.

% Complete

Why Build This?

🎯 Hard Production Release Date (cannot slip)

🔒 Internal Discussion Only (hide from GTM / external sharing)

Dependencies

Risks

Notes ⓘ

👥

Who's working on this feature. PM Owner and Eng Lead drive the work; Assignee is the IC actually doing the build; QE Assignee owns testing; Technical Writer owns the user-facing docs. Reporter is auto-filled from the person who created the feature and is read-only.
📣 Updater marks who is responsible for the weekly status update on this feature — they'll receive the Slack nudge. Defaults: PM Owner for Backlog features, Eng Lead for Roadmap. Anyone can be checked.

PM Owner 📣 Updater

Eng Lead 📣 Updater

Assignee (IC doing the work) 📣 Updater

QE Assignee 📣 Updater

Technical Writer 📣 Updater

Reporter (auto)

—

Design Start (PM phase)

Design Completion Date (committed handoff to Eng)

Dev Start *

Sandbox Date

GA Date (General Availability) * Same as Prod Release date

Prod Release Date *

Add one link per field. Each chip below opens in a new tab when clicked. Please put links here rather than pasting them into Description, Rationale or Notes — the Audit Log can then surface them as their own clickable entries.

📄 PRD

📐 Blueprint

🎨 Figma / Prototype

🧪 Test Cases

📘 User Guide (published)

🪲 Jira

📣 Release Notes

🎬 How-To Video

Month	FTE by Skill

💬

When to use Comments vs Notes vs Change Reason:
• Comments (this tab) — ongoing back-and-forth discussion with @mentions; replies are threaded.
• Notes (Details tab) — static, long-form context that stays with the feature: scope notes, links to related Slack threads, risks the PM wants documented.
• Change Reason — required short explanation captured at save time whenever Dev Start / GA / Sandbox / Release date changes; surfaces in the Audit Log.

Audit Detail

✨ What's New — May '26

✨ May 2026 Release

4 new in-app guides ship this sprint — covering Dashboard deep-dives, Bandwidth analytics, and FTE capacity planning. Use the ▶ buttons below to explore each guide now.

🖥️ Dashboard Navigation

🔀

Switching Dashboard Lens A.1.1

Toggle between Monthly, Gantt, By Product, and By Skill views to see your roadmap from any angle

🃏 Feature Card Intelligence

🃏

Reading Dashboard Feature Card A.1.2

Decode the Health indicator, GA date, % Done, and pillar badge on every feature card

📊 Bandwidth & Capacity

📈

Bandwidth Chart Deep-Dive A.1.3

Read team capacity vs. allocation bars, drill into monthly breakdowns, and spot over-allocated teams

⏱️

FTE Hours Distribution A.1.4

Assign engineering hours per skill in the Monthly Status & FTE tab — shapes the Bandwidth chart in real time

Bandwidth Utilization by PM

Rolling Month Management

Bulk Import Features

Scheduled Reports

Slack Notifications (per-user, real-time DMs)

Email Diagnostics

View History

Slack PM Nudge — Dry-Run Preview

Dashboard Card Fields

FTE Capacity Reference

How Health is Calculated

🗑 Recently Deleted 0

Plan, track, and ship the AppZen roadmap.