Register or log in to access this video
Developing a clear target architecture will take your technical leadership to the next level by improving collaboration, increasing efficiency, speeding up execution and allowing you to make data-driven decisions while building to scale.
Can you imagine if construction workers built a skyscraper using notes scribbled on random bits of paper? Imagine how they would coordinate the plumbing, electricity, floor plans…Yikes! Yet, this is sadly what most tech systems look like – patched up to “make things work”, always fixing “the previous person’s code” and constantly bumping into chunks of code which make absolutely no sense but you’re too scared to remove because you’re pretty sure it does something important somehow.
As the founding engineer of the Cash Flow domain in Pleo, I was privileged enough to play a key role in architecting a whole subsection of the company’s backend ecosystem while building up a team that would take it to new heights. In this talk, we’ll walk through this case study which covers the wins and fails of our journey and ultimately highlights the importance of having a target architecture and how it has helped inform decision-making (technical and non-technical), increase efficiency, improve collaboration and speed up execution while building to scale.
Key takeaways
- How to grow domains and teams based on target architecture
- What is a target architecture diagram and how to create it for different stakeholders
- How target architecture informs decision-making (technical and non-technical), increases efficiency and speeds up execution
