This is a second article in the series about Nuri rebranding. If you haven't, go ahead and read Nuri — formerly Bitwala; How To Manage An Ambit

Nuri — Formerly Bitwala; How To Migrate A Rebranding

submited by
Style Pass
2021-05-30 01:00:05

This is a second article in the series about Nuri rebranding. If you haven't, go ahead and read Nuri — formerly Bitwala; How To Manage An Ambitious Rebranding, which is more about processes and structure we set up for the rebranding project.

I’ve started working on this project as the only engineer a nd later technical lead in January of 2021. Being the only technical person in it from the start gave me freedom in choosing how to technically proceed with this massive company-wide project. It has been a blessing and a curse. I could do things my way but also anything that doesn’t go well will be attributed to me. That was enough motivation for me to try to make it as seamless as possible.

Before we started hiring people for this specific project (as explained in the previous article), I already started thinking about how to technically deliver redesign. But there were some constraints. Specifically:

Those have been the constraints we needed to work with. And as you can imagine, they meant we couldn't do things in a perfectly orderly manner but we needed to consider all of them before jumping ahead.

Leave a Comment