The Last Pickaxe: Reflective Practice, Hyperfocus, and a Founder’s Decision to Continue FA

Essay · Retrospective Practitioner Reflection

Persistence becomes mature when it can examine and revise its own reasons.

About this essay

This is a first-person reflection on my experience of building K2Quant over roughly fifteen years. The turning point described here emerged in a coaching-style dialogue and the self-inquiry that followed; it was not a formal coaching engagement, clinical assessment, or research protocol. I use hyperfocus as a descriptive concept for an experience of intense, narrowing absorption, not as a diagnosis. Published research helps locate the experience conceptually, but it does not establish that reflective practice caused the change I describe or that it is an effective intervention for hyperfocus. No investor, client, employee, or participant details are included.

For roughly fifteen years, I have been building K2Quant.

The system has changed many times. Strategies have improved. Bugs have been found and removed. Architecture has been rebuilt. Parts that once failed now work. The project has not stood still.

Yet progress and arrival are not the same thing.

For years, I have carried an image that circulates in motivational stories: a miner digs toward a seam of gold, stops one strike too early, and walks away without knowing how close he was. The image can preserve courage. It can also become a trap. Every unfinished year can be interpreted as evidence that the next strike may be the decisive one.

That was the question underneath my work:

What if the next pickaxe strike is the last one—and I stop just before it?

K2Quant is not only a technical project or private ambition. It also carries responsibility: to people who have trusted the work, to resources already committed, and to a system whose progress I can see even when the destination remains uncertain. That responsibility made stopping feel morally heavier than changing a product plan.

A recent reflective conversation did not tell me whether to continue or stop. It changed the question. Instead of asking only, “How many more strikes should I make?” I began asking:

What is making me raise the pickaxe again—evidence, hope, fear, identity, responsibility, or a commitment I still consciously choose?

That question became more consequential than the metaphor.

Table of contents
  1. The last-pickaxe story contains both courage and danger
  2. Reflective practice changed the object of the decision
  3. Fear, hope, and commitment were all present
  4. A review date alone does not break the loop
    1. Define what the period is testing
    2. Choose evidence before seeing the outcome
    3. Define more than success
    4. Make the alternatives explicit
    5. Audit the reason for extending the period
  5. Hyperfocus can be both an asset and a narrowing context
  6. A founder must govern more than the company
  7. The personal experience becomes a learning-transfer question
  8. What changed—and what remains unproven
  9. Conclusion: perhaps the last pickaxe is a question
  10. References

The last-pickaxe story contains both courage and danger

Entrepreneurship often requires action before certainty exists. A founder cannot demand proof of success before building the thing that might produce the proof. Persistence is therefore not automatically irrational. A difficult quarter, a failed experiment, or a technical setback may be part of a credible learning process.

But persistence can also become self-protective.

Research on escalation of commitment describes the tendency to continue investing in a course of action despite discouraging evidence. Joel Brockner reviewed how self-justification can contribute to this pattern: stopping may force a decision-maker to face the possibility that earlier time, money, and identity investment did not produce the intended result. Research on entrepreneurial reinvestment has likewise examined whether decisions to expand, maintain, or contract a venture are shaped only by expected future value or also by escalation pressures (McCarthy, Schoorman, and Cooper, 1993).

The last-pickaxe image intensifies this tension because it makes an unknowable future feel visually close. It does not say that the next strike is the breakthrough. It says that stopping removes the possibility of discovering whether it was.

That possibility is real. It is not sufficient evidence.

The rational question is not whether I have already spent fifteen years. Those years cannot be recovered by either continuing or stopping. The more useful questions concern the future:

  • What has changed in the system recently?
  • Which hypothesis is the next period testing?
  • What evidence would increase or reduce confidence?
  • What alternatives am I not examining because K2 occupies most of my attention?
  • Under what conditions would continuation, redesign, or stopping each become the responsible choice?

Past investment gives the decision emotional weight. It should not be allowed to answer these questions by itself.

Reflective practice changed the object of the decision

I entered the conversation thinking the problem was time allocation. K2 needed attention. My English and migration plans also needed attention. When K2 was unstable, I stopped moving elsewhere. I had become accustomed to the pressure of the project, but the feeling of falling behind in other parts of life was consuming energy.

The conversation moved beneath scheduling.

At one point I completed a sentence:

If K2 fails, it means I wasted my life.

The sentence carried more than a business judgment. It connected the outcome of one project to the meaning of fifteen years of living. Under that frame, stopping could not be a strategic decision. It could only be a verdict on who I had been.

Then another account became available: I had built, learned, endured, changed, and lived through those years. The intended result still mattered, but it was no longer the only possible measure of the time. That did not make failure desirable. It separated the project’s outcome from the total value of the life around it.

The immediate effect was calm.

I do not treat that moment as proof of transformation. A meaningful realization inside a supported conversation can disappear when pressure returns. But it illustrates what reflective practice can do. It can change the object of attention from the external problem alone to the assumptions and meanings organizing the problem.

