Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium


Create your first initiative

Start building your roadmap by creating an initiative for one real project, feature, or customer request. Use an initiative when the work needs intent, ownership, progress tracking, and a place on the roadmap.

Create an initiative

What an initiative is

An initiative represents larger work: a feature, product bet, engineering project, customer request, goal, or other trackable effort. Initiatives can be nested under parent initiatives so large work can be broken into smaller pieces without losing the strategic thread.

Initiatives live on the roadmap and can be filtered, grouped, ranked, assigned, and measured. In spec-driven development, the initiative also becomes the source brief people and agents build from.

Use Initiatives for planned work and Bugs for defects or incidents. Issues are synced execution items from apps such as Linear, Jira, GitHub, or GitLab.

Replacing Aha!, Productboard, or another roadmap tool? Move projects, epics, and larger product bets into initiatives first. Keeping Linear, Jira, or another issue tracker? Put initiatives above synced issues so execution stays in the source issue tracker while roadmap context lives here.

Create the first initiative

Start from the roadmap, backlog, or recap. Give the initiative a clear title and description.

Set the fields that make the work actionable:

FieldWhat it controls
StatusWhere the initiative sits in the workflow: idea, planned, in progress, in review, blocked, completed, or cancelled.
TeamsWhere the initiative appears in team planning, standups, reports, and analytics.
AssigneesWho is assigned to move the work forward.
TaxonomyHow the initiative is grouped and measured by goal, product, company, skill, coding tool, or agent.
Parent initiativeWhere the initiative sits in the roadmap hierarchy.

Use Writer Mode when the brief is rough

Initiatives can start in Writer Mode. Describe the work in plain language, answer follow-up questions about problem, scope, constraints, proposal, and risks, then save the generated draft as the initiative description. The same writing session can continue from dashboard or Slack until finalized.

Writer Mode is available for initiatives. Bugs do not support it yet.

After the first initiative exists, invite your team so teammates join with current work already in place. For the full initiative model, including hierarchy and Writer Mode, continue to Initiatives.


PreviousSet up integrationsNextInvite your team

Related Articles

Getting started

Create a workspace, connect apps like GitHub, Linear, Jira, Slack, or Google Calendar, then start with one initiative.

Invite your team

Invite teammates, choose their workspace role, and add them to the right teams.

Plan today's work

Review the Daily recap and Board before the day starts.

Set up integrations

Add integrations for apps that hold code, issues, meetings, and team communication.

  • What an initiative is
  • Create the first initiative
  • Use Writer Mode when the brief is rough
  • Back to top