11–20 of 24 posts
One thing that helps me a bit: I try to prioritize based on impact—if something doesn’t directly contribute to growth, engagement, or key goals, I push it down the list. But still, balancing everything is tough. How do you manage?
I’m in the same boat, working at a startup where taking on multiple projects isn’t really a choice. No matter how careful I am with planning, I still end up overwhelmed. Curious to see what others suggest! One thing that helps me a bit: I try to prioritize based on impact—if something doesn’t directly contribute to growth, engagement, or key goals, I push it down the list. But still, balancing everything is tough. Ho…
Whatever estimate you came up with: double it. You think it will take 3 weeks, conservatively? No, it's going to take a month and half. If somehow you deliver earlier then so be it but give yourself ample space to do things properly and avoid burnout. Another thing, which I'm still learning to do, is saying "No" to new projects until you finish at least one of the WIPs.
The general rule is 80% of the work takes 80% of the time, and the remaining 20% takes 80% of the time. Try to get 80% of it done in 50% of the time.
So the goal should be to get development 80% done in 3 weeks and begin QA by then.
I’m in the same boat, working at a startup where taking on multiple projects isn’t really a choice. No matter how careful I am with planning, I still end up overwhelmed. Curious to see what others suggest! One thing that helps me a bit: I try to prioritize based on impact—if something doesn’t directly contribute to growth, engagement, or key goals, I push it down the list. But still, balancing everything is tough. Ho…
Saying “no” is always a choice. If a startup can’t afford to hire enough people to not stress out its employees, it doesn’t deserve to exist
Earlier quoted context omitted.
Saying “no” is always a choice. If a startup can’t afford to hire enough people to not stress out its employees, it doesn’t deserve to exist
I get where you're coming from, but startups often have to make the most of limited resources. It’s less about saying 'no' and more about prioritizing smartly. Have you found a good way to manage workload in a fast-paced environment?
I put in 40 maybe 45 hours of work and the company gets to choose how they get to use that time. I give my input. But they make the decision.
When I need to do “deep work”, I turn off Slack and email. Even before remote work was a thing, I would tell my managers I need some quiet time to get $x done and I’m working from home. They would get a couple of more hours in from me then.
I’m not afraid to say “no” traditionally because I thought I could get another job quickly. Things are of course crazier now and I’m a lot less cocky. But I still have a years expenses in the bank in addition to investments.
I have been working for 30 years almost and I have found that early stage, underfunded startups aren’t worth the effort or the monetary return.
In my later years, I’ve had multiple opportunities to be a “CTO” or “director” of a startup. The positions were always just a glorified team lead. I’ve said no.
Whatever estimate you came up with: double it. You think it will take 3 weeks, conservatively? No, it's going to take a month and half. If somehow you deliver earlier then so be it but give yourself ample space to do things properly and avoid burnout. Another thing, which I'm still learning to do, is saying "No" to new projects until you finish at least one of the WIPs.
There's a trap to be careful of here, because your estimate now is 1.5 months, so it's actually going to take 3 months. The general rule is 80% of the work takes 80% of the time, and the remaining 20% takes 80% of the time. Try to get 80% of it done in 50% of the time. So the goal should be to get development 80% done in 3 weeks and begin QA by then.
Earlier quoted context omitted.
I get where you're coming from, but startups often have to make the most of limited resources. It’s less about saying 'no' and more about prioritizing smartly. Have you found a good way to manage workload in a fast-paced environment?
My thought doesn’t change. Are you a founder? Are you getting outsized compensation for your work? I manage my workload by being able to communicate trade offs between cost, requirements and time and setting a ceiling on how long I’m willing to work. I put in 40 maybe 45 hours of work and the company gets to choose how they get to use that time. I give my input. But they make the decision. When I need to do “deep wor…
Prioritization helps, but in a high-growth environment, trade-offs aren’t always straightforward. You mentioned setting a ceiling on your work hours—how do you enforce that when leadership keeps shifting priorities?
Earlier quoted context omitted.
My thought doesn’t change. Are you a founder? Are you getting outsized compensation for your work? I manage my workload by being able to communicate trade offs between cost, requirements and time and setting a ceiling on how long I’m willing to work. I put in 40 maybe 45 hours of work and the company gets to choose how they get to use that time. I give my input. But they make the decision. When I need to do “deep wor…
Fair points. I’m not a founder, but I’ve navigated three very different domains—business development in high-end fashion (traveling across multiple countries), niche technical leadership hiring, and now technical marketing, SEO, and product advocacy at a product-based startup. Burnout or feeling overwhelmed isn’t pushing me to quit.....I just want to manage it better. Prioritization helps, but in a high-growth enviro…
I was the second technical hire by the then new CTO of a startup I worked for from 2018-2020. He was hired to bring the development in house from a third party consulting company after the company had traction. He was in his 50s and very technical and I was in my mid 40s. The founders were also adults with families. None of us were young tech bros who put the job before everything else.
I was over the architecture and much of the technical strategy. I knew how to talk to them in terms of the business and they trusted my judgment.
> You mentioned setting a ceiling on your work hours—how do you enforce that when leadership keeps shifting priorities?
Just saying “no” especially after I had proven myself. I knew they weren’t going to fire me as long as I was respectful and professional because I was good at what I did - “cloud native development”. They were forced to make a decision about priorities.
Honestly, would I do that now in 2025 with the job market the way it is? I wish I could say I would. But I would probably just suck it up to a point. But most of the time, you can get them to prioritize.
I left that company in 2020 when a job at BigTech fell into my lap. But in 2023, the company that acquired the startup offered me a job as a staff architect based on a reference. When I spoke to the new CTO and described my thought process about trade offs between on time, on budget and meeting requirements and prioritization without burning people out, he liked my response
Earlier quoted context omitted.
There's a trap to be careful of here, because your estimate now is 1.5 months, so it's actually going to take 3 months. The general rule is 80% of the work takes 80% of the time, and the remaining 20% takes 80% of the time. Try to get 80% of it done in 50% of the time. So the goal should be to get development 80% done in 3 weeks and begin QA by then.
Redefine the 20% so it's out of scope.
There's going to be something that gets redefined and that's where company culture falls.