My father spent nearly thirty years with the same company. Growing up, I saw that as stability and loyalty. Today, staying somewhere for five years makes people ask: are you still growing?
I have asked myself that question too.
Five years at a startup is not like five years anywhere else. The best way I can describe it is a treadmill that keeps getting faster. You solve one problem, and before you have caught your breath, another one shows up. The pace is relentless. But so is the learning.
That is the most honest description of my five years at SatSure.
What I Came In Thinking
I joined SatSure as a Product Designer. I came in thinking I understood what that meant. Design the product. Understand the user. Make the experience better. Ship it.
That understanding was not wrong. It was just incomplete.
What I did not know then is that finding what works is one problem. Making it repeatable is another. Scaling it is another entirely. Each stage of a product's life brings a different kind of design challenge, and the skills that serve you in one stage are often not the ones you need in the next.
In the early years, everything was about speed and clarity. What is the core problem? What is the simplest thing we can build to test whether we are solving it? How do we get something in front of real users fast enough to find out if we are wrong?
Then the problems changed. The product started to exist in the world. Clients were using it. Patterns were emerging. And suddenly the question was not what to build but how to make what we had built more consistent, more scalable, more trustworthy across very different use cases.
Then it changed again. At some point, the work shifted from building for one client to thinking about how to build for many. How do you design a system that serves an agriculture company and an insurance company and an infrastructure operator, without becoming so generic that it serves none of them well?
Three very different problems. Three very different versions of what product design actually means in practice.
When Design Went Beyond the Product
Somewhere in the middle of those five years, I noticed that the way I was thinking about design problems had started to show up in other kinds of problems too.
In conversations with engineers about how a system should behave. In client meetings where the real question was not about the feature being discussed but about the decision the client was trying to make. In team dynamics where the friction was not about who was right but about two people solving for different versions of the same problem.
Design thinking, at its core, is a way of approaching problems. Start with the problem, not the solution. Understand the person, not just the task. Question the assumptions underneath the brief. Explore before you converge. Work within constraints rather than against them. Iterate toward the answer rather than arriving at it in one move.
I had been applying that process to products. And then, without really deciding to, I started applying it everywhere else.
My title changed over those five years. My responsibilities changed. The rooms I was in changed. But the underlying way of thinking stayed consistent. And I think that is the thing I am most grateful for from this period. Not a specific skill or a specific project or a specific outcome. A way of approaching problems that I now carry into every room I enter.
The Question I Kept Asking Myself
There were moments in those five years when I wondered whether staying was the right decision. Whether moving to a different company, a different domain, a different kind of problem would have built something in me that staying could not.
What I kept coming back to was this: in a startup, five years rarely means doing the same thing for five years. The problems change. The team changes. The company changes. And if you are paying attention, you change with it.
I did not stay because I stopped being curious. I stayed because the curiosity kept finding new things to land on.
And somewhere along the way, I stopped seeing staying as the opposite of growing. I started seeing it as a different kind of growing. Slower in some ways. Deeper in others. The kind that only happens when you are in the same place long enough to see what your early decisions actually produced.
What Five Years Actually Gave Me
A clearer understanding of how B2B products get adopted, not just designed. The experience of watching something I helped build get used, adapted, trusted, and sometimes rejected by real people in real organisations over time. The ability to sit in a difficult room with difficult stakeholders and know, from experience rather than instinct alone, what is actually being asked of me.
And something harder to name. A kind of confidence that comes not from knowing more, but from having been tested more. From having been in enough situations where I did not have all the answers, and having found a way through anyway.
Five years of startup life made me a better designer. Not because I got faster or more technically skilled, though both of those happened too. But because the pace of the problems forced me to get more honest about what design actually is.
It is not about the product. It is a way of approaching problems. And I have not outgrown it.
I have grown into it.