https://selfconference.org/sessions#speaker_458 It’s expected that an experienced team would avoid common issues through the use of all the known tools available. One of the most reliable among those is the development process. For the past four years, I’ve chosen a different path that involves letting such process emerge instead of enforcing it from the start. Let me tell you how I went from a solo CTO, to building a team of experienced and novices that managed to shape our process. Not to its final form. But into a resilient strategy that is constantly changing. Showing how we purposely did not use any of the major, well-known frameworks, and through frequent self-evaluation are continuously evolving our way of work. Not in search to be perfect, but to adapt to the changes of the business, the users and the team itself. I’ll share the path, mistakes, and lessons from this period along with the tools we used to help steer the team and keep learning through the process. This is the story of a small fintech company that started out to build a technology that connects elderly people and banks. Over the course of these four years, the product team had to face many challenges. Ranging from the business model adaptations, embracing pivots, partner changes, and development speed. On the client side, building a UX to help seniors, team changes, security threats and connecting to the different parts of the company.