How to Set Up Height for Product Management (Step-by-Step)
Height is a project management tool designed for modern software teams that combines the power of Jira with the simplicity of Linear. Its standout features for product managers include AI-powered task suggestions, a flexible attribute system, and tight GitHub integration. For PMs who find Jira too complex and Linear too minimal, Height occupies a useful middle ground.
This guide covers setting up Height for product management workflows from initial project structure through sprint execution.
Step-by-step guide
Create your workspace and add your team
After signing up, create a Height workspace with your company name. Add team members via email invitation. Height automatically creates a default "General" list — rename this to your first product area (e.g., "Platform" or "Core Product"). Height's structure is simpler than Jira: Workspace > Lists > Tasks > Subtasks.
Set up lists for product management
Create the following lists: Product Roadmap, Feature Backlog, Sprint (current), and Bug Tracker. In Height, lists are the primary organizational unit — they combine the functions of Jira projects and issue types. Each list has its own workflow states, attributes, and permissions.
Configure task attributes
Height's attribute system is more flexible than Jira custom fields. For the Feature Backlog list, add attributes: Priority (single select: P0/P1/P2), Story Points (number), Sprint (single select with sprint names), PRD Link (URL), and Epic (single select). Attributes appear in both list and detail views.
Set up workflow states
Each Height list has configurable states. For the Sprint list, set states: Backlog, To Do, In Progress, In Review, Done, Cancelled. Map these to your team's actual workflow stages. Height's state machine is simpler than Jira but more structured than Trello.
Enable the GitHub integration
Go to Settings > Integrations > GitHub. Connect your GitHub organization. Once connected, Height auto-creates tasks from GitHub issues and shows PR status in task detail views. Engineers can update Height task status via commit message commands (e.g., "fixes HGT-123").
Use Height AI for task generation
Height has built-in AI that suggests subtask breakdowns for complex tasks. Open a task, click the AI button, and provide context about the feature. Height AI generates a subtask list that the PM or engineer can accept, edit, or reject. This is particularly useful during backlog grooming to break down large features.
Set up sprint cycles
In Height, model sprints using the Sprint attribute (a single-select with sprint names). Filter the Sprint list to "Sprint = Current Sprint Name" for the active sprint board view. Save this as a filtered view. At sprint end, change the Sprint attribute on all completed tasks to the sprint name, giving you a historical sprint record filterable by sprint.
Common mistakes
Creating too many lists
Height lists with different attribute configurations are harder to maintain than one unified list with filters. Start with fewer lists and use attributes to differentiate task types.
Not using the GitHub integration
Height's GitHub integration is one of its strongest features. Without it, engineering and product work remain disconnected. Connect GitHub in the first week of setup.
Skipping the AI task breakdown feature
Height AI's subtask generation saves significant grooming time. Teams that skip this feature miss the tool's most distinctive productivity improvement over competitors.
Tips
Use Height's "Bulk edit" feature to update story points or sprint fields across multiple tasks simultaneously during planning
Height's command palette (Cmd+K) is faster than clicking through the UI for experienced users
Export Height data to CSV for velocity calculations until Height adds native velocity charts
Use Height's public API to pull task data into your reporting dashboards
How Vantage helps
Vantage generates structured tickets that can be imported into Height via CSV export or API. Height's flexible attribute system maps cleanly to Vantage's ticket metadata: priority, wave, dependency, and acceptance criteria all become Height attributes.