Getting startedCreate your first initiativeConnect version controlInvite your teamPlan today's work
Pilot GuidePitch GuideDesktop appSDK
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Changelog
  • Docs

Features

  • Assistants
  • Workflows and agents
  • Capability management
  • Boards
  • Roadmap
  • Triage
  • Progress
  • Insights
  • CLI
  • Integrations

Solutions

  • Insurance
  • Finance
  • Software

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
  • Support
  • API reference
  • Desktop app
  • SDK
  • Vault
  • QR code generator
  • Video frame extractor

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXTikTokYouTubeMedium


Pilot Guide

A pilot tests the workflow with one or two teams before a broader rollout. A good pilot runs for 1 to 2 weeks and compares the current reporting process against work captured from connected tools.

Define success before the pilot starts. Most teams measure reporting time, visibility into progress, blocker discovery, and whether developers feel less pressure to rewrite status by hand.


Pick your pilot team

Start with a team that spends visible time on standups and status updates and can influence the larger organization. The pilot works best when the team's commits, pull requests, issues, calendar events, and team communication already reflect the work.

Agree on the pilot dates, the tools the team will connect, and how you will collect feedback.


Create a baseline survey

Before changing anything, run a short survey on how reporting works today, where information is missing, and how much time the team spends on status. Adapt these sample questions to your organization.

Reporting overhead

How much time do you spend per week on status updates?
What percent of your work is reflected in status updates?

Visibility and clarity

On a scale of 1 to 5 (select all that apply):

Developer experience

On a scale of 1 to 5 (select all that apply):

Get integration approval

If an admin must approve third-party apps, choose the relevant message below and replace each bracketed placeholder before sending it.


Set up integrations

Connect the apps the pilot team uses daily:

  • GitHub or GitLab for commits, pull requests, merge requests, and reviews
  • Linear or Jira for issues, status, ownership, and project work (Enterprise plan)
  • Google Calendar for meetings, events, and standup schedules
  • Slack for recaps, standup prompts, and team updates

Run the pilot

During the pilot, developers review their Recaps, team leads check progress without asking for updates, teams skip or shorten standups, and no one writes manual status updates.

If you need help with setup, contact support before the pilot window starts so the pilot measures product usage, not setup problems.


Send a post-pilot survey

Reuse the baseline questions after the pilot and add open text fields for what changed. Set a response deadline at least one week before the leadership review so you have time to compile results.

Sample questions:

How much time do you spend per week on status updates now?
On a scale of 1 to 5 (select all that apply):

Compile your data and present your case

Pull out the 4 to 5 strongest quantitative changes and place them beside the baseline, with one short quote when it explains a metric. Useful comparisons are hours spent on status updates, visibility scores, developer experience scores, and how many team members actively used the product.


Make the switch

Let the pilot evidence decide the next step. Many teams expand to adjacent teams first, then roll out to the workspace once integrations, roles, and reporting routines are clear. Invite your team covers adding people.

Sign up and exploreBook a demo

PreviousContactNextPitch Guide

Pitch Guide

Help your team evaluate One Horizon with clear messages for executives, engineering leads, developers, and external stakeholders.

Case Studies

Customer stories and examples of teams using One Horizon in real engineering workflows.

Community

Join Slack for product feedback and support, or Stripe Eindhoven for community events.

  • Pick your pilot team
  • Create a baseline survey
  • Get integration approval
  • Set up integrations
  • Run the pilot
  • Send a post-pilot survey
  • Compile your data and present your case
  • Make the switch
  • Back to top