Why did your Product Vision fall from 91% to 73%?

LangDrift shows how your product moved from the vision you intended — what changed, who moved it, why it happened, and whether the change was intentional.

See what moved How it works

Product Vision73%

Vision movementdown from 91% · 14 intentional · 4 unexplained

Jun 28 · PricingPricing strategy changedAna + Carlos · Product

Why? Enterprise customers required a different packaging model.

Decision recorded · View decision context →

-9Intentional Evolution

Connected context

Select a node to see who was involved and follow the movement on the chart.

Loading connected context…

Drift describes movement relative to a product vision. It can reveal a gap, a realignment, or a positive change.

Vision → Loop → Evidence

Your product evolves through priorities, decisions, and discoveries. LangDrift connects the direction you intended with the changes made along the way and the evidence that explains them. Explore how those changes can reveal a gap, a deliberate trade-off, or a better direction.

Explore a scenario

A customer request moves advanced configuration earlier in onboarding. The team needs to understand how that priority affects the original first-use experience.

Vision

Vision Target: Help a new workspace owner reach a useful first result before asking them to configure advanced settings.
Who it serves: Small teams setting up their first workspace without dedicated technical support.
Success criterion: A new owner can complete the core workflow with sensible defaults and adjust advanced settings afterward.

Loop

Request
A prospective customer asks for advanced configuration before their evaluation can begin.
Change
The team brings the configuration step forward in the onboarding flow.
Review
The request explains the new priority, but the records do not establish whether the trade-off for first-time users was accepted.

Evidence

Supporting records

Product brief
Onboarding target
The original brief puts the first useful result before advanced configuration.
Customer request
Evaluation requirement
The customer request explains why configuration became a near-term priority.
Change review
Revised onboarding flow
The revised flow places configuration before the first result, creating tension with the original criterion.

What this change means

A priority shift to review

The product now asks for configuration earlier than the original target intended. The customer request explains the pressure behind that change, but it does not explain whether the broader onboarding trade-off was accepted. That distinction gives the team a concrete decision to revisit.

Open question

Should this requirement apply only to the customer's evaluation, or should the team intentionally revise the onboarding target?

Drift can reveal a gap, a course correction, or a valuable discovery. Its meaning comes from context and evidence.

Continue to attribution

Know why

Every movement keeps its context.

Select a marked point in the Product Vision curve to see what changed, its impact, why it happened, who was involved, and the recorded decision state.

Selected movement

Pricing strategy changed

Jun 28 · Pricing

-9Intentional Evolution

Why it moved

Enterprise customers required a different packaging model.

Decision stateDecision recorded

Who was involved

Ana + Carlos

Know who

Know who moved the product.

Important movement stays connected to people, teams, product areas, decisions, and review state without turning LangDrift into punitive surveillance.

Jun 28Pricing

Pricing strategy changed

-9Intentional Evolution

Jul 22Authentication

Authentication redesigned

-6Unexplained Drift

Aug 20Exports

Export behavior changed

-3Under Review

Intent matters

Evolution is expected. Unexplained movement is different.

Intentional Evolution14 points

Movement backed by a recorded decision, reason, and attributable actors.

Unexplained Drift4 points

Meaningful movement without enough recorded product rationale.

Under Review1 event

Evidence exists, but the relationship is not ready for a confident classification.

Executive voice

Ask the same model you can see.

Voice sits on top of structured Product Vision, Drift, attribution, and evidence — not a separate chat history.

“Why did Product Vision move this week?”

Executive output

A report should read like a decision brief, not an engineering dump.

Weekly product evolutionProduct Vision · 81 → 76

Largest movement: Authentication · -3
Why: No linked product decision
Who: Carlos · Platform
Status: Unexplained Drift
Needs attention: Review authentication rationale

Integrations

Connected to the way your team works.

Bring your product context and evidence into LangDrift through the SDK connection. Connect GitHub for pull request automation, start PRDs and Research in Obsidian, and mirror specs and tickets in Linear. The platform connection is the foundation; additional tools extend the workflow your team chooses.

Your project

LangDrift SDK

Prepare and send the product context and records that help explain how your product is evolving.

