All Collections
Quick Guides
Connections: How it all fits together
Connections: How it all fits together

How Ignition's different sections interact

Derek Osgood avatar
Written by Derek Osgood
Updated over a week ago

Connections: How It All Fits Together

On the whole, this is what a Go-to-Market process looks like:

Ignition's real magic comes from leveraging the power of Connections to drive products from concept all the way through post-launch success though (although it is all modular, so you don't need to use any given part of Ignition). Connections allow for key context to flow through the various stages of the product build and launch process, so stakeholders at each step can track progress and understand the "why" behind plans.

Generally, this is the flow of the product lifecycle in Ignition:

Research/Insights ➡️ Product Ideas ➡️ Roadmap Items ➡️ GTM Plans ➡️ Release Notes

  1. Insights (your learnings) turn into Personas, Competitors, and Product Ideas

  2. Product Ideas turn into Roadmap Items (the features you plan to build)

    1. Roadmap Items are packaged up into Releases (the update you plan to ship)

    2. Roadmap Items will also often have Personas, Competitors, Product Ideas, and Inisghts connected to them, for context.

    3. Roadmap Items will also often be connected to Engineering Tasks (the specific tasks your Eng team needs to complete to build the feature)

  3. Roadmap Items turn into GTM Plans (the launch plan for the customer-facing announcement of a product or feature)

    1. GTM Plans will inherit all the Connections from the Roadmap Items

  4. GTM Plans turn into Release Notes (the customer-facing communication of the new product or feature)

When any item is "Connected" to a new item, that new item inherits all the Connections from the previous item.

Did this answer your question?