The question I did not ask

When I walked into a broken system, my instinct was to fix it.

That instinct served me well. I found the problems, traced them to their roots, and fixed them one by one. Over time the system stabilized. The team started owning things. The product stopped bleeding.

But there was a question I never asked in those initial months. I did not ask what the company needed to survive.

Not because I was not curious. Because I was an engineer, and engineers ask engineering questions. What is broken. Why is it broken. How do we fix it. Those questions felt like the whole job.

They were not.

Understanding the full situation before narrowing into the problem. That is the part I skipped.

The economic reality of the company was not something I walked in asking about. How much it was spending. How far it was from profitable. What it needed to get there.

I assumed that if the product was stable, everything else would follow. I was wrong about the order.

I figured it out eventually. The cost work, the path to profitability. I got there. But I got there by following problems as they surfaced, not by understanding the stakes from the start. The two are different paths. One of them is slower.

The slowness had a cost I could not control. People I had worked alongside lost their jobs. Some of them I had known from before. I had not asked the question that would have told me that earlier.

If you are leading a team, the responsibility is different. Your team trusts you with more than the technical direction. They trust you with their time, their bets, their careers. Understanding the reality of the company you are all working inside is not optional for a leader. It is the minimum.

The hardest part of that role was not the broken system. It was letting people go. People I had worked alongside, people I had brought in. I had turned the product profitable. But I had not moved fast enough. I always wonder if I had understood the full picture earlier, would I have saved them.

There is a question worth asking early in any role, especially when you are walking into something broken.

What does this company need to survive and how does my work connect to that?

That question does not replace the engineering. It gives it direction.

I learned that late. I would ask it first now.