People ask me for the lessons. Usually they want a list. Five things. Seven principles. A framework they can screenshot and send to their team.
I understand the impulse. I had the same one for years. But the honest lessons from 35 years of building companies are not clean. They are messy, contradictory, and often painful. Here are the ones I think matter most.
When I founded WLC College India, I thought I was solving an access problem — giving students in India access to international-quality education in fashion, design, and business. That was real. But the deeper problem, the one I didn't see for years, was a relevance problem. The market didn't need another college. It needed an institution that could bridge the gap between what students learned and what the industry actually needed.
Once we reframed around relevance, everything changed. 50,000+ alumni later, the institution works. But it works because we eventually solved the right problem, not the first one.
The startup world worships speed. Move fast and break things. Ship it. Iterate. There is truth in this — paralysis is real, and perfection is the enemy of progress.
But I have also seen speed destroy more value than it creates. Teams moving fast on a wrong interpretation. Products shipped before the market was understood. Fundraises closed before the business model was validated. In every case, the speed felt productive. The results said otherwise.
The most valuable thing I learned to do was slow down at the right moments. Not all moments. The moments where the interpretation matters more than the action.
I spent my early years thinking about people in terms of roles and outputs. What does this person produce? How efficiently? Can they be replaced?
This mindset works at small scale and short horizons. It fails completely when you are trying to build something that lasts. The institutions that endure — WLC is now decades old — endure because they are built on relationships, not transactions. The people who stayed through the hard years stayed because they believed in what we were building together, not because their compensation was optimal.
This one took the longest to learn. When something goes wrong in a company, the natural response is to find the person or process that failed. But the deeper pattern I kept discovering was that the failure originated in how the organisation saw reality — the frame it used to interpret what was happening.
At GoodSpace, when we struggled with a product direction, the temptation was always to blame execution. Ship faster. Work harder. But the real problem, almost every time, was that we had not examined our own assumptions thoroughly enough. We were executing well on a misunderstanding.
This pattern is what eventually led me to build the SIV Method.
I did not start writing because I wanted to be an author. I started writing because I could not think clearly enough without it. Building a company generates an enormous amount of experience. But experience without examination is just time spent. Writing forced me to examine what I had actually learned versus what I had merely survived.
AI For Business Leaders came from that process. So did The SIV Method. Both books are attempts to distill decades of building into something transferable — not advice, but frameworks for thinking that might help someone avoid the mistakes I made.
Thirty-five years taught me that most failure begins in misunderstanding. That the mind wants relief more than reality. That the organisations we build are only as good as the quality of thinking inside them. And that understanding, properly earned, is the most valuable thing a leader can produce.
Everything else follows from that.