What are the key takeaways from this Software Engineering Daily episode?

Key insights include: **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.

What did Tobias Dunn-krahn discuss on Software Engineering Daily?

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 topics include: **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..

How long is this episode of Software Engineering Daily?

This episode is 46 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

Software Engineering Daily

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

August 19, 2025

46 min episode · 2 min read

Tobias Dunn-krahn

Episode

46 min

Read time

2 min

Topics

Health & Wellness, Investing, Design & UX

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓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.

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.

Notable Moment

One company with 400 developers could only afford 20 licenses for their feature management tool, forcing critical risk-reduction capabilities into the hands of five percent of their engineering team rather than democratizing deployment control across the organization.

Know someone who'd find this useful?