Instead of arguing over which software subscriptions to cut when budgets get tight we tried a simple experiment we just turned off editing permissions for four secondary tools for 30 days and forced everyone onto our main workspace.
Turns out, most of the "crucial workflows" those apps handled were completely forgotten within a week and nobody even complained.
It saved us hours of debate. Have you ever tried freezing a tool instead of canceling it right away to see if people actually miss it?
We made a huge blunder at launch by charging flat monthly rates based on arbitrary feature lists instead of tracking how much usage customers actually got out of the product.
Heavy power users ended up paying next to nothing while taking up all our support time and fixing those legacy contracts later created a ton of awkward customer conversations.
If you had to reset your entire pricing model today, would you stick with flat seats or move straight to usage-based tiers?
This is the toughest part of building engineering teams right now. When I started, you learned by grinding through hundreds of basic CRUD endpoints and simple UI bug fixes.
Now, an LLM handles all of that in a few seconds, which has completely wiped out the traditional stepping stones for fresh grads. Companies expecting mid-level skills for entry-level pay are missing the point entirely.
If you're hiring or mentoring juniors today, what kind of actual entry-level tasks are you giving them to help them grow without burning them out?