Vishesh Duggar bio photo

Vishesh Duggar

5x founder. Co-founder & CTO Product @vamstar. 15+ years building and advising startups of all sizes. If you're building something cool, I'd love to hear about it.

Looking for advice on product, strategy or engineering?

Book Appointment

Subscribe to my mailing list


Vamstar LinkedIn Twitter Github

There are many like them marching to the beat of feature churn. And frankly, we’ve all done it. Engineers working relentlessly, managers checking off feature lists.

Fact: Resource utilization is a top concern for management. And why not? High-cost engineers and a thirst for product differentiation drive this mindset.

Product managers see new features as a way to improve the product. I’ve never seen criticism hurled toward a team for pushing out too many features.

What does this yield? A race to track productivity and a healthy bump to the overall complexity of the product. Releases increase, pull requests multiply, bugs get fixed, and features roll out, but does it matter?

Engineering is more than a feature factory.

But what does engineering do with all of this new free time if we decide to slow down and really make every feature win its seat on the train?

Here's what engineers can do beyond churning out features:

1. Talk to customers

Yes, not enough engineering members actually sit on the customer or customer support calls and they should. This gets them closer to the customer who they are building for!

2. Explore

Give them time to explore new ideas. Autonomy to add things that they might interested in experimenting with.

3. Enhance the developer experience

  • Cut the time to set up a developer machine for someone new joining in.
  • Identify and fix things that are slowing engineers down while working on their local machines.
  • Eliminate grunt work that engineers have to carry out regularly.

4. Speed up release times

  • Improve the time it takes to merge the pushed changes for a developer.
  • Cutting the overall time to get to production. Especially things that are carried out manually to push a release if any.

5. Stability

  • Prioritize E2E automated tests. Stability through simulated tests can accelerate releases in the long term.
  • Refactoring code where needed.
  • All the TODO things that have been lying around for years :)

6. Improve Monitoring

Better monitoring equals proactive problem-solving.

7. Upgrade Security

Often overlooked due to fast-paced development, but security is crucial.

Summary

Productivity is easy to showcase, but outcomes are what drive results. So next time you’re caught in the feature churn, remember - there’s more to engineering than meets the eye. Let’s focus on the right things.

15+ Years strategising and delivering growth, engineering, customer value and more. I have served as a CTO to multiple organizations, including Vamstar, AtruHelp, Billaway, SuperSehat, and more.

If you're a founder or CEO eager to move faster and seek tailored strategies for your unique challenges, don't navigate this journey alone. Reach out to me. Together, we can dissect, refine, and optimize your enterprise's trajectory to withstand the tests of time and innovation. Let's make your vision not just a goal, but an impending reality.

I have limited open hours. Book Appointment