Almost

You’ve just wrapped up a product launch that hit 90% of its sales target. The team celebrated the effort, leadership noted the progress, and the post-mortem focused on what went well. But six months later, the initiative was quietly sunsetted—not because it failed dramatically, but because it never quite reached the threshold to justify continued investment. It wasn’t a failure. It was an almost.

This is the almost mindset in action: when outcomes land just short of the mark, they’re often reframed as partial successes, learning experiences, or stepping stones. But in business, almost doesn’t just mean “close.” It means resources spent, attention diverted, and momentum stalled—all without the clear signal of failure that would force a course correction. Unlike outright failure, which demands a response, almost tricks you into thinking you’re on the right track while quietly eroding results.

The Hidden Cost of Almost

Almost outcomes are more dangerous than failures because they don’t trigger urgency. A missed sales target by 10% feels fixable with a little more effort next quarter. A product launch delayed by three weeks seems like a minor hiccup in an otherwise smooth rollout. A hiring process that stalls at final interviews appears to be thorough, not broken. But these near-misses accumulate. They create what psychologists call “false progress”—the feeling of advancement without real results.

Consider a SaaS company that consistently hits 85% of its quarterly renewal goal. Leadership praises the retention team for “strong performance” and invests in expanding the customer success function. Yet year-over-year revenue growth remains flat because the 15% gap represents a structural leak in the business model—one that feels manageable month-to-month but becomes catastrophic over time. The team isn’t failing; they’re almost succeeding, and that’s what prevents them from asking why the gap exists in the first place.

Almost costs you in three ways:

• Resource drain: Time, budget, and talent are invested in initiatives that never reach escape velocity.
• Morale erosion: Teams begin to distrust metrics when “success” is constantly redefined downward.
• Strategic drift: Without clear thresholds for success or failure, it’s impossible to know whether a strategy is working—or just almost working.

Spotting the Almost in Your Work

The first step to overcoming the almost mindset is recognizing it in real time. Almost moments aren’t always obvious—they often hide in plain sight as “good enough” outcomes or “valuable learning.” But they share a pattern: the result is meaningful, but not sufficient to trigger the next phase of investment, scaling, or decision-making.

Think about your last three major initiatives. For each, ask:

• Did we hit the predefined threshold for success?
• If not, did we still treat it as a win?
• What did we not do because we assumed we were “close enough”?

For example, a marketing team launches a campaign aiming for 500 qualified leads. They generate 470. The team leads highlight the “strong engagement” and “high-quality leads” in the debrief, and the campaign is labeled a success. But the sales team can’t hit its pipeline target because of the 30-lead shortfall. No one questions the campaign’s design—they just assume they’ll “do better next time.” That’s an almost moment: a meaningful effort that fell just short of enabling the next step.

To diagnose your own almost patterns, start by listing three recent outcomes where you or your team:

• Met most, but not all, of a key goal
• Received positive feedback despite missing the target
• Continued with the same approach without adjusting the target or method

Write them down. Be specific: include the goal, the actual result, and how the outcome was framed. This isn’t about blame—it’s about calibration. The almost mindset thrives in ambiguity. Naming it is the first step to closing the gap.

To move beyond recognizing isolated almost moments, you need a systematic way to uncover where and why they keep happening. The Almost Audit Worksheet provides a structured method to catalog near-misses across initiatives, categorize them by type, and trace them to underlying root causes. This isn’t about assigning blame—it’s about identifying repeatable friction points so you can adjust systems, not just effort.

The Almost Audit Worksheet

The worksheet has two dimensions: type and cause.

Type describes where the almost occurred in the initiative lifecycle:

• Planning: Goals, scope, or resources were misaligned from the start (e.g., unrealistic targets, missing dependencies).
• Execution: The plan was sound, but implementation faltered (e.g., missed deadlines, inconsistent follow-up, quality gaps).
• Follow-up: Results were achieved, but insufficient to trigger the next step (e.g., hitting 90% of a target that needed 100% to unlock scaling).

Cause identifies why the almost happened:

• Skills: Capability gaps in knowledge, training, or experience.
• Systems: Broken or missing processes, tools, or handoffs.
• Signals: Poor or delayed feedback that prevented course correction.

By plotting each almost moment on this grid, you shift from vague frustration (“we keep falling short”) to precise diagnosis (“our follow-up consistently fails due to weak signals”).

Consider a B2B software company that repeatedly fell 10–15% short of its quarterly upsell target. Using the worksheet, they tagged each quarterly shortfall as a follow-up type almost—meaning they hit the activity goal (e.g., 100 outreach attempts) but not the outcome goal (e.g., 20 upsells). Digging into cause, they found:

• Systems: No automated trigger to flag when a customer hit usage thresholds indicating upsell readiness.
• Signals: Customer success managers relied on memory or sporadic check-ins to spot opportunities.
• Skills: Some CSMs lacked confidence in discussing pricing or advanced features.

This clarified that the issue wasn’t effort—it was a broken follow-up system. Fixing it meant implementing usage-based alerts, refining the CSM playbook, and adding micro-training on value-based conversations. The next quarter, upsell attainment jumped to 95% of target.

Completing Your Own Audit

Start with three recent initiatives where you experienced an almost outcome. For each, fill in one row of the worksheet:

1. Describe the goal and actual result.
2. Judge whether the gap lived in planning, execution, or follow-up.
3. Hypothesize the root cause—skills, systems, or signals—and note evidence for your choice.

Look for patterns. If most of your almosts cluster in one cell (e.g., follow-up/signals), you’ve found a leverage point. If they’re scattered, examine whether inconsistent goal-setting (planning/skills) is creating noise that masks deeper issues.

Try This

This week, run a mini-audit on one current project:

• Identify one recent milestone where you missed the target but still moved forward.
• Classify it by type (planning, execution, follow-up) and cause (skills, systems, signals).
• Share your hypothesis with a teammate and ask: “What’s one small fix we could test in the next two weeks?”

Key Takeaways

• Almost patterns repeat when the same type-cause combination goes unaddressed.
• The Almost Audit Worksheet turns vague near-misses into actionable diagnostic data.
• Fixing systems and signals often yields faster results than trying to upskill alone.
• Naming the almost is not admitting failure—it’s installing an early-warning system for your strategy.
• Consistent almosts in follow-up often point to missing leading indicators or delayed feedback loops.

Imagine setting a goal that feels clear, only to realize weeks later that you and your team were aiming at different targets. This disconnect is where almosts are born—effort expended, but outcomes fall short not for lack of trying, but because the goal itself left room for interpretation.

Why Goals Breed Almosts

Vague or poorly structured goals create ambiguity that manifests as almost outcomes. When a goal lacks precision, teams interpret success differently, effort becomes misaligned, and feedback loops break down. You might hit activity metrics but miss the outcome because the goal didn’t specify what success looked like, how it would be measured, or who was accountable. This gap between intention and result is fertile ground for almosts to take root.

Consider a marketing team tasked with "improve lead quality." Without clarity, one member focuses on increasing form completions, another on scoring leads higher in the CRM, and a third on reducing spam submissions. After a month, each reports progress, but sales still complains about poor lead quality. The almost here isn’t laziness—it’s a goal that allowed multiple interpretations of success, diluting impact.

The SMART-Plus framework closes this gap by adding two critical dimensions to the classic SMART criteria: Visibility and Ownership. These ensure goals are not only well-defined but also transparent and accountable.

Take the earlier example: "improve lead quality." A SMART-Plus version might read: "Increase the percentage of marketing-qualified leads that sales accepts as sales-qualified from 60% to 75% by September 30, tracked weekly in the CRM dashboard, owned by the Demand Generation Manager." This version eliminates ambiguity—everyone knows the target, how it’s measured, who’s responsible, and when it’s due.

Now apply this to your own work. Pick one current goal that has felt fuzzy or produced almost results. Rewrite it using all six SMART-Plus elements. Test it by asking: Could a stranger on the team understand exactly what success looks like, how we’ll know we’ve achieved it, and who’s in charge? If not, refine until the answer is yes. This clarity is the first line of defense against almosts.

Clear goals set the direction, but without systems to monitor progress, almosts can still slip through unnoticed. Even well-defined targets fail when teams lack real-time signals that warn of drift before it becomes a gap. The key is to install leading indicators—measurable signs that predict outcomes—and feedback loops that surface issues early, allowing course correction while there’s still time to act.

Designing Leading Indicators That Predict Almosts

Lagging indicators, like quarterly revenue or final product adoption, tell you what already happened—too late to prevent an almost. Leading indicators, by contrast, change before the outcome, giving you a window to intervene. Examples include weekly confidence scores, milestone completion rates, or early user engagement metrics. The best leading indicators are actionable, tied directly to the goal, and reviewed with enough frequency to catch trends.

Consider a product team preparing for a major feature launch. Their lagging indicator is launch date adherence—a binary hit or miss that only becomes clear at the end. To catch delays earlier, they implement a weekly “confidence vote”: each core member (product, engineering, design) rates their confidence in hitting the date on a scale of 1–5, with explanations for scores below 4. Over six weeks, the average score trends downward from 4.8 to 3.2, driven by recurring blockers in dependency integration. The team sees the pattern two weeks before the deadline, reallocates resources to resolve the bottleneck, and launches on time. Without this signal, the almost—missing the date by days—would have been a surprise.