LangDrift MCP

LangDrift

Required for dashboard

Connect your project to bring its context and evidence into the dashboard, graph, and reports.

This is the core connection between your project and the LangDrift platform.

GitHub
Required for pull requests
Enable the workflow to open pull requests automatically with the defined template and the context needed for review.
Pull request context
Change summary, related spec, and verification notes, organized in the pull request template.
Obsidian
Optional
Start PRDs and Research in Obsidian, keeping early product thinking in the knowledge workspace your team already uses.
Product thinking at the source
A PRD or Research note can begin in Obsidian and remain connected to the product context LangDrift uses for review.
Linear
Optional
Replicate specs and tickets in Linear so the team can follow the work in the planning tool it already uses.
Shared planning context
A ticket carries the related spec context into the team's planning workflow.

The SDK prepares and validates project data, then uses the LangDrift MCP connection to send that context to the platform. This connection supports the dashboard experience.

External integrations extend that workflow. GitHub is required for the pull request automation described here. Obsidian and Linear are optional: Obsidian can be used to begin PRDs and Research in a familiar knowledge workspace, while Linear can carry specs and tickets into the team's planning workflow. Each connector follows its own integration path; choosing one does not require enabling the others.

Start with the platform connection. Add the tools that support your team's workflow.

Get early access

Executive review

What needs attention before your next release?

Explore where your product changed, inspect the context behind those changes, and revisit the decisions that still need attention. LangDrift connects the release overview with the records and review conditions behind it, so leadership can move from a question to a specific next decision.

Explore a questionFour-week period

Current selection

What changed across this release? · All targets · All classifications

Product movement, with context

This selection contains 12 Drift Events across 3 Vision Targets. 7 are Expected, 3 are Unexpected, and 2 are not yet classified. 10 events have linked evidence, and 4 open review items are recorded. Select a target to inspect the changes and the context behind them.

Drift Events: 12
Vision Targets: 3
Open reviews: 4
Events with linked evidence: 10 of 12

Drift Events by Vision Target

Entire release

Entire release. Select a target or segment to inspect a subset.

Vision Target

Classification

Expected does not mean beneficial, and Unexpected does not mean harmful. Linked sources provide context; their presence alone does not establish confidence or causality.

Linked evidence

Inspect the sources linked to each event in the current selection.

Linked evidence
Drift Event	Spec	Decision	Verification	User feedback
E01 · Week 1Workspace defaultsOnboarding · Expected
E02 · Week 2Manual integration setupOnboarding · Expected				Not linked
E03 · Week 3Contextual setup guidanceOnboarding · Expected			Not linked
E04 · Week 3Advanced configuration gateOnboarding · Unexpected		Not linked
E05 · Week 4Early invitation stepOnboarding · Unexpected		Not linked		Not linked
E06 · Week 4Alternate setup pathOnboarding · Unclassified	Not linked	Not linked	Not linked	Not linked
E07 · Week 1Connection retry summaryIntegrations · Expected				Not linked
E08 · Week 2Clearer connection errorsIntegrations · Expected
E09 · Week 3Connection scope previewIntegrations · Expected				Not linked
E10 · Week 4Fallback scope mismatchIntegrations · Unexpected		Not linked
E11 · Week 2Guided permission presetsPermissions · Expected
E12 · Week 4Role selection proposalPermissions · Unclassified	Not linked	Not linked	Not linked	Not linked

Review conditions

R01
Review the manual setup compromise
Related event: Manual integration setup
The manual setup compromise needs setup observations and support feedback before broader rollout.
1. Week 1
  Decision recorded
  Manual configuration was accepted for the initial integration release.
2. Week 2
  Flow reviewed
  The delivered setup includes the accepted manual step.
3. Pending condition
  Before broader rollout
  Gather setup observations and support feedback, then review whether the additional effort remains acceptable.
Next decision
Should the manual step remain for the broader audience, or should guided configuration be completed first?
No user feedback is linked to this event.
R02
Review the configuration gate
Related event: Advanced configuration gate
The configuration gate needs a decision about its scope before this flow is expanded.
1. Week 1
  Scope recorded
  Advanced configuration follows the first useful result.
