Developer Log #3

Posted by

on

in

The whole team is back at work and the first thing we decided to do was to think really hard about how we work. Instead of focusing on shiny new features, we went about fixing how we decide what actually deserves our time.

As Kanka grows, the biggest risk isn’t technical debt, it’s attention debt. Too many ideas, too many “nice things to have”, too many distractions, and suddenly nothing meaningful gets done. We’ve been feeling that friction for too long, and with the new year we finally addressed it head-on by redefining how we plan, prioritise, and work.

We’ve said goodbye from our old Trello setup which has been the backbone of how we work for nearly 8 years. Our new home is a clearer system built around quarterly focus, and on bets that support outcomes. Work that stays front and centre instead of drowning in an ever-growing backlog. The goal isn’t to do less, quite the contrary. It’s to ship better, with intention, and without constantly context-switching.

1. What we shipped

All these changes don’t mean nothing happened this week either. We fixed (and fixed again) a set of issues around password resets that could either not work, or break logins for accounts tied with a Facebook or Google account.

2. What we’re working on next

We now need to define concrete bets for the first quarter and start working on those. One thing that is also in nearly ready is characters having multiple locations.

3. Behind the scenes

We wanted to share this shift early on, even before the first full quarter under the new system is locked in. How decisions get made behind the scenes is precisely what this part of the dev logs are for.


Hopefully you enjoyed this little peek at what we’re working on. We plan to keep these short but frequent. If you want even more tea on upcoming updates, consider joining our Discord.


Comments

Leave a comment