How to survive for a long time in one organization?

The number one thing you can do is write up your “hat” in the organisation that you want to pass on and make it as easy as possible for someone else to occupy it.

If there are aspects of your job, like the legacy systems you are talking about, that only you know about, you need to start the process of documenting those systems so that someone else can take them over.

This isn’t just raw documentation, but you need to build the “how to” guide for them.

Focus on one system first and then present it to the CEO and tell them that you have written up this function because you want to help remove the key person risk of knowledge being only in your head. Also tell them why you are doing it (you want to grow further into the company to bigger opportunities).

As a business owner, I can tell you that this sort of initiative is greatly appreciated and valued.

Once done on a hat, get it to a more junior engineer and help them get in control of that part of the job.

Then repeat as many times as needed.

Even if you don’t find someone to take over some aspect immediately, doing this is very therapeutic anyway and also means that when the opportunity does arrive for you to hand it over, you can!

This will also declutter tour mind and help give that “fresh start” you are after as you won’t have to remember everything.

The best advice I ever got on this was to “give away your legos”. https://review.firstround.com/give-away-your-legos-and-other...

You have to intentionally give away ownership of the things you made and entrust other people to figure them out as well as you did.

> I work in organization for a long time (8+ years) and I really like it. I had a good growth path, and it's still exciting.

Sounds like you should be telling us how to survive for a long time in one organization.

I don't get what the problem is - Meetings? (everyone has meetings). Being asked to support legacy stuff?

You are 2 people, one with a bunch of skills to offer a new job and another with in depth knowledge at the current company. You could refuse to use those skills in your current company, but that's a big part of the value you represent in that orginisation. You could move somewhere else. I think if you want to stay you have to accept that people will ask you questions, but maybe if you move to another area/role they will diminish over time.

The amount of helpfulness you show when people ask your questions will determine the amount of new questions you get :-)

Start saying No to things that don’t provide direct value to the organizations. Those are meetings, work, and efforts that may be present that have no legs in the first place.

You will get someone’s baggage anywhere you go. A new job will pile it on fast, but an old job you have to become the decider of your fate and workload. Just start saying no when it gets unattainable.

I have worked for my current company since 2015, so these are tactics I used:

1/ 30m meeting. Everyone who wants to make a meeting with me must via the invitation ( send to my calendar ), and the meeting duration must be 30m ( or less than ).

2/ Document by priority. I track the top 3 problems by their frequency and make the document ( troubleshooting ) next week. Automate your work first, after that, do delegate.

3/ Keep the fire burning. I mean you have to find your top 3 reasons, why you are still here, and work for the company. If you tried but can't find them, leave.

Hope it can help.

I never had this problem before and I switched positions in the same company more than once, in different companies. I think the companies I worked for fell under one, or both, two categories- big companies or good engineering culture.

If a company is big enough you simply get too detached from your previous projects, you might be asked for help here and there but the distance (physical, mental and managerial) will make it harder and harder to actually be productive.

The other type of company understands that it is not sustainable to keep a system maintained by someone with no commitment or dedicated time and will insist on a proper handover to a new owner.

Out of curiosity: Do you hesitate to leave for a new job? If so, may I ask why?

Argue that legacy system needs to be kicked off the kerb, that you do not wish to be the sole owner of these. By making it someone else's problem you will share the pain, and therefore add a voice of "discontent" to change.

For time management, there isn't any silver bullet, and we just have to work around hard constraints. Btw one solution might work for you, but not necessarily.