LIFTS

Implementation Toolkit · Version 2.0

The LIFTS Framework

A five-stage way for small and emerging technology companies to decide where to invest, what to test, and when AI is the right tool, using evidence that separates what happened from what a decision actually caused.

The LIFTS cycle Five stages arranged in a loop: Locate, Investigate, Fit, Test, Scale or stop, which feeds back into Locate. L I F T S lift = test result − counterfactual

Overview

Most small technology companies make growth decisions on reported numbers. A campaign looks like it worked, so it gets more budget. LIFTS asks a harder question first: what did the decision actually cause, compared with what would have happened anyway?

The framework turns that question into a repeatable cycle with five stages. Each stage has a working template, so a team moves from "why isn't this product growing?" to a documented, evidence-based decision. LIFTS is the operational name and structure of the author's AI-Enabled Commercialization Decision Methodology.

Who it is for. Small and emerging U.S. technology companies making high-stakes growth decisions without dedicated growth, analytics, or experimentation teams. The level of rigor scales to the data a company actually has.

The cycle

Each stage produces one completed template, and each decision starts the next cycle.

  1. Locate the constraint

    Find the one barrier holding the product back, based on evidence.

    ProducesConstraint Diagnostic

  2. Investigate and design the test

    Turn the constraint into a testable question, with decision rules set in advance.

    ProducesExperiment Protocol

  3. Fit the intervention

    Choose the response, and use AI only if it beats a non-AI option.

    ProducesUse-Case Assessment

  4. Test incremental impact

    Measure what the response caused, net of side effects.

    ProducesImpact Assessment

  5. Scale or stop

    Act on the result using the rules agreed before the test.

    ProducesDecision Matrix

Core rules

Five rules apply to every cycle. They make results comparable across cycles, products, and teams.

  1. R1

    One primary constraint per cycle

    A cycle that addresses several constraints at once cannot attribute its result to any one of them.

  2. R2

    Decision rules before data

    Success thresholds and the action for each possible result are recorded before the test begins, and are not changed once results arrive.

  3. R3

    AI must earn its place

    Choose an AI option only when there is good reason to expect it to beat a named non-AI option on results, cost, effort, risk, and human oversight. Then measure whether it did.

  4. R4

    Realized impact, not gross

    Results are reported net of offsetting effects elsewhere in the business.

  5. R5

    Every decision has an owner and a review date

    A decision without both is recorded as open, not made.

Stage gates

A stage is not complete until its gate is met, and the next stage does not begin until then.

StageEntry conditionRequired outputExit gate
L · LocateA product with a stated growth goalConstraint Diagnostic naming one primary constraint, with evidenceDecision owner agrees the primary constraint
I · InvestigateAn agreed primary constraintExperiment Protocol (hypothesis, metrics, baseline, design, decision rules), with the Decision Matrix filled inHypothesis, measurement plan, thresholds, and provisional decision rules approved before testing begins
F · FitA signed-off test planUse-Case Assessment comparing the AI option with a non-AI alternative, including risks and compliance reviewIntervention chosen and implemented as specified
T · TestIntervention live for the planned periodImpact Assessment with gross and realized impact, against the pre-set threshold and evidence tierResult classified against the decision rules
S · Scale or stopA classified resultDecision recorded in the Decision Matrix with an owner and a review dateScale, iterate, or stop; the decision feeds the next cycle

Evidence tiers

Every result is labeled with the tier it rests on. The tier sets how much weight the final decision can carry.

TierDesignWhen to useConfidence
Tier 1Randomized holdout: users, accounts, or markets randomly assigned to test and controlDefault whenever the channel or platform allows random assignmentHigh, if the test is well designed, large enough, and run as planned. Can support scaling when the effect size, uncertainty, economic value, and rollout risks justify it.
Tier 2Geo split or synthetic control: matched or modeled comparison marketsWhen randomization is not possible, such as market-wide campaigns, partnerships, or offline channelsModerate. Can support scaling when comparison markets tracked closely before the test; confirm with a second test where possible.
Tier 3Structured before-and-after: comparison to a pre-set baseline, with seasonality controlledLow-cost, reversible decisions, or as a screen before a stronger testLow confidence that the change caused the result. Enough to keep investigating or make small, reversible calls; not enough to scale.

The toolkit

Five instruments, one per stage. Each has a template to fill in and an illustrative example that follows one hypothetical company, an appointment-scheduling startup for independent clinics, through the full cycle.

