Empowering Cross-Functional Product Teams with Tobias Dunn-Krahn and Doug Peete

Modern software teams typically rely on a patchwork of tools to manage planning, development, feature rollout, and post release analysis. This fragmentation is a known challenge that can create friction and slow down software development iteration. It's especially problematic for cross functional teams where differences in roles, expertise, and work culture can further complicate collaboration. There is growing consensus that successful software product development requires continuous collaboration across functions, including design, engineering, and operations. Tobias Duncron is the CTO, and Doug Peat is the chief product officer of Atano, which is a software development lifecycle platform focused on cross functional teams. They join the podcast with Kevin Ball to talk about the challenges of modern product development, the importance of low friction UX, the role of AI and product tooling, and how to unify product, design, engineering, and operations in a single workflow. Kevin Ball or Kay Ball is the vice president of engineering at Mento and an independent coach for engineers and engineering leaders. He cofounded and served as CTO for two companies, founded the San Diego JavaScript meetup, and organizes the AI in action discussion group through Latent Space. Check out the show notes to follow Kay Ball on Twitter or LinkedIn, or visit his website, kbal.llc. Hey, guys. Welcome to the show. Hello. Hi there. Alright. Let's get started with a little bit about you two and what kind of led into Atono. So maybe a quick intro and then how that has evolved into what Atonno is becoming. Let's start with you, Tobias. Okay. Hi, everyone. My name is Tobias Duncron. I am a CTO and cofounder of Atonno. I started out in the development sphere over the course of my career in the past twenty five, thirty years. That role evolved into managerial roles. I did get quite involved in the operational side of things over time and then actually ended up doing quite a bit in terms of product ownership and product strategy. So a pretty good swath of the various roles, not all the roles that are involved in making software, but a good little sampler there. And I've worked at companies that are very small, just a few people, all the way up to large public companies, and a lot of that experience actually informs how we've decided to build and the way that we built Atona. But before we get too detailed on that, pass it over to Doug. Hi. My name is Doug, and I'm chief product officer at Atona. Like Tobias, I come from the nineteen hundreds. Been building and designing software for a long time. I'm a geek at heart, started out in the engineering world, but I've always gravitated more towards customer facing type of technical roles, consulting, technical presales, but for the last twenty five years, product management. So, typically, forming with Tobias, a dynamic duo, building out strategy, building out road maps, building out products, getting all the way down to the feature levels that …