working on the right problems

i have been reading atomic habits recently.

it is one of those books that feels simple on the surface but keeps lingering in your mind long after you close it. the core idea is almost obvious once you hear it. progress is rarely about dramatic change. it is about small systems that quietly shape what you do every day. not motivation. not bursts of discipline. systems.

the interesting part is how universal that idea is. the book talks about personal habits, but once you start thinking about it, the same logic applies to almost everything else. companies. products. engineering teams. a lot of things that look like sudden success are really just habits that compounded quietly over time.

the engineering version of habits

in software, habits show up as systems.

things like how code gets reviewed. how problems get investigated. how teams decide what matters and what does not. none of these decisions look dramatic on any single day, but over months they shape the entire trajectory of a product.

• a team that ships carefully structured systems will slowly accumulate stability.
• a team that improvises everything will slowly accumulate chaos.

both outcomes look similar at the beginning. the difference only becomes visible over time.

reading atomic habits made me think about how much of building a company is really about designing these invisible patterns. what you default to when things get busy. how you recover when something breaks. how often you revisit assumptions. the habits of the system become the habits of the company.

compounding in strange places

one thing i find fascinating is how compounding rarely happens where people expect it. people expect breakthroughs to come from big ideas. sometimes they do. but more often they come from quiet repetition.

• a small improvement in how something is designed.
• a small improvement in how a team works together.
• a small improvement in how decisions get made.

over time those improvements stack on top of each other until suddenly something feels different. more stable. more capable. more difficult to replicate.

the outside world sees the outcome and assumes it appeared suddenly. the people inside know it was the result of hundreds of small adjustments.

the work happening at sagea

a lot of what we have been doing at sagea recently fits into this pattern. over the past months we have been spending a significant amount of time on identity systems. specifically the infrastructure behind identity verification and kyc.

it started as research.

understanding how these systems behave in real environments. mapping out where the bottlenecks appear. studying the assumptions that most existing solutions are built around. what we found was interesting. many identity systems were designed in a different distribution environment. lower onboarding volumes. more predictable inputs. slower growth curves. when those assumptions change, the systems start developing friction in unexpected places.

so we went deeper.

a lot of r&d went into understanding how identity infrastructure should behave when scale, reliability, and messy real world inputs all collide at once. the kind of work that does not produce immediate announcements but slowly shapes the architecture of what you build next. that work has started turning into something more concrete. we are building something around it now. still early, still evolving, but we can feel the outcome.

it is one of those projects that came directly from sustained curiosity rather than a sudden idea.

habits inside the company

thinking about atomic habits also made me reflect on how companies develop their own behavioral patterns. small teams especially; if the default habit is rushing everything, the product eventually reflects that. if the default habit is careful iteration, that shows up too. over time these patterns become culture. not the kind of culture written on websites, but the real one. the one that determines how problems get solved when no one is watching.

for us, a lot of the focus has been on building systems that reward careful thinking. taking the time to understand problems properly before rushing toward solutions. investing in infrastructure that might only show its value months later.

those habits are starting to compound in interesting ways.

the long curve

small improvements do not look impressive at first. the curve is almost flat in the beginning. it only becomes visible once enough iterations have stacked together. this applies to personal habits. it applies to engineering systems. and it definitely applies to startups. most of the meaningful work happens during the part of the curve where progress still looks invisible. that is where we are spending a lot of time right now.

building small systems. refining small assumptions. letting the compounding happen slowly. if the ideas in that book are correct, the results of those habits will become visible eventually.

until then, the only thing to do is keep building.