To build your own leading indicator system:

1. Identify the outcome you want to predict (e.g., hitting a sales target, avoiding a bug escape).
2. Ask: What changes weeks before success or failure becomes evident? Look for behaviors, metrics, or sentiments that correlate strongly with the result.
3. Choose one or two simple, observable signals (e.g., pipeline coverage ratio, daily build stability, customer sentiment in early access).
4. Set a threshold that triggers review (e.g., “if pipeline coverage drops below 3.0x for two weeks, convene a deal clinic”).
5. Assign ownership and visibility—track the indicator in a shared space and update it weekly.

Closing Feedback Loops for Faster Correction

Indicators only work if they trigger action. That’s where feedback loops come in: structured moments to review data, diagnose causes, and decide on adjustments. The tighter the loop, the faster you can respond to an almost-forming signal. Weekly pulse checks, milestone gates, or stand-up reviews serve this purpose—if they’re designed to surface truth, not just report status.

A sales team struggling with quarterly forecast accuracy installs a biweekly deal health review. Instead of reviewing only closed-won deals, they examine every deal in the pipeline over a certain size, asking: Is the close date still realistic? Have we validated the economic buyer? Is the mutual action plan updated? By surfacing stalled deals two weeks before the forecast deadline, they adjust commits early, reducing forecast variance by 40% in one quarter.

Effective feedback loops share three traits:

• Regularity: Frequent enough to catch drift (weekly or biweekly for most initiatives).
• Focus: Centered on predictive signals, not just activity.
• Psychological safety: Designed to surface problems without blame, so issues are raised early.

To strengthen your feedback loops:

• Audit your current review meetings: Do they reveal emerging risks, or only confirm what’s already known?
• Add one leading indicator to the agenda and ask: “What does this suggest about our trajectory?”
• End each loop with a clear decision: continue, adjust, or escalate.

Try This

This week, install a simple early-warning system for one of your current projects:

1. Pick a goal that has historically produced almost results (e.g., a launch date, a conversion target).
2. Identify one leading indicator you can track weekly (e.g., confidence score, milestone completion rate, early engagement metric).
3. Set up a shared tracker (a spreadsheet or dashboard column) and review it in your next team meeting. Ask: Does this signal suggest we’re on track, or do we need to adjust?

Key Takeaways

• Leading indicators turn almosts into early warnings by signaling risk before outcomes are fixed.
• Effective feedback loops combine regularity, focus on predictive data, and psychological safety to enable fast correction.
• Ownership and visibility—carried forward from SMART-Plus—ensure that signals are monitored, discussed, and acted on consistently.

Imagine you just missed hitting your quarterly revenue target by 5%. The team celebrates the effort, but you feel a lingering unease. That gap isn’t failure—it’s an almost. And almosts, left unexamined, become blind spots that erode progress over time.

The Almost-to-Action Loop: A Weekly Practice for Turning Near-Misses into Momentum

The Almost-to-Action loop is a four-step rhythm designed to transform recurring near-misses into deliberate improvements. Unlike post-mortems that wait for failure, this loop runs weekly on one persistent almost pattern—small enough to manage, significant enough to matter. Each step builds on the last: you notice the almost, name the underlying gap, extract a concrete lesson, and apply a specific fix. Over time, this practice shifts your mindset from celebrating near-successes to engineering consistent wins.

Consider a founder who repeatedly almost missed sending investor updates. The updates went out, but always late, causing anxiety and eroding trust. Using the loop, she noticed the pattern (almost missed updates), named the gap (poor time blocking despite knowing the deadline), extracted the lesson (her calendar lacked protected time for recurring tasks), and applied the fix (a recurring 90-minute calendar guard every other Friday). Within two months, updates shipped early, and the almost vanished.

Running Your First Loop: From Observation to Action

Start by selecting one almost that repeats—a metric just shy of target, a handoff that’s always delayed, a meeting that nearly derails. Apply the loop in writing, using this structure:

1. Notice the almost: Describe what happened and how close it was.

Example: "Sales team hit 92% of quota three months in a row; celebrated each time, but never triggered bonus."

1. Name the gap: Use the Almost Audit Worksheet’s dimensions—type (planning, execution, follow-up) and cause (skills, systems, signals)—to pinpoint why it happened.

Example: "Follow-up type, systems cause: no automated tracking to flag when reps fall below 95% pace by mid-month."

1. Extract the lesson: State one clear insight about what the almost reveals.

Example: "We rely on lagging indicators; by the time we see the gap, it’s too late to correct."

1. Apply the fix: Define a small, testable action to try for the next cycle.

Example: "Add a leading indicator: weekly pipeline coverage report shared every Monday; if below 1.2x, trigger a deal-review huddle."

Repeat this loop weekly on the same almost until the gap closes. Then move to the next pattern. The goal isn’t perfection—it’s progress. Each loop tightens the feedback between what you almost did and what you actually do, turning near-misses into the fuel for reliable performance.

When almosts go unexamined in a team setting, they create a culture of silent drift—where near-misses are shrugged off as “close enough,” and systemic issues fester unseen. The danger isn’t just missed targets; it’s the erosion of psychological safety when problems are ignored until they become crises. To break this cycle, teams need a structured way to reflect on almosts that feels safe, productive, and habitual—without veering into blame or vague retrospection.

The key is to normalize almost-reflection as a routine practice, not a reaction to failure. By treating near-misses as data points rather than disappointments, teams can uncover patterns in planning, execution, or follow-up that individuals might miss. This shifts the focus from “who dropped the ball” to “what in our system allowed the gap to persist?”—turning almosts into collective learning fuel.

Designing a Blame-Free Almost Reflection Ritual

Start small and consistent: a monthly “Almost Hour” where the team examines one recurring near-miss using the Almost Audit Worksheet. The goal isn’t to solve everything at once but to build muscle memory for spotting and acting on gaps before they widen.

Begin by selecting an almost that has happened at least twice—a sales demo that consistently runs long, a client onboarding step that’s frequently delayed, or a sprint goal that’s repeatedly missed by 10–15%. Frame it as a pattern worth understanding, not a failure to fix. Then, guide the team through the four steps of the Almost-to-Action Loop together:

1. Notice the almost: Agree on what happened and how close it was. Use specific metrics or observations.

Example: “In the last three sprints, we completed 85% of committed story points; each time, we said we’d do better next sprint.”

1. Name the gap: Apply the worksheet’s type and cause dimensions as a team. Ask: Was this a planning, execution, or follow-up issue? Did it stem from skills, systems, or signals?

Example: “Execution type, systems cause: no shared definition of ‘done’ for tasks, leading to inconsistent effort estimation.”

1. Extract the lesson: Vote on one clear, actionable insight. Avoid vague takeaways like “we need to communicate better.”

Example: “We overestimate capacity because we don’t account for context-switching time between tasks.”

1. Apply the fix: Agree on one small experiment for the next cycle. Make it testable and time-bound.

Example: “Add a 15-minute capacity planning buffer in sprint planning to account for meetings and unknowns; review its impact in the retrospective.”

After the session, document the almost, the gap named, the lesson, and the fix in a shared log. Revisit it next month to see if the experiment closed the gap—or revealed a new layer to address.

Case Study: How a Support Team Turned Repeat Almosts into Reliability

A technical support team at a mid-sized SaaS company noticed they were almost hitting their SLA for first-response time—averaging 58 minutes against a 60-minute target. Each week, they celebrated being “under an hour,” but the pattern persisted, causing subtle customer frustration and internal pressure.

Using the Almost Hour ritual, they worked through the loop:

• Noticed the almost: First-response time was 58±2 minutes for six weeks straight.
• Named the gap: Follow-up type, systems cause: ticket routing relied on manual triage, causing delays during shift changes.
• Extracted the lesson: “We’re fast most of the time, but our system creates avoidable lag at predictable moments.”
• Applied the fix: Tested an auto-routing rule that assigned tickets based on agent availability and skill tags during shift overlaps.

After four weeks, average response time dropped to 52 minutes. The almost was gone—not because they worked harder, but because they fixed a hidden systems flaw. Over the next quarter, repeat almosts in response time dropped by 40%, and the team began using the Almost Hour to address other patterns, like knowledge-base article gaps and escalation delays.

This shows how normalizing almost-reflection doesn’t just close single gaps—it builds a team’s capacity to detect and correct systemic drift before it scales.

Try This: Launch Your Team’s First Almost Hour This Week

1. Pick one recurring almost your team has experienced at least twice in the past month—something that’s “almost” on target but never quite there.
2. Schedule a 30-minute session to run the Almost-to-Action Loop together, using the four steps above. Focus on understanding, not fixing everything.
3. Document the outcome in a shared space: what you noticed, the gap you named, the lesson, and the fix you’ll test. Commit to reviewing it in four weeks.

Key Takeaways

• Almosts are systemic signals, not individual shortcomings—treat them as data to uncover hidden gaps in planning, execution, or follow-up.
• A regular, blame-free reflection ritual like the Almost Hour builds team resilience by turning near-misses into structured learning opportunities.
• Fixing one almost at a time—through small, testable experiments—creates compounding improvement in reliability and trust over time.
• The Almost-to-Action Loop works for individuals and teams; scaling it starts with making reflection habitual, not heroic.
• Momentum comes not from avoiding almosts, but from learning to harvest them—for insight, innovation, and consistent progress.