I did not arrive at this way of thinking through a single defining moment. It came gradually, shaped by moving between very different environments — a regulated bank, a fast-moving consulting platform, a church community platform, a university classroom, and rooms full of founders, policymakers, and investors at a youth forum. Each environment asked something different of me, and each one taught me that the people who last are rarely the ones chasing dramatic leaps. They are the ones who show up, again and again, and get slightly better each time.

The Meaning of One Percent Growth

One percent growth is not a metric I track on a spreadsheet. It is a mindset: that mastery in engineering, in leadership, or in any discipline worth pursuing, is rarely built in a single sprint. It is built in the accumulation of ordinary days — the bug fixed a little faster than last time, the stakeholder conversation handled a little more clearly, the deployment done a little more carefully. None of these moments feel significant on their own. Strung together over months and years, they compound into real capability.

This is why I do not wait for motivation or the "right" project to start improving. Every task, however small, is an opportunity to refine how I think, how I build, and how I communicate.

Adaptability in Changing Environments

Working across a corporate platform, a banking environment, a church community system, and a youth-led forum has meant constantly recalibrating how I operate. What works in a fast-moving consulting engagement does not always translate directly into a regulated, process-heavy institution. What works when coordinating a technical team is not the same as what works when negotiating a partnership with a corporate sponsor.

Adaptability, to me, is not about abandoning standards when the environment changes. It is about protecting the same underlying principles — clarity, reliability, respect for the people you work with — while adjusting the approach to fit the context in front of you.

Growth Through Challenges

Every environment I have worked in has surfaced its own version of difficulty: a system that needed to be more reliable than it was, a timeline that needed to be met despite competing priorities, a partnership that needed patience to build. None of these challenges arrived with a clear playbook attached.

What I have come to appreciate is that challenges are rarely obstacles to growth — they are usually the mechanism through which growth happens. The discomfort of not immediately knowing the answer is often the clearest sign that the situation is asking something new of you. Treating that discomfort as information, rather than as a setback, has been one of the more useful shifts in how I approach difficult work.

Consistency Over Motivation

Motivation is unreliable. It shows up generously on some days and disappears entirely on others, often without explanation. Consistency does not depend on how I feel about a task on a given morning — it depends on a standard I hold myself to regardless of mood, energy, or circumstance.

In practice, this looks unremarkable: showing up to write the same quality of code on a difficult day as on an easy one, preparing for a partnership conversation the same way whether or not I feel ready, following through on a commitment even when a more exciting opportunity appears. It is this unremarkable repetition, sustained over time, that produces results motivation alone cannot.

Never Stop Learning

Technology, teams, and organizations do not stand still, and neither can the way I work. Every role and every partnership has taught me something I did not know before I started — a new framework, a new way of structuring a difficult conversation, a new appreciation for how much operational detail sits behind a system that looks simple from the outside.

I try to treat every project, every collaboration, and every setback as a source of information rather than a final verdict. That posture — staying curious instead of assuming I already know enough — is, I believe, the real engine behind the one percent I am trying to add each day.

Principles I Try to Live By

  • Consistency — showing up to the same standard regardless of mood, deadline pressure, or how visible the work is.
  • Adaptability — adjusting my approach to fit the environment, without compromising on the principles underneath it.
  • Continuous learning — treating every project and every setback as new information rather than a final judgment.
  • Discipline — doing the necessary work on the days it is not exciting, not just on the days it is.
  • Resilience — staying in difficult situations long enough to actually learn from them.
  • Incremental progress — trusting that small, repeated improvements compound into meaningful capability over time.

None of this is about being extraordinary. It is about being reliable — with myself, with the people I work with, and with the standards I have set. I do not expect every day to bring visible progress. I only expect to be slightly more capable than I was the day before, and to keep showing up long enough for that to matter.

“Small progress, repeated consistently, becomes transformation.”