Files

43 lines
2.0 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
depends_on: [M001]
---
# M002: Tracking control center — Context Draft
**Gathered:** 2026-03-24
**Status:** Draft — needs milestone-specific discussion before planning
## Seed from broader discussion
The product should feel first like a tracker and follow-up system, not just a collection of AI tools. The agreed navigation hierarchy is job table first, then follow-up/dashboard, then individual job workspace. That means M002 is the milestone where the tracking and control-center surfaces likely get stronger after M001 proves Gmail import quality and AI draft quality.
## Intended milestone role
M002 likely expands the app from “good Gmail + good drafts” into a clearer job-search control center for an individual user. The likely emphasis is better table/dashboard/follow-up workflow, better visibility into what needs action, and stronger continuity through the life of each application.
## Likely capabilities
- stronger table views and status clarity
- better follow-up/dashboard action surfacing
- tighter tracking continuity across manual updates and imported correspondence
- clearer operating rhythm for daily use
- likely analytics/pattern visibility only where it directly improves decision-making
## Constraints already known
- individual-first product shape remains in force
- no auto-send or auto-apply behavior
- job discovery still happens outside the app
- table → follow-up/dashboard → job workspace remains the intended daily navigation hierarchy unless usage disproves it
## What this milestone unlocks
A version of the product that feels more like the users daily control center and less like a set of helpful but disconnected screens.
## Open questions for future discussion
- How much of M002 should be action clarity versus analytics polish?
- Which table/dashboard views feel most lacking in current use?
- Should saved views, stronger filtering, or timeline/history clarity be core in this milestone?
- What specific “I know what to do next” experience should the dashboard deliver every morning?