Donald Schön distinguished reflection on action from reflection in action. In my experience, both were present. I looked back on a long pattern, but I also noticed the pattern while making a live decision about continuation. Research by Di Stefano and colleagues similarly suggests that reflection on accumulated experience can, under some conditions, contribute more to learning than simply adding another round of practice. The benefit depends on what experience exists, when reflection occurs, and how it is conducted.

The lesson was not “thinking is better than doing.” It was that another unit of action is not always the missing input. Sometimes the missing input is a better relationship with the experience already accumulated.

Fear, hope, and commitment were all present

When I listened more carefully, the drive to continue did not come from one source.

There was fear: What if stopping damages trust? What if I later discover I was close? What if the project’s outcome changes how I judge my own life?

There was pressure: I am thirty-six. Work, income, migration, relationships, and time do not wait outside the laboratory while one project reaches certainty.

There was also hope: the system continues to improve, and the next changes may matter.

And there was commitment: I still find meaning in solving the problems themselves. When I remove one part of a bug—even before the entire bug is gone—I experience real progress. The work is not valuable to me only after a final treasure appears.

That distinction mattered. If every strike had value only as a promise of gold, continuation would be almost entirely hostage to an uncertain outcome. Because the craft, learning, and incremental improvement also matter, the decision contains something more than fear of loss.

This is what I mean by conscious commitment. It is not commitment without fear. It is commitment that can see fear, responsibility, hope, identity, and evidence without allowing any one of them to remain invisible.

Fear can be in the vehicle without being the driver.

That sentence is useful only if it changes the design of the decision. Calling commitment “conscious” does not make indefinite continuation responsible. A person can become highly articulate about a loop and still remain inside it.

A review date alone does not break the loop

My first practical answer was to set a future review point. I would make specific changes, observe their effect, and reassess against a KPI.

Then another problem became visible: a three-month review can simply turn one endless loop into a series of three-month loops.

At each review, the founder can say:

  • the signal is not clear yet;
  • the latest change needs more time;
  • the next version will be more representative;
  • one more cycle will finally reveal the answer.

A date creates a pause. It does not guarantee inquiry.

The review becomes different only when some of its logic is defined before the result is known. Chip Heath’s work on mental budgeting suggests that setting and tracking resource boundaries can help explain when people escalate or de-escalate commitment. In practice, a founder needs more than a calendar reminder. The decision requires a small evidence architecture.

For my own work, that architecture can be expressed as:

change or hypothesis
-> observable evidence and KPI
-> review date
-> thresholds for success, ambiguity, and failure
-> continue, redesign, pause, or stop
-> record what was learned and why the next decision changed

Each part matters.

Define what the period is testing

“Improve K2” is too broad. A review period should test a named change: a strategy revision, a reliability improvement, a market assumption, a risk control, or a path to revenue.

Choose evidence before seeing the outcome

A KPI selected afterward can become a story about whatever happened. The relevant signal, its baseline, and the expected direction should be named in advance where possible.

Define more than success

A binary pass-or-fail threshold may hide useful ambiguity. It is better to distinguish at least three states: evidence supporting continuation, evidence requiring redesign, and evidence that weakens the case enough to pause or stop.

Make the alternatives explicit

The choice is rarely only “continue exactly as before” or “abandon everything.” A strategy can change while the company continues. A product can pause while a capability survives. A project can end while its accumulated learning moves elsewhere.

Audit the reason for extending the period

At the review, I need to ask whether a new cycle is justified by new evidence and a changed hypothesis—or by the same hope using newer language.

This does not eliminate judgment. It makes judgment inspectable.

Hyperfocus can be both an asset and a narrowing context

The word hyperfocus gave me another way to describe the pattern. I use it cautiously.

The research literature does not offer one settled definition. Ashinoff and Abu-Akel describe hyperfocus as intense absorption in a task to the point that other information is tuned out, while also emphasizing how limited and inconsistent the research remains. Hupfeld, Abagis, and Shah found greater self-reported hyperfocus among adults with higher ADHD symptom levels. But Groen and colleagues did not find that adults with ADHD experienced hyperfocus more frequently than healthy controls, although hyperfocus related positively to ADHD traits. The phenomenon is therefore not unique to ADHD, and the term should not be used casually as a clinical conclusion.

As an experiential description, however, it fits part of my work.

Intense focus has helped me build technical depth, remain with difficult problems, notice small inconsistencies, and continue through periods in which external rewards were weak. The same focus can narrow the field until other obligations, alternatives, or signals become less available. It can make a local improvement feel like sufficient evidence for the global direction. It can also make disengagement feel like a threat to identity rather than a normal executive function.

The question is not how to destroy intense focus. A founder may need it.

The question is whether attention can regain width when the decision requires it.

