Reducing the chaos before addressing the complex socio-technical system

Fintech Engineering Strategy. Post VI

The Fintech post series aims to share my personal experience as an engineer manager and later on as head of engineering, which were the challenges, the decisions, and the good and bad outcomes they had. The content has been adapted to keep the decisions without disclosing internal information.

---

Fintech Engineering Strategy Post Series

• Post I. A legacy, a deadline, and no team.

• Post II. Building a product vision, and a team, and replacing Ktor with Spring Boot incrementally.

• Post III. Merging two teams for fast flow.

• Post IV. Simplifying a Ports and Adapters architecture and remove anti-corruption layers made sense from a sociotechnical perspective.

• Post V. Going to production killed fast flow. Understanding how company culture materializes on unaligned team dynamics.

• Post VI. Reducing the chaos before addressing the complex socio-technical system [This post]

---

I introduced the whole context in the previous post. In case you didn’t read it, now it a good moment to do so!

Going to production killed fast flow. Understanding how company "culture" materializes on unaligned team dynamics. Part I

Using the Cynefin Framework and identified that the team was in a chaotic domain, we had to act-sense-respond.

So, how do we move away from the loop of death?

When the teams dynamics aren’t helping but just making it worse?

Making though and focused decisions. One thing at a time.