Instrument 1 · Locate the constraint

Commercialization Constraint Diagnostic

What is holding this product back, and which barrier matters most?

SectionWhat to captureYour response
Product and stageProduct, target customer, market, stage (pre-launch, launch, scaling)Fill in
Growth goalThe outcome the company needs, with a number and dateFill in
Current performanceKey metrics today: acquisition, conversion, retention, cost per customerFill in
Candidate barriersUnclear product-market fit; low trust or understanding; inefficient acquisition spend; missing measurement; compliance friction; manual workflow on a small team; otherFill in
Evidence for each barrierData, customer feedback, or past tests that support or rule out each candidateFill in
Primary constraintThe single barrier to address first, and why it outranks the othersFill in
Cost of inactionWhat continuing without addressing it costs, in money, time, or customersFill in
UnknownsWhat the team does not yet know, to carry into Stage 2Fill in
  • Rank by evidence, not instinct. A barrier with no supporting data becomes an unknown, not the primary constraint.
  • For an early-stage company, the most common primary constraints are unclear product-market fit and low trust.

Instrument 2 · Investigate and design the test

Learning Agenda and Experiment Protocol

What must be proven, how will it be tested, and what will each result trigger?

SectionWhat to captureYour response
Constraint addressedThe primary constraint from Stage 1Fill in
Hypothesis"If we [change], then [outcome] will [move by how much], because [reason]."Fill in
Primary metricsThe one to three metrics that decide the resultFill in
Secondary metricsMetrics that explain why the result happened or flag side effectsFill in
BaselineCurrent values of the primary metrics and the period they coverFill in
Test designHoldout, market split, synthetic control, or structured before-and-after, matched to available dataFill in
Measurement limitationsKnown data gaps, delays, or biases, and how each will be handledFill in
Success thresholdThe result that counts as success, stated as a numberFill in
Execution rulesWhat stays fixed during the test (pricing, budgets, channel mix, messaging), dates, approvalsFill in
Decision for each outcomePositive, neutral, and negative ranges, and the action each triggersFill in
  • Match rigor to data. A company with limited volume can use a structured before-and-after comparison, as long as its limitations are written down.
  • Keep other conditions as steady as you can, and write down anything that changes. If something cannot be controlled, account for it in the design or analysis.

Instrument 3 · Fit the intervention

AI-Enabled Use-Case Assessment

Does an existing AI tool outperform a non-AI alternative for this specific problem?

SectionWhat to captureYour response
Constraint addressedThe primary constraint from Stage 1Fill in
Response optionsThe AI option and at least one non-AI option (research, process change, analytics, repositioning)Fill in
Users and workflowWho uses the tool, at which step, and how oftenFill in
Expected benefitThe measurable improvement expected (time, cost, speed, accuracy), with a numberFill in
ComparisonWhy the AI option beats the non-AI option, or why it does notFill in
Data and accessThe data the tool needs, where it lives, and who must approve accessFill in
Human oversightWhich decisions stay with people, and who reviews the tool's outputFill in
Risks and limitationsAccuracy, data quality, privacy, compliance, costFill in
Success criteriaHow the benefit will be measured after adoption (carried into Stage 4)Fill in
RecommendationAdopt, pilot, or declineFill in
  • Start with tools the company already has. LIFTS applies existing AI tools; it does not require building models.
  • In regulated industries, keep compliance review in the workflow; use AI to speed that review up, not to replace it.

Instrument 4 · Test incremental impact

Incremental Impact Assessment

Did the response cause a real improvement, or would the result have happened anyway?

SectionWhat to captureYour response
Test referenceThe Stage 2 protocol and the actual test datesFill in
Baseline vs resultPrimary metrics before and after, with the period for eachFill in
Method usedHoldout, market split, synthetic control, or before-and-after, and any deviation from the planFill in
Incremental effectThe change attributable to the response, net of what would have happened anywayFill in
Attributed vs incrementalWhere reported or attributed results differ from the incremental estimate, and by how muchFill in
Economic impactGross and realized effect on spend, revenue, profit, or time, after side effectsFill in
Side effectsChanges in other channels, teams, or metricsFill in
Confidence and caveatsStatistical significance where available, data gaps, and what the test could not showFill in
VerdictPositive, neutral, or negative against the pre-set success thresholdFill in
  • State what the test could not show. An honest limit is more useful than an overstated result.

