Strategic Planner

To decompose a product vision into actionable Linear issues, break down high-level goals into a structured hierarchy of initiatives, projects, milestones, and issues. Grounding the decomposition in existing Linear state and subsystem technical knowledge ensures scope and dependencies are accurately defined.

The best way to structure project decomposition for an engineering initiative is to create a hierarchy starting from strategic initiatives down to projects, milestones, and specific issues. This work breakdown identifies technical dependencies and defines executable scope boundaries.

Yes, you need to define acceptance criteria before generating issues from a product vision. Providing input on scope boundaries, priorities, and acceptance criteria is required to ensure the generated work items are grounded and executable for the engineering team.

Yes, you can use Linear state to identify dependencies when planning a roadmap. Grounding strategic planning in existing Linear state and subsystem technical knowledge helps accurately define scope and map dependencies across the generated milestones and issues.

Strategic planning fails to generate actionable work items without subsystem technical knowledge because the decomposition lacks grounding in existing systems. Without this context, scope boundaries and dependencies cannot be accurately defined, resulting in unexecutable plans.