You're unable to read via this Friend Link since it's expired. Learn more
Member-only story
Product
What NOT to Do When Rebuilding Your Tech
Startups often feel the need to discard the tech they’re working on and starting over. Here are some of the reasons why this happens . . . and how you can avoid a ‘big bang rebuild’.
‘We’ll probably have to rebuild this one day.’
What starts as an innocent comment can quickly turn into something that comes up at every technical meeting. The backlog is filled with bugs, and less of the sprint is focused on generating value for customers. Iteration cycles take forever, and new ideas are quickly shrugged off as impossible to implement.
Great effort is required for relatively low return and as progress slows, competitors start to rush past you. It’s demoralizing for the technical and non-technical teams alike. Eventually, it’s pure frustration for everyone.
How did we get here?
If rebuilding is the topic on everyone’s list, it’s worth figuring out how you arrived here, before figuring out how to proceed. I’ve seen — and been in — this situation multiple times, so I can hazard a few guesses.