2. Week 3
  Difference observed
  The inspected flow requires configuration earlier.
3. Pending condition
  Before expanding this flow
  Decide whether to restore the scoped sequence or explicitly revise the target and rationale.
Next decision
Should the gate apply to a narrower evaluation path, or should the broader onboarding target be deliberately revised?
No decision accepting this ordering change is linked.
R03
Establish the context of the alternate path
Related event: Alternate setup path
The alternate path needs its intended flow and rationale established before classification.
1. Week 4
  Inventory entry
  An alternate setup path was listed in the release inventory.
2. Pending condition
  Before classifying the change
  Link the intended flow and the rationale for introducing this path.
Next decision
What target and decision should this alternate path be evaluated against?
No supporting sources are linked.
R04
Establish the role proposal's scope
Related event: Role selection proposal
The role proposal needs its intended audience and permission policy documented before a rollout decision.
1. Week 4
  Inventory entry
  A role-selection proposal was listed without supporting context.
2. Pending condition
  Before deciding on rollout
  Document the intended audience and permission policy, then review the proposal against that scope.
Next decision
Which audience and permission requirements should guide this proposal?
No supporting sources are linked. The review request itself is not evidence of an approved policy.

Get early access

Return on your product investment

Make your product investment go further.

Every release commits time, talent, and budget. Understand the decisions behind your product’s evolution, revisit trade-offs before expanding your investment, and recognize opportunities worth pursuing.

Spend less time rebuilding context.
Bring connected decisions, changes, and supporting records into the discussion, so your team can focus on what happens next.
Revisit the trade-off before investing further.
See which compromises still serve your goals and which deserve another decision before a broader rollout.
Recognize opportunities worth pursuing.
Explore when a change reveals a promising direction—and which evidence you need before committing to it.

Product briefE02 · R01

Before broader rollout

Manual setup helped bring the integration forward. Its effect on new customers still needs validation.

Expand with the current setup, or invest in completing the guided experience first?

Recorded trade-off
Implementation verification
User feedback pending

E02-DDecision
E02-VVerification

No user feedback is linked to this event.

Get early access Explore plans

A few things worth knowing.

What drift means, how LangDrift fits your workflow, and what happens when you join early access.

LangDrift is preparing for early access, with a 15-day free trial starting when your access is activated.

See what clearer product decisions could mean for your team.

Join the early-adopter list for a 15-day trial when LangDrift launches.

We’ll email you when access is available. Your trial starts when your access is activated.

Why did your Product Vision fall from 91% to 73%?

Connected context

Vision → Loop → Evidence

Vision

Loop

Request

Change

Review

Evidence

Onboarding target

Read the source context: Onboarding target

Evaluation requirement

Read the source context: Evaluation requirement

Revised onboarding flow

Read the source context: Revised onboarding flow

A priority shift to review

Every movement keeps its context.

Pricing strategy changed

Know who moved the product.

Pricing strategy changed

Authentication redesigned

Export behavior changed

Evolution is expected. Unexplained movement is different.

Ask the same model you can see.

A report should read like a decision brief, not an engineering dump.

Connected to the way your team works.

Your project

LangDrift

GitHub

Obsidian

Linear

How the connections work

What needs attention before your next release?

Product movement, with context

Drift Events by Vision Target

Linked evidence

Review conditions

Review the manual setup compromise

Decision recorded

Flow reviewed

Before broader rollout

Review the configuration gate

Scope recorded

Difference observed

Before expanding this flow

Establish the context of the alternate path

Inventory entry

Before classifying the change

Establish the role proposal's scope

Inventory entry

Before deciding on rollout

Make your product investment go further.

Spend less time rebuilding context.

Revisit the trade-off before investing further.

Recognize opportunities worth pursuing.

Before broader rollout

A few things worth knowing.

What does “drift” mean?

Does “Expected” mean a change was beneficial?

What do I need to connect?

Do I need GitHub, Obsidian, and Linear?

When does the 15-day trial start?

Is there a permanent free plan?

What is included in Plus and Pro?

Can I use LangDrift today?

See what clearer product decisions could mean for your team.