A good startup = idea x execution x timing + listening to the customers.

One common pitfall is focusing too much on the idea and not enough on the execution.

The execution needs to be good, yet fast. You cannot afford architecting the "best" system, implementing the "best" code etc.

It's a good idea to take on some tech debt but only if you make sure to take care of it.

It's a delicate balance.

What management thinks a developer does:

• drinks coffee ☕
• writes code ✒️

What a developer actually does:

• drinks coffee ☕ or tea 🍵
• reads and understands previously written code ✅
• communicates and plans new features ✅
• challenges plans and provides estimates ⏲️
• makes design decisions before starting to implement 🤔
• writes tests 🧠
• writes code ✒️

If you ask for feedback, and you receive it, and then you don't act on it... then why bother at all?

This is available on a personal level as well as a business one.

If you ask me to spend time sending you some feedback (through NPS or otherwise) and then nothing really happens -- more often than not I get annoyed.

So please, don't ignore #customerfeedback. It will also improve your product or service in the long run, so it's a win-win situation.

And if you struggle with a huge backlog, there are ways to deal with that as well.

Reach out if you have questions - I'm open to technical and non-technical discussions.