Instrument 5 · Scale or stop

Commercialization Decision Matrix

Given the evidence, what should happen next?

Result rangeWhat it meansActionOwnerReview date
Positive (above threshold)Fill inScale, expand to new markets or teams, or keep the changeNameDate
Neutral (between thresholds)Fill inAdjust and retest, or keep partiallyNameDate
Negative (below threshold)Fill inStop and revert, or return to Stage 1NameDate
Inconclusive (data too weak)Fill inExtend the test or redesign itNameDate
  • Also record the decision taken, any deviation from the matrix and why, how the change will be monitored, and the next question for a new cycle.
  • The same process can produce opposite decisions in different situations. That is the point: the evidence decides, not the plan.

Defined terms

These terms mean the same thing everywhere in the toolkit.

Commercialization constraint
The barrier that most limits a product's growth or adoption at a given time, such as unclear fit, low trust, inefficient acquisition spend, or weak conversion.
Primary constraint
The single constraint a LIFTS cycle addresses, chosen in Stage 1 on the strength of evidence.
Counterfactual
What would have happened without the change. It can be estimated through an experiment or a careful comparison, and it is only as reliable as the design and data behind it.
Incrementality
The share of an observed outcome caused by the intervention rather than by factors that would have produced it anyway.
Lift
The measured difference between the test group and the counterfactual, as an absolute or percentage change.
Decision rule
A pre-agreed statement of what the team will do for each possible result, recorded before the test starts.
Realized impact
Gross impact net of offsetting effects elsewhere, such as volume or cost shifted to another channel.
AI-enabled intervention
A change that uses an existing AI tool for analysis, targeting, content, or automation, evaluated against a non-AI alternative.

Scope and limitations

Intended use

Commercialization decisions in small and emerging technology companies, including go-to-market spend, acquisition channels, conversion, retention, and the adoption of existing AI tools in those workflows.

Outside scope

Building or training AI models; brand or creative strategy that cannot be measured against a counterfactual; legal, regulatory, or financial advice.

Minimum conditions

A measurable outcome metric, enough volume to detect the expected effect, and a named decision owner. Where volume is too low for a Tier 1 or Tier 2 design, the toolkit still applies and the result is labeled Tier 3.

Limitations

Results are specific to the product, market, and period tested, and should be re-validated before they are applied elsewhere. The toolkit structures judgment; it does not replace it.

About and sources

Efearue Uduigwomen is a growth and commercialization practitioner with a master's degree in marketing analytics. LIFTS formalizes decision processes she developed and applied through her work at Risevest, Remitly, and Inkitt between 2020 and 2026. The integrated framework was formally documented in October 2026, and the examples on this page use a hypothetical company.

Foundations

LIFTS draws on established improvement, experimentation, and growth methods and combines selected principles into one decision framework built for small and emerging technology companies.

  • Theory of Constraints (Goldratt, The Goal, 1984): the focus on one primary constraint before any response.
  • DMAIC (Six Sigma, Motorola, 1980s): the five-stage structure and control step, rebuilt around causal testing.
  • PDCA (Deming, building on Shewhart): the repeating loop, with "check" replaced by an incrementality test.
  • Build-Measure-Learn (Ries, The Lean Startup, 2011): measuring what was caused rather than only what happened.
  • G.R.O.W.S. (Ellis and Brown, Hacking Growth, 2017): structured experimentation, started from a diagnosed constraint.

References

  1. Abadie, A., Diamond, A., & Hainmueller, J. (2010). Synthetic control methods for comparative case studies. Journal of the American Statistical Association, 105(490), 493–505.
  2. Deming, W. E. (1986). Out of the Crisis. MIT Press.
  3. Ellis, S., & Brown, M. (2017). Hacking Growth. Crown Business.
  4. Goldratt, E. M., & Cox, J. (1984). The Goal: A Process of Ongoing Improvement. North River Press.
  5. Kohavi, R., Tang, D., & Xu, Y. (2020). Trustworthy Online Controlled Experiments. Cambridge University Press.
  6. Pyzdek, T., & Keller, P. A. (2014). The Six Sigma Handbook (4th ed.). McGraw-Hill Education.
  7. Ries, E. (2011). The Lean Startup. Crown Business.
  8. Shewhart, W. A. (1939). Statistical Method from the Viewpoint of Quality Control. Graduate School of the U.S. Department of Agriculture.