GLIDR uses a small vocabulary that shows up across the product. This page is the source of truth for what each term means.
A note on Ideas vs. Hypotheses. On GLIDR they're called Ideas; on LaunchPad they're called Hypotheses. Same concept, different label depending on which product you're using. In this glossary we use "Idea (Hypothesis)" to cover both.
Core concepts
Project
A workspace for one product, business model, or initiative. Projects live under an Organization. Each project can map to a product, team, or whole company. Tier determines how many projects you can have at once.
Organization
Your company's instance of GLIDR. Permissions in GLIDR are layered: organization level (umbrella) and project level (per project).
Card
The generic name for the three content types in a project: Ideas (Hypotheses), Evidence, and Posts. You can edit any card after publishing.
Idea (Hypothesis)
A testable claim about your business, product, or customer. The atomic unit of the Canvas. Each idea sits in a specific Canvas block.
Evidence
Data that supports or refutes an Idea. Includes Customer Discovery interviews, support tickets, sales calls, competitor analysis, test results — anything that grounds an Idea in reality.
Experiment
A focused test of an Idea, usually involving live user behavior, with a clearly-stated hypothesis that can be proven or disproven.
Post
The simplest entry type — a quick update, link, or file shared with the team. Can be a standalone note or attached to other cards.
Connection
Links cards together (Evidence to Ideas, Experiments to Ideas, Ideas to each other) to show which evidence supports or opposes which idea.
Attachment
Files attached to a card — reports, survey results, audio recordings of interviews — anything you want to keep alongside an Idea, Evidence, or Post.
Comment
A way to discuss a card with your team. Use @mentions to direct
attention.
Canvas (Business Model Canvas)
The Canvas is where you organize your Ideas into a coherent business model. GLIDR ships with the Business Model Canvas as the default; the Mission Model Canvas and Product Canvas are available as variants.
The nine blocks of the BMC:
- Customer Segments — who you sell to
- Value Propositions — what makes your product attractive to those customers
- Channels — how the product reaches the customer (marketing + distribution)
- Customer Relationships — how you reach and maintain customers
- Revenue Streams — how the business earns money
- Key Resources — the assets needed to make the model work
- Key Activities — the activities the business does to deliver value
- Key Partners — outside relationships that make the model viable
- Cost Structure — what it costs to operate the model
The Product Canvas is a separate canvas for ideas specific to one product within the broader business.
Scoring
Trending Score
A weighted average of all the ratings your team has assigned to Evidence and Experiments connected to an Idea. Tells you which Ideas have the strongest backing.
ICE Score
Impact, Confidence, Ease — each scored on a 10-point scale, averaged together. A simpler version of RICE that drops the Reach factor.
RICE Score
(Reach × Impact × Confidence) / Effort. The classic prioritization formula.
Results
Mark an Idea as Validated or Invalidated once you have enough Evidence to decide.
Riskiest Ideas / Hypotheses (Enterprise + LaunchPad)
The Ideas that would have the biggest impact on the business model if right or wrong. Worth testing first.
Organizing your work
Theme
A category you create to group Ideas — e.g., "Integrations" or "Usability." Default is "no theme."
Tags
Free-form labels for cross-cutting concerns. Mix and match across cards.
Kanban view
A column-based view of Ideas — drag cards between columns to reflect their status.
Roadmap
A strategic plan of Ideas ordered by priority (Now, Next, Future, Backlog). Captures the why behind the plan, not just the what.
Status
Projects are Active by default. Switch to Archive when a project is done, or Backlog when it's not yet time to work on it.
Collections
A way to group a subset of Projects to monitor their stats and financials in one place.
The interface
Dashboard (Enterprise)
A high-level overview of how a project is performing, with metrics and trends.
Overview
Per-project context: Team Description, Problem Statement, Solution Statement, Market Type, link to the MVP / demo / website.
Activity Feed
A live stream of everything happening in a project — cards added, edited, commented on. Filter, sort, and comment from here.
Notifications
Updates from projects you're involved in.
Drafts
Anything you start but don't publish auto-saves as a Draft. Drafts are visible only to you and live under the Notifications icon.
Permissions
GLIDR uses two permission levels:
- Organization level — controls access across the whole instance
- Project level — controls access to specific projects within the org
A user can have different roles at each level — e.g., view-only at the organization level but admin on one specific project.