In this episode, reflective practice created a temporary exit from the tunnel. It helped me observe the focus, name what it protected, and place conditions around its continuation. That is a first-person observation, not evidence that reflective practice treats hyperfocus. I have not found direct research establishing such an intervention claim.

A more defensible hypothesis is narrower:

Reflective practice may help some people notice when intense focus has become the context governing their judgment, creating a chance to examine alternatives before continuing automatically.

Whether that chance becomes a stable capacity remains open.

A founder must govern more than the company

A founder’s work is often described through what is being built: product, strategy, team, capital, distribution, and operations. But the founder is also part of the company’s decision environment.

My attention determines which problems receive years. My identity affects which evidence feels threatening. My responsibilities shape how costly stopping appears. My hope influences how ambiguous signals are interpreted. These are not private psychological details outside the company. They can affect resource allocation, opportunity cost, and the lives of other people.

This is why reflective practice belongs inside leadership, not beside it.

A company can have dashboards while its founder remains governed by an unexamined frame. KPIs can measure progress inside a strategy without asking whether the strategy should still organize the work. Reflection adds a second layer of governance:

  • What assumption makes this metric meaningful?
  • What am I protecting by continuing?
  • Which evidence have I treated as noise because it threatens the story?
  • What alternative would I consider if I had not made the previous investment?
  • What would a responsible stop preserve rather than destroy?

This resembles double-loop learning. The first loop asks how to improve execution. The second examines the governing assumptions, goals, and criteria by which execution is being judged.

The point is not to turn every founder decision into therapy or endless introspection. Reflection that never returns to action can become another avoidance strategy. The practical cycle is action, evidence, reflection, and revised action.

A founder does not become mature merely by refusing to quit. Maturity includes the capacity to continue, pivot, pause, or stop without allowing past investment alone to choose.

The personal experience becomes a learning-transfer question

This essay is connected to a larger inquiry already present in my work.

In Can the Learner Carry the Context?, I ask whether a person can carry a capacity for inquiry, reflection, and choice after the classroom, facilitator, or supportive environment changes. In What Remains When the Learning Space Disappears?, I distinguish performance inside a supportive context from learning and durable transfer.

This K2Quant experience gives that abstract question a personal test case.

The awareness described here arose inside a particular context: time to pause, a coaching-style dialogue, repeated questions, and enough safety to say that failure might mean I had wasted my life. The context helped produce access to the insight.

What happens tomorrow when that context is absent?

What happens when a production failure demands immediate attention, a market result disappoints, responsibility toward other people intensifies, or the familiar reward of solving one more technical problem pulls me back into the tunnel? Do I still notice the pattern? Can I reconstruct the questions without another person holding the conversation? Can I build a review structure strong enough to survive urgency?

Research by Griggs and colleagues is relevant here. Their interviews with human-resource professionals suggested that transfer of reflective learning into work was uneven. Participants did not simply reproduce formal techniques, but some appeared to translate the learning into a more meaningful reflective practice. Context, supportive processes, and the learner’s readiness all mattered.

That finding does not answer my case. It sharpens it.

The important outcome may not be whether I repeat the exact questions from one conversation. It may be whether I can recreate a reflective relationship with my own experience when the surrounding conditions change.

What changed—and what remains unproven

Something real changed in the decision.

I moved from an indefinite story—“one more strike may be the last”—toward a conditional commitment with an explicit hypothesis, evidence, review point, and alternatives. I could see that hope, fear, responsibility, craft, and identity were all participating. I could also see that a local sense of progress does not automatically validate the whole direction.

That is meaningful. It is not yet durable transfer.

I do not yet know:

  • whether the reflective capacity will activate under a different kind of pressure;
  • whether I can notice hyperfocus early enough to widen attention rather than only explaining it afterward;
  • whether the KPI and review structure will constrain escalation or merely give it a more sophisticated vocabulary;
  • whether the insight generalizes beyond K2Quant;
  • whether another founder would experience the same process; or
  • whether reflective practice can reliably help people work with hyperfocus without weakening the productive depth it can provide.

The next context will provide evidence that this conversation could not.

Conclusion: perhaps the last pickaxe is a question

For years, the last-pickaxe image asked me to continue because breakthrough might be close.

Reflective practice did not remove that possibility. It added another one: perhaps the decisive act is not always the next strike. Perhaps it is the capacity to see why I am striking, what the strike is testing, what evidence it produces, and what would justify choosing another tool—or leaving the mine.

Persistence remains part of my identity as a founder. I do not want to replace it with caution disguised as wisdom. But I also do not want persistence to become a story that makes every additional investment appear responsible.

The commitment I want is not blind and not fear-free. It is revisable, evidence-aware, and chosen again with open eyes.

This leaves me with two connected questions:

Can reflective practice help people who experience hyperfocus notice and leave its narrowing tunnel without destroying the depth and energy that make it valuable?

And when the context changes, does that reflective awareness travel with them—or was the original context carrying more of it than they knew?

For now, these are questions, not conclusions.

References