Strategic Decision Architect | Business redesign for Owners & CEOs | Strategy, management systems & transitions | 50+ business architectures
Company: Independent
We are thrilled to have you join us today, welcome to ValiantCEO Magazine’s exclusive interview! Let’s start off with a little introduction. Tell our readers a bit about yourself and your company.
Semen Sokha: I am Semen Sokha, an Architect of Strategic Decisions. I work with business owners and CEOs when a company has outgrown its current model, strategy fails to translate into execution, or the owner has become a bottleneck to growth.
My work focuses on identifying the core constraint holding a business back, redesigning its operating structure, and guiding the implementation of changes through the first 90 days.
I bring 14 years of practical experience, having designed more than 50 business architectures across 40+ industries and worked with over 250 clients. In addition to my consulting work, I own and operate three businesses myself. This gives me a firsthand understanding of the risks, trade-offs, and personal accountability involved in making strategic decisions – not just as an advisor, but as an entrepreneur responsible for real business outcomes.
I typically help businesses address three challenges: restructuring for the next stage of growth, turning strategic decisions into measurable results, and redefining the owner’s or CEO’s role so the business can operate more effectively without depending on one person for everything.
My approach goes beyond providing recommendations. I work alongside business owners to put decisions into practice and turn them into measurable business outcomes.
What was the moment you realized that complexity was holding your company back, and how did that shift your approach to product, operations, or strategy?
Semen Sokha: When we talk about complexity in a company or in the processes we manage, we first need to define what we actually mean by complexity.
Does it mean making something unnecessarily complicated? Perhaps we already have reasonably effective processes, but we make them significantly harder to execute. Or does it mean having too many moving parts, when simplifying them could make the path to profitability much faster and easier? Or perhaps we simply haven’t found the simplest way to do something, so we’ve built a model that works well but could work much more efficiently, without even understanding why we’ve made it so complicated.
I’ve dealt with all these forms of complexity throughout my career.
Especially when I first started running businesses systematically, one of my earliest indicators was my own psychological and emotional state. I paid attention to moments when I felt so dissatisfied with a business that I wanted to shut it down.
At some point, you find yourself thinking: “No, no, we’re not going to close the company just yet. Let’s figure out what needs to change. What isn’t working for us? Which people or processes are causing problems? What’s missing? What would need to be different for me to say, ‘Yes, let’s change this particular element, and then build a more satisfying way of working around it’?”
That was my first indicator that something needed to change.
Later, I began tracking complexity against measurable goals. I would set specific targets with clear deadlines, expecting certain results by a particular date. Then I would compare the actual pace of progress with what I had expected.
Based on the deadlines, results, actions taken, and my own dissatisfaction with particular methods, assumptions, values, or approaches, I would evaluate whether they were genuinely moving me forward. Were they helping me achieve the intended results, or were they getting in the way?
That process helped me determine what needed to be simplified and how simplification could improve results across the product, operations, and strategy.
I don’t improve individual areas of a business simply for the sake of improving them. In fact, that can create even more complexity. I focus on achieving a specific result through the right tools and approaches. If something doesn’t contribute to that result, I question whether it needs to be there at all.
Can you share one specific example of something you simplified (a product feature, process, pricing model, or customer experience) that delivered outsized results?
Semen Sokha: In 2025, I acquired a loss-making company in the education sector. I spent approximately two weeks working full-time, every day, trying to understand how the existing business operated.
I went through folders, spreadsheets, tabs, program workflows, CRM systems, HR software, chats, message histories, saved conversations in messengers, and company documents. Information was scattered across an enormous number of different places.
The more information I gathered, the less sense the overall system seemed to make.
I eventually put together several hundred questions for the previous owner, from whom I was acquiring the company. As we worked through them, it became clear that even he no longer fully understood how the system actually worked or how to transfer its operation to someone else.
The reason was simple: he hadn’t built the system himself. It had been created by various specialists who no longer worked for the company. The result was a structure that had become incredibly difficult to understand and manage, creating considerable psychological and emotional pressure for him. I started experiencing that same pressure as I tried to take over the business.
After examining the reporting system, performance tracking, sales department, specialist workflows, and management mechanisms, I realized one thing: I didn’t want to run a business this way, and I wasn’t going to.
Rather than simply simplifying individual elements of the existing system, I decided to abandon it altogether, even though I had effectively paid to acquire it as part of the business.
I built a new system from scratch using straightforward spreadsheets and simple software tools, each with only one, two, or three essential functions. They did exactly what I needed them to do. Anything more sophisticated would have been unnecessary overhead.
The results were significant.
For example, onboarding a new specialist, which had previously taken 15 days, was reduced to just two days. The new system cost nothing, whereas the previous one had required approximately $600 per month.
It’s difficult to calculate the full time savings because I can’t reliably estimate how much time I would have continued spending managing the old system. But the operational savings were substantial, and the business became much easier to manage.
How do you systematically identify and eliminate complexity across the organization without oversimplifying in ways that hurt quality or value?
Semen Sokha: I once discussed this very question with Vitalik Buterin. His response was essentially this: “We simplify products right up to the point where removing the next component breaks everything or causes the product to lose its critical functionality.”
That’s a principle I strongly relate to.
When it comes to profitability, I call my approach a simple profitability model. The idea is to determine how quickly, and in how few steps, we can generate profit and deliver whatever it is that customers have paid us for.
How much time does it take? How many steps are required?
The closer we get to a continuous, uninterrupted flow of revenue, the more successful our business model becomes. We can move things through faster, introduce fewer delays, and avoid creating unnecessary barriers for ourselves.
To identify complexity systematically as an organization grows, we need to start by asking two questions: What exactly are we trying to improve, and how will we know whether we’ve improved it?
Then we need to examine every proposed addition: another question, another resource, another action, another meeting, another visual element, another slide in a presentation.
Does it make a meaningful difference to the product or the way the business operates? Does it fundamentally improve the outcome?
If not, the proposed improvement should compete for priority with all the other changes we want to introduce.
We evaluate each potential improvement by asking: Will implementing this solve a problem we actually have? Will it produce a meaningful benefit right now?
We assess each one, determine its value, and rank it accordingly. This creates a prioritized list of initiatives, with the most important ones at the top and lower-priority changes further down.
We then focus on implementing the changes that score highly enough to justify the resources they require. Everything else gets postponed.
In practice, many of those postponed initiatives eventually disappear from consideration altogether. People forget about them, they stop feeling so important, or the company simply has no time to implement them. Meanwhile, the business continues to operate perfectly well without those supposed improvements.
That is an important lesson: not every improvement that seems valuable in theory is actually necessary in practice.
What’s the biggest resistance you’ve faced when pushing for radical simplicity, and how did you overcome it?
Semen Sokha: The greatest resistance I encounter is often within myself, particularly when it comes to my own businesses.
My fears, psychological and emotional barriers, and positive or negative past experiences can fundamentally change, and even distort, the way I perceive reality.
You can understand intellectually that something needs to change, yet still be unable to act because you’re afraid. You freeze, look for other things to do, and end up trapped in a cycle of avoidance.
Finding a way out of that trap is one of the hardest parts of the process.
It can be particularly difficult to let go of things you’ve convinced yourself are essential to the business. You may have built up an enormous number of processes that you believe are necessary to keep everything running. But when you finally start removing them, you discover that life becomes easier, the company operates faster, and profitability improves.
That’s when you realize that simplifying things was the right decision all along.
The real challenge is how quickly you can recognize your own mistakes and act on that realization.
I encounter this barrier frequently. Even now, as I look for a way to reach the next level and understand intellectually what needs to happen, I still find it difficult on an emotional level. Those barriers don’t simply disappear because you know what the right decision is.
Learning to move past them is an ongoing process.
For other CEOs who struggle with feature bloat, process overload, or confusing customer journeys, what’s the most important principle or first step you would recommend they take?
Semen Sokha: First, I would recommend bringing in other people and explaining to them how your business actually works.
Try to articulate your processes clearly. Walk someone through the system and show them how it operates, especially if that person has relevant expertise and can critically assess what you’re presenting.
These conversations can be uncomfortable. You may feel embarrassed or find yourself making excuses for why things work the way they do.
But that discomfort can be valuable. It can help you recognize that the way you’ve been operating is not necessarily the way you want to continue operating.
Second, try to identify the simplest possible profitability model.
In my experience, you can often find it by looking back at the earliest days of your company, when it had just started operating. Even then, the business was already generating revenue. Over time, however, we started adding layers of complexity until we turned something relatively simple into a leviathan.
That’s not a sustainable way to operate.
Third, don’t become attached to historical practices or previous investments. Don’t continue using a system or maintaining a process simply because you’ve already invested money, software development time, or employee hours in it.
If something isn’t working, track the results, understand why it isn’t working, and let it go.
If you can’t measure whether something is working, introduce a tracking mechanism first. Observe the results, evaluate what you learn, and then make an informed decision about whether to keep it or abandon it.
The key is to make decisions based on actual results rather than on the time, money, or effort you’ve already invested.
