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

What It Covers

Tobias Dunn-Krahn and Doug Peete from Atono discuss their software development lifecycle platform that unifies product, design, engineering, and operations teams through structured user stories, integrated feature flags, and post-deployment analytics to reduce friction.

Key Questions Answered

• •Structured Acceptance Criteria: Atono treats acceptance criteria as first-class objects with unique IDs, enabling permanent linking, automated story splitting, targeted commenting, and direct attribution of product usage metrics to specific ACs rather than text blobs.
• •Feature Flag Democratization: Built on OpenFeature standard, flags integrate directly into stories with no additional licensing costs, allowing all 400 developers access instead of restricting to 20 expensive licenses, reducing deployment risk through team-wide visibility and automated cleanup suggestions.
• •Story Decomposition Workflow: Default workflow requires design completion before engineering sizing since small design variations create drastically different work levels. Structured ACs enable AI-suggested story splits based on INVEST criteria, particularly optimizing for independently shippable small increments.
• •Post-Deployment Integration: Feature engagement module tracks which acceptance criteria get exercised in production, attributing usage back to specific ACs and teams, enabling data-driven decisions about feature investment while empowering entire cross-functional teams beyond just PMs with